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.
Office of Supplier Diversity The State of Florida supports its diverse business community by creating opportunities for woman-, veteran-, and minority-owned small business enterprises to participate in procurements and contracts. The Department encourages supplier diversity through certification of woman-, veteran-, and minority-owned small business enterprises and provides advocacy, outreach, and networking through regional business events. For additional information, please contact the Office of Supplier Diversity (OSD) at xxxxxxx@xxx.xxxxxxxxx.xxx.
PUBLIC RECORDS COMPLIANCE (APPLICABLE FOR SERVICE CONTRACTS Orange County is a public agency subject to Chapter 119, Florida Statutes. The Contractor agrees to comply with Florida’s Public Records Law. Specifically, the Contractor shall:
1. Keep and maintain public records required by Orange County to perform the service.
2. Upon request from Orange County’s custodian of public records, provide Orange County with a copy of the requested records or allow the records to be inspected or copied within a reasonable time at a cost that does not exceed the cost provided in this chapter or as otherwise provided by law.
3. Ensure that public records that are exempt or confidential and exempt from the public records disclosure requirements are not disclosed except as authorized by law for the duration of the contract term and following completion of the contract if the Contractor does not transfer the records to Orange County.
4. Upon completion of the contract, Contractor agrees to transfer at no cost to Orange County all public records in possession of the Contractor or keep and maintain public records required by Orange County to perform the service. If the Contractor transfers all public record to Orange County upon completion of the contract, the Contractor shall destroy any duplicate public records that are exempt or confidential and exempt from public records disclosure requirements. If the Contractor keeps and maintains public records upon completion of the contract, the Contractor shall meet all applicable requirements for retaining public records. All records stored electronically must be provided to Orange County, upon request from Orange County’s custodian of public records, in a format that is compatible with the information technology systems of Orange County.
5. A Contractor who fails to provide the public records to Orange County within a reasonable time may be subject to penalties under section 119.10, Florida Statutes.
6. IF THE CONTRACTOR HAS QUESTIONS REGARDING THE APPLICATION OF CHAPTER 119, FLORIDA STATUTES, TO THE CONTRACTOR’S DUTY TO PROVIDE PUBLIC RECORDS RELATING TO THIS CONTRACT, CONTACT THE CUSTODIAN OF PUBLIC RECORDS AT : Procurement Public Records Liaison
Reporting of Sales to TIPS by Vendor The Participation Fee that was published as part of the Solicitation and the fee published is the legally effective fee, along with any fee conditions stated in the Solicitation. Collection of the fees by TIPS is required under Texas Government Code §791.011 Et seq. Fees are due on all TIPS purchases reported by either Vendor or Member. Fees are due to TIPS upon payment by the Member to the Vendor, Reseller or Vendor Assigned Dealer. Vendor, Reseller or Vendor Assigned Dealer agrees that the participation fee is due to TIPS for all Agreement sales immediately upon receipt of payment including partial payment, from the Member Entity and must be paid to TIPS at least on a monthly basis, specifically within 31 calendar days of receipt of payment, if not more frequently, or as otherwise agreed by TIPS in writing and signed by an authorized signatory of TIPS. Thus, when an awarded Vendor, Reseller or Vendor Assigned Dealer receives any amount of payment, even partial payment, for a TIPS sale, the legally effective fee for that amount is immediately due to TIPS from the Vendor and fees due to TIPS should be paid at least on a monthly basis, specifically within 31 calendar days of receipt of payment, if not more frequently. Vendor is required to report all sales under the TIPS contract to TIPS. When a public entity initiates a purchase with a TIPS Awarded Vendor, if the Member inquires verbally or in writing whether the Vendor holds a TIPS Contract, it is the duty of the Vendor to verify whether or not the Member is seeking a TIPS purchase. Once verified, the Vendor must include the TIPS Contract number on any communications and related sales documents exchanged with the TIPS Member entity. To report sales, the Vendor must login to the TIPS Vendor Portal online at xxxxx://xxx.xxxx-xxx.xxx/vendors_form.cfm and click on the PO’s and Payments tab. Pages 3-7 of the Vendor Portal User Guide will walk you through the process of reporting sales to TIPS. Please refer to the TIPS Accounting FAQ’s for more information about reporting sales and if you have further questions, contact the Accounting Team at xxxxxxxxxx@xxxx-xxx.xxx. The Vendor or vendor assigned dealers are responsible for keeping record of all sales that go through the TIPS Agreement and submitting same to TIPS. Failure to render the participation fee to TIPS shall constitute a breach of this agreement with our parent governmental entity, Texas Education Service Center Region 8, as established by the Texas legislature and shall be grounds for termination of this agreement and any other agreement held with TIPS and possible legal action. Any overpayment of participation fees to TIPS by a Vendor will be refunded to the Vendor within ninety (90) days of receipt of notification if TIPS receives written notification of the overpayment not later than the expiration of six (6) months from the date of overpayment and TIPS determines that the amount was not legally due to TIPS pursuant to this agreement and applicable law. It is the Vendor’s responsibility to identify which sales are TIPS Agreement sales and pay the correct participation fee due for TIPS Agreement sales. Any notification of overpayment received by TIPS after the expiration of six (6) months from the date of overpayment will be non-refundable. Region 8 ESC and TIPS reserve the right to extend the six (6) month deadline to notify if approved by the Region 8 ESC Board of Directors. TIPS reserves all rights under the law to collect the fees due. Please contact TIPS at xxxx@xxxx-xxx.xxx or call (000) 000-0000 if you have questions about paying fees.
Instructions for Operators This agreement is intended to be provided to an Operator from a LEA. The Operator should fully read the agreement and is requested to complete the below areas of the agreement. Once the Operator accepts the terms of the agreement, the Operator should wet sign the agreement and return it to the LEA. Once the LEA signs the agreement, the LEA should provide a signed copy of the agreement to the Operator. Cover Page Box # 3 Official Name of Operator Cover Page Box # 4 Date Signed by Operator Recitals Box #5 Contract Title for Service Agreement Recitals Box #6 Date of Service Agreement Article 7 Boxes #7-10 Operator’s designated representative Signature Page Boxes #15-19 Authorized Operator’s representative signature Exhibit A Box #25 Description of services provided Exhibit B All Applicable Boxes Operator notates if data is collected to provide the described services. Defines the schedule of data required for the Operator to provide the services outlined in Exhibit A Exhibit D All Applicable Boxes (Optional Exhibit): Defines deletion or return of data expectations by LEA Exhibit E All Applicable Boxes (Optional Exhibit): Operator may, by signing the Form of General Offer of Privacy Terms (General Offer, attached as Exhibit E), be bound by the terms of this DPA to any other Subscribing LEA who signs the acceptance in said Exhibit. Exhibit F Boxes # 25-29 A list of all Subprocessors used by the Operator to perform functions pursuant to the Service Agreement, list security programs and measures, list Operator’s security measures
Notice of Network Changes If a Party makes a change in the information necessary for the transmission and routing of services using that Party’s facilities or network, or any other change in its facilities or network that will materially affect the interoperability of its facilities or network with the other Party’s facilities or network, the Party making the change shall publish notice of the change at least ninety (90) days in advance of such change, and shall use reasonable efforts, as commercially practicable, to publish such notice at least one hundred eighty (180) days in advance of the change; provided, however, that if an earlier publication of notice of a change is required by Applicable Law (including, but not limited to, 47 CFR 51.325 through 51. 335) notice shall be given at the time required by Applicable Law.
Hosting Services 13.1 If Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract Hosts Customer Data in connection with an Acquisition, the provisions of Appendix 1, attached hereto and incorporated herein, apply to such Acquisition.
13.2 If the Hosting of Customer Data by Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract contributes to or directly causes a Data Breach, Supplier shall be responsible for the obligations set forth in Appendix 1 related to breach reporting requirements and associated costs. Likewise if such Hosting contributes to or directly causes a Security Incident, Supplier shall be responsible for the obligations set forth in Appendix 1, as applicable. 14 Change Management
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
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.
Lost Shareholder Due Diligence Searches and Servicing The Trust hereby acknowledges that USBFS has an arrangement with an outside vendor to conduct lost shareholder searches required by Rule 17Ad-17 under the Securities Exchange Act of 1934, as amended. Costs associated with such searches will be passed through to the Trust as an out-of-pocket expense in accordance with the fee schedule set forth in Exhibit C hereto. If a shareholder remains lost and the shareholder’s account unresolved after completion of the mandatory Rule 17Ad-17 search, the Trust hereby authorizes vendor to enter, at its discretion, into fee sharing arrangements with the lost shareholder (or such lost shareholder’s representative or executor) to conduct a more in-depth search in order to locate the lost shareholder before the shareholder’s assets escheat to the applicable state. The Trust hereby acknowledges that USBFS is not a party to these arrangements and does not receive any revenue sharing or other fees relating to these arrangements. Furthermore, the Trust hereby acknowledges that vendor may receive up to 35% of the lost shareholder’s assets as compensation for its efforts in locating the lost shareholder.
