Architecting Connected Buildings, What I Wish Someone Had Told Me
summary
Company consolidates nine sites into 35,000 m2 head office serving 1,000-event visitors and 1,800–2,000 staff, exposing dozens of OT/IT silos (lighting, AV, HVAC, parking, lockers, catering, fridges). Project adds an IT architect, runs 1-year pilots and integrates cloud and on-site servers; an IBM Watson pilot supports analytics. Key surprises: variety of luminaires, weak vendor API documentation, missed locker testing, and the hard dependency chain — priority: electricity then network — that determines whether systems actually work.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:24Background
- 1:03Context
- 3:32Team
- 4:20Event Center
- 6:50Architecture
- 7:51Operational Technology
- 9:06Silos
- 12:06Smart Office
- 14:39Open API
- 17:01IT vs Construction
- 19:21Continuous Service
- 21:15Dependence
- 21:55Blocks
- 23:29Information Security
- 24:09Data Privacy
- 25:26Conclusion
related talks
16mEveryone architect!
26mBuild best-in-class customer experiences in Smart Cities
45mTowards Architecture Organization Topologies for Sustainable Fast Flow of Change
01h 00mDescribing and Documenting Your Architecture
16mEnterprise IoT software: Build vs. buy
19mHow Did We Get Here? Looking to the past to transform the future of IT
10mSmart Cities: The Rise of Programmable Buildings with APIs
08mthe role of software architecture