In Part 1 of this blog series, I proposed that closed-loop orchestration (CLO) is a data management problem. Data extends beyond your medical history, social media, and other PII in the digital world. Configurations, inventories, and monitoring systems are based on managing, interpreting, and actioning data. CLO is a workflow about manipulating the data around the target environments. Even the policies and constraints need to be expressed as data.