Purchasing often arrives with a corridor photograph or a catalogue speed: four cameras and a recorder for that site, write it up. We do not read that sentence as a one-line hardware order. The stream may be real; which VLAN the recorder sits on, where the password is written, whether a retention period is in the file, and who is called during an outage are usually empty. The gap is a scattered operating picture, not the make of the box.

This note is the reasoning behind the CCTV, ERP, and related business-app line on Services. Cameras, access control, and line-of-business apps go into the same file as network, identity, and backup. The deliverable is not a forced brand. Which VLAN carries recording, who watches, and who is on call when the circuit drops stay on paper.

Recorder on a random VLAN

If the recorder sits on a random VLAN, the password is on a sticker, and nobody wrote a retention period, the fault is not the box — it was never part of the environment. The device may share a broadcast domain with the till line, the guest network, or printer DHCP. The till does not close that day; the next morning a stretch of recording is missing. Ordering more cameras does not end that collision.

The floor runs on hours. Till close, shift change, and a seasonal store set the measurement window and the cutover window. “We’ll cut over at the weekend” has to appear in the proposal as a window, or install day collides with till close. We do not price a twenty-site camera refresh from a corridor photograph or a catalogue speed.

Six doors, six password papers, six disks, and a “someone knows” arrangement are still one business. From the hub it all looks like the same box. From a site it is another vendor. The assessment puts both views in one file. Missing documents are not ignored; they sit as risk in the next phase.

A retention period is a row in that file: is it written, who signed it, what happens when the disk fills. That row is not a legal opinion. We do not publish camera-law advice, a consent pack, or a “keep it for N days” rule.

Integration, not a gadget catalogue

Cameras, access control, and line-of-business apps belong with network, identity, and backup. Which VLAN, who watches, where recording lands, how an outage is handled — integration is the answer to those four questions. We do not push a camera brand; procurement runs after funds are in.

A camera plan is not boxes on a corridor. Staff, guest, and recording traffic take separate paths; firewall rules keep that split. Whose account watches, whether the password still lives on paper, and whether it closes when someone leaves all go into the identity inventory. The backup window does not rest on “someone copies the disk”; it sits in the proposal.

The NVR or recording software is not an annex to the site LAN. When the branch circuit drops, the till, identity, and the stream can drop together. Which location has a spare path, who brings it up, and who is called — those three lines sit in the operating picture. The on-call number does not live in a catalogue; it lives in the proposal.

On a six-site business each door is not a separate “camera job.” The inventory is one file: which site, which circuit, which identity, which recorder. The fourth branch is a row in that file. We do not publish customer interiors, camera stills, or field photographs; the schematic stays unnamed.

Wi-Fi is an operations problem writes the same picture from the wireless side. The recording VLAN is a row in that picture, not a separate toy.

Assessment first

Pricing unwritten camera work as an implementation project is the wrong order. The default first paid step is offer A: a paid assessment and roadmap. Deliverables are a current-state summary, a risk and priority matrix, a 90-day / 6-month / 12-month roadmap, and a management presentation. Hardware purchase, installation, third-party licences, and ongoing support sit outside that fee.

The method is on the Approach page; phase titles match the proposal template. Phase 1 narrows scope: how many locations are in this assessment, which are storage or seasonal, whether a cutover window is tied to till close, which doors already have recording. Phase 2 plans interviews and technical review against site count. Phase 3 classifies risk; “buy this box” becomes a procurement line only after dependencies are written. Phase 4 puts dated bands in the management summary.

Why the paid assessment comes first sets out what A delivers and what stays outside the fee. This note attaches that method to field systems. Delivery of the assessment does not automatically open an “install it now” line.

A single-office, single-rack discovery does not hold at this scale. Interviews and the field tour follow the scope note. A crew walking six doors in one pass is not the promise of Phase 2. A signing authority from the hub and at least one site lead at the opening meeting is enough.

Implementation, retainer, procurement

Once scope is tight, modernisation (B) is a separate project. Workstreams split: recording VLAN, identity, backup, cutover window, access control where it exists. We do not write a large fixed price before discovery. Installation is not an annex to the assessment; B is written from the items in Phase 4. There is no one-line fixed price for “connect everything.”

Run-state work is its own line. A monthly support fee (retainer) is billed in advance; hours, response window, and out-of-scope extras are written. Signed call-out work (D) runs as needed; a minimum call-out or half-day, travel as a separate line. The on-call number sits in the proposal. Ongoing operations are not inside the assessment fee.

We do not fold B and C into one sentence. After install, “call us and it will be fine” is not an operations contract. Which password reset is a call-out and which sits inside the monthly fee stays on paper. Otherwise a full disk at the fourth site mixes into the implementation balance.

Procurement (E) is its own commercial line. Cameras, recorders, and licences are not a catalogue pick. Make and model attach to a line in the assessment or implementation proposal. One hundred percent of the supplier cost is collected before the order; the service margin is separate. The company does not finance customer hardware from its own cash.

“Buy this” written before VLAN, identity, and backup are on paper produces the next outage and the wrong purchase order. Unless the proposal says otherwise, installation and run-state operations are later phases. We do not put a box list in place of the assessment.

How to write

Write to info@akillitrakya.com to pin down scope. The fields on the Contact page are enough for a pre-proposal file: name, company, number of sites (1 / 2–5 / 6–20 / 20+), user band, need (assessment / implementation / support / procurement / other), a short message, and an optional callback number. Writing is a pre-contract request under the privacy notice. There are no prices on the site; a price sits in a proposal after scope is written.

Write the picture before the box list, so the site still runs.