Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.
Not an Authoritative Copy With respect to Contracts that are “electronic chattel paper”, the Servicer has marked all copies of each such Contract other than an authoritative copy with a legend to the following effect: “This is not an authoritative copy.”
Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.
ELECTRONIC SUBMITTALS Contractor shall obtain a license for the State to utilize Submittal Exchange for the purposes of this project. The State and its representatives will have full control of the use of Submittal Exchange by authorized users of the State.
ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to TWTC via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN. If AT&T determines the Secure FTP Mailbox is nearing capacity levels, AT&T may move the customer to CONNECT: Direct file delivery. 6.2.2 If the customer is moved, CONNECT: Direct data circuits (private line or dial-up) will be required between AT&T and TWTC for the purpose of data transmission. Where a dedicated line is required, TWTC will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with AT&T. TWTC will also be responsible for any charges associated with this line. Equipment required on the AT&T end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be TWTC's responsibility. Where a dial-up facility is required, dial circuits will be installed in the AT&T data center by AT&T and the associated charges assessed to TWTC. Additionally, all message toll charges associated with the use of the dial circuit by TWTC will be the responsibility of TWTC. Associated equipment on the AT&T end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on TWTC end for the purpose of data transmission will be the responsibility of TWTC. 6.2.3 If TWTC utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of TWTC.
Electronic Visit Verification ("EVV A. To ensure: 1. the EVV system is used to verify the provision of services governed under 40 TAC, Chapter 68 or its successor; 2. only authorized people access the Contractor's EVV account; 3. all data elements required by HHSC or HHSC's designee are uploaded or entered and maintained in the EVV system completely, accurately, and prior to submitting the claim; 4. that each time services governed by 40 TAC Chapter 68 or its successor are delivered to an individual, the Contractor's staff uses an HHSC-approved EVV system; and 5. service delivery documentation is immediately available for review by HHSC when requested. B. Equipment provided to Contractor by HHSC, HHSC’s designee, or an HHSC-approved EVV vendor, must be returned in good condition when the equipment is no longer needed under this Contract. In the context of this agreement, “good condition” means Contractor must not place any marks or identifying information on the equipment and may not alter information on the equipment including logos and serial numbers. If the equipment is lost, stolen, marked, altered or damaged by Contractor, Contractor may be required to pay the replacement cost for each piece of equipment that is lost, stolen, marked or damaged. Replacement costs for lost, stolen, marked or damaged equipment may be assessed periodically. If Contractor recovers previously lost or stolen equipment for which Contractor paid the replacement cost in the prior 12 months, Contractor may return the equipment and be reimbursed for the replacement costs within 12 months of the date HHSC, HHSC’s designee or an HHSC-approved EVV vendor (as applicable) received payment in full from the Contractor. This is provided the equipment is returned in good condition as specified above. C. HHSC may perform EVV compliance oversight reviews to determine if Contractor has complied with EVV compliance requirements as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC EVV website or EVV Policy Handbook. D. If the Contractor determines an electronic record in the EVV system needs to be adjusted at any time, the Contractor will make the adjustment in the EVV system using the most appropriate EVV reason code number(s), EVV reason code description(s) and enter any required free text when completing visit maintenance in the EVV system, if applicable. E. Contractor must begin using an HHSC-approved EVV system prior to submitting an EVV relevant claim. F. All claims for services required to use EVV (EVV claims) must match to an accepted EVV visit transaction in the EVV Aggregator (the state’s centralized EVV database) prior to reimbursement of an EVV claim. Without a matching accepted EVV visit transaction, the claim will be denied. G. Contractor must submit all EVV related claims through the Texas Medicaid Claims Administrator, or as otherwise described in the EVV Policy posted on the HHSC EVV website or in the EVV Policy Handbook. H. Contractor must complete all required EVV training as outlined in the EVV Policy posted on the HHSC EVV website or EVV Policy Handbook: • Prior to using either an EVV vendor system or an EVV proprietary system and • Yearly thereafter. I. Contractor and, if applicable, the Contractor’s appointed EVV system administrator, must complete, sign and date the EVV Onboarding Form as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC website or EVV Policy Handbook.
ELECTRONIC SUBMISSIONS Concessionaire must have the capacity to send and receive electronic submissions and communications as a pre-condition and continuing requirement of this Agreement. For purposes of this Agreement, “Electronic Submissions” shall only include the transmission of documents by email. Concessionaire shall comply with the following terms and conditions: A. Concessionaire shall electronically submit all reports, including, but not limited to, Monthly Reports and Annual Reports as described in Paragraphs 12 and 13, by email to: XxxxxxxxXxxxxx@xxx.xx.xxx. Failure on the part of Concessionaire to submit reports electronically shall be a material breach of this Agreement, subject to Suspension of Operations and/or Termination in accordance with the terms and conditions set forth in Paragraphs 9 and 10. B. Concessionaire shall maintain and monitor on a daily basis an active email address, designated for this Agreement and report any change to the email address during any Term of this Agreement. Failure on the part of Concessionaire to maintain and monitor the active email address, designated for this Agreement, shall be a material breach of this Agreement, subject to Suspension of Operations and/or Termination in accordance with the terms and conditions set forth in Paragraphs 9 and 10.
zone Information Publication ICANN’s publication of root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
Physical File Characteristics 7.2.1 The EODUF feed will be distributed to Comcast Phone over their existing Optional Daily Usage File (ODUF) feed. The EODUF messages will be intermingled among Comcast Phone’s Optional Daily Usage File (ODUF) messages. The EODUF will be a variable block format (2476) with an LRECL of 2472. The data on the EODUF will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). 7.2.2 Data circuits (private line or dial-up) may be required between BellSouth and Comcast Phone for the purpose of data transmission. Where a dedicated line is required, Comcast Phone will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. Comcast Phone will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit successfully ongoing will be negotiated on an individual case basis. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to Comcast Phone. Additionally, all message toll charges associated with the use of the dial circuit by Comcast Phone will be the responsibility of Comcast Phone. Associated equipment on the BellSouth end, including a modem, will be negotiated on an individual case basis between the Parties. Version 4Q01 12/01/01 All equipment, including modems and software, that is required on Comcast Phone’s end for the purpose of data transmission will be the responsibility of Comcast Phone.
POST ONLINE PUBLIC AUCTION PROCEDURES 4.1. Successful E-bidders shall and undertake to sign the Memorandum of Sale at the office of the Auctioneer within 3 working days from the date of auction, failing which the deposit paid will be forfeited to the Assignee bank and the sale will be deemed cancelled/terminated and the property may be put up again for subsequent auction without further notice to the said E-Bidders. The Auctioneer shall send the Memorandum of Sale for stamping and thereafter forward the same together with the required deposit paid under Clause 2.4 above and the differential sum paid under this clause (if any) to the Assignee bank. 4.2. Any successful E-bidder who is unable to attend to sign the Memorandum of Sale at the Auctioneer's office may do so by authorising another person to sign the same of his/her behalf by inserting the particulars of the authorised person and furnishing a copy of his/her identity card and also a Letter of Authorisation for this purpose. 4.3. In the event that there is inconsistency between the personal details and the documents uploaded in the PAH Website and the actual documents produced by the successful bidder, the Auctioneer shall have the right to refuse the successful bidder from signing the Memorandum of Sale and may at its discretion cancel the sale and proceed to put up property up for a new auction and the deposit paid shall be forfeited. 4.4. The Memorandum of Sale upon being signed by the Auctioneer, Solicitor for the Assignee bank and the successful Bidder/Authorised agent shall be conclusive evidence of the sale of the property to the successful bidder.
