Ownership
The operational data belongs to the operator named in the agreement, pooled with nothing and training nothing.
For data center operations and site teams. We build the system the site is run from: what work is open, which vendor is on the floor, who was granted access and why, and what the conditions were when it happened. It runs inside your environment, including on premises, and it reports upward on the cadence you already owe.
Where the data lives
On a data center engagement this question comes first, not last. If the answer is wrong, nothing else in the scope matters.
The system runs where you decide it runs: on premises inside the facility, in your own cloud account under your own controls, or split, with the operational record held locally and only agreed reporting leaving the site. It does not need to call out to us to function, and nothing degrades in an isolated deployment.
Ownership
The operational data belongs to the operator named in the agreement, pooled with nothing and training nothing.
Access by us
None by default: any access is granted by you, scoped, time bound, logged on both sides and revoked.
Export
Complete export in open formats on request and at handover, with the structure documented.
Audit
Every entry and amendment keeps who, when and the previous value, so history reconstructs under scrutiny.
Confidentiality
Site layouts, vendor arrangements, planning and incident detail stay inside the engagement, never named publicly.
What we build
The operating record of the facility, written where the work happens rather than reconstructed afterwards from tickets and recollection.
Work tracking
Planned, corrective, installation and decommission work, held against the space, room and system it touches.
Vendor management
Who is engaged, on what scope, with which documentation current: the vendor record and the work record are one.
Access control records
Requests, approvals, escorts, areas and the window granted, reconciled against the physical access system.
Site conditions
Readings, walk observations and environmental notes captured against location and time.
Change and method
A method of procedure, its approvals, its window and what was done inside it, held as one object.
Reporting upward
Daily, weekly and monthly, generated on the hour it is due, with the exception detail questions return to.
Integration and stakeholders
A running site has a stack already, and most of it is load bearing. We integrate with it as named categories of system and replace none of it by default.
Building and facility monitoring
Conditions and alarm history read in, so a work record carries the state of the space around it.
Asset and infrastructure management
Asset identifiers taken from the system that already owns them, never duplicated into a second inventory.
Maintenance management
Planned schedules and corrective work exchanged with the maintenance system of record.
Ticketing and incident management
Operational work linked to the ticket it came from and back again, in both directions.
Physical access systems
Granted access reconciled against recorded entry, with discrepancies raised rather than filed.
Identity and directory
Sign-in through your own directory, with roles and removal following your joiner and leaver process.
Monitoring and observability
The system reports its own health into the tooling your team already watches.
Operations, the site team and the vendors on the floor all write into it, and each has a different amount of time to give it. Site technicians and shift teams author most of the record, often on a tablet or a phone, standing in a cold aisle with hearing protection on and hands occupied. Capture has to beat the paper form it replaces, or it gets completed later from memory, which is the failure that makes every report downstream untrue.
More than 45 people deliver it: in-house planners, architects, designers and data analysts, with engineering contracted to scope.
Shift and site teams
The walk, the reading and the work note follow the route they already take, in the order they take it.
Operations management
Overdue work, open access grants and vendor documentation gaps surfaced rather than searched for.
Vendors and contractors
A narrow, scoped way in: their own scope and documentation, nothing else on the site visible to them.
Security and compliance teams
Access and change history reconstructable end to end, with the evidence attached.
Whoever receives the reporting
Figures that keep their derivation, so a challenged number has an answer rather than a rebuild.
Scope and assurance
Scoping starts from the reporting you owe and the conditions the work is performed in, then works back to what has to be captured. We map the current record: what is captured, where, what is retyped, and what the last reporting cycles cost in hours. That map is the scope, written as a schedule of capabilities, integrations, hardware, hosting location and training, with the deployment environment named in it.
The engagement is quoted as a single number for that site or estate, with payments tied to milestones, so it sits in the operating technology line and is administered like any other committed work. A second site extends the same system under a new work order.
Nothing we deliver sits in the path of running infrastructure. The system reads from operational tooling and writes to its own store, so installation, upgrade and rollback need no change window against production plant.
Prepared in advance, in your formats, because on a facility engagement this is the gate rather than a formality.
Insurance certificates
Issued to the operator at the required limits, with additional insured and waiver language, before site attendance.
Master agreement
A master services agreement with per-site work orders, so a further site or scope needs no reopened terms.
References
References on request from work of comparable operational sensitivity, given privately and never published.
Security questionnaire
Hosting, access control, encryption, subprocessors, personnel screening, secure development and incident response.
Continuity
Source code and schema escrow, documented infrastructure, runbooks and a handover package, so your team can change it.
Site requirements
Our people work to your induction, screening, escort, photography, clean work and record retention rules.
A capability statement comes back written against that site, for facilities anywhere in the United States. To start: call (252) 666-7217 or email [email protected].