Site protocol. The UDDGP has sets out rules for the drilling operation to promote safe work. It includes ten aspects, and the details of each aspect are described below.
Site protocol Sample Clauses
Related to Site protocol
Site Plan It is Licensee’s responsibility before signing this Agreement to ensure that the Site Plan correctly shows the work that Licensee intends to perform, that the Site Plan correctly shows all improvements and equipment that Licensee intends be located on the Use Areas, that the Site Plan shows no work, improvements or equipment outside the Exclusive Areas and Shared Areas properly depicted and labeled on the Boundary Plan, and that all work, improvements and equipment is encompassed within the purposes enumerated in the Standard Terms for that particular Exclusive Area or Shared Area. Any work, improvements or equipment not conforming to all the foregoing is prohibited, even if it is clearly shown on the Site Plan or discussed in the Standard Terms. Any refinement or other change to the Site Plan after Licensor executes this Agreement is void unless Licensee obtains Licensee’s approval of the change pursuant to the plans approval processes set out in the Standard Terms and pursuant to all applicable regulatory requirements.
Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.
Protocol The attached Protocol shall be an integral part of this Agreement.
Architect/Engineer (A/E) means a person registered as an architect pursuant to Tex. Occ. Code Xxx., Chapter 1051, as a landscape architect pursuant to Tex. Occ. Code Xxx., Chapter 1052, a person licensed as a professional engineer pursuant to Tex. Occ. Code Xxx., Chapter 1001 and/or a firm employed by Owner or a design-build contractor to provide professional architectural or engineering services and to exercise overall responsibility for the design of a Project or a significant portion thereof, and to perform the contract administration responsibilities set forth in the Contract.
Project Engineer If the Project has been designed by the Project Engineer, the Project Engineer is to act as the Owner's representative, assumes all duties and responsibilities, and has the rights and authority assigned to Project Engineer in the Contract Documents in connection with completion of the Work all in accordance with the Contract Documents.
Site Preparation Contractor shall not begin a project for which the site has not been prepared, unless Contractor does the preparation work at no cost, or until Region 4 ESC includes the cost of site preparation in a purchase order. Site preparation includes, but is not limited to: moving furniture, installing wiring for networks or power, and similar pre-installation requirements.
Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.
The Site The site of the Project Highway (the “Site”) shall comprise the site described in Schedule-A in respect of which the Right of Way shall be provided by the Authority to the Contractor. The Authority shall be responsible for:
Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.
System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.
