SOURCES SOUGHT
15 -- PDSS4
- Notice Date
- 8/23/2013
- Notice Type
- Sources Sought
- NAICS
- 334511
— Search, Detection, Navigation, Guidance, Aeronautical, and Nautical System and Instrument Manufacturing
- Contracting Office
- Other Defense Agencies, U.S. Special Operations Command, Technical Applications Contracting Office (TAKO), ATTN: AMSAM-TASO-K, Lee Boulevard, Building 401, Fort Eustis, Virginia, 23604-5577
- ZIP Code
- 23604-5577
- Solicitation Number
- RFI-PDSS4
- Archive Date
- 10/8/2013
- Point of Contact
- Jack L. Shifflett, Phone: 757-878-5223 x243
- E-Mail Address
-
jack.l.shifflett.civ@mail.mil
(jack.l.shifflett.civ@mail.mil)
- Small Business Set-Aside
- N/A
- Description
- Cockpit Management System and the Common Avionics Architecture System Post-Deployment Software Support (PDSS) for Army Special Operations Aviation, Fiscal Years (FY) 2014-2019 Notice Type: Sources Sought 1.0 - DESCRIPTION 1.1 - The Government has a requirement for the sustainment, modernization and enhancement of the Cockpit Management System (CMS) and for the Common Avionics Architecture System (CAAS) software. To fulfill this requirement, the United States Special Operations Command, Technology Applications Contracting Office is seeking interested industry organizations that can furnish the personnel, facilities, equipment and materiel necessary to perform post-deployment software support (PDSS), systems integration and system modernization. 1.2 - THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information and planning purposes - it does not constitute a Request For Proposal (RFP) or a promise to issue an RFP in the future. This request for information does not commit the Government to contract for any supply or service whatsoever. Further, the Government is not at this time seeking proposals and will not accept unsolicited proposals. Respondents are advised that the Government will not pay for any information or administrative costs incurred in responding to this RFI; all costs associated with responding to this RFI will be solely at the interested parties' expense. Not responding to this RFI does not preclude participation in any future RFP, if issued. If an RFP is released, it will be synopsized on the Federal Business Opportunities (FedBizOpps). It is the responsibility of the potential responder to monitor these sites for additional information pertaining to this requirement. 2.0 - DESCRIPTION OF NEED 2.1 - Objectives Overview. Objectives for the CMS and CAAS PDSS FY 2014-2019 program and Vendor capabilities/qualifications includes: Performance 2.1.1 - Software support including: 2.1.1.1 - Emergency repair (Respond to Priority 1 problem report(s) w/in 48 hrs, proposed solutions w/in 1 wk, both from time of problem report submission, resulting in formally released software, including all associated/pertinent documentation updates and releases, as required. Note: A Priority 1 problem is defined as an issue that prevents the accomplishment of an operational or mission essential capability or jeopardizes personnel safety.) 2.1.1.2 - Corrective coding (Modifications performed to correctly reflect the specification or to correctly utilize system resources as documented by non-Priority 1 problem report(s).) 2.1.1.3 - Enhancements (Modifications performed in response to requirements for changes and additions.) 2.1.1.4 - Technology Insertion (Modifications performed to adapt to changes in processing requirements.) 2.1.1.5 - Growth (Modifications performed to adapt to changes in data requirements or the addition of new programs or users.) 2.1.1.6 - System modernization (Research, analysis, design, implementation and test, (or support of these activities) of any modernization effort that enables the ARSOA to meet mission and deployment requirements.) 2.1.1.7 - Software DO-178C compliance capable (Software maintained/updated at DO-178C assurance levels potentially up to Level A, as appropriate.) 2.1.1.8 - Standard acquisition documentation for software development per DoDD 5000.1 (Creation and maintenance of Vendor-generated documentation for software development during the execution of the ARSOA PDSS program.) 2.1.1.9 - Software developed under this contract will have Unlimited Rights. 2.1.1.10 - Integration of 3rd party hardware and software to include 3rd party source code. 2.1.1.11 - Systems integration/testing/verification (Planning, documentation updates/generation, and execution of systems integration activity including Systems Integration Laboratory (SIL) modifications, SIL lab test execution, including nominal and off-nominal (corner-case, exception handling, robustness) requirements-based and operational/mission-based scenario testing, leading to requirements proof of compliance and air worthiness documentation, and on and off-site development flight test support, as necessary.) 2.1.1.12 - SIL and test stand build, modification, and maintenance in support of software development and test (Objective uses to include, but not limited to, software/system test and verification, Pilot Vehicle Interface (PVI) demonstration and evaluation, and operator training. Capabilities including maximum utilization of real avionics hardware and wiring, simulation/stimulation capabilities to produce dynamic flight environment and data capture ability for analysis/investigation of system anomalies.) Organization/Personnel/Facilities 2.1.2 - Organization 2.1.2.1 - Capability Maturity Model Integration (CMMI) Level 5. 2.1.2.2 - Extensive experience in Aviation software and systems development, integration, and support of complex avionics systems, capabilities including, but not limited to, communication, navigation, guidance, controls & displays, sensors, weapons, Aircraft Survivability Equipment (ASE) and data bus structures such as MIL-STD-1553, ARINC 429, and Ethernet. The order of magnitude of software to be supported ranging 1.1-1.5 million Source Lines of Code (SLOC). 2.1.2.3 - Experience in conduct of structural and test coverage analysis. 2.1.2.4 - Experience and capability to maintain software development and system integration test lab environments. 2.1.2.5 - Experience in systems integration and flight test support of complex avionics systems. 2.1.2.6 - Experience in development of dynamic simulation capabilities. 2.1.2.7 - Familiarity with military and commercial standards. 2.1.2.8 - Familiarity with Real Time Operating System (RTOS) and Real Time Environments (RTEs) for software development. 2.1.2.9 - Employees must be US Citizens and posses, or that the ability to obtain, secret level security clearance. 2.1.2.10 - Ability to travel Continental United States (CONUS) 2.1.2.11 - Familiar with Integrated Product Teams (IPTs) and comfortable with working in collaborative environments 2.1.3 - Facilities space and power 2.1.3.1 - Company must have DSS approved Facility Clearance (FCL). 2.1.3.2 - Capabilities to install, operate, and maintain Government Furnished Property (GFP) provided SIL test benches supporting CMS and CAAS systems, with a footprint of approximately 6000 sq ft. Power to include 400 Hz, 3-Phase. 3.0 - ACQUISITION STRATEGY 3.1 - If awarded, the contract for this program is intended to be an Indefinite Delivery, Indefinite Quantity (IDIQ) for a 12 month period, with four (4) one year options. Contract types to potentially include Firm Fixed Price (FFP), Cost Plus (CP), and Time & Material (T&M). 4.0 - REQUESTED INFORMATION 4.1 - Interested parties are invited to submit technical information describing their organization's ability/capability to meet the objectives described in Section 2. This request is intended to identify an organization's qualifications without the award of a contract to the respondent. 4.2 - Additionally, provide an itemization of data items desired/required in order to accomplish a smooth and complete transition from incumbent PDSS provider. 5.0 - RESPONSES 5.1 - Interested parties are requested to respond to this RFI with a white paper. The white papers should be provided in PDF or Microsoft Word for Office 2003 or later compatible format, supplemented with Microsoft Word, Excel, PowerPoint, PDF, or JPG attachments as necessary. The responses are due no later than 30 days from the date of this RFI, 4:00 p.m. Eastern Daylight Time (EDT). White papers shall be limited to the page count specified below. All documents shall be submitted via e-mail only to Mr. Jack L. Shifflett (jack.l.shifflett.civ@mail.mil). 5.2 - Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. Please be advised that all submissions will not be returned. 5.3 - The Government intends to utilize personnel from Cruz Associates, Inc., Yorktown, Virginia, and Yahwehs Computers, Inc., Williamsburg, Virginia to provide technical advice and support in review of submitted information. By submitting a response to this RFI, the Contractor consents to the Government disclosing Contractor proprietary information to the aforementioned contractors to develop the acquisition approach. Each of these support contracts have the Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.227-7025, Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends, in the contracts with the Government and employees of these companies have individual non-disclosure statements on file with the company. 5.4 - The white paper shall provide administrative information, and shall include the following as a minimum: Primary Point of Contact, name, mailing address, overnight delivery address (if different from mailing address), phone number, facsimile phone number, and e-mail address. No page limit is imposed on the responses to this RFI, but the responders are encouraged to make their responses clear and concise without superfluous information. Provide the following information: 5.4.1 - Introduction and Executive Summary Respondent Name, Point of Contact, Title, Date, E-Mail Address, Phone #, Fax #, Organization/Office Symbol, and Address. 5.4.2 - List of previous and current customers and current contract vehicles that are being used by the Government of similarly complex Aviation post-deployment software and systems support. Please describe in particular work efforts that provided flight worthy software that have received flight approval from a military airworthiness engineering activity, Federal Aviation Administration (FAA) or authorized representative, or the European Aviation Safety Agency (EASA) or predecessor. 5.4.3 - Business type - (large business, small business, small disadvantaged business, 8(a)-certified small disadvantaged business, HUBZone small business, woman-owned small business, very small business, veteran-owned small business, service-disabled veteran-owned small business) based upon North American Industry Classification System (NAICS) code 334220 -- Other Communications Equipment Manufacturing. "Small business concern" means a concern, including its affiliates that is independently owned and operated, not dominant in the field of operation in which it is bidding on Government contracts, and qualified as a small business under the criteria and size standards in 13 CFR part 121. A small business concern for the purposes of this procurement is generally defined as a business, including its affiliates, that has no more than 750 employees. Respondents are cautioned, however, that this is a general description only. Additional standards and conditions apply. Please refer to Federal Acquisition Regulation FAR 19 for additional detailed information on Small Business Size Standards. The FAR is available at http://www.arnet.gov. 5.4.4 - The facility security clearance of the vendor. 5.5 - Other Special Requirements: DO NOT SUBMIT PROPOSALS AT THIS TIME. SUBMIT WHITE PAPERS ONLY. No contracts will be awarded based solely on this announcement. 6.0 - QUESTIONS Questions regarding this announcement shall be submitted in writing by e-mail to the Contracting Specialist, email address: (jack.l.shifflett.civ@mail.mil). Verbal questions will NOT be accepted. Questions will be answered by posting answers to the FedBizOpps website; accordingly, questions shall NOT contain proprietary or classified information. The Government does not guarantee that questions received more than 21 days after the RFI issue date will be answered. 7.0 - USE OF INFORMATION The purpose of this notice is to gain information leading to Government/Industry collaboration for development of United States Special Operations Command (USSOCOM) technology capabilities and to assist in accelerating the delivery of these capabilities to the warfighter. All proprietary information contained in the response shall be clearly marked. The Government will protect all proprietary information from unauthorized disclosure. The Government will not use proprietary information submitted from any one firm to establish future capability or requirements. 8.0 - SUMMARY THIS IS A REQUEST FOR INFORMATION (RFI) ONLY to identify sources that can provide post-deployment software and system support for complex avionics DoD Platforms. The information provided in the RFI is subject to change and is not binding on the Government. The Government has not made a commitment to procure any of the items discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur cost for which reimbursement would be required or sought. All submissions will not be returned. CONTACT: This Request for Information (RFI) is issued solely for information and planning purposes only and does not constitute a solicitation. All information received in response to this RFI that is marked Proprietary will be handled accordingly. Responses to the RFI will not be returned. In accordance with FAR 15.201(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Responders are solely responsible for all expenses associated with responding to this RFI. All interested, capable, and responsible sources that wish to respond to this RFI are asked to provide input to Mr. Jack Shifflett, Contract Specialist via email at jack.l.shifflett.civ@mail.mil and no later than 12:00 pm EST on 24 September 2013. Questions may be forwarded to the Contract Specialist by email. Contracting Office Address: ATTN: AMSAM-TASO-K Lee Boulevard, Building 401 Fort Eustis, VA 23604-5577 Primary Point of Contact: Jack L. Shifflett Contract Specialist jack.l.shifflett.civ @mail.mil 757-878-3299 ext. 243 Secondary Point of Contact: Michael J. Wastella Contracting Officer Michael.j.wastella.civ @mail.mil 757-878-3299 ext. 259
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/ODA/USSOCOM/FortEustisVA/RFI-PDSS4/listing.html)
- Place of Performance
- Address: Ft. Eustis, VA, Ft. Eustis, Virginia, 23604, United States
- Zip Code: 23604
- Zip Code: 23604
- Record
- SN03161153-W 20130825/130824000319-4908f016e35586150a7b941f064d4a9b (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 |