Specification for ERMS Based Records Sample Clauses

Specification for ERMS Based Records. The SMURF ERMS The SMURF (Semantically Marked Up Records Format) ERMS Content Information Type specification caters for the archiving of records which are either exported from an Electronic Records Management System (ERMS) or any other application or system with records management capabilities (e.g. capabilities of classifying and describing information which is stored in binary formats like .doc or .pdf). Note that the SMURF format in general can be used for archiving “loose” data organised as computer files and/or folders on a hard drive. For this scenario please consult Chapter 3.5 Specification for Simple File-System Based Records: The SMURF SFSB.
AutoNDA by SimpleDocs

Related to Specification for ERMS Based Records

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Detailed Description of Services / Statement of Work Describe fully the services that Contractor will provide, or add and attach Exhibit B to this Agreement.

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

  • Specification and Service Levels The Specification sets out the Services that the Contractor has undertaken to provide. The Specification includes Service Levels setting out particular levels of service that the Contractor has undertaken to meet.

  • Evaluation Forms a. Performance evaluation forms will at a minimum have:

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

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

  • EODUF Packing Specifications 7.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.

  • Drug Testing Procedures a. The testing procedures and safeguards provided in this policy shall be adhered to by any laboratory personnel administering departmental drug tests.

  • Ongoing Review and Revisions As set forth in Section 35.7, the Parties have agreed to the coordination and exchange of data and information under this Agreement to enhance system reliability and efficient market operations as systems exist and are contemplated as of the Effective Date. The Parties expect that these systems and the technology applicable to these systems and to the collection and exchange of data will change from time to time throughout the term of this Agreement. The Parties agree that the objectives of this Agreement can be fulfilled efficiently and economically only if the Parties, from time to time, review and, as appropriate, revise the requirements stated herein in response to such changes, including deleting, adding, or revising requirements and protocols. Each Party will negotiate in good faith in response to such revisions the other Party may propose from time to time. Nothing in this Agreement, however, shall require any Party to reach agreement with respect to any such changes, or to purchase, install, or otherwise implement new equipment, software, or devices, or functions, except as required to perform this Agreement.

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