Multiple agencies keep local CMDB-like sources but must report against shared IRM entity types for a federated city program. What design approach fits?
Select an answer to reveal the explanation.
Short Explanation
Federated doesn’t mean chaotic. Agencies can keep feeding from local sources as long as those feeds map into shared entity types and classes. That’s how one citywide compliance view still makes sense.
Full Explanation
A federated model preserves agency source systems while unifying governable objects through shared entity types and classes. Clear mapping from each source table into the common entity framework enables consistent scoping and reporting without requiring a single physical CMDB. Unrelated per-agency definitions without class unification prevent enterprise-level IRM views.