NOTICE TO MEMBERS REGARDING ATTRIBUTE RESPONSES TIPS VENDORS RESPOND TO ATTRIBUTE QUESTIONS AS PART OF TIPS COMPETITIVE SOLICITATION PROCESS. THE VENDOR’S RESPONSES TO ATTRIBUTE QUESTIONS ARE INCLUDED HEREIN AS “SUPPLIER RESPONSE.” PLEASE BE ADVISED THAT DEVIATIONS, IF ANY, IN VENDOR’S RESPONSE TO ATTRIBUTE QUESTIONS MAY NOT REFLECT VENDOR’S FINAL ATTRIBUTE RESPONSE, WHICH IS SUBJECT TO NEGOTIATIONS PRIOR TO AWARD. PLEASE CONTACT THE TIPS OFFICE AT 866-839- 8477 WITH QUESTIONS OR CONCERNS REGARDING VENDOR ATTRIBUTE RESPONSE DEVIATIONS. PLEASE KEEP IN MIND THAT TIPS DOES NOT PROVIDE LEGAL COUNSEL TO MEMBERS. TIPS RECOMMENDS THAT YOU CONSULT YOUR LEGAL COUNSEL WHEN EXECUTING CONTRACTS WITH OR MAKING PURCHASES FROM TIPS VENDORS. Number: 220105 Addendum 1 Title: Technology Solutions, Products and Services Type: Request for Proposal Issue Date: 1/6/2022 Deadline: 2/18/2022 03:00 PM (CT) Notes: I F YO U ALREAD Y HOL D TIP S CONTRAC T 200105 TECHNOLOGY SOLUTIONS, PRODUCTS AND SERVICES (“200105”) OR 210101 TECHNOLOGY SOLUTIONS, PRODUCTS AND SERVICES ("210101"), YOU DO NOT NEED TO RESPOND TO THIS SOLICITATION UNLESS YOU WISH TO REPLACE 200105 OR 210101 AT THIS TIME. IF YOU HOLD 200105 OR ꞏ TIPS 190103 Web and Cloud Computing Services ꞏ TIPS 181203 Management Software and Services ꞏ TIPS 181204 Notification Systems Address: Region 8 Education Service Center 0000 XX Xxxxxxx 000 Xxxxx Xxxxxxxxx, XX 00000 Phone: +0 (000) 000-0000 Email: xxxx@xxxx-xxx.xxx Address: 000 X XXX 00 Xxxxx 00 Xxxxxxxxxx, XX 00000 Phone: (000) 000-0000 Web Address: xxxxxxxxxxxxx.xxx By submitting your response, you certify that you are authorized to represent and bind your company. If you have not taken exception or deviation to the agreement language in the solicitation attributes, download the AGREEMENT SIGNATURE FORM from the "ATTACHMENTS" tab. This PDF document is a fillable form. Download the document to your computer, fill in the requested company information, print the file, SIGN the form, SCAN the completed and signed AGREEMENT SIGNATURE FORM, and upload here. If you have taken exception to any of the agreement language and noted the exception in the deviations section of the attributes for the agreement, complete the AGREEMENT SIGNATURE FORM, but DO NOT SIGN until those deviations have been negotiated and resolved with TIPS management. Upload the unsigned form here, because this is a required document. All Other Certificates (if applicable) must be scanned and uploaded. If vendor has more than one other certification scan into one document. (PDF Format ONLY) DO NOT UPLOAD encrypted or password protected files. The vendor must download the PRICING SPREADSHEET SHEET from the attachment tab, fill in the requested information and upload the completed spreadsheet. DO NOT UPLOAD encrypted or password protected files.
Alternative Dispute Resolution Limitations This is a requirement of the TIPS Contract and is non-negotiable. No Waiver of TIPS Immunity This is a requirement of the TIPS Contract and is non-negotiable. 5 5 Payment Terms and Funding Out Clause This is a requirement of the TIPS Contract and is non-negotiable. 6
Dispute Resolution Mechanisms Registry Operator will comply with the following dispute resolution mechanisms as they may be revised from time to time: the Trademark Post-Delegation Dispute Resolution Procedure (PDDRP) and the Registration Restriction Dispute Resolution Procedure (RRDRP) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/pddrp and xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp, respectively). Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PDDRP or RRDRP panel and to be bound by any such determination; and the Uniform Rapid Suspension system (“URS”) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/urs), including the implementation of determinations issued by URS examiners. CONTINUED OPERATIONS INSTRUMENT The Continued Operations Instrument shall (a) provide for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period of one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6th) anniversary of the Effective Date, and (b) be in the form of either (i) an irrevocable standby letter of credit, or (ii) an irrevocable cash escrow deposit, each meeting the requirements set forth in item 50(b) of Attachment to Module 2 – Evaluation Questions and Criteria – of the gTLD Applicant Guidebook, as published and supplemented by ICANN prior to the date hereof (which is hereby incorporated by reference into this Specification 8). Registry Operator shall use its best efforts to take all actions necessary or advisable to maintain in effect the Continued Operations Instrument for a period of six (6) years from the Effective Date, and to maintain ICANN as a third party beneficiary thereof. If Registry Operator elects to obtain an irrevocable standby letter of credit but the term required above is unobtainable, Registry Operator may obtain a letter of credit with a one-year term and an “evergreen provision,” providing for annual extensions, without amendment, for an indefinite number of additional periods until the issuing bank informs ICANN of its final expiration or until ICANN releases the letter of credit as evidenced in writing, if the letter of credit otherwise meets the requirements set forth in item 50(b) of Attachment to Module 2 – Evaluation Questions and Criteria – of the gTLD Applicant Guidebook, as published and supplemented by ICANN prior to the date hereof; provided, however, that if the issuing bank informs ICANN of the expiration of such letter of credit prior to the sixth (6th) anniversary of the Effective Date, such letter of credit must provide that ICANN is entitled to draw the funds secured by the letter of credit prior to such expiration. The letter of credit must require the issuing bank to give ICANN at least thirty (30) calendar days’ notice of any such expiration or non-renewal. If the letter of credit expires or is terminated at any time prior to the sixth (6th) anniversary of the Effective Date, Registry Operator will be required to obtain a replacement Continued Operations Instrument. ICANN may draw the funds under the original letter of credit, if the replacement Continued Operations Instrument is not in place prior to the expiration of the original letter of credit. Registry Operator shall provide to ICANN copies of all final documents relating to the Continued Operations Instrument and shall keep ICANN reasonably informed of material developments relating to the Continued Operations Instrument. Registry Operator shall not agree to, or permit, any amendment of, or waiver under, the Continued Operations Instrument or other documentation relating thereto without the prior written consent of ICANN (such consent not to be unreasonably withheld). If, notwithstanding the use of best efforts by Registry Operator to satisfy its obligations under the preceding paragraph, the Continued Operations Instrument expires or is terminated by another party thereto, in whole or in part, for any reason, prior to the sixth anniversary of the Effective Date, Registry Operator shall promptly (i) notify ICANN of such expiration or termination and the reasons therefor and (ii) arrange for an alternative instrument that provides for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period of one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6) anniversary of the Effective Date (an “Alternative Instrument”). Any such Alternative Instrument shall be on terms no less favorable to ICANN than the Continued Operations Instrument and shall otherwise be in form and substance reasonably acceptable to ICANN. Notwithstanding anything to the contrary contained in this Specification 8, at any time, Registry Operator may replace the Continued Operations Instrument with an Alternative Instrument that (i) provides for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6) anniversary of the Effective Date, and (ii) contains terms no less favorable to ICANN than the Continued Operations Instrument and is otherwise in form and substance reasonably acceptable to ICANN. In the event Registry Operator replaces the Continued Operations Instrument either pursuant to paragraph 2 or this paragraph 3, the terms of this Specification 8 shall no longer apply with respect to the original Continuing Operations Instrument, but shall thereafter apply with respect to such Alternative Instrument(s), and such instrument shall thereafter be considered the Continued Operations Instrument for purposes of this Agreement. REGISTRY OPERATOR CODE OF CONDUCT In connection with the operation of the registry for the TLD, Registry Operator will not, and will not allow any parent, subsidiary, Affiliate, subcontractor or other related entity, to the extent such party is engaged in the provision of Registry Services with respect to the TLD (each, a “Registry Related Party”), to: directly or indirectly show any preference or provide any special consideration to any registrar with respect to operational access to registry systems and related registry services, unless comparable opportunities to qualify for such preferences or considerations are made available to all registrars on substantially similar terms and subject to substantially similar conditions; register domain names in its own right, except for names registered through an ICANN accredited registrar; provided, however, that Registry Operator may (a) reserve names from registration pursuant to Section 2.6 of the Agreement and (b) may withhold from registration or allocate to Registry Operator up to one hundred (100) names pursuant to Section 3.2 of Specification 5; register names in the TLD or sub-domains of the TLD based upon proprietary access to information about searches or resolution requests by consumers for domain names not yet registered (commonly known as, “front-running”); or allow any Affiliated registrar to disclose Personal Data about registrants to Registry Operator or any Registry Related Party, except as reasonably necessary for the management and operations of the TLD, unless all unrelated third parties (including other registry operators) are given equivalent access to such user data on substantially similar terms and subject to substantially similar conditions. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will, or will cause such Registry Related Party to, ensure that such services are offered through a legal entity separate from Registry Operator, and maintain separate books of accounts with respect to its registrar or registrar-reseller operations. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will conduct internal reviews at least once per calendar year to ensure compliance with this Code of Conduct. Within twenty (20) calendar days following the end of each calendar year, Registry Operator will provide the results of the internal review, along with a certification executed by an executive officer of Registry Operator certifying as to Registry Operator’s compliance with this Code of Conduct, via email to an address to be provided by ICANN. (ICANN may specify in the future the form and contents of such reports or that the reports be delivered by other reasonable means.) Registry Operator agrees that ICANN may publicly post such results and certification; provided, however, ICANN shall not disclose Confidential Information contained in such results except in accordance with Section 7.15 of the Agreement. Nothing set forth herein shall: (i) limit ICANN from conducting investigations of claims of Registry Operator’s non-compliance with this Code of Conduct; or (ii) provide grounds for Registry Operator to refuse to cooperate with ICANN investigations of claims of Registry Operator’s non-compliance with this Code of Conduct. Nothing set forth herein shall limit the ability of Registry Operator or any Registry Related Party, to enter into arms-length transactions in the ordinary course of business with a registrar or reseller with respect to products and services unrelated in all respects to the TLD. Registry Operator may request an exemption to this Code of Conduct, and such exemption may be granted by ICANN in ICANN’s reasonable discretion, if Registry Operator demonstrates to ICANN’s reasonable satisfaction that (i) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator for the exclusive use of Registry Operator or its Affiliates, (ii) Registry Operator does not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an Affiliate of Registry Operator, and (iii) application of this Code of Conduct to the TLD is not necessary to protect the public interest. REGISTRY PERFORMANCE SPECIFICATIONS DNS. Refers to the Domain Name System as specified in RFCs 1034, 1035, and related RFCs. DNSSEC proper resolution. There is a valid DNSSEC chain of trust from the root trust anchor to a particular domain name, e.g., a TLD, a domain name registered under a TLD, etc.
Customer Service, Dispute Resolution If you have a question about your XOOM charges or service you may contact XOOM directly by calling 0-000-000-0000 Monday – Friday 8 (eight) a.m. to 11 (eleven)p.m.
Dispute Resolution Procedures (a) In the event a dispute arises about the interpretation, application, calculation of Loss, or calculation of payments or otherwise with respect to this Single Family Shared-Loss Agreement (“SF Shared-Loss Dispute Item”), then the Receiver and the Assuming Institution shall make every attempt in good faith to resolve such items within sixty (60) days following the receipt of a written description of the SF Shared-Loss Dispute Item, with notification of the possibility of taking the matter to arbitration (the date on which such 60-day period expires, or any extension of such period as the parties hereto may mutually agree to in writing, herein called the “Resolution Deadline Date”). If the Receiver and the Assuming Institution resolve all such items to their mutual satisfaction by the Resolution Deadline Date, then within thirty (30) days following such resolution, any payment due as a result of such resolution shall be made arising from the settlement of the SF Shared-Loss Dispute.
(b) If the Receiver and the Assuming Institution fail to resolve any outstanding SF Shared-Loss Dispute Items by the Resolution Deadline Date, then either party may notify the other of its intent to submit the SF Shared-Loss Dispute Item to arbitration pursuant to the provisions of this Article VII. Failure of either party to submit pursuant to paragraph (c) hereof any unresolved SF Shared-Loss Dispute Item to arbitration within thirty (30) days following the Resolution Deadline Date (the date on which such thirty (30) day period expires is herein called the “Arbitration Deadline Date”) shall extinguish that party’s right to submit the non-submitted SF Shared-Loss Dispute Item to arbitration, and constitute a waiver of the submitting party’s right to dispute such non-submitted SF Shared-Loss Dispute Item (but not a waiver of any similar claim which may arise in the future).
(c) If a SF Shared-Loss Dispute Item is submitted to arbitration, it shall be governed by the rules of the American Arbitration Association (the “AAA”), except as otherwise provided herein. Either party may submit a matter for arbitration by delivering a notice, prior to the Arbitration Deadline Date, to the other party in writing setting forth:
(i) A brief description of each SF Shared-Loss Dispute Item submitted for arbitration;
(ii) A statement of the moving party’s position with respect to each SF Shared-Loss Dispute Item submitted for arbitration;
(iii) The value sought by the moving party, or other relief requested regarding each SF Shared-Loss Dispute Item submitted for arbitration, to the extent reasonably calculable; and
(iv) The name and address of the arbiter selected by the moving party (the “Moving Arbiter”), who shall be a neutral, as determined by the AAA. Failure to adequately include any information above shall not be deemed to be a waiver of the parties right to arbitrate so long as after notification of such failure the moving party cures such failure as promptly as reasonably practicable.
(d) The non-moving party shall, within thirty (30) days following receipt of a notice of arbitration pursuant to this Section 7.1, deliver a notice to the moving party setting forth:
(i) The name and address of the arbiter selected by the non-moving party (the “Respondent Arbiter”), who shall be a neutral, as determined by the AAA;
(ii) A statement of the position of the respondent with respect to each Dispute Item; and
(iii) The ultimate resolution sought by the respondent or other relief, if any, the respondent deems is due the moving party with respect to each SF Shared-Loss Dispute Item. Failure to adequately include any information above shall not be deemed to be a waiver of the non-moving party’s right to defend such arbitration so long as after notification of such failure the non-moving party cures such failure as promptly as reasonably practicable
(e) The Moving Arbiter and Respondent Arbiter shall select a third arbiter from a list furnished by the AAA. In accordance with the rules of the AAA, the three (3) arbiters shall constitute the arbitration panel for resolution of each SF Loss-Share Dispute Item. The concurrence of any two (2) arbiters shall be deemed to be the decision of the arbiters for all purposes hereunder. The arbitration shall proceed on such time schedule and in accordance with the Rules of Commercial Arbitration of the AAA then in effect, as modified by this Section 7.1. The arbitration proceedings shall take place at such location as the parties thereto may mutually agree, but if they cannot agree, then they will take place at the offices of the Corporation in Washington, DC, or Arlington, Virginia.
(f) The Receiver and Assuming Institution shall facilitate the resolution of each outstanding SF Shared-Loss Dispute Item by making available in a prompt and timely manner to one another and to the arbiters for examination and copying, as appropriate, all documents, books, and records under their respective control and that would be discoverable under the Federal Rules of Civil Procedure.
Dispute Resolution All or any disputes arising out or touching upon or in relation to the terms and conditions of this Agreement, including the interpretation and validity of the terms thereof and the respective rights and obligations of the Parties, shall be settled amicably by mutual discussion, failing which the same shall be settled through the adjudicating officer appointed under the Act.
Dispute Resolution Procedure 21.1 All disputes or grievances arising between the Parties shall as far as practical be resolved at the workplace level through consultation. Accordingly the following procedure must be followed:
21.1.1 Initially the Employee shall discuss any grievance, dispute or claim with their immediate supervisor;
21.1.2 If the matter is not resolved at such a meeting, the Parties may hold further discussions with appropriate senior levels of management;
21.1.3 If the matter cannot be resolved at the workplace level, the Parties agree to refer the matter to Enterprise Initiatives Pty Ltd who will engage a third party mediator to mediate the dispute. Any such mediator will conduct the mediation in accordance with the provisions of Part 13, Division 6 of the Act.
21.2 To the extent that the dispute concerns Employee entitlements or Employer obligations under the Agreement the Employer will ask for the Employee's agreement to seek advice from EI Legal Pty Ltd.
21.3 This dispute resolution procedure does not apply to Employees where the Employer has given notice and reasons for termination according to clause 5 of the Agreement.
21.4 Where the Parties agree to pursue mediation the Parties:-
21.4.1 Will participate in the mediation process in good faith;
21.4.2 Acknowledge the right of other to appoint in writing, another person to act on their behalf in relation to the mediation process;
21.4.3 Agree not to commence any action against the other; and
21.4.4 Agree that during the time when the Parties attempt to resolve the matter:
i) the Parties continue to work in accordance with the contract of employment unless the Employee has a reasonable concern about an imminent risk to his or her health or safety; and
ii) subject to relevant provisions of any state or territory occupational safety law, even if the Employee has a reasonable concern about an imminent risk to his or her health or safety, the Employee must not unreasonably fail to comply with a direction by his or her Employer to perform other available work, whether at the same workplace or another workplace, that is safe and appropriate for the Employee to perform; and
iii) the Parties must cooperate to ensure that the dispute resolution procedures are carried out as quickly as is reasonably possible.
Alternative Dispute Resolution Prior to filing of litigation, the parties may select non-binding mediation as a method of conflict resolution for issues arising out of or relating to this procurement process or any contract resulting from or any contemplated transaction. The parties agree that if non-binding mediation is chosen as a resolution process, the parties must agree to the chosen mediator(s) and that all mediation venue shall be at a location in Xxx Xxxxx County, Texas or agreed by the parties. The parties agree to share equally the cost of the mediation process and venue cost.
Dispute Resolutions Parties agree to arbitration of dispute in Houston, Texas, USA.
BREACH DISCOVERY AND NOTIFICATION 17 1. Following the discovery of a Breach of Unsecured PHI, CONTRACTOR shall notify 18 COUNTY of such Breach, however both parties agree to a delay in the notification if so advised by a 19 law enforcement official pursuant to 45 CFR § 164.412.
20 a. A Breach shall be treated as discovered by CONTRACTOR as of the first day on which 21 such Breach is known to CONTRACTOR or, by exercising reasonable diligence, would have been 22 known to CONTRACTOR.
23 b. CONTRACTOR shall be deemed to have knowledge of a Breach, if the Breach is 24 known, or by exercising reasonable diligence would have known, to any person who is an employee, 25 officer, or other agent of CONTRACTOR, as determined by federal common law of agency.
26 2. CONTRACTOR shall provide the notification of the Breach immediately to the COUNTY 27 Privacy Officer. CONTRACTOR’s notification may be oral, but shall be followed by written 28 notification within twenty four (24) hours of the oral notification.
29 3. CONTRACTOR’s notification shall include, to the extent possible:
30 a. The identification of each Individual whose Unsecured PHI has been, or is reasonably 31 believed by CONTRACTOR to have been, accessed, acquired, used, or disclosed during the Breach;
32 b. Any other information that COUNTY is required to include in the notification to 33 Individual under 45 CFR §164.404 (c) at the time CONTRACTOR is required to notify COUNTY or 34 promptly thereafter as this information becomes available, even after the regulatory sixty (60) day 35 period set forth in 45 CFR § 164.410 (b) has elapsed, including:
36 1) A brief description of what happened, including the date of the Breach and the date 37 of the discovery of the Breach, if known;
1 2) A description of the types of Unsecured PHI that were involved in the Breach (such 2 as whether full name, social security number, date of birth, home address, account number, diagnosis, 3 disability code, or other types of information were involved);
4 3) Any steps Individuals should take to protect themselves from potential harm 5 resulting from the Breach;
6 4) A brief description of what CONTRACTOR is doing to investigate the Breach, to 7 mitigate harm to Individuals, and to protect against any future Breaches; and
8 5) Contact procedures for Individuals to ask questions or learn additional information, 9 which shall include a toll-free telephone number, an e-mail address, Web site, or postal address.
10 4. COUNTY may require CONTRACTOR to provide notice to the Individual as required in 11 45 CFR § 164.404, if it is reasonable to do so under the circumstances, at the sole discretion of the 12 COUNTY.
13 5. In the event that CONTRACTOR is responsible for a Breach of Unsecured PHI in violation 14 of the HIPAA Privacy Rule, CONTRACTOR shall have the burden of demonstrating that 15 CONTRACTOR made all notifications to COUNTY consistent with this Subparagraph F and as 16 required by the Breach notification regulations, or, in the alternative, that the acquisition, access, use, or 17 disclosure of PHI did not constitute a Breach.
18 6. CONTRACTOR shall maintain documentation of all required notifications of a Breach or 19 its risk assessment under 45 CFR § 164.402 to demonstrate that a Breach did not occur.
20 7. CONTRACTOR shall provide to COUNTY all specific and pertinent information about the 21 Breach, including the information listed in Section E.3.b.(1)-(5) above, if not yet provided, to permit 22 COUNTY to meet its notification obligations under Subpart D of 45 CFR Part 164 as soon as 23 practicable, but in no event later than fifteen (15) calendar days after CONTRACTOR’s initial report of 24 the Breach to COUNTY pursuant to Subparagraph F.2. above.
25 8. CONTRACTOR shall continue to provide all additional pertinent information about the
