Professional Documents
Culture Documents
Version: 1.0
TABLE OF CONTENTS
1 Sign-Off .................................................................................................................... 3
2 Problem Statement:.................................................................................................. 4
3 Vision ....................................................................................................................... 4
4 Project Scope & Description ..................................................................................... 4
5 Roles......................................................................................................................... 5
6 AMS Workflow ......................................................................................................... 5
7 Setup Table –Parameters ......................................................................................... 6
8 System Administrator............................................................................................... 7
9 Reports & History ..................................................................................................... 7
10 Email Alerts / Reminders......................................................................................... 7
11 Annex – A (Process Flow)......................................................................................... 8
12 Annex – B (Demo Document) ................................... Error! Bookmark not defined.
1 Sign-Off
2 Problem Statement:
Documents of any organization have to go through a long chain of physical approval process, which
cause serious delays in the routine official work. Even, users have to face loss of documents some-
times during the physical circulation of papers. Steps in a manual process allow each reviewer /
approver to make changes or comments that subsequent reviewers / approvers can read, once the
physical document is received. Manual processing involves significant time and resources to be
spent preparing and routing change documents for review and subsequent approvals. Bottlenecks
include copying, distribution & receipt of approval files; manually tracking and reporting of status;
indefinite waiting for the key personnel to sign off especially when they are out of office / travelling.
3 Vision
To over-come the above situation, UBL Centralized Procurement is intended to develop a
comprehensive automated Approval Management System (AMS) to manage internal approvals in
a sequential unified format. Through a single repository, this approval process will efficiently track
the document and will eliminate the need of human tasks involved with the approval process
(Sending / Receiving / Physical Sign-offs) and will provide the real-time status of the document
during & after its approval cycle.
Equipped with an intuitive graphical interface, AMS will also increase the security and
confidentiality of the documents, while letting approving managers create an IT audit trail of all
actions, identities, TATs and comments.
a. General
• Internal Approval Memo
• Corporate Communication
• Procurement Requisitions
b. Financial
• Procurement Approval Note
• Annual Maintenance Contracts
• Payment Authority Memo
• Budget / Tax Amendments, Trainings, Travel & Entertainment related approval memos
5 Roles
This section represents various roles and profiles that are outlined in the Active Directory &
further will be defined in the approval process. The initiator will define the reviewer (optional) &
approver of the request to enable access of the published documents.
6 AMS Workflow
1. Initiator logins the system with the domain credentials. Upon login, system gets the details of
user from AD i.e. Name & Department along with the availability of current timestamp (logged
in Date & Time) on the form.
5. Approval Type
a. General
b. Financial
6. Expense Currency
a. PKR
b. USD
c. Any other currency (if required)
7. Nature of Expense
a. OPEX
b. CAPEX
8. Budget Status
a. Budgeted
b. Non-Budgeted
9. User inputs complete detail on the form that includes business case, summary, justification /
requirement & financials etc. in the approval description tab.
10. In case the reviewer/approver is on leave the document will be re-routed to the initiator
through system administrator.
11. Attachment option in the form is available for the attachment of related documents. These
will be viewable with the serial number, name & type of file.
12. Once the required mandatory fields are completed, the user submits the approval to next level
as defined in the reviewer & approver grid.
13. The reviewer logins & review the “Pending for Review” documents in his bucket for necessary
decision (approved / reject / enquire/ send back to initiator).
a. Approved - Document will be approved & will follow the further defined approval
hierarchy.
b. Reject - Document will be rejected & send back to initiator with proper log.
c. Enquire – Document will travel one step back with the required query & will fall in “on
hold” bucket till the recipient responses the query.
d. Send back to initiator - Document will be returned to initiator for the desired amendment.
Approval cycle will be re-initiated after changes.
14. Subsequent to the approval of reviewer, approver receives the document in his bucket for
necessary decision (approved/reject/enquire/ send back to initiator).
15. Approver/reviewer can always add comments on the note in the Comments Box.
16. Complete history from initiator to approval of the document will be available.
17. AMS dashboard contains the complete database details of the notes as follows:
Sample Grid:
Approval
Expense Currency Nature of Expense Budgeted Status
Type
General PKR OPEX Budgeted
Financial USD CAPEX Non- Budgeted
(Any other Currency)
Table for the re-routing of request will also be made available in the system for the administrator
to cater correct routing, in case of leaves of respected person or any mistake / error.
Audit log of parametric changes will also be maintained. Administrative rights for the interim
period will remain with the Centralized Procurement. However, rights will be transferred to IT
later on.
8 System Administrator
System administrator will have full rights to modify, add, delete & re-route requests as well as
to modify the setup tables.
• All related participants will also receive email reminders of the pending tasks in
accordance to defined TATs.
Yes
Reviwed Approved
Submits
A
A A/B A/End
Annex- B
Centralized Procurement
Financial /
Amount in PKR / USD CAPEX / OPEX Budgeted / Non Budgeted
General
Subject Re:
Approval Description:
This content box may be comprising of text, cell pasting (excel sheet), image etc. (no limit
constraint)
Submitted by:
__________________
Logged In User
Reviewed By (optional):
___________________ ___________________
AD User 1 AD User n
Designation Designation
Approved By:
________________ ___________________
AD User 1 AD User 2
Designation Designation
________________ ____________________
AD User 3 AD User 4
Designation Designation