Technical Specifications for Deliverables Sample Clauses

Technical Specifications for Deliverables. (1) Sampling and monitoring data must be submitted in standard Regional Electronic Data Deliverable (EDD) format prescribed in the Removal Work Plan. Other delivery methods may be allowed if electronic direct submission presents a significant burden or as technology changes. (2) Spatial data, including spatially-referenced data and geospatial data, must be submitted: (a) in the ESRI File Geodatabase format; and (b) as unprojected geographic coordinates in decimal degree format using North American Datum 1983 (NAD83) or World Geodetic System 1984 (WGS84) as the datum. If applicable, submissions should include the collection method(s). Projected coordinates may optionally be included but must be documented. Spatial data should be accompanied by metadata, and such metadata should be compliant with the Federal Geographic Data Committee (FGDC) Content Standard for Digital Geospatial Metadata and its EPA profile, the EPA Geospatial Metadata Technical Specification. An add-on metadata editor for ESRI software, the EPA Metadata Editor (EME), complies with these FGDC and EPA metadata requirements and is available at ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/geospatial/epa-metadata- editor. (3) Each file must include an attribute name for each site unit or sub- unit submitted. Consult ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/geospatial/geospatial-policies-and- standards for any further available guidance on attribute identification and naming. (4) Spatial data submitted by Purchaser does not, and is not intended to, define the boundaries of the Site.
View SourceView Similar (6)
Technical Specifications for Deliverables. (1) Document submissions (including sampling and monitoring data) must be provided as text-readable PDF. If requested by EPA, sampling and monitoring data may also be submitted as Excel spreadsheet, or other mutually acceptable format.‌ (2) If requested by EPA, spatial data, including spatially-referenced data and geospatial data, may be submitted: (a) in the ESRI File Geodatabase format; or (b) as unprojected geographic coordinates in decimal degree format using North American Datum 1983 (NAD83) or World Geodetic System 1984 (WGS84) as the datum; or (c) another mutually acceptable format. Projected coordinates may be provided but must be documented (coordinate system and datum). If applicable, submissions should include the collection method(s).‌
View SourceView Similar (4)
Technical Specifications for Deliverables i. Sampling and monitoring data should be submitted in standard Regional Electronic Data Deliverable (“EDD”) format. Other delivery methods may be allowed if electronic direct submission presents a significant burden or as technology changes. ii. Spatial data to be submitted pursuant to Task 6.3 of the 2010 SOW, including spatially-referenced data and geospatial data, should be submitted: (a) in the Environmental Systems Research Institute (ESRI) File Geodatabase format; and
View SourceView Similar (3)
Technical Specifications for Deliverables. (1) Sampling and monitoring data contained in any deliverables should be submitted in standard Electronic Data Deliverable (“EDD”) format consistent with the format that Respondent has used for submission of such data from the ▇▇▇▇▇▇ River to EPA since the completion of the dredging component of the OU2 remedy. . Other delivery methods may be allowed if electronic direct submission presents a significant burden or as technology changes. (2) Spatial data, including spatially-referenced data and geospatial data, should be submitted: (a) in the ESRI File Geodatabase format and (b) as unprojected geographic coordinates in decimal degree format using North American Datum 1983 (NAD83) or World Geodetic System 1984 (WGS84) as the datum. If applicable, submissions should include the collection method(s). Projected coordinates must be included and documented. Spatial data should be accompanied by metadata, and such metadata should be compliant with the Federal Geographic Data Committee (“FGDC”) Content Standard for Digital Geospatial Metadata and its EPA profile, the EPA Geospatial Metadata Technical Specification. An add-on metadata editor for ESRI software, the EPA Metadata Editor (“EME”), complies with these FGDC and EPA metadata requirements and is available at ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/geospatial/epa-metadata-editor. (3) Each file must include an attribute name for each site unit or sub- unit submitted. Consult ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/geospatial/geospatial-policies-and- standards for any further available guidance on attribute identification and naming. (4) Spatial data submitted by Respondent does not, and is not intended to, define the boundaries of the Site.
View Source

Related to Technical Specifications for Deliverables

  • Technical Specifications The purpose of the Technical Specifications (TS), is to define the technical characteristics of the Goods and Related Services required by the Procuring Entity. The Procuring Entity shall prepare the detailed TS consider that:

  • Contract Deliverables The Contractor shall provide information technology staff augmentation services, including comprehensive management of staff, as set forth in this Contract. The term “staff” refers to the temporary staff provided by the Contractor to render information technology services identified by Customers, but that staff shall not be deemed an employee of the State or deemed to be entitled to any benefits associated with such employment. Contracts resulting from this solicitation should not be structured as fixed-price agreements or used for any services requiring authorization for payment of milestone tasks. Contractor shall only provide information technology staff augmentation services for those Job Titles awarded to the Contractor and shall be paid on an hourly basis. The Department’s intent is for Contractor’s information technology staff to provide services closely related to those described in the Job Family Descriptions document. Detailed scopes of work, specific requirements of the work to be performed, and any requirements of staff shall be provided by the Customer in a Request for Quote. The Contractor shall possess the professional and technical staff necessary to allocate, outsource, and manage qualified information technology staff to perform the services requested by the Customer. The Contractor shall provide Customers with staff who must have sufficient skill and experience to perform the services assigned to them. All of the information technology staff augmentation services to be furnished by the Contractor under the Contract shall meet the professional standards and quality that prevails among information technology professionals in the same discipline and of similar knowledge and skill engaged in related work throughout Florida under the same or similar circumstances. The Contractor shall provide, at its own expense, training necessary for keeping Contractor’s staff abreast of industry advances and for maintaining proficiency in equipment and systems that are available on the commercial market. The Contractor shall be responsible for the administration and maintenance of all employment and payroll records, payroll processing, remittance of payroll and taxes, and all administrative tasks required by state and federal law associated with payment of staff. The Contractor shall, at its own expense, be responsible for adhering to the Contract background screening requirements, testing, evaluations, advertising, recruitment, and disciplinary actions of Contractor’s information technology staff. The Contractor shall maintain during the term of the Contract all licenses, permits, qualifications, insurance and approvals of whatever nature that are legally required to perform the information technology staff augmentation services.

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

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

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