Automation ConfigurationSimplifying Automation Configuration at Scale
Designed automation configuration tools that helped building operations teams turn manual equipment adjustments, schedules, rule parameters, rule formulas, and setpoint changes into scalable control workflows.
Building operations teams were still handling many automation tasks manually, including schedule updates, setpoint changes, rule tuning, parameter adjustments, and repeated equipment-level configuration.
Operators needed a way to manage building devices and control systems at scale without losing confidence in what each rule would change, when it would run, or which assets it would affect.

Model operator work before modeling the interface
The work started with understanding how building teams adjusted schedules, tuned setpoints, reviewed equipment exceptions, and repeated configuration changes across assets. Those patterns shaped the product model more than the screen structure did.

Rule Parameter Management
Set default and exception values once, then apply them across hundreds of targets.

Schedule Management
Plan occupied and unoccupied windows on one shared calendar.

Rule Editor
Author reusable if/else templates with actions, alarms, and outcomes.

Bulk Edit Setpoints
Change many points in one pass from the floor plan or a global parameter.
Make control logic visible enough to trust
Rules, formulas, parameters, operating schedules, and affected devices had to be connected in one experience so operators could understand what would change, when it would run, and which systems it would affect.
Outcomes & scope
Manual work reduced: Replaced repeated asset-by-asset edits with configurable rules, schedules, parameters, formulas, and bulk setpoint controls.
4 operational workflows connected: Brought schedule management, rule configuration, parameter editing, and bulk setpoint changes into one automation model.
Reusable rule architecture: Standardized how operators define formulas, manage parameters, and apply building-specific values.
Portfolio-level control: Helped teams manage equipment behavior across buildings while keeping scope, timing, and impact visible.
Learnings & reflection
Automation design depends as much on understanding human operating patterns as understanding the underlying control system. The interface had to reflect how operators think about timing, exceptions, responsibility, and risk.
Rules are only useful when users can see the relationship between logic, parameters, affected equipment, and real-world operating schedules. Exposing those relationships made automation feel manageable instead of hidden.




