Program Monitoring and Evaluation The Recipient shall prepare, or cause to be prepared, and furnish to the Association not later than six months after the Closing Date, a report of such scope and in such detail as the Association shall reasonably request, on the execution of the Program, the performance by the Recipient and the Association of their respective obligations under the Legal Agreements and the accomplishment of the purposes of the Financing.”
Project Delivery Contractor shall construct the Project in accordance with the Contract Documents, and Contractor shall deliver the Project completed in accordance with the Contract Documents, substantially free from defects, and within the Contract Time.
Project Delivery Order Procedures Status of TIPS Members as Related to This Agreement
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.
Delivery Schedule The Goods specified in the List of Goods are required to be delivered within the acceptable time range (after the earliest and before the final date, both dates inclusive) specified in Section V, Schedule of Requirements. No credit will be given to deliveries before the earliest date, and Tenders offering delivery after the final date shall be treated as non-responsive. Within this acceptable period, an adjustment of [insert the adjustment factor], will be added, for evaluation purposes only, to the Tender price of Tenders offering deliveries later than the “Earliest Delivery Date” specified in Section V, Schedule of Requirements.
ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.
DELIVERY: FOB DESTINATION, INSIDE DELIVERY, FREIGHT PAID Whenever possible, contractors should give the ordering entities 3 working days prior notice of any deliveries and/or installations. Furniture contractors will not be responsible for the removal/moving of existing furnishings unless requested by the ordering entity. Contractors should verify site readiness prior to delivery. All deliveries will be made during normal working hours unless otherwise arranged with the ordering entity. Contractor will communicate any scheduling delays and/or changes immediately. Agencies will not be responsible for any freight damage, concealed or otherwise.
Service Delivery Grantee shall:
1. Adhere to the Priority Populations for Treatment Programs as stated in the SUD UM Guidelines.
2. Maintain Daily Capacity Management Report in CMBHS as required in the SUD UM Guidelines.
3. Maintain a Waiting List to track all eligible individuals who have been screened but cannot be admitted to SUD treatment immediately.
i. Grantee that has an individual identified as a federal and state priority population on the waiting list shall confirm this in the Daily Capacity Management Report.
ii. Grantee shall arrange for appropriate services in another treatment facility or provide access to interim services as indicated within 48 hours when efforts to refer to other appropriate services are exhausted.
iii. Grantee shall offer directly or through referral interim services to wait-listed individuals.
iv. Establish a wait list that includes priority populations and interim services while awaiting admission to treatment services.
v. Develop a mechanism to maintain contact with individuals awaiting admission.
4. If unable to provide admissions to individuals within Priority Populations for Treatment Programs according to SUD UM Guidelines:
i. Implement written procedures that address maintaining weekly contact with individuals waiting for admissions as well as what referrals are made when a client cannot be admitted for services immediately.
ii. When Grantee cannot admit a client, who is at risk for dangerous for withdrawal, Grantee shall ensure that an emergency medical care provider is notified.
iii. Coordinate with an alternate provider for immediate admission.
iv. Notify Substance Use Disorder (Xxxxxxxxx_Xxx_Xxxxxxxx@xxxx.xxxxx.xx.xx) so that assistance can be provided that ensures immediate admission to other appropriate services and proper coordination when appropriate.
v. Provide pre-admission service coordination to reduce barriers to treatment, enhance motivation, stabilize life situations, and facilitate engagement in treatment.
vi. Adhere to Informed Consent Document for Opioid Use Disorder applicable to the individual as stated in the SUD UM Guidelines.
vii. When an individual is placed on the Wait List, Grantee shall document interim services as referrals that provides applicable testing, counseling, and treatment for Human Immunodeficiency Virus (HIV), tuberculosis (TB) and sexually transmitted infections (STIs).
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.
Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives.
C.1. <Title> Deliverable 1
