CSP to Service Provider - Warrant Files Sample Clauses

CSP to Service Provider - Warrant Files. Warrant files received by the Service Provider shall require a “handshake” message to be sent to CSP. This is to confirm successful receipt of individual files by the Service Provider. Cases transferred from another Service Provider (“Reallocated cases”) will be passed in a separate file formatted in the same way as new cases. Collectively these files are known as “warrant files”. A warrant file and (if applicable) a reallocated warrant file shall be written to the “CSP to Bailiff” directory for the Service Provider. Warrant files shall be processed by the Service Provider within one hour of receipt from the CSP, during Working Hours.
AutoNDA by SimpleDocs

Related to CSP to Service Provider - Warrant Files

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

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

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • Access to Files A copy of any completed evaluation which is to be placed in a nurse’s file shall be first reviewed with the nurse. The nurse shall initial such evaluation as having been read and shall have the opportunity to add her views to such evaluation prior to it being placed in her file. It is understood that such evaluations do not constitute disciplinary action by the Hospital against the nurse. Each nurse shall have reasonable access to all her files for the purpose of reviewing their contents in the presence of her supervisor. A copy of the evaluation will be provided to the nurse at her request. No document shall be used against a nurse where it has not been brought to her attention in a timely manner. Any letter of reprimand, suspension or other sanction will be removed from the record of a nurse eighteen months following the receipt of such letter, suspension or other sanction provided that the nurse’s record has been discipline free for one year. Newly hired part-time nurses shall beconsidered to be on probation for a period of sixty tours worked hours of work for nurses whose regular hours of work are other than the standard work day). If retained the sixty tours hours) worked. With the written consent of the or her designate, such probationary period may be extended. Where the Hospital requests an extension of the probationary period, it will provide notice to the Association at least fourteen calendar days prior to the expected date of expiration of the initial probationary period. It is to the probationary period will not exceed an additional sixty tours hours) worked and, where requested, the Hospital will advise the nurse and the Association of the basis of such extension. A nurse who transfers from casual part-time or full-time to regular not has previously completed one since her date of last hire. Where no such probationary period has been served, the number of tours worked (hours worked for nurses whose regular hours of work are other than the standard work day) during the nine months immediately preceding the transfer shall be credited towards the probationary period.

  • Maintenance of Review Materials It will maintain copies of any Review Materials, Review Reports and other documents relating to a Review, including internal correspondence and work papers, for a period of at least two years after any termination of this Agreement.

  • Access to Review Materials The Servicer will give the Asset Representations Reviewer access to the Review Materials for all of the Subject Receivables within sixty (60) calendar days after receipt of the review notice in one or more of the following ways in the Servicer’s reasonable discretion: (i) by electronic posting of Review Materials to a password-protected website to which the Asset Representations Reviewer has access, (ii) by providing originals or photocopies of documents relating to the Subject Receivables at one of the properties of the Servicer or (iii) in another manner agreed by the Servicer and the Asset Representations Reviewer. The Servicer may redact or remove PII from the Review Materials so long as all information in the Review Materials necessary for the Asset Representations Reviewer to complete the Asset Review remains intact and unchanged.

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

  • LIABILITY FOR UNAUTHORIZED USE-LOST/STOLEN CARD NOTIFICATION You agree to notify Credit Union immediately, orally or in writing at Florida Credit Union, X.X. Xxx 0000, Xxxxxxxxxxx, XX 00000 or telephone (000) 000-0000 twenty four

  • Access to Data Operator shall make Data in the possession of the Operator available to the LEA within five (5) business days of a request by the LEA.

  • Breach by Authorized User An Authorized User’s breach shall not be deemed a breach of the Centralized Contract; rather, it shall be deemed a breach of the Authorized User’s performance under the terms and conditions of the Centralized Contract.

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