Initial User Credential Sample Clauses

Initial User Credential. Setup Completed Tyler configuration completion of username values included in Collin County provided Startup Pack. The following state reports and exchanges are included in the scope of this project: • TJJD Electronic Data Interchange • JJAEP Reports • Human Health Services Report • CJIS/JJIS Reporting Requirements specific including but not limited to: o Referral and Adjudication Reporting o Probation / Case Closures Stage 3: Data Conversion Xxxxx will develop conversion routines to migrate the data extracts from Client’s current environment to the Tyler Supervision solution. Xxxxx’x conversion tools facilitate the predictable, repetitive, repeatable conversion process that is necessary. The tools have reports and metrics built in to measure the quality and breadth of the converted data. Xxxxx will initiate the conversion using the best location for each data element and will work with the Client to adjust data as needed to conform with the Tyler Supervision data requirements. Through this process, Xxxxx will successfully migrate the legacy data into Tyler Supervision, but will not construct data that is not already present within the legacy data.
AutoNDA by SimpleDocs
Initial User Credential. Setup Completed Tyler configuration completion of username values included in Collin County provided Startup Pack. Tyler will develop conversion routines to migrate the data extracts from Client’s current environment to the Tyler Supervision solution. Tyler’s conversion tools facilitate the predictable, repetitive, repeatable conversion process that is necessary. The tools have reports and metrics built in to measure the quality and breadth of the converted data. Tyler will initiate the conversion using the best location for each data element and will work with the Client to adjust data as needed to conform with the Tyler Supervision data requirements. Through this process, Tyler will successfully migrate the legacy data into Tyler Supervision, but will not construct data that is not already present within the legacy data.

Related to Initial User Credential

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • END USER AGREEMENTS (“EUA GAC acknowledges that the END USER may choose to enter into an End User Agreement (“EUA) with the Contractor through this Agreement, and that the term of the EUA may exceed the term of the current H-GAC Agreement. H-GAC’s acknowledgement is not an endorsement or approval of the End User Agreement’s terms and conditions. Contractor agrees not to offer, agree to or accept from the END USER, any terms or conditions that conflict with those in Contractor’s Agreement with H-GAC. Contractor affirms that termination of its Agreement with H-GAC for any reason shall not result in the termination of any underlying EUA, which shall in each instance, continue pursuant to the EUA’s stated terms and duration. Pursuant to the terms of this Agreement, termination of this Agreement will disallow the Contractor from entering into any new EUA with END USERS. Applicable H-GAC order processing charges will be due and payable to H-GAC

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

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

  • AGREED FACTS Registration History 7. Since June 2006, the Respondent has been registered in Ontario as a mutual fund salesperson (now known as a dealing representative)1 with WFG Securities Inc. (the “Member”), a Member of the MFDA. 8. At all material times, the Respondent conducted business in the Vaughan, Ontario area. 9. At all material times, the Member’s policies and procedures prohibited Approved Persons from signing a client’s name to a document. 10. Between January 2018 and September 2018, while the Respondent was an Approved Person of the Member, the Respondent signed the initials of clients on 8 trade tickets next to alterations he made to information on the trade tickets, and submitted them to the Member for processing. 11. The alterations made by the Respondent on the trade tickets included alterations to: trade instructions, client signature dates and special instructions. 12. At all material times, the Member’s policies and procedures prohibited Approved Persons from altering information on a signed document without the client initialing the document to show that the changes were approved. 13. In May 2018, while the Respondent was an Approved Person of the Member, he altered 1 account form in respect of 1 client by altering information on a trade ticket without having the client initial the alterations, and used this altered form to process a transaction. 1 In September 2009, the registration category mutual fund salesperson was changed to “dealing representative” when National Instrument 31-103 came into force. 14. The Respondent altered the trading instructions, special instructions and representative commission percentage on the trade ticket without having the client initial these alterations. 15. At all material times, the Member’s policies and procedures prohibited Approved Persons from holding an account form which was signed by a client and was blank or only partially completed. 16. Between January 2015 and October 2018, while the Respondent was an Approved Person of the Member, he obtained, possessed and used to process transactions, 30 pre-signed account forms in respect of 21 clients. 17. The pre-signed account forms consisted of: 25 Trade Tickets, 3 New Account Application Forms and 2 Non Financial Information Update Forms.

  • End User Agreement This publication is distributed under the terms of Article 25fa of the Dutch Copyright Act. This article entitles the maker of a short scientific work funded either wholly or partially by Dutch public funds to make that work publicly available for no consideration following a reasonable period of time after the work was first published, provided that clear reference is made to the source of the first publication of the work. Research outputs of researchers employed by Dutch Universities that comply with the legal requirements of Article 25fa of the Dutch Copyright Act, are distributed online and free of cost or other barriers in institutional repositories. Research outputs are distributed six months after their first online publication in the original published version and with proper attribution to the source of the original publication. You are permitted to download and use the publication for personal purposes. All rights remain with the author(s) and/or copyrights owner(s) of this work. Any use of the publication other than authorised under this licence or copyright law is prohibited. If you believe that digital publication of certain material infringes any of your rights or (privacy) interests, please let the University Library know, stating your reasons. In case of a legitimate complaint, the University Library will, as a precaution, make the material inaccessible and/or remove it from the website. Please contact the University Library through email: xxxxxxxxx@xxx.xx.xx. You will be contacted as soon as possible. University Library Radboud University

  • Procurement of Recovered Materials In the performance of this contract, the Contractor shall make maximum use of products containing recovered materials that are EPA-designated items unless the product cannot be acquired

  • Use of Basement and Service Areas The basement(s) and service areas, if any, as located within the

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

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