ADDITIONAL TECHNICAL REQUIREMENTS Clause Samples

ADDITIONAL TECHNICAL REQUIREMENTS. The Contractor shall be responsible for the installation of fire stopping at all internal and external penetrations. The Contractor shall provide a lockable AC disconnect switch to disconnect the Project from the electric distribution system of the Local Electric Utility. Placement of such a disconnect switch shall meet the requirements of the Local Electric Utility.

ADDITIONAL TECHNICAL REQUIREMENTS. 51 11.1.7 Affiliate........................................................................... 51 11.1.8 Agreement........................................................................... 51 11.1.9 Amdocs.............................................................................. 51 11.1.10

ADDITIONAL TECHNICAL REQUIREMENTS. If necessary, EDI shall provide the End-Users with additional information regarding technical measures to protect the account, the use of Services and other digital content provided, as well as information relevant to the interoperability of the Services with the End-User’s computer hardware and software.

ADDITIONAL TECHNICAL REQUIREMENTS. (a) TasNetworks will ensure the fault current contribution from the transmission system to the three phase and single phase fault levels on the connection site busbars is not more than specified in Clause S5.2.8 of the Generator Performance Standards (b) Each party will ensure that the design of its electricity infrastructure allows for a maximum fault current contribution from Network User to the three phase and single phase fault levels on the connection site busbars as specified in Clause S5.2.8 of the Generator Performance Standards.

ADDITIONAL TECHNICAL REQUIREMENTS. ‌ a. SLA of 99.95 uptime. Describe remediation if SLA is not met. EPR’s solution guarantees 99.95% uptime. If that is not met, it is considered a breach of the SLA. b. For top finalists, the City requests access to a demo environment/install of the proposed solution for a period of 14 days to conduct an evaluation. EPR will provide a demo environment for the City for fourteen (14) days upon request. c. Project Plan shall include tasks, milestones, specific resources responsible, deliverables, and overall timeline for completion, including durations for each task Please see implementation plan in Section 12. Installation & Implementation. d. Specify responsibilities of both the vendor and the City for the implementation, including an estimate of which City employees are needed, how many hours and the role each resource will play in the project (Fire Staff, Project Manager, IT Staff, and vendor resources) EPR is responsible for all aspects of the implementation. We recommend a stakeholder from each of the above listed departments be on the Kickoff call, this will determine the required staff and time needed. Generally, there is not a big time on task for City staff during the implementation phase. It is recommended that all stakeholders attend the admin and system training. This is an eight-hour commitment over two sessions.