Subrecipient Monitoring and Management Sample Clauses

Subrecipient Monitoring and Management. The Subrecipient acknowledges that OBO is acting as a pass- through entity for the ARPA Grant and the Subrecipient agrees to meet the requirements found in Sections 2 CFR §200.331 and §200.332 as a subrecipient as well as aid OBO upon request in its monitoring capacity by providing access to as well as any information requested by OBO for that purpose.
Sample 1Sample 2Sample 3See All (8)
AutoNDA by SimpleDocs
Subrecipient Monitoring and Management. You must monitor and manage any subrecipients in accordance with 2 CFR §§ 200.330-.332.
Sample 1Sample 2Sample 3See All (6)
Subrecipient Monitoring and Management. If Contractor is determined to be a subrecipient, Contractor agrees to: A. Provide a fiscal monitoring report which compares the contract budget per line item in relation to the monthly invoice, cumulative total invoice, and the total contract balance. The County will provide the required format. B. If applicable, conduct an annual single audit, at Contractor’s expense, according to the requirement of 2 CFR part 200, subpart F Audit Requirements, which identifies all funds granted, received, disbursed and expended. C. In adherence with 2 CFR part 200, subpart D, this Contract (subaward) must include the following information at the time of contract (subaward) execution. Significant changes to these data elements may require a modification form. 1. Subrecipient Name (which must match the name associated with its DUNS number): [Benicia Family Resource Center (FRC)] 2. Subrecipient DUNS number: [048023122] 3. Federal Award Identification Number (XXXX): [N/A] 4. Federal Award Date (date when the federal award was signed by authorized official of awarding agency): [See Contract p. 2] 5. Subaward Period of Performance Start and End Date: [See Contract p. 1] 9. Federal award project description, as required to be responsive to the Federal Funding Accountability and Transparency Act (FFATA): [N/A] 10. Name of Federal awarding agency, pass-through entity and contact information for awarding official: [U.S. Dept of Health and Human Services-California Department of Aging-Xxxxxx County-Contractor]
Sample 1Sample 2
Subrecipient Monitoring and Management. A. Pursuant to 2 C.F.R. Section 200.331 (Requirements for Pass Through Entities), the following information is applicable to Subrecipient’s Grant Award: (1) Federal Award Identification – 2019-DJ-BX-0250 (2) Subrecipient’s Name – City of Arlington (3) Subrecipient’s unique entity identifier – 000-000-000 (4) Federal Award Identification Number (XXXX) – 2019-DJ-BX-250 (5) Federal Award Date – 9/18/2019 (6) Subaward Period of Performance Start and End Date 10/01/2018 – 09/30/2022 (7) Amount of Federal Funds obligated by this action - $480,961.00 (8) Total Amount of Federal Funds obligated to the Subrecipient - $111,641.00 (9) Federal award project description - FY18 Justice Assistance Grant Collaboration with Fort Worth, Tarrant County, Arlington, and Bedford. (10) Name of Federal Awarding Agency, Pass-Through Entity – Department of Justice passed through the City of Fort Worth (11) CFDA Number and Name – 16.738 Xxxxxx Xxxxx Memorial Justice Assistance Program (12) Identification of whether the award is R&D - This award is not being utilized for research or development. (13) Indirect cost rate for the Federal award -The Subrecipient did not request reimbursement for indirect costs.
Sample 1

Related to Subrecipient Monitoring and Management

  • Contract Monitoring The criminal background checks required by this rule shall be national in scope, and must be conducted at least once every three (3) years. Contractor shall make the criminal background checks required by Paragraph IV.G.1 available for inspection and copying by DRS personnel upon request of DRS.

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity 1.1.02 Identify at least one individual to act as the program contact in the following areas: 1. Immunization Program Manager;

  • Project Management Project Management Institute (PMI) certified project manager executing any or all of the following: • Development of Project Charter • Development of project plan and schedule • Coordination and scheduling of project activities across customer and functional areas • Consultation on operational and infrastructure requirements, standards and configurations • Facilitate project status meetings • Timely project status reporting • Address project issues with functional areas and management • Escalation of significant issues to customers and executive management • Manage project scope and deliverable requirements • Document changes to project scope and schedule • Facilitate and document project closeout

  • Utilization Management Contractor shall maintain a utilization management program that complies with applicable laws, rules and regulations, including Health and Safety Code § 1367.01 and other requirements established by the applicable State Regulators responsible for oversight of Contractor.

  • Network Maintenance and Management 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result. 38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center. 38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed. 38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties. 38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events. 38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time. 38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below. 38.7.1 AT&T TENNESSEE Disaster Recovery Plan 38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases. 38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate. 38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.

  • Service Management Effective support of in-scope services is a result of maintaining consistent service levels. The following sections provide relevant details on service availability, monitoring of in-scope services and related components.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!