Our Story (1)
NCR 1970s until mid 1980s – Introduction to IT
Developed core business applications on NCR-mini computers. Included: accounting , HR, payroll,
estimation, budgeting, and cost control.
1980s – PC Era and Primavera Established
Migration of applications to VAX and then to PCs
1989 to 1998 – The rise of Project Controls Paradigm
DAS Island LNG Project Challenge (limited space and huge fabrication scope)
Logistics and Material Management Challenge
Full Talisman Issued (Project ERP System)
CCC captures major fast track mechanical projects with innovative risk sharing strategy. Thus
becoming the “C of EPC”.
Pyramid: the need to validate progress resulted in introducing lower levels of controls than planning
Established need to control progress at Object level development of shop drawing solutions
extracted from 3D Models (SpoolGen and Taliso)
Material Forward Planning Issued (late 1990’s)
EDI Standard Established to import data from 3D mechanical design systems (PDS, PDMS)
Our Story (2)
1999 to 2004 – I need intelligent 3D!!
Realized the need for visual systems to access multi-faceted project data
VBC & C3D development initiated in parallel with traditional applications
VBC Release 1 was completed January 2002 (document management with an underlying
temporal data structure)
2004 to 2007 – Stirrings of the BIM Era
Major shift back to high quality buildings and civil works
Establishment of BIM Centers to service high quality building segment/GIS
Beta Releases of C3D; tested on project environment around 2007
KM Initiative started
2007 to-date – “The proof of the pudding is in the eating…” We started to harvest
Full implementation of VBC and C3D in CCC projects
Development of best practices in BIM Implementation
Creation of Simulation Department
Development of Earthwork simulator/ Development of Crew Optimization Simulator (CIFE)
Project Control Strategy
Reliant Pull-Driven Technique optimize supply chain rather than sub optimization
Assure availability of resources before start of activity.
Emphasize productivity through the full work chain vs. individual activities
Proper Project Work Breakdown Structure
Integrated EPC schedule with Emphasis on Handover and Construction Activities.
(effective supply chain)
3D model built with WBS in mind and used as primary scope management tool.
Early on Cooperation with the Partners/ EDI definition.
3 Month Look Ahead Schedule/ Material forward plan
3 weeks Look Ahead Schedule
C3D Implementation Steps
• Import BIM 3D model
• Importation of MTO
• Link 3D objects to baseline Activities
• Assign 3D objects to related progress operation templates
• Update progress
Percentage Completion per
Total Cost & Man_Hours
Total Earned Value for Activity
Activities are sorted per ADAC
L6 & L7
EV per ADAC L6 & L7
Future: 3 Week Look Ahead Meeting
All rights reserved to CCC
Visual Project Controls of Plant
Case study – Habshan 5
C3D Visual Project Controls
Work Packages Definition
Applied Workface Planning
C3D Visual Project Controls
Define Field Work-packages: Create small, well defined, Field Installation Work
Packages (FIWP) for the construction workforce using C3D Volumes and
Define FIWP constraints: Each FIWP has a standard list of constraints that must be
satisfied prior to the work being released (example. Use C3D Relations and Queries
to fetch these constraints i.e. a list of all of the things that a Foreman will need to
execute the work: drawings, materials, scaffolds, steel structure etc.
Use C3D to monitor and manage FIWPs: C3D to Produce an Erectibility Study to
visualize results through a 3D view of:
what we should be doing next (the target schedule).
what we could be doing next (information, equipment, resources and materials).
what we are doing next (actuals/reality).
Project Division into work packages
Areas and Sub areas are often very large to analyze
Divide the subareas furthermore to work packages through 3D volumes and aggregations.
Section of a Piperack
substations, building etc…
Define Typical Fragnets for each subarea (standard sequence of work)
Load / Analyze each package separately
FIWP Pipe Racks Definition
Pipe racks in 3D are modeled as one ‘piece’.
Divide Pick Racks into steel structure packages(ST). (designer, fabricator)
If ST packages are not tagged: assign a tag for them.
Define FIWP Constraints
Loading per ST package
Selecting only specific ST packages to be loaded
Analyze each discipline per ST package:
Piping, scaffolding, cable trail etc.
Steel Structure Package Progress
The Steel structure package progress is linked to the 3D model
Packages are assigned a color according to a legend:
Scaffolds are represented in the 3D model as ‘blocks’.
Each block is tagged and assigned attributes such as:
– Scaffold type, level, tag no
Scaffolding progress linked to each level in the package
Target spools (pipes) based on their levels in case:
Different crews are responsible of different pipe rack levels.
Scaffolding is not yet present at particular elevations
Spools & FRs assignment
An isometric span relatively a large area making it
difficult to identify the exact location of the
Assign each spool to its related package.
In case the spools is located in a ST package add
its level in it.
Define Field (Site) priorities
Field Prioritizes based on:
Steel Structure availability
Piping continuity, space
constraints and connectivity.
C3D Gives each Package
Volume a priority tag between
1 and 6 based on above.
Manage FIWPs Constraints
Allocate material and resources
Allocate needed material to
Defined Work packages
On rare conditions, material
is allocated to higher
priority Work Package
Direct Link to Stores and Site
Evaluate – Spools Status
Colorize Spools by Actual Status
The main purpose is to target those spools whose fabrication will lead to proceed with the
line continuity and expand the work front for site engineers.
Spool in site
lay down area
Spool to be
Spool in Fab