📘 Technical System Tracking Guide
Purpose: To help users understand how technical systems and components are structured, identified, and used across project phases.
🧭 Introduction
In construction and building operations, managing technical systems—like lighting, ventilation, or fire protection—is critical. This guide explains how we organize and track these systems using a structured identification method that supports planning, execution, testing, and maintenance.
🔄 Project Phases Overview
We divide our work into two key phases:
1. Pre-Execution Phase
-
Define system types (e.g., Lighting System)
-
Assign serial numbers to each system type
-
Specify component types and type numbers
-
Plan floor-level placement
2. Execution Phase
-
Install components into systems
-
Assign component numbers to each physical item
-
Confirm exact location (floor, room, etc.)
-
Perform testing and verification
🏗️ Understanding System Types
A System Type is a category of technical functionality in the building. Examples include:
|
System Type |
Description |
Serial Number Example |
|---|---|---|
|
Lighting System |
Controls all lighting infrastructure |
01 |
|
Ventilation System |
Manages airflow and air quality |
02 |
Each system type is assigned a Serial Number to uniquely identify it across the project.
🔩 Components and Identification
Each system type uses Components—physical items like light bulbs, sensors, or valves. Components are tracked using three identifiers:
|
Identifier |
Purpose |
Example |
|---|---|---|
|
Component Type |
General category of item |
Light Bulb |
|
Type Number |
Differentiates between variations |
003 |
|
Component Number |
Unique ID for each installed component |
00002076 |
🔍 Example:
Let’s say you’re working on the Lighting System on the 3rd floor. You might see:
-
System Type: Lighting System
-
Serial Number: 01
-
Component Type: Light Bulb
-
Type Number: 003
-
Component Number: 00002076
-
Floor Location: Floor 3
This tells you exactly what item is installed, where it is, and what system it belongs to.
🗂️ Floor-Level Mapping
Each system is mapped to a Floor Location. This helps you:
-
Know where each system is installed
-
Track which components are on which floor
-
Simplify testing and maintenance
🧾 Example Breakdown
Let’s say you’re working on a building with five floors. You’re installing lighting systems on each floor. Here’s how the mapping might look:
|
Floor |
System Type |
Serial No. |
Component Type |
Type No. |
Component No. |
|---|---|---|---|---|---|
|
2 |
Lighting System |
01 |
Light Bulb |
003 |
00002076 |
|
3 |
Lighting System |
01 |
Light Bulb |
003 |
00002075 |
✅ How to Use This in Practice
Step 1: Identify the System
Start by selecting the system type you're working on (e.g., Lighting System). Use the Serial Number to locate it in your documentation or software.
Step 2: Review Component Types
Check which Component Types are used in that system. For lighting, this might include bulbs, switches, or drivers.
Step 3: Match Type Numbers
Each component type has a Type Number to distinguish variations. For example, LED bulbs vs. halogen bulbs.
Step 4: Locate Component Numbers
During execution, each installed item gets a Component Number. This is your key for testing, checklisting, and troubleshooting.
Step 5: Verify Floor Location
Use the floor mapping to find where each system and component is physically located.
🧪 Testing & Checklists
Because every component has a unique number, you can:
-
Generate targeted checklists
-
Run system-specific tests
-
Track issues to exact items
-
Ensure compliance with environmental certifications (e.g., BREEAM, LEED)
🧠 Summary
This system gives you full traceability from design to delivery. You’ll know:
-
What system you’re working on
-
What components it uses
-
Where those components are installed
-
How to test and verify them