Governed knowledge
Published Concepts, ontologies, IFC schema references, mappings, controlled business rules and reusable Reference Use Cases. Administrator-governed and revision-aware.
Connect governed, version-pinned shared Concepts to real project data. Compose reference-driven Project Use Cases into an auditable Project IDM without mixing global semantic definitions with project-owned information.
Architecture specification · Baseline OpenSPAD 7.8.53 · 17 October 2026. Planned functions must not be mistaken for shipped functionality.
OpenSPAD distinguishes reusable published knowledge from the changing state of a single construction project. A project references global definitions; it does not copy them into ungoverned duplicates.
Published Concepts, ontologies, IFC schema references, mappings, controlled business rules and reusable Reference Use Cases. Administrator-governed and revision-aware.
Imported IFC model instances, Excel and JSON schedules, project ontologies, information requirements, constraints, mappings, users and project-specific decisions.
Project Use Cases, Project IDM and actor responsibilities, IDS specifications, BCF issues, validation runs and model-viewer feedback.
A Project Use Case expresses intent with explicit references to source models, semantic definitions, constraints and project participants. Composition creates an information-flow graph across several Use Cases.
| Element | Example relationship | Meaning |
|---|---|---|
| Project → Use Case | HAS_USE_CASE | Ownership and access scope of project intent |
| Project Use Case → Reference Use Case | DERIVED_FROM | Reusable template lineage, preserving source revision |
| Project Use Case → Concept revision | USES_CONCEPT_VERSION | Version-pinned semantic dependency |
| Project → Source model | HAS_SOURCE | IFC/Excel/JSON import revision and provenance |
| Use Case → Use Case | REQUIRES, PRECEDES | Dependency and execution ordering |
| Use Case → Use Case | PROVIDES_INFORMATION_TO | Information handover; not necessarily strict temporal precedence |
| Use Case → IDS/BCF | SPECIFIED_BY, HAS_ISSUE | Machine-readable requirement and issue linkage |
A reusable, administrator-governed information need such as “Verify required door accessibility properties.” It can be selected and adapted by authorized project roles according to policy.
A project-owned instance with selected Concept versions, actual sources, actor assignments and project constraints. It can belong to a multi-Use-Case Project IDM.
The BIM Manager leads semantic composition and project integration; the Standard User selects approved Reference Use Cases for inclusion in an IDM. Administrative publication of global Concepts is reserved for the Administrator.
Record project scope, owners, membership, required lifecycle phase and target deliverables.
Choose approved templates; keep stable links to the source versions.
Import IFC, Excel or project ontologies, and map their fragments into the Project Knowledge Graph.
Choose pinned published Concepts, adjust project-specific constraints and record intended responsibilities.
Review REQUIRES, PRECEDES, parallel execution and information handover; check contradictions and missing prerequisites.
Review the graph and provenance, check permissions, then record an auditable approval event.
Compose the Project IDM, BPMN actor flows and IDS requirements where supported by the specification.
Run appropriate model checks; link failures to IFC entities, BCF topics and viewer highlights.
Machine-readable applicability and requirements for IFC entities, attributes, properties or classifications where representable in IDS. Import and export must preserve semantic meaning and expose unsupported constraints explicitly.
The coordinated structure of multiple Use Cases, actors and information exchanges. It captures who needs which information, when and for what purpose.
Swimlanes describe participants, tasks, gateways and sequence flows. BPMN does not replace the Concept Graph or the Project IDM's semantic dependencies.
Issues contain status, responsibility, comments and IFC viewpoints or selected elements. Multiple BCF topics may relate to one Use Case or validation run; BCF is not a BPMN swimlane.
| Action | Administrator | BIM Manager | Standard User |
|---|---|---|---|
| Publish or modify shared Concepts / Reference Use Cases | Authorized governance | Propose change only | No |
| Import project IFC, Excel, ontology sources | Policy / system oversight | Responsible | Only if delegated |
| Create project-specific constraints and Use Cases | Governance oversight | Responsible | Compose approved references within granted scope |
| Build Project IDM from approved references | Oversight | Lead / validate | Yes, within permissions |
| Approve global Concept version upgrades | Publish / authorize | Review project impact | No |
| Assign BCF issues and review check results | According to authorization | Coordinate | Participate if assigned |
Matrix specifies the target role model. Fine-grained organization, project and resource authorization is a separate future implementation scope.
Project Use Cases pin Concept versions. When a new Concept revision is published, old dependencies remain valid references until a deliberate project migration and revalidation decision is recorded.
For example, new bSDD alignment enriches an existing published Concept.
List all referencing Project Use Cases, IDS outputs, checks and composed IDMs.
Inspect changed class bindings, property constraints, allowed relations and semantic meaning.
Create an explicit project revision, pin new Concept version and rerun impacted checks; retain historical snapshots.
Example: Project Use Case "Door accessibility"
reference_use_case_version: 2
concept_pins:
- concept: Door accessibility
version: 3
source_revisions:
- IFC model: coordination-model / revision 11
change_policy: explicit-review-and-revalidation
status: illustrative proposed data contract| Capability | Maturity | What is established |
|---|---|---|
| Neo4j-based Concept model and administration | Verified baseline | Existing deployed graph/data services and Concept audit documented in the 7.8.53 development context |
| Persisted Concept relation-rule pilot | Pilot | Heating Systems → Boilers allowed; Accessibility blocked; restricted rule coverage |
| Reference-to-project Use Case composition | Planned | Target workflow and authorization boundaries specified, not asserted as production-ready |
| IDS import/export and semantic alignment | Planned / partial work | Modules and prototypes exist in project history; complete standards roundtrip is not verified |
| Project IDM, BPMN orchestration and BCF linkage | Planned | Graph dependencies and human workflows specified |
| Complete validation engine, 3D overlays and impact reports | Planned | Target architecture, not a validated end-to-end delivery |
| Cross-tenant federated project queries | Future | Depends on federation, query and granular authorization infrastructure |