Requirements for Small Unmanned Aircraft System Sample Clauses

Requirements for Small Unmanned Aircraft System. All requests to purchase Small Unmanned Aircraft System (SUAS) must comply with Information Bulletin (IB) 426 and must include the policies and procedures in place to safeguard individuals’ privacy, civil rights, and civil liberties in the jurisdiction that will purchase, take title to, or otherwise use the SUAS equipment.
Sample 1Sample 2Sample 3See All (16)
AutoNDA by SimpleDocs
Requirements for Small Unmanned Aircraft System. (SHSP, UASI, and OPSG) All requests to purchase Small Unmanned Aircraft Systems (SUAS) with FEMA grant funding must comply with IB 426 and IB 438 and include a description of the policies and procedures in place to safeguard individuals’ privacy, civil rights, and civil liberties of the jurisdiction that will purchase, take title to or otherwise use the SUAS equipment.
Sample 1Sample 2
Requirements for Small Unmanned Aircraft System. All requests to purchase Small Unmanned Aircraft System (SUAS) must comply with Information Bulletin (IB) 426 and must include the policies and procedures in place to safeguard individuals’ privacy, civil rights, and civil liberties in the jurisdiction that will purchase, take title to, or otherwise use the SUAS equipment. Funding for Critical Emergency Supplies Critical emergency supplies—such as shelf stable products, water, and basic medical supplies—are an allowable expense under EMPG. DHS/FEMA must approve a state’s five-year viable inventory management plan prior to allocating grant funds for stockpiling purposes. The five-year plan should include a distribution strategy and related sustainment costs if the grant expenditure is over $100,000. Equipment Acquisition Costs Supporting Documentation: Provide copies of invoices, receipts and cancelled checks, credit card statements, bank statements for proof of payment. Provide the Authorized Equipment List (AEL) # for each equipment purchase.
Sample 1Sample 2
Requirements for Small Unmanned Aircraft System. All requests to purchase Small Unmanned Aircraft System (SUAS) with FEMA grant funding must also include the policies and procedures in place to safeguard individuals’ privacy, civil rights, and civil liberties of the jurisdiction that will purchase, take title to, or otherwise use the SUAS equipment, see Presidential Memorandum: Promoting Economic Competitiveness While Safeguarding Privacy, Civil Rights, and Civil Liberties, in Domestic Use of Unmanned Aircraft Systems(xxxxx://xxx.xxxxxxxxxx.xxx/the-press-office/2015/02/15/presidential-memorandum- promoting-economic-competitiveness-while-safegua), issued February 20, 2015. Equipment Acquisition Costs Supporting Documentation: Copies of invoices/receipts and cancelled checks or general ledger for proof of payment. AEL# for each purchase (if applicable).
Sample 1Sample 2
Requirements for Small Unmanned Aircraft System. All requests to purchase Small Unmanned Aircraft System (SUAS) must comply with Information Bulletin (IB) 426 and must include the policies and procedures in place to safeguard individuals’ privacy, civil rights, and civil liberties in the jurisdiction that will purchase, take title to, or otherwise use the SUAS equipment. Funding for Critical Emergency Supplies Critical emergency supplies—such as shelf stable products, water, and basic medical supplies—are an allowable expense under EMPG-ARPA. DHS/FEMA must approve a state’s five-year viable inventory management plan prior to allocating grant funds for stockpiling purposes. The five-year plan should include a distribution strategy and related sustainment costs if the grant expenditure is over $100,000.
Sample 1

Related to Requirements for Small Unmanned Aircraft System

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

  • Additional Requirements for Sleeping Rooms The Contractor shall provide departing Attendees a secured area for storing belongings.

  • Minimum Customer Support Requirements for TIPS Sales Vendor shall provide timely and commercially reasonable support for TIPS Sales or as agreed to in the applicable Supplemental Agreement.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • ADMISSION REQUIREMENTS FOR SENIOR COLLEGE PROGRAM  The A.A. degree and a minimum GPA of 2.00  Grade of C or better in a credit-bearing mathematics course worth three or more credits*  Grade of C or better in freshman composition, its equivalent, or a higher-level English course* *(Effective 10/1/08, per University policy) Students who wish to transfer but do not meet all of the above requirements or are unable to enroll within two years after graduation will receive admission consideration under our standard transfer credit policies. Total transfer credits granted toward the baccalaureate degree: 60 Total additional credits required at the senior college to complete baccalaureate degree: 60 Total credits required for the B.A. in Global History: 120

  • Changes to the Department's Requirements 5.1 The Department shall notify the Contractor of any material change to the Department's requirement under this Contract.

  • Minimum Site Requirements for TIPS Sales (when applicable to TIPS Sale). Cleanup: When performing work on site at a TIPS Member’s property, Vendor shall clean up and remove all debris and rubbish resulting from their work as required or directed by the TIPS Member or as agreed by the parties. Upon completion of work, the premises shall be left in good repair and an orderly, neat, clean and unobstructed condition. Preparation: Vendor shall not begin a project for which a TIPS Member has not prepared the site, unless Vendor does the preparation work at no cost, or until TIPS Member includes the cost of site preparation in the TIPS Sale Site preparation includes, but is not limited to: moving furniture, installing wiring for networks or power, and similar pre‐installation requirements. Registered Sex Offender Restrictions: For work to be performed at schools, Vendor agrees that no employee of Vendor or a subcontractor who has been adjudicated to be a registered sex offender will perform work at any time when students are, or reasonably expected to be, present unless otherwise agreed by the TIPS Member. Vendor agrees that a violation of this condition shall be considered a material breach and may result in the cancellation of the TIPS Sale at the TIPS Member’s discretion. Vendor must identify any additional costs associated with compliance of this term. If no costs are specified, compliance with this term will be provided at no additional charge. Safety Measures: Vendor shall take all reasonable precautions for the safety of employees on the worksite, and shall erect and properly maintain all necessary safeguards for protection of workers and the public. Vendor shall post warning signs against all hazards created by the operation and work in progress. Proper precautions shall be taken pursuant to state law and standard practices to protect workers, general public and existing structures from injury or damage. Smoking: Persons working under Agreement shall adhere to the TIPS Member’s or local smoking statutes, codes, ordinances, and policies.

  • Quality control system (i) The Contractor shall establish a quality control mechanism to ensure compliance with the provisions of this Agreement (the “Quality Assurance Plan” or “QAP”).

  • Data Requirements ‌ • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.

  • Maintenance Manual No later than 60 (sixty) days prior to the Project Completion Date, the Contractor shall, in consultation with the Authority’s Engineer, evolve a maintenance manual (the “Maintenance Manual”) for the regular and preventive maintenance of the Project Highway in conformity with the Specifications and Standards, safety requirements and Good Industry Practice, and shall provide 5 (five) copies thereof to the Authority’s Engineer. The Authority’s Engineer shall review the Maintenance Manual within 15 (fifteen) days of its receipt and communicate its comments to the Contractor for necessary modifications, if any.

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