Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.
Account Verification Whether or not a Default or Event of Default exists, Agent shall have the right at any time, in the name of Agent, any designee of Agent or any Borrower, to verify the validity, amount or any other matter relating to any Accounts of Borrowers by mail, telephone or otherwise. Borrowers shall cooperate fully with Agent in an effort to facilitate and promptly conclude any such verification process.
TECHNICAL EVALUATION (a) Detailed technical evaluation shall be carried out by Purchase Committee pursuant to conditions in the tender document to determine the substantial responsiveness of each tender. For this clause, the substantially responsive bid is one that conforms to all the eligibility and terms and condition of the tender without any material deviation. The Institute’s determination of bid’s responsiveness is to be based on the contents of the bid itself without recourse to extrinsic evidence. The Institute shall evaluate the technical bids also to determine whether they are complete, whether required sureties have been furnished, whether the documents have been properly signed and whether the bids are in order.
(b) The technical evaluation committee may call the responsive bidders for discussion or presentation to facilitate and assess their understanding of the scope of work and its execution. However, the committee shall have sole discretion to call for discussion / presentation.
(c) Financial bids of only those bidders who qualify the technical criteria will be opened provided all other requirements are fulfilled.
(d) AIIMS Jodhpur shall have right to accept or reject any or all tenders without assigning any reasons thereof.
How to Update Your Records You agree to promptly update your registration records if your e-mail address or other information changes. You may update your records, such as your e-mail address, by using the Profile page.
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.
Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.
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.
FINAL BILLING SUBMISSION Unless otherwise provided by the System Agency, Grantee shall submit a reimbursement or payment request as a final close-out invoice not later than forty-five (45) calendar days following the end of the term of the Contract. Reimbursement or payment requests received after the deadline may not be paid.
Program Evaluation The School District and the College will develop a plan for the evaluation of the Dual Credit program to be completed each year. The evaluation will include, but is not limited to, disaggregated attendance and retention rates, GPA of high-school-credit-only courses and college courses, satisfactory progress in college courses, state assessment results, SAT/ACT, as applicable, TSIA readiness by grade level, and adequate progress toward the college-readiness of the students in the program. The School District commits to collecting longitudinal data as specified by the College, and making data and performance outcomes available to the College upon request. HB 1638 and SACSCOC require the collection of data points to be longitudinally captured by the School District, in collaboration with the College, will include, at minimum: student enrollment, GPA, retention, persistence, completion, transfer and scholarships. School District will provide parent contact and demographic information to the College upon request for targeted marketing of degree completion or workforce development information to parents of Students. School District agrees to obtain valid FERPA releases drafted to support the supply of such data if deemed required by counsel to either School District or the College. The College conducts and reports regular and ongoing evaluations of the Dual Credit program effectiveness and uses the results for continuous improvement.
Statement of Grievance The grievance shall contain a statement of:
1. Specific situation, act or acts complained of as violation of this Agreement, or written rules, regulations or policies;
2. The damage suffered by the employee; and
3. The relief sought.
