Smart Completions Overview - Intergraph Smart Completions - Intergraph Smart Completions Update 18 - Help - Hexagon

Intergraph Smart Completions Help (5.3.18)

Language
English
Product
Intergraph Smart Completions
Search by Category
Help
Smart Completions Version
5.3.18

The Smart Completions software suite is comprised of a complete set of Construction, Mechanical Completion and Commissioning managers 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.

SC_Visio-level2

'Typical' Implementation Process:

  • 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 Edge 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)

The Smart Completions 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 Smart Completions. By linking this information it dramatically simplifies usage while improves searching, reporting and handover of information.