01
The door schedule never matches site
A door gets reversed, a reader moves inside, a maglock becomes a strike. The schedule stays as issued and the as-built is fiction.
Solutions · Security
A door is never one device. It is a reader, a controller, a lock, a power supply, a request to exit, a contact and four cables. Graftix holds all of it against one pin on the drawing.
The problem
Nobody loses money on a security install because the cameras were hard to fit. They lose it because the door schedule was wrong, the IP addressing was done twice, and the client changed their mind about three rooms at second fix.
01
A door gets reversed, a reader moves inside, a maglock becomes a strike. The schedule stays as issued and the as-built is fiction.
02
Camera IPs, controller addresses and door numbers held in a spreadsheet on one laptop. When that person is off, work stops.
03
Three extra cameras and a door added verbally on site. No instruction, no cost, no evidence. That is the margin gone.
On the drawing
Pin each camera, reader, controller, intercom and detector where it actually sits. Hold IP address, camera model, door number, lock type and controller reference as custom fields on the pin.
Shot S1
Camera and door pins with addressing in custom fields
1600 × 1000
Shot S2
Site instruction and variation logged against a task
1600 × 1000
Protecting the margin
Security work attracts late changes more than any other trade on the job, because the client only understands what they are buying once they can see it on the wall. The answer is not to refuse. It is to log it.
The Vault · AES-256-GCM
No trade carries more sensitive credentials than security. Reader controllers, camera estates, intruder panels, VMS licences. Right now most of it lives in a WhatsApp thread that will still be on a former engineer's phone in two years.
The Vault holds them against the project, encrypted under a password you set. Graftix cannot read the contents, which means neither can anyone who compels us.
Shot V1
Vault unlocked, showing stored entries for a project
1600 × 1200
What you will be asked for
Whether you are inspected by a certification body, audited by the client, or simply asked to prove a system does what the specification said, the records need to exist and be findable.
Device and door schedules
Every camera, reader, controller and lock with its reference, address and location, matched to the drawing.
Commissioning sheets
Built as eForms in your own wording and completed on site, one per door or per system.
Technical submittals
Product data sheets held at organisation level and attached to the tasks they apply to.
As-built records
The drawing and the device data stay in step, because they were never separate files.
Variations and instructions
A documented trail of every change, what it cost and who asked for it.
Asset register
Serials, models and warranty dates, ready to hand straight into a maintenance agreement.
Security
Seven days, every feature, no card. Put a door schedule in it and see what happens when the drawing and the data are the same thing.