Semantic project planning

Work and evidence

Original catalogue identifiers are retained.

Earlier investigations

Distinct earlier cases and constructions keep their existing routes.

Scenario

Tunnel section connecting two shores beneath the Solway
Toy scenario

Imagine delivering a tunnel beneath the Solway.

A finished tunnel needs more than permanent lining: excavation, temporary access and support, installed systems, inspections and evidence all play different roles. Smaller installation examples let us test those distinctions without pretending to engineer the whole tunnel.

Can a description of the desired result explain the work needed to achieve it?

Back to the foray

Purpose

Semantic project planning

From an outcome
to the work it needs.

A tunnel fit-out needs installed equipment, temporary access and acceptance evidence. Can we explain the work a goal requires by distinguishing products, processes, temporary means and evidence?

Semantic project planning · A tunnel beneath the Solway

What does this project link say? is a small reading exercise: follow the different links around a fan, its planned installation and an intended inspection record. Inspect each statement’s name, direction and Turtle source.

The broader tunnel ontology remains available for exploration. The app collection includes separate investigations of temporal relations, local-to-global construction and ontology auditing.

The early ontology essai retains separately labelled Tokyo and HS2 project models. Model checks establish results within declared assumptions; they do not establish an engineered tunnel design, empirical verification of those models or practitioner validation.

Original question. Multilayer project ontology records the early question about connecting different project descriptions. The maintained Solway examples separate vocabulary, declared requirements and required work; the original post is a history of the enquiry, not validation of a tunnel design.

Reading routes and the full catalogue

Try the distinctions

The handover game

Choose the work needed to deliver an accepted installation. Discover why a finished product alone does not reveal all the work.

Play the game →
The handover game showing the shared gantry and two units awaiting installation
An example game state. Your choices change the work and its outcome.

Inspect the construction

The work that must exist

Start with Deliver both units, then untick Unit B in the brief. Which temporary work still serves unit A?

Change scope, access or methods. Follow shared work and causal support, try two work breakdowns, and compare ontology with executable PDDL.

The work that must exist showing the gantry route and an explanation of replaceable setup work
An example essay state. Change the brief to inspect its current result.
Digital Construction module map showing ontology modules and the relationships between them
The retained DiCon map; Tokyo stadium and HS2 cases are inside.

Early essai · Inspect the vocabulary

What can an ontology say about a project?

Explore Digital Construction terms, a Tokyo stadium model and an HS2 roles snapshot. Ask what else is needed before a project description can explain required work.

Open the early essai →

Back to the foray