openSPAD / docs
Documentation 2.0 · Chapter 07 · Process & collaboration architecture

From connected Use Cases to coordinated information delivery.

Compose a project Information Delivery Manual, model its process choreography with BPMN 2.0, and manage model-related issues through BCF—without confusing requirements, process control, and issue exchange.

IDMBPMN 2.0BCFUse Case dependenciesIDS linkageGraph traceability

Design/specification draft 0.1 · 17 October 2026 · Baseline 7.8.53. Planned capabilities are not represented as deployed features.

01 / A clear separation of concerns

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.

Information delivery

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.

Process orchestration

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.

Issue coordination

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.

Architecture rule: BPMN swimlanes represent actors and process responsibilities. BCF topics are linked to process tasks and Use Cases as issue records; they are not BPMN swimlanes and do not replace an IDM.
02 / Composition architecture

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.

GLOBAL GOVERNANCE SCOPEPublished Concept vNReference Use CasesGovernance / ProvenancePROJECT KNOWLEDGE SCOPEProject Use Case AEnergy demand assessmentProject Use Case BHVAC coordinationProject Use Case CModel verificationProject IDMDependency / exchange graphBPMN processIDS requirementsBCF issue links

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.

03 / Worked example — illustrative

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.

UC-A
Energy demand
requires spaces & envelope
→
UC-B
HVAC coordination
consumes loads, adds systems
→
UC-C
Verification
checks model & constraints
→
Exchange
Approved result
plus open BCF issues
ILLUSTRATIVE SWIMLANE VIEW — conceptual, not serialized BPMN XMLArchitectMEP EngineerBIM ManagerModel CheckerProvide IFC modelspaces & envelopeCoordinate HVACsystems & exchangesApprove exchangeor request revisionCheck IDS / rulesrecord validation runsCoordinate projectrequirements & owners

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.

Semantics matter: In BPMN, lanes partition a process inside a pool. Sequence flows cannot cross pool boundaries; cross-participant collaboration is represented with message flows. This overview intentionally stays conceptual rather than claiming to be an executable BPMN model.
04 / Dependency semantics

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.

RelationshipMeaningExampleValidation consideration
REQUIRESA 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.
PRECEDESDefines a mandatory ordering constraint.Model coordination precedes final verification.Check directed ordering for cycles and conflicting constraints.
PROVIDES_INFORMATION_TODefines information delivery across Use Cases.Architectural model provides space data to HVAC coordination.Specify the deliverable, provider, receiver and acceptance contract.
PARALLEL_WITH proposedCaptures intentional concurrency where dependencies allow it.Quantity and energy analyses run in parallel.Must not override a mandatory prerequisite.
CONFLICTS_WITH proposedFlags mutually incompatible choices or requirements.Two incompatible classification strategies.Requires review or explicit resolution before publication.
Design rule: A valid dependency graph is not automatically a valid BPMN process. BPMN generation requires an explicit process mapping, event/gateway semantics, participant assignments and a validation pass before export.
05 / Issue handling

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.

Check
ValidationRun
evaluates requirement
→
Finding
Fail / warning
evidence & element IDs
→
BCF topic
Assign + viewpoint
comments & status
→
Recheck
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.

06 / Permissions & lifecycle

Who defines, composes and approves?

ActorAllowed project responsibility (target)Protected boundary
AdministratorGovern/publish global Concepts and Reference Use Cases, define allowed rule types and access policy.Published global versions are immutable; revisions require review.
BIM ManagerCompose and coordinate project Use Cases, assign actors, project requirements and verification responsibilities; propose global changes.Cannot directly rewrite published global Concepts.
Standard UserAssemble 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 participantExecute 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

Draft IDM
select version-pinned Use Cases
→
Design flow
roles, exchanges, dependencies
→
Review
constraints, process & completeness
→
Publish snapshot
preserve reproducible baseline
→
Execute & revise
BCF, validation, new revision
07 / Implementation maturity

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.

Verified 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.

Pilot

Concept rule evaluation

Selected ALLOWS_CHILD / EXCLUDES examples in a draft context; not a production-wide enforcement engine.

Planned

IDM process orchestration

Use Case dependency graph, role/task mapping, BPMN editor/export, IDS-acceptance linkage and BCF lifecycle integrations.

Future architecture

Federated authorization

Cross-server IDM references, tenant-aware delegated access, controlled selective sharing and distributed query execution.

Planned

Validation & viewer

Persist ValidationRun / Result provenance, select failed IFC elements and synchronize model viewpoints with BCF.

Planned

Version-safe migration

Impact reports and explicit Use Case/IDM upgrade steps when new global Concept versions are published.

08 / Acceptance criteria and open decisions

Before implementation, validate the contract.

Minimum acceptance tests

  1. Three project Use Cases bind to immutable Concept versions.
  2. REQUIRES, PRECEDES and information exchanges are stored and queryable.
  3. Cycles or impossible prerequisites are rejected or flagged before approval.
  4. BPMN task mapping identifies pool, lane, actor, event and message/sequence semantics.
  5. BCF issues reference a specific Use Case and validation finding, including a reproducible model viewpoint.
  6. New Concept revisions do not silently alter published Project IDM snapshots.

Decisions still required

  1. Authoritative IDM schema and export packaging.
  2. Which user roles may approve, waive or publish a project IDM?
  3. Are dependency edges scoped per IDM revision or reusable as templates?
  4. Which BCF standard/API version and interchange modes should be first?
  5. What is the minimum executable BPMN subset for the first pilot?
  6. When does an unresolved BCF topic block formal information acceptance?

Related: Concept Governance · Hierarchy Rules · Versioning · Data Sources · Project Knowledge.