Map the service
Record the service owner and dependencies across people, processes, technology, facilities and suppliers.
Manage service resilience from mapping through to remediation.
Lexa maintains important business services, impact tolerances, dependencies and testing records together. An identified weakness remains connected to the service it affects and the work required to address it.
THE WORK YOUR TEAM MANAGES
Operational resilience
A service map, test result and remediation log can each appear complete while telling different stories. The people reviewing resilience need to understand the relationship between the service, the assumptions behind its recovery and the results actually observed.
Testing and management judgments remain with your firm. A complete record does not by itself establish that a service can remain within its impact tolerance.
WORKING IN LEXA
How the workflow operates
Review testing
Attach scenarios and results to the relevant service, record limitations and review performance against the documented tolerances.
Resolve weaknesses
Assign remediation, track dependencies between actions and retain the supporting records used to approve closure.
RECORDS AND OUTPUTS
What the workspace maintains
- Important business service register
- Impact tolerances and dependency maps
- Scenario and testing records
- Vulnerability and remediation registers
SHARED PRODUCT CAPABILITIES
Use the same records
across your reviews.
Ownership, document history, actions and approvals are shared platform capabilities. A record can support more than one regulatory workflow while retaining its original source and review history.