Mission Ready Packages Sample Clauses

Mission Ready Packages. The function of a Mission Ready Package (MRP) is to succinctly describe all the resources and support needed for an emergency response and to facilitate requests across states to ensure the recipient is getting the support needed to address a response. An MRP details the task and purpose of the emergency response, required support, equipment, special instructions, and cost, among others. This allows responders to efficiently mobilize, track resources, and budget. Moreover, following a response, an MRP can also ensure timely reimbursement. Three Mission Ready Packages were created for the HPAI response effort, specifically for decontamination, depopulation and disposal (Appendix D). These were developed following meetings with GDA staff, including the GDA Director of Emergency Management and Rapid Response Team Program Manager, and livestock poultry field staff that will work directly in the field during an HPAI response. The creation of these documents will allow for a more organized and efficient response, which is critical during an HPAI outbreak, and can be added to the HPAI response plan as support tools for the State of Georgia.
Sample 1
AutoNDA by SimpleDocs

Related to Mission Ready Packages

  • Delivery Schedule The scheduled months of delivery of the Aircraft are listed in the attached Table 1. Exhibit B describes certain responsibilities for both Customer and Boeing in order to accomplish the delivery of the Aircraft.

  • Project Completion Report At the completion of construction and once a Project is placed in service, the Subrecipient must submit a Project Completion Report that includes the total number of units built and leased, affordable units built and leased, DR-MHP units built and leased, an accomplishment narrative, and the tenants names, demographics and income for each DR-MHP unit.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Project Reports; Completion Report 1. The Recipient shall monitor and evaluate the progress of the Project and prepare Project Reports in accordance with the provisions of Section 2.06 of the Standard Conditions and on the basis of indicators agreed with the World Bank. Each Project Report shall cover the period of one (1) calendar semester, and shall be furnished to the World Bank not later than one (1) month after the end of the period covered by such report.

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • Project Delivery Order Procedures The TIPS Member having approved and signed an interlocal agreement, or other TIPS Membership document, may make a request of the awarded Vendor under this Agreement when the TIPS Member desires goods or services awarded to the Vendor. Notification may occur via phone, the web, courier, email, fax, or in person. Upon notification of a pending request, the awarded Vendor shall acknowledge the TIPS Member’s request as soon as possible, but must make contact with the TIPS Member within two working days. Status of TIPS Members as Related to This Agreement TIPS Members stand in the place of TIPS as related to this agreement and have the same access to the proposal information and all related documents. TIPS Members have all the same rights under the awarded Agreement as TIPS.

  • Construction Progress Schedule; Overall Project Schedule The Contractor shall submit for review by the Design Professional and approval by the Owner a Construction Progress Schedule based upon the Design Professional’s Preliminary Design and Construction Schedule and prepared using a CPM (Critical Path Method) process within sixty days after the Effective Date of the Contract, utilizing a full-featured software package in a form satisfactory to the Design Professional and Owner, showing the dates for commencement and completion of the Work required by the Contract Documents, including coordination of mechanical, plumbing, and electrical disciplines, as well as coordination of the various subdivisions of the Work within the Contract. Milestones must be clearly indicated and sequentially organized to identify the critical path of the Project. The Construction Schedule will be developed to represent the CSI specification divisions. It shall have the minimum number of activities required to adequately represent to the Owner the complete scope of Work and define the Project’s (and each Phase’s if phased) critical path and associated activities. The format of the Construction Progress Schedule will have dependencies indicated on a monthly grid identifying milestone dates such as construction start, phase construction, structural top out, dry-in, rough-in completion, metal stud and drywall completion, equipment installation, systems operational, inspections for Material Completion and Occupancy Date, and Final Completion Date. The Contractor shall submit, along with the Construction Progress Schedule, the Submittal Schedule for approval by the Design Professional, correlating the associated approval dates for the documents with the Construction Progress Schedule. Upon recommendation by the Design Professional and approval by the Owner, the Construction Progress Schedule shall become the Overall Project Schedule, which shall be utilized by the Design Professional, Owner and Contractor. The Contractor must provide the Design Professional and the Owner with monthly updates of the Overall Project Schedule indicating completed activities and any changes in sequencing or activity durations, including approved change orders. See also Article 3.3.5.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • Vehicle Base Specifications Note: The actual vehicle awarded may exceed the minimum specifications stated below. The Authorized User may elect to add additional Options, delete Options, or substitute a vehicle feature that is an Option with another Option. See Contract Section III.6

Time is Money Join Law Insider Premium to draft better contracts faster.