Three standards, three distinct jobs.
The project graph links requirements, actors, models and outcomes, while preserving each format’s purpose. An OpenSPAD IDM is an orchestrated specification—not a synonym for a BPMN diagram or a BCF issue collection.
IDM
Who must deliver which information, for what purpose, at which project milestone, and with what acceptance criteria?
Aggregates reference/project Use Cases, exchange requirements, responsibilities and dependencies.
BPMN 2.0
Who performs which task, in what sequence, with which gateways, pools, lanes and message exchanges?
Represents the workflow; use formally correct BPMN elements in the implementable editor/export.
BCF
Which model-related issue needs attention, who owns it, what is its status and what IFC viewpoint supplies context?
Topics, comments, status, assigned users and viewpoints linked to model objects.
The Project IDM lives in the property graph.
A composed IDM holds references to version-pinned Project Use Cases and expresses their interactions explicitly. Published global Concepts and Reference Use Cases remain separately governed.
Logical architecture, not an assertion that IDM, BPMN or BCF generation is currently implemented. Concept-version pinning, provenance and authorization are design invariants.
Stable references
Project Use Cases must refer to explicit, published Concept versions. New Concept revisions do not silently rewrite already approved project deliveries.
Link, do not conflate
IDS captures machine-checkable information requirements where expressible; BPMN captures tasks and message flows; BCF captures the issue lifecycle for individual findings.
One building project, three coordinated Use Cases.
A BIM Manager assembles an energy assessment, HVAC coordination and compliance verification. The scenario is an illustrative design example, not a claim that a complete project IDM editor already exists.
Energy demand
requires spaces & envelope
HVAC coordination
consumes loads, adds systems
Verification
checks model & constraints
Approved result
plus open BCF issues
The diagram communicates the intended actors and handoffs. True BPMN 2.0 process definitions must distinguish sequence flow inside a pool from message flow between pools, and must preserve valid gateways and events.
Explicit, typed Use Case relationships.
Every dependency must have a defined subject, target, direction, scope and version. A graph visualization alone does not establish process execution order.
| Relationship | Meaning | Example | Validation consideration |
|---|---|---|---|
REQUIRES | A Use Case depends on an input or precondition from another Use Case. | HVAC coordination requires an energy assessment. | Required dependency must be satisfied before the dependent deliverable is approved. |
PRECEDES | Defines a mandatory ordering constraint. | Model coordination precedes final verification. | Check directed ordering for cycles and conflicting constraints. |
PROVIDES_INFORMATION_TO | Defines information delivery across Use Cases. | Architectural model provides space data to HVAC coordination. | Specify the deliverable, provider, receiver and acceptance contract. |
PARALLEL_WITH proposed | Captures intentional concurrency where dependencies allow it. | Quantity and energy analyses run in parallel. | Must not override a mandatory prerequisite. |
CONFLICTS_WITH proposed | Flags mutually incompatible choices or requirements. | Two incompatible classification strategies. | Requires review or explicit resolution before publication. |
BCF closes the collaboration loop.
A validation finding can trigger a model-related BCF topic. Topic status, assignee and viewpoints are collaborative metadata, and the issue can be traced back to the validation result, Use Case and relevant IFC elements.
ValidationRun
evaluates requirement
Fail / warning
evidence & element IDs
Assign + viewpoint
comments & status
New ValidationRun
close only when resolved
Traceability
BCFTopic → ValidationResult → Requirement → Project Use Case, with explicit IFC element identifiers.
Open issues
A milestone can be conditionally accepted, blocked, or explicitly waived according to project policy. No silent pass.
Round-trip goal
Support interoperable BCF topic exchange and map external updates to stable project issue identities.
Who defines, composes and approves?
| Actor | Allowed project responsibility (target) | Protected boundary |
|---|---|---|
| Administrator | Govern/publish global Concepts and Reference Use Cases, define allowed rule types and access policy. | Published global versions are immutable; revisions require review. |
| BIM Manager | Compose and coordinate project Use Cases, assign actors, project requirements and verification responsibilities; propose global changes. | Cannot directly rewrite published global Concepts. |
| Standard User | Assemble existing reference Use Cases into the project IDM within granted project rights. | Cannot create or publish global Concepts or Reference Use Cases. |
| Model Checker / external participant | Execute authorized checks, provide model submissions and work assigned BCF topics as granted. | Access controlled by project/org/resource scope; granular policy is future architecture. |
Proposed orchestration lifecycle
select version-pinned Use Cases
roles, exchanges, dependencies
constraints, process & completeness
preserve reproducible baseline
BCF, validation, new revision
Architecture specification is not current product capability.
This chapter describes agreed design direction, dependencies, and future functionality. Each claim below is constrained by the known OpenSPAD 7.8.53 baseline.
Persisted pilot foundation
Neo4j-backed Concept Graph pilot and selected rule reading were tested around 7.8.53. This does not verify an implemented IDM engine.
Concept rule evaluation
Selected ALLOWS_CHILD / EXCLUDES examples in a draft context; not a production-wide enforcement engine.
IDM process orchestration
Use Case dependency graph, role/task mapping, BPMN editor/export, IDS-acceptance linkage and BCF lifecycle integrations.
Federated authorization
Cross-server IDM references, tenant-aware delegated access, controlled selective sharing and distributed query execution.
Validation & viewer
Persist ValidationRun / Result provenance, select failed IFC elements and synchronize model viewpoints with BCF.
Version-safe migration
Impact reports and explicit Use Case/IDM upgrade steps when new global Concept versions are published.
Before implementation, validate the contract.
Minimum acceptance tests
- Three project Use Cases bind to immutable Concept versions.
REQUIRES,PRECEDESand information exchanges are stored and queryable.- Cycles or impossible prerequisites are rejected or flagged before approval.
- BPMN task mapping identifies pool, lane, actor, event and message/sequence semantics.
- BCF issues reference a specific Use Case and validation finding, including a reproducible model viewpoint.
- New Concept revisions do not silently alter published Project IDM snapshots.
Decisions still required
- Authoritative IDM schema and export packaging.
- Which user roles may approve, waive or publish a project IDM?
- Are dependency edges scoped per IDM revision or reusable as templates?
- Which BCF standard/API version and interchange modes should be first?
- What is the minimum executable BPMN subset for the first pilot?
- When does an unresolved BCF topic block formal information acceptance?
Related: Concept Governance · Hierarchy Rules · Versioning · Data Sources · Project Knowledge.