Exhibit C: MRO Reliability Standards Development Sample Clauses

Exhibit C: MRO Reliability Standards Development. 277. Exhibit C to the MRO Delegation Agreement consists of narrative responses addressing each of NERC’s 34 pro forma Common Attributes addressed above.157 In 155 See 18 C.F.R. §§ 39.1 and 39.10 (2006). See also Order No. 672, FERC Stats. & Regs. ¶ 31,204 at P 113. 157 See supra section IV(A). addition, NERC and MRO rely on an MRO draft manual, “The Midwest Reliability Organization Regional Reliability Standards Process Manual,” version 3.0 (MRO Standards Development Manual).158 The MRO Standards Development Manual is included in NERC’s filing as supplemental information and is cross-referenced in the narrative responses addressing NERC’s 34 pro forma Common Attributes. 278. NERC, in its transmittal letter, states that the MRO Standards Development Manual is consistent with the requirements set forth in NERC’s 34 pro forma Common Attributes. Specifically, NERC states that it has not identified any substantive differences between the MRO Standards Development Manual and NERC’s 34 Common Attributes. XXXX adds that it has worked closely with each of the Regional Entity candidates, including MRO, to attain a high level of consistency among the proposed Regional Entity standards development procedures. NERC further states that each reliability standard that will be proposed to NERC by MRO will have the same format as a NERC reliability standard, will contain the same elements as a NERC reliability standard, and will have been developed through a process meeting the common procedural elements. 279. The MRO Standards Development Manual also addresses voting procedures applicable to the adoption of a proposed reliability standard.159 Specifically, the MRO Standards Development Manual provides for the establishment of a registered ballot body comprised of all organizations and entities that: (i) qualify for one of seven designated voting segments;160 (ii) are registered with MRO as ballot participants in the voting on standards; and (iii) are current with any MRO designated fees associated with the Standards Development Process.161 The MRO Standards Development Manual states board. 159 See MRO Standards Development Manual at app. C (registered ballot body registration procedures) and app. D. (balloting examples).
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs

Related to Exhibit C: MRO Reliability Standards Development

  • Enterprise Information Management Standards Grantee shall conform to HHS standards for data management as described by the policies of the HHS Office of Data, Analytics, and Performance. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.

  • Human and Financial Resources to Implement Safeguards Requirements The Borrower shall make available necessary budgetary and human resources to fully implement the EMP and the RP.

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

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Quality Standards Each Party agrees that the nature and quality of its products and services supplied in connection with the other Party's Marks will conform to quality standards set by the other Party. Each Party agrees to supply the other Party, upon request, with a reasonable number of samples of any Materials publicly disseminated by such Party which utilize the other Party's Marks. Each Party will comply with all applicable laws, regulations, and customs and obtain any required government approvals pertaining to use of the other Party's marks.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • COUNTY’S QUALITY ASSURANCE PLAN The County or its agent will evaluate the Contractor’s performance under this Contract on not less than an annual basis. Such evaluation will include assessing the Contractor’s compliance with all Contract terms and conditions and performance standards. Contractor deficiencies which the County determines are severe or continuing and that may place performance of the Contract in jeopardy if not corrected will be reported to the Board of Supervisors. The report will include improvement/corrective action measures taken by the County and the Contractor. If improvement does not occur consistent with the corrective action measures, the County may terminate this Contract or impose other penalties as specified in this Contract.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Attachment A, Scope of Services The scope of services is amended as follows:

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!