Table of Content
General Terms
Explanation of common terms related to O3.
Admin Terms
Terms used by System and Project Administrators in O3.
Project Usage Terms
Terms used in relation to O3 Projects.
General Terms
Explanation of common terms related to O3.
Term | Description | Category |
Agile | Agile methodology is a project management framework that breaks projects down into several dynamic phases, commonly known as sprints. The Agile framework is an iterative methodology. Scrum and Kanban are example agile approaches. | Term |
Autodesk ™ | Professional CAD/CAM Tools, Integrated BIM Tools, and Artistic Tools. 3D Design, Architecture, Construction, Engineering, Media, and Entertainment Software. | Term |
AWP | The Construction Industry Institute defines Advanced Work Packaging (AWP) as the overall process flow of all the detailed work packages (construction, engineering, and installation work packages). AWP is a planned, executable process that encompasses the work on an EPC project, beginning with initial planning and continuing through detailed design and construction execution. AWP provides the framework for productive and progressive construction and presumes the existence of a construction execution plan. | Acronym |
BIM | Building Information Modeling (BIM360 is an Autodesk software product supporting BIM) | Acronym |
BOM | Bill of Materials | O3 Entity |
CII | Construction Industry Institute | Acronym |
CM | Construction Manager | Acronym |
COAA | Construction Owners Association of Alberta | Acronym |
Construction Equipment | Within O3, this refers to any items that cannot be (easily) hand carried such as wheeled generators, compactors and vehicle-based equipment such as tractors, trailers, forklifts and excavators. For handheld items such as hammers, grinders, saws, etc. refer to Tools. | Term |
CWA | Construction Work Area | O3 Entity |
CWP | Construction Work Package | O3 Entity |
Deployment | In O3 terms, it's a hosted website (URL) for a client that can contain one or more O3 projects. | Term |
DWP | Design Work Packages | O3 Entity |
E&I/I&E | Electrical and Instrumentation | Acronym |
Entity | Is an object in O3, such as a Work Pack, Drawing, RFI. In database terms these could be considered a table of related records. | Term |
EPC | Engineering, Procurement, and Construction | Acronym |
EWP | Engineering Work Package | O3 Entity |
Export | A means to transfer data out of a system or platform such as O3. | Term |
FEED | Front-End Engineering Design | Acronym |
FIATECH | Fully Integrated and Automated Technology | Acronym |
FIWP | Field Installation Work Package | Acronym |
GF | General Foreman | Acronym |
Grid | This is where data is presented in a tabular format. | Term |
HSE | Health Safety and Environment | Acronym |
IAP/IPP | Interactive Project Planning | Acronym |
IFC | Issued for Construction | Acronym |
IFP | Issued for Procurement | Acronym |
IFR | Issued for Review | Acronym |
IM | Information Management | Acronym |
IMM | Integrated Materials Management | Acronym |
Import | A means to bring in/upload external data into a system or platform such as O3. | Term |
ISO | Isometric Drawing | Acronym |
ISBL | Inside Battery Limits (ISBL) refers to the responsible project scope area as would be indicated on a plot plan. Areas outside but that may interface/impact with the project site area are called Outside Battery Limits (OBSL). | Acronym
|
IWP | Installation Work Package | Acronym |
KPI | Key Performance Indicator | Acronym |
Layout | These are formatted and stored (mainly) data grids or form layouts. For example, you may have an IWP grid layout with just 5 columns of interest and filtered for a specific CWA. You can store this as a layout and retrieve for later use. Grid layouts can also be shared with others. Form layouts typically have a system default, but variations of say an IWP form layout can be saved. For example, you may have a contractor form being different to your owner form layout. | Term |
LWP | Labor Work Package | O3 Entity |
Materials | These are commodities/items that engineers/designers determine required for installation/construction purposes to realize the design. In O3 terms, these may be part of a larger construction component, such as a pipe spool in the 3D model or can be independent as applicable (such as bulk items like bolts, nuts and fixtures and fittings, etc.). See also BOM. | Term |
MAWP | Module Assembly Work Package | Acronym |
MMS | Material Management System | Acronym |
MRR | Material Receiving Report | Acronym |
MTO | Material Take-Off | Acronym |
MTR | Material Test Report | Acronym |
MWP | Module Work Package | Acronym |
NCR | Non-Conformance Report | Acronym |
OSBL | Outside Battery Limits (OSBL) refers to the areas of interest on a plot plan that are not directly the responsibility of the project scope. This might be an external power or data supply that needs to be connected to the project site or a place where the project will eventually deliver the product via pipe to external infrastructure, etc. Areas inside the project area are called Inside Battery Limits (See IBSL). | Acronym
|
O3 | O3 is the overall name for our agile, AWP implementation software product. | Term |
O3 Solutions | The software company that produces and maintains O3 software. | Term |
ONx | The 'ON..' series references are used for grouping O3 software offerings and functionality, for easier consumption of information, by breaking this out into typical project lifecycle stages. See below. | Term |
ONBuild | Effective Workface Planning requires a single comprehensive tool that can scope, manage, and progress all Installation Work Packages across all disciplines (not just pipe and steel), functions, and package phases. ONBuild is the first comprehensive Workface Planning solution that combines sophisticated graphical work packaging with true constraint management, and comprehensive reporting and analysis to identify and resolve problems before they impact productivity. | Term |
ONDesign | Providing value directly to the Engineering and Procurement teams is critical to driving AWP adoption. Forcing Engineering and Procurement to adjust their work process to benefit construction downstream can make the overall project more productive. AWP mature organizations understand that the best path to efficiency is one where every department actively embraces the better process for their own benefit and for the benefit of the overall project. | Term |
O3Go | This is a grouping for O3 mobile related offerings such as Tool Time and Safety Observations. | Term |
ONPlan | O3’s ONPlan solution is designed to make the AWP project setup easy, scalable, repeatable, and consistent. Maximizing AWP benefits over the life of a project requires starting the project with AWP in mind. ONPlan makes that process simple with purpose-built tools that can be configured to your organization’s specific AWP approach and then saved as templates to be reused on other projects. | Term |
ONSafe | ONSafe Mobile Safety Tracking from O3 Solutions delivers real-time safety observations from the field. Safety is the most important thing on any well-run job site. Targeting zero safety incidents starts with a consistent, simple, and efficient way to collect accurate data on safety exposure. O3’s ONSafe mobile app allows users to perform mobile safety observations in the field. This is a separate O3 software module. See O3 Entities – Safety Observations and Safety Reporting. | Term |
ONStart | Successful turnover requires an understanding of the true status of the installation of systems and the power to act to drive completion. ONStart gives Owners the real-time information they need to identify blocking items, assign their completion, and track progress. With barriers removed, work can proceed quickly with automated approvals and deliverables to take work from construction to operations. ONStart is the first solution to give Owners the power to not only understand status and issues but also drive their completion for an on-schedule project. | Term |
ONTarget | Get your entire team out of spreadsheets and into one cloud platform sharing data in real time. O3’s ONTarget solution allows each team member to visualize their actions and priorities to manage their entire workload and avoid surprises. This provides project leadership with valuable insight into project status, allowing them to focus attention in the most critical areas. | Term |
ONTools | Mobile tool-time tracking in the field to drive productivity. This is a separate O3 software module. See Tool Time. | Term |
P&ID | Piping and Instrumentation Diagram | Acronym |
Pilot | This term refers to a trial implementation of O3 to test its capabilities. | Term |
PCF | Piping Component File (PCF). PCF is a BIM standard file format used in industrial piping. |
|
PFD | Process Flow Diagram | Acronym |
PMT | Project Management Team | Acronym |
POC | Path of Construction | Acronym |
Production | Refers to a live, in use business scenario. See Deployments and Projects, Sandbox. |
|
Project Settings | Term used to describe where the project is configured and what settings are specific to the project (vs System Admin settings, which are deployment wide). | Term |
PWP | Procurement Work Package/Procurement Work Process | O3 Entity |
QA | Quality Assurance | Acronym |
QC | Quality Control | Acronym |
RFI | Request for Information | O3 Entity |
Sandbox | Used to describe typically a project or area where you can train and test/trial functionality without impacting Live / Production projects. | Term |
SAML | Security Assertion Markup Language is tied to Single Sign On whereby your organization will manage and verify who you are (like Windows), and if verified, O3 will log you in. | Acronym
|
SMARTStart | O3’s implementation approach facilitates quick wins with minimal disruption. The goal is to drive our clients to self-sufficiency as soon as possible. SMARTStart is an agile project management approach where we plan and measure progress in 2–4 week Sprints. Starts from Kick Off Meeting through training and User Acceptance. | Term |
SME | Subject Matter Expert | Acronym |
SPRINT | This is an agile term that is typically SCRUM related, where work to do is refined, prioritized from a backlog (of to do items), and selected for the next 2 (typical) to 4-week schedule. O3 implementations and product development typically work in Sprints. | Term |
STO / SDTA / STA | Shut Down Turn Around | Acronym |
STP | System Turnover Package | O3 Entity |
SU | Startup | Acronym |
TA | Turnaround | Acronym |
TIC | Total Installed Cost | Acronym |
TO | Turnover | Acronym |
Tools | Within O3, this refers to any items such as hammers, grinders, saws, etc. that you wish to manage as resources on your package (typically for IWPs). These are generally handheld manual and powered items vs construction equipment that you cannot (easily) carry such as wheeled generators, compactors and vehicle-based equipment such as tractors, trailers, forklifts and excavators. | Term |
TOOL TIME | Part of our ONTools functionality. Includes tool time observations and reporting. | Term |
TOP | Turnover Package | O3 Entity |
TOT/ToT | Time on Tools | Acronym |
TWLA | Three Week Look Ahead | Acronym |
TWP | Test Work Package | O3 Entity |
VWP | Vendor Work Package | O3 Entity |
WBS | Work Breakdown Structure | Acronym |
WFP | Work Face Planning / WorkFace Planner | Acronym |
Widget | This is a reference to the selectable and configurable dashboard components. A widget might be a type of chart, a video link (such as training) or a query tile as used to retrieve, for example, a count of IWPs, constraints, etc. | Term |
Work Orders | Work Orders are a means to manage project scope work against a WBS coding structure. Consider them like a package or activity type. |
|
Work Pack | Scope broken out into small packages of work that typically take 2-4 weeks to complete. Examples include EWP, CWP, IWP, PWP, TWP and TOP. | Term |
XWP | This is a non-specific reference to work packages (CWP, EWP, IWP, TWP, etc.). | Term |
Admin Terms
Terms used by System and Project Administrators in O3.
Entity (Table) | Description |
API Users | For application programming interface connection details. |
Project Teams | Similar to User Groups, except these are also used for Team Boards membership and if using Contracts to restrict access (such as for sub-contractors), these are assigned to the contract/s and all members of that Project Team will then have access to that contract’s data (see Roles for permissions). |
Roles | The Roles are used for permission and assignment purposes. For example, an ‘RFI Engineer’ role might only need to edit access to the RFI section and view access to other areas. A manager might only need view only access to all areas, so you could have a Role as ‘View Only’ for example. The Role/s are applied to the User accounts. |
Units | These are typically a sub-split of a Plant/Major Asset and therefore can be created and modified under the ‘Plants’ form layout. |
Users | User Accounts – Profile and Project Team memberships. Contact details and training records also shown (as applicable). |
User Groups | Like Project Teams, this is a means to group O3 users. Assignments can be sent to the group and thereby extension, all group members. This might also be useful where there is a back-to-back position, so it does not matter who is on shift. |
Project Usage Terms
Terms used in relation to O3 Projects.
Entity | Description |
Activity Stream | An activity stream is typically seen as a dashboard widget in O3 where you can view what activities have recently taken place and by whom. |
Annotation Types | When you make an annotation to a drawing (if configured with access from O3) you can categorize the type of annotation, such as Standard, No Constraint, Restricted, Constraint Restricted. |
Approval Types | Approval Types are used to define groups of related approvals. They need to be configured in the entity type that uses approvals (e.g., IWP) and before individual Approval items are established. Approval Types are also configurable to auto create approval items on the entity. For example, ‘Engineering’ for related approvals such as by discipline leads. |
Approvals | Approval items that are on an entity. An example is ‘Approved for Construction,’ or a specific engineering approval required such as a Piping Lead needs to sign something off. The approval item must have an approval type and should be assigned to someone to approve or reject that approval item. |
Areas | Areas are generally considered a subset of a CWA, but depend on organization requirements (i.e., the CWA might be part of an Area). Areas, like CWAs, normally represent an area of the project site with a specific purpose, like a utility or service. |
Associations | Associations are used to link one entity to another. For example, you may want to link a CWP to one or more documents, systems, or drawings. |
Associations - Full Update | A full Associations update will empty and replace the existing Associations data from a given source with the new Associations data from said source. |
Attachments | An attachment in O3 is similar to how you may attach a file to an email, except you typically use this to attach a file to a package such as an IWP or EWP. |
Bill Of Materials (BOM) - Full Update | A full BOM update will empty and replace the existing BOM data from a given source with the new BOM data from said source. |
Bill Of Materials (BOM) - Partial Update | A partial BOM update will keep the existing BOM data intact and will not remove any exiting entries but only add and modify existing ones. |
Checklist Configuration | Checklist configurations are configured from the CWP entity. On the CWP form layout, they will be shown as a sub grid option of Development Steps. They are a means to indicate items that need to be considered for the development of the package (such as applied to child IWPs). This might include paperwork in place of e.g. safety reports, equipment booked, scaffolding requested. This is generally a high-level tick box vs detailed constraint management. |
Component Task Backlog | These are Execution Tasks that will be performed for each construction component (CC) when applied to an IWP for execution, even if they do not have standardized rules for their creation. |
Component Backlog Task Step Import | This is an import type that allows you to bulk import/update Construction Task Backlog execution steps against Construction Components. You can set the step name, estimated hours, weight (5%. 25%...), tag number, total units and also to delete tasks. This is primarily used when tasks are not set to be automatically created from construction component data. |
Constraint Types | These need to be configured before Constraints. Example types include ‘Company Materials,’ ‘Drawings,’ ‘RFI,’ ‘Predecessor’. Like Approval types, Constraint Types are set-up and configured on each entity constraints are being used. So IWP constraint types could be different to TWP types. |
Constraints | These are individual constraints raised and require to be assigned against a ‘Constraint Type’. Here you can outline (or can be auto-generated such as for blocking predecessor) the issue that is or might inhibit the work package from being started or completed, for example. Constraints are normally assigned to an individual, team, or role to resolve the constraint. Hard constraints are those that block completion of the work package. Soft constraints do not block completion (such as an FYI requirement). Note these are not included in e.g., IWP Constraint grid totals. |
Construction Components (CC) | These are the individual parts of a model/structure such as a valve or pipe. |
Construction Equipment Requirements | This is where you can store what Construction Equipment you need. This is shown under IWP, Resources, Construction Equipment. Examples include Crane, Compressor, Welding Unit, etc. |
Construction Subcomponents | This allows you to breakdown the main components (if applicable), such as a Pipe Spool into Pipe, Fittings (elbows, tees, etc.). |
Construction Work Areas (CWA) | A CWA represents a geographic cube of logically associated work within a project. It includes all disciplines (such as civil, mechanical, electrical, etc.). |
Construction Work Packages (CWP) | These are (generally) a breakdown of a CWA into packages, which are further broken down into IWPs. If using EWPs then these typically aim to convert to CWPs for the construction phase. Under project settings, it’s possible to toggle on transferring scope from EWPs to CWPs. Consider using ‘CWP Releases’ if you want to release the CWP in parts so that construction can make a start. |
Construction Work Package Releases | Are used to track part release of CWP scope (from engineering to construction). For example, engineering might be able to release 50% (release 1) initially of the scope as this has been approved for Construction. |
Contracts | This is typically used to identify subcontractor scope. If you are restricting data access to subcontractors/contract parties, then you will need to establish the contracts and which project teams can access it (such as the contractor team and owner/managing contractor). Suggest making your contract-based entities have ‘Contract’ as a mandatory field. Navigate to Project Settings – general - RESTRICT DATA ACCESS BY CONTRACT AND PROJECT TEAM. |
Crews | You can create setting the name, foreman and size (number of people) of the crew, discipline, and crew category. |
Daily Reports | With Daily Reports, you can, as the name implies, capture reports on a daily basis! These reports can include: Work Journals: With Work Journals, you can track events that took place on the project and track Notices to Comply and Safety Notes. You can also track Events, Notices to Comply and Safety Notes at the Daily Journal level. Your Weather Reports and Work Journals can be linked to specific IWPs, so you can add context to your project's data. |
Data Deliverables | Data deliverables are a tool used to define a regular data exchange for data being brought into O3. Data deliverables can include configured field mappings, and track the imports provided and frequency of data input. |
Data Sources | Data Sources are used as a means to list and manage where you might be importing or integrating data with other systems or manually maintained (such as spreadsheet imports). For example, you might have a Data Source “MMS” (as your Material Management System). The data source can be used on other applicable entities with ‘Source’ field as a means to identify where the data came from. |
Delays | You can list any associated delays, typically against IWPs. See Delay Type. To access the Delays, you will need to switch the IWP Grid view to ‘Delays.’ |
Delay Types | The Delay Types are a means to group related Delays. For example, any delays associated with a type ‘Severe Rainfall,’ ‘Lightning,’ ‘Safety Incident.’ |
Deliverables | This is a list of documentation you intend to deliver as part of your work package. |
Design Work Packages (DWP) | DWPs are an O3-specific Entity. You can break EWPs down into DWPs to assign smaller chunks of scope to members of your design teams. DWPs will typically be used to manage the development of a few drawings. |
Development Step Types | This is a group of a Development Step. The Type can be configured to auto-create deliverables steps on packages. For example, ‘Initial Scope Identification,’ ‘Preliminary BOM / MTO Receipt and Incorporation.’ These can apply to CWPs, EWP, IWPs, TWPs and TOPs. In general terms, a list of major deliverables the package is expected to produce. |
Development Steps | This is a specific action involved in developing a work package. In some cases, you may only have one step/item per type, others you can breakdown further. |
Disciplines | Typically used to link an entity to the type of work, such as Piping, Structural, Instruments, Electrical, Mechanical, etc. |
Documents | Similar to drawings, this is a repository/register of documents. In general terms any document you would like to associate with and reference an O3 package/entity. For example, these might include Quality Assurance Documents, which may be part of your IWP inspection and close-out requirement procedure. |
Drawing Types | These are a means to group drawings. For example, ‘Detail,’ ‘For Information Only,’ etc. The types do not have to be created against the entity they are associated with. |
Drawings | This is a drawing register. It is possible to attach the actual drawing and examine and annotate it with the ‘Viewer.’ Drawings can also be linked to model data and assigned a Drawing Type. |
Engineering Work Packages (EWP) | EWPs are used by engineering teams to help develop CWPs. They will sit within a CWA and generally develop in line with the path of construction. You will likely include drawings, so consider uploading these (either manually, imported or API connected from your company drawing register repository). |
Entity Checklist Configuration | See Checklist Configuration. |
Entity Statuses | The Packages offer a status list, which typically indicates the package’s progress from initiation to close-out. Examples include ‘Approved for Construction’ and ‘Started Execution.’ |
Exports (Scheduled) | This refers to data leaving O3, as this might be used externally for analysis or data consumption by another system or platform. You can use scheduled exports to log time determined export schedules. Navigate to User Profile – Notification Settings – Scheduled Exports |
Imports | This refers to data being uploaded into O3. This might be data from another platform or as a means to bulk update a data grid with new values. In O3 you can see the list/log of historic imports into the platform. |
Installation Work Packages | In a Work Face Planning/Construction phase of AWP, the IWPs form the backbone key package types to drive completion of construction. Once the CWP is established, IWPs can be generated against it. IWPs can be generated by selecting components from 3D model and/or IWPs can be imported or created directly in O3. In some circumstances the IWPs represent scope that may not be on the model. For example, sometimes this is the case with Power lines, etc. IWPs should be coded against a ‘Purpose.’ Note: Material Requirements will not be consumed by packages that do not have a Purpose. |
Interface Agreements (Who/How) | Interface Management is used to coordinate between two stakeholder groups when they have common concern or interest near their boundaries of work. In O3 terms, the Interface Agreements sit under the Interface Point. This will indicate how the two groups agree to coordinate at the Interface Point. There can be multiple agreements related to the Interface Point. For example, Stakeholder A has agreed to install a shut-off valve on the boundary and Stakeholder B has agreed to connect pipe to the valve, going into its managed territory. |
Interface Points (Where) | Interface Management is used to coordinate between two stakeholder groups when they have common concern or interest near their boundaries of work. An Interface Point is where the overlap is taking place. This might be a pipe that will travel across the boundary and may need an isolation valve or a joint on the boundary. This can result in one or more Interface Agreements on who does what and how. |
Labor Work Packages | A means to package labor requirements for a CWA by discipline/purpose. |
Lookups | These are a means to keep data such as categories and types consistent by creating a standard list of values to use. Also avoids typos and variations of spellings and formats. Examples include ‘Document Type’ and ‘Project Phase.’ |
Manpower Requirements | This is tied to Resources and what manpower/labor resources a package requires. Examples might include a ‘Welder,’ ‘Electrician,’ ‘Plumber.’ |
Manpower Schedule Items | These are the Period Start and Finish, hours, headcount list under the ‘Manpower Schedules’ header record. |
Manpower Schedules | This is for creating a manpower header for the schedule, e.g., name, discipline, and description. The schedule specifics are noted under Manpower Schedule Items. |
Material Catalog | This is a list of materials required on the project and is typically built from the BOM extracted from the model. Can also be imported independently. |
Mechanical Equipment | This is used for listing key material equipment/tags to support construction. |
Model Groups | This allows you to group related standalone models into a group. |
Models | Standalone Model details might be a single NWD (Navis Works CAD) file. |
P6 Schedule Import | This is for importing Primavera P6 – XER schedule files into O3. |
Pipelines | This manages the pipe lengths and connected tags against a CWP. |
Plot Plans | In O3, these are typically 2D visuals of the project site (Inside Battery Limits) and applicable surrounding area that impacts or integrates with the project scope (Outside Battery Limits). In lieu of a basic engineering site layout, you could use a map scan of the construction/site area and overlay and build your initial Construction Work Areas to determine your Path of Construction (POC). In O3 you can have multiple plot plans (including sub plot plans to break out detail) per project. |
Procurement Work Packages (PWP) | PWPs are procurement deliverables that contain all the materials required to satisfy a single CWP. They can be tied to related Purchase Orders. |
Project Team Members | This is used to manage which user accounts are members of which Project Team. Project Teams are configured by system admins. |
Punchlist Items | Punchlist Items are normally inspection defects picked up on site walk downs with asset client/owner and typically inhibit a hand over until the punch item is cleared. For example, Cat A, B and C are normally used to state what stage the punch needs to be resolved by. This may require, for example, tracking the re-ordering of replacement equipment to replace a damaged part and the swap-out effort. These can be created independently or tied to IWPs, TWPs, Systems, and TOPs. |
Purchase Order Line Items | These are the material/service (line) items of the Purchase Order and will include quantity required. |
Purchase Order Types | A means to group the Purchase Orders. |
Purchase Orders (PO) | This entity allows you to manage (upload from your material management system) your project related purchase orders. This can be incorporated with your PWPs. |
Requisitions | These are precursors to the contractual Purchase Orders. It’s a means to track enquiries and bids from the selected list of Vendors who can fulfill the Purchase Order. |
Report Templates | Report Templates can be found under Project Settings where you can upload your Word based reports for generating ‘Detail’ reports within O3. Typically against your O3 package entities, such as an EWP or IWP cover sheet where you want to report out the details, model shot, attachments, approvals and constraints, or RFIs, etc. |
Request for Information (RFIs) | This means that technical requests can be tracked. Examples include requesting data from engineering and site enquiries . |
Risks | This is where projects can manage a risk log within O3. Risk examples include Supply Chain, Environment, Resourcing, Labor, etc. |
Safety Observation | Part of the ‘ONSafe’ Mobile Safety Tracking. They can be inputted directly into to O3. These are related to diagnose of safety trends on a project. |
Safety Observation Items | These are individual observations of an overall ‘Safety Observation’ group. |
Safety Observation Types | Part of the ‘ONSafe’ Mobile Safety Tracking. The types are connected with ‘Safety Observation Items’ and as means to group the items. Examples include ‘Eyes,’ ‘Manual Lifting,’ ‘Pinch Point,’ ’Confined Space,’ ’Temperature,’ etc. |
Scaffold Requests | This is an individual scaffolding request. This can be created by a workface planner, for example, and later grouped by the Scaffolding contractor/s into a package. These are a type of Action within O3. |
Scaffolding | Scaffolding (Project Information) is a track of scaffolding equipment (Tags). |
Scaffolding Work Packages (SWP) | This is used to bundle related scaffolding requests into a package of work to hand over to scaffolding crews. For example, there may be two requests in the same area and timeframe/on same/CWP/IWP. This is mainly for the scaffolding contractor to manage. |
Schedule | This acts as a header record and pertains to a whole schedule imported (P6/XER or CSV). Below this are the individual schedule activities. Field mappings can be applied here. |
Schedule Activity | Schedule activities are the individual tasks on a schedule, or they could be milestone based. They will sit under a parent ‘Schedule’ record. |
Schedule Activity Associations | This allows you to associate a Schedule Activity with another O3 entity, such as CWP. |
Systems | On many projects, once construction has matured, the project moves to a System/Sub System (e.g., potable water, nitrogen lines, power generation etc.) completion phase. System completions are generally post-construction (although systems will be outlined/drawn up during engineering phase) and relate to pre-commissioning and commissioning activities as well as turn/handover steps. |
Tasks | Not to be confused with Execution Tasks. This is a list of Actions/tasks typically connected with a team board. Also see Tools – Task List. |
Team Boards | A team board in O3 is basically a hub (all in one place) location where you can list your tasks/actions that relate to your project team (or can established for individual or made public wide use). |
Team Goals | You can define a list of goals within Project Settings – Team Goals. Examples like Establish a Work Package Template, ensure your AWP program works, establish a new risk management process, standardize your weekly engineering meetings. |
Test Work Packages (TWP) | TWPs are packages for managing testing events (hydro testing on pipe as a common example) and are mainly used for (but not restricted to) pre-commissioning phase of project and are normally coded against a CWA and System / Sub system. Punch List Items can also be generated at this point (if shown on your form layout). Like IWPs, constraints and approvals can also be applied as well as the linking of related drawings, documents, etc. |
Tool Requirements | This is tied to Resources, such as what tools (hammers, grinders, etc.) are required for the installation work. |
Tool Time Observation Type | This is defined under system admin and will generally be Non-Tool Time (e.g. nonproductive such as training, safety talks, breaks, etc.) vs Tool Time (actual time on tools, such as installing something or welding, operating equipment, etc.). |
Tool Time Observation Types Import | Tool Time: Mobile App module – Observation Types Import. |
Tool Time Observations | Tool Time: Mobile App module – Observations recorded (list) against a Reading. |
Tool Time Readings | Tool Time: Mobile App module – The Reading is a header entry – dates, people observed, etc. |
Turnover Work Packages (TOP) | This is a means to account for final inspection (walk downs) and handover of parts of/whole system/sub system to the customer’s or owner’s satisfaction. Punch List Items can also be generated at this point. TOPs like TWPS are normally coded against a CWA and System/Sub system. Like IWPs, constraints and approvals can also be applied as well as the linking of related drawings, documents, etc. |
User Certifications | These are related to O3 training functionality. |
Users | O3 Account users. |
Vendor Data | This will be items such as Data Sheets and Drawings that engineers may use to assist with Requisition and Purchase Orders or to assist with technical queries. |
Vendor Work Packages | This is managing external vendor work/service, such as coating, security, catering/welfare, and testing services, which support the project. |
Vendors | This is a list of Vendors as used in connection with Vendor Data. |
Work Breakdown Structures (WBS) | This entity allows you to store your WBS structure. An example might be ‘1.12.5 Data Centre.’ |
Work Centers | This field is used when entering tool time observations. A user will denote a work center, and O3 will send an alert if the time conducting the observations is outside of the work center (location). |
Work Orders | Work Orders are a means to manage project scope work against a WBS coding structure. Consider them as a package or activity type. |
Work Package Components | This is a relationship table that links an entity such as an IWP to a Construction Component (and child/subcomponents (optional). |
Work Package Types | Consider these O3 Entities in that they refer to the type of data package, be it an EWP, CWP, IWP or user defined type, for example. |
EXECUTION TASKS | Hierarchy: Task Type Component Filters |
Work Package Execution Task Steps | Implemented, the steps progress towards Execution Type completion on the work package. |
Work Package Execution | Definition of component filters added to the Task Type. |
Work Package Execution | Defined as: A specific sequence of actions or sub-activities that are part of a larger execution task. These steps break down the task into manageable units that guide how the work is to be performed in the field.
Rebar Installation:
|
Work Package Execution | Defining which entity task types relates (see e.g., IWP settings – Execution Task Type), a name, available purpose, component type and rate of placements and unit of measure. Progress measurement/rates of placement.
Execution Task Type examples:
|
Work Package Execution | Implemented, Execution Task Types added to the Work Package. |
Work Package Material Requirement | These are Material Catalog items that the package (e.g., IWP) requires. |
Work Package Purposes | This is a list of purposes. These are typically created against the CWP and IWP entities (see entity settings). |
Work Package Stages | A means to group work package by stages. Examples include 30 days out, 60 days out, 90 days out or more. For example, you may wish to extract all those IWPs that are at a particular stage. |
User Defined Data | Within O3 you can now create your own entity types, which are called User Defined Types. These need to be configured at the system level by an O3 system administrator. See System – Systems Admin – User Defined Types. Once set up, they are then configured at the project level (if using) as you would any other O3 entities like RFIs. For example, you might want a type to manage NCRs or Change Management, such as design or field changes. |
