System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.
Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.
Customer Requirements Customer will be required to maintain complex passwords for their User accounts where applicable. For any such passwords LightEdge will provide a secure URL that any User can access to change passwords. All User passwords are set to a ninety (90) day password expiration schedule by default. LightEdge is not responsible for unexpected use of Services whether by ex-employees, compromised User passwords or any other misuse of Customer accounts. Customer shall be responsible for all costs incurred by such unexpected use of Service. Customer shall be fully responsible for providing to LightEdge at Customer’s own expense and in a timely manner the following: - All security for its Services and systems used or accessible in connection with Service; - Cooperative testing of all Customer-provided hardware, software, and Services for compatibility with Service; - Designating an Authorized Contact(s) to be the point of contact to interface with LightEdge Technical Support; - All cabling necessary to support Service; and - Physical and remote management access to any and all Servers onto which Service is installed.
Network Requirements Customer shall be responsible for ensuring that all aspects of the applicable network environment(s) adhere to the applicable standards and requirements specified in the Documentation and are configured appropriately to its proposed use of Ordered SaaS Services.
Interface Requirements 2.4.5.1 The NID shall be equal to or better than all of the requirements for NIDs set forth in the applicable industry standard technical references.
Technical Requirements 4.5.3.1 Tandem Switching shall have the same capabilities or equivalent capabilities as those described in Telcordia TR-TSY-000540 Issue 2R2, Tandem Supplement, June 1, 1990. The requirements for Tandem Switching include but are not limited to the following:
4.5.3.1.1 Tandem Switching shall provide signaling to establish a tandem connection;
4.5.3.1.2 Tandem Switching will provide screening as jointly agreed to by <<customer_short_name>> and BellSouth;
4.5.3.1.3 Where applicable, Tandem Switching shall provide AIN triggers supporting AIN features where such routing is not available from the originating end office switch, to the extent such Tandem switch has such capability;
4.5.3.1.4 Where applicable, Tandem Switching shall provide access to Toll Free number database;
4.5.3.1.5 Tandem Switching shall provide connectivity to Public Safety Answering Point (PSAP)s where 911 solutions are deployed and the tandem is used for 911; and
4.5.3.1.6 Where appropriate, Tandem Switching shall provide connectivity for the purpose of routing transit traffic to and from other carriers.
4.5.3.2 BellSouth may perform testing and fault isolation on the underlying switch that is providing Tandem Switching. Such testing shall be testing routinely performed by BellSouth. The results and reports of the testing shall be made available to <<customer_short_name>>.
4.5.3.3 BellSouth shall control congestion points and network abnormalities. All traffic will be restricted in a non-discriminatory manner.
4.5.3.4 Tandem Switching shall process originating toll free traffic received from <<customer_short_name>>’s local switch.
4.5.3.5 In support of AIN triggers and features, Tandem Switching shall provide SSP capabilities when these capabilities are not available from the Local Switching Network Element to the extent such Tandem Switch has such capability.
Accounting System Requirement The Contractor shall maintain an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles or “GAAP.”
Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.
System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades.
5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2
