Operational Policy and System Evaluation Radio System Operations Sample Clauses

Operational Policy and System Evaluation Radio System Operations 
AutoNDA by SimpleDocs

Related to Operational Policy and System Evaluation Radio System Operations

  • System Operations Each party, at its own expense, shall provide and maintain the equipment, software, services and testing necessary to transmit Data Communications to, and receive Data Communications from the parties’ respective Receipt Computers.

  • System Operation The Parties shall adhere to any applicable operational requirements of PJM necessary to protect the integrity of the transmission system within the PJM Control Area and the transmission systems of interconnected control areas, and shall satisfy any and all PJM, RFC and NERC criteria, when applicable. The DS Supplier shall also adhere to any applicable operational requirements of the Company necessary to protect the integrity of the Company’s local distribution system.

  • INTERNET PLANNING, ENGINEERING AND OPERATIONS ‌ Job Title: Internet/Web Engineer Job#: 2620 General Characteristics Integrally involved in the development and support of all Internet/Intranet/Extranet sites and supporting systems. Works closely with other IT groups and customers to define the system design and user interface based on customer needs and objectives. Participates in all phases of the development and implementation process, and may act as a project manager on special projects. Ensures the integration of the Web servers and all other supporting systems. Responsible for system tuning, optimization of information/data processing, maintenance and support of the production environment.

  • Disaster Recovery and Business Continuity The Parties shall comply with the provisions of Schedule 5 (Disaster Recovery and Business Continuity).

  • System Protection Facilities The Interconnection Customer shall, at its expense, install, operate and maintain System Protection Facilities as a part of the Large Generating Facility or the Interconnection Customer’s Interconnection Facilities. The Participating TO shall install at the Interconnection Customer's expense any System Protection Facilities that may be required on the Participating TO’s Interconnection Facilities or the Participating TO’s Transmission System as a result of the interconnection of the Large Generating Facility and the Interconnection Customer’s Interconnection Facilities.

  • ACCESS TO OPERATIONS SUPPORT SYSTEMS 2.1 BellSouth shall provide Cellutell Communications, Inc. access to operations support systems (“OSS”) functions for pre-ordering, ordering and provisioning, maintenance and repair, and billing. BellSouth shall provide access to the OSS through manual and/or electronic interfaces as described in this Attachment. It is the sole responsibility of Cellutell Communications, Inc. to obtain the technical Version R4Q01: 12/01/01 capability to access and utilize BellSouth’s OSS interfaces. Specifications for Cellutell Communications, Inc.’s access and use of BellSouth’s electronic interfaces are set forth at xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx and are incorporated herein by reference.

  • Accounting System Requirement The Contractor shall maintain an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles or “GAAP.”

  • Operations Logs Seller shall maintain a complete and accurate log of all material operations and maintenance information on a daily basis. Such log shall include, but not be limited to, information on power production, fuel consumption, efficiency, availability, maintenance performed, outages, results of inspections, manufacturer recommended services, replacements, electrical characteristics of the generators, control settings or adjustments of equipment and protective devices. Seller shall maintain this information for at least two (2) years and shall provide this information electronically to Buyer within one day of Buyer’s request.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Emergency Mode Operation Plan Contractor must establish a documented plan to enable continuation of critical business processes and protection of the security of electronic DHCS PHI or PI in the event of an emergency. Emergency means any circumstance or situation that causes normal computer operations to become unavailable for use in performing the work required under this Agreement for more than 24 hours.

Time is Money Join Law Insider Premium to draft better contracts faster.