1.4 Agility MOC Terminology
There are a number of different terms and abbreviations used within the subject of Management of Change and also within the Agility MOC Module. The following is a list of common terminology used.
1.4.1 MOC
Management of Change.
1.4.2 Change Request
This is the initial stage in the MOC process and involves an Originator recording the details of the change being requested.
A Change Request cannot not be closed out until all associated Change Request Actions have been closed out and also that all Additional Approvers have approved the Change Request for close out.
1.4.3 Originator
This is the person that raises the change request in the first instance.
1.4.4 Coordinator
This is the person responsible for review the initial Change Request to identify if the change is go forward or will be rejected. The Coordinator is also responsible for defining the Collaborators and issuing the change request for review.
It should be noted the title Coordinator can be changed and configured to meet an organisation’s internal process.
1.4.5 Collaborator
This is the person or in most cases persons that are requested by the Coordinator to review the Change Request and provide comments and ultimately to vote on whether the Change Request should go forward or not. The system allows for multiple additional Collaborators.
It should be noted the title Collaborator can be changed and configured to meet an organisation’s internal process.
1.4.6 Change Request Owner
This is the person that will be nominated by the Coordinator who will manage the Change Request as it progresses. There can only be a single Owner for a Change Request.
It should be noted the title Owner can be changed and configured to meet an organisation’s internal process.
1.4.7 Additional Approver
There are people that can be nominated for a Change Request; these people are then required to approve the change request for close out prior to the Owner being able to close the Change Request. The system allows for multiple Additional Approvers.
1.4.8 Change Request Action
This is an individual action associated to the Change Request that requires completing and closing out. A Change Request does not require an Action to be raised, though it is recommended to take full advantage of the action workflow.
There is no limit as to the number of actions that can be raised for a Change Request.
1.4.9 Change Request Action Owner
This is the person that will be nominated by the Change Request Owner who will manage the Change Request Action as it progresses. There can only be a single Owner for a Change Request Action.
It should be noted the title Change Request Action Owner can be changed and configured to meet an organisation’s internal process.
1.4.10 Change Request Action Subscriber
These are the people that can be defined as requiring to be made aware of actions within a Change Request.Subscribers will be required to acknowledge that they have read, understood and implemented the action.Change Request Actions cannot be closed out until such time that all Subscribers have submitted acknowledgement.