Inactive

PROPOSAL DUE DATE AND TIME: This BAA will remain open for a period of SEVEN (7) years from the date of publication. NO PROPOSALS SHOULD BE SUBMITTED AGAINST THIS OVERARCHING BAA. Proposal due dates an... PROPOSAL DUE DATE AND TIME: This BAA will remain open for a period of SEVEN (7) years from the date of publication. NO PROPOSALS SHOULD BE SUBMITTED AGAINST THIS OVERARCHING BAA. Proposal due dates and times will be specified in CALLs published separately from the overarching announcement. Proposals received after the due date and time specified in the CALL shall be governed by the provisions of FAR 52.215- 1(c)(3). 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”. Note: If offerors use commercial carriers for delivery of proposals, carriers may not honor time-of-day delivery guarantees on military installations. Early proposal submission is encouraged. I. PROGRAM DESCRIPTION 1. Program Background Vanguard Center (formerly known as Maui High Performance Computing Center MHPCC) is one of five Defense Supercomputing Resource Centers (DSRCs) for the Department of Defense (DoD) High Performance Computing Modernization Program (HPCMP), and provides advanced, high-performance computing tools based on the latest technologies to Government researchers. The mission of the Vanguard Center is to evaluate and optimize early-production HPC technology and provide breakthrough software solutions to significantly increase the breadth and impact of the HPCMP. The strategic focus areas of the Vanguard Center are: ? Exploring and evaluating emerging HPC architectures and technologies ? Developing breakthrough, HPC-backed solutions for high priority DoD use cases ? Lowering barriers to high productivity computing by creating a modern HPC ecosystem In addition to the HPCMP-focused mission, the Vanguard Center contributes to the AFRL modeling, simulation, and data analytics (MS&A) enterprise which may include supporting real time, physics-based campaign level as well as space situational analyses. The Vanguard Center also plans to demonstrate high impact HPC integration and federation to address DoD needs in the Pacific Theater. Requirement Description The R&D requirement for this BAA is based on the Vanguard Center’s mission to evaluate and optimize earlyproduction HPC technology and provide breakthrough software solutions to significantly increase the breadth and impact of the HPCMP. In particular, research objectives center on emerging technologies and lowering barriers to the use of HPC. Vanguard Center is seeking to reduce risk and improve performance by transitioning HPC research and benchmarking hardware, application software, networking and refactoring approaches into HPCMP research system procurement activities; identify and exploit trends in HPC hardware and software to deliver capability and decrease time to solution for R&D. Additionally, the Vanguard center is seeking to advance DoD productivity through a modern HPC ecosystem. This ecosystem will integrate hardware (HW) and software (SW) to create dynamic workflows, increased accessibility, and enhanced collaboration by identifying trends in best software and Command and Control (C2) practices to improve effectiveness and productivity of R&D, including secure access to HPC using modern hardware and software. Tasks associated with these technical objectives may include: ? Exploring new architectures for HPC applicability such as: many core; GPGPUs; ARM64; next generation x86; data-intensive; cognitive; quantum; MLS ? Developing new software approaches for HPC applicability such as: Python (+ extensions); domain specific languages (DSL) ? Researching new networking approaches for HPC applicability and utility, to include programmable networks ? Exploring new network and system interfaces such as optical networks fused with optical interconnections and chip photonics ? Exploring and developing new computer/software/network ecosystems such as interactive computing and rendered results via Jupyter notebooks over application driven networks ? Developing new and/or updating legacy software (aka: code refactoring) for use with new and emerging HPC architectures ? Researching new network and software interfaces and developing software to provide secure access of HPC at different levels of security through modern browsers and devices, to include application driven networks ? Researching and developing HPC workflow extractions to support a broad class of physics-based modeling and simulation techniques for test and integration and speeding time to solution through innovative use of HPC hardware and software AFRL may seek teaming-approaches for testing and disseminating capabilities as ancillary to these technical areas. The teams may be established by parties external to the research or in addition to Government personnel. Deliverable Items: The following general data deliverables are representative of the types of data that may be required for any CALL: (1) program plan with updates as needed; (2) test plans; (3) monthly status/financial reports; (4) technical reports; (5) computer program documentation/software user manuals; (6) computer program/software source code; (7) final scientific and technical reports; (8) presentation materials; (9) patent reports; and (10) prototypes. Data deliverables are subject to negotiations on each individual CALL. The Scientific and Technical Report shall be prepared IAW the most current AFRL ANSI/NISO Standard Z39.18-2005 guidelines, or other most current report preparation guidance. 2. Schedule: The period of performance will be stated in the CALL. 3. White Papers/Proposals: White papers are brief descriptive summaries that can be submitted by offerors for consideration in response to this BAA solicitation as specified per individual CALL (see Section V for information on white paper evaluation procedures). Offerors whose white papers are evaluated as satisfying the technical merit factor (Section V, paragraph 2), and for which it is determined there is sufficient funding available, will be asked to submit a full technical and cost/business proposal. Offerors whose white papers were not selected to submit a technical cost/business proposal will be notified. 4. Organizational Conflict of Interest (OCI): OCI, if applicable, will be determined and addressed at the CALL level. 5. System for Award Management (SAM): Unless exempted by 2 CFR 25.110 all offerors must: (1) be registered in the System for Award Management (SAM) prior to submitting an application (for an award) or proposal; (2) maintain an active SAM registration with current information at all times during which it has an active Federal award or an application or proposal under consideration by an agency; and (3) provide its DUNS number in each application or proposal it submits to the agency. On-line registration instructions can be accessed from the SAM home page at www.sam.gov. Potential offerors that are notified as eligible for an award must submit annual Electronic Representations and Certifications via the System for Award Management (SAM) website at www.sam.gov. These FAR and DFARS level representations and certifications are required in addition to the representations and certifications that will be attached to each CALL. Before submitting the Electronic Representations and Certifications, Contractors must be registered in the Systems for Award Management (SAM) Database. II. AWARD INFORMATION 1. Anticipated Funding: The estimated overarching BAA ceiling is $48.0M. All funding is subject to change due to Government discretion and availability. All potential offerors should be aware that funding in any or all areas may change with little or no notice due to unanticipated budget fluctuations. 2. Anticipated Number of Awards: The Air Force anticipates awarding one or more contracts, and may consider an Assistance Instrument, or Other Transaction Procurements (OTPs). The Air Force reserves the right to select all, part, or none of the proposals received, subject to the availability of funds. * A version of this BAA for Assistance Instrument opportunities will be posted on www.grants.gov. 3. Anticipated Award Date: It is anticipated this BAA will remain open for a period of seven (7) years from the date of publication. This BAA will be reviewed annually. Any updates or possible cancellation will be issued as an amendment to the BAA. This annual review and subsequent amendment to the BAA shall meet the requirement of FAR 35.016 to publish the BAA no less frequently than annually. 4. Anticipated Period of Performance: The period of performance will be determined for each contract award based on the requirements of the effort. 5. Funding Restrictions: The cost of preparing white papers and/or proposals in response to a CALL 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 costs specified in FAR 31.205-18(c), Independent Research and Development and Bid and Proposal Costs. III. ELIGIBILITY INFORMATION 1. Eligible Offeror/Applicants: All responsible sources capable of satisfying the Government's needs may submit a proposal. Small Businesses, Small Disadvantaged Business (SDB), Woman-Owned Businesses, and Service-Disabled Veteran-Owned Businesses are encouraged to submit proposals; however, no part of this announcement will be a set-aside. Foreign or foreign-owned offerors are advised that their participation is subject to foreign disclosure review procedures. Foreign or foreign-owned offerors should immediately contact the contracting office focal point identified in the CALL for information if they contemplate responding. All correspondence must reference the BAA number, the BAA title and the CALL number. 2. Federally Funded Research and Development Centers: The following guidance is provided for Federally Funded Research and Development Centers (FFRDCs) contemplating submitting a proposal, as either a prime or subcontractor, in response to a CALL against this BAA. FAR 35.017-1(c)(4) prohibits an FFRDC from competing with any non-FFRDC concern in response to a Federal agency request for proposal for other than the operation of an FFRDC (with exceptions stated in DFARS 235.017-1(c)(4)). There is no regulation prohibiting an FFRDC from responding to a solicitation. However, the FFRDC’s sponsoring agency must first determine whether the proposed effort falls within the purpose, mission, general scope of effort, or special competency of the FFRDC, and that determination must be included in the FFRDC’s proposal. In addition, the non-sponsoring agency must determine if the work proposed would place the FFRDC in direct competition with domestic private industry. Only after these initial determinations are made will a determination be made concerning the FFRDC’s eligibility to receive an award. 3. Government Agencies: If a Government agency is interested in performing work, please contact the Technical Point of Contact (TPOC) identified in the CALL. If discussions result in a mutual interest to pursue your agency's participation, the effort will be pursued independently of this BAA. 4. Security Classification: Depending on the work to be performed, the offeror may require a classified facility clearance and safeguarding capability; therefore, personnel identified must be cleared for access to information at the equivalent level of security at the time of award. In addition, the offeror may be required to have, or have access to, a certified and Government-approved facility to support work under a CALL. If a DD Form 254 is applicable, it will be specified in the individual CALL with the applicable FAR clause attached. Offerors must verify their Cognizant Security Office information is current with Defense Security Service (DSS) at www.dss.mil. CALLs are anticipated to be unclassified. For CALLs requiring access to classified information, offerors must have a valid U.S. security clearance of SECRET or higher in order to respond. CALLs including information classified at the SECRET or higher level will be released only to offerors possessing the appropriate clearance. All classified material will be handled in accordance with E.O. 13526, National Industrial Security Program Operating Manual (NISPOM) DoD 5220.22-M, DoD Industrial Security Program 5200.01 Volume 1 through 4, and AFI 16-1406. 5. Foreign Participation: a. Foreign or foreign-owned offerors are advised their participation is subject to foreign disclosure review procedures. Foreign or foreign-owned offerors should immediately contact the contracting office focal point identified in Section VII for information if they contemplate responding. Foreign contractors will not be permitted to participate at the prime contractor level if it is determined the acquisition requires access to classified information. b. AFRL Policy on Employment of Non-US Citizen Contractors applies to this BAA. Contractor employees requiring access to USAF bases, AFRL facilities, and/or access to U.S. Government Information Technology networks in connection with the work on this contract must be U.S. citizens. Possession of a permanent resident card (“Green Card”) does not equate to U.S. citizenship. This requirement does not apply to foreign nationals approved by the U.S. Department of Defense or U.S. State Department under international personnel exchange agreements with foreign governments. Any waivers to this requirement must be granted in writing by the Contracting Officer prior to providing access. The above requirements are in addition to any other contract requirements related to obtaining a Common Access Card (CAC). c. This acquisition involves data that are subject to export control laws and regulations. Only contractors who are registered and certified with the Defense Logistics Services Center (DLSC) and have a legitimate business purpose may participate in this solicitation. Contact the Defense Logistics Services Center, 74 Washington Avenue N., Battle Creek, Michigan 40937-3084 (1-877-352-2255) for further information on the certification process. You must submit a copy of your approved DD Form 2345, Militarily Critical Technical Data Agreement, with your proposal. 6. Export Control: Information involved in this research effort will be subject to Export Control (International Traffic in Arms Regulation (ITAR) 22 CFR 120-130 or Export Administration Regulations (EAR) 15 CFR 730- 774). If the effort is subject to export control, then a Certified DD Form 2345, Militarily Critical Technical Data Agreement, will be required to be submitted with proposal. Export-Controlled Items: As prescribed by DFARS 225-7901, DFARS 252.225-7048, “Export-Controlled Item (JUN 2013)” is contained in this solicitation (as shown below). This clause shall be contained in ALL solicitations and resulting contracts. EXPORT-CONTROLLED ITEMS (JUN 2013) (a) Definition. “Export-controlled items,” as used in this clause, means items subject to the Export Administration Regulations (EAR) (15 CFR Parts 730-774) or the International Traffic in Arms Regulations (ITAR) (22 CFR Parts 120-130). The term includes: (1) “Defense items,” defined in the Arms Export Control Act, 22 U.S.C. 2778(j)(4)(A), as defense articles, defense services, and related technical data and further defined in the ITAR, 22 CFR Part 120. (2) “Items,” defined in the EAR as “commodities”, “software”, and “technology,” terms that are also defined in the EAR, 15 CFR 772.1. (b) The Contractor shall comply with all applicable laws and regulations regarding exportcontrolled items, including, but not limited to, the requirement for contractors to register with the Department of State in accordance with the ITAR. The Contractor shall consult with the Department of State regarding any questions relating to compliance with the ITAR and shall consult with the Department of Commerce regarding any questions relating to compliance with the EAR. (c) The Contractor's responsibility to comply with all applicable laws and regulations regarding export-controlled items exists independent of, and is not established or limited by, the information provided by this clause. (d) Nothing in the terms of this contract adds, changes, supersedes, or waives any of the requirements of applicable Federal laws, Executive orders, and regulations, including but not limited to— (1) The Export Administration Act of 1979, as amended (50 U.S.C.App.2401, et seq.); (2) The Arms Export Control Act (22 U.S.C. 2751, et seq.); (3) The International Emergency Economic Powers Act (50 U.S.C.1701, et seq.); (4) The Export Administration Regulations (15 CFR Parts 730-774); (5) The International Traffic in Arms Regulations (22 CFR Parts 120-130); and (6) Executive Order 13222, as extended; 7. Government Property availability: GP (to include government furnished equipment, property or information or contractor acquired property), if applicable, will be identified at the CALL level. If applicable, the contractor is responsible for all costs related to making the property available for use, such as payment of all transportation, installation, or rehabilitation costs in accordance with FAR 45.201(b). If GP is included in the CALL or requested in the white paper and/or proposal, the following clauses/provisions apply: a. FAR 52.245-1 Government Property (APR 2012) or FAR 52.245-1, Alt II (JAN 2017) if the resulting contract is for basic or applied research at a nonprofit institution of higher education or at a nonprofit whose primary purpose is the conduct of scientific research. b. FAR 52.245-9 Use and Charges (APR 2012), c. DFARS 252.211.7007 Reporting of Government-Furnished Property (AUG 2012), d. DFARS 252.245-7001 Tagging, Labeling, and Marking of Government-Furnished Property (APR 2012), e. DFARS 252.245-7002 Reporting Loss of Government Property (APR 2012) f. DFARS 252.245-7003 Contractor Property Management System Administration (APR 2012) g. DFARS252.245-7004 Reporting, Reutilization, and Disposal (SEP 2016) 8. Government Furnished Information (GFI) availability: GFI, if applicable, will be identified at the CALL level. If applicable, technical data or computer software provided to the Contractor as Government-furnished information (GFI) under this contract may be subject to restrictions on use, modification, reproduction, release, performance, display, or further disclosure. The Contractor will take all reasonable steps to protect the technical data or computer software against any unauthorized release or disclosure. GFI provided could consist of, but not be limited to, technical specifications, manuals, drawings, test data, and software. If GFI is included in the solicitation or requested in the proposal the following clauses/provisions apply: DFARS 252.227-7025 Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends applies. 9. Base Support/Network Access: Base support/network access may be provided under any resulting contract and will be specified in the individual CALL. 10. Data Rights: Required data rights will be identified per CALL; Minimum required data rights are: a. Technical Data: Unlimited Rights or Government Purpose Rights b. Non-Commercial Software (NCS): Unlimited Rights or Government Purpose Rights c. NCS Documentation: Unlimited Rights or Government Purpose Rights d. Commercial Computer Software Rights: Customary License, etc. e. Third Party Software (Commercial and Noncommercial) The Air Force Research Laboratory is engaged in the discovery, development, and integration of warfighting technologies for our air, space, and cyberspace forces. As such, rights in technical data and NCS developed or delivered under this contract are of significant concern to the Government. The Government will therefore carefully consider any restrictions on the use of technical data, NCS, and NCS documentation which could result in transition difficulty or less-than full and open competition for subsequent development of this technology. In exchange for paying for development of the data, the Government expects technical data, NCS, and NCS documentation developed entirely at Government expense to be delivered with Unlimited Rights. Technical data, NCS, and NCS documentation developed with mixed funding are expected to be delivered with at least Government Purpose Rights. Offerors proposing delivery of technical data, NCS, or NCS documentation (subject to Government Purpose Rights) should fully explain what technical data, NCS, or NCS documentation (developed with costs charged to indirect cost pools and/or costs not allocated to a Government contract) will be incorporated, how the incorporation will benefit the program, and address whether those portions or processes are able to be segregated. The Government expects delivery of technical data, NCS, and NCS documentation subject to Government Purpose Rights will fully meet program needs. Offers proposing delivery of technical data, NCS, or NCS documentation subject to Limited Rights, Restricted Rights, or Specifically Negotiated License Rights will be considered. Proposals should fully explain what technical data, NCS, or NCS documentation developed with costs charged to indirect cost pools and/or costs not allocated to a Government contract will be incorporated and how the incorporation will benefit the program. Offerors are reminded that the Identification and Assertion of Restrictions on the Government’s Use, Release, or Disclosure of Technical Data or Computer Software (the assertions list), required under DFARS 252.227- 7013 and DFARS 252.227-7014, is included in Section K and due at time of proposals. Assertions must be completed with specificity with regard to each item, component, or process listed. Note that DFARS 252.227-7014(d) describes requirements for incorporation of third party computer software (commercial and noncommercial). Any commercial software to be incorporated into a deliverable must be clearly identified in the proposal. Prior to delivery of any third party software, the contractor will obtain an appropriate license for the Government, and the written approval of the Contracting Officer. As used in this subparagraph, the terms Unlimited Rights, Government Purpose Rights, Specifically Negotiated License Rights, and Limited Rights in Technical Data are as defined in DFARS 252.227-7013. The terms Unlimited Rights, Government Purpose Rights, Specifically Negotiated License Rights, and Restricted Rights in noncommercial computer software and noncommercial software documentation are as defined in DFARS 252.227-7014. The term Commercial Computer Software is as defined in DFARS 252.227-7014. IV. APPLICATION AND SUBMISSION INFORMATION NO PROPOSALS OR WHITE PAPERS SHOULD BE SUBMITTED AGAINST THIS BASELINE BAA 1. 1-Step and 2-Step Procedures: The application process for opportunities presented in this BAA will be identified in CALLs published separately from the overarching announcement. Each CALL will identify the procedure to accept and evaluate offeror responses (One Step or Two Step) and if applicable, specify a date and time for receipt of proposals or white papers. Below is a description of One Step and Two Step procedures for acceptance and evaluation of offeror responses: When a one-step process is utilized by the Government, proposals submitted in response to CALLs should be submitted in accordance with this BAA and the individual CALL instructions. The Government reserves the right to select all, part, or none of the proposals received in response to a CALL, subject to the availability of funds and without negotiation/discussion. However, the Government reserves the right to negotiate with those offeror(s) whose proposal is selected for funding. When a large volume of responses are anticipated by the Government, a two-step process will be utilized requesting white papers. This two-step process is to streamline the proposal process and to assist offerors in determining whether to incur the cost of generating a formal CALL proposal (not all CALLs will require a submittal of a white paper). Offerors of those white papers evaluated as satisfying technical merit factor (Section V, paragraph 2) and for which it is determined there is sufficient funding available, will be sent a letter Request for Proposal (RFP) to submit a formal technical and cost proposal. An RFP does not assure an offeror of a subsequent contract award. White papers not selected for full proposal submission or proposals not selected for immediate funding will be disposed of/destroyed after the indicated holding period for each CALL. 2. Monitoring Government-wide Point of Entry: Offerors should monitor www.SAM.gov regularly for any BAA amendments that may permit extensions to the proposal submission date or make other changes. Offerors are advised that only Contracting Officers are legally authorized to contractually bind or otherwise commit the Government. 3. Response Costs: The cost of preparing a response to CALLs issued under this BAA are not considered an allowable direct charge to any resulting or any other contract; however, it may be an allowable expense to the normal bid and proposal indirect costs as specified in FAR 31.205-18. 4. Submitting Classified Information: DO NOT SUBMIT CLASSIFIED INFORMATION IN THE PROPOSAL. IF NECESSARY, CLASSIFIED MATERIAL SHALL BE SUBMITTED AS A SEPARATE ADDENDUM. SPECIFIC INSTRUCTIONS FOR SUBMITTING A CLASSIFIED ADDENDUM, UP TO SECRET, WILL NEED TO BE COORDINATED AND ARRANGED WITH THE TECHNICAL POCS FOR EACH CALL PRIOR TO SUBMISSION. 5. White Paper Submissions: Content and Form of Submission for White Papers (2-step process): The paragraphs below identify white paper format and content. White papers should be addressed and delivered as specified in the CALL. a. General Instructions White Papers (2-Step Process Only): Offerors including data in their proposals they do not want disclosed to the public for any purpose or used by the Government should mark restriction on disclosure and use of data. Technical and cost volumes should be submitted as separate volumes and must be valid for 180 days. The white paper volumes must reference the BAA number FA9451-18-S-0002, CALL number, and title. b. White Paper Format: The following format shall be used for submission of white papers in a 2-step process unless otherwise stated in the CALL. i. Page Size: 8 ½ x 11 ii. Microsoft Word format. iii. Margins – one-inch on each side iv. Font - Arial 11+ point v. Spacing: Single vi. Page Limit: Five pages maximum (One-side only) All text, including text in tables and charts, must adhere to all font size and line spacing requirements listed herein. No hard copies of the white papers are requested unless otherwise stated in the individual CALL. c. Instructions for White Paper Content: i. Cover Page (not to exceed one page): The white paper cover page shall include at a minimum: Title of the white paper; name of the organization submitting the white paper; organization size; technical and contracting points of contact; telephone number; fax; and email. Additionally, the cover page shall include BAA and CALL number and CALL title. ii. Technical/Business Content (not to exceed three pages): The technical content in white papers should capture the following information: innovative and technically sound approach to accomplish the CALL’s objective(s) and/or advances in knowledge, understanding, technology, and state-of-the-art. The Cost/Business content (which includes the ROM) should provide toplevel details on major cost items such as labor, special equipment that must be purchased, materials, and any subcontracts or other organizations’ costs (to include Government furnished facilities, equipment, or personnel) for the proposed effort. The ROM cost section shall not exceed one page. iii. Addendum (not to exceed one page): Include biographical sketches of the key personnel who will perform the research, highlighting their qualifications and experience. iv. After the review of white papers, the Government will determine whether a formal proposal will be requested based on the evaluation criteria listed in Section V, White Paper Evaluation Criteria. Offerors of those white papers evaluated as satisfying the technical merit factor (Section V, paragraph 2) and for which it is determined there is sufficient funding available, will be sent a Request for Proposal (RFP) letter to submit a formal technical and cost/business proposal to the contracting point of contact. An RFP does not assure an offeror of a subsequent contract award. White papers not selected for full proposal submission or proposals not selected for immediate funding will be disposed of/destroyed after the indicated holding period for each CALL. v. Any questions concerning the white paper preparation shall be referred to the Technical or Contracting POCs identified in the CALL. d. Handling and Transmittal Instructions: Electronic submission via DoD SAFE site or email is required, specific instructions will be provided at the CALL. Offerors are responsible for confirming receipt with AFRL/RKDB. AFRL/RKDB is not responsible for undelivered documents. 6. Full Proposal Submissions: The paragraphs below identify proposal format and content. Proposals should be addressed and delivered as specified in the CALL. (Note Full Proposal instructions apply to 1 and 2-Step processes) a. General Instructions Proposals: Offerors that including data in their proposals they do not want disclosed to the public for any purpose or used by the Government should mark restriction on disclosure and use of data. Technical and cost/business volumes should be submitted in separate volumes, and must be valid for 180 days. Proposals must reference the BAA announcement number FA9451-18-S-0002, CALL number and title. b. Proposal Format: i. The technical proposal shall be limited to 30 pages unless otherwise stated in the CALL and shall be prepared and submitted in Microsoft Word format. The Statement of Work (SOW) does not count against the page limit. ii. Cost/Business proposals have no page limitations; however, offerors are requested to keep cost proposals under 100 pages (cost break-outs should be submitted in Microsoft Excel with the formulas, all other information should be provided in Microsoft Word). iii. Paper Size – 8.5 inch x 11 inch iv. Margins – one-inch on each side v. Font - Arial 11+ point font or equivalent, to include tables, diagrams, and charts. Any other information (e.g. captions, restrictive markings) shall not be smaller than Calibri 10 point font or equivalent. vi. Pages shall be single-spaced and double-sided (each side counts as one page) vii. All text, including text in tables and charts, must adhere to all font size and line spacing requirements listed herein viii. The Technical proposal page limit does not include the offeror’s proposed SOW; however, the same formatting rules apply to the SOW, which is limited to ten (10) pages. Note: The number of hard copies and submission instructions will be stated in the individual CALL. c. Technical Volume: The technical volume shall include a discussion of the following information: creative or innovative and technically sound approach to accomplish the CALL’s objective(s) and/or advances in knowledge, understanding, technology, state-of-the-art, and rationale of the Offeror’s technical approach and the relevance to the Directed Energy Directorate/Vanguard Center’s program objective(s). The Offeror shall provide any information on prior work in the technical areas, descriptions of available equipment, data and facilities as attachments to the technical proposal. This information will be used in the proposal evaluation to help determine the soundness of the technical ap...