Specification of scope through Standards Sample Clauses

Specification of scope through Standards work As stated multiple times, the complexity (e.g., of the MNM types, uses, regulatory oversight, and disciplines, and stakeholder groups of experts) of the scope for Task 2.3 makes interpretation of results difficult. One of the lessons learned through developing the questions and considering the responses for the task was that the specification of topic is necessary prior to a discussion of foresight and methods needs. For example, a question of methods needs for SbD development of a new use of nanoscale SiO2 will differ by MNM form, life cycle stage, use, and regulatory category. The opinions of stakeholders will also differ. Therefore, framing a question to support policy about specific methods is not possible at some aggregate level of general policy making. For nanomaterials, the level of aggregation may be as simple as a single MNM with multiple uses, or a grouping of MNM types with similar surface characteristics, or a grouping of functionalities. Instead of developing general questions to bridge these differences, it may be necessary to create specifications that can then be used to generate finer grained data about methods needs and markets. The finer grained data can then be aggregated into overall policy needs. Making such specifications is the province of standards development organizations (SDO). Therefore, in order to be useful to SbD decision making, discussion of foresight may need to be carried out through scope narrowed to a material type or use or life cycle stage and a similarly structured parsing of the other specifications. Such a structured discussion is also needed so that issues of one material, use, or regulatory decision context are not inappropriately taken as relevant to another. This kind of structure through specification could be further formalized in standards processes such as Technical Reports and Standard Methods also developed through standards development organizations. Several groups are attempting to address this kind of specificity in methods development/standardization in regions and internationally. Including an awareness of foresight needs for SbD in the standards process would be a valuable addition to these efforts to facilitate safe innovation.
AutoNDA by SimpleDocs

Related to Specification of scope through Standards

  • REFERENCE STANDARDS A. Standards, Specifications, Codes, Laws, and Regulations

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

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

  • Specifications and Standards a) All articles supplied shall strictly conform to the specifications, trademark laid down in the bidding document and wherever articles have been required according to ISI/ ISO/ other applicable specifications/ certifications/ standards, those articles should conform strictly to those specifications/ certifications/ standards. The supply shall be of best quality and description. The decision of the competent authority/ purchase committee whether the articles supplied conforms to the specifications shall be final and binding on the supplier/ selected bidder.

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

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

  • Service Level Standards In addition to all other requirements in this Agreement, and in accordance with the Best Claims Practices & Estimating Guidelines, Vendor shall use reasonable and good faith efforts to meet the Service Level Standards set forth below.

  • WORKLOAD STANDARDS One (1) Direct Service Hour (DSH) will be equal to sixty (60) minutes of direct services.

  • Class Specifications The Human Resources Division shall determine:

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