Verify reality before specifying technology — assess the physical and digital environment across only the modules the Operational Requirements actually call for.

Trigger

Operational Requirements defined.

Owner

Estimator

Inputs

• Operational Requirements list.
• Site access.

Required conditions

• Site visit scheduled and confirmed with the customer.

Steps

1. Determine which assessment modules apply — site/physical, access-control openings, video locations, network/connectivity, power, cybersecurity — based on the requirements and project type.
2. Conduct the physical site inspection per the Site Survey Procedure SOP.
3. Assess power availability and existing infrastructure for each applicable module.
4. Assess network/connectivity dependencies for each applicable module.
5. Identify cybersecurity ownership considerations where a connected system is involved.
6. Note system dependencies and material failure modes where relevant.
7. Document constraints, risks, and unknowns discovered during assessment.

Decision points

• Which modules actually apply to this opportunity's requirements? — apply Minimum Necessary Capture; don't assess a module with no related requirement.
• Is anything requested physically infeasible as understood so far? → Note it now, don't wait for Solution Design to discover it.

Outputs

• Structured findings per applicable module, photos, and a constraints/risks log.

Failure / exception path

Site access not obtainable, or scope is not physically feasible as understood — held pending customer coordination or Sales Director escalation.

Related system objects

Future automation opportunity

Auto-select applicable assessment modules from ProjectType/Requirements, so the assessor only sees relevant sections; batch-capture pattern for repeated items like openings or camera locations.

Required data

• Applicable modules selected
• Per-module findings
• Photos per checklist category
• Constraints/risks log