◈ OpenSPAD · Documentation 2.0
Chapter 06 · Information delivery architecture

Project Knowledge Graph
& Use Case Composition

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.

Global ↔ ProjectReference Use CasesVersion PinningIDSIDM · BPMNBCF

Architecture specification · Baseline OpenSPAD 7.8.53 · 17 October 2026. Planned functions must not be mistaken for shipped functionality.

01 · Knowledge boundaries02 · Graph model03 · Composition workflow04 · IDS / IDM / BCF05 · Roles06 · Change control07 · Delivery maturity

Shared semantics are not project data.

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.

Shared / Global

Governed knowledge

Published Concepts, ontologies, IFC schema references, mappings, controlled business rules and reusable Reference Use Cases. Administrator-governed and revision-aware.

Project / Scoped

Project Knowledge Graph

Imported IFC model instances, Excel and JSON schedules, project ontologies, information requirements, constraints, mappings, users and project-specific decisions.

Delivery / Versioned

Information deliverables

Project Use Cases, Project IDM and actor responsibilities, IDS specifications, BCF issues, validation runs and model-viewer feedback.

Key distinction: An IFC model is a project data source, not automatically an OWL ontology. Both can be transformed into graph fragments, but their identity, provenance and governance scope remain explicit.
GLOBAL KNOWLEDGEPublished Concept v3Immutable semantic revisionReference Use CaseReusable, governed templateOntology / IFC schemaExternal identities preserved PROJECT GRAPHProject Use CasePins Concept v3 & referencesIFC model / ExcelInstance data, Psets, provenanceConstraints & alignmentsProject-scoped requirements DELIVERABLESProject IDM + BPMNActors & information exchangesIDS RequirementsMachine-readable constraintsBCF / Validation / ViewerIssues, results, model contextpins v3composesExplicit provenance · Independent lifecycle · No silent upgrade of pinned Concept versionsTarget logical model; not a statement that all exchange and validation paths exist in production
Design diagram: global definitions, project-owned graph fragments and generated outputs remain independently governed.

Use Cases are graph-native, not just documents.

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.

ElementExample relationshipMeaning
Project → Use CaseHAS_USE_CASEOwnership and access scope of project intent
Project Use Case → Reference Use CaseDERIVED_FROMReusable template lineage, preserving source revision
Project Use Case → Concept revisionUSES_CONCEPT_VERSIONVersion-pinned semantic dependency
Project → Source modelHAS_SOURCEIFC/Excel/JSON import revision and provenance
Use Case → Use CaseREQUIRES, PRECEDESDependency and execution ordering
Use Case → Use CasePROVIDES_INFORMATION_TOInformation handover; not necessarily strict temporal precedence
Use Case → IDS/BCFSPECIFIED_BY, HAS_ISSUEMachine-readable requirement and issue linkage
Schema notation: The relationships above are a proposed canonical contract for the target architecture, not evidence that all labels and edges are currently present in Neo4j. API and schema changes require dedicated implementation and migration.

Reference Use Case

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.

Project Use Case

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.

From reference intent to a coordinated 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.

  1. Create or select project

    Record project scope, owners, membership, required lifecycle phase and target deliverables.

  2. Select Reference Use Cases

    Choose approved templates; keep stable links to the source versions.

  3. Bind project data

    Import IFC, Excel or project ontologies, and map their fragments into the Project Knowledge Graph.

  4. Compose Project Use Cases

    Choose pinned published Concepts, adjust project-specific constraints and record intended responsibilities.

  5. Resolve dependencies

    Review REQUIRES, PRECEDES, parallel execution and information handover; check contradictions and missing prerequisites.

  6. Human review and confirmation

    Review the graph and provenance, check permissions, then record an auditable approval event.

  7. Prepare information delivery

    Compose the Project IDM, BPMN actor flows and IDS requirements where supported by the specification.

  8. Validate and track issues

    Run appropriate model checks; link failures to IFC entities, BCF topics and viewer highlights.

UC-ADefine Door DataSource / criteriaUC-BAccessibility CheckUC-CDoor Asset CheckUC-DCoordinate HandoverPRECEDESPRECEDESPROVIDESPROVIDESIllustrative target composition — parallel branches do not imply a forced sequential process
Use Case dependency example. Edges describe information transfer and ordering; actor swimlanes are introduced separately in BPMN.

IDS, IDM, BPMN and BCF serve different purposes.

IDS · Exchange requirements

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.

IDM · Project information delivery

The coordinated structure of multiple Use Cases, actors and information exchanges. It captures who needs which information, when and for what purpose.

BPMN · Process representation

Swimlanes describe participants, tasks, gateways and sequence flows. BPMN does not replace the Concept Graph or the Project IDM's semantic dependencies.

BCF · Issue collaboration

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.

Validation linkage: A model check should retain its IDS specification revision, IFC model revision, Concept pins, timestamp and results. A 3D viewer can highlight affected IFC entities by stable identifiers such as GlobalId, with BCF issue overlays where available.

Clear boundaries between users and governance.

ActionAdministratorBIM ManagerStandard User
Publish or modify shared Concepts / Reference Use CasesAuthorized governancePropose change onlyNo
Import project IFC, Excel, ontology sourcesPolicy / system oversightResponsibleOnly if delegated
Create project-specific constraints and Use CasesGovernance oversightResponsibleCompose approved references within granted scope
Build Project IDM from approved referencesOversightLead / validateYes, within permissions
Approve global Concept version upgradesPublish / authorizeReview project impactNo
Assign BCF issues and review check resultsAccording to authorizationCoordinateParticipate if assigned

Matrix specifies the target role model. Fine-grained organization, project and resource authorization is a separate future implementation scope.

No silent Concept upgrades.

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.

  1. Detect candidate revision

    For example, new bSDD alignment enriches an existing published Concept.

  2. Calculate impact

    List all referencing Project Use Cases, IDS outputs, checks and composed IDMs.

  3. Review proposed differences

    Inspect changed class bindings, property constraints, allowed relations and semantic meaning.

  4. Authorize upgrade

    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

Specification is not implementation.

CapabilityMaturityWhat is established
Neo4j-based Concept model and administrationVerified baselineExisting deployed graph/data services and Concept audit documented in the 7.8.53 development context
Persisted Concept relation-rule pilotPilotHeating Systems → Boilers allowed; Accessibility blocked; restricted rule coverage
Reference-to-project Use Case compositionPlannedTarget workflow and authorization boundaries specified, not asserted as production-ready
IDS import/export and semantic alignmentPlanned / partial workModules and prototypes exist in project history; complete standards roundtrip is not verified
Project IDM, BPMN orchestration and BCF linkagePlannedGraph dependencies and human workflows specified
Complete validation engine, 3D overlays and impact reportsPlannedTarget architecture, not a validated end-to-end delivery
Cross-tenant federated project queriesFutureDepends on federation, query and granular authorization infrastructure
Architectural decision: The Concept Graph is a flexible directed property graph. Hierarchy is a rule-governed view. Use Cases pin immutable published Concept revisions; a change cannot silently propagate across project boundaries.