Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF AUGUST 14, 2016 FBO #5378
MODIFICATION

58 -- Advanced Threat Detection System (ATDS) Request for Information and Industry Day Announcement - Questions and Answers

Notice Date
8/12/2016
 
Notice Type
Modification/Amendment
 
NAICS
334419 — Other Electronic Component Manufacturing
 
Contracting Office
Department of the Army, Army Contracting Command, ACC - RSA (W58RGZ) Aviation, SPARKMAN CIR BLDG 5303, Redstone Arsenal, Alabama, 35898-0000, United States
 
ZIP Code
35898-0000
 
Solicitation Number
Advanced_Threat_Detection_System_(ATDS)
 
Archive Date
9/22/2016
 
Point of Contact
Stefanie Polk, Phone: 2568424417
 
E-Mail Address
stefanie.f.polk.civ@mail.mil
(stefanie.f.polk.civ@mail.mil)
 
Small Business Set-Aside
N/A
 
Description
Questions and Answers for RFI and/or Industry Day This amendment provides additional clarification in the areas of cost estimation and provides the Army's definition and methodology for determining Technology Readiness Level (TRL) / Manufacturing Readiness Level (MRL) and identifying critical technology elements. Cost Estimate Information - The Army requests that vendor RFI responses include the cost information set forth below. Vendor cost estimates can include both prototype and production level costs. Cost and pricing information need not be certified, but the Government requests a description of each cost item and details as to the methodology used to create the cost estimate. Cost Estimate Items: B -Kit unit cost by LRU and ship set A-Kit unit cost by platform variant Non-Reoccurring Engineering (NRE): - Hardware - B-Kit - A-Kit - Software/Firmware/Digital System Model - Algorithm Operations and Sustainment cost (average annual) per system (B-kit ship set or LRU) assuming contractor logistic support Production rate change limits; annual or monthly; Minimum, Optimum and Maximum number of units produced Technology Readiness - Provide a TRL and Manufacturing Readiness Level (MRL) assessment for the proposed technologies. Describe how these assessments were conducted and the party who conducted them (self or independently assessed). Discuss methodologies (simulations/lab tests, etc.) used to conduct TRL and MRL assessments. Identify Critical Technologies associated with the proposed design to include technology description, rationale why the technology is "critical," the environment in which the technology operates, and quantifiable metrics and test events that verify the technology satisfies the designed performance. The methodology and definitions stated below are provided as a reference only, so vendors can understand the US Army's process for establishing and identifying Critical Technologies, TRL and MRL levels. - Technology Readiness Level (TRL) 6 - System model or prototype demonstration in a relevant environment - Representative model or prototype system - Represents a major step up in a technology's demonstrated readiness - Relevant Testing Environment that simulates the key aspects of the operational environment - Definitions - Model: Functional form of the system sufficient to demonstrate the technical and operational capability required - Prototype: Physical or virtual model to evaluate technical or manufacturing feasibility or military utility of a technology, process, concept or system - Manufacturing Readiness Level (MRL) 6 - Capability to produce a prototype system or subsystem in a production relevant environment - Initial manufacturing approach developed - The majority of manufacturing processes have been defined and characterized, but there are still significant engineering and/or design changes in the system itself - Producibility assessments of key technologies complete Critical Technology Element (CTE) definition: A technology element is "critical" if the system being acquired depends on this technology element to meet operational requirements (within acceptable cost and schedule limits) and if the technology element or its application is either new or novel or in an area that poses major technological risk during detailed design or demonstration. CTEs could be software/hardware/firmware/A-kit. To identify a CTE, the vendor must be able to address the following areas: A technology element is "critical" if the system being acquired depends on this technology element to meet operational requirements and If the technology element or its application is either new or novel or In an area that poses major technological risk during detailed design or demonstration. Below are additional sub categories to assist in identifying if a CTE is critical, new or novel application, or high risk. This is an example how to complete a CTE assessment. *******************************Begin Example************************** Sub-Category Y/N Y/N 1) Critical Directly impact an operational Requirement threshold (KPP or WBS)? Y Y Significant impact on an improved delivery schedule? N Significant impact on program affordability? N AND 2) New or novel application Is the technology new or novel? N N Is the technology modified? N Tech repackaged such that a new relevant Environment is realized? N Expected to operate beyond design intention/demonstrated capability? N Or 3) High Risk Is the technology in an area that poses major technological risk during detailed design or demonstration? Y Y For a technology to be a CTE, it must be a yes response for category '1) Critical' and '2) New or novel application' or be a yes for '3) High Risk'. In each sub-category if any question is answered yes then that category should be considered a yes. *****************************End Example******************************
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/notices/efcf499d09357f78b5a0f00e276a6c84)
 
Record
SN04222053-W 20160814/160812235024-efcf499d09357f78b5a0f00e276a6c84 (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.