{"component": "clause", "props": {"groups": [{"size": 2, "snippet_links": [{"key": "to-provide", "type": "definition", "offset": [11, 21]}], "samples": [{"hash": "ft8orZ4tLWk", "uri": "/contracts/ft8orZ4tLWk#network-engineering", "label": "Network Services Agreement (AOL Inc.)", "score": 21.0, "published": true}, {"hash": "Xwpb7TH46r", "uri": "/contracts/Xwpb7TH46r#network-engineering", "label": "Network Services Agreement (AOL Inc.)", "score": 21.0, "published": true}], "snippet": "MCI agrees to provide network engineering to address operational and long-term planning issues.", "hash": "1e181341dab701634cfe195386bfefaa", "id": 2}, {"size": 4, "snippet_links": [{"key": "to-provide", "type": "definition", "offset": [14, 24]}], "samples": [{"hash": "dyWh2TirTYN", "uri": "/contracts/dyWh2TirTYN#network-engineering", "label": "Network Services Agreement (Genuity Inc)", "score": 18.0, "published": true}, {"hash": "9hakvlCk5nU", "uri": "/contracts/9hakvlCk5nU#network-engineering", "label": "Network Services Agreement (Genuity Inc)", "score": 18.0, "published": true}, {"hash": "6JpkoPC96xa", "uri": "/contracts/6JpkoPC96xa#network-engineering", "label": "Network Services Agreement (Genuity Inc)", "score": 18.0, "published": true}], "snippet": "Vendor agrees to provide network engineering to address operational and long-term planning issues.", "hash": "7a58d4975723851acf6a5596ca96031b", "id": 1}, {"size": 2, "snippet_links": [{"key": "confidential-treatment-requested", "type": "definition", "offset": [0, 32]}, {"key": "vendor-will-provide", "type": "clause", "offset": [33, 52]}, {"key": "technical-issues", "type": "clause", "offset": [94, 110]}, {"key": "vendor-network", "type": "definition", "offset": [200, 214]}, {"key": "responsible-for", "type": "clause", "offset": [231, 246]}, {"key": "network-design", "type": "clause", "offset": [258, 272]}, {"key": "network-expansion", "type": "clause", "offset": [283, 300]}, {"key": "technical-procedures", "type": "clause", "offset": [314, 334]}, {"key": "resolving-problems", "type": "clause", "offset": [336, 354]}, {"key": "performance-issues", "type": "definition", "offset": [421, 439]}, {"key": "cost-reduction", "type": "definition", "offset": [451, 465]}, {"key": "continuous-process-improvement", "type": "clause", "offset": [498, 528]}], "samples": [{"hash": "9hakvlCk5nU", "uri": "/contracts/9hakvlCk5nU#network-engineering", "label": "Network Services Agreement (Genuity Inc)", "score": 18.0, "published": true}, {"hash": "4XXz1vXMDq4", "uri": "/contracts/4XXz1vXMDq4#network-engineering", "label": "Network Services Agreement (Genuity Inc)", "score": 18.0, "published": true}], "snippet": "CONFIDENTIAL TREATMENT REQUESTED Vendor will provide network engineering expertise to address technical issues that arise during the deployment of the Broadband Backhaul Services and operation of the Vendor Network. Vendor will be responsible for performing network design; planning network expansion; documenting technical procedures; resolving problems escalated by the NOC; addressing architecture, implementation and performance issues; providing cost reduction recommendations; and performing continuous process improvement.", "hash": "ded50d81fc267fa55802a1a6800386e9", "id": 3}, {"size": 2, "snippet_links": [{"key": "traffic-engineering", "type": "clause", "offset": [0, 19]}, {"key": "interconnection-to", "type": "clause", "offset": [97, 115]}, {"key": "the-\u2587", "type": "clause", "offset": [116, 121]}, {"key": "operator-services", "type": "clause", "offset": [139, 156]}, {"key": "data-services", "type": "clause", "offset": [247, 260]}, {"key": "within-thirty", "type": "clause", "offset": [371, 384]}, {"key": "the-effective-date", "type": "clause", "offset": [398, 416]}, {"key": "a-schedule", "type": "clause", "offset": [471, 481]}, {"key": "services-in-the", "type": "clause", "offset": [553, 568]}, {"key": "the-exhibit", "type": "clause", "offset": [613, 624]}, {"key": "supply-agreement", "type": "definition", "offset": [666, 682]}, {"key": "execution-version", "type": "clause", "offset": [693, 710]}, {"key": "payment-to", "type": "clause", "offset": [872, 882]}, {"key": "amount-for-the-service", "type": "clause", "offset": [1014, 1036]}, {"key": "a-subcontractor", "type": "definition", "offset": [1085, 1100]}], "samples": [{"hash": "6WTfx7ThtwC", "uri": "/contracts/6WTfx7ThtwC#network-engineering", "label": "Supply Agreement (Winstar Communications Inc)", "score": 18.0, "published": true}, {"hash": "5kEEUIEjZGb", "uri": "/contracts/5kEEUIEjZGb#network-engineering", "label": "Supply Agreement (Winstar Communications Inc)", "score": 18.0, "published": true}], "snippet": "Traffic Engineering will be migrated as set forth below. This shall include sizing of trunks for interconnection to the \u2587\u2587\u2587, \u2587\u2587\u2587 services, operator services, SS7 and AIN and interconnection of hub-to-hub and hub-to-switch inter-city connectivity, data services, etc. For new cities (i.e., cities planned for implementation in 1999), Lucent will assume the responsibility within thirty (30) days of the Effective Date. For existing cities, Lucent will develop and present a schedule within sixty (60) days of the Effective Date, with assumption of these Services in the first city within seventy-five (75) days of the Exhibit A-4 to the Confidential - Winstar/Lucent Supply Agreement - A-4-2 - Execution Version Effective Date. If Lucent cannot meet this responsibility within the timeframes specified, it shall subcontract the responsibility to WinStar. In such case, the payment to WinStar for this responsibility shall be the amount set forth in Exhibit C-5, prorated monthly (i.e., WinStar will pay Lucent that amount for the Service and Lucent will pay WinStar that same amount as a subcontractor).", "hash": "9045e50a5954b218703f965a8267bd46", "id": 4}, {"size": 2, "snippet_links": [{"key": "to-provide", "type": "definition", "offset": [19, 29]}, {"key": "network-design", "type": "clause", "offset": [146, 160]}, {"key": "in-order-to", "type": "clause", "offset": [161, 172]}, {"key": "the-price", "type": "clause", "offset": [226, 235]}, {"key": "transmission-system", "type": "clause", "offset": [255, 274]}, {"key": "to-establish", "type": "clause", "offset": [299, 311]}, {"key": "last-resort", "type": "definition", "offset": [323, 334]}, {"key": "the-facilities", "type": "clause", "offset": [378, 392]}, {"key": "equipment-and-software", "type": "clause", "offset": [394, 416]}, {"key": "the-services", "type": "definition", "offset": [433, 445]}, {"key": "in-accordance-with", "type": "definition", "offset": [467, 485]}, {"key": "vendor-support", "type": "clause", "offset": [525, 539]}, {"key": "release-information", "type": "clause", "offset": [540, 559]}, {"key": "maintaining-equipment", "type": "clause", "offset": [576, 597]}, {"key": "good-operating-condition", "type": "definition", "offset": [601, 625]}, {"key": "preventive-maintenance", "type": "clause", "offset": [655, 677]}, {"key": "the-applicable", "type": "clause", "offset": [734, 748]}, {"key": "equipment-manufacturer", "type": "definition", "offset": [749, 771]}, {"key": "software-maintenance", "type": "definition", "offset": [810, 830]}, {"key": "software-vendor", "type": "clause", "offset": [916, 931]}, {"key": "by-court-order", "type": "clause", "offset": [1064, 1078]}, {"key": "applicable-law", "type": "definition", "offset": [1082, 1096]}, {"key": "vendor-shall-provide", "type": "clause", "offset": [1158, 1178]}, {"key": "notice-of-the", "type": "clause", "offset": [1213, 1226]}, {"key": "scope-and", "type": "clause", "offset": [1245, 1254]}, {"key": "new-interconnection-points", "type": "clause", "offset": [1479, 1505]}, {"key": "as-required", "type": "clause", "offset": [1506, 1517]}, {"key": "been-agreed", "type": "clause", "offset": [1616, 1627]}, {"key": "in-advance", "type": "clause", "offset": [1637, 1647]}, {"key": "according-to", "type": "definition", "offset": [1687, 1699]}, {"key": "distribution-of", "type": "clause", "offset": [1717, 1732]}], "samples": [{"hash": "jxZwPL9IChC", "uri": "/contracts/jxZwPL9IChC#network-engineering", "label": "Telecommunications Services Agreement (America Online Latin America Inc)", "score": 18.0, "published": true}, {"hash": "aSvvLnkMNiK", "uri": "/contracts/aSvvLnkMNiK#network-engineering", "label": "Telecommunications Services Agreement (America Online Latin America Inc)", "score": 18.0, "published": true}], "snippet": "2.1. Vendor agrees to provide network engineering to address operational and long-term planning issues.\n2.2. Vendor shall continue to improve the network design in order to reduce risks to AOL, improve robustness, and enhance the price/performance of the transmission system. AOL shall be permitted to establish a route of last resort on the network.\n2.3. Vendor shall maintain the facilities, equipment and software used to provide the Services so that they operate in accordance with their specifications (e.g., applicable vendor support release information), including (a) maintaining equipment in good operating condition, (b) undertaking repairs and preventive maintenance on equipment, including at a minimum in accordance with the applicable equipment manufacturer's recommendations, and (c) performing software maintenance, including at a minimum in accordance with the applicable software documentation and software vendor's recommendations.\n2.4. Vendor agrees not to restrict traffic to and from AOL unless requested to do so by AOL or required to do so by court order or applicable law. Before restricting traffic as permitted under this Section, Vendor shall provide AOL with reasonable prior written notice of the timing, duration, scope and reasons for such restriction.\n2.5. Vendor shall manage the backbone and interconnection points with other Internet providers and customers to minimize loss and delay of AOL traffic. Such management shall include creation of new interconnection points as required.\n2.6. Vendor shall provide the Services via POPs whose geographical distribution and location has been agreed with AOL in advance and which, at a minimum, are dispersed according to the geographical distribution of the population in each particular territory.", "hash": "e74691269b4d1e51c98703cabf8e1670", "id": 5}, {"size": 2, "snippet_links": [{"key": "urban-area", "type": "definition", "offset": [18, 28]}, {"key": "business-case", "type": "clause", "offset": [48, 61]}, {"key": "based-on", "type": "definition", "offset": [62, 70]}, {"key": "the-municipality", "type": "definition", "offset": [79, 95]}, {"key": "city-council", "type": "clause", "offset": [96, 108]}, {"key": "complete-address", "type": "clause", "offset": [377, 393]}, {"key": "homes-passed", "type": "definition", "offset": [442, 454]}, {"key": "detailed-design", "type": "definition", "offset": [466, 481]}, {"key": "types-of", "type": "clause", "offset": [532, 540]}, {"key": "permits-and-approvals", "type": "clause", "offset": [541, 562]}, {"key": "public-domain", "type": "definition", "offset": [578, 591]}, {"key": "to-ensure", "type": "clause", "offset": [702, 711]}, {"key": "responsibility-of-company", "type": "clause", "offset": [775, 800]}, {"key": "contact-details", "type": "clause", "offset": [944, 959]}, {"key": "figure-7", "type": "clause", "offset": [966, 974]}, {"key": "in-order-to", "type": "clause", "offset": [1025, 1036]}, {"key": "in-parallel", "type": "definition", "offset": [1089, 1100]}], "samples": [{"hash": "kDFVofqm6E0", "uri": "/contracts/kDFVofqm6E0#network-engineering", "label": "Service Description & Working Level Agreement", "score": 34.2111167908, "published": true}, {"hash": "bSGyari1QXQ", "uri": "/contracts/bSGyari1QXQ#network-engineering", "label": "Service Description & Working Level Agreement", "score": 25.8706359863, "published": true}], "snippet": "As soon as a city/urban area reaches a positive business case based on HLD and the municipality/city council orientation comes back favorable, the engineering phase starts. For the most efficient design, an advanced alignment with the municipality council on POP locations is supposed to take place. In the Engineering period, a street- and infrastructure survey result in the complete address database with all premises to be covered in the Homes Passed network. A Detailed Design (DD) is made for each Fiberzone and the different types of permits and approvals are requested (public domain, fa\u00e7ade approval, syndic alignment). Regarding alignment with syndics, this is initiated as early as possible to ensure Homes Passed network is available in the entire MDU. It is the responsibility of Company to ensure agreement is reached regarding HP network. However, Operator can always help with existing syndic relationships (e.g. syndic names & contact details). See Figure 7 for a schematic overview of the roll-out process. In order to minimize lead- time, several activities are planned in parallel. Figure 7: Schematic overview of the roll-out process", "hash": "c297025dd06391730a471eaf0613d728", "id": 6}, {"size": 2, "snippet_links": [{"key": "will-provide", "type": "clause", "offset": [13, 25]}, {"key": "engineering-functions", "type": "clause", "offset": [45, 66]}, {"key": "as-required", "type": "clause", "offset": [67, 78]}, {"key": "business-requirements", "type": "clause", "offset": [91, 112]}, {"key": "implementation-planning", "type": "clause", "offset": [142, 165]}, {"key": "configuration-management", "type": "clause", "offset": [196, 220]}, {"key": "inclusive-of", "type": "clause", "offset": [297, 309]}, {"key": "and-equipment", "type": "clause", "offset": [375, 388]}, {"key": "site-surveys", "type": "definition", "offset": [401, 413]}, {"key": "for-equipment", "type": "clause", "offset": [439, 452]}, {"key": "engineering-services", "type": "definition", "offset": [485, 505]}, {"key": "relate-to", "type": "definition", "offset": [514, 523]}, {"key": "quality-of-service", "type": "definition", "offset": [547, 565]}, {"key": "projected-traffic", "type": "definition", "offset": [567, 584]}, {"key": "business-process", "type": "definition", "offset": [595, 611]}, {"key": "administrative-issues", "type": "clause", "offset": [625, 646]}, {"key": "management-process", "type": "clause", "offset": [652, 670]}, {"key": "information-on", "type": "clause", "offset": [753, 767]}, {"key": "omitted-and-filed-separately-with-the-commission", "type": "clause", "offset": [787, 835]}, {"key": "confidential-treatment", "type": "clause", "offset": [837, 859]}, {"key": "with-respect-to", "type": "clause", "offset": [879, 894]}, {"key": "to-provide", "type": "definition", "offset": [949, 959]}, {"key": "the-total", "type": "clause", "offset": [1044, 1053]}, {"key": "service-provided", "type": "definition", "offset": [1082, 1098]}, {"key": "agreement-for", "type": "clause", "offset": [1109, 1122]}, {"key": "configuration-requirements", "type": "clause", "offset": [1238, 1264]}, {"key": "third-party-vendors", "type": "definition", "offset": [1294, 1313]}, {"key": "effective-communication", "type": "clause", "offset": [1447, 1470]}, {"key": "implementation-of-the-services", "type": "clause", "offset": [1475, 1505]}, {"key": "technical-resources", "type": "definition", "offset": [1521, 1540]}, {"key": "development-of-a", "type": "clause", "offset": [1556, 1572]}, {"key": "strategic-direction", "type": "definition", "offset": [1589, 1608]}, {"key": "the-scope-of-the-services", "type": "clause", "offset": [1632, 1657]}, {"key": "consultative-services", "type": "clause", "offset": [1702, 1723]}, {"key": "authorized-requests", "type": "clause", "offset": [1739, 1758]}, {"key": "engineering-support", "type": "definition", "offset": [1810, 1829]}, {"key": "design-criteria-and-standards", "type": "clause", "offset": [1848, 1877]}, {"key": "monitoring-tools", "type": "definition", "offset": [1936, 1952]}, {"key": "adequate-capacity", "type": "definition", "offset": [1956, 1973]}, {"key": "network-devices", "type": "definition", "offset": [1992, 2007]}, {"key": "activities-required", "type": "clause", "offset": [2086, 2105]}, {"key": "to-continuously", "type": "clause", "offset": [2106, 2121]}, {"key": "the-principal", "type": "clause", "offset": [2131, 2144]}, {"key": "performance-indicators", "type": "definition", "offset": [2145, 2167]}, {"key": "network-operation", "type": "clause", "offset": [2171, 2188]}, {"key": "to-establish", "type": "clause", "offset": [2277, 2289]}, {"key": "managing-the-network", "type": "clause", "offset": [2327, 2347]}, {"key": "in-the-event", "type": "clause", "offset": [2398, 2410]}, {"key": "leadership-role", "type": "definition", "offset": [2627, 2642]}, {"key": "products-and-or-services", "type": "definition", "offset": [2694, 2718]}, {"key": "unless-otherwise-agreed", "type": "definition", "offset": [2839, 2862]}, {"key": "in-writing", "type": "clause", "offset": [2863, 2873]}, {"key": "terms-of", "type": "definition", "offset": [2918, 2926]}, {"key": "cost-effectiveness", "type": "definition", "offset": [2927, 2945]}, {"key": "to-the-extent", "type": "clause", "offset": [2961, 2974]}, {"key": "ability-to", "type": "clause", "offset": [3024, 3034]}, {"key": "the-service-levels", "type": "clause", "offset": [3040, 3058]}, {"key": "right-to-approve", "type": "clause", "offset": [3172, 3188]}, {"key": "changes-to-the-network", "type": "clause", "offset": [3193, 3215]}, {"key": "information-page", "type": "definition", "offset": [3440, 3456]}, {"key": "network-performance", "type": "definition", "offset": [3504, 3523]}, {"key": "comply-with-the", "type": "clause", "offset": [3564, 3579]}, {"key": "management-responsibilities", "type": "definition", "offset": [3693, 3720]}, {"key": "reviewing-and-reporting", "type": "clause", "offset": [3734, 3757]}, {"key": "to-determine", "type": "clause", "offset": [3821, 3833]}, {"key": "network-usage", "type": "clause", "offset": [3894, 3907]}, {"key": "verifying-performance", "type": "clause", "offset": [3970, 3991]}, {"key": "decision-making", "type": "definition", "offset": [4142, 4157]}, {"key": "network-changes", "type": "clause", "offset": [4174, 4189]}, {"key": "performance-data", "type": "definition", "offset": [4205, 4221]}, {"key": "the-current", "type": "clause", "offset": [4252, 4263]}, {"key": "applicable-to", "type": "clause", "offset": [4297, 4310]}, {"key": "the-performance", "type": "clause", "offset": [4342, 4357]}, {"key": "to-control", "type": "definition", "offset": [4390, 4400]}, {"key": "network-capacity", "type": "clause", "offset": [4501, 4517]}, {"key": "service-controls", "type": "definition", "offset": [4533, 4549]}, {"key": "user-requirements", "type": "clause", "offset": [4586, 4603]}, {"key": "change-management-procedures", "type": "definition", "offset": [4621, 4649]}, {"key": "section-5", "type": "definition", "offset": [4663, 4672]}, {"key": "cross-functional-services", "type": "definition", "offset": [4709, 4734]}, {"key": "statement-of-work", "type": "definition", "offset": [4735, 4752]}, {"key": "the-data", "type": "clause", "offset": [4761, 4769]}, {"key": "management-activities", "type": "clause", "offset": [4800, 4821]}, {"key": "to-develop", "type": "definition", "offset": [4832, 4842]}, {"key": "respond-to", "type": "definition", "offset": [4999, 5009]}, {"key": "operational-requirements", "type": "clause", "offset": [5016, 5040]}, {"key": "subject-to-the", "type": "clause", "offset": [5084, 5098]}, {"key": "physical-capacity", "type": "definition", "offset": [5347, 5364]}, {"key": "participating-in", "type": "definition", "offset": [5727, 5743]}, {"key": "capacity-planning", "type": "clause", "offset": [5752, 5769]}, {"key": "based-on", "type": "definition", "offset": [5837, 5845]}, {"key": "performance-monitoring", "type": "definition", "offset": [5867, 5889]}, {"key": "network-loads", "type": "clause", "offset": [5914, 5927]}, {"key": "changes-in", "type": "clause", "offset": [6043, 6053]}, {"key": "operational-needs", "type": "clause", "offset": [6093, 6110]}, {"key": "improve-performance", "type": "clause", "offset": [6169, 6188]}, {"key": "in-anticipation-of", "type": "definition", "offset": [6189, 6207]}, {"key": "performance-improvement", "type": "clause", "offset": [6237, 6260]}, {"key": "implementation-plans", "type": "clause", "offset": [6290, 6310]}, {"key": "approved-business", "type": "definition", "offset": [6329, 6346]}], "samples": [{"hash": "5qRCQRVvSWX", "uri": "/contracts/5qRCQRVvSWX#network-engineering", "label": "Master Services Agreement (Gap Inc)", "score": 21.0, "published": true}], "snippet": "(a) Supplier will provide Network design and engineering functions as required to meet Gap business requirements, including planning; design; implementation planning; implementation; capacity and configuration management; optimization; efficiency tuning; Third Party Vendor coordination; ordering inclusive of preparing all required Gap Documentation and installing circuits and Equipment; conducting site surveys; and performing upgrades for Equipment.\n(b) Supplier will also provide engineering services as they relate to topology; performance; quality of service; projected traffic patterns; business process and drivers; administrative issues; and management process activities including Software as may be needed to perform the Services. * Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions.\n(c) Supplier\u2019s responsibilities to provide such Network engineering functions include the following:\n(1) Monitoring and tuning the total Network within the scope of Service provided under the Agreement for efficiency and cost-effectiveness on an \u201cend-to-end\u201d basis; all bandwidth; developing, maintaining and adhering to configuration requirements; and coordinating with other Third Party Vendors. With respect to these requirements, Supplier is expected to work cooperatively with Third Party Vendors and Gap staff to facilitate effective communication and implementation of the services.\n(2) Providing technical resources to support the development of a clear, concise, strategic direction for the Network within the scope of the Services.\n(3) Providing Gap with Network engineering consultative services in response to authorized requests in support of business requirements.\n(4) Providing engineering support in developing the design criteria and standards.\n(5) Implementing and managing performance management and monitoring tools of adequate capacity and scale so that Network devices will be under management as appropriate. This monitoring will encompass those activities required to continuously evaluate the principal performance indicators of Network operation; verify Service Levels; identify actual and potential performance impacting issues; and to establish and report on trends.\n(6) Tuning and managing the Network to meet business requirements and Service Levels. In the event that Supplier does not have the necessary technology or services to meet Gap\u2019s requirements with respect to particular modifications, enhancements or improvements in the services, Supplier will at its expense take a leadership role in assisting Gap in identifying Third Party Vendor products and/or services to accomplish Gap\u2019s objectives.\n(7) Performing, on *, regular optimization analyses. Such analyses will be performed *, unless otherwise agreed in writing. Supplier will also optimize the Network in terms of cost effectiveness and efficiency to the extent possible, but without sacrificing performance or ability to meet the Service Levels. Supplier will hold briefings with Gap to review the optimization levels in greater detail and Gap will have the right to approve any changes to the Network. * Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions. Exhibit A.5 Gap/IBM Confidential and Proprietary Information Page 10 of 45\n(8) Continually tracking and managing Network performance, including *, to the extent required to comply with the Service Levels, and will regularly report on such performance as described below. Supplier\u2019s Network performance management responsibilities include:\n(A) Reviewing and reporting on the utilization and latency of infrastructure and transport to determine appropriate sizing and port speed given the topology of the Network usage patterns.\n(B) Evaluating principal performance indicators and verifying performance against Service Levels.\n(C) Identify actual and potential performance impacting problems in the Network.\n(D) Establishing and reporting on trends for decision making and planning of Network changes.\n(E) Analyzing performance data to evaluate the efficiency of the current design.\n(F) Using modeling where applicable to determine methods of improving the performance of the Network.\n(9) Employing * to control and contain traffic levels and secure sensitive applications and data.\n(10) Balancing deployment of Network capacity and quality of service controls as appropriate to meet business and user requirements.\n(11) Subject to Change Management procedures described in Section 5 (Change Management) of Exhibit A.2 (Cross Functional Services Statement of Work), using the data gathered from its performance management activities set forth to develop recommendations to optimize or improve the performance of the Network.\n(12) On * basis, managing the capacity of the Network to meet the Service Levels and respond to Gap\u2019s operational requirements as they evolve. Such modifications will be subject to the Change Management procedure described in Section 5 (Change Management) of Exhibit A.2 (Cross Functional Services Statement of Work). Supplier\u2019s Network capacity optimization responsibilities include:\n(A) Monitoring, measuring, and reporting on the physical capacity of the Network. * Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions. Exhibit A.5 Gap/IBM Confidential and Proprietary Information Page 11 of 45\n(B) Upgrading, removing, or adding Network capacity as necessary to meet Gap\u2019s requirements.\n(C) Participating in joint * capacity planning reviews during which Supplier will generate recommendations to Gap based on Network capacity and performance monitoring.\n(D) Identifying future Network loads and utilization that could impact performance on the Network.\n(E) Developing forecasts of Network growth and other changes in response to the projected business and operational needs of Gap.\n(F) Proposing to Gap for Gap Approval, changes to improve performance in anticipation of such future loads, including performance improvement expectations.\n(d) Developing implementation plans in support of Gap Approved business requirements.", "hash": "6ebf6719d95e49f3202c21b3b121924a", "id": 7}, {"size": 1, "snippet_links": [{"key": "the-design", "type": "clause", "offset": [110, 120]}, {"key": "systems-and-data", "type": "clause", "offset": [356, 372]}, {"key": "sensitive-data", "type": "clause", "offset": [420, 434]}, {"key": "internal-network", "type": "definition", "offset": [441, 457]}, {"key": "applicable-information", "type": "definition", "offset": [560, 582]}, {"key": "security-mechanisms", "type": "clause", "offset": [666, 685]}, {"key": "service-levels", "type": "definition", "offset": [687, 701]}, {"key": "management-requirements", "type": "clause", "offset": [706, 729]}, {"key": "network-services", "type": "clause", "offset": [737, 753]}, {"key": "in-network", "type": "clause", "offset": [788, 798]}, {"key": "services-agreements", "type": "clause", "offset": [799, 818]}, {"key": "services-are-provided", "type": "clause", "offset": [834, 855]}, {"key": "business-needs", "type": "clause", "offset": [895, 909]}, {"key": "laws-and-regulations", "type": "definition", "offset": [929, 949]}, {"key": "an-exception", "type": "clause", "offset": [976, 988]}, {"key": "this-policy", "type": "definition", "offset": [992, 1003]}, {"key": "acceptable-alternative", "type": "definition", "offset": [1111, 1133]}], "samples": [{"hash": "dYRrDIe0Cfb", "uri": "/contracts/dYRrDIe0Cfb#network-engineering", "label": "Student Data Privacy Agreement", "score": 36.3634641729, "published": true}], "snippet": "August Schools implements security functions in a layered approach, minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers. August Schools utilizes a defense-in-depth (DiD) architecture to protect the confidentiality, integrity, and availability of information systems and data, i.e. placing information systems that contain sensitive data in an internal network zone, segregated from the DMZ and other untrusted networks. August Schools synchronizes clocks of all applicable information systems to the same time protocol to enforce consistent and accurate timestamping. Security mechanisms, service levels and management requirements of all network services should be identified and included in network services agreements, whether these services are provided in-house or outsourced. August Schools business needs, local situations, laws and regulations may occasionally call for an exception to this policy or any other August Schools policy. If an exception is needed, August Schools management will determine an acceptable alternative approach.", "hash": "9e3ba2845e3b030e72279689d86b8954", "id": 8}, {"size": 1, "snippet_links": [{"key": "vendor-will-provide", "type": "clause", "offset": [0, 19]}, {"key": "responsible-for", "type": "clause", "offset": [266, 281]}, {"key": "confidential-treatment-requested", "type": "definition", "offset": [282, 314]}], "samples": [{"hash": "dyWh2TirTYN", "uri": "/contracts/dyWh2TirTYN#network-engineering", "label": "Network Services Agreement (Genuity Inc)", "score": 18.0, "published": true}], "snippet": "Vendor will provide network engineering expertise to address [*Material Omitted and Separately Filed Under an Application for Confidential Treatment] that arise [*Material Omitted and Separately Filed Under an Application for Confidential Treatment]. Vendor will be responsible for CONFIDENTIAL TREATMENT REQUESTED [*Material Omitted and Separately Filed Under an Application for Confidential Treatment].", "hash": "cde576d8be954c0bea769ed3d9cac997", "id": 9}, {"size": 1, "snippet_links": [{"key": "party-states", "type": "definition", "offset": [20, 32]}, {"key": "a-team", "type": "definition", "offset": [45, 51]}, {"key": "long-term", "type": "clause", "offset": [84, 93]}, {"key": "operational-planning", "type": "clause", "offset": [94, 114]}, {"key": "network-project", "type": "clause", "offset": [172, 187]}, {"key": "the-risks", "type": "clause", "offset": [204, 213]}, {"key": "the-contracting-party", "type": "clause", "offset": [218, 239]}, {"key": "the-cost", "type": "clause", "offset": [273, 281]}, {"key": "transmission-system", "type": "clause", "offset": [301, 320]}, {"key": "the-facilities", "type": "clause", "offset": [359, 373]}, {"key": "the-equipment-and-the-software", "type": "clause", "offset": [375, 405]}, {"key": "the-services", "type": "definition", "offset": [421, 433]}, {"key": "in-accordance-with", "type": "definition", "offset": [459, 477]}, {"key": "operational-conditions", "type": "clause", "offset": [559, 581]}, {"key": "maintenance-of-the-equipment", "type": "clause", "offset": [634, 662]}, {"key": "minimum-level", "type": "definition", "offset": [681, 694]}, {"key": "the-applicable", "type": "clause", "offset": [715, 729]}, {"key": "equipment-manufacturer", "type": "definition", "offset": [744, 766]}, {"key": "software-maintenance", "type": "definition", "offset": [788, 808]}, {"key": "applicable-documentation", "type": "clause", "offset": [873, 897]}, {"key": "software-supplier", "type": "definition", "offset": [928, 945]}], "samples": [{"hash": "eT5Tqt0acsg", "uri": "/contracts/eT5Tqt0acsg#network-engineering", "label": "Agreement for the Supplying of Commuted Fixed Telephone Service and Other Telecommunications Services and Internet/Ip Services (America Online Latin America Inc)", "score": 18.0, "published": true}], "snippet": "2.1. The Contracted Party states that it has a team of network engineers to perform long term operational planning.\n2.2. The Contracted Party shall continue to improve the network project so as to reduce the risks for the Contracting Party, to improve the powerfulness and the cost/performance of the transmission system.\n2.3. The Contracted Party shall keep the facilities, the equipment and the software used to supply the services so that they can operate in accordance with their respective specifications, including:\n2.3.1. to keep the equipment in good operational conditions,\n2.3.2. to take over the repairs and the preventive maintenance of the equipment, including in its minimum level, in accordance with the applicable advice of the equipment manufacturer,\n2.3.3. to carry out software maintenance including to a minimum level, in accordance with the software's applicable documentation and to the suggestions of the software supplier.", "hash": "696308b8699ee114e9bfd99a0b302000", "id": 10}], "next_curs": "ClwSVmoVc35sYXdpbnNpZGVyY29udHJhY3RzcjgLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhxuZXR3b3JrLWVuZ2luZWVyaW5nIzAwMDAwMDBhDKIBAmVuGAAgAA==", "clause": {"size": 24, "children": [["circuit-provision", "Circuit Provision"], ["calling-line-identification", "Calling Line Identification"], ["network-changes", "Network Changes"]], "title": "Network Engineering", "parents": [["general", "General"], ["construction", "Construction"], ["summary-and-implementation-plan", "Summary and Implementation Plan"], ["specifications-and-acceptance-criteria", "Specifications and Acceptance Criteria"], ["broadband-backhaul-purchase-commitments", "Broadband Backhaul Purchase Commitments"]], "id": "network-engineering", "related": [["engineering", "Engineering", "Engineering"], ["reverse-engineering", "Reverse Engineering", "Reverse Engineering"], ["engineering-services", "Engineering Services", "Engineering Services"], ["value-engineering", "Value Engineering", "Value Engineering"], ["geotechnical-engineer", "Geotechnical Engineer", "Geotechnical Engineer"]], "related_snippets": [], "updated": "2025-07-13T05:45:30+00:00"}, "json": true, "cursor": ""}}