PROJECT DESCRIPTION / JUSTIFICATION FOR DATA USE Sample Clauses

PROJECT DESCRIPTION / JUSTIFICATION FOR DATA USE. Describe the intended data use, including a justification of why the data are needed. If this response exceeds the space available, attach additional pages.
AutoNDA by SimpleDocs

Related to PROJECT DESCRIPTION / JUSTIFICATION FOR DATA USE

  • Authorized User’s Statement of Work A competitive Mini-Bid is required for every transaction under this Centralized Contract. An Authorized User must prepare a detailed Statement of Work using Appendix F, Attachment 1, Mini-Bid Template. The Authorized User must distribute the Mini-Bid to all qualified Vendors per Lot(s) (unless a Vendor has removed itself from consideration via the Appendix F, Attachment 5, Mini-Bid Participation Interest Template). Contact information, organized by Lot, will be available on the OGS website for this Contract. An Authorized User shall conduct its Mini-Bid in accordance with the requirements set forth in Appendix F, Attachment 2, How to Use this Contract. The following terms and conditions shall apply to each Mini-Bid issued by an Authorized User:  An Authorized User may require the execution of unique forms, such as Confidentiality Non- Disclosure agreements; and  An Authorized User is required to make tentative award and non-award notifications to each Contractor who submitted a response to the Mini-Bid. Additionally, the minimum time, excluding the date of release, between issuance of the Mini-Bid by the Authorized User to the Mini-Bid Opening is as follows:  Xxx 0 Xxxx-Xxxx: Xxxx (0) Xxxxxxxx Xxxx  Xxx 0 Mini-Bids: Ten (10) Business Days

  • Statement of Work The Contractor shall provide the services and staff, and otherwise do all things necessary for or incidental to the performance of work, as set forth below:

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

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

  • Product Description The lead products covered by this Settlement Agreement is limited to following Amazon Identification Number (ASIN) B0BBMRLNV9, with the description, "Lesnow 63-37 Tin Lead Rosin Core Solder Wire for Electrical Soldering 0.8mm Soldering Wire Electronics Solder Content Solder Flux 1.8% (0.8mm, 50g)," which was offered for sale by the Settling Entity on xxxxxx.xxx, hereinafter the “Product” or “Products.”

  • Project Description In two or three brief sentences, provide a concise description of your exhibition. Include the subject matter, type of objects to be included (paintings, sculpture, manuscripts, etc.), those responsible for organizing the exhibition, and catalogue author(s).

  • Service Description The Parties will provide Common Channel Signaling (CCS) to one another via Signaling System 7 (SS7) network Interconnection, in accordance with prevailing industry standards. Use of a third party provider of SS7 trunks is permitted.

  • Contract Description The Description and Location of the Contract and related project(s) are as follows.

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

  • TIMELINESS OF BILLING SUBMISSION The parties agree that timeliness of billing is of the essence to this Contract and recognize that the City is on a fiscal year. All xxxxxxxx for dates of service prior to July 1 must be submitted to the City no later that the first Friday in August of the same year.

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