Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.
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.
Supplier’s Staff 3.3.1 Access to the Premises shall be limited to such Staff and the Supplier’s suppliers as are necessary for the Supplier to fulfil its obligations under the Contract. The Supplier shall co-operate with others working on the Premises to such extent as the Authority may reasonably require. 3.3.2 The Authority reserves the right to refuse to admit to, or to withdraw permission to remain on, the Premises:- (a) for any member of the Staff; or (b) for any person employed or engaged by any member of the Staff, whose admission or continued presence would be, in the reasonable opinion of the Authority, undesirable. 3.3.3 At the Authority’s written request, the Supplier shall provide a list of the names and business addresses of all persons who may require admission in connection with the Contract to the Premises, specifying the capacities in which they are concerned with the Contract and giving such other particulars as the Authority may reasonably request. 3.3.4 The Supplier’s Staff, engaged within the boundaries of the Premises, shall comply with such rules, regulations and requirements (including those relating to security arrangements) as may be in force from time to time for the conduct of personnel when at or outside those premises. 3.3.5 If the Supplier fails to comply with Clause 3.3.3 within one (1) Month of the date of the request and in the reasonable opinion of the Authority, such failure may be prejudicial to the interests of the Crown, then the Authority may terminate the Contract, provided always that such termination shall not prejudice or affect any right of action or remedy which shall have accrued or shall thereafter accrue to the Authority. 3.3.6 The decision of the Authority as to whether any person is to be refused access to the Premises and as to whether the Supplier has failed to comply with Clause 3.3.3 shall be final and conclusive.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
ODUF Packing Specifications 6.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.
