Knowledge / AEC-native Data
Drawing schedules (doors, windows, finishes, equipment)
Tabular schedules on drawings or in the model listing elements, their references, properties and locations, and the links between them and the plans.
A door schedule is the join between the plan and the specification. The plan shows door D-1-014 in a wall; the schedule row gives it a fire rating, an acoustic rating, a frame type and an ironmongery set, and each of those answers to a different specification clause. Schedules for doors, windows, finishes and equipment arrive as drawing sheets, as spreadsheets exported from the model, or both, and they drift apart because a revision to the plan does not always reach the schedule. Drawing schedule data extraction today is mostly a person retyping rows into a spreadsheet to check them against something else. Structured knowledge turns the schedule into something a team can question row by row, with every answer traceable to the sheet, the revision and the clause.
What Teams Ask of the Data
Which doors on this level are scheduled below the rating the fire strategy requires for the wall they sit in?
Which schedule rows changed between the last two revisions, and did the plan change with them?
Which door references appear on the plans but have no row in the schedule, or the reverse?
Which ironmongery set is each door scheduled with, and which specification clause defines that set?
Which finishes are scheduled for the rooms in this package, and do they match the finishes specification?
Which items of equipment are scheduled without a location, a power requirement or a supplier reference?
Does the schedule on the drawing sheet still agree with the one exported from the model?
What Generic AI Misses
A schedule is a table whose columns carry the meaning. Read the sheet as text and the columns collapse into a run of values with nothing to say which is the fire rating and which is the acoustic rating, or which door a value belongs to once a reference has wrapped to the next line. A schedule split across several sheets, or continued from a previous issue, loses its headings. The references in each row point outward, to a wall type on another drawing, an ironmongery set in the specification, a room on a plan, and a text reader sees a code where the engineer sees a link. It cannot tell you that D-3-021 sits in wall type W4, having never seen W4 as anything but two characters.
The other failure is currency. A schedule is revised on its own cycle and the plan it describes is revised on another. A tool given the schedule sheet reports the rating on that sheet, without knowing that the plan moved the door into a different wall two issues ago, or that the export from the model was regenerated since. It gives a clean answer with a row reference and the wrong rating, in the schedule's own layout. Nobody rereads a table that looks like the table. That is how a door specified correctly on paper is installed at the wrong rating.
What Structured Knowledge Answers
QUESTION
Which doors on level 3 are scheduled below the rating the fire strategy requires for the wall they sit in, and which schedule revision changed the rating?
ANSWER
Three doors on level 3 are scheduled FD30S where the fire strategy requires FD60S. D-3-014 and D-3-015 open off the protected corridor into the plant room and the electrical riser, both in wall type W4, scheduled EI 60; D-3-022 is the door from the stair lobby into the north corridor, in wall type W3, also EI 60. All three were FD60S in the door schedule at rev C02. Rev C03, issued with the level 3 plan re-issue, changed D-3-014 and D-3-015 to FD30S; the revision note refers to a client instruction on the plant room layout and says nothing about the wall rating. D-3-022 changed at rev C04 with no note. The fire strategy plan for level 3 still shows the corridor and riser enclosures as 60-minute compartment lines, and section 6.2 of the report requires FD60S doors to them; whether a lower rating could be accepted on any of them is for the fire engineer.
SOURCES
door schedule, drawing 6001 rev C02, C03 and C04; wall type schedule, drawing 9001 rev C02; level 3 general arrangement, drawing 2103 rev C05; fire strategy report rev P03, section 6.2 and level 3 plan FS-103.
Illustrative. The project, documents and references are invented to show what an answer looks like; nothing in it is advice.
We onboard a focused slice of your project data, configure the ingestion paths, extract a structured context graph, and build a workflow against the resulting structured knowledge layer.
The Data in Context
Schedules sit between the construction drawings, which locate each element, and the construction specifications, which define what each attribute in a row means. On projects with a federated model the schedule is often exported from the IFC and BIM models and then edited by hand. The specification to drawing consistency check and the drawing coordination review both read schedules as part of the drawing set.
Related Knowledge
Construction drawings
The 2D graphical record of design intent: plans, sections, elevations, details, schedules and title blocks, issued as sheets with revisions.
Construction specifications
The written performance and prescriptive requirements for materials, workmanship and systems, organised by work section (NBS, CSI MasterFormat, Uniclass).
IFC and BIM models
The federated 3D information model and its IFC exchange format: objects, properties, classifications, relationships and geometry.
Specification to drawing consistency check
Reconciling what the specification requires with what the drawings and schedules show, item by item, with every mismatch traced to its clause and sheet.
Drawing coordination review
Checking architectural, structural and MEP sheets against each other for conflicts, missing references and inconsistent schedules before issue.
Which schedule formats can it read?
Does it cover finishes and equipment schedules, or only doors?
How do we see it running on our own schedules?