Organization-Specific Facility Model
Bringing a real site onto the reference model is mostly a vocabulary problem, not a drawing one. The hard part is not what corresponds — it is what does not, and saying so instead of guessing.
Every gap here stays a gap. Two of the 8 object types have no counterpart at all — a site’s project milestones are schedule events rather than decisions with named participants, and its applicability decisions live in meeting minutes with nothing addressable to point at — so they are recorded as unmapped rather than forced into a shape that would misrepresent the site. 2 conflicts between the customer’s own documents remain open, with both values visible, because SPEQ does not arbitrate between two of a customer’s sources. A file that arrived as a document rather than data shows an em dash in every count, never a zero. And 340 assets carry an unconfirmed location rather than a defaulted one. The site, its files and every figure are fictional; SPEQ is never the system of record for a customer’s facility data — the model points at their systems and says so. For the reference site this maps onto, see the interactive reference facility.
Intake
What we ask for, what each input makes possible, and — the column that matters — what happens when you cannot supply it. None of those answers is that we estimate it.
| Input | Need | What it makes possible | Without it |
|---|---|---|---|
| Room and area schedule | Required | Establishes the addressable objects: which rooms exist, what they are called and which area each belongs to. | We walk the site or work from an evacuation plan. Slower, and the names will need confirming. |
| System inventory with kind | Required | Populates utilities, process equipment and computerised systems as three declared kinds rather than one word. | We reconstruct from maintenance asset lists, which usually omit computerised systems entirely. |
| Classification and pressure scheme | Helpful | Colours the model by classification and lets the cascade be shown as designed. | The model shows rooms without classification, which limits most contamination-control conversations. |
| Organisation chart by role | Helpful | Maps your titles to the canonical role list so accountability is visible per area. | Roles default to the reference list and are labelled as unconfirmed until you correct them. |
| Stage gate definitions | Helpful | Aligns your gates with the readiness view so the two products agree. | Readiness views are omitted rather than approximated. |
| System of record register | Required | Every evidence reference points at your system, never at SPEQ. | We cannot show evidence references at all, which removes most of the value. |
| Site drawings or CAD | Optional | Improves geometric fidelity at the higher levels. Not needed for the semantic model. | The model is schematic and correctly proportioned rather than dimensionally accurate. |
| Prior inspection findings | Optional | Focuses the model on the areas where the site is actually under scrutiny. | The model is built evenly, which is fine but less useful in the first month. |
A synthetic customer engagement for orientation. The site, its files, its conflicts and every figure are fictional. SPEQ is never the system of record for a customer’s facility data; the model points at the customer’s systems and says so.