Operational Strategy Sample Clauses

Operational Strategy. Members may engage in the development of cost-efficient technologies for electronic circuit assembly, interconnect, materials and processes to the extent such technologies are applicable to iNEMI’s objectives.
Sample 1
AutoNDA by SimpleDocs
Operational Strategy. As stated in the Record of Decision (ROD), “the primary objective of this interim remedial action is to implement a first-phase remedial action as an interim action to initiate hydraulic control of the high concentration area within the Northeast Plume that extends outside the plant security fence.” The Explanation of Significant Differences to the Record of Decision for the Interim Remedial Action of the Northeast Plume at the Paducah Gaseous Diffusion Plant, Paducah, Kentucky, DOE/LX/07-1291&D2/R2, (ESD) was developed to document the necessary changes made to optimize the Northeast Plume interim remedial actixx (IRX) (DOE 2016). The Memorandum of
Sample 1

Related to Operational Strategy

  • Operational Standards Customer shall furnish, install, operate and maintain in good order and repair, all without cost to the City, all equipment required for the safe operation of the Facility in parallel with the City’s electric distribution system. This includes, but is not limited to, equipment necessary to:

  • Operational Manual (a) The Multiplex Licensee agrees to develop an operational manual in consultation with all Access Seekers to deal with technical and operational matters that arise under or in connection with this Agreement, or the supply of the Multiplex Transmission Service (Operational Manual).

  • Operational Support Systems <<customer_name>> shall pay charges for Operational Support Systems (OSS) as set forth in this Agreement in Attachment 1 and/or in Attachments 2, 3 and 5, as applicable.

  • 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.

  • Operational Support Systems (OSS 2.13.1 BellSouth has developed and made available the following electronic interfaces by which <<customer_name>> may submit LSRs electronically. LENS Local Exchange Navigation System EDI Electronic Data Interchange TAG Telecommunications Access Gateway

  • Implementation of Strategic Plan Goals This Agreement supports the County’s Strategic Plan, Goal 1, Operational Effectiveness/Fiscal Sustainability. This Agreement will provide revenue reimbursement to the Department for services rendered.

  • Synchronisation Commissioning and Commercial Operation 8.1 The Developer shall provide at least forty (40) days advanced preliminary written notice and at least twenty (20) days advanced final written notice to ESCOM of the date on which it intends to synchronize the Power Project to the Grid System.

  • Financial Stability The Contractor shall meet and comply with all requirements located in Title 27, Articles 1 through 15, of the Indiana Code. This includes, but is not limited to, the requirements pertaining to financial solvency, reinsurance and policy contracts, as well as administration of these processes. FSSA and the Indiana Department of Insurance (IDOI) will monitor the Contractor’s financial performance. FSSA will include IDOI findings in their monitoring activities. FSSA shall be copied on required filings with IDOI, and the required filings shall break out financial information for the Hoosier Healthwise line of business separately. The financial performance reporting requirements are listed in Section 9.1 and are further described in the Hoosier Healthwise MCE Reporting Manual, which shall be provided following the Contract award date.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least thirty (30) days written notice to the SLDC and GUVNL, of the date on which it intends to synchronize the Power Project to the Grid System.

  • REGULATORY FILINGS AND CAISO TARIFF COMPLIANCE 3.1 Filing

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