Overview
The Construction Component module manages the definition, classification, and assignment of construction components (such as equipment, devices, or materials) within a project. The Component Usage module tracks where and how each component is used, supporting links to built spaces, functional systems, and technical systems. Both modules support advanced classification, multi-level identifiers, and integration with system functions.
Key Concepts
-
Construction Component: Represents a physical or logical component (e.g., device, equipment) with classification, description, and serial number.
-
Component Usage: Tracks the assignment and usage of components within built spaces, functional systems, and technical systems.
-
Classification: Multi-level classification based on external standards, supporting filtering, reporting, and unique identifiers.
-
System Function: Links components to system functions and component functions for traceability.
-
Integration: Components can be assigned to built spaces, functional systems, and technical systems, and their usage is tracked in detail.
Main Pages
1. Construction Components List
-
Purpose: View, filter, and manage all construction components in the project.
-
Key Fields:
-
Code: Unique identifier for the component.
-
Type: Indicates if the record is a type/template or an instance.
-
System Function / Component Function: Links to system and component functions.
-
Description/Translation: Component description and translation.
-
Serial No.: Serial number for the component.
-
Built Space / Functional System / Technical System Code: Where the component is used.
-
Classification Term Lookup: Classification system term.
-
Classification Identifiers: Multi-level and single-level identifiers for type, function, location, and element.
-
Level 1–4: Multi-level classification codes.
-
Definition / Examples: Additional classification details.
-
-
Actions:
-
Create Instances: Generate component instances from a type/template.
-
Assign Attributes: Batch-assign components to built spaces, functional systems, or technical systems.
-
2. Construction Components Card
-
Purpose: View and edit details of a single construction component.
-
Sections:
-
General: Main details, type, system function, and description.
-
Where Used: Shows built space, functional system, and technical system assignments.
-
Classification Group: Multi-level classification and details.
-
Classification Identifiers Group: Unique identifiers for reporting and traceability.
-
3. Component Usage List
-
Purpose: View, filter, and manage all component usage records.
-
Key Fields:
-
Code: Unique identifier for the usage record.
-
Parent Code: Code of the parent (built space, system, etc.).
-
Type: Usage type (Built Space, Technical System, Functional System, etc.).
-
System Function / Component Function: Links to system and component functions.
-
Component No.: Linked construction component.
-
Description / Translation: Usage description and translation.
-
Classification / Level 1–4: Classification details.
-
Include in Test: Indicates if the component is included in testing.
-
4. Component Usage Subforms
-
Purpose: Used as subpages to display and manage component usages related to a specific parent (built space, system, etc.).
-
Features:
-
Tree View: Visualizes the hierarchy of component usage.
-
Indentation: Shows the structure of system and component functions.
-
Auto-fill: Filters and parent codes are auto-filled based on context.
-
How to Use
Creating a Construction Component
-
Go to NOC Construction Components and select New.
-
Fill in the required fields: Type, System Function, Component Function, Description, Serial No., etc.
-
Use the Classification Term Lookup to select a classification term. The system will auto-fill classification levels and identifiers.
-
Assign the component to built spaces, functional systems, or technical systems as needed.
Creating Component Instances
-
Use the Create Instances action to generate multiple component instances from a type/template. Specify the number to create and the target built space, functional system, or technical system.
Assigning Attributes
-
Use the Assign Attributes action to batch-assign selected components to built spaces, functional systems, or technical systems using a filter page.
Managing Component Usage
-
Component usage records are created automatically when components are assigned to built spaces, systems, etc.
-
Use the Component Usage pages or subforms to view, edit, or remove usage records.
-
The tree view subform helps visualize the hierarchy and relationships.
Field Descriptions
|
Field |
Description |
|---|---|
|
Code |
Unique identifier for the component or usage |
|
Type |
Indicates if the record is a type/template or an instance |
|
System Function |
System function linked to the component |
|
Component Function Code |
Component function code |
|
Description / Translation |
Description and translation |
|
Serial No. |
Serial number for the component |
|
Built Space / Functional System / Technical System Code |
Where the component is used |
|
Classification Term Lookup |
Classification system term |
|
Level 1–4 |
Multi-level classification codes |
|
Classification Identifiers |
Unique IDs for type, function, location, and element |
|
Include in Test |
Indicates if the component is included in testing |
|
Indentation |
Visualizes hierarchy in tree view |
Actions & Integration
-
Create Instances: Quickly generate multiple component instances from a template.
-
Assign Attributes: Batch-assign components to built spaces, functional systems, or technical systems.
-
Component Usage: Track and manage where each component is used.
-
Tree View: Use the tree view subform for a visual overview of component usage hierarchy.
Tips
-
Use the Classification Term Lookup to ensure consistent classification and reporting.
-
Use the Assign Attributes action for efficient bulk assignment.
-
Use the Component Usage subforms to understand and manage component relationships.
Security & Permissions
-
Only users with appropriate permissions can create, edit, or assign construction components and usages.
-
Assignment fields are validated against related tables.
Troubleshooting
-
If you cannot see or edit a component or usage, check your permissions and assignment.
-
If classification fields are not auto-filled, ensure the correct term is selected and classification data is set up.
-
If usage records are missing, verify that components are properly assigned to built spaces or systems.