Data Specifications Sample Clauses

Data Specifications a) The Parties acknowledge and agree that under this Agreement IDES will not share or provide the RECIPIENT with any information obtained from an individual or employing unit during the administration of the Illinois unemployment insurance (UI) program including, but not limited to, social security numbers, benefit records and employer’s wage records.
AutoNDA by SimpleDocs
Data Specifications. Improving the data quality is important to enhance the today’s transit data best practices, but improvement to the underlying data specifications can expand what is possible. These improvements could include the capability to describe stop and station amenities, represent planned and unplanned service changes, integrate fare schedules and payment options, and provide schedule and/or real-time information for on-demand transit services (TransitCenter, 2018). Describing the station amenities benefit especially older adults and disabled people. Currently, transit agencies are working on different aspects of these problems to show the real situation of the bus stations. For instance, NYC Transit offers a real-time feed describing elevator status, but it is not yet integrated with GTFS (TransitCenter. 2018). Another important service the transit providers and application developers are working is to provide accurate information about service changes and detours. Schedules could be updated with the recent changes which are going to be better that printed announcements, the website, or social media. Application developers can assist in this effort. For instance, Transit App applies MTA New York City Transit (NYC Transit) service changes using a partially automated review of published changes, with human oversight (TransitCenter, 2018). The GTFS fare model is limited because describes only single-trip zone and route-based fares with transfers, but not regional transit fares, pass products, and other pricing schedules such as time-of day and distance-based fares. Meaning that every fare application needs a specific programming code and the third-party trip planner software often have a fare information deficiency. This situation prevents the customer from having a smooth transaction when purchasing a transit ticket because of the lack of a standardized interface for transit trip planners and third-party applications with a ticketing and fare payment systems. There are at least two possible avenues that can be used for users and application interoperability (TransitCenter, 2018):
Data Specifications. The specific elements of Claims Data that will be collected by VHI for the APCD, along with the detailed field definitions, submission guidelines and instructions set forth in Exhibit 1 (Data Submission Manual), which is attached hereto and incorporated herein by reference.
Data Specifications. Subject to the terms of this Article 3, the Data Specifications shall be as set forth in Exhibit 1.
Data Specifications. An overview of the relationship between data specifications and Download Services, and how Data Publishers should be approaching this. Guidance on how data specification compliance will be managed, and how UKL will define standard datasets for INSPIRE themes.
Data Specifications. The Parties acknowledge and agree that under this Agreement IDES will not share or provide the RECIPIENT with any information obtained from an individual or employing unit during the administration of the Illinois unemployment insurance (UI) program including, but not limited to, social security numbers, benefit records and employer’s wage records. In accordance with 56 Ill. Admin. Code 2960.120, IDES may provide RECIPIENT with non-UI information contained in the Illinois Job Link (IJL) including: (i) a customer’s name, address, phone number, and/or employment history; (ii) an employer’s name, address, and phone number; (iii) job order information; and (iv) other non-UI information contained in IJL, provided that disclosure of such information is not prohibited under this Agreement.

Related to Data Specifications

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Technical Specifications 1. A procuring entity shall not prepare, adopt or apply any technical specification or prescribe any conformity assessment procedure with the purpose or effect of creating an unnecessary obstacle to trade between the Parties.

  • Quality Specifications SANMINA-SCI shall comply with the quality specifications set forth in its Quality Manual, incorporated by reference herein, a copy of which is available from SANMINA-SCI upon request.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. Items Offered as New. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • General specifications 6.1.1. A vehicle and its electrical/electronic system(s) or ESA(s) shall be so designed, constructed and fitted as to enable the vehicle, in normal conditions of use, to comply with the requirements of this Regulation.

  • Product Specifications The Company agrees that all Products sold to Xxxx hereunder shall conform to the respective specifications set forth on Schedule A or to such other specifications as are from time to time agreed upon by the Parties.

  • Specifications That part of the Contract Documents consisting of written requirements for materials, equipment, systems, standards, and workmanship as applied to the Work, and certain administrative requirements and procedural matters applicable thereto. The term "Specifications" shall also include all written matter in the Project Manual or on the drawings and any Addenda or Change Orders thereto.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

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