Curate once. Reuse safely.
Global Concepts and Reference Use Cases form a governed shared knowledge layer. Project information uses stable published version references, with explicit approval for migration.
Version rule: published Concept versions are immutable. New revisions must undergo review, and existing Use Cases stay pinned until explicitly upgraded and revalidated.
Administrator mission
The Administrator curates shared semantic knowledge and governs its use across projects. This role controls publication of global Concepts, source registration, rules, and operational safeguards. A BIM Manager proposes project needs; a Standard User composes approved resources.
Access & responsibility
Administrator: review and publish global knowledge, authorize global data sources, administer business rules and inspect audit history. BIM Manager: assemble project-specific use cases, bring project data and request changes. Standard User: reuse published reference use cases and compose a project IDM; no global editing.
Create a global Concept
- Capture the intent, stable identifier and accountable owner.
- Select a semantic type, root eligibility and provenance.
- Choose relevant source ontologies and classes.
- Associate IFC property sets, properties, required values and optional alignment evidence.
- Propose graph rules such as ALLOWS_CHILD or EXCLUDES.
- Save a Draft; run structural, semantic and dependency checks.
- Submit for review; publish an immutable version only after approval.
Correct a published Concept
- Open an immutable published version.
- Create a new Draft revision rather than editing the published snapshot.
- Record a change reason and source evidence.
- Diff classes, properties, mappings and graph rules.
- Compute impacted Use Cases and other Concept references.
- Review and publish a new version.
- Offer projects an explicit migration with revalidation; never silently repoint their references.
Register a new data source
- Classify source scope: global vocabulary versus project-instance data.
- Register source URI, authority, access restrictions, version and refresh policy.
- Extract and normalize candidate graph fragments.
- Align candidates with existing Concepts, recording confidence and evidence.
- Review unmatched and conflicting terms.
- Propose amendments as new Concept drafts; approve only reviewed mappings.
- Re-run impact checks before exposing updated knowledge.
Graph business rules
Use explicit directed relationships and typed semantics. Examples: ALLOWS_CHILD establishes a permitted composition; EXCLUDES prevents a pairing; REQUIRES and PRECEDES describe dependencies. Root eligibility is separately governed. Enforce cycle checks for hierarchy-like relations, while preserving valid multiple-parent graph relationships.
Version review & impact
For every proposed publication, inspect changed attributes, source citations, changed graph edges, affected Use Cases, constraints, IDS definitions, and project-specific pins. Make the review decision explicit: approve, request changes or reject. Store reviewer identity, timestamp, rationale and source-version evidence.
Global vs project boundaries
Shared graph: published ontologies, classifications, reusable Concepts and Reference Use Cases. Project graph: IFC instance models, Excel/JSON instance records, project mappings, project use cases, project IDS/IDM and validation evidence. Link project nodes to pinned global versions without rewriting global definitions.
Operations & recovery
Verify service health, documentation routes and Neo4j instance before any disruptive operation. Back up database and configuration with integrity verification. Record a recovery procedure and perform a separate restore rehearsal. Preserve audit trails; do not reset credentials, stop Neo4j or alter live project data as part of documentation maintenance.
Federation & security
Long-term design: independently managed OpenSPAD servers expose authorized graph fragments through identity-aware and versioned interfaces. Provider-managed manufacturer product graphs may disclose selected public nodes while withholding private records. Authorization must govern traversal, derived results, caches, queries and exports.
Administrator acceptance checklist
Before publishing: confirm stable identity and type; source provenance; direct/derived mappings; relationship constraints; root eligibility; version diff; impacted references; approvals; audit entry; and rollback/recovery notes. If a check is inconclusive, keep the revision in Draft/Review.