01 / WHO THIS IS FOR
Who this is for
You may have a point list, configuration export, or integration mapping that needs a closer review. A possible starting point is one subsystem with approved requirements and supplied information that can be reviewed without plant access. A short description starts the discussion; we’d agree the requirements and controls reviewer before accepting work.
02 / PROPOSED PILOT
Proposed point and integration QA pilot
A possible pilot would compare supplied point and configuration information with approved requirements for one subsystem. Quality assurance (QA) here means checking that information for the completeness and consistency we agree to review. The proposed findings report would show the evidence and which agreed checks passed, failed, or were not assessed, with reasons.
The findings would help your controls lead decide which mappings need clarification and what requires further engineering investigation. This pilot is being developed alongside our BMS practice. We’d confirm the task, relevant experience, permissions, and reviewer before accepting work.
03 / SCOPING INPUTS
Information needed
For the first conversation, describe which documents or exports are available, if known. We can agree a suitable sharing channel and permissions before you send detailed material. The following inputs would be agreed for the review itself.
- Approved requirements
- The expected behavior or project criteria that define the checks.
- Configuration data
- A relevant point list or configuration export for the subsystem, with permission to share it.
- Identifiers and mappings
- Point names, identifiers, mappings, units, and data types needed to understand relationships.
- Review arrangement
- The controls reviewer, agreed checklist and limits, findings format, and review point.
04 / REVIEW METHOD
Checks and findings
Depending on the requirements and data supplied, a proposed review could check for missing expected points, inconsistent identifiers or mappings, and units or data types that need clarification. The aim is to show what needs attention and what requires further engineering review. If BACnet or Modbus is involved, we’d discuss the specific information and our current experience before agreeing checks.
- Evidence for each finding.The requirement and supplied information behind the observation.
- Results of agreed checks.Passed, failed, or not assessed, with the supporting evidence or reason a check could not be completed.
- Questions to resolve.Missing, conflicting, or unclear details for your team to examine.
- A report for review.Findings and open questions brought together for your controls lead’s next decision.
05 / BOUNDARIES
Scope and responsibilities
What the proposed review covers
Agreed completeness and consistency checks against approved requirements, using supplied configuration information. The report would identify evidence, results, open questions, and items not assessed.
What it does not cover
Physical wiring, sensor or actuator performance, HVAC design or tuning, live system changes, plant readiness, and commissioning acceptance.
Your team would approve the requirements and permissions, decide access, assess physical implications, and retain plant acceptance authority. Crew Bravo would be responsible for the agreed checks and findings report. The report would support your controls team’s review, without certifying plant or establishing commissioning readiness.
06 / CURRENT CAPABILITY
Current experience
Our established background covers software engineering, cloud, networking, diagnostics, and API and system integration. That experience includes working with data exchanged between systems. We’re building hands-on BMS protocol, platform, and field experience, and would discuss the relevant experience and limits before agreeing your task.
Our initial market focus is the Netherlands. We’re interested in conversations with integrators and controls teams there about suitable ways to collaborate.
07 / INQUIRY
Discuss your task
Send a short description of the issue or question you’d like to review. Include the subsystem, available documents, and possible reviewer if known. Please keep passwords, access credentials, and sensitive configuration exports out of the form.