Opportunity specifications

Technical and scope specifications extracted from an opportunity's tender documents.

Part of Opportunities in the register catalog.

Register ID

opportunity_specificationsUse this name to ask for the register. The API calls it a shelf ID.

Each record is

A stateThe current value of something, replaced when it changes.

Status

AvailableFilled today from connected systems, uploads or public data.

Data

OrganisationPrivate to each organisation's own workspace.

Version

v1Current version.

Download JSON SchemaSee an example record

Standards

This register holds records these standards and laws ask for. Holding them does not by itself certify compliance.

• ISO 19650Information management using building information modellingInternational

Connectors

Connected today

Demiton keeps this register current from these systems now.

No system fills this register yet.

On the roadmap

Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.

None planned yet.

Fields

9 fields: 5 required, 4 optional.

Required

Every record carries these fields.

specification_codeText

The clause/document code exactly as written on the drawing, including parenthetical alternative codes and revision suffixes (the parser's own examples: C242, TS 02168.1 (R64), AS3798-2007); explicit null when the entry has no code of its own.

Example: MRTS04

specification_descriptionText

The specification's title as the issuing body wrote it.

Example: General Earthworks

issuing_bodyText

The issuing body / code-set grouping the entry sits under; explicit null only when the drawing set places the entry nowhere.

Example: TMR

source_document_pathText

The resolved path of the drawing-set PDF. Provenance key for the fact.

Example: /Opportunities/RFT260051/Drawings/RFT260051-Specification…

specificationsList

The extracted governing-specification entries. Empty array is meaningful and must be written.

Optional

Present when the source system records them.

source_document_nameText

Human-readable file name.

Example: RFT260051-Specifications.pdf

extracted_page_countNumberUnit: pages

Pages the parser actually read, capped at 40.

Example: 32

specifications_table_presentTrue or false

Whether the drawing set carried a literal boxed "PROJECT SPECIFICATIONS" table rather than inline/clause-list references.

Example: true

extraction_notesText

Free-text caveats from the extractor (raster pages, LLM notes).

Example record

A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.

opportunity_specifications.example.json

{
  "extracted_page_count": 32,
  "issuing_body": "TMR",
  "source_document_name": "RFT260051-Specifications.pdf",
  "source_document_path": "/Opportunities/RFT260051/Drawings/RFT260051-Specifications.pdf",
  "specification_code": "MRTS04",
  "specification_description": "General Earthworks",
  "specifications": [
    {
      "code": "MRTS04",
      "description": "General Earthworks"
    }
  ],
  "specifications_table_present": true
}

Use this contract

The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.

Schema URL

https://docs.demiton.io/registers/opportunity_specifications/v1.json

Show the full JSON Schema

Loading the schema…