.png)
Dartmouth Integrates Metasys BMS to Planon IWMS So Device and Firmware Data Drive Capital Planningc
Dartmouth College's Integrated Automation team is on a mission to make BAS data more reliable and accessible to the larger campus team.
Instead of requiring staff to request BMS reports and data from the small group who could run them, the college built an internal integration between the JCI Metasys REST API and its IWMS platform, Planon. The goal was to publish device metadata, including BACnet device IDs and firmware versions, into a system that other teams already use.
The immediate use case is lifecycle planning. Dartmouth tied the work directly to budgeting for controller replacements and firmware upgrades. Obsolete firmware is no longer something the team discovers mid-project or mid-failure. Itâs visible in Planon before budgets are set.
The BMSâIWMS integration sits inside a broader effort to treat OT devices as managed infrastructure. Dartmouth combines network monitoring, IP address tracking, and daily BACnet topology mapping through ACE IoTâs Grasshopper to keep inventory and firmware data current across a constantly changing campus.
That visibility reduces risk for the campus. When device state, firmware versions, and network placement are continuously tracked, integrations are easier to troubleshoot, and upgrade cycles are easier to plan. The team said that confidence has reduced the instinct to âhardwire everythingâ for reliability. With better control over device lifecycle and network posture, Dartmouth is more comfortable scaling BACnet across buildings.
â
Register for the next Nexus Labs event
Sign up for the newsletter to get 5 stories like this per week:
Dartmouth College's Integrated Automation team is on a mission to make BAS data more reliable and accessible to the larger campus team.
Instead of requiring staff to request BMS reports and data from the small group who could run them, the college built an internal integration between the JCI Metasys REST API and its IWMS platform, Planon. The goal was to publish device metadata, including BACnet device IDs and firmware versions, into a system that other teams already use.
The immediate use case is lifecycle planning. Dartmouth tied the work directly to budgeting for controller replacements and firmware upgrades. Obsolete firmware is no longer something the team discovers mid-project or mid-failure. Itâs visible in Planon before budgets are set.
The BMSâIWMS integration sits inside a broader effort to treat OT devices as managed infrastructure. Dartmouth combines network monitoring, IP address tracking, and daily BACnet topology mapping through ACE IoTâs Grasshopper to keep inventory and firmware data current across a constantly changing campus.
That visibility reduces risk for the campus. When device state, firmware versions, and network placement are continuously tracked, integrations are easier to troubleshoot, and upgrade cycles are easier to plan. The team said that confidence has reduced the instinct to âhardwire everythingâ for reliability. With better control over device lifecycle and network posture, Dartmouth is more comfortable scaling BACnet across buildings.
â
Register for the next Nexus Labs event
Sign up for the newsletter to get 5 stories like this per week:
This is a great piece!
I agree.