Traditional design services provided 2D drawings and separate data lists, where as BIM typically provides a 3D representation of the asset, with each component in the 3D model containing meta data to describe the specification of that object. This allows for seamless transfer of data from the design package to technical specifications without the need to transpose data manually across multiple documents.
1. Organizational Information Requirements (OIR)– Although Process Group can not execute this, we are available to discuss options based on what has been seen within the industry.
2. Asset Information Requirements (AIR) – Process Group would prefer to work with the client to define the Asset Data specification, allowing us to identify the client's needs, providing suggestions of typical norms within, and outside the industry. This section would consider design codes and standard to be employed as well as the key design data to be captured for each asset.
3. Employer’s Information Requirements (EIR) – Process Group prefer to would work with the client to capture the key deliverables on final as-built design documentation, operating and maintenance manuals, commissioning /validation data, and the storage location/systems of the data.
4. Digital Plan of Works (DPoW) – The PDD (Project Definition Document) defines the key deliverables (from the AIR & EIR) in the Scope of Work section. The Schedule section would define the key data and associated delivery milestones (soft Landings) using a standard stage gate process. For more complex projects, separate PDDs would be developed to further refine the detailed sections of a larger project.
5. Common Data Environment (CDE) - The ability to share design documents throughout the project is key to an efficient process, allowing regular design reviews/guidance before significant rework is required. Document management is at the heart of our process, yet we offer a flexible approach, either using the clients web based tools, Process Groups cloud based document management system database, or collaboratively develop a SharePoint site or similar. For larger projects we can provide access to the live design data allowing online commenting, with the option of maintaining the system for the full lifecycle of the plant/site.
Typically Asset Information and Project Information are developed in parallel using the same data environment, however the asset data contains additional metadata providing efficient data retrieval for ongoing asset lifecycle management.
6. BIM Execution Plan (BEP) – The PDD is further enhanced from the The Digital Plan of Works setting out the Objective, Scope, Timing, Costs, Project organization, Risks & Opportunities and approvals. One hour spent on upfront definition can save weeks of none value added downstream rework. Larger projects would also be tracked with a Gantt Chart providing a clear picture of the key steps and timing to achieve the overall goal.
Known deliverables (Design documents) are populated in our document management system early in the project, starting as early as the Scoping phase, becoming more detailed through the Feasibility & Development phases to a definitive set in the Validation phase. This provides progress visibility of the deliverables throughout the project lifecycle, including the status of final update of asbuilt data to the client document management system.
Project Planning with suitable milestones and stage gates provides clarity for all parties on the scope, timing and key deliverables.
7. Project Information Model (PIM) – Our approach is to develop Asset Information (AI) as a deliverable throughout the project, resulting in a seamless transfer from Project Information (PI) to AI. The data from the common data environment used during the project development is seamlessly transferred (with revision update to “As-built”) to the clients Asset Information Model (AIM). In addition, project related documents such as Gantt Charts, Action & Decision Logs which a critical to be shared across the project team, but ultimately would be discarded at the end of the project since they would not be required to maintain the asset throughout its lifecycle.
8. Asset Information Model (AIM) - The use of an Engineering Document Management System (EDMS) is critical to managing Asset Information. There are a myriad of systems used by industry, hence we have to be flexible to adapt to the clients systems. For small projects or for clients without sophisticated corporate systems this can be as simple as a SharePoint site, or managed through Process Groups cloud based asset management database. However for larger projects, and especially for large asset reverse engineering programs, a fully integrated engineering database solution such as Aveva Engineering is recommended allowing integration to the 3D Model, PIDs, other drawings & datasheets.
It is possible to maintain live data via Aveva Engineering (or similar) with revision history, and as a backup store “project snapshots” of asset data in a separate EDMS system such as corporate SAP system linking to the Maintenance module.
9. Master Information Delivery Plan (MIDP) - The deliverables would be defined at a high level in the PDD scope section at a minimum identifying the discipline documents and main assets. This definition would be further defined during each phase of the project in collaboration with the client.
10. Soft Landings – Our open approach for document collaboration, and continual document definition through the project lifecycle enables the client to see the design in real time. This allows the client to understand and guide the design and maximizing the ability to achieve the desired scope, preventing costly rework and delays.