The following describes the roles and responsibilities of the project team expected from any client who intends to implement SOLABS QM10.
Project Owner |
Main stakeholder on the Client’s side. This person is responsible for assigning resources, endorsing project change requests (if any), and approving deliverables. This person also provides final and definite approval of the project and project closing. |
Steering Committee | Monitors and reviews the project’s progress; keeps the project scope under control as possible emergent issues force changes to be considered and ensures the project's scope aligns with stakeholder group's requirements. |
Project Manager | Acts as main contact point for SOLABS’ project manager. Responsible for project communications internally as well as coordinating the work of resources internally. |
SOLABS QM Super User / SME | Advanced system users and experts in the internal workings of areas impacted by the automation project. Typically: Training administrators, Document coordinators, Process Owners and/or System administrators. |
System Owner |
Responsible for setting up Level I support internally, and to ensure that the system remains under Change Control during its Life Cycle (i.e., while in operation). |
Quality Assurance Representative | Reviews and prepares the validation documentation for Client. Supports validation activities associated with the project. |
IT Representative | Offers technical support and coordination during the project. Reviews and approve technical documents. Facilitates and coordinates different integration scenarios. May also be responsible for setting up Level 1 support internally. |
Note: It is understood that a single person may take several roles mentioned above.
Comments
0 comments
Please sign in to leave a comment.