Skip to main content
AP AI Software Register Interest

Workflow

How it works

One project's information, carried from the room to the reviewed deliverable without being retyped, redrawn or reconstructed at each handover.

This describes the workflow AP AI Software is building. It is in development end to end, and no step below is commercially available.

  1. Step 1

    Capture the room

    Field measurement, photographs and room geometry are recorded on site, in a native Apple application, while the room is still in front of you.

  2. Step 2

    Draw and document on site

    Floor plans, reflected ceiling plans, device placement and signal intent are authored in the field rather than reconstructed later from notes.

  3. Step 3

    Carry the evidence forward

    What the field recorded travels with the project, so a later reviewer can see where a measurement or an assumption came from.

  4. Step 4

    Develop requirements and design

    Source documents and site evidence become reviewable AV requirements, and the design develops with its assumptions and revisions visible.

  5. Step 5

    Estimate and engineer

    Equipment and materials lists stay connected to the design decisions that produced them.

  6. Step 6

    Review and issue

    Qualified people check and release the deliverables. AI proposes and assists; it does not approve.

What travels with the work

A drawing is only as trustworthy as the evidence behind it. Each stage below keeps the record that produced it, so a number on an issued sheet can be traced back to the reading it came from, the device that took it and the person who accepted it.

  1. 01

    Capture

    CaptureID

    A scan or photograph of the room, stored immutably with its sensor and source metadata.

  2. 02

    Reading

    ReadingID

    A measurement, its device and session provenance, and an explicit acceptance by the person who took it.

  3. 03

    Revision

    RevisionID

    The drawing that the accepted reading supported, appended as a new revision with its lineage intact.

  4. 04

    Equipment

    EquipmentID

    One device record, with its typed ports — shown on the floor plan, the ceiling plan and the one-line without becoming three devices.

  5. 05

    Publication

    Export manifest

    One resolved revision, its approval status and the sheets issued from it.

One measurement, end to end

Following a single dimension through the chain, in a room that does not exist.

ILLUSTRATIVE A fictional room, with invented identifiers and dates. Not a customer project, not a screenshot, and not a record of work performed.

Illustrative AV floor plan of a fictional training room A rectangular room 6 800 by 3 600 millimetres with a 3 048 millimetre ceiling. A display is mounted on the north wall, four ceiling speakers are arranged in a two by two grid, a PTZ camera faces the display from the south wall, an equipment rack sits in the south-west corner, and a floor box serves a central table. A cable pathway runs from the rack to the display. Every dimension is invented. TABLE D-1 S-1 S-2 S-3 S-4 CAM-1 RK-1 FB-1 PATHWAY 6 800 mm 3 600 mm TRAINING ROOM 2-114 AV FLOOR PLAN · REV r4 SCALE 1:50 · FICTIONAL N

Drawn, not captured. This is what the work produces — dimensioned geometry, tagged devices, pathways, a title block carrying the revision it came from. The table below follows one measurement on this plan back to the reading it came from.

An invented measurement traced from capture to publication
Stage Record What it holds
Capture CAP-8831 LiDAR scan of the room, taken on site. Stored immutably with its sensor metadata.
Reading RDG-0421 7 315 mm wall-to-wall from a laser distance meter, accepted by the surveyor who took it.
Revision REV-r4 The floor plan that acceptance supported. Revision r3 is still there, unchanged.
Equipment EQ-114-DSP-01 One processor record with typed ports — not three records for three drawings.
Placement PL-0067, PL-0068 That one record shown on the floor plan and again on the ceiling plan.
Publication PUB-2026-03-14 The sheet set issued from r4, with the manifest of what went out.

The point is the direction it runs in. Ask why a wall is where it is on the issued sheet, and the answer is a specific reading, taken with a specific device, that a specific person accepted — rather than a dimension someone typed in at some point and nobody can now account for.

The rules that make it hold

These are design commitments for software in development, not descriptions of shipped behaviour.

  • An accepted reading is evidence plus a decision.

    Taking a measurement does not silently resize the drawing. Someone applies it, and the drawing records which acceptance supported the change.

  • One device is one record.

    A processor on the floor plan, the ceiling plan and the one-line is the same record three times over, not three devices that can quietly disagree.

  • Schedules are derived, not maintained.

    A cable schedule comes from the signal graph. It is not a second list kept alongside it, because two lists eventually contradict each other.

  • Partial stays partial.

    The observed end of an incomplete scan is not a confirmed corner. Closure and construction readiness are explicit checks, not a guess at the nearest endpoint.

  • Editing appends.

    A revision is a descendant with its lineage intact. Earlier revisions are not overwritten, and a later change cannot rewrite what an issued sheet was based on.