Newshot

A Model-Driven Automation Pipeline for Building Operation

Summary

arXiv:2611.21631v1 Announce Type: new Abstract: Building Control Systems (BCS) engineering in the Architecture, Engineering, Construction & Operations (AECO) domain remains a complex, manual, and error-prone process, with fractured tools and manual commissioning causing design and built reality to diverge into a performance gap. We argue that a fully integrated and automated, tool-supported workflow spanning design, programming, and operation is feasible and can improve efficiency while reducing manual effort and configuration errors. Building on model-driven engineering, we present an automated process pipeline for modeling, programming, and auto-commissioning BCS. It uses two domain-specific modeling languages with tooling support to synthesize and deploy executable artifacts from platform-independent models, replacing a fractured, multi-stakeholder handoff process with a defined four-step workflow and improving consistency across the engineering lifecycle. Our evaluation reports not…

Original text(via arXiv cs.SE)

Computer Science > Software Engineering

Title:A Model-Driven Automation Pipeline for Building Operation

Abstract:Building Control Systems (BCS) engineering in the Architecture, Engineering, Construction & Operations (AECO) domain remains a complex, manual, and error-prone process, with fractured tools and manual commissioning causing design and built reality to diverge into a performance gap. We argue that a fully integrated and automated, tool-supported workflow spanning design, programming, and operation is feasible and can improve efficiency while reducing manual effort and configuration errors. Building on model-driven engineering, we present an automated process pipeline for modeling, programming, and auto-commissioning BCS. It uses two domain-specific modeling languages with tooling support to synthesize and deploy executable artifacts from platform-independent models, replacing a fractured, multi-stakeholder handoff process with a defined four-step workflow and improving consistency across the engineering lifecycle. Our evaluation reports notable efficiency gains, improved adaptability, moderate-to-high user acceptance, and good performance with solid scalability.
Comments:Accepted for publication at the 27th International Conference on Product-Focused Software Process Improvement (PROFES 2026)
Subjects:Software Engineering (cs.SE)
Cite as:arXiv:2611.21631 [cs.SE]
(or arXiv:2611.21631v1 [cs.SE] for this version)
https://doi.org/10.48550/arXiv.2611.21631 arXiv-issued DOI via DataCite (pending registration)

Submission history

Access Paper:

  • HTML (experimental)

Additional Features

  • Audio Summary

Current browse context:

References & Citations

  • Google Scholar
  • Semantic Scholar

BibTeX formatted citation

Bookmark

Bibliographic and Citation Tools

Code, Data and Media Associated with this Article

Demos

Recommenders and Search Tools

arXivLabs: experimental projects with community collaborators

arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website.

Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them.

Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs.

The text above was extracted automatically from the source page and may miss images, tables or code blocks. The original is authoritative.

Published by arXiv cs.SE
This site only summarises and aggregates; copyright stays with the original author. Headlines and summaries follow the source — where they differ, the original wins.
Read the original ↗