Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF MARCH 03, 2017 FBO #5579
SPECIAL NOTICE

A -- Future Embedded Rotorcraft Sustainment Technologies (FERST) Program - W911W6-17-R-0009 Future Embedded Rotorcraft Sustainment Technologies (FERST) Program

Notice Date
3/1/2017
 
Notice Type
Special Notice
 
NAICS
541712 — Research and Development in the Physical, Engineering, and Life Sciences (except Biotechnology)
 
Contracting Office
Department of the Army, Army Contracting Command, ACC - RSA (W911W6) (AATD) (SPS), LEE BLVD BLDG 401, FORT EUSTIS, Virginia, 23604-5577, United States
 
ZIP Code
23604-5577
 
Solicitation Number
W911W6-17-R-0009
 
Archive Date
4/29/2017
 
Point of Contact
Ann M. Calvin, Phone: 7578785703, Kenneth E. Helms, Phone: 7578785909
 
E-Mail Address
ann.m.calvin.civ@mail.mil, kenny.e.helms.civ@mail.mil
(ann.m.calvin.civ@mail.mil, kenny.e.helms.civ@mail.mil)
 
Small Business Set-Aside
N/A
 
Description
ATTENTION SPECIAL NOTE: Technical Proposals shall be received not later than 14 April 2017; 2:00PM EST. Cost Proposals shall be received not later than 02 May 2017; 2:00PM EST. Technology Investment Agreement Template 1.0Purpose & Background Call number W911W6-17-R-0009, Future Embedded Rotorcraft Sustainment Technologies (FERST) Program, solicits proposals for 6.3 Advanced Technology Development. The Future Embedded Rotorcraft Sustainment Technologies (FERST) program will demonstrate the ability of the aircraft to autonomously respond to the overall health of the aircraft. The Army's aviation sustainment goals are to improve aircraft operational availability (Ao), reduce operations and support (O&S) costs, and minimize the logistics footprint. The Army's Future Vertical Lift (FVL) program has Condition Based Maintenance (CBM) as a performance goal, to include simultaneous monitoring, acquisition, storage, and processing of aircraft data (structural, engine, drive train, and electronic) and aircrew voice interchanges, with condition and health indicators, and tolerance monitoring in flight. FVL goals also include the ability to autonomously provide data to maintenance personnel and to download/track status during flight. The shift from time-based maintenance toward CBM with a Zero-Maintenance emphasis is focused on analysis of aircraft health and usage data to assess the present and projected condition of the aircraft to determine when maintenance is absolutely required. An Army S&T goal is to develop technologies that provide aviation platforms the ability to accurately assess health and project failure of critical aircraft components, based on actual usage in operational environments. This effort is not intended to develop a new Adaptive Vehicle Management system but to take advantage of the extensive work that has already been done in this area. Past applied research and advanced technology development efforts have focused on developing, maturing, and demonstrating individual autonomous diagnostic, prognostic, and system health assessment technologies such as: •Aircraft Level Reasoner (COST-A) •Auto Track and Balance (ASTRO) •Virtual Bus and Power Line Communication (OSST-II, ASTRO) •Smart LRU's (OSST-II, COST-A, ASTRO) •Solid State Power Distribution (ASTRO) •Automated Power Assurance and Engine Health (OSTT-II, COST-A, ASTRO) •Adaptive Vehicle Management System (AVMS) •Fly-by-Wire / Full Authority (JMR-TD, AVMS) These efforts have provided a capability to know the current health state of aircraft components and the general configuration of the aircraft. They have also in some cases provided the sub-systems or components with the ability to adapt based on their health. The FERST program seeks to build upon past efforts by integrating, at the aircraft system level, autonomous sustainment technologies that allow informed, intelligently determined, real-time comprehensive system control, mission planning and an overall maintenance philosophy based on actual aircraft health and usage. This will ensure aircraft reliability and availability while taking advantage of ultra-durable, adaptable, and damage tolerant systems. The Army's Aviation Development Directorate is soliciting FERST proposals for the development, maturation, and demonstration of integrated health management technologies (encompassing Engines, Drives, Structures, VMS, Electrical, and Rotors Systems) thus enabling the aircraft to autonomously respond to the overall health of the aircraft. Vehicle self-assessment technologies, including usage and component tracking, that provide real-time health information to an integrated aircraft adaptive control system (ACS) that adjusts the aircraft control logic based on overall current and projected vehicle health are key elements of this effort. FERST offers the potential to reduce usage based damage and mitigate environmental and combat induced damage, by cueing the pilot before entering a damaging regime. The part history and aircraft configuration management capabilities provided by FERST should further reduce the current sustainment burden associated with tasks such as historical record keeping and part ordering. This program will increase time on wing and maintenance free operational periods, resulting in increased Ao, decreased O&S Costs, and a reduced logistics footprint for Army aircraft; while also enabling an increased based capability that will lead to fully integrated adaptive controls as envisioned for a Zero Maintenance Aircraft. Additional instruction and information can be found under the Master Broad Agency Announcement (BAA) W911W6-16-R-0003 which is posted to Federal Business Opportunities (FedBizOpps) at https://www.fbo.gov. 2.0Scope of Research Effort 2.1Background The Aviation Development Directorate is soliciting technical and cost proposals to accomplish the FERST program. Starting Technology Readiness Level (TRL) of individual technologies may be as low as TRL 4. Technologies and the integrated solution are expected to be matured to a TRL 6 under this advanced technology development effort. Offerors may submit multiple proposals. Each proposal shall describe an effort to address all of the requirements defined within the performance objectives and technical constraints. Offerors shall describe in their proposal a clear path to transition the proposed solution to future aircraft and where applicable to current Army aircraft. Offerors shall also describe and substantiate the anticipated operations and support benefits of their proposed integrated solution. Offerors are strongly encouraged to take advantage of currently available technologies (sensors, algorithms, etc.) and existing aircraft data sources wherever possible. Demonstration testing shall be full-scale and representative of the expected aircraft operating environment and be of sufficient scope to demonstrate the capability, accuracy and robustness of the technologies. An integrated, aircraft flight test demonstration is required. Although FERST is not a fielding effort, Offerors should consider qualification requirements in the design and when proposing a technical approach (e.g., ADS-79E, MIL-STD-810G for system durability, MIL-STD-461F as modified by ADS-37A-PRF for EMI, MIL-STD-704F for aircraft power compatibility, ADS-89-SP for structural integrity latest revision, DO-178C for software, and DO-254 for hardware). FERST is intended to utilize an Open Systems Architecture (OSA) approach that integrates business and technical practices to create systems with interoperable and reusable components based on using modular design, standards-based interfaces, and widely-supported open standards. Offerors shall address OSA in the transition plan and considerations should be made for alignment with the Army's Joint Common Architecture (JCA) Functional Reference Architecture and conformance to the Future Airborne Capability Environment (FACETM) Technical Standard. Program efforts shall identify the requirements to qualify and transition the technology to the field. 2.2Performance Objectives and Technical Constraints The goal of the FERST program is to increase Ao by optimizing aircraft performance, component remaining useful life, and maintenance based on aircraft health and usage. The objective of this program is to demonstrate an intelligent aircraft system that provides the ability for the aircraft to safely and autonomously respond to the overall health through a comprehensive (Engines, Drives, Structures, VMS, Electrical, Avionics, and Rotors Systems) integrated solution. The FERST program shall develop, mature and integrate sustainment technologies that support and feed adaptive controls, mission execution, and mission planning based on aircraft health and usage. FERST will demonstrate, real-time in-flight, automated methods to sense aircraft and system-level health, make adjustments, and predict remaining useful life. Key focus areas include, but are not limited to, all functions and operations of an overall adaptive vehicle management system, system self-assessment (remaining useful life (RUL), prognostics and diagnostics, usage tracking, and embedded aircraft/component history), onboard and off-board configuration management and parts management, and the ability to interface/export data to other supporting off-board systems (Maintenance, Logistics, Fleet Management, etc...). The FERST program shall provide onboard embedded configuration and parts management to facilitate Ao and O&S decision making tasks. Since FVL is identified as the primary transition target, Offerors are encouraged to take advantage of the clean sheet design and maintenance opportunity and not be constrained by conventional practices. FERST shall: •Develop, mature, and integrate the health assessment and adaptive systems required to enable an integrated aircraft adaptive control system to safely and autonomously respond to overall aircraft health •Provide onboard aircraft embedded configuration and parts management •Utilize an open system architecture and common data standards •Demonstrate the integrated solution to TRL 6 upon completion of the effort oProvide Real-time automated health assessment (RUL/usage tracking/diagnostic and prognostic data etc.) oProvide cognitive decision aiding to the pilot about possible damaging regimes based on health oFinal demonstration desired on aircraft •Develop a Transition Plan FERST shall utilize integrated adaptive technologies capable of providing information and adjustments to the aircraft during in-flight operations and mission execution, to maximize aircraft performance based upon overall aircraft health. At a minimum, Offerors shall consider the following aircraft, sub-system, and component critical areas: •State Awareness •Baseline Control Logic •Historical Information •RUL Based on Usage •Health State Change •Autonomous System/Component Adjustments Available Required development, maturation, and integration must be addressed for solutions leveraging existing technologies such as: •Aircraft Level Reasoner •Auto Track and Balance •Virtual Bus and Power Line Communication •Smart LRU's •Solid State Power Distribution •Automated Power Assurance and Engine Health •Adaptive Vehicle Management System •Fly-by-Wire / Full Authority Solutions •Virtual Sensors/Monitoring Offerors shall indicate the entering TRL of each of the proposed technologies and describe the technical approach to achieve a TRL 6 for the integrated system by the completion of the effort. Offerors shall start with the air vehicle as the starting level Work Breakdown Structures (WBS) and go down to the component level or three levels down, whichever is more detailed, in describing and detailing the work required to show how the work progresses from the component level up to the aircraft level. The system shall utilize all available information/data across all subsystems and react to real-time changes in: vehicle health (system/subsystem/component), flight conditions, platform /mission equipment package (MEP), subsystem, damage, etc. Due to the impact the system will have on the flight worthiness of the aircraft, the system shall function in real-time as a cohesive and collaborative system. The system shall also have an override that reverts the aircraft back to a normal predefined flight control logic. FERST shall enable integrated adaptive aircraft systems capable of providing information and adjustments to the aircraft in-flight operation and mission execution that adapt to aircraft health. Pilot cueing will allow the pilot to effectively manage changes to mission and maneuvers; damage, failure, or degradation of components; vehicle state or configuration; and environment. FERST shall provide embedded configuration and parts management by serial number down to the component/LRU level where applicable. The monitored components shall automatically record and store the pertinent data (i.e., part number, serial number, time on wing, flight hours, usage, maintenance actions, RUL, and additional DA Form 2410, Component Removal and Repair/Overhaul Record, data) and transmit the required information for onboard processing and use, and provide the interfaces required to pass or export the information to ground-based maintenance, logistics, and fleet management systems (Enterprise solutions ex. Global Combat Support System-Army (GCSS-A), Logistics Modernization Program (LMP), etc.) FERST data exported off the aircraft shall be limited by performing preprocessing on sensors, in an onboard processing unit, and/or on smart components (ex: parametric, health, historical, maintenance), or other methods to enable real-time response. Raw data shall be available on the aircraft for a specified number of flight hours (ex: 50 FH) for event and schedule driven data collection (i.e., aircraft incident, product improvement). RUL shall be in a quantitative format based on usage (ex: damage fraction, predicted remaining flight hours based on usage and health, etc...). The FERST demonstration testing shall be a full scale on aircraft flight demonstration and representative of the expected aircraft operating environment and be of sufficient scope to demonstrate the capability, accuracy and robustness of the integrated system. Offerors shall justify how the proposed testing meets TRL 6. FERST offerors shall use an open system architecture and common data standards. Offerors are also advised to keep JCA and FACE conformance in mind when developing their proposals, as these are prospective methodologies for FVL. FERST is intended to utilize an Open Systems Architecture (OSA) approach that integrates business and technical practices to create systems with interoperable and reusable components based on using modular design, standards-based interfaces, and widely-supported open standards. Offerors shall address OSA in the transition plan and considerations should be made for alignment with the Army's Joint Common Architecture (JCA) Functional Reference Architecture and conformance to the Future Airborne Capability Environment (FACETM) Technical. Offers shall identify and substantiate proposed common data standards in their proposal. FERST offerors shall provide a Transition Plan as a deliverable under this effort. Offerors shall address the transition of the technology to FVL platforms and insertion of high payoff capabilities into the current fleet. Program efforts shall identify the requirements to qualify and transition the technology to the field. Offer shall consider potential changes to safety and qualification practices that these technologies may facilitate or require for fielding. The Transition Plan shall also include data verification for certification efforts and cybersecurity for methodologies utilized in the effort and proposed in the plan. The FERST Transition Plan shall include critical enabling technologies development strategies as well as provide justification for estimated cost and overall operational benefits (Ao, O&S cost, and logistics footprint). Offeror shall use the following metrics: •Ao = MTBM/ (MTBM + MMT + MLDT) = 90% (Threshold) / 95% (Objective) Where: MTBM is Mean Time Between Maintenance MMT is Mean Maintenance Time MLDT is Mean Logistics Delay Time Ao for this effort is for a Battalion level fleet. Offerors shall detail how they achieved the desired Ao in terms of the formula provided above, providing sufficient detail so the benefits can be traced back to a specific technology, system, or process improvement. •O&S Costs = (Most Current FY available for Medium Lift Aircraft)*75% with an allowable 2% inflation rate for 20 year. •Logistics Footprint <= (Most Current FY available for Medium Lift Aircraft) Personnel and Equipment, Aircraft Ground Support Equipment (AGSE) (Aircraft Specific and Common), and Parts and Spares Offerors are strongly encouraged to take advantage of previously developed and demonstrated technologies wherever possible. This effort shall define system level design concepts which support the capabilities desired for a FVL aircraft. Offerors shall perform tradeoffs, quantify/substantiate improvements, conduct proof-concept demonstrations (where applicable), and describe a clear path for technology development, maturation, and integration for each concept and/or component to a TRL 6 by 2022, including a development, maturation, and integration strategy for critical enabling technologies. Key considerations include performance, operational suitability, volumetric power density SWaP (size, weight, and power), reliability, safety, scalability, affordability, risks, and maintenance requirements. 3.0Call Specific Instructions This call will use the Proposal Submission Process as described in 5.2 of the Broad Agency Announcement, as further supplemented below: 3.1 Proposal Instructions Do not combine multiple topics into one proposal. Specific instructions pertaining to the content and structure of provided proposals are provided in BAA W911W6-17-R-0003, paragraphs 5.2.2 and 5.2.3. In addition to the content required, the offeror shall provide the following: Volume 1 - Technical Proposal: The Offeror shall detail and substantiate the proposed solution including its benefits thereof relative to the FERST requirement, the Technical Objectives of interest, and the plan to execute the proposed solution. Technical proposals are limited to 40 pages total for this Call. Pages in excess of the page limitation will not be read or evaluated. Fold-out illustrations required for reader ease are allowed, however, illustration shall be counted in 8 ½" x 11" increments (e.g., an 11" x 17" document will count as two pages). Font shall be no small than 12 point for all content to include tables, inserts, etc. List of Technical Data and Computer Software proposed for use in performance of the research subject to restrictions using the format at Defense Federal Acquisition Regulation Supplement (DFARS) 252.227-7017, will be included within Volume 1, using the instructions from paragraph 5.2.3., Volume 1, Assertion of Data Rights, of W911W6-17-R-0003 Volume 2 - Price/Cost Proposal: If a foreign entity is participating as part of a prime's team, the cost volume shall clearly identify such participant and the Offeror's planned compliance with U.S. export controls, including any required export licensing. As part of this volume, the proposal must address the desired type of business arrangement, see Section 3.3 of W911W6-17-R-0003. Offeror's proposing use of a Technology Investment Agreement (TIA) shall include the draft TIA provided by the Government with proposed changes clearly marked to facilitate Government evaluation. If a TIA is proposed, the total cost of the proposed effort (which includes cost share) must be provided in the same detail/format as those costs which are to be funded by the Government. A fiscal year funding profile shall be included in the cost proposal. The offeror shall provide the applicable CAGE and DUNS number for offeror's company and all proposed subcontractors. The cost proposal shall include a separate Tab or Section identified as ‘Cost Roll-Up' which provides a clear and concise summary of all costs (i.e., cost element breakdown for the grand total). The Cost proposal shall correlate to the WBS structure in the Technical Proposal. This section shall consist of no more than 15 pages and is required to summarize and facilitate Technical review of costs. If your cost proposal is 20 pages or less, disregard this requirement. The Offeror will propose the cost for Government procurement of software that the Government has less than Government Purpose Rights in event that the Government desires procure by separate contract. This software licensing cost separate from the WBS for performance of the SORE and SOW. This cost will not be evaluated as part of Criterion IV for proposal selection. 3.2 Period and Place of Performance Offerors should clearly depict their proposed schedule and place of performance. The period of performance for FERST research efforts are not to exceed 60 months total (56 months for technical effort and 3 months for data/final report). 3.3 Funding The award of selected proposal(s) will be subject to availability of funds. The Government anticipates one award under this call beginning in the 4th quarter of Government FY17. However, the Government reserves the right to award only one or none, based upon the technical merit and affordability of received technical proposals. Anticipated total Government funding is approximately $17M (6.3 funds). Government fiscal year funding distribution is anticipated as follows: FY17 $0.5M, FY18 $2M, FY19 $3.5M, F&20 $3.8M, FY21 $3.7M and FY22 $3.8M. TIAs with a minimum of 50% cost share are desired. Offerors must review Section 3.3 of W911W6-17-R-0003 for instrument requirements. 3.4 Required Government Facilities, Property, and Data It is the Offeror's responsibility to identify, coordinate, and furnish supporting documentation in the proposal for use of any Government furnished facilities, equipment, or property. The offeror shall provide evidence of coordination with any desired government facilities proposed for use. No government furnished data will be provided. Offerors must have access to or be capable of generating the data required to develop and validate the algorithms or systems proposed. 3.5 Security Performance will require access to and/or generation of technical data the export of which is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec. 2751 e t. seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C. App. 2401 et. seq. Prior to award, the successful offeror will be required to provide an Export-Controlled DoD Data Agreement certification number issued in accordance with DoD Directive 5230.25. This certification may be requested from the Defense Logistics Services Center, ATTN: DLSC-FBA Federal Center, Battle Creek, MI 49017-3084, Telephone 1-800-352-3572. Pre-award access to or submission of a classified proposal is not authorized. Offerors will not submit certification requests to the contracting office. This Announcement is limited to U.S. firms as Prime Contractors. 3.6 Technical Data and Software Rights The Government desires, "Unlimited Rights", but at a minimum requires, "Government Purpose Rights" as defined by DFARS Part 227, to all technical data, deliverables, and computer software developed under this program, and no limitations on the use of delivered and/or residual hardware. It is the Offeror's responsibility to clearly define the proposed data rights for technical data, computer software and each deliverable. Ambiguities will be negatively evaluated against the Offeror. 3.7 Required Reporting and Deliverables All awards under this announcement will require a kickoff meeting to be held at the Offeror's facility following award. The award will require monthly review, preliminary Design Review, Critical Design Review, Test Readiness Review, and Safety of Flight Review. The award will require delivery of the following items delivered in Contractor's format: (1) Program Plan, (2) Design Review Briefing Charts, (3) Bi-Monthly Progress, Cost and Performance Reports, (4) Final Report (Public Releasable and Government Use versions), (5) Final Briefing at Fort Eustis, (6) Test Plans (7) Test Reports (8) Software Development Plan, (9) Software Requirements Specification(SRS), (10) Interface Control Document (ICD), (11) Airworthiness Substantiation Documentation, and (12) Transition Plan (13) Trade Study. All awards will include a requirement to present the results of the work in a final briefing at Ft. Eustis, Virginia upon completion of all technical effort. 4.0 Order of Precedence Any inconsistency between this Call and the Master BAA shall be resolved by giving precedence to this Call (W911W6-17-R-0009). 5.0 Evaluation Criteria The evaluation criteria outlined in BAA, W911W6-17-R-0003, paragraph 6.1 will be used with the following modification to Criterion IV: The reasonableness of the Offeror's proposed cost to the Government, which includes the realism of the cost elements (labor hours, labor categories/mix, subcontracts, travel, materials, and any other direct costs), any proposed cost share. The Government's evaluation of this criteria will be in two stages. All cost proposals will be evaluated for the realism of the proposed labor categories/mix, subcontracts, travel, materials, any other direct costs, cost share if proposed, and offered data rights. A full cost analysis for reasonableness of proposed rates, both direct and indirect, including any Forward Pricing Rate Agreements, Forward Pricing Rate Recommendations, and/or Forward Pricing Rate Proposals will be performed only for proposals selected for negotiations. In addition a full evaluation of cost share if proposed will be done at this time. 6.0 Other Information In addition to the information provided in BAA, W911W6-17-R-0003, paragraph 7.4 the following applies. Offerors shall incorporate the subcontracting plan as part of the offeror's proposal submission. DFARS 226.370-8 discusses subcontracting incentive and goals with the Historically Black Colleges and Universities and Minority Institutions. DFARS 219.708(b)(1)(A) and (B), discusses the appropriate use of DFARS Clauses 252.219-7003 and 252.219-7004 in solicitations and contract related to small, small disadvantaged and women-owned small business subcontracting plans. Offerors are cautioned that in solicitations where subcontracting opportunities exist, the Government will not execute a contract unless the Contracting Officer determines that the negotiated plan provides the maximum practicable opportunity for SBs, SDB, WOSB, HUBZone, and Veteran-owned Small Business concerns or HBCUs/MIs to participate in the performance of the contract. Offerors should note that DFARS 219.705-4 provides for a goal of 5% for SDB concerns and HBCUs/MIs. In reference to paragraph 4.2, Cost Volume, a draft TIA format is attached with this call. 6.1 Additional Proposal Instructions Proposals shall be valid for a period of 7 months from the closing date of this call. Technical and cost proposals shall be provided in original plus three paper copies and one electronic copy (CD ROM disk format). The cost proposal shall be provided in Excel format for cost verification purposes. Electronic submission of proposals is not authorized under this Call. Proposals shall be submitted to Army Contracting Command, Attn: CCAM-RDT, Ann Calvin, Building. 401 Lee Blvd., Fort Eustis, VA 23604-5577. Questions may be submitted in writing via email to Ann M. Calvin, ann.m.calvin.civ@mail.mil. All questions must be submitted within 7 days prior to call closing to ensure a response. All questions and responses received will be posted to FedBizOpps as an amendment to the call. Proposals received after the date and time specified for closing will be handled in accordance with FAR 52.215-1, Instructions to Offerors - Competitive Acquisition. This call is issued subject to the availability of funds. Technical Proposals shall be received not later than 14 April 2017; 2:00PM EST. Cost Proposals shall be received not later than 02 May 2017; 2:00PM EST.
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/notices/def60545e2fc29652816c584202348e1)
 
Place of Performance
Address: Army Contracting Command, ATTN: CCAM-RDT, Building 401, Lee Boulevard, Fort Eustis, VA 23604-5577, Ft. Eustis, Virginia, 23604, United States
Zip Code: 23604
 
Record
SN04419109-W 20170303/170301234900-def60545e2fc29652816c584202348e1 (fbodaily.com)
 
Source
FedBizOpps Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.