Accessibility Information

Users of assistive technologies such as screen readers should use the following link to activate Accessibility Mode before continuing: Learn more and Activate accessibility mode.

A--Modification to Sources Sought W91260-LEMV, posted 22 Apr 09. Draft Statement of Objectives(SOO) for the Long Endurance Multi-INT Vehicle LEMV)is posted for Industry comment.

Solicitation Number: W91260-LEMV
Agency: Department of the Army
Office: Army Contracting Command
Location: U. S. Army Strategic Command
  • Print
Added: Apr 22, 2009 4:36 pm Modified: May 29, 2009 6:07 pmTrack Changes

Program Objectives:
Engineer, design, develop, construct, integrate, test, operate and maintain an unmanned, untethered, hybrid airship with a contractor-supplied, Government approved payload, or a Government-supplied payload.
Support Government operational demonstrations and military utility assessment.
Advance the technologies for a system that will be capable of accommodating and powering a heavier payload and operating autonomously for sustained, long endurance (greater than 21 days) operation as a stable, geostationary platform suitable for various payloads.

Objective Category Task Description/Objectives
1.0 LEMV Basic Objectives.
1.1 Untethered and unmanned; optionally manned for self-deployment (CONUS operations).
1.2 Deployable and sustainable at a nominal altitude of 20,000 feet above Mean Sea Level (MSL). Capable of flying missions with weather avoidance and within national and international airspace. Must be able to forward deploy to support extended operations from austere, forward operating locations with a goal of flying 2500 statute mile roundtrip missions.
1.3 The Contractor may propose and/or provide the payload/s. The Government reserves the right to designate, approve and/or provide the payload(s). The LEMV System prime contractor is to assume sole responsibility for platform system performance and assist in Payload-to-Airship integration. Refer to Annex B for a list (not all inclusive) of candidate missions. The Government may designate one or more classified payloads for demonstration during this demonstration. The Government may operate Government-supplied payload(s).
1.4 Payload specifications do not include the airship or any components/subsystems thereof, including Standard Mission Equipment for airship operations.
Minimum payload capacity is to be 2,500 lbs. (Maybe compartmentalized)
Minimum power delivered to the payload is to be 16 kW.
Payload must be capable of being recovered intact with interfaces to allow destruction (or zeroed out) to prevent enemy capture if required by the government.
Provide an environmental enclosure(s) (as required) and interface(s) for the designated payload(s) that is self contained.
Payload subsystems required to maintain the environment for payload components is to be considered part of the payload with regard to weight and power allocations (specific details to be agreed to by the Government).
Payloads and payload-specific requirements to be specified by the Government at a later date.
The payload bay (gondola) is to be a large as possible in size relative to the 2,500lbs with a plug and play interfaces. The Government will identify/provide payload(s) and an Interface Control Document at early stages of the program.
The contractor shall ensure the gondola and airship structure is capable of carrying heavier payloads (~5000 lbs.) for designed flights as low as 10,000 feet altitude.
Payload bay design must be modular for easy access and testing.
1.5 Sustain station-keeping at operational altitude for three continuous weeks at the designated demonstration location(s) within following parameters:
In the local horizontal plane around the desired station keeping point, the LEMV must remain within a 3.5-km radius circle 50% of the time, within 75 km radius 75% of the time, and within a 150-km radius circle 95% of the time.
Nominal cruise operating altitude is 20,000 ft above MSL.
Airship stability and control parameters consistent with integration of payload(s) into the airship.
Wind speed profile: Airship is to be capable of average cruise speed of 20 knots true airspeed at the nominal cruise altitude carrying a capacity payload over the flight duration.
Provide detailed operational template for wind events in excess of the parameters above.
The airship shall be capable of a dash speed of 80 knots.
1.6 Maintain internal environment (humidity, gaseous composition, pressure, electromagnetic, vibration, temperature, etc.) for airship electrical, power and propulsion subsystems, in accordance with applicable component specifications without degradation of performance through all stages of flight.
1.7 Plan and document a growth path to extend key technologies to the objectives (below) for higher performance platform, including complete airship specifications and an analysis of life cycle and degradation characteristics of components identified as part of the growth path.
Design for this LEMV is to demonstrate scalability of components, structures and subsystems (documented and verified by measurements collected during LEMV demonstration).
Accommodate and ensure total integration (interface definition and coordination of sensor payloads) with airship, Government furnished payload package(s) with nominal weight of up to 7,000 lbs.
Generate and supply power to support station keeping, payload power of 73 kW continuous and all other airship functions for station time of at least one month.
Sustain station time of at least one month within the following parameters:
" In the local horizontal plane around the desired station the LEMV must remain within a 2-km radius circle 50% of the time, and within a 50-km radius circle 95% of the time.
" Nominal cruise altitude of 10,000 ft above MSL to 20,000 ft above MSL.
" Airship stability and control parameters consistent with integration of payload(s) into the airship.
" Wind speed profile: Airship is to be capable of a average cruise speed of 30 knots true airspeed at the nominal cruise altitude over the operational flight duration.
" Provide detailed operational template for wind events in excess of parameters above.
The airship shall be capable of a dash speed of 80 knots.
Provide a global, autonomous, joint-interoperable C2 system capable of controlling the airship from a fixed command center in the US utilizing available SATCOM, terrestrial and/or aerial capabilities.
1.8 Support the Government in the development of a Joint Military Utility Assessment for the LEMV.

1.9 The first LEMV is Government owned and Contractor operated with the contractor providing a path to Government operated in the future if required by the Government.
2.0 Monitoring and Instrumentation.
2.1 Acquire, transmit instrumentation data (telemetry) in accordance with FAA specifications for pilotless controlled aircraft to the ground in near real time and record measurements characterizing the outside flight environment, weather avoidance capability, airship performance, internal and payload bay environments. Measurements to include, but not limited to the following:
Airship stability and control
Power generation, management and distribution
Payload environment (thermal environment, humidity, electro-magnetic, and mechanical jitter)
Other critical systems and components
Exterior atmospheric conditions (temperature, wind velocity, lightening conditions, relative humidity, etc.)
Provide above information, as required, to the payload(s).
2.2 Provide any required ground-based sensor processing (sensor health and status monitoring, sensor calibration, image decompression, image formation, data description, and error detection and decoding) for the payload that is not performed on board the airship. The Government may provide the above for Government-supplied payload(s).
3.0 Command and Control (C2).
3.1 The contractor is to provide a mobile, tactically transportable C2 ground station for the platform and payload operations. This includes fixed both BLOS and mobile LOS capabilities. The contractor may propose a GFE solution comparable to Universal Ground Control Station (UGCS).
3.2 Provide a functional C2 capability from existing equipment or provide alternate options for PM consideration,, for use in this LEMV and adaptable and/or expandable for use in and capable of achieving station-keeping metrics defined for the future higher performance platform described in Section 1.7. The C2 capability is to provide:
Monitoring and instrumentation data and information related to integral airship operation and health within 10 to 60 seconds, depending on the nature of the data.
Self sustaining (existing or planned) ground segment with any combination of communications, data processing, and mission planning hardware/software to demonstrate airship performance through launch, flight duration and recovery, including receiving and executing mission plans prior to flight and updated during flight.
The C2 system is to enable flight and navigation capability that will enable the airship to fly within the station-keeping metrics described in Section 1.5.
The C2 system is to enable complete way-point/route/trip navigation and remain at planned destinations until new mission requirements are provided.
The C2 system is to enable autopilot functionality to minimize manual operator control of the airship.
3.3 Encrypt and secure all C2 communications to known DoD standards to prevent unauthorized access to platform and telemetry data.
3.4 The C2 operator interface is to involve Service tactical users early in the development process prior to key milestones and any long-lead C2 procurement.
4.0 Risk Mitigation and Trade Space Analysis.
4.1 Develop and maintain risk mitigation plans and tradeoff analyses that adequately address, (including potential technical and non-technical risk items), as a minimum, the following issues:
Materials, materials production and integration and hybrid airship construction.
Power generation, management and distribution, including the use energy storage systems.
Payload capability (payload weight and power).
Propulsion and station keeping.
Thermal management.
Launch and recovery.
Emergency procedures
System integration.
Launch metrics for CONUS/OCONUS, listing the Pros/Cons of each method
Environmental limitations at launch and at altitude
4.2 The contractor is to establish parallel risk mitigation activities to increase the probability of successful demonstrations and flight tests. Efforts to be established are to include, but not limited to:
1. Build and test instrumented hybrid airship materials.
2. Build and test representative coupon materials in chambers that represent the airship operational environmental conditions (temperature, UV, and ozone).
3. Conduct ground testing using appropriate models to evaluate proposed handling and deployment solutions.
5.0 Ground Facilities.
5.1 The contractor is to provide all ground support equipment and personnel for launch and recovery during contractor testing and Government demonstrations. The contractor may propose a GFE solution.
5.2 Ground facilities for hybrid airship operations, to include hybrid airship fabrication, flight preparation, launch, recovery, and maintenance, are to be located initially at a fixed location in the United States and provided, operated, and maintained by the contractor for testing and Government demonstrations. Deployable ground facilities must be able to forward deploy to support sustained operations from austere, forward operating locations. The contractor may propose a GFE solution.
6.0 Testing and Demonstration.
6.1 Develop, integrate, implement and document according to Section 10.6, testing program.
6.2 The contractor is to support all reviews, testing, and post-test analyses and reports, and provide input to the mission planning and flight operations to support the mission/systems objectives defined by the Government.
6.3 Contractor-flown demonstrations to be conducted in accordance with Annex A.
7.0 Flight Safety and Regulatory Issues.
7.1 Flight safety is not to be sacrificed to meet any other system capability.
7.2 The contractor is to comply with FAA flight safety rules, regulations, and requirements for flight operations and is to obtain any waivers necessary to perform operations.
7.3 The LEMV system design must consider Electromagnetic Compatibility (EMC) and include features that either eliminate or mitigate those issues to eliminate negative impact on operations and flight safety.
7.4 The contractor is to develop a set of hybrid airship emergency procedures and backup systems for storage, ground handling, launch, ascent, cruise, descent and recovery.
7.5 The hybrid airship is to include a redundant, independent, Rapid Deflation Device (RDD) termination system for range safety and for operational use that would be used if loss of all flight control occurs or to prevent the aircraft from becoming a hazard or penetrating restricted or prohibited airspace, as well as for protecting the possession of sensitive payloads. It will provide both LOS and BLOS capability and be integrated with and independent of the C2 data link(s).
7.6 If the LEMV airship is Government Owned Government Operated (GOGO), it will require a safety assessment by ATEC.
8.0 Operations and Support
8.1 The contractor is to provide operations and sustainment support under the direction of the Government for the duration of the development effort and for a period of 24 months following the conclusion of the demonstration. This is to include support during demonstrations as defined by Annex A. Examples of operations and support include flight planning, hybrid airship launch and recovery, flight operations, equipment and facility maintenance and repair, routine inspections, software maintenance and upgrade, and payload support.
8.2 The contractor is to develop documentation necessary for successful operations and support of LEMV including training and maintenance.
8.21 Procedures: Contractor is to develop Procedures for all essential functions and tasks. The procedures/manuals are for performing essential functions, with caveats or considerations to military personnel performing the same functions in the future. Essential functions refer to all actions required to launch, fly, maneuver, execute mission, reposition, perform emergency actions, perform recovery; and conduct maintenance, monitoring of flight systems and other necessary tasks.
8.22 Training: Contractor is to develop training and manuals to perform essential functions mentioned in 8.21. Training packages do not necessarily need to be complete with training curriculum, but should provide basic estimates of types and lengths of training required, with basic materiel and manuals. Training needs to consider various echelons, such as training requirements for user units, commander and controllers, and Theater-level command and staff personnel.
8.23 Logistics: Contractor is to provide initial logistics materiel, to include maintenance manuals, tools and spare parts, which can be modified to meet system logistics requirements.
8.24 Organization: Contractor is to provide estimates of types of operators/maintainers and skills that can be translated into a military force structure.
8.25 Personnel: Contractor is to provide estimates of numbers of operator/maintainers that can be readily translated into military operational specialties.
8.26 The system must be deployed to CONUS demonstration locations and to the area of responsibility (AOR) defined by the government. Upon completion of deployment, system must be ready for ISR missions within days.
8.3 The contractor is to provide a list of certain critical spares that are additional parts to sufficiently mitigate the risk of substantial program delays during flight tests. The Government may, at its option, elect to contract for these critical spare parts and will convene a spare parts conference for the purposes of providing direction to the contractor.
8.4 The contractor is to provide data collection and analyses, and any associated logistics support analysis, to support the Government military utility assessment.
9.0 Software.
9.1 Provide documented open architecture, open source code and executables for all software. Documentation should be in sufficient form to retain the software design for re-use in later systems. The use of non-developmental item (NDI) software may be acceptable if the item meets the requirements of 1.7
10.0 Data and Reports
10.1 Integrated Master Plan (IMP).
Develop and update IMP to show the overall integration at critical system events, essential tasks to integrate the system, deliver to the field and support and conduct demonstrations.
10.2 Work Breakdown Structure
The contractor is to update and maintain a work breakdown structure (WBS).
10.3 Integrated Master Schedule (IMS).
Develop and update IMS that complements IMP and provides status of program accomplishments. IMS is to define: connectivity of major program events, as well as critical paths and their duration periods, including but not limited to, trade studies, design studies, component/subsystem requirements definition, design completion and fabrication/integration, test events (including component, subsystems and integrated airship).
10.4 Cost/Schedule Management.
Establish implement and maintain a cost performance system that provides for the planning and control of cost and schedule, measurement of performance and generation of timely and reliable information for reporting purposes.
10.41 Cost/Schedule Report: Cost/Schedule reporting is to be through the use of the Cost/Schedule Status Report (C/SSR) to be provided to the Government on a monthly basis.
10.42 LEMV System Description: Prepare a Minimum Technical Data Set (MTDS) for the project. The MTDS is to be updated with each major change to the system description including operating and support requirements. An MTDS is to be included for the higher performance platform System (reference Para. 1.7).
10.5 Contract Data Status and Schedules.
Develop and update Data Accession List (DAL), which contains periodic reports on the status of the Contractors, as well as the Contractors subordinate suppliers/subcontractors data products.
10.6 Data Acquisition Handling and Analysis Plan (DAHAP).
Develop and update (each separate flight test mission) DAHAP that describes the test data required and describes the data collection and data analysis methodologies, shows traceability to key issues and lists threshold levels for successful issue resolution.
10.7 Test Plans.
Develop and update test plans that enumerate objectives and procedures for laboratory and field tests, along with the appropriate documentation that includes the following:
" Detailed test schedule showing all start/stop dates for all phases of hardware/software tests, interface and performance tests, test facilities and test data to be obtained from each test.
" Identification of all ground and flight test readiness reviews (Test Readiness Reviews, Flight Readiness Reviews, System Requirement Reviews, etc.) and show correlation with program objectives.
10.8 In Process Reviews (IPR).
Schedule, conduct and document IPRs quarterly and/or at significant milestones, to include:
" Preliminary Design Review (PDR) and Critical Design Review (CDR) to precede fabrication of subsystems and integration of airship.
" Flight Readiness Review (FRR) prior to each flight.
" Additional IPRs as directed or required by the Government (Government is to provide advance notice and intended agendas).
10.9 Final Report.
The contractor is to provide an interim final report and briefing following the 18-month development and demonstration effort and a final report and briefing at the end of the contract. The reports, in both white paper and briefing format, are to be detailed and comprehensive reports on work completed under this contract. As a minimum, the report is to contain the conceptualized design solutions for all subsystems and integration efforts, demonstration results, vulnerability analysis, and discussion of the final growth path concept and its associated risk.


Demonstration Flight Objectives

The contractor is to support the Government demonstration of the LEMV. Part of that support is to include contractor conducted flight operations to enable the Government to collect various data required to evaluate operational issues, measures of performance, and measures of effectiveness. All flight operations are to meet the safety and performance requirements of the SOW. While the following schedule represents a reasonable estimate of the number, location, and duration of flights that are to occur during the Government demonstration, the actual schedule (including number of flights, objectives, location, and duration) is likely to change as the Government develops more detailed demonstration planning. For this reason, the information presented herein is to be used by offerors for preparation of their proposals in response to the Government's RFP only. The Government is to provide the actual flight schedule after contract award. Please note that the flights shown below are in addition to all flights conducted in support of contractor testing prior to the Government demonstration.

Demonstration Flight Objectives1

Demo Where When Flight Duration Altitude Payload Objectives
1 TBD TBD TBD TBD None Launch2, C2, low altitude flight and recovery.
2 TBD/Military Range TBD Days Note 1 TBD Launch, C2, operational altitude flight, station keeping, payload operation and recovery, lost and reestablishment of lost communications link, operations over mountain regions if possible.
3 Operational Environment 3rd Qtr FY 11 21 days Note 1 TBD Launch, C2, operational altitude flight, station keeping, payload operation and recovery, lost and reestablishment of lost communications link.
Note 1: Nominal 20,000 ft altitude above MSL
Note 2: May be launched from contractor facility/or military range


Candidate Missions

The LEMV is an autonomous, long-endurance platform that is to enable continuous over-the-horizon communications, wide-area surveillance and protection to support theater operations without interruption in urban and mountainous terrain. Its unique performance characteristics can potentially supplant the use of otherwise unaffordable combinations of such assets as those of conventional ground, air, space, and UAVs.

Each individual LEMV can provide up to 173 statute miles line-of-sight at 20,000 ft MSL for target reconnaissance, intelligence, surveillance, and other missions in support of the battlefield commander. LEMVs employed along the U.S. border or as contingency platforms could provide multifunction support to non-DoD agencies such as Office of Homeland Security, Federal Aviation Administration (FAA), Customs, Immigration and Naturalization Service and the Drug Enforcement Agency.

Listed below are candidate missions for objective system LEMV systems. Specific payload equipment that supports one or more of these missions is to be selected by the Government (TBD and provided separately) and demonstrated during the program. The Government may select one or more classified payloads.

Theater Support
Optical/radar surveillance (horizontal/upward viewing)
Broadband data relay of beacon, sensor, lasercom, C2, and intelligence information to various level headquarter units
Intelligence sensors
Utility (flight test support; experimental use of new optical/radar subsystems, communication equipment, and Intel sensors; and test of new airship subsystems)

Civil Applications
Wireless telecommunication (receive/transmit, relay, range extension)
FAA communication range-extension relay, transponder radar beacon adjunct
BLM land surveys
NOAA surveys
EPA surveys

Homeland Security
Real-time multi-band persistent area surveillance (horizontal/downward viewing)
Border patrol
Counter terrorism operations
Drug smuggling operations
Communications linking and relay

Space Mission Areas
Space Force Enhancement
C4, intelligence, surveillance, reconnaissance
Position/Navigation Augmentation
Space Force Application
Targeting & weapons

The Point of Contact for Industry comment is Marie Tornai, Contract Specialist. All comments shall be put in writing via email, mail, or facsimile. The mailing address is US Army Space and Missile Defense Command/Army Forces Strategic Command (USASMDC/ARSTRAT), CAMO-W, Bldg 3, Peterson AFB, CO 80914-4914. Email: Fax: (719)554-8442. Industry comments shall be sent no later than 4:30 PM MST on 10 Jun 2009.

U.S. Army Strategic Command , XR W4T8 ARSPACE CONTRACTING BR, 350 Vandenberg St. Bldg 3, Peterson Air Force Base, CO 80914-4914
U.S. Army Strategic Command XR W4T8 ARSPACE CONTRACTING BR, 350 Vandenberg St. Bldg 3 Peterson Air Force Base CO
Marie Tornai, 719-554-8446

U.S. Army Strategic Command