Where this offering fits
The Xage Fabric platform discussion concerns the architecture connecting identity-based controls across distributed assets. It is a platform-level enquiry, not a substitute for specifying which access or data-exchange outcomes are required. Begin with site boundaries, critical assets and the dependencies that must continue during communication loss.
Architecture and rollout decisions
Prepare a topology showing central services, local components, identity sources and enforcement boundaries proposed by the manufacturer. Review deployment and resilience for each site rather than assuming every location has identical connectivity. Pilot an access workflow and the approved behaviour during a lost link. Distinguish platform components from separately licensed capabilities and from customer-owned network or identity services.
An evaluation scenario for this offering
Use two representative sites with different connectivity assumptions. Demonstrate the approved local access task, central administration and the documented response to an unavailable inter-site link. Review which policies or components each site needs to retain operations. The architecture should identify dependencies and supported failure behaviour explicitly, rather than infer resilience from a distributed platform description. Include an upgrade sequence so the operational team can maintain the system without an undocumented all-sites change.
Evidence to request for this scope
- Obtain a current architecture with component roles and required communication paths.
- Confirm how local operations behave under the selected failure scenarios.
- Define upgrade sequencing and ownership across central administration and site maintenance teams.