Completions Overview

The CCMS software suite is comprised of a complete set of Construction, Mechanical Completion and Commissioning modules designed to manage planning and work activities from early engineering stages through startup and turnover to operations. It is designed to manage one or multiple projects all within one database, and can roll up reporting to the Project Governance Management System (PGMS).

The CE CCMS is the most comprehensive system on the market because it provides visibility of completions throughout the full project lifecycle.

CCMS - 'Typical' Implementation Process:

The diagram below defines the general life-cycle of the usage of a CCMS.

Step 1: Import Engineering Data, Define WBS, Systemization, Location, Structures, and Role Profiles & Rights assignments to Users.

Step 2: Develop Task Models, Test Profiles, and Format Test Forms.

Step 3: Configure TOP requirements, Perform PCA, and Enter RFIs.

Step 4: Batch Assign Tasks, Define TOP Packages & Content Requirements.

Step 5: Develop Job Cards, Schedule JCs and Complete Baseline S-Curves.

Step 6: Perform Resource loading vs. Workload Requirement Analysis.

Step 7: Execute Work Packs, Track Punchlist Items and track custody transfer of Subsystems and Systems, Generate "Completions" reporting.

The following list of questions is intended to find out if the database is ready for population and end users ready to use the product. Often circumstances do not allow for this to happen so it is therefore important that these items are acted upon and completed ASAP.

Browser Requirements:

Do end users have Internet Explorer 10.0 or greater or Chrome installed?
Do end users have a PDF viewer on their machines?
Does the project want to use mobile solution?

Database Requirements:

Where is the database going to be located? Hosted in Data Center or Client Network?
Who is going to maintain the data?

Access Requirements:

How many users are going to use the CCMS on the project?
Are all users located on the same network, or will access the CCMS from different networks?
Does IS&T block all sites, but specified sites?
Does data from each company need to only be accessed by that company? Or is information shared among companies?
Does the project want to implement user profiles or granular role strategy?
Do you have a list of users and their associated responsibilities?

Project Status and Responsibilities:

What is the target commissioning and C&SU dates?
What is the total CAPEX budget for the project?
Where do they stand % complete in Detailed Design?
Where do they stand % construction completion?
Is there a responsibility Matrix developed for the project?

Project Data Requirements:

Does the project have a Process Breakdown Structure (PBS) - Systemization.?
Does the project have a Locational Breakdown Structure (LBS)?
What is the established Work Breakdown Structure (WBS)?
Is the equipment, instrument/loop, cable, line / valve list available and IFC status or greater?
Is there a master document list available?
Does the project want to put the latest approved version of documents into the database (pdf)?
Does each discipline leads have a “test profile” for tag types (i.e. classes) available?
Does the project have forms they want to upload into the CCMS? Are they in Word format?
Does the project want to use paper or digital only approach, or combination thereof?
Has Punchlist list Categories or Priorities been determined?
Has the project defined the different handover packages, and content requirements?
Are vendors going to use the system, and if so, do you have their forms and test profiles?

The typical inputs and outputs of a CCMS are:

Items we typically import into the database are (in .xls, .xlsx, .csv):

Mechanical Equipment List
Electrical Equipment List
Instrument Index
Cable Schedule
Piping & Valve List
I/O list
Document List

Optional items that can be imported:

Work Breakdown Structure (WBS)
Process Breakdown Structure (PBS)
Location Breakdown Structure (LBS)
Activity List from the Master Schedule (e.g. P6 or Project Schedule)

CE has the ability to bulk upload electronic documentation into the database against the Document IDs (or records) in the database. The CE bulk upload utility is designed to upload both NATIVE and PDF formats. The upload utility is only provided to those appointed personnel responsible for either periodically uploading the latest documents or uploading completed scanned forms.

Uploading Electronic Documentation: CE can bulk upload electronic files into the database against their associated document ID. We can bulk upload PDF files, MS Office files, and even ACAD files with XREF data, if required. We have uploaded over 27,000 files in a little over 3 days before for clients that use CE for document control.

Uploading Paper Based Forms: CE utilizes QR Codes for all test forms and our utility reads the QR code and matches the form to the task in the database, completes the task, uploads the file into the database and allocates the scanned form into the appropriate turnover package automatically.

CE includes advanced Batch Editing features that allow an advanced user to mass change project information such as batch editing assets into subsystem, entering in OEM information, or assigning tasks to equipment.

The CE database is an advanced database that has over a 1,000 tables and 10,000’s of fields. To illustrate at a high level, diagram below will show how the use of common core data structures can link most information together in CE. By linking this information it dramatically simplifies usage while improves searching, reporting and handover of information.

Abbreviation	Definition
LBS	Location Breakdown Structure is the backbone of location-based management. To get greatest benefit for the project, all subcontractors working on the same construction phase (for example, superstructure or interiors) should agree on one LBS. The typical practice in projects has been that each subcontractor plans their own work using different location breakdowns.
OBS	Organizational Breakdown Structure displays organizational relationships and then uses them for assigning work to resources in a project. The hierarchical nature of the Organizational Breakdown Structure allows for the appropriate resources and responsibilities to be assigned. While the WBS is used to define the project during early stages of its cycle, the OBS provides an organizational structure for the project as it moves to completion.
PBS	Process Breakdown Structure, also known as systemization is a breakdown of equipment into major process systems. The systems are ordered to facilitate the planning, sequencing and control of completions & commissioning activities.
WBS	Work Breakdown Structure is a hierarchical decomposition of the project into phases, stages, activities and eventually work packages. It is a tree structure, which shows a subdivision of effort required to achieve an objective. In a project or contract, the WBS is developed by starting with the end objective and successively subdividing it into manageable components in terms of size, duration, and responsibility to achieve the objective.

Next Training: Planning & Task Assignment

For internal use only