BAC Guidelines

BAC Airport Design Guidelines

BAC Switchboard Selector

A guided selector for specifying new BAC-compliant LV switchboards — walk the BAC Airport Design Guidelines as a set of questions, get a clause-cited draft specification out the other end. Companion project to the BAC LV Audit System, for the same client (Brisbane Airport) and switchboard fleet.

The pipeline

From the project brainstorm — sb-selector-brain-storm.docx / Jake's-Switchboard-Selector-Flow-Chart.pdf:

Pre-fill from the LV AuditWhere this board replaces or upgrades one that has been audited
Engineer inputThe judgement calls only the engineer can make
BAC GuidelinesSix source documents, held and readable below
Summarised GuidelinesClause-referenced and verified against the sources
SelectorWalks the guidelines as questions
SpecificationDraft, then finalised by an engineer
SwitchboardBuilt to the specification, verified on the Checklist

The source documents

The BAC Airport Guidelines library, held in full and readable here — clause by clause, with the issued PDF alongside where we hold it. Every citation elsewhere in the app links back into this tab at the exact clause it came from.

Specifying a switchboard — the six documents the requirements model is built on.

The rest of the library — carried for reference. Nothing in the model cites these, but a project will reach for them.

Registry — what we hold and what we do not

A citation is only as good as the document behind it. This records which sources are available to check against, and which are not.

Summarised BAC Guidelines

The requirements the BAC guidelines place on a switchboard, sectioned, each carrying the clause it came from. Click any citation to read that clause in the source. Every item shows the result of checking it against that source.

Open questions

Points the source documents do not settle. These go to BAC as RFIs — they are not for the tool to decide.

Selector

Walk the Airport Design Guidelines as a set of questions and get a clause-cited draft specification. Where the board replaces one that has been audited, pre-fill reads that board's record and maps it onto the questions below. Reaching the Specification step files the draft under Document outputs.

Reads the board's audit record from the LV Audit System and maps it onto the Selector's questions. Every value arrives with where it came from and how far it was inferred — review before sending.

Document outputs

Every time the Selector reaches its Specification step, the resulting spec lands here as a Draft. Mark it Finalised once an engineer has checked it over — same draft-until- confirmed pattern as the LV Audit System's report review gate.

Checklist

What to verify on a manufactured board before it is accepted. Generated from the Summarised Guidelines, so it cannot drift from them — and deliberately narrower: only requirements you can actually confirm by looking at the finished board. Design decisions, BAC submissions and project-stage gates are requirements too, but they are not checked here.