Certificates Overview
A Certificate is a legal document used to transition between phases of a project led by different parties, functions or companies.
A certificate is a summary document that officiates multiple aspects of the Completions database for a scope of work. For example, in a Ready for Pre-Commissioning (RFPC) Certificate, the requirements include:
-
The scope of work for the certificate is all pieces of equipment associate to the Sub-System
-
All construction checklists (A-ITR) for equipment in that scope are complete
-
Any issue of type Punch and Category A are resolved
-
A Final Walkdown Inspection of the work has been completed
-
A turnover package has been created for review
After all those conditions are met, the project can initiate the certificate sign off process where the Issuer individuals (Construction) and the Receiver individuals sign the certificate. After all signature are collected, on most projects, the scope of work transfers from the Issuer team to the Receiver team where they are able to perform their work activities.
Examples of types of Completion Certificates include:
- Construction Complete (CC)
- Ready for Commissioning (RFC)
- Ready for Start Up (RFSU)
- Ready for Operation
- Facility Acceptance
Signed Certificates becomes part of the final Turnover Package that the issuer signs off, saying that they have met all their obligations, and is handed over to the receiver.
View Certificate Details
From the Certificates tab, certificates are listed by columns such as Certificate ID, System Number, Discipline, Status, and Template Name.
You can double-click on a specific Certificate to show you the Certificate’s detail information and Phase List. You can also select a Certificate ID, and then click View Certificate Details.
Reassign a Phase
Before the certificate phases can be signed by the appropriate authorities, the project admin is required to reassign each phase to the appropriate team responsible for signing the Phase. Reassigning tells the user who is responsible to sign that line item, and tells the application to allow signatures.
Although editing a certificate’s Phase Status is a function of the Completions Coordinator or Admin, reassigning a Phase is used by the Coordinator to tell the system, and the user, who is supposed to sign that line item.
Step by Step — Reassign a Phase
- From the Certificate tab, select a Certificate ID to reassign.
- Select a Phase.
- Select Reassign Phase.
- Select a new Responsible Team.
- Click OK.
At this point, Completions starts to evaluate the Workflow Gates defined by the project. It evaluates content for a scope of work such as completion of:
-
Checklists of a certain type
-
Issues of a certain type and severity
-
Inspection of a certain type
Bulk Reassign a Phase
Assigning each phase of a certificate can be a long task for an admin. The admin can assign multiple phases of multiple certificate records at the same time.
Bulk Reassign a Phase
-
From the Certificate tab, select one or many Certificates while holding the CTRL key.
-
Select Reassign Phases.
-
Choose Phases from the lower drop-down menu, and then select to add them.
-
Choose the Responsible Team and add any notes.
-
Select Save.
Update Phase Status
After all Completions requirements are met, you can update the Phase Status to Signed.
A sequencing of certificate signatures is built into Completions to ensure the proper authorities review the turnover package.
In the example of this certificate:
• Construction Discipline signatures need to sign first
• After a single Construction Discipline has been signed, the Commissioning Authority of the same discipline can sign
• The Construction Manager can only sign after all the Commissioning Discipline Authorities have signed
• The Commissioning Manger can only sign after the Construction Manager has signed
It is critical to know that Certificate Gates, created at the admin level, prevent someone from signing off on a Sub-System Certificate unless all Phase Checklists have previously been signed off on.
In the example shown, this system has seven pieces of tagged equipment with a total of 17 checklists. Each checklist must be completed as dictated by the created Certificate Gates.
Progress Roll-Up Reports
To validate that all certificates are completed, you can look at the Progress Roll-up Reports. These reports are configured to be in the context of how the project evaluates completeness.
Step by Step — Progress Roll-Up Report Review
- From the Certificates tab, double-click to select a Certificate ID.
- Click on the Elements context path button.
- Click to open the Sub-System.
- Click on the Sub-System Readiness Reporting drop-down arrow.
- View the number of Completed Checklists as compared to Total Checklists.
In the example shown below, only one of the 13 needed A Checklists are completed.
To view the details on those certificates, click the Certificates context path button to view the current status of the Certificates linked to the Sub-System.
Type A (AITR) qualify against the Construction Complete (CC) Certificate.
Type B (BITR) looks at the Ready for Commissioning (RFC) Certificate.
Type C (CITR) looks at the Ready For Startup (RFSU) Certificate.
If all Certificates are complete, go back into the Certificate and click Update Phase Status > SIGN.
Role of Pending Update
When changes have been made, updates need to be synced to send all updates to the server.
Step by Step — Pending Updates
- Click Pending Updates.
- Review the pending changes.
- Click Publish.
- After doing so, the red Pending Updates button changes to a dimmed No Pending Updates
PDF Reports
Certificate status can be documented as an artifact, or snapshot, of progress.
Step by Step — Generate PDF Report
- Click Save To.
- Navigate to the folder where you want to save the PDF file.
- Rename the file, if necessary.
- Click Save.