Robust Fuzewell Instrumentation System (RFIS)

NAICS CODE: 541712 FEDERAL AGENCY NAME: AIR FORCE RESEARCH LABORATORY, MUNITIONS DIRECTORATE, CONTRACTING DIVISION (AFRL/RWK), EGLIN AFB, FLORIDA BAA TITLE: ROBUST FUZEWELL INSTRUMENTATION SYSTEM BAA TYPE: INITIAL ANNOUNCEMENT BAA NUMBER: BAA-RWK-10-0004 WHITE PAPER DUE DATE AND TIME: White papers are due by 2:00 PM Central Time on 14 April 2010. Deliver to: AFRL/RWK, ATTN: Ms Melissa Campbell, 101 West Eglin Blvd, Suite 337, Eglin AFB, FL 32542-6810. White Papers received after this due date and time shall be governed by the provisions of FAR 52.215-1(c)(3). See Section IV for additional information. It should be noted that this installation observes strict security procedures to enter the facility. These security procedures are NOT considered an interruption of normal Government processes, and proposals received after the above stated date and time as a result of security delays will be considered "late." Furthermore, note that if offerors utilize commercial carriers in the delivery of White Papers, they may not honor time-of-day delivery guarantees on military installations. Early White Paper submission is encouraged. I. PROGRAM DESCRIPTION: The Air Force Research Laboratory Munitions Directorate, Contracting Division (AFRL/RWK) is soliciting White Papers for the Fuzes Branch (AFRL/RWMF) on the following research effort: Robust Fuzewell Instrumentation System (RFIS). It is anticipated approximately two of the White Papers may be selected for further consideration, and their originators may subsequently be requested to submit formal written technical and cost proposals, with the intent of negotiating one contract for the RFIS program. However, the Government reserves the right to award one, multiple, or no contracts pursuant to this BAA. (1) Introduction: The Robust Fuzewell Instrumentation System (RFIS) program will develop an instrumentation package that will replace the fuze inside a penetrator weapon for both sled and flight tests. The RFIS will house a minimum of two (2) internal data recorders that will be used to measure and record deceleration data in testing of penetrating weapons. Such tests have high value and a need exists for a reliable alternative to existing methods which have proven to be inadequate. The RFIS technology program will provide increased reliability by providing the platform for multiple data recorders to be housed within the volume of a standard 3" bomb fuzewell. (2) Program Objective: General Program Objective: The objective of this task is to design and develop a non-proprietary Robust Fuzewell Instrumentation System (RFIS) which can be fabricated at relatively low cost in a repeatable fashion. The RFIS will be strictly an instrumentation item and will replace the fuze inside a penetrator weapon for both sled and flight tests. Generally the primary data recorder is placed inside the fuze body. These recorders are hand-assembled units which are generally put together just prior to the tests because of battery limitations. Additionally, these recorders have generally used volatile memory which requires excavation and recovery of the data recorder within 30 days. Depending upon the range restrictions, target characteristics and depth of penetration this may not always be possible. Also, for flight tests, the flight profiles of the test aircraft have to be restricted because previous data recorders have not had temperature compensation circuits. Specific Program Objective: The instrumentation system will be comprised of existing state-of-the-art harsh environment data recorders with sensors, power supply, interface control module, and carrier package. This system will house a minimum of two (2) independent internal data recorders with a goal of three (3) independent internal data recorders that will be used to measure and record deceleration data in testing of penetrating weapons. Such tests have high value and a need exists for a reliable alternative to existing methods which have proven to be inadequate. The RFIS program will provide increased reliability by providing the platform for multiple data recorders to be housed within the volume of a standard 3" bomb fuzewell. Prior data recorders have shown a moderately high failure rate during sled tests and an unacceptably high failure rate (>50%) during actual weapon flight tests when used in penetration experiments into either rock or concrete. These tests are extremely expensive and cannot always be repeated due to fiscal constraints. The deceleration data is required to accurately model and predict the penetration capability of current and future weapons and to determine the limits of fuze and weapon survivability. (3) Technical Requirements: The RFIS design will contain multiple data recorders for redundancy and maintain the general form factor of the FMU-152 fuze to fit into current penetrator weapons. In conjunction with the development of the RFIS, tests should evaluate RFIS activation schemes for both sled and flight tests as well as impact survivability. The design shall be modular with cavities to fit multiple data recorders within and electrically interface with them for power, communications and any other necessary functions. Develop an Interface Control Drawing (DI-CMAN-81248A) to document mechanical and electrical requirements for both the overall RFIS as well as the internal recorder modules, plug-and-play compatibility with multiple internal data recorders, etc. The interface module shall incorporate the FMU-152 electrical interface and will communicate with the weapon system within the limitations of the FMU-152 electrical interface to provide information such as health check, system activation, and any other necessary functions. The RFIS external dimensions shall be established to allow installation within the standard 3" fuzewell of penetrating weapons (e.g. BLU-109, BLU-113, BLU-122, Massive Ordnance Penetrator (MOP)) and maintain compatibility with weapon systems which incorporate existing (e.g., FMU-143, FMU-152) and future fuzes (e.g., Hard Target Void Sensing Fuze (HTVSF)). The RFIS shall be secured within the fuzewell sufficiently to prevent movement within the fuzewell and warhead base plate through the target penetration event. Develop protocols for data recorder activation, functional testing, and impact survivability demonstration. Develop Finite Element (FE) model of RFIS for shock loading analysis and test predictions. Develop and breadboard interface module architecture. Information for interfacing with existing recorders is contained in the Annex. Other technical information is also contained in the Annex. Certified DD Form 2345, Militarily Critical Technical Data Agreement, is required to be submitted to the Program Manager and the Contract Specialist in order to receive the Annex. Once a certified DD Form 2345, Militarily Critical Technical Data Agreement, is received, then the contractor will receive access to the Annex. See paragraph I(11)(d) for further details on how to request the Annex. (4) Program Tasking: The program is anticipated to include design, analysis, modeling and simulation, software development, test plans, prototype hardware fabrication and delivery, bench testing, laboratory shock testing, and cannon launched penetrator shock testing, sled and flight testing. a. Trade Study: The contractor shall conduct a trade study of available recorders for suitability of use in the RFIS design. The contractor shall present results of the trade study to the Government for approval prior to the RFIS design. b. Design: The contractor shall design a Robust Fuzewell Instrumentation System that will meet or exceed the technical requirements. The contractor shall identify all necessary elements and incorporate them into a system design. c. Analysis: The contractor shall conduct analyses and tests as necessary to predict and validate: i. Survivability of the RFIS when subjected to the shock loads associated with impacting and penetrating hard and deeply buried targets. ii. The functionality of the RFIS to perform within a weapon system both pre and post-penetration. d. Modeling and Simulation: The contractor shall develop a Finite Element model of the RFIS to predict shock loading effects on the RFIS and provide this information for shock survivability design margin analysis. e. Software Development: The contractor shall develop and document all software associated with RFIS communications with the weapon system and the individual recorder modules, and the interface with the user. f. Prototype Hardware Fabrication and Delivery: The contractor shall fabricate and deliver hardware according to the proposed test schedule. The contractor shall fabricate and deliver a sufficient number of test articles to accomplish all tests identified in the test plan, plus provide five (5) fully functional, complete test items for Government evaluation. g. Testing: The prototype units' performance shall be fully tested in bench-level tests at the contractor's facility and the test results shall be delivered to the Government within 30 days of test completion. Prototype design variants will undergo a series of shock survivability tests in a laboratory setting. The offeror may choose to have the Government conduct these tests at a Government facility, or if the offeror has the capability to perform such tests, the evaluation may be conducted at their facility. Laboratory test results shall be delivered to the Government within 30 days of test completion. Upon approval by the Government the offeror will refine the design(s) as necessary and fabricate prototype design(s) for evaluation in a series of field cannon tests. It is anticipated that up to ten (10) field cannon tests, two (2) sled tests and one (1) flight test will be conducted. Upon completion of field-testing, the offeror shall evaluate the results and incorporate lessons learned into a final design. The contractor shall provide support (personnel, equipment, and supplies) for all testing provided by the Government. h. Low Cost Producibility: The contractor shall consider design practices for low cost of producibilty in the design of RFIS. The contractor shall provide a unit cost of production estimate for low quantity custom fabrication (10 units). (5) Test Support: The contractor shall be responsible for all test plans necessary for the maturation and demonstration of the hardware and software products to be tested. Contractor-generated test plans, as approved by the Government, will become schedule milestones and will identify test methodologies required to meet each major program milestone. For tests being conducted at Government facilities, the contractor shall be responsible for providing technical support, analysis, data and test planning support to the identified responsible Government test organization. The contractor shall provide test support to include, but not limited to, the following: support of test planning meetings; test setup advice; test article build up; checkout; installation of hardware; instrumentation package support; required documentation for testing; support of safety and Seek Eagle reviews and analysis for flight testing; identification of risk and suggestion of improvements; record test setup; data collection for evaluation of results; support required for test accident/mishap investigations; post-test analysis and test result documentation. (6) Risk: During all phases of the RFIS technology program, the contractor shall identify and track all risks relating to the technical, safety, financial, and schedule aspects of the program. The contractor is responsible for utilizing a risk evaluation process, determining all major program risks, assigning values to those risks, developing mitigations for those risks, and periodically re-evaluating those risks after the mitigations are applied. The contractor shall make risk evaluation a component of all major technical reviews, and risk items/progress shall be discussed in monthly status reports. (7) Management: The contractor shall be responsible for meeting all requirements of this effort, including but not limited to: cost, technical, safety, schedule, security and subcontractor management. The contractor shall communicate the technical and programmatic status through Data Requirements submissions discussed in section/paragraph I(8) and scheduled meetings discussed in section/paragraph I(9). In addition to formal design reviews, informal program status interchanges (such as weekly teleconferences) are encouraged. (8) Data Requirements: The following data submittals are expected to be required for each contract awarded: a. Monthly Status Reports (Status Report: DI-MGMT-80368/T) b. Contract Work Breakdown Structure (DI-MGMT-81334C) c. Quarterly Contract Funds Status Report (DI-MGMT-81468) d. Program Review Material (Presentation Material: DI-ADMN-81373/T) e. Design Drawings (Developmental Design Drawings and Associated Lists: DI-SESS-81002D) f. Computer Software Product End Item (DI-MCCR-80700) g. Interface Control Drawing Documentation (DI-CMAN-81248A) h. Test Plans (Test Plan: DI-NDTI-80566) i. Test Data (Test/Inspection Report: DI-NDTI-80809B) j. System Engineering Management Plan (DI-MGMT-81024) k. Status of Government Furnished Equipment (GFE) Report (DI-MGMT-80269) l. Final Technical Report (Scientific and Technical Reports (Final Report): DI-MISC-80711A/T) m. The contractor may propose additional elements or submittal of combined elements or Data Item Descriptions (DIDs) as appropriate for the proposed program. (9) Meetings and Reviews: The Government anticipates the following program meetings and reviews: Kickoff within a month of contract start date at contractor's facilities; Technical Interchange Meetings (TIM) quarterly and/or at times coinciding with key program milestones or decision points that alternate between the contractor's facilities and Eglin AFB, FL; and a Final Program review at completion of the program at Eglin AFB, FL. The contractor may propose to conduct or participate in other meetings with subcontractors, Government agencies, or third parties, as deemed necessary. The contractor may also propose different meeting locations for the formal reviews based on technical and or programmatic reasons. (10) Other Requirements: a. Program Security Requirements: Portions of this program will be classified at the Secret level and a DD Form 254 will apply to the awarded contract. Thus, offerors must verify their Cognizant Security Office information is current with Defense Security Service (DSS) at www.dss.mil . b. Emissions Security (EMSEC) requirements will apply. Generation of classified material is authorized only on equipment approved for classified processing by Air Force EMSEC authorities. Based upon the proposed technical approach, the Government will provide a Security Classification Guide at contract award or during the performance of the contract, whenever the requirements of the guide, as it pertains to the contract performance, can be determined. c. International Traffic in Arms Regulations and Public Law 98-94 (export control) will apply to this effort. d. It is anticipated that all data delivered under any resulting award will be delivered with unlimited rights; however different rights may be negotiated as appropriate. The contractor shall identify data rights assertions, licenses, patents, etc. that apply to any proprietary materials, technical data, products, software, or processes to be used by the prime or subcontractor(s) in the performance of this program; and shall address acquisition of data rights or licenses, or expected recoupment of development costs for those proprietary items that will be integral to the design. The contractor shall specifically address data rights/proprietary issues at each meeting discussed in section/paragraph I(9). The contractor shall specifically address inventions/patents identified in the performance of the program at each meeting discussed in section/paragraph I(9). e. Subcontracting Plans: Subcontracting plans will be required in accordance with FAR 19.702 Small Business Programs (11) Other Information: a. Government Furnished Property (GFP): The Government may assist in providing GFP, based on availability, if requested. Therefore, the offeror shall include a detailed list of Government resources, with their associated approximate value (if known), required to execute a contract in a timely and cost effective manner. b. Base Support/Network Access: The offeror should identify any they believe is necessary in their White Paper and any subsequent proposals. c. Hazardous Materials: The contractor must identify any hazardous materials to be used in performance of this effort in the White Paper and any subsequently requested formal proposal. d. Request for Annex: To receive the Annex, the offeror must be certified to receive military critical technical data under the US/Canada Joint Certification Program (JCP) (www.dlis.dla.mil/jcp). To request this Annex, forward a written request for release of export-controlled data related to the RFIS technology program to Mr. Steven Smith via mail or fax (see section VII - Agency Contacts, paragraph (2)). The written request shall include: i. Certified copy of a DD Form 2345, Militarily Critical Technical Data Agreement ii. Commercial and Government Entity (CAGE) code iii. Name, phone, email, and fax of the person to receive the annex iv. Self-addressed mailing envelope or self-adhesive label The request should be provided early enough to allow the Government up to 14 calendar days to provide the document. No supplemental documentation will be provided unless requested in strict accordance with these instructions. II. AWARD INFORMATION: (1) Type of Contract: The Government anticipates negotiating a Cost-Plus-Fixed-Fee (CPFF) contract type for this effort. (2) Anticipated Number of Awards: The Government anticipates negotiating approximately one Cost-Plus-Fixed-Fee contract for the program. However, the Government reserves the right to award multiple, or no contracts pursuant to this BAA. (3) Anticipated Award Date: The Government expects to receive White Papers within 45 days of publication of this BAA, and to request proposals within 3 weeks thereafter. The Government expects to receive proposals within 30 days after request, and to negotiate and award a single contract within 8-9 weeks thereafter. (4) Anticipated Period of Performance: The RFIS Technology program contract period will be 27 months (24 months for the technical effort, 1 month for first submission of the Final Report, 2 months for revisions). (5) Anticipated Funding: Anticipated funding for the total program (not per contract or award) is approximately $2.5M. This figure includes approximately $750K FY10, $1M FY11, and $750K FY12. This funding profile is an estimate only and will not be a contractual obligation for funding. All funding is subject to change due to government discretion and availability. All potential offerors should be aware that due to unanticipated budget fluctuations, funding in any or all areas may change with little or no notice. III. ELIGIBILITY INFORMATION: (1) Eligible Offeror/Applicants/Notice to Foreign-owned Firms: All applicants are potentially eligible. A determination has been made for this solicitation, that foreign participation is allowed at the prime contractor and subcontractor levels. (2) Cost Sharing or Matching: Cost sharing is not a requirement but is encouraged. IV. PROPOSAL/APPLICATION AND SUBMISSION INFORMATION: (1) Application Package: THIS ANNOUNCEMENT CONSTITUTES THE ONLY SOLICITATION. WE ARE SOLICITING WHITE PAPERS ONLY. DO NOT SUBMIT A FORMAL PROPOSAL AT THIS TIME. (See Sections V and VI of this announcement for further details.) (2) General: Offerors should be alert to any amendments that may be published. The Government reserves the right to amend due dates or other data as necessary, and to make awards without discussions. Multiple White Papers within the purview of this announcement may be submitted by each offeror. All offerors should apply the restrictive notice prescribed in the provision at FAR 52.215-1(e), Restriction on Disclosure and Use of Data, to trade secrets or privileged commercial and financial information contained in their White Papers (and formal proposals, if requested in accordance with section/paragraph VI(1)). Any classified material must be provided in a separate Annex and must be properly marked and handled as such. Any classified material should be provided directly to Mr. Steven Smith (see section/paragraph VII(2)) rather than to AFRL/RWK. For formal proposals, submit separate Technical and Cost Volumes, and mark them as valid for 180 days. Volume 1 should provide the Technical proposal, and should be unclassified, if possible. Volume 2, Cost Proposal, must be unclassified, and should address the price, cost details, and a risk assessment of the proposal. (3) Content and Form of Submission for White Papers: Offerors are required to submit one (1) original and three 3 copies, and one (1) electronic copy (on a CD or DVD) of a White Paper summarizing their proposed approach/solution. The White Paper shall be limited to 20 pages, prepared and submitted in Microsoft Word format. Font shall be standard 10-point business font Arial or Times New Roman. Character spacing must be "normal," not condensed in any manner. Pages shall be single-spaced, single-sided, 8.5 by 11 inches, with at least one-inch margins on all sides. All text, including text in tables, must adhere to all font size and line spacing requirements listed herein. Font and line spacing requirements do not have to be followed for illustrations, flowcharts, drawings, and diagrams. These exceptions shall not be used to circumvent formatting requirements and page count limitations by including lengthy narratives in such items. The page limitation covers all information except the cover page. Any pages in excess of the stated page limitation will be removed (after page 20) and will not be considered. Email submissions will not be accepted. A confirmation of receipt may be generated via email as White Papers are received (if an email address is provided with the White Paper). The purpose of the White Paper is to preclude unwarranted effort on the part of an offeror whose proposed work is not of interest to the Government. Format the White Paper as follows: Section A: Cover Page. BAA Reference number "BAA-RWK-10-0004", Title of Paper, Period of Performance, Estimated Cost, Name/Address of Company, Commercial and Government Entity (CAGE) number, Dun & Bradstreet (D&B) Data Universal Numbering System (DUNS) number, Technical and Contracting Points of Contact (phones, fax and emails) (this section is NOT included in the page count). Section B: White Paper Details. White Papers should address all areas indicated by the Evaluation Criteria (see Section V(1)), including how the contractor intends to achieve the objectives of Section I for the program based on the anticipated funding shown in Section II(5) . Both corporate and individual experience should be addressed (See evaluation criteria in Section V(1)). A rough order of magnitude (ROM) cost estimate broken down by task should be provided. Also, the White Paper shall include a top level discussion of tests planned, which identifies contractor- and Government-conducted testing, as well as the facilities at which the testing is to occur. Additionally, the White Papers shall include any partners, subcontractors, etc., to be utilized, discuss risk (technical, schedule and cost) assessment, technology maturity levels and maturity plans required to meet requirements, and identify the modeling and simulation (M&S) software that will be used in system design and effectiveness assessments. (4) Content and Form of Submission for Full Proposals: The Government reserves the right to request one, multiple or no proposals as a result of the White Paper evaluations. In the event that the White Paper results in an invitation to submit a formal proposal, the paragraphs below indentify proposal format and content. Offerors must submit one (1) original and six (6) paper copies, and one (1) electronic copy (on a CD or DVD) of both the Technical and Cost proposals. a. Volume 1- Technical Proposal: (i) Page Limitation: The Proposal shall be limited to 75 pages, prepared and submitted in Microsoft Word format. Font shall be standard 10-point business font Arial or Times New Roman. Character spacing must be "normal," not condensed in any manner. Pages shall be single-spaced, single-sided, 8.5 by 11 inches, with at least one-inch margins on all sides. All text, including text in tables, must adhere to all font size and line spacing requirements listed herein. Font and line spacing requirements do not have to be followed for illustrations, flowcharts, drawings, and diagrams. These exceptions shall not be used to circumvent formatting requirements and page count limitations by including lengthy narratives in such items. The page limitation covers all information except the cover page. Any pages in excess of the stated page limitation will be removed (after page 75) and will not be considered. (ii) The Technical Proposal shall fully address the approach in accomplishing the Program Objectives of Section I, Program Description. The contractor must also provide a summary of relevant past and present capabilities and experience. Both corporate and individual experience should be addressed (See evaluation criteria in Section V(2)). The offeror must provide sufficient technical discussion and technical detail to establish the soundness of the proposed approach; provide an adequate basis for assessing program technical cost and schedule risk; and form a sound basis for the cost proposed in Volume 2. The technical proposal shall also include an overall test plan, with a supporting test matrix and discussion, which identifies all contractor- and Government-conducted testing, as well as the facilities at which the testing is to occur. The contractor must demonstrate knowledge of the systems engineering process and make realistic assumptions of how the proposed technology enhances performance at the missile system level; identify any perceived risks, and risk mitigation actions to be taken. b. Volume 2 - Cost Proposal: Cost proposals have no page limitations; however, offerors are requested to keep cost proposals under 100 pages as a goal. See FAR Table 15.2 for specific information for adequate cost proposal requirements. Cost proposal spreadsheets must be submitted in Microsoft Excel format. The Volume 2 formal cost proposal must include and segregate the contract costs by year, and also provide a total summary. The contract costs shall include, as a minimum, a labor category and man-hour breakdown, by task, including applicable labor rates, a cost element summary including labor, travel, other direct costs, consolidated bill of material, overheads, G&A, fee, etc., and reflecting all rates for the contract and data, and an expenditure schedule for the entire program. The offeror shall include estimates for the cost/value of any Government Furnished Property (GFP), and all costs expected to be incurred by the Government associated with providing the equipment, facilities and support necessary to meet the contractor's testing requirements. Any costs associated with data or data rights shall be separately identified in the cost proposal. Certified Cost or Pricing data shall be required in accordance with FAR 15.403. c. Cover Page: Both the Technical and Cost proposal must have a cover page with the following information: BAA Reference number "BAA-RWK-10-0004", Title of Paper, Period of Performance, Estimated Cost, Name/Address of Company, Commercial and Government Entity (CAGE) number, Dun & Bradstreet (D&B) Data Universal Numbering System (DUNS) number, Technical and Contracting Points of Contact (phones, fax and emails). The Cover page is NOT included in the page count. (5) Submission Dates and Times: White papers are due by 2:00 PM Central Time on 14 April 2010. White Papers received after this due date and time shall be governed by the provisions of FAR 52.215-1(c)(3). Both White Papers and Proposals must be submitted to AFRL/RWK Contracting Office to the parties shown in Section VII - Agency Contacts, paragraph (1). (6) Funding Restrictions: The cost of preparing White Papers/proposals in response to this announcement is not considered an allowable direct charge to any resulting contract or any other contract, but may be an allowable expense to the normal bid and proposal indirect cost specified in FAR 31.205-18. (7) Contractual Authority: Offerors are advised that only the Contracting Officer is legally authorized to contractually bind or otherwise obligate the Government. The Government reserves the right to award one, multiple, or no contracts, based on the proposals received and the requirements of the Government. V. WHITE PAPER/PROPOSAL/APPLICATION REVIEW INFORMATION: (1) White Paper Evaluation Criteria: White Papers will be evaluated as to their projected success in achieving the objectives/requirements outlined in Section I, of this BAA, utilizing the Factors and Sub-factors below. Additionally, a risk assessment (See section/paragraph V(3)) will be made of the offers, and selections will be made based on the Best Value to the Government. Awards may be made without discussions. Factors are listed in descending order of importance. All evaluation factors other than cost or price, when combined, are significantly more important than cost or price. (1.1) Factor (1) Scientific/Technical Merit - Sub-factors (a) through (c) are of equal importance. (a) Soundness of offeror's proposed RFIS Concept, proposed development, and producibility approach (b) Soundness of the offeror's proposed approach to conducting the design (c) Soundness of the offeror's proposed approach to performing test, evaluation and assessment of the design (1.2) Factor (2) Capabilities and Experience - Subfactors (a) through (c) in Factor (2) are of equal importance. (a) Personnel/Management: Experience and capabilities of key personnel (both technical and management); experience and capabilities to manage technical risks, control cost and schedule. (b) Facilities, equipment and techniques necessary to accomplish the project. (c) Subcontract Management: Experience and capabilities to manage subcontractor performance, cost and schedule; nature and extent of reliance on subcontractor. Capabilities and experience may include unique combinations of these subfactors, which are integral factors for achieving proposal objectives. Experience may be best indicated by work performed on programs of similar scope and complexity within the last 5 years. Any resumes should be in a separate Appendix, which is not included in the White Paper page limits. The Government team may request supplemental historical information if required to confirm/verify experience and capabilities. (1.3) Factor (3) Cost - Cost/Price includes the reasonableness and realism of the proposed cost and fee and consideration of proposed budgets and funding profiles. Cost/Price is a substantial factor, but ranked as the third order of priority. (2) Proposal Evaluation Criteria: Proposals will be evaluated as to their projected success in achieving the objectives/requirements outlined in Section I, of this BAA, utilizing the Factors and Sub-factors below. Additionally, a risk assessment (See Section V(4)) will be made of the offers, and selections will be made based on the Best Value to the Government. Awards may be made without discussions. Factors are listed in descending order of importance. All evaluation factors other than cost or price, when combined, are significantly more important than cost or price. (2.1) F...