0011_SRW_Section_L_Instructions.docx

ATTACHMENT 0011 – SECTION L

1.1. OVERVIEW

The contract resulting from this request for proposal shall be awarded to that responsible Offeror whose offer, conforming to the RFP, is determined to provide the “best value” to the Government.

The Government intends to evaluate proposals and award the contract resulting from this RFP without discussions with the Offerors with the exception of clarifications as described in FAR 15.306(a); and will evaluate each offer on the basis of the Offeror’s initial proposal. Therefore, the initial proposal should contain the Offeror’s best terms from a technical and price standpoint. However, the Government reserves the right to conduct discussions and request final proposal revisions if it is determined it is in the Government’s best interest to do so.

The Government reserves the right to establish a competitive range for evaluating proposals if it is determined it is in the Government’s best interest to do so.

1.1.1. General Instructions

1.1.1.1. This section provides general guidance for preparation of proposals as well as specific instruction on the format and content of the proposal. The Offeror’s proposal must include all data and information requested and must be submitted in accordance with these instructions. The proposal shall be compliant with requirements as stated herein. Non-conformance with these instructions may result in an unfavorable proposal evaluation. Any Offeror who submits an incomplete proposal (i.e., lack of Technical Proposal, Price Proposal, Past Performance Proposal, Small Business Participation Plan) may be considered unacceptable.

1.1.1.2. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for sustaining the validity of the stated claims. The proposal should not simply rephrase or restate the Government’s requirements, but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements. The Offeror shall assume that the Government has no prior knowledge of the Offeror’s facilities and experience and will base its evaluation on the information presented in the Offeror’s proposal.

1.1.1.3. Questions regarding this Request for Proposal (RFP) must be made in writing via e-mail no later than 1100 EDT 10 calendar days after RFP release and directed to the Contract Specialist, Mr. Nicholas Bartolomei at: nicholas.bartolomei.civ@mail.mil. When submitting questions, please reference “RFP No. W15P7T-12-R-0059” in the Subject Line and reference the specific RFP Section(s), Paragraph(s), and Page(s) you are inquiring about. All questions will be answered via amendment and provided to all Offerors on the Internet at https://acquistion.army.mil/asfi/. No questions will be attributed to the respective Offerors. The Government reserves the right to decline addressing questions received after this date and time. Telephonic questions will not be accepted.

1.1.1.4. If an Offeror believes that the requirements in these instructions contain an error, omission, conflict, or are otherwise unsound; the Offeror shall immediately notify the Contract Specialist listed above in writing with supporting rationale. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

1.1.1.5. The Offeror may request debriefings by providing a written request to the Contracting Officer. If the Government elects to establish a competitive range, the Contracting Officer will promptly notify the Offeror of any decision to exclude an offer from the competitive range. Upon written request, an Offeror may receive a debriefing in accordance with Federal Acquisition Regulation (FAR) 15.505. To the maximum extent practicable, debriefings will be conducted within five working days after receipt of the Offeror’s request.

1.1.1.6. The Government may conduct a pre-award survey and/or site visit prior to any contract award. The pre-award survey may examine the Offeror’s record of integrity and business ethics (which includes satisfactory compliance with the law including tax, labor and employment, environmental, antitrust, and consumer protection laws) technical ability, production capacity, management structure, financial capability, accounting systems, security controls/clearances, labor resources, performance record, and ability to meet required schedules.

1.1.2. Proposal Instructions, Format and Content

1.1.2.1. Introduction. Each Offeror is required to submit the Technical, Past Performance, Price Proposal, and Small Business Participation Plan as outlined below. The Offeror shall submit a written proposal in accordance with these Proposal Submission Instructions. The Offeror shall also complete Section B and Section K of the RFP and furnish this information with its proposal. Offerors need to have a current profile at the Central Offeror Registration (https://www.bpn.gov/ccr/) in order to submit proposals. Offerors must have a current valid Classified Material Storage (CMS) account in order to receive classified information.

1.1.2.2. Proposals shall be submitted prior to 2:00 PM EDT on XX XX 2012. The Offerors proposal shall be submitted electronically via the Army Single Face to Industry (ASFI) in separate and discrete volumes or files. Files shall not contain classified data. The use of hyperlinks in proposals is prohibited and any such links will not be viewed or considered. The URL for ASFI is \*HYPERLINK h t t p s : / / a c q u i s i t i o n . a r m y . m i l / a s f i / (). ASFI User guides and Frequently Asked Questions can be found at : \ * H Y P E R L I N K " h t t p s : / / a c q u i s i t i o n . a r m y . m i l / a s f i / A S F I F A Q . c f m (https://acquisition.army.mil/asfi/ASFI_FAQ.cfm). For ASFI technical assistance please email the ASFI help desk at usarmy.redstone.acc.mbx.hqacc-asfi@mail.mil . Offerors need to have a current profile at the Central Offeror Registration \ * H Y P E R L I N K h t t p s : / / w w w . b p n . g o v / c c r / (https://www.bpn.gov/ccr/ ) in order to submit proposals.

1.1.2.2.1. WARNING: To avoid submission of late proposals, we recommend the transmission of your proposal file one business day prior to the required proposal due date and time.

1.1.2.3. The Offeror shall prepare proposal volumes with the titles and page limitation show below:

COMPANYNAME_SRW_VOL_1_SUBVOL_A_WAVEFORMS.PDF

COMPANYNAME_SRW_VOL_1_SUBVOL_B_CERTIFCATIONS.PDF

COMPANYNAME_SRW_VOL_1_SUBVOL_C_SUITABILITY.PDF

No Limit

No Page Limit

No Page Limit

V - Delivery Order 0001 - Technical

COMPANYNAME_SRW_VOL_5_DO_0001_TECH.PDF

COMPANYNAME_SRW_VOL_5_SUBVOL_A_PROD_SCHED.PDF

COMPANYNAME_SRW_VOL_5_SUBVOL_B_CERT.PDF

COMPANYNAME_SRW_VOL_5_SUBVOL_C_SUIT.PDF

COMPANYNAME_SRW_VOL_5_SUBVOL_D_MAN.PDF

COMPANYNAME_SRW_VOL_5_SUBVOL_E_QASP.PDF

COMPANYNAME_SRW_VOL_6_SANITIZED_COST_DO_0001.xls COMPANYNAME_SRW_VOL_6_COST_NARRATIVE_DO_0001.doc No Page Limit

VII - Delivery Order 0002 - Technical

COMPANYNAME_SRW_VOL_7_DO_0002_TECH.PDF

COMPANYNAME_SRW_VOL_7_SUBVOL_A_PROD_SCHED.PDF

COMPANYNAME_SRW_VOL_7_SUBVOL_B_CERT.PDF

COMPANYNAME_SRW_VOL_7_SUBVOL_C_SUIT.PDF

COMPANYNAME_SRW_VOL_7_SUBVOL_D_MAN.PDF

COMPANYNAME_SRW_VOL_7_SUBVOL_E_QASP.PDF

COMPANYNAME_SRW_VOL_8_SANITIZED_COST_DO_0002.xls COMPANYNAME_SRW_VOL_8_COST_NARRATIVE_DO_0002.doc No Page Limit

1.1.2.4. Proposal Files.

1.1.2.4.1. Format. The submission shall be clearly indexed and logically assembled. Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date, and solicitation number in the header and/or footer. Microsoft Office will be used to create the files. Files shall use the following page set-up parameters:

1.1.2.4.2. The following additional restrictions apply:

1.1.2.4.2.1. Each paragraph shall be separated by at least one blank line. A standard, 12-point minimum font size applies. Arial or Times New Roman fonts are required. Tables and illustrations may use a reduced font size not less than 8-point and may be landscape. 11”x17” (TABLOID) sized pages are permitted and will only count as one page. 11”x17” pages may only be used for schedules, drawings, and other documents more appropriate to larger paper. In no case shall 11”x17” pages be used exclusively for text.

1.1.2.4.2.2. Page numbers, company logos, and headers and footers may be within the page margins ONLY, and are not bound by the 12-point font requirement. Footnotes to text shall not be used. If the Offeror submits annexes, documentation, attachments or the like, not specifically required by this solicitation, such will count against the Offeror’s page limitations unless otherwise indicated in the specific Volume instructions below. Pages in violation of these instructions, either by exceeding the margin, font or spacing restrictions or by exceeding the total page limit for a particular volume, will not be evaluated. Pages not evaluated due to violation of the margin, font or spacing restrictions will not count against the page limitations. The page count will be determined by counting the pages in the order they come up in the print layout view.

1.1.2.4.2.3. Each volume shall be properly identified, numbered, and logically assembled. Each factor shall contain clearly identified sections and all pages shall be appropriately numbered and identified by the complete company name, date, and solicitation number in the header and/or footer.

1.1.2.4.3. File Packaging. All of the proposal files shall be submitted in accordance with the instructions found in the ASFI Vendor Bid Response System (BRS) Users Guide. The link to the ASFI Vendor BRS Users Guide is found on page 5 of the ASFI User Guide located a t \ * H Y P E R L I N K " h t t p s : / / a c q u i s i t i o n . a r m y . m i l https://acquisition.army.mil . These instructions are as follows:

1.1.2.4.3.1. Pricing Type Data: All pricing information shall be included only in Volumes III, VI and VIII. Under no circumstances shall pricing type data be included elsewhere in the proposal. Paragraph cross-referencing between Price Proposal paragraphs and technical proposal paragraphs is requested to provide clarity.

1.1.2.4.3.2. The electronic submittal shall consist of separate files as set forth in the paragraphs below. MS Office 2003 software or higher shall be used to create the required files. These files shall then be converted to searchable PDF format using Adobe Acrobat version 8.1.4 or greater.

1.1.2.4.3.3. PLEASE NOTE: There is a combined file limit of 10 Mb/upload. You must break your attachments into smaller files or utilize the upload utility multiple times if the upload exceeds the 10 Mb limit. Filenames MUST NOT contain single quotes, spaces, pound or percent signs. Your computer must also be running updated virus protection. If your computer is not protected, please do not upload files. Uploading files with viruses may jeopardize your electronic bid submission.

1.1.2.5. Content Requirements. All information shall be confined to the appropriate volume. All information the Offeror wishes to have considered must be submitted with the initial proposal. The Offeror shall confine submissions to essential matters, sufficient to define the proposal and provide an adequate basis for evaluation of each proposal. Each volume of the proposal shall include a Table of Contents (which is not included in any page limitations). Offerors wishing to restrict the disclosure of their proposal must mark their proposal in accordance with FAR 52.215-1(e).

1.1.2.6. The proposal shall remain valid for a minimum of 240 days and shall not contain classified data/information. Proposals offering a shorter period of time will be considered unacceptable and may be rejected. Proposal preparation costs, evaluation participation costs are the responsibility of the Offeror.

1.1.3. Government Furnished Information (GFI)

1.1.3.1. GFI, other than that described in 1.1.3.2, can be obtained via downloads from the JTRS Information Repository (IR) To gain access to the JPTR IR (http://ir-public.jpeojtrs.mil/) companies must request a JPTR IR user account by selecting “SECURE REGISTRATION PROCESS” on the public page. Government POC for sponsorship is: Dian Blum, PEO C3T, PdM NS, 443-395-1131, dian.e.blum.civ@mail.mil.

1.1.3.2. TRANSEC and COMSEC keys can be obtained through COMSEC channels.

1.1.4. Security Classification Guide (SCG).

1.1.4.1. No page limit; excluded from total page count. Offeror’s electing to propose on D.O. 0001 and/or D.O. 0002 shall provide a copy of an approved SCG for the offered radio IAW AR 380-5. If not available, the Offeror shall provide a draft SCG. The SCG or draft SCG will not be evaluated as part of D.O. award. However, Offerors who fail to submit a SCG or draft SCG may not be considered for award of D.O. 0001 or 0002.

1.1.5. Proprietary Software and Hardware.

1.1.5.1. No page limit; excluded from total page count. In addition to the Offeror’s Data/Software Rights Assertions (required in response to the provisions of DFARS 252.227-7017), the Offeror shall provide a detailed description of the functionality of any hardware, software or firmware developed exclusively at private expense, which has been incorporated into the SRW baseline. Furthermore, the Offeror shall provide a statement as to the percentage of the current software source code that was developed exclusively at private expense. In addition, the Offeror shall provide a statement as to whether the Offeror will deliver software (in executable code format or source code format) developed exclusively at private expense (which is incorporated in the offered SRW radio). This information will not be evaluated as part of contract award. However, Offerors who fail to submit this information may not be considered for award.

1.2. INSTRUCTIONS TO OFFERORS

1.2.1. VOLUME I – Technical: Page Limitation: 100 pages, single sided, unless specifically excluded below. Any additional pages included in the Offeror’s proposal above and beyond the page limitation shall not be considered by the Government in the evaluation of the Offeror’s proposal.

1.2.1.1. The Offeror shall submit a technical proposal for the offered SRW Radio addressing the Sub-Volumes below to enable the Government to complete a thorough evaluation. To this end, each technical proposal shall be specific, detailed, and complete so as to clearly and fully demonstrate that the prospective Offeror has a comprehensive knowledge and understanding of the requirements and objectives and has valid and practical solutions for any technical problems. Statements which paraphrase the specifications or attest that “standard procedures shall be employed, etc.,” are inadequate.

1.2.1.2. In the PWS, the term “shall” is used to mean a minimum threshold requirement. The term “objective” is defined as a desired performance characteristic that exceeds the minimum requirement. The terms “may” and “can” are not considered to be requirements. When an objective value is listed in conjunction with a threshold value it must be understood that the threshold value represents the minimum requirement that must be met while the objective value represents the desired performance characteristic. The Government will consider giving strengths for exceeding PWS threshold requirements. The Government may also consider giving strengths for meeting or exceeding objectives identified in the PWS. Such strengths may result in an increase in the rating that would otherwise be assigned for the relevant assessment.

1.2.1.3. All PWS requirements and any Offeror proposed objective values shall be incorporated into the contract.

1.2.1.4. Offerors’ Volume I – Technical shall contain the following sub-volumes:

1.2.1.4.1. Sub-Volume A - Waveforms

1.2.1.4.1.1. Software Version Description. No page limit; excluded from Volume I total page count. The Offeror shall provide a Software Version Description (SVD) IAW Data Item Description DI-IPSC-81442A, Software Version Description (SVD) which addresses all firmware, software, waveform(s) and/or the integrated build for the offered radio.

1.2.1.4.1.2. Requirements Traceability. No page limit; excluded from Volume I total page count. The Offeror shall provide a Requirements Traceability document indicating the extent that each requirement of the SRW Waveform Design Specification (WDS) Revision C, March, 2012 has been implemented (fully implemented, partially implemented, not implement) and how that requirement was verified/tested. Include a reference which captures the name and control information of the report that documents the verified or tested requirement. There is no requirement to meet all of the requirements in the WDS, however all requirements must be included in the Requirements Traceability.

1.2.1.4.1.3. Interoperability with JTRS POR and/or non-POR SRW Radio. No page limit; excluded from Volume I total page count. The Offeror shall provide artifacts attesting to over-the-air Interoperability with a Joint Tactical Radio Systems (JTRS) Program of Record (POR) and/or non-POR running the SRW waveform (such as the Rifleman Radio, Manpack Radio, and/or non-POR radio). If not supported by an operational event, provide technical, lab test documentation and analyses. Machine documented voice and data exchanges between radio systems is best evidence of OTA interoperability; documented human observations are acceptable.

1.2.1.4.1.4. Interoperability with IP Based Management Tools. No page limit; excluded from Volume I total page count. The Offeror shall provide artifacts attesting to interoperability between the offered radio and some or all of the targeted IP Based Management Tools, that is: Enterprise Network Manager (JENM); Joint Automated Communication-Electronics Operating Instructions Systems (JACS); Automated Communication Engineering Software (ACES); and the Soldier Radio Waveform Network Manager (SRWNM). The Offerors shall provide artifacts attesting to: the ability to consume keying material, consume initialization data, accept configuration files and re-configuration data and interoperable with other network management features. There is no requirement for the SRW radio to support all features from all of the targeted IP based management tools. However, if an interoperability capability with a specific tool has been documented that information should be provided for considerations. Machine documented success of the various network management capabilities is best evidence of interoperability with the tools; documented human observations are acceptable.

1.2.1.5. Sub-Volume B - Certifications

1.2.1.5.1. NSA Certification. Page Limit: 5 pages. The Offeror shall provide a copy of the NSA SECRET or Sensitive but UNCLASSIFED (SBU) Certification for the offered radio system. If not currently certified, the Offeror shall provide a certification plan stating the Radio System baseline configuration, what type of Certification is expected, when the Certification is expected, what steps remain to obtain Certification and the Government NSA POC. The Government may contact NSA to discuss the contents of the Offeror’s proposed certification plan.

1.2.1.5.2. ATO/DIACAP. Page Limit: 5 pages. The Offeror shall provide a copy of the Authority to Operate (ATO/Interim ATO (IATO) for the offered radio system. If no ATO currently exist, the Offeror shall provide a plan that details how and when they will receive an ATO. The successful implementation of the Defense Information Assurance Certification and Accreditation Process (DIACAP) culminates in an ATO. The DIACAP process will be followed while pursuing the ATO. The Government may contact the Designated Accreditation Authority (DAA) to discuss the contents of the Offeror’s proposed certification plan.

1.2.1.5.3. Spectrum Certification. No page limit; excluded from Volume I total page count. The Offeror shall provide a copy of the Spectrum Certification for the offered radio system. If not currently certified, the Offeror shall provide a completed DD Form 1494 (threshold requirement for Item 3 – Stage of Allocation is Stage 4 – Operational) with its proposal. The Government may contact the Headquarters Department of the Army (HQDA) Chief Information Officer (CIO) to discuss the contents of the Spectrum Certification.

1.2.1.5.4. SAR. No page limit; excluded from Volume I total page count. The Offeror shall provide a copy of a U. S. Army Electronic Communication Command (CECOM) Life Cycle Management Command (LCMC) approved Safety Assessment Report (SAR) for the offered radio. If no CECOM LCMC approved SAR currently exists, Offerors shall provide a draft SAR which includes all inherent safety hazards and all environmental considerations IAW MIL-STD-882E & MIL-STD-810G. The Government may contact the LCMC Safety Office to discuss the contents of the SAR.

1.2.1.6. Sub-Volume C - Suitability

1.2.1.6.1. Baseline Description Document. No page limit; excluded from Volume I total page count. The Offeror shall provide a Baseline Description Document depicting the offered SRW Radio System and its associated components to include all hardware, software and firmware IAW DI-CMAN-81121.

1.2.1.6.2. EMI/EMC. Page Limit: 15 pages. The Offeror shall provide a synopsis of results of the Electro Magnetic Interference (EMI) and Electro Magnetic Compatibility (EMC) tests that were completed on the offered radio as required by the PWS. The synopsis shall include complete reference to the applicable test plans and reports IAW MIL-STD-461F, MIL-STD-464C, and MIL-STD 2169B. The synopsis shall clearly state which PWS EMI/EMC requirements Passed (without comment), Passed With Comment, or Failed testing. A discussion should be included for all requirements that Passed With Comment or Failed testing.

1.2.1.6.3. Environmental. Page Limit: 15 pages. The Offeror shall provide a synopsis of results of the Environmental tests that were completed on the offered radio. The synopsis shall include complete reference to the applicable test plans and reports IAW MIL-STD-810G. The synopsis shall clearly state which PWS environmental requirements Passed (without comment), Passed With Comment or Failed testing. A discussion should be included for all requirements that Passed With Comment or Failed testing.

1.2.1.6.4. ILS Plan. Page Limit: 50 pages; these 50 pages are included in the total Volume I page count. The Offeror shall provide an Integrated Logistics Support (ILS) Plan that support CONUS and OCONUS operations and addresses all ten (10) integrated logistics support elements IAW Table 3-1 of AR 700-127. For the ILS elements of Maintenance Planning, Supply Support and Training Concept ensure the items below in paragraphs 1.2.1.6.4.1, 1.2.1.6.4.2, and 1.2.1.6.4.3 are addressed. Please note that Maintenance Planning, Supply Support and Training Concept are no more important than the other elements of the ILS Plan detailed in Table 3-1 of AR 700-127.

1.2.1.6.4.1. Maintenance Planning. Will be counted as part of the ILS Plan which is limited to a total of 50 pages. The Offeror shall provide a Maintenance Concept to support CONUS and OCONUS field operations. The Maintenance Concept should articulate how the Offeror’s approach will support a CONUS Repair Turn Around Time (RTAT) of 30 days and an OCONUS RTAT of 7 days. The Maintenance Concept will include a draft Maintenance Allocation Chart (MAC) with suggested spares and parts lists. The Maintenance Concept shall address how software, firmware and hardware upgrades will be applied to fielded units. The Concept shall address a plan for technology refresh.

1.2.1.6.4.2. Supply Support. Will be counted as part of the ILS Plan which is limited to a total of 50 pages. The Offeror shall identify any prepositioned or forward deployed spare radios and parts that will be utilized to ensure Repair Turnaround Time (RTAT) is met.

1.2.1.6.4.3. Training Concept. Will be counted as part of the ILS Plan which is limited to a total of 50 pages. The Offeror shall provide a course outline for the Radio System Operator/Maintainer Course and the Brigade and Below S-6 Network Planner and Configuration Course. The course outlines shall provide: Course Title, Subject Area, Learning Objective, Target Audience, Training Duration, Material Requirements, and Instructional Methods. The course outlines shall be provided in a table format (vice paragraph format). The S-6 Network Planner and Configuration Course should provide the unit’s network planning personnel task-based training that will allow for deployment of and planning for the SRW radio system within the larger network using Government provided IP based management tools. The S-6 class is not a “S-6 Operator Course.”

1.2.1.6.5. Reliability Analysis. The analysis shall be limited to 10 pages. The Offeror should provide the reliability, availability, maintainability (RAM) analysis that was the basis for the projected Repair Turnaround Time (RTAT). The Offeror may use either measured or calculated data but must state which was used.

1.2.2. VOLUME II – Past Performance

2. The Past Performance Factor Volume is comprised of a single volume. Offerors are responsible for including sufficient detail to permit a complete evaluation.

Page limitations on submissions (maximum 17 total pages):

2. Offerors are to provide information on recent and relevant contract for the Offeror, and the Offeror’s proposed critical subcontractor(s). Critical subcontractors are defined as members of an Offeror’s overall team who are expected to manufacture the cryptologic subsystem and/or Line Replaceable Units (LRUs). The Offeror shall only submit five (5) recent and relevant contracts for itself and its subcontractor(s) for efforts that it proposes to be performed by the Offeror and its subcontractor(s) on this solicitation. These may include Federal, state, local Government. Recent includes performance of contracts occurring within five (5) years of the date of issuance of this solicitation. Relevant past performance is defined as past performance that demonstrates knowledge or experience with software defined radio sets, or demonstrates management, cost, and technical experience with the design, development, production and or integration of software defined radio sets.

2. Contract Information: For each of the five (5) recent and relevant contracts, provide the following information: (Limit 3 pages per contract submitted, maximum 15 pages))

For any contracts that did not/do not meet original schedule or technical performance requirements, provide a brief explanation of the reason(s) for the shortcomings and any corrective action(s) taken to avoid recurrence. Offerors must list each time the delivery schedule was revised and provide an explanation of why the revision was necessary. All Requests for Deviation and Requests for Waiver shall be addressed with respect to causes and corrective actions.

(l) Offerors shall also provide copy of any Cure Notices or Show Cause Letters received on each contract listed and a description of any corrective action implemented by the Offeror or proposed subcontractor. The Offerors shall indicate if any of the contracts listed were terminated and the type and reasons for the termination.

(m) Offerors shall state that no Cure Notices or Show Cause Letters were received on each contract listed by either the Offeror or proposed subcontractor.

2. The Offeror shall briefly describe the specific work activity to be performed by itself, as the prime Offeror, and by each of its critical partners/subcontractors/teammates in addition to providing the cage code for each. (Page limit 2 pages)

2. The Offeror shall sanitize the information relative to classified contracts.

2. The Offeror will indicate if it has no past performance. Offerors with no past performance will receive a neutral rating.

2. The above instructions are provided to advise Offerors as to the information required by the Government to assess the contractors recent and relevant past performance. Since this information constitutes a basis of the Government's review, it is imperative that the Offeror present its past performance in a clear and complete manner.

2. Corporate Entities. If any contract, listed as part of the Past Performance Factor submission, was performed by a corporate entity or division other than the corporate entity or division that would perform work under this solicitation, please identify them and indicate which entity will perform this effort. The Offeror shall also provide the above requested information for any proposed subcontractor on which the Offeror is submitting past performance information.

2. Predecessor Companies. If you, or your subcontractor(s), only have relevant and recent performance history as a part of a predecessor company, we may consider that past performance in our evaluation of past performance. Please provide the information for those recent, relevant contracts of that predecessor company. Offerors must also document the history of the evolution from the predecessor company.

2. Contacting References. Offerors are advised that the Government may contact any of the references that the Offeror provides, may contact other third parties for performance information, and the Government reserves the right to use any information received as part of its evaluation. Offerors shall include in their proposal the written consent of their proposed subcontractors to allow the Government to discuss the subcontractor's past performance.

1.2.2.10. Complete Information. The Government does not assume the duty to search for data to cure problems we find in proposals. The burden of providing thorough and complete past performance information remains with the Offeror. While the Government may elect to consider data obtained from external sources other than the proposal, such as from the Past Performance Information Retrieval System (PPIRS), the burden on providing thorough and complete past performance information rests with the Offeror.

1.2.3. VOLUME III – Basic IDIQ Cost/Price Proposal

1.2.3.1. The Offeror shall complete the MS Excel file named 0001-SRW Price Spreadsheet.xlsx in accordance with the embedded instructions. All prices shall be in U.S. dollars. Offers received in other than U.S. dollars may be rejected.

1.2.3.2. The Offerors price proposal shall reflect a range FFP for each of the hardware-related item and non-range FFP for non-hardware-related items. The Offeror shall provide prices for the range and non-range quantities as identified in 0001-SRW Price Spreadsheet.xlsx (see Attachment 0001) and for the five contract years and five one year options. The quantities of units for evaluation purposes are identified within the aforementioned workbook.

1.2.3.3. The contracting officer has determined there is a high probability of adequate price competition in this acquisition. However, if at any time during this solicitation the contracting officer determines that adequate price competition no longer exists; Offerors may be required to submit information other than cost or pricing data to support a determination of price reasonableness. The prices proposed upon award will be the contractual ceiling price; at subsequent task orders Offerors may propose hardware at or below this ceiling price as it deems necessary.

1.2.3.4. Offerors shall submit a pricing methodology document in order that the Government may understand its proposed prices. Each Offerors price proposal shall contain sufficient quantitative and narrative documentation necessary to adequately support and explain the proposed prices. At a minimum the pricing methodology shall include support for the range pricing step methodology and non-range pricing support buildup methodology. (No Page Limit).

1.2.3.5. Offerors’ Volume III – Cost/Price Proposal shall contain the following:

1.2.3.5.1. FFP Range Quantity Pricing. The Offeror shall submit range quantity unit prices for all range quantity FFP items listed in the MS Excel file named 0001-SRW Price Spreadsheet.xlsx. All line items shall be priced for all range quantities and all program and option years. All prices proposed by the Offeror shall be the final delivered price to the Government.

1.2.3.5.2. FPP non-Range Quantity Pricing. The Offeror shall submit unit prices for all non-range quantity FFP items listed in the MS Excel file named 0001-SRW Price Spreadsheet.xlsx, except for those that are proposed as not separately priced. All line items shall be priced for all program and option years. All prices proposed by the Offeror shall be the final delivered price to the Government.

1.2.3.5.3. Cost-Plus-Fixed-Fee (CPFF) Fixed Fee Ceiling Rate. On the basic contract support services are unknown and may be expected during the contract period. CPFF services will be defined and evaluated in accordance with (IAW) the FAR. Offerors shall propose on the 0001-SRW Price Spreadsheet.xlsx Excel spreadsheet the basic contract ceiling rate for each contract and option year. For all CPFF services required under all subsequent delivery orders, Offerors shall propose at or below this established ceiling rate. These fixed fees will be subject to downward negotiation by the Government on delivery orders.

1.2.3.5.4. Warranty. The Offeror shall submit all the warranty support information required in Attachment 0003 for each of the requested warranties required at FAR Clause 52.246-18 Warranty of Supplies of a Complex Nature. All supporting information, related to cost, shall be considered the final delivered price to the Government.

1.2.4. VOLUME IV – Small Business Participation Plan

All Offerors, whether small or large businesses, shall submit a Small Business Participation Plan. Offerors should propose the level of participation of small businesses (as a small business prime and/or small business subcontractors) in the performance of the acquisition relative to the objectives/goals set forth in the evaluation of this area. The Small Business Participation Plan shall include the following information outlined in 1.2.4.1 through 1.2.4.13 below:

Type of Business of Prime Offeror -- Check all applicable boxes:

{ } Large Prime or { } Small Business Prime; also categorized as a { } Small Disadvantaged Business (SDB) { } Women-Owned Small Business (WOSB) { } HUBZone Small Business (SBA certified) { } Veteran Owned Small Business (VOSB)

{ } Native American Owned / Tribally Owned Small Business { } Historically Black Colleges and Universities/Minority Institution (HBCU/MIs))

1.2.4.1. Submit the total combined percentage of work to be performed by both large and small businesses (include the percentage of work to be performed both by Prime and Subcontractors):

Example: If Prime proposed a price of $1,000,000 (including all options), and small business(es) will provide $250,000 in services/supplies as a prime or subcontractors, the % planned for small business is 25%; and 75% for large business equaling 100%.

Total Contract Value (TCV): (Including Options, etc) $__________ Dollar Value of your participation as a Prime Contractor: $_________ Total Percentage Planned for Large Business(es) __________% = $___________ Total Percentage Planned for Small Business(es) __________% = $___________

* Note – When combined, Large and Small Business totals must equal 100%.

1.2.4.2. Please indicate the total percentage of participation to be performed by each type of subcategory small business. An Offeror who qualifies as a small business should include its prime Contractor dollars in calculating its proposed percentage goals in all of the small business categories that it qualifies for. The percentage of work performed by small businesses that qualify in multiple small business categories may be counted in each category.

Example : Victory Prop Mgt (WOSB and SDVOSB) performing 2% ; and Williams Group (SDB, HUB Zone, and WOSB) performing 3%. Results equate to: SDB 3%, HUB Zone 3%, WOSB 5%, SDVOSB 2%, VOSB 2%). SDVOSBs are also VOSBs automatically; however VOSBs are not automatically SDVOSBs.

Offerors who propose small business participation percentages that cannot meet the Government’s Small Business goals for this procurement as stated in Section M “Basis for Award” shall explain in detail why such goals cannot be met.

NOTE: The sum of all the percentages need not equal 100% as individual subcontractors may be counted towards more than one category. All percentages shall use TOTAL CONTRACT VALUE as a baseline.

1.2.4.3. The extent to which such firms, as defined in FAR Part 19, are specifically identified in proposals.

Please provide a listing of all proposed Sub-Contractors, their Commercial and Government Entity (CAGE) code, and respective type of business concern in the format below. Any Sub-Contractor identified as a 8(a) or HUBZone MUST have an active SBA certification of its status at the time of proposal:

Company

CAGE

*Must Be SBA Certified

1.2.4.4. Describe the extent of commitment to use small businesses as defined by FAR 19, as subcontractors. Offerors that have enforceable agreements must provide fully executed copies (i.e. the entire agreement and not just the first and last pages) to receive more favorable consideration under Section M. An enforceable commitment is defined as “A written and signed agreement (by both parties) that details that all parties have agreed to a business relationship for this procurement. This document must be clear that both parties have defined and agreed to the extent of the relationship to include the type or types of work the sub-contractors/partners shall perform and what areas of the PWS they will cover. The agreement shall be specific in nature.”

1.2.4.5. A list of supply/service each small business will provide. Be as specific as possible (i.e. references to Statement of Work, etc.) to demonstrate the variety and complexity of work:

COMPANY

1.2.4.6. The realism of the proposal. Provide narrative information on how requirements for this effort were developed and why they are realistic.

1.2.4.7. Address past performance of the Offeror in complying with the requirements of the clauses at FAR 52.219-8, Utilization of Small Business Concerns, and, additionally for all large business Offerors, past performance of the Offeror in complying with FAR 52.219-9, Small Business Subcontracting Plan. For small businesses Offerors, if utilizing small businesses in current or prior contracts was not practicable IAW FAR 52.219-8, the Offeror shall explain why.

1.2.4.8. Provide any information substantiating the Offeror’s track record of utilizing small business on past contracts in detail, to include any justifications explaining why goals or targets were not met. For Large and Small businesses: provide descriptive historical information for ALL small business categories. Any information concerning long-term relationships with Small Business subcontractors, such as mentor-protégé relationships, should be provided. For Large Business: include their latest Administrative Contracting Officer (ACO) rating and, at a minimum, their two (2) most recent SF295s, Summary Subcontract Report (SSR) or Electronic Subcontracting Report equivalent. Provide a listing in the following format:

Small Business

Small Disadvantaged Business

Women Owned Small Business

Hubzone Small Business

Veteran Owned Small Business

Service Disabled Veteran Owned Small Business

Native American/Tribally Owned Small Busness

8(a) Small Business

1.2.4.9. Small Business (SB) Sub-Categories participation shall be expressed in dollars and percentages of TOTAL CONTRACT VALUE in each of the applicable authorized six digit 2007 North American Industry Classification System (NAICS) Industry Subsectors that the Offeror believes best describes the product or service planned for subcontracts, (available at http://www.census.gov/epcd/naics07/) and a total target for SB sub-categories participation by the Offeror. SB sub-categories targets by NAICS code shall be incorporated into any resulting contract and shall be required to report SB sub-categories participation.

Fill in the chart below to include dollars and percentages by NAICS code (expand if necessary):

(list all sub-categories as applicable)

1.2.4.10. Detailed explanations/documentation supporting the proposed participation percentages, or lack thereof. Also, list the details of what conferences or trade shows will be attended and their relevance to this requirement.

1.2.4.11. *Large Businesses Only. Each Large Business Offeror shall also provide a separate Small Business Subcontracting Plan meeting the requirement of FAR 52.219-9 and DFARS 252.219-7003 (or DFARS 252.219-7004 if the Offeror has a comprehensive subcontracting plan). This plan shall be submitted separately from the Small Business Participation Plan required above, which applies to both large and small businesses. The Small Business Subcontracting Plan is not a requirement for evaluation in source selection, but rather a requirement for award to a large business and will be incorporated into any resultant contract. Subcontracting plans shall reflect and be consistent with the commitments offered in the Small Business Participation Plan. The Small Business Subcontracting plan will be evaluated IAW with AFARS Appendix DD, and must receive an “Acceptable” rating prior to award.

1.2.4.12. In order to comply with the requirements for the Small Business Participation Plan, please be sure to include the following:

· Base your percentages on TOTAL CONTRACT VALUE

· Provide NAICS codes for all SB Sub Categories.

· Include detail and documentation supporting the small business goals you have proposed. If applicable, be sure you explain why goals cannot be met or exceeded as stated in Section M “Basis for Award”.

· Include detail regarding your historical performance with small businesses.

· Include specifics and details of how you will execute the plan in order to meet requirements (i.e. by providing specific trade shows/conferences and how they specifically affect performance on meeting requirements on this contract).

1.2.5. Volume V - Delivery Order 0001 - Technical

1.2.5.1. Sub-Volume A - Production Schedule. Page Limit: 5 pages. The Offeror shall provide a production and delivery schedule for the following items:

1.2.5.1.1. A total of 238 radio systems. The Offeror shall deliver 92 systems no later than 60 days after delivery order award and the remaining 146 radios no later than 120 days after delivery order award.

1.2.5.1.2. A total of 92 HMMWV installation kits. Shall deliver 92 HMMWV kits no later than 60 days after delivery order award.

1.2.5.1.3. A total of 228 MRAP installation kits. Shall deliver 228 MRAP kits no later than 120 days after delivery order award.

1.2.5.2. Sub-Volume B - Certification.

1.2.5.2.1. NSA Certification. Page Limit: 5 pages. The Offeror shall provide a copy of the NSA SECRET Certification for the offered radio system no later than 1500 EST on 1 February 2013. This certification shall be submitted via email to the Contract Specialist, Mr. Nicholas Bartolomei at: nicholas.bartolomei.civ@mail.mil, and the Contracting Officer, Mr. David Hackett, at david.e.hackett4.civ@mail.mil. Offerors who fail to submit certification by this date shall not be considered for award.

1.2.5.2.2. ATO/DIACAP. Page Limit: 5 pages. The Offeror shall provide a copy of the Authority to Operate (ATO/Interim ATO (IATO) for the offered radio system. If no ATO/IATO currently exists, the Offeror shall provide a plan that details how and when they will receive an ATO/IATO. The successful implementation of the Defense Information Assurance Certification and Accreditation Process (DIACAP) culminates in an ATO. The DIACAP process will be followed while pursuing the ATO/IATO. The Government may contact the Designated Accreditation Authority (DAA) to discuss the contents of the Offeror’s proposed certification plan. Offerors who fail to submit ATO plans that indicate they will obtain an ATO by 30 June 2013 will not be considered for award.

1.2.5.3. Sub-Volume C - Suitability. Page Limit: 70 pages. Offeror shall provide an itemized approach detailing their logistics support concept for the 238 radio systems being procured under this D.O. At a minimum, the support concept shall address CONUS and OCONUS installations (IAW PWS paragraph 4.4.7), interoperability and integration support services (IAW PWS paragraphs 4.4.6), sustainment maintenance and supply support (IAW PWS paragraph 4.4.4 & 4.4.5). Offeror shall provide training courses/materials and manuals (IAW PWS paragraph 4.4.3). Offeror shall be responsible for packaging, handling, shipping and storage (IAW PWS paragraph 4.4.10). Offeror shall adhere to identification/marking requirements (IAW PWS paragraph 4.4.11).

1.2.5.4. Sub-Volume D – Manpower. Page Limit: 5 pages. The estimated manpower for this requirement can be found at Volume VI – Delivery Order 0001 Cost/Price Proposal. Offerors shall provide a position description, and resume for all personnel proposed for the services described at D.O. 0001 PWS paragraphs 3.1 and 3.2. In addition, the Offerors shall all provide a narrative justifying why the position descriptions and resumes proposed are appropriate for the services to be performed. The position descriptions provided shall be incorporated into the PWS and become a requirement of the D.O.

1.2.5.5. Sub-Volume E – Quality Assurance Surveillance Plan. Page Limit: 10 pages. In accordance with FAR subpart 46.4 Offerors shall propose a QASP which describes how their performance should be measured against the requirements of this PWS. Offerors shall submit a QASP that includes key metrics that will be used throughout the period of performance of the awarded task order by the Government to assess the contractor’s quality of performance. At minimum Offerors proposal shall include the following key metrics within their proposed QASP: Cost control; Schedule; Contractor personnel resource control; radio system and installation kit requirements conformance. The methods described should be logical and relevant to the effort, and the metrics identified should be quantifiable, relevant to the effort and sufficient to measure performance. The QASP shall be proposed in a table format. Each metric proposed including the above required key metrics shall include at a minimum a performance objective, the standard to be met for evaluation of performance success, and how the Government should conduct the surveillance to ensure the metric proposed is accurately measured and assessed.

1.2.6. Volume VI – Delivery Order 0001 Cost/Price Proposal

1.2.6.1. The Offeror shall submit the following for this Firm-Fixed-Price, Cost-Plus-Fixed-Fee Term and Cost D.O.