Market data audit Sample Clauses

Market data audit. 5.11.1 The purpose of a market data audit is to examine the operational controls underlying the release of Data on devices and to confirm the correct Charges have been paid to the Exchange over an agreed audit period.
AutoNDA by SimpleDocs

Related to Market data audit

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

  • Data Analysis In the meeting, the analysis that has led the College President to conclude that a reduction- in-force in the FSA at that College may be necessary will be shared. The analysis will include but is not limited to the following: ● Relationship of the FSA to the mission, vision, values, and strategic plan of the College and district ● External requirement for the services provided by the FSA such as accreditation or intergovernmental agreements ● Annual instructional load (as applicable) ● Percentage of annual instructional load taught by Residential Faculty (as applicable) ● Fall Full-Time Student Equivalent (FFTE) inclusive of dual enrollment ● Number of Residential Faculty teaching/working in the FSA ● Number of Residential Faculty whose primary FSA is the FSA being analyzed ● Revenue trends over five years for the FSA including but not limited to tuition and fees ● Expenditure trends over five years for the FSA including but not limited to personnel and capital ● Account balances for any fees accounts within the FSA ● Cost/benefit analysis of reducing all non-Residential Faculty plus one Residential Faculty within the FSA ● An explanation of the problem that reducing the number of faculty in the FSA would solve ● The list of potential Residential Faculty that are at risk of layoff as determined by the Vice Chancellor of Human Resources ● Other relevant information, as requested

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

  • PRICING/AUDIT The Contractor shall establish and maintain a reasonable accounting system, which enables ready identification of Contractor’s cost of goods and use of funds. Such accounting system shall also include adequate records and documents to justify all prices for all items invoiced as well as all charges, expenses and costs incurred in providing the goods for at least five (5) years after completion of this contract. The County or its designee shall have access to such books, records, subcontract(s), financial operations, and documents of the Contractor or its subcontractors, as required to comply with this section for the purpose of inspection or audit anytime during normal business hours at the Contractor's place of business. This right to audit shall include the Contractor’s subcontractors used to procure goods under the contract with the County. Contractor shall ensure the County has these same rights with subcontractors and suppliers.

  • Minimum Technical Requirements Participant will be responsible for installing (unless Vendor provides), maintaining and hosting the Vendor’s integration package (either “Full Express” or “Express Lite” software) on Participant’s own computer to enable connectivity to the Network for the Patient Look-Up and Delivery Services including installing and maintaining updates and upgrades. Participant’s machine must meet the following requirements for hosting the Vendor’s integration package: • A virtual machine environment running VMware Player (free open source product) that can run the Express VMware disk image (.ova format) • For Vendor’s “Express Lite” software (for Participants that already have an enterprise master patient index (MPI) and a clinical data repository), the minimum system resources that should be allocated to the virtual machine are: o 4 CPU cores o 8GB of RAM o 100GB of available disk space • For Vendor’s “Full Express” software (for Participants that do not already have an MPI or a clinical data repository), the minimum system resources that should be allocated to the virtual machine are: o 8 CPU cores o 16GB of RAM o 500GB of available disk space • Network access between the Vendor’s Express software (either “Express Lite” or “Full Express”) and the Participant’s health information exchange system for the exchange of clinical system data for the Patient Look-Up and Delivery Services. The Participant shall maintain availability of its data for query on a 24 hour/7 day basis with the exception of routine and unexpected maintenance, at greater than 99% uptime monthly. The Participant shall make its data available for a minimum look-back period of 18 months up to and including current available data and update the available data daily.

  • Statistical Sampling Documentation a. A copy of the printout of the random numbers generated by the “Random Numbers” function of the statistical sampling software used by the IRO.

  • Data Use Each party may use Connected Account Data in accordance with this Agreement and the consent (if any) each obtains from each Connected Account. This consent includes, as to Stripe, consent it receives via the Connected Account Agreement.

  • SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work.

  • Contract Database Metadata Elements Title: Whitesville Central School District and Whitesville Central School Educational Support Staff Association (2003) Employer Name: Whitesville Central School District Union: Whitesville Central School Educational Support Staff Association Local: Effective Date: 07/01/2003 Expiration Date: 06/30/2006 PERB ID Number: 10699 Unit Size: Number of Pages: 23 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT BETWEEN WHITESVILLE CENTRAL SCHOOL EDUCATIONAL SUPPORT STAFF ASSOCIATION AND THE WHITESVILLE CENTRAL SCHOOL DISTRICT JULY 1, 2003 THROUGH JUNE 30, 2006 TABLE OF CONTENTS ARTICLE TITLE PAGE Preamble 1 I Recognition 1 II Collective Bargaining U n i t 1 III Dues/Agency Fee Ckoffand Payroll Deduction 1 IV Rights of Employees 2 V Rights of Employer ------------- 2 VI Personnel F i l e 2 VII Employee Definitions 3 VIII Permanent Status/Seniority 4 IX Wages 5 X Overtime 7 XI Vacation 7 XII Holidays 8 XIII Sick Leave and Leavesof A b s e n c e 8 XIV Conference, Workshops,Required Courses 10 XV Meal Allowance and M i l e a g e 11 XVI Retirement 11 XVII Insurance 12 XVIII Cafeteria P l a n 14 .XIX Uniform Allowance------------------ 14 XX Hours of W o r k 14 XXI Transfers/Promotions 15 XXII Job Descriptions 15 XXIII Grievance Procedure 15 XIV Copies of the Contract 18 XV Zipper C x x x x x 18 XXVI Legislative Clause 18 XXVII Duration 19 SIGNATURES 19 APPENDIX A Grievance F o r m 20 APPENDIX B Dues Authorization F o r m 21

  • Technical Requirements 2.7.4.1 The NID shall provide an accessible point of interconnection and shall maintain a connection to ground.

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