TMA Tafoya Mission Assurance

Deliverables & Pilot

From conflicting records to a traceable handoff.

A defined documentation workflow for federal and military construction primes, building automation and HVAC controls integrators, FRCS contractors and project closeout teams.

The reconciliation workflow

01 · Client-supplied inputs

Equipment schedules, drawings, controller lists, network records, vendor documents and authorized exports. Agree source versions and review ownership before work begins.

02 · Compare & reconcile

Normalize device attributes, compare records, retain source references and document conflicts or omissions. Route technical questions to the customer's qualified reviewer.

03 · Document & hand off

Maintain revision history, evidence references and visible exception ownership. Package reconciled records and unresolved items for designated review and turnover.

Defined work products, not hidden assumptions.

The agreed documentation package may include the following. Unverified attributes and unresolved exceptions stay visible rather than being silently treated as confirmed.

  1. 01

    Reconciled building-control asset register

  2. 02

    Device inventory comparison and normalization

  3. 03

    Discrepancy and exception tracking log

  4. 04

    Source-document and FRCS cybersecurity evidence index

  5. 05

    Revision-controlled inventory workbook

  6. 06

    Reviewer-ready documentation and open-item handoff

Proposed first engagement

Building Controls Inventory Reconciliation Pilot

Start with a bounded record set and a customer-designated reviewer. The following are proposed starting parameters, not guarantees of capacity, price, turnaround or acceptance.

Subsystem
1 building-control subsystem
Device records
Up to 50 client-supplied device records
Source documents
Up to 3 agreed source-document sets
Outputs
Documented exceptions, traceable reconciliation outputs and a final package for the customer's designated reviewer

Final scope, technical oversight, acceptance criteria, schedule and pricing must be agreed before work begins. Documentation support does not independently establish regulatory compliance or guarantee government acceptance.

Discuss a Pilot Engagement Download Capability Statement
Building automation equipment inside an electrical control enclosure

Technical delivery boundaries

Standard scope: records reconciliation and cybersecurity evidence organization using customer-supplied documentation and authorized exports. Customer-designated qualified personnel remain responsible for physical verification, technical engineering and cybersecurity compliance determinations, live OT access and scanning, configuration changes, testing and commissioning. These activities are not independently delivered by TMA under the standard documentation-support scope.