Data Extract Sample Clauses

Data Extract. To the extent permitted by law, XXXXXXX agrees to provide the OAG with a copy of data transmitted by GRANTEE to the Certified Vendor. XXXXXXX authorizes the Certified Vendor to directly provide such data to the OAG. The Parties agree that this data may be used to monitor GRANTEE performance and the Certified Vendor=s performance. This data may be used for such other purposes allowed by law. The data will be provided in such electronic format (including, but not limited to, an XML extract) as requested by the OAG.
AutoNDA by SimpleDocs
Data Extract. The Data Extract Option will be included in the C3 Hub if, and only if, agreed to by the parties in the C3 Hub Order Form. If such option is included, C3 will offer a periodic data extracts (daily or more frequent) in CSV format for certain data elements like purchase orders, reservations, faults, base data, vehicles, etc. These are generated on a recurring basis and posted to C3’s SFTP for the Customer to consume and post back into their BI tools for reporting purposes. Additional definitions and utilization guidelines for the Data Extract Option can be found in the Documentation.
Data Extract. The standard conversion includes converting from a single source of data, if data is stored in multiple databases OR databases and additional files custom conversion services may be required. The data will need to be provided in one of the following formats: ▪ Microsoft SQL Server database ▪ Microsoft Access database ▪ Delimited ASCII text file(s) ); pipe delimited is preferred ▪ Excel spreadsheets - with flat data, not grouped like a report ▪ Media must be in .jpg or .bmp format or imbedded in a record in a readable format that can be tested prior to Tyler committing to conversion. Images built by third party proprietary software must be converted to .jpg or .bmp by the legacy vendor. The screen shots and balancing reports need to be provided to Tyler at the same time as the data, if not an additional data pull may be required which may result in a delay in schedule. It is important to understand that the conversion will not ‘rehabilitate’ old data. The adage “garbage in, garbage out” certainly applies for data conversions. The conversion process does not clean up or correct problems in old data; data is converted one-to-one. For example, if the current system allowed punctuation, the new software will also display data with the exact same punctuation after the conversion. If data manipulation is desired, please contact your project manager to assist in preparing a work order for these services. The following are a few examples of items that are not included in the standard conversion. • Cross referencing data-such as combining multiple vehicle models into one • Converting records with counts of less than 250 • Running more than 3 iterations of converted data • Data cleaning-including but not limited to name clean up, data fixes • Converting from multiple sources of data • Tyler assisting in data extraction from legacy system • Tyler defining file layout if it is not provided • Changing configuration after sign off • Media in a nonstandard format • Narratives in a nonstandard format
Data Extract. The standard conversion includes converting from a single source of data. If data is stored in multiple databases or data is provided in multiple formats custom conversion services may be required. Below are the approved formats: O Microsoft SQL Server database O Microsoft Access database O Delimited ASCII text files with headers (pipe “|” delimited is preferred) O Excel spreadsheets – with flat data and headers, not grouped in report fashion O PROGRESS database To ensure that no data is corrupted, staff should exit the software prior to pulling the data and restrict processing of any transactions during this time. It is important to understand that the conversion will not “rehabilitate” old data. The conversion process does not clean up or correct problems in old data; data is converted one for one. For example, if the current system allowed punctuation, the new software will also display data with the exact same punctuation after the conversion. If data manipulation is desired, please contact your Project Manager to assist in preparing a work order for these services. Tyler Technologies deploys several methods of transferring files across the internet. For client’s sensitive data, we use Secure File Transfer Protocol (SFTP) servers because it is our policy to never transmit sensitive data across the Internet. If your data requires more sensitive measures please contact your assigned Project Manager. All data uploads and downloads are performed via secure connections. Prior to any data uploads you must compress your data. Your Project Manager will provide you with instructions containing your SFTP user name and password along with a tool for compressing your data.
Data Extract. District may request a one-time extract of the data stored in the Contractor application. Contractor will provide data, at a fee not to exceed 50% of the annual subscription fee. The provided data will be made available to District for up to thirty (30) calendar days. Specific filtering, formatting or alteration requests will be scoped as a billable service at then current rates.
Data Extract. Client may request a one-time extract of the data stored in the Accruent application. Accruent will provide data, in a format defined by Accruent, at a fee not to exceed 50% of the annual subscription fee. The provided data will be made available to Client for up to thirty (30) calendar days. Specific filtering, formatting or alteration requests will be scoped as a billable service at then current rates.

Related to Data Extract

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Contract Database Metadata Elements Title: Whitesville Central School District and Whitesville Central School Educational Support Staff Association (2007) Employer Name: Whitesville Central School District Union: Whitesville Central School Educational Support Staff Association Local: Effective Date: 07/01/2007 Expiration Date: 06/30/2011 PERB ID Number: 10699 Unit Size: Number of Pages: 29 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, 2007 THROUGH JUNE 30, 2011 TABLE OF CONTENTS PREAMBLE 3 ARTICLE I - RECOGNITION 3 ARTICLE II - COLLECTIVE BARGAINING UNIT 3 ARTICLE III - DUES CHECKOFF, PAYROLL DEDUCTIONS, AND AGENCY FEES 3 ARTICLE IV - RIGHTS OF THE EMPLOYEES 4 ARTICLE V - RIGHTS OF THE EMPLOYER 4 ARTICLE VI - PERSONNEL FILE 4 ARTICLE VII - EMPLOYEE DEFINITIONS 5 ARTICLE VIII - PERMANENT STATUS / SENIORITY 7 ARTICLE IX - WAGES 8 ARTICLE X - OVERTIME 10 ARTICLE XI - VACATIONS 11 ARTICLE XII - HOLIDAYS 11 ARTICLE XIII - SICK LEAVE AND LEAVES OF ABSENCE 12 ARTICLE XIV - CONFERENCES, WORKSHOPS, REQUIRED COURSES 15 ARTICLE XV - MEAL ALLOWANCE AND MILEAGE 16 ARTICLE XVI - RETIREMENT 16 ARTICLE XVII - INSURANCE 17 ARTICLE XVIII - CAFETERIA PLAN 17 ARTICLE XIX - UNIFORM ALLOWANCE 22 ARTICLE XX - HOURS OF WORK 22 ARTICLE XXI - TRANSFERS/PROMOTIONS 22 ARTICLE XXII - JOB DESCRIPTIONS 22 ARTICLE XXIII - GRIEVANCE PROCEDURE 23 ARTICLE XXIV - COPIES OF THE CONTRACT 26 ARTICLE XXV - ZIPPER CLAUSE 26 ARTICLE XXVI - LEGISLATIVE CLAUSE 27 ARTICLE XXVII - DURATION 27 APPENDIX A - GRIEVANCE FORM 28 APPENDIX B - DUES AUTHORIZATION FORM 29 PREAMBLE This Agreement is made and entered into between the WHITESVILLE CENTRAL SCHOOL DISTRICT SUPERINTENDENT, hereafter referred to as the "SUPERINTENDENT" representing the WHITESVILLE CENTRAL SCHOOL DISTRICT hereafter referred to as the "DISTRICT" and the WHITESVILLE CENTRAL SCHOOL EDUCATIONAL SUPPORT STAFF ASSOCIATION, hereafter referred to as the "ASSOCIATION".

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

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)

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