Initial Systems Sample Clauses

Initial Systems. Firm Order Completions (FOC), Jeopardies, Rejects, and Completions. CLEC and PACIFIC will translate necessary data elements used in their internal processes into mutually agreeable file formats and record layouts. CLEC and PACIFIC will develop a mutually agreeable schedule for transmissions throughout the day using the CONNECT: Direct protocol.
Sample 1Sample 2
Initial Systems. Except as provided in Exhibit 1. PACIFIC will provide CLEC, on or before the Effective Date, with an electronic interface known as Resale Mechanized Interface (RMI) for transmitting and receiving Service Requests and related information such as Firm Order Confirmations (FOC, Jeopardies, Rejects, and Completions). CLEC and PACIFIC will translate necessary data elements used in their internal processes into mutually agreeable file formats and record layouts. CLEC and PACIFIC will develop a mutually agreeable schedule for transmissions throughout the day suing the CONNECT: Direct protocol. For the ordering of products not supported by RMI, PACIFIC will provide CLEC with other technologies mutually agreed to by the Parties.
Sample 1Sample 2
Initial Systems. Except as provided in Exhibit 1, PACIFIC will provide CLC, on or before the Effective Date, with an electronic interface known as Resale Mechanized Interface (RMI) for transmitting and receiving Service Requests and related information such as Firm Order Confirmations (FOC), Jeopardies, Rejects, and Completions. CLC and PACIFIC will translate necessary data elements used in their internal processes into mutually agreeable file formats and record layouts. CLC and PACIFIC will develop a mutually agreeable schedule for transmissions throughout the day using an agreed upon file transfer protocol. 2.1.1.1. For the ordering of products not supported by RMI, PACIFIC will provide CLC with other technologies mutually agreed to by the Parties.
Sample 1
Initial Systems. CLC will utilize XXXX and various manual methods agreed upon by the Parties for preordering information exchange. Additional enhancements to XXXX will be mutually coordinated between the Parties to ensure full use of the capabilities when implemented on a mutually agreeable schedule.
Sample 1
Initial Systems. Prior to implementation of EDI, CLEC will utilize various manual methods, or mechanized methods as the Parties shall mutually agree, of preordering information exchange. The manual methods will include monthly diskettes, facsimile, and/or telephone.
Sample 1
Initial Systems. In the event that an EDI interface has not been deployed prior to CLEC’s intent to enter the NEVADA market, within 30 days of a written request from CLEC, NEVADA will provide CLEC the ability to order appropriate resale services with the Electronic Interface known as Resale Mechanized Interface/Network Data Mover (RMI/NDM) for transmitting and receiving Service Requests and related information such as Firm Order Confirmations (FOC, Jeopardies, Rejects, and Completions) using the same file formats, record layouts and network interfaces in place between CLEC and Pacific Bxxx. CLEC and NEVADA will develop a mutually agreeable schedule for transmissions throughout the day using the CONNECT: Direct protocol. For the ordering of products not supported by RMI/NDM, NEVADA will provide CLEC with other technologies mutually agreed to by the Parties.
Sample 1
Initial Systems. CLEC and NEVADA will use two types of orders, an Infrastructure Provisioning order and a Customer Specific Provisioning order to order and provision Network Elements and Combinations. The Infrastructure Provisioning Footprint order notifies NEVADA of the commonly used (across CLEC Retail Customers) Network Elements and Combinations that CLEC will require, and identifies the geographic area CLEC expects to serve through the Network Elements and Combinations ordered. NEVADA and CLEC will utilize the same ordering process and forms used for Exchange Access products as is agreed to between CLEC and Pacific Bxxx. If no process exists between CLEC and Pacific Bxxx, CLEC and NEVADA will mutually agree to adopt a process until the ATIS/OBF has adopted an acceptable alternative method. In addition NEVADA will accept a modified version of the Translation Questionnaire (TQ) adopted by the OBF. The modified TQ will be sent to NEVADA, and NEVADA will modify the routing tables for its end offices to accommodate the treatment of customer calling associated with the combination of Network Elements and Combinations that CLEC is employing to deliver service. CLEC will provide the Infrastructure Footprint Order and all associated ASR forms. NEVADA will accept delivery of the Infrastructure Provisioning Forms through the ASR process. The customer specific provisioning order will be based upon OBF LSR Forms. NEVADA agrees that the information exchange will be forms based using the Local Service Request Form, End User Information Form, Loop Element Form (formerly Loop Service form), and Switch Element Form (formerly Port Form) developed by the OBF. Such customer specific elements include, but are not limited to, the customer loop, the network interface device, the customer dedicated portion of the local switch, and any combination thereof. For ordering of products not supported by Electronic Data Interface, NEVADA will provide CLEC with other technologies mutually agreed to by the Parties.
Sample 1
Initial Systems 
Sample 1

Related to Initial Systems

  • Secondary Systems The Developer and Connecting Transmission Owner shall each cooperate with the other in the inspection, maintenance, and testing of control or power circuits that operate below 600 volts, AC or DC, including, but not limited to, any hardware, control or protective devices, cables, conductors, electric raceways, secondary equipment panels, transducers, batteries, chargers, and voltage and current transformers that directly affect the operation of Developer or Connecting Transmission Owner’s facilities and equipment which may reasonably be expected to impact the other Party. The Developer and Connecting Transmission Owner shall each provide advance notice to the other Party, and to NYISO, before undertaking any work on such circuits, especially on electrical circuits involving circuit breaker trip and close contacts, current transformers, or potential transformers.

  • Computer Systems (a) Servicer to operate systems (b) Servicer to maintain back-up facilities (c) Servicer to notify location of computer tapes

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Software Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.

  • Drainage Systems (1) Clear culvert inlets, outlets, and sediment catching basins. (2) Maintain waterbars, drainage dips, and other water diversion measures. (3) During active use, patrol and maintain functional drainage. (4) Repair damaged culvert ends.

  • Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.

  • Master Feeder Structure If permitted by the 1940 Act, the Board of Trustees, by vote of a majority of the Trustees, and without a Shareholder vote, may cause the Trust or any one or more Series to convert to a master feeder structure (a structure in which a feeder fund invests all of its assets in a master fund, rather than making investments in securities directly) and thereby cause existing Series of the Trust to either become feeders in a master fund, or to become master funds in which other funds are feeders.

  • Installation Services The Bitstream 2a Service includes a Standard Install as set out below (in each case to the extent that the relevant provisioning works are not already complete for the relevant Service Order).1

  • Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If ECI chooses to subtend a Verizon access Tandem, ECI’s NPA/NXX must be assigned by ECI to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 ECI shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from ECI’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office ECI utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow ECI’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.