Integrated Systems & Equipment List (ISEL)
Define a hierarchical, machine‑readable breakdown of a project from system level down to parts, serving as the canonical source for BOMs, WBS, logistics, maintenance, and MakeAltQ/biz117 opportunity mapping.
Primary structural artifact for:
System architecture: systems, subsystems, assemblies, equipment, parts
BOM projection: manufacturing and procurement views
WBS projection: task and responsibility views
Logistics: spares, provisioning, support equipment
MakeAltQ/biz117: HS‑code mapping and capability analysis
Configuration management: controlled revisions and traceability
Created once per project; updated whenever:
new systems/parts are added
equipment changes
capabilities change
BOM/WBS/logistics views need refresh
ils01 Configuration Management List
ils02 Work Breakdown Structure (WBS)
biz102 Capability Statement
biz103 Quotation Workflow
biz117 Case Study Framework
HRI SIG:ILS Data Dictionary (terms, units, statuses, item types)
Systems Engineering: overall hierarchy and relationships
Engineering / Design: technical item definitions
Logistics / Supportability: provisioning and spares views
Manufacturing / Operations: BOM and process views
Business / MakeAltQ: HS‑code and capability mapping
Project Systems Engineer or Configuration Manager.
Moderate initially; low for incremental updates.
Effort scales with project complexity and integration depth (BOM, WBS, logistics, biz117).
Incomplete hierarchy → broken BOM/WBS/logistics views
Outdated item definitions → wrong provisioning or quoting
Missing HS codes → weak MakeAltQ analysis
Uncontrolled revisions → conflicting versions in downstream systems
Ambiguous units or terms → calculation errors
Each ISEL entry (system, subsystem, assembly, equipment, part) includes:
10.1 Tag Number:
Unique identifier for the item.
10.2 Item Name:
Human‑readable name.
10.3 Parent Tag Number:
Links item into the hierarchy (system → subsystem → assembly → equipment → part).
10.4 Item Type:
System / Subsystem / Assembly / Equipment / Part (dictionary‑linked).
10.5 Data Sheet URL:
Link to technical or commercial data sheet (internal or external).
10.6 Status:
Active / Deprecated / Prototype / On‑Hold / TBD (dictionary‑linked).
10.7 Revision Number:
Controlled version identifier.
10.8 Revision Date:
Date of last change.
10.9 Material / Specification:
Material or spec (e.g., steel grade, electronic spec, software version).
10.10 Units:
Primary units relevant to the item (mm, kg, N, psi, volts, amps, etc.).
10.11 Tolerances / Constraints:
Dimensional, environmental, electrical, thermal, or other constraints.
10.12 Supplier / Source:
Internal, external, TBD, or specific supplier name.
10.13 HS Code (optional):
For trade data and MakeAltQ/biz117 integration.
10.14 Capability Flags:
Manufacturable / Purchasable / Outsourced / Critical / Optional.
10.15 Notes / Comments:
Free‑form human notes.
Canonical machine‑readable schema for each ISEL item, enabling:
BOM/WBS auto‑generation
MakeAltQ/biz117 integration
unit‑safe calculations
dictionary validation
downstream tool interoperability
Example (XML):
xml
<Item>
<Tag>ils03-001</Tag>
<Name>Motor Assembly</Name>
<Parent>ils03-000</Parent>
<Type>Assembly</Type>
<DataSheetURL>/docs/motor.pdf</DataSheetURL>
<Status>Active</Status>
<Revision>3</Revision>
<RevisionDate>2026-08-15</RevisionDate>
<Material>Aluminum</Material>
<Units>mm</Units>
<Tolerance>±0.05</Tolerance>
<Supplier>XYZco</Supplier>
<HSCode>8501.10</HSCode>
<Capability>Manufacturable</Capability>
<Notes>Updated mounting holes.</Notes>
</Item>
Example (JSON):
json
{
"tag": "ils03-001",
"name": "Motor Assembly",
"parent": "ils03-000",
"type": "Assembly",
"dataSheetURL": "/docs/motor.pdf",
"status": "Active",
"revision": "3",
"revisionDate": "2026-08-15",
"material": "Aluminum",
"units": "mm",
"tolerance": "±0.05",
"supplier": "XYZco",
"hsCode": "8501.10",
"capability": "Manufacturable",
"notes": "Updated mounting holes."
}
Storage:
/sig/ils/ils03/ for master ISEL; projections under /bom/, /wbs/, /log/, /biz117/.
Version Control:
Managed via ils01; each ISEL revision logged and approved.
Access:
Read‑only for most users; edit rights restricted to systems/configuration roles.
Export:
XML/JSON exports for MakeAltQ, analytics, and external tools.
Initialize ISEL:
Define top‑level systems and major subsystems.
Populate Hierarchy:
Add assemblies, equipment, and parts with parent relationships.
Fill Item Fields:
Complete section 10 fields for each item (material, units, HS code, etc.).
Validate Against Dictionary:
Check item types, statuses, units, and terms against SIG:ILS dictionary.
Generate Projections:
BOM view
WBS view
logistics/provisioning view
MakeAltQ/biz117 opportunity view
Review & Approve:
Systems engineering and configuration management sign‑off.
Maintain & Update:
Apply changes via controlled revisions; regenerate projections as needed.
How to build an ISEL from scratch
How to use ISEL to generate BOM and WBS views
How to link ISEL items to HS codes for biz117
How to keep units and terms dictionary‑consistent for automated calculations