Government of Newfoundland and Labrador
Office of the Chief Information Officer
Solution Delivery: Project Management Office
<< PROJECT NUMBER AND NAME >>
BUSINESS PROCESS DEFINITION
VERSION: N.N
DATE <<YYYY-MM-DD >>
Government of Newfoundland and Labrador
Office of the Chief Information Officer
Solution Delivery: Project Management Office
This template is owned and maintained by the Project Management Office (PMO) of the Office of the
Chief Information Officer (OCIO). Direct questions about this template to OCIO-PMO@gov.nl.ca
DOCUMENT OWNER
Client:
Author:
<< Person who created the document >>
Version:
<< First version should be 1.0 and increment up >>
Status
<< Enter status of document (i.e., Draft, Pending Sign-off, Final, et cetera) >>
Date:
<< YYYY-MM-DD >>
DOCUMENT REVISION HISTORY
Date
Version
Description
Author
<< YYYY-MM-DD >>
<< YYYY-MM-DD >>
<< YYYY-MM-DD >>
REVIEWERS OF FINAL DOCUMENT
Identify the individuals who reviewed this document. Signatures are not required.
<<Role>>
<<Role>>
<< YYYY-MM-DD >>
(name)
(signature)
(date)
<< YYYY-MM-DD >>
(name)
(signature)
(date)
APPROVERS OF FINAL DOCUMENT
These signatories confirm this document serves as the business process definition for the << Project
Name >> Project.
Project Sponsor
OCIO Delivery Manager
BUSINESS PROCESS DEFINITION
TEMPLATE VERSION 2.0, 2014-04-28
<< YYYY-MM-DD >>
(name)
(signature)
(date)
<< YYYY-MM-DD >>
PAGE 2 OF 9
Government of Newfoundland and Labrador
Office of the Chief Information Officer
Solution Delivery: Project Management Office
(name)
BUSINESS PROCESS DEFINITION
TEMPLATE VERSION 2.0, 2014-04-28
(signature)
(date)
PAGE 3 OF 9
Government of Newfoundland and Labrador
Office of the Chief Information Officer
Solution Delivery: Project Management Office
TABLE OF CONTENTS
1
BUSINESS PROCESS DEFINITION .............................................................................................. 5
2
COMMON BUSINESS PROCESSES ............................................................................................. 6
<<Process 1 - Description Example>> .................................................................................. 6
<<Process 2 - Workflow Example>> ..................................................................................... 6
3
LOCATION SPECIFIC: <<LOCATION NAME>>............................................................................. 7
<<Process 1 – Location / Description Example>> ................................................................ 7
<<Process 2 – Location / Workflow Example>> ................................................................... 7
4
REFERENCES .......................................................................................................................... 7
APPENDIX A: SAMPLE REPORTS..................................................................................................... 9
BUSINESS PROCESS DEFINITION
TEMPLATE VERSION 2.0, 2014-04-28
PAGE 4 OF 9
Government of Newfoundland and Labrador
Office of the Chief Information Officer
Solution Delivery: Project Management Office
1
BUSINESS PROCESS DEFINITION
This template should only be used when there are no financial processes to be defined. If there are financial
processes please use the Financial Management and Business Process Definition Template for all financial
and non-financial processes to be defined.
<<Note that for each process, if applicable:
 Confirm the use of any existing integrations, if applicable;
 Consider the impact of different locations at all times;
 Identify the approach for segregation of duties;
 Identify the approach for delegation of duties:
o Out of office; and
o Signoff and approval authority.
 Manual and system tasks:
o Only manual and automatic system-related processes should be documented. Processes
that do not influence or affect the system in any way should be omitted.
 Timing of events and tasks;
 For any processes being presented as a description, consider presenting the content as a bulleted
list;
 In documenting processes as workflows:
o
Create workflows as horizontal swim lane diagrams. Swim lanes are used to indicate the
various roles and responsibilities involved with the process;
o
Roles should identify positions rather than individual names;
o
Task connectors should not intersect;
o
Include only the following shapes:
Object
Terminator
Task
Predefined
Process
Description
Terminator objects will typically indicate the Start and End
of a procedure or process
Each defined task should start with an active verb (e.g.
Select, Complete, Confirm, etc.).
Predefined Process objects will be used to indicate that a
defined process or procedure already exists for completing
the required work.
If the predefined process is outside the scope of this
document, reference should be made where to find
supporting documentation for this process. If
documentation doesn’t exist, an exemption should be
requested or the process included as part of this document.
RGB Colour
R:191
G:177
B:207
R:153
G:177
B:208
R:175
G:221
B:128
Dynamic Connectors will be used to connect objects; they
should be attached to objects at both ends, with the arrow
indicating the appropriate directional flow
BUSINESS PROCESS DEFINITION
TEMPLATE VERSION 2.0, 2014-04-28
PAGE 5 OF 9
Government of Newfoundland and Labrador
Office of the Chief Information Officer
Solution Delivery: Project Management Office
o
o
o
2
Decisions should be referenced within the Step Details in the Step Table rather than in the
workflow diagrams;
Each task or predefined process in one swim lane (for one role) should follow the same
numbering scheme (e.g., 1.1, 1.2, 1.3, et cetera) for the Step ID; and
In the Step table, the Role, Step ID and Step Title should mimic those presented within the
workflow;>>
COMMON BUSINESS PROCESSES
<<PROCESS 1 - DESCRIPTION EXAMPLE>>
<<<Insert description. Content may be presented as a bulleted list.>>>
<<PROCESS 2 - WORKFLOW EXAMPLE>>
<<<Insert brief description>>>
Workflow Diagram
<<<Insert workflow diagram>>
Steps
Role
Step ID
Step Title
Step Details
Reports
<<Insert reporting / querying overview related to this process if applicable.>>
The following reports which support this process are included in the Appendix:
Report
<<Insert report name. Link to
report in appendix. >>
BUSINESS PROCESS DEFINITION
TEMPLATE VERSION 2.0, 2014-04-28
Description
<<Provide a description of the report.>>
PAGE 6 OF 9
Government of Newfoundland and Labrador
Office of the Chief Information Officer
Solution Delivery: Project Management Office
3
LOCATION SPECIFIC: <<LOCATION NAME>>
The following business processes are specific to one location. <<Only identify by location if a separate
business process is followed.>>
<<PROCESS 1 – LOCATION / DESCRIPTION EXAMPLE>>
<<<Insert description. Content may be presented as a bulleted list.>>>
<<PROCESS 2 – LOCATION / WORKFLOW EXAMPLE>>
<<<Insert brief description>>>
Workflow Diagram
<<<Insert workflow diagram>>
Steps
Role
Step ID
Step Title
Step Details
Reports
<<Insert reporting / querying overview related to this process if applicable.>>
The following reports which support this process are included in the Appendix:
Report
<<Insert report name. Link to
report in appendix. >>
4
Description
<<Provide a description of the report.>>
REFERENCES
The following table includes a listing of related documentation to this procedure.
BUSINESS PROCESS DEFINITION
TEMPLATE VERSION 2.0, 2014-04-28
PAGE 7 OF 9
Government of Newfoundland and Labrador
Office of the Chief Information Officer
Solution Delivery: Project Management Office
Name
BUSINESS PROCESS DEFINITION
TEMPLATE VERSION 2.0, 2014-04-28
Owner
Comment
PAGE 8 OF 9
Government of Newfoundland and Labrador
Office of the Chief Information Officer
Solution Delivery: Project Management Office
APPENDIX A: SAMPLE REPORTS
<<INSERT PROCESS NAME. LINK TO PROCESS DEFINITION IN THIS
DOCUMENT.>>
Report 1: <<Insert report name>>
<<Include description of report.>>
<<Insert image of the report.>>
Report 2: <<Insert report name>>
<<Include description of report.>>
<<Insert image of the report.>>
<<INSERT PROCESS NAME. LINK TO PROCESS DEFINITION IN THIS
DOCUMENT.>>
Report 1: <<Insert report name.>>
<<Include description of the report.>>
<<Insert image of the report.>>
Report 2: <<Insert report name>>
<<Include description of report.>>
<<Insert image of the report.>>
BUSINESS PROCESS DEFINITION
TEMPLATE VERSION 2.0, 2014-04-28
PAGE 9 OF 9