{"component": "clause", "props": {"groups": [{"samples": [{"hash": "3d1oKDFYo9P", "uri": "/contracts/3d1oKDFYo9P#availability-management", "label": "Contact Center Managed Service Agreement", "score": 24.7638494975, "published": true}, {"hash": "6ezabEQdJlp", "uri": "/contracts/6ezabEQdJlp#availability-management", "label": "Contact Center Managed Service Agreement", "score": 20.9438740589, "published": true}, {"hash": "93MNwkdceV0", "uri": "/contracts/93MNwkdceV0#availability-management", "label": "Contact Center Managed Service Agreement", "score": 20.7932922656, "published": true}], "size": 5, "snippet_links": [{"key": "service-availability", "type": "clause", "offset": [42, 62]}, {"key": "design-improvements", "type": "definition", "offset": [88, 107]}, {"key": "as-required", "type": "clause", "offset": [109, 120]}, {"key": "the-development", "type": "clause", "offset": [202, 217]}, {"key": "improvement-plans", "type": "definition", "offset": [243, 260]}], "snippet": "Verizon will actively monitor and analyze service availability, recommending device and design improvements, as required. When needed, Verizon will proactively address availability improvements through the development and execution of service improvement plans.", "hash": "23bf63407814fb35db6b6675cfc6178a", "id": 1}, {"samples": [{"hash": "bZoz5cQcVmB", "uri": "/contracts/bZoz5cQcVmB#availability-management", "label": "Managed Application Services Agreement", "score": 22.6440793977, "published": true}], "size": 3, "snippet_links": [{"key": "activities-of-the", "type": "clause", "offset": [4, 21]}, {"key": "management-process", "type": "clause", "offset": [35, 53]}, {"key": "portfolio-management", "type": "clause", "offset": [90, 110]}, {"key": "availability-requirements", "type": "definition", "offset": [145, 170]}, {"key": "unit-availability", "type": "clause", "offset": [195, 212]}, {"key": "requirements-for", "type": "clause", "offset": [213, 229]}, {"key": "enhanced-service", "type": "definition", "offset": [239, 255]}, {"key": "design-criteria", "type": "definition", "offset": [302, 317]}, {"key": "application-services", "type": "clause", "offset": [335, 355]}, {"key": "it-component", "type": "definition", "offset": [512, 524]}, {"key": "where-appropriate", "type": "definition", "offset": [534, 551]}, {"key": "to-provide", "type": "definition", "offset": [596, 606]}, {"key": "the-applications", "type": "clause", "offset": [748, 764]}, {"key": "cost-effective", "type": "clause", "offset": [776, 790]}, {"key": "the-targets", "type": "clause", "offset": [856, 867]}, {"key": "reliability-and-maintainability", "type": "clause", "offset": [886, 917]}, {"key": "software-components", "type": "definition", "offset": [929, 948]}, {"key": "reporting-of", "type": "clause", "offset": [1098, 1110]}, {"key": "support-organization", "type": "definition", "offset": [1208, 1228]}, {"key": "trend-analysis", "type": "clause", "offset": [1260, 1274]}, {"key": "it-systems", "type": "clause", "offset": [1331, 1341]}, {"key": "corrective-actions", "type": "definition", "offset": [1488, 1506]}, {"key": "aimed-at", "type": "definition", "offset": [1740, 1748]}, {"key": "application-components", "type": "clause", "offset": [1812, 1834]}, {"key": "future-business", "type": "clause", "offset": [1856, 1871]}, {"key": "reporting-to", "type": "definition", "offset": [1949, 1961]}, {"key": "management-services", "type": "clause", "offset": [2135, 2154]}, {"key": "policies-and-procedures", "type": "clause", "offset": [2228, 2251]}, {"key": "management-tools", "type": "definition", "offset": [2281, 2297]}, {"key": "support-requirements", "type": "clause", "offset": [2362, 2382]}, {"key": "adhere-to", "type": "clause", "offset": [2485, 2494]}, {"key": "authorized-staff", "type": "definition", "offset": [2568, 2584]}, {"key": "designated-personnel", "type": "definition", "offset": [2594, 2614]}, {"key": "access-to", "type": "definition", "offset": [2633, 2642]}, {"key": "knowledge-base", "type": "definition", "offset": [2683, 2697]}, {"key": "participate-in", "type": "definition", "offset": [2710, 2724]}, {"key": "requirements-analysis", "type": "clause", "offset": [2725, 2746]}, {"key": "systems-and-services", "type": "clause", "offset": [2759, 2779]}, {"key": "to-ensure", "type": "clause", "offset": [2798, 2807]}, {"key": "required-availability", "type": "clause", "offset": [2858, 2879]}, {"key": "system-design", "type": "clause", "offset": [3009, 3022]}, {"key": "management-personnel", "type": "clause", "offset": [3100, 3120]}, {"key": "availability-service-levels", "type": "clause", "offset": [3287, 3314]}, {"key": "measurement-tools", "type": "clause", "offset": [3427, 3444]}, {"key": "technology-advancements", "type": "clause", "offset": [3501, 3524]}, {"key": "best-practices", "type": "clause", "offset": [3532, 3546]}, {"key": "related-to", "type": "clause", "offset": [3547, 3557]}, {"key": "service-areas", "type": "definition", "offset": [3706, 3719]}, {"key": "third-parties", "type": "clause", "offset": [3742, 3755]}, {"key": "internet-service-providers", "type": "clause", "offset": [3780, 3806]}, {"key": "infrastructure-service-providers", "type": "definition", "offset": [3808, 3840]}, {"key": "review-sessions", "type": "clause", "offset": [3900, 3915]}, {"key": "party-service-providers", "type": "clause", "offset": [4015, 4038]}, {"key": "information-on", "type": "clause", "offset": [4049, 4063]}, {"key": "service-availability", "type": "clause", "offset": [4079, 4099]}, {"key": "availability-measures", "type": "clause", "offset": [4209, 4230]}, {"key": "assistance-to", "type": "clause", "offset": [4405, 4418]}], "snippet": "The activities of the Availability management process include:\na. Analysis of application portfolio management, incidents and capacity to inform Availability requirements\nb. Determining business unit Availability Requirements for a new or enhanced Service and formulating the Availability and recovery design criteria for the existing application services so that such Services are designed to deliver the appropriate levels of Availability\nc. Determining the critical business functions and impact arising from IT component failure. Where appropriate, reviewing the Availability design criteria to provide additional resilience to prevent or minimize impact to STC Customer\u2019s business.\nd. Identifying opportunities to optimize the Availability of the Applications to deliver cost effective improvements that deliver tangible business benefits\ne. Defining the targets for Availability, Reliability and Maintainability for the IT software components that underpin the application services to enable these to be documented and agreed within Service Levels, and contracts\nf. Establishing measures and reporting of Availability, Reliability, and Maintainability, that reflects the STC Customer\u2019s business and IT support organization perspectives\ng. Monitoring and trend analysis of the Availability, Reliability and Maintainability of IT systems and components\nh. Reviewing the application services, system, and component Availability, identifying unacceptable levels, and taking appropriate corrective actions to address Availability shortfalls\ni. Investigating the underlying reasons for unacceptable Availability\nj. Producing and maintaining a forward-looking Availability plan, which prioritizes and plans overall Availability improvements aimed at improving the overall Availability of the Project Services and Application components so that existing and future business Availability requirements can be met\nk. Providing a range of IT Availability reporting to the MSI so that agreed levels of Availability, Reliability and Maintainability are measured and monitored on an ongoing basis The following list identifies the Availability Management Services that Service Provider will perform.\n1. Recommend Availability management policies and procedures and appropriate Availability management tools and methods that support STC Customer\u2019s Availability management support requirements.\n2. Assist with the implementation of agreed-upon Availability management policies and procedures.\n3. Adhere to Availability management policies and procedures.\n4. Provide STC Customer-authorized staff, MSI and designated personnel unrestricted read access to all current and historical Availability knowledge base records.\n5. Participate in requirements analysis when new IT systems and services are being defined to ensure that Project Services are designed to deliver the required availability levels.\n6. Assist in the creation of Availability and recovery design criteria to be applied to new or enhanced Applications and system design.\n7. Coordinate with the STC Customer IT service support and service delivery management personnel to research, review, and assess Availability issues and optimization opportunities.\n8. Recommend appropriate tools and practices to measure and report on agreed-upon Availability Service Levels for new and enhanced Applications.\n9. Assist MSI with the implementation of approved Availability Service Level measurement tools and practices.\n10. Monitor and maintain an awareness of technology advancements and IT best practices related to Availability optimization and periodically provide updates to STC Customer.\n11. Assist in the coordination of Availability management across all IT service areas with STC Customer and third parties (e.g., public carriers, Internet Service Providers, Infrastructure Service Providers, etc.).\n12. Assist STC Customer in Availability assessment review sessions and provide cost-justified improvement recommendations.\n13. Coordinate with STC Customer and third-party Service Providers to gather information on IT systems and service Availability issues and trends to be used for trend analysis.\n14. Review Full-Service Applications and Interfaces against Availability measures and take appropriate corrective actions to address Availability shortfalls, if such shortfalls are related to such Applications\u2019 or Interfaces\u2019 code.\n15. Provide support and assistance to STC Customer and MSI in investigating the underlying reasons for unacceptable Availability.", "hash": "e9af46fb294cd932340cdd752c90d40e", "id": 2}, {"samples": [{"hash": "dyxoEiMrZyC", "uri": "/contracts/dyxoEiMrZyC#availability-management", "label": "Trustbuilder Terms and Conditions", "score": 25.2258726899, "published": true}, {"hash": "aqUnZ7SKuGd", "uri": "/contracts/aqUnZ7SKuGd#availability-management", "label": "Trustbuilder Terms and Conditions", "score": 24.8548939083, "published": true}], "size": 2, "snippet_links": [{"key": "purpose-of-the", "type": "clause", "offset": [4, 18]}, {"key": "management-practice", "type": "definition", "offset": [32, 51]}, {"key": "to-ensure", "type": "clause", "offset": [55, 64]}, {"key": "of-customers", "type": "clause", "offset": [135, 147]}, {"key": "authorised-users", "type": "definition", "offset": [156, 172]}, {"key": "activities-include", "type": "clause", "offset": [206, 224]}, {"key": "required-availability", "type": "clause", "offset": [351, 372]}, {"key": "services-and", "type": "clause", "offset": [397, 409]}, {"key": "data-required", "type": "clause", "offset": [445, 458]}], "snippet": "The purpose of the availability management practice is to ensure that services deliver agreed levels of availability to meet the needs of Customers and the Authorised Users. \ud83e\udc26 The TrustBuilder availability activities include: - Negotiating and agreeing achievable targets for availability; - Designing infrastructure and applications that can deliver required availability levels; - Ensuring that services and components are able to collect the data required to measure availability; - Monitoring, analysing, and reporting on availability; - Planning availability improvements.", "hash": "f9b078c08c558307c64b31658d85d5be", "id": 3}, {"samples": [{"hash": "lT9sHpxlf2u", "uri": "/contracts/lT9sHpxlf2u#availability-management", "label": "Master Services Agreement (Aci Worldwide, Inc.)", "score": 21.3230663929, "published": true}, {"hash": "7sb96b7p5jH", "uri": "/contracts/7sb96b7p5jH#availability-management", "label": "Master Services Agreement (Aci Worldwide, Inc.)", "score": 21.0, "published": true}], "size": 2, "snippet_links": [{"key": "the-process", "type": "clause", "offset": [30, 41]}, {"key": "procedures-required", "type": "clause", "offset": [106, 125]}, {"key": "the-services", "type": "definition", "offset": [136, 148]}, {"key": "availability-of", "type": "clause", "offset": [164, 179]}, {"key": "software-components", "type": "definition", "offset": [236, 255]}, {"key": "it-infrastructure", "type": "definition", "offset": [319, 336]}, {"key": "supporting-organization", "type": "definition", "offset": [345, 368]}, {"key": "level-of-service", "type": "definition", "offset": [411, 427]}], "snippet": "a. Availability Management is the process for coordinating the appropriate skills, information, tools and procedures required to manage the Services including, the availability of interactive networks and their supporting Equipment and software components. Availability Management will optimize the capability of ACI\u2019s IT infrastructure and the supporting organization to deliver a cost-effective and sustained level of Service.", "hash": "4c619563ca2d3f922a3887d460763ebe", "id": 4}, {"samples": [{"hash": "gRITXQAz1br", "uri": "/contracts/gRITXQAz1br#availability-management", "label": "Service Level Agreement", "score": 30.2642675923, "published": true}], "size": 2, "snippet_links": [{"key": "in-advance", "type": "clause", "offset": [54, 64]}, {"key": "scheduled-maintenance", "type": "definition", "offset": [79, 100]}, {"key": "disruption-of-the-service", "type": "clause", "offset": [122, 147]}], "snippet": "When possible, the CSM will notify Customer nine days in advance of any Orange Scheduled Maintenance that may result in a disruption of the Service.", "hash": "b6775ae449a1966dcb10ea4b602b7f97", "id": 5}, {"samples": [{"hash": "hqdlvjzFy4", "uri": "/contracts/hqdlvjzFy4#availability-management", "label": "Master Services Agreement", "score": 31.340862423, "published": true}], "size": 2, "snippet_links": [{"key": "purpose-of-the", "type": "clause", "offset": [4, 18]}, {"key": "the-design", "type": "clause", "offset": [68, 78]}, {"key": "management-of", "type": "clause", "offset": [112, 125]}, {"key": "services-and", "type": "clause", "offset": [147, 159]}, {"key": "business-process", "type": "definition", "offset": [166, 182]}, {"key": "requirements-for", "type": "clause", "offset": [224, 240]}, {"key": "health-net", "type": "definition", "offset": [353, 363]}, {"key": "and-health", "type": "clause", "offset": [365, 375]}, {"key": "availability-requirements", "type": "definition", "offset": [464, 489]}, {"key": "management-organization", "type": "clause", "offset": [533, 556]}, {"key": "business-continuity-management", "type": "clause", "offset": [629, 659]}, {"key": "business-information", "type": "clause", "offset": [737, 757]}, {"key": "increases-and-decreases", "type": "clause", "offset": [785, 808]}, {"key": "availability-of", "type": "clause", "offset": [812, 827]}, {"key": "service-levels", "type": "definition", "offset": [900, 914]}, {"key": "where-permitted", "type": "clause", "offset": [946, 961]}, {"key": "technically-feasible", "type": "clause", "offset": [966, 986]}, {"key": "trend-analysis", "type": "clause", "offset": [1003, 1017]}, {"key": "unscheduled-downtime", "type": "clause", "offset": [1070, 1090]}, {"key": "root-cause-analysis", "type": "definition", "offset": [1109, 1128]}, {"key": "problem-management", "type": "clause", "offset": [1173, 1191]}, {"key": "planning-and-implementation", "type": "clause", "offset": [1280, 1307]}, {"key": "the-applicable", "type": "clause", "offset": [1311, 1325]}, {"key": "schedule-a", "type": "clause", "offset": [1336, 1346]}, {"key": "to-ensure", "type": "clause", "offset": [1458, 1467]}], "snippet": "The purpose of the \u201cAvailability Management\u201d process is to consider the design, implementation, measurement and management of those aspects of the Services and other business process may impact availability so that business requirements for availability are consistently met. Supplier\u2019s responsibilities for Availability Management will be to work with Health Net (and Health Net\u2019s infrastructure provider(s)) and include the following activities:\n(i) determining availability requirements by collecting input from the Service Level management organization;\n(ii) determining vital business Functions by collecting input from the business continuity management organization;\n(iii) analyzing the impact on the business (where the relevant business information is available) of potential increases and decreases in availability of the business process;\n(iv) defining availability objectives (other than Service Levels);\n(v) monitoring availability (where permitted and technically feasible) and conducting trend analysis;\n(vi) reviewing and auditing scheduled downtime and unscheduled downtime;\n(vii) conducting root cause analysis of low availability in conjunction with the Problem management organization;\n(viii) developing and maintaining an \u201cAvailability Plan\u201d;\n(ix) supporting planning and implementation of the applicable TBCP; and Schedule A A-20 Health Net / Cognizant Confidential\n(x) working closely with Health Net\u2019s processing platforms partner(s) to ensure the on-going availability of the In-Scope Applications and suitability of all the environments.", "hash": "ed88ce3aa7266668eb5a35d4f4c0e901", "id": 6}, {"samples": [{"hash": "317ErG3s24w", "uri": "/contracts/317ErG3s24w#availability-management", "label": "Master Professional Services Agreement (Virtusa Corp)", "score": 25.3798767967, "published": true}], "size": 1, "snippet_links": [{"key": "vendor-shall", "type": "clause", "offset": [0, 12]}, {"key": "responsible-for", "type": "clause", "offset": [16, 31]}, {"key": "availability-of", "type": "clause", "offset": [95, 110]}], "snippet": "Vendor shall be responsible for proactively analyzing, measuring and attempting to improve the availability of applications under their control.", "hash": "24c06ed4ca6ac0d90c26ac40d8571735", "id": 7}, {"samples": [{"hash": "d3lTTsCen2j", "uri": "/contracts/d3lTTsCen2j#availability-management", "label": "Data Center Services Multisourcing Service Integrator Master Services Agreement", "score": 22.2087611225, "published": true}], "size": 1, "snippet_links": [], "snippet": "\uf0a7 Enterprise Availability Plans will be delivered annually instead of quarterly. \uf0a7 DCS Customer Availability Plans will be delivered annually instead of quarterly.", "hash": "57343e959f8aedfa9369b6c62f4b4dbe", "id": 8}, {"samples": [{"hash": "fVVsZLTTASG", "uri": "/contracts/fVVsZLTTASG#availability-management", "label": "Managed Operations Services Agreement (Franklin Resources Inc)", "score": 18.0, "published": true}], "size": 1, "snippet_links": [{"key": "ibm-will", "type": "clause", "offset": [3, 11]}, {"key": "availability-requirements", "type": "definition", "offset": [55, 80]}, {"key": "processes-and-procedures", "type": "clause", "offset": [115, 139]}, {"key": "during-the-transition-period", "type": "clause", "offset": [173, 201]}, {"key": "hours-of-operation", "type": "clause", "offset": [214, 232]}, {"key": "maintenance-windows", "type": "clause", "offset": [234, 253]}, {"key": "pertinent-information", "type": "clause", "offset": [266, 287]}, {"key": "in-accordance-with", "type": "definition", "offset": [367, 385]}, {"key": "equipment-manufacturer", "type": "definition", "offset": [390, 412]}, {"key": "mutually-agreed", "type": "clause", "offset": [446, 461]}, {"key": "recovery-of-data", "type": "clause", "offset": [511, 527]}, {"key": "types-of", "type": "clause", "offset": [557, 565]}, {"key": "equipment-malfunction", "type": "clause", "offset": [583, 604]}, {"key": "temporary-power", "type": "clause", "offset": [606, 621]}, {"key": "provide-the", "type": "clause", "offset": [664, 675]}, {"key": "focal-point", "type": "definition", "offset": [685, 696]}, {"key": "system-availability", "type": "definition", "offset": [727, 746]}], "snippet": "a. IBM will:\n1. assist Franklin in defining Franklin's availability requirements;\n2. establish backup and recovery processes and procedures;\n3. develop an availability plan during the Transition Period, to include hours of operation, maintenance windows and related pertinent information;\n4. track, analyze and report on availability;\n5. provide hardware maintenance in accordance with the equipment manufacturer's specifications or as otherwise mutually agreed;\n6. develop and maintain a plan that enables the recovery of data due to unplanned operational types of failures such as equipment malfunction, temporary power disturbances and abnormal termination;\n7. provide the Franklin Focal Point with procedures for measuring system availability;", "hash": "ed4802c2425f6aa2144f77ac4945c7d1", "id": 9}, {"samples": [{"hash": "i6UYUYUjYWW", "uri": "/contracts/i6UYUYUjYWW#availability-management", "label": "Managed Operations Services Agreement (Franklin Resources Inc)", "score": 18.0, "published": true}], "size": 1, "snippet_links": [{"key": "ibm-will", "type": "clause", "offset": [3, 11]}, {"key": "availability-requirements", "type": "definition", "offset": [55, 80]}, {"key": "processes-and-procedures", "type": "clause", "offset": [115, 139]}], "snippet": "a. IBM will:\n1. assist Franklin in defining Franklin's availability requirements;\n2. establish backup and recovery processes and procedures;", "hash": "0e2995d90de3994ee4ff179fa2918570", "id": 10}], "next_curs": "CmASWmoVc35sYXdpbnNpZGVyY29udHJhY3RzcjwLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IiBhdmFpbGFiaWxpdHktbWFuYWdlbWVudCMwMDAwMDAwYQyiAQJlbhgAIAA=", "clause": {"children": [["reporting", "REPORTING"], ["general", "General"], ["requirements", "Requirements"]], "size": 30, "title": "Availability Management", "parents": [["general", "GENERAL"], ["standard-service-features", "Standard Service Features"], ["service-management-conditions-for-use", "Service Management Conditions For Use"], ["services-management", "SERVICES MANAGEMENT"], ["processes", "Processes"]], "id": "availability-management", "related": [["utilization-management", "Utilization Management", "Utilization Management"], ["availability-control", "Availability Control", "Availability Control"], ["service-availability", "Service Availability", "Service Availability"], ["vulnerability-management", "Vulnerability Management", "Vulnerability Management"], ["epp-service-availability", "EPP service availability", "EPP service availability"]], "related_snippets": [], "updated": "2025-07-07T12:35:11+00:00", "also_ask": [], "drafting_tip": "", "explanation": "The Availability Management clause defines the requirements and standards for ensuring that a service or system remains accessible and operational as agreed upon by the parties. It typically outlines specific uptime targets, maintenance schedules, and procedures for handling outages or disruptions. By setting clear expectations for service availability, this clause helps minimize downtime, ensures reliability, and provides a framework for addressing performance issues."}, "json": true, "cursor": ""}}