Change Projects organize the proposed changes in an organization as a set of interrelated tasks that must be performed over a fixed period with necessary approvals. This ensures that the change process is initiated, implemented, and delivered effectively to all stakeholders.
A Change Project in MOC stores all the details about a change. When you create a Change Project in MOC, you must provide details about the change. This includes details such as the scope of the project, the purpose of the project, the asset(s) that will be impacted by the change, and the type of change that is being implemented. You can also add team members who will approve and manage tasks proposed in the Change Project. You can associate related files as Reference Documents. A reference document can be any document that is relevant to implementing the change (e.g., a drawing or an equipment detail document).
After you define the Change Project, you can associate the Change Project to the following records:
Change project types are used to describe the type of change which is being undertaken. In MOC, a Change Project can be of one of the following four types:
Temporary: Indicates that the change is planned for a limited duration.
Permanent: Indicates that the change is a major change that will remain unchanged for a longer duration.
Minor Instrument Change: Indicates that the change includes minor modification to the process or equipment and does not significantly affect the workflow in the organization.
Personnel: Indicates a change in the organizational structure, change in number of employees, change in the contractor for a site, or development of a new role in the organization.
Note: The change types described in the above list are available in GE Digital APM by default. As needed, you can add or remove change types by modifying the MI_Change_Project_Type System Code Table.
Based on the type of change, you can configure Checklists and use them to drive the efforts towards the implementation of change.
