Controls Assessment Preparation

Use this guide to gather a few useful facts before discussing a Controls Assessment. The list is optional, and missing records are welcome. It is preparation for a conversation, not a completed assessment, survey submission, or appointment. You can use the checklist below on this page or print a copy for your own notes. Checkbox selections are never sent to SOMA.

Controls platform, if known

Share the controls platform or front-end name if you know it. A name from an existing drawing, equipment label, or operator screen is useful; you do not need to identify every controller before contacting us. Note any known mix of systems or separate operator interfaces. If the platform is unknown, say so. Do not send passwords, login links with access tokens, or other credentials. Any system access needed for agreed work is arranged separately with the authorized site representative.

Buildings and equipment

Describe the buildings or areas involved and the equipment you want to discuss. For example, identify the air handlers, terminal units, heating or cooling plant, or other controlled equipment involved in the concern. Use the equipment IDs already used by your operators or drawings where possible. An approximate inventory is enough for an initial conversation. Identify areas that are particularly sensitive to interruptions, and distinguish equipment you have confirmed from equipment you believe may be involved.

Available drawings, point lists and sequences

Gather existing controls drawings, point lists, and sequences of operation that are readily available. Note their date or revision and whether they reflect the installed system as far as you know. You may have only part of the record set, an older document, or no drawings at all. Missing records are welcome; describe what is available and what is uncertain. Do not recreate a complete submittal just to make an inquiry. Keep original records with your site and share only material you are authorized to provide.

Operating symptoms and priorities

Explain what operators or occupants have observed, where it happens, and when it began or tends to recur. Separate observations from a suspected cause: an area that is too warm is an observation, while a failed sensor may still be a hypothesis. Existing alarm examples or a short description of an operating pattern can help. Say which concerns matter most to the site, such as comfort, repeated alarms, equipment operation, or difficulty using the interface. No trend export or completed investigation is required for an initial discussion.

Site contact and access constraints

Identify the person who can explain the site and coordinate any agreed access. Describe known constraints such as occupied hours, restricted areas, escort requirements, or work windows. These details help frame a conversation; they do not book a visit or confirm availability. Avoid sharing access codes or credentials in preparation notes. Permission to reach a system, any interruption to equipment, and the scope of an assessment must be agreed with the responsible people before work begins.