Technical Services

PQS & Technical Services are responsible for highlighting variance in meeting promise to user. The CU will interface with the Assurance Manager(s).

Deliverable Map

Visioning
  • Translating the P0 technical deliverable into the overall G- Six commitment map
  • Resource Identification: Formation of commissioning teams with experts from Process, Product, Design, Function
Specification
  • Confirming PG parameters to fulfill the P0 commitment.
  • Prepare Commissioning Plans & Procedures, Confirming PG parameters
  • Ensure availability of ITP aligned to the QAP provided by Engg Manager
  • Supporting the Project team in HAZOP study
Build
  • Reporting variance in Quality and Safety as per standard and COPQ.
  • Analysis of variance and feedback
  • Readiness for commissioning using pre-commissioning checkpoints.
  • Commissioning
Handover
  • Compilation of plug list items (handover to Assurance Manager for liquidation)
  • Final Document submission to stakeholder – (including Protocols, As built drawings etc.)
  • PG Tests
  • Submission of learning documents for deployment in future projects

In the Visioning Phase:

In the 1st phase an execution excellence document is created incorporating all the learnings from the previous projects. In this phase, they also plan for the formation of commissioning teams.

In the specification phase:

The Project Manager is looking for comfort if we are on the right track. This is the last chance to check before we place orders and move ahead into build.

While traditional quality role gets trapped into the details of whether something is working or not. Technical Services is taking a helicopter view of the project. They have access to all the technical specifications, designs. Without getting lost in the mass of details, they are able to gauge if we are headed towards our outcome and all the pieces are fitting together or not. So, the focus is not checking veracity of details but to ensure internal consistency and alignment to the purpose. If they find an inconsistency, then they can deep dive.

Therefore, the checks being done by Technical Services is an offline activity, not a series activity which is duplicating the work of the functions or holding up the project.

This group can play a role in a final check – to ensure the technical specifications will lead to excellence as per requirement.

In this phase, they also prepare commissioning plans and procedures.

So, while the locus of the role has been in the build and handover stage. However, what also emerged is that if the specification stage is thought through, we would have addressed many things which could go wrong, at a fraction of the cost.

In the Build Phase:

  • In the build phase, the team is assuring the project manager of safety and the quality of equipment, people, material, execution in the project. While every function is creating and following their QAPs (as a self-managed team). Just like in maker and checker, this team is playing the checker role to assure whether what is promised is being delivered or not. (while not duplicating work)
  • There are several backend quality and safety roles they may be playing with the several functions like construction and manufacturing. They have not been considered here.

Aside: It was noted thatCost of Poor Quality (COPQ) can be made the measure of quality. It will make people accountable for poor quality.

Clarify your doubts & questions about the model with the Implementation Team: Post your question