Sec_L_jmm20DEC2017_v2.docx

FOR OFFICIAL USE ONLY

SOURCE SELECTION INFORMATION – SEE FAR 2.101 AND 3.104

SECTION II

SOLICITATION PROVISIONS

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.14 GENERAL INSTRUCTIONS

The offeror shall prepare the proposal as follows:

XX_VOL 1 – TECH_ PERFORMANCE DATA_MMDDYYYY.xlsx or docx or .pdf XX_VOL 1 – TECH_ PERFORMANCE SUPPORT INFO_MMDDYYYY. docx or .pdf XX_VOL 1 – SMALLBP_SBCERT_MMDDYYYY docx or .pdf 25 page limit No page limit 100 page limit

XX_VOL 2 – COST_DETAILS_MMDDYYYY.xlsx, No page limit

Offerors shall replace XX with the company name/short-name and MMDDYY with the date of the proposal. For example, ACME TOOL_Volume 7 – OFFER_01312017.docx.

In order to reduce proposal size, proposals shall be limited to the number of pages outlined above for each volume. Page limit is viewed as total pages within a file including, but not limited to, table of contents, cover page, etc. All proposal information shall be confined to the appropriate file. Pages containing text shall be typewritten using the standard letter size (8.5 x 11) in Microsoft Word. Text shall be in a minimum of twelve (12) point Times New Roman font and the page layout shall have no less than one inch (1) margins. Drawings or other graphics shall be reduced only to the extent legibility is not lost. Any table or graphic shall have a minimum of ten (10) point Times New Roman font. All pages shall be appropriately numbered using style “X of Y” with X being the specific page and Y being the total page number for the respective document. Additionally, each page shall be marked with the complete company name, date, and solicitation number in the header or footer.

L.15 PROPOSAL CONTENTS

All information the offeror intends to have considered shall be submitted with the initial proposal. Initial proposal shall contain the best offer. Offerors are responsible for including sufficient information to permit a complete, thorough, and accurate evaluation of the submitted proposal. Proprietary information shall be clearly marked.

L.15.1 Cover Letter Offerors shall submit a cover letter on company letterhead. It shall not exceed three (3) pages, including the signed Standard Form 33 (SF 33).

L.15.1.1 Cover Letter shall include the following:

L.15.1.2 Offerors shall attach to the cover letter any submissions required in accordance with Section K of this solicitation. Submission requirements for Section K are not included in the page limit for the cover letter.

L.15.2 Volume 1 – Technical

L.15.2.1 – Compliance with the Complete Requirement.

(a) The Offeror shall indicate its intention to fully meet all requirements set forth in: Performance Work Statement (PWS) Section 3.0; and PWS Attachment A, System Performance Specifications (SPS), in its entirety.

(b) The Offeror shall submit a Compliance Matrix (Matrix) with applicable supporting performance data, information, test results, and directly relevant supporting narrative.

(1) The Matrix will address each paragraph of the entire PWS and the entire SPS.

(2) Each PWS/SPS paragraph addressed in the Matrix shall be cross-referenced to the Offeror's proposal including any and all supporting information and test data, including, but not limited to system and modem performance curves, transmit/receive channel gain, EIRP, spectrum compliance, procedures for setup/teardown, size and weight characteristics, and system power characteristics. The words for each paragraph contained in the PWS need not be repeated in the compliance matrix, only the reference number. Upon acceptance by the Government, all proposed documents, including supporting information and test data, will become part of the contract.

(3) The Matrix shall contain a definitive Offeror response for each PWS/SPS paragraph in the form of “yes” or “no.” A "yes" response to a paragraph number shall mean that the Offeror has read and understood the paragraph and can meet the requirements identified and is supported by the Offeror's narrative discussion and/or submitted plans. A "no" response will result in an unacceptable rating. Failure to provide a response will also result in an unacceptable rating. Stipulations, caveats and/or terms and conditions associated with a "yes" response for any compliance matrix response will result in an unacceptable rating.

(4) Thresholds: The Matrix shall provide a deeper level of response for the following aspects of technical performance: Throughput; Distance; Setup Time; Antenna Self-Alignment; Transport; and Two Person Setup. For these 6 aspects of system performance, the Offeror shall additionally indicate in the matrix that it either can or cannot meet the threshold level of performance. The Offeror must provide supporting test data to support these performance claims.

(5) Objectives: The Matrix shall provide the deepest level of response for the following aspects of technical performance: Throughput; Distance; and Setup Time. For these 3 most critical aspects of system performance, the Offeror shall additionally specify in the matrix what degree of performance it can provide above the threshold values. The Offeror must provide supporting test data to support these performance claims.

L.15.2.2 –Verification of Claimed System Performance

(a) Offerors are instructed that the Government shall selectively verify specific system performance claims made by the Offerors. Verification shall take the form of the System Verification Demonstration (SVD). Proposed Offeror systems will be evaluated at a Government test range to objectively verify –

(b) Offerors are instructed that by submitting the written proposal, they are obligating themselves to support the SVD.

The following shall be considered the “SVD PLAN.”

(c) SVD shall be conducted as per the following controlling conditions, procedures, guidance, and instructions:

(1) Location - Fort Bliss, TX and White Sands Missile Range (WSMR), NM.

(2) Demonstration Manager - Program Manager Tactical Networks (PM TN).

(3) Duration - no longer than 4 weeks.

(4) Schedule - Specific dates to be provided to offerors following RFP release.

(5) Fairness - the Government shall strive to ensure a fair and objective process and shall apply the same plans and procedures to all Offerors proposed systems.

(7) It is the responsibility of the Offeror to – Provide the requisite personnel to conduct the physical SVD;

Limit the total number of Offeror personnel to ten (10) (consisting of the prime and any subcontractor) will be permitted to attend the SVD, of which, no more than 2 will be allowed to participate in the physical setup. Up to 4-man team can be used to offload cases from a transport state to a ready for setup state.

Provide a minimum of two TROPO systems for SVD purposes with up to two additional replacement/backup systems to support the SVD and be prepared to operate continuously for 24 hours a day, 5 days a week for the duration of the SVD. If an offeror is not able to complete the SVD as a result of faulty equipment, the offeror shall receive no further consideration for award.

(9) Offeror – shall not be permitted to use the services of Government personnel in conjunction with its physical SVDs.

(10) Offeror – all Offeror personnel and vehicles shall have proper identification and shall process through the security check point at the designated government facilities.

(11) Offeror – Range Safety (complete required training and required visitor access request per attachment titled “Visit Request Steps”) Offerors are to provide 2 systems for the SVD no later than 3 weeks following the proposal submission deadline to the below address:

Attn: Aaron Brown 706-570-0973 Bliss Central Receiving Point BLDG 2527 Chaffee RD.

Fort Bliss, TX 79918

The Offeror’s candidate TROPO systems shall each be delivered as a turnkey system that is in compliance with all specifications in Appendix A.

The Offeror is solely responsible for ensuring its equipment’s shipping containers provide sufficient protection to eliminate any instances of transportation damage.

The Offeror, at no time, will be authorized to substitute the candidate TROPO system after the start of a test case, except when the candidate TROPO system under test fails.

A failed candidate TROPO system will be recovered by the Offeror’s onsite personnel to complete the test case. Regardless of the reason for the failure or method of recovery, the time for the Offeror’s onsite personnel to recover or replace the failed candidate TROPO system is limited to 60 minutes, during each test case, from the time the notification is made to the Offeror’s onsite personnel to fully restored operations. Failure to recover system in the specified time may result in offerors system not being considered for award.

Upon completion of the maintenance action to recover the failed candidate TROPO system, the Offeror’s onsite personnel will provide the Government with a written document that details the steps and procedures to correct the reported failure. In the event the maintenance action is not successful, the Offeror’s onsite personnel shall still provide a written document detailing the steps and procedures that occurred.

The Offeror shall not provide revised versions of their candidate TROPO systems or any proposed I&T equipment during SVD Testing.

Transport of the TROPO systems between the SVD storage facility and SVD test range is the responsibility of the Offeror.

(2) Government Upon receipt by the Government, the Offeror’s candidate TROPO systems will be placed under configuration control where all hardware and/or software baselines will remain fixed throughout the duration of the SVD.

After receipt of the TROPO systems for the SVD the Government will inventory, inspect, measure and weigh the Offeror’s candidate TROPO systems and record findings.

Government SVD Testing personnel will actively monitor all government test equipment utilized in the conduct of the SVD for failures or anomalies, and will promptly replace the test equipment to eliminate any potential for impact to testing of an Offeror’s candidate TROPO systems.

Government troubleshooting activities will not be performed during SVD test case execution.

The re-run of any test case(s) is at the sole discretion of the Government, and will not be performed in a manner that affords an unfair advantage or disadvantage to any Offeror.

All candidate TROPO systems will be returned to their respective Offeror at the conclusion of the SVD activity in their original shipping containers. Offerors shall be responsible for the shipping costs to return their candidate TROPO systems to the Offeror’s designated facility.

Government SVD Test personnel will act as observers and/or data collectors at the SVDs, and there will be no contractual discussions between Offeror and Government during the SVD.

The Government will provide generators for the SVD per requirements stated in Appendix A of this proposal Government will provide Highly Mobile Multi-Purpose Wheeled Vehicles (HMMWV) in order to evaluate the Offerors systems per Appendix A for transport. The HMMWVs will not be utilized for transport between the storage and test locations.

If circumstances (inclement weather, range safety event, etc…) arise that prevent the completion of the demonstration within the prescribed time frames, the Government will work to adjust and accommodate accordingly to ensure all Offeror’s are afforded the ability to complete the demonstrations.

L.15.2.3 Small Business Participation A Small Business Subcontracting Plan (a requirement for all Other Than Small Businesses) shall be submitted by the offeror and will be reviewed and evaluated in accordance with FAR 52.219-9, and AFARS Appendix DD. In accordance with FAR 9.104-3(b), prior compliance with subcontracting plans required by FAR subpart 19.7 shall be considered in determining the responsibility of an Offeror bidding on a contract requiring a subcontracting plan.

Offeror shall submit information substantiating the compliance with FAR 52.219-8, “Utilization of Small Business”, maximizing opportunities for U.S. small business subcontractors.

Offeror shall also provide a statement indicating whether any negative information has been reported in the past five years concerning the past compliance with FAR 52.219-8.

If any such negative information has been reported, the Offeror may submit explanations or comments responding to such negative information.

Offerors with no prior contracts containing FAR 52.219-8 shall certify the same.

Offeror shall utilize “Small Business Certification” attachment to convey results and name this document XX_VOL 1 – SMALLBP_SBCERT_MMDDYYYY.

L.15.3 Volume 2 -- Cost The Cost Volume shall include the information, detailed in the subparagraphs below, as it applies to the configuration as described in Appendix A.

Offerors shall submit a cost narrative with sufficient documentation necessary to adequately support and explain the costs proposed as required below. Offerors are advised that in order to be considered for award, proposed costs shall be determined fair, reasonable, and realistic. Offerors that fail to provide all of the supporting documentation as required above may not be eligible for award. If after receipt of proposals the Contracting Officer determines there is insufficient information available to determine cost reasonableness or cost realism and none of the exceptions identified in FAR 15.403-1 apply, the offeror may be required to submit certified cost and pricing data. There is no page limitation for the cost narrative.

Offerors shall provide whatever information is necessary for the Government to determine why the proposed costs are realistic as required below. In accordance with FAR 15.403-1(b), data other than certified cost or pricing data is required to support cost realism. All rates proposed in support of proposed costs shall include clear and precise references to the related supporting documentation. All supporting documents shall be referenced and explained within the Cost Volume Narrative. Any rates reflected in the supporting documentation provided shall exactly match the rates in the proposal.

Offerors shall support any proposed rates with the most recent and relevant supporting documentation including, if available, any applicable: Forward Pricing Rate Agreements (FPRA’s); Forward Pricing Rate Recommendations (FPRR’s) from DCAA or DCMA; Forward Pricing Rate Proposals (FPRP’s); and Compensation Rate Tables approved by DCMA or DCAA. If providing an FPRR, FPRP, Approved Provisional Rates Proposal, or other statement of current rates, offeror shall provide adequate informational support including 3 (three) years of historical actual pool and base information (by expense account) that validates the proposed rates.

Offerors shall provide evidence that the Government has determined the offeror’s disclosure statement under FAR Part 30 to be adequate. If an offeror certifies for an exemption to the requirement for a disclosure statement in accordance with FAR 52.230-1 (Section K of this solicitation), the offeror shall state so in the Cost Narrative.

Offerors shall provide evidence of an adequate accounting system. Evidence may include emails, letters, or reports from DCAA or DCMA.

15.4 -- Volume 3 -- Organic Sustainment Strategy

The Offeror’s proposed Sustainment Strategy shall address the following areas of hardware and software support:

Hardware:

Depot Transition Plan – The Offeror shall propose a strategy to support the establishment of organic sustainment no later than five years from task order award. A Transition Strategy Plan for establishing specified level of organic support shall be provided to include but not limited to the following items:

A schedule defining the sequence and timelines of events and activities required for facilitating Government Sustainment Capabilities no later than five years after task order award. (The schedule shall be excluded from the page count) Itemization of the Technical Data required for Offeror’s Proposed Level of Organic Support to include but not be limited to training, automated tools, firmware, devices, hardware repair maintenance procedures, drawings, wiring diagrams, and documentation. The Offeror shall identify and address those technical data listed within the CDRLs that will be provided to facilitate Offeror’s defined/specified level of organic sustainment.

Documented procedures and processes for establishing training for/of Organic support established within Government Resources.

Identification of test equipment and maintenance procedures required for the Organic depot to maintain the test equipment. This includes any software required to keep the test equipment relevant after hardware baseline changes. The Offeror’s plan shall include training the Organic depot on the use and maintenance of test equipment, and identify associated documentation that will empower Government’s ability to verify the functions of the hardware products developed under this contract.

Special requirements associated with the system that the government would require to sustain it.

The Government may consider giving strengths in the area of depot plan transition for the following considerations, however, this does not limit or restrict the Government from considering giving additional strengths for aspects of an Offerors proposal that have merit or exceed specified performance or capability requirements:

Test, Troubleshooting and Repair – Offeror's maintenance concept includes tools and test equipment to diagnose LRU/SRU failure at field level with a minimum 97% confidence level.

Common Tools: Test, Troubleshooting and Repair - The tools required to execute vendor’s recommended field level maintenance require tools that are listed in the Government TMDE preferred items list, are in common use by the Army, or are readily available to the Army.

CDRLs – Offeror’s proposal identifies the technical data required under the Government provided CDRLs and any technical data required under the Offeror recommended CDRLs which will enable the government to achieve Organic Depot Sustainment to implement Offeror’s proposed Organic sustainment strategy Technical Data – The Offeror is able to provide the government (unlimited or (Government Purpose Rights) (GPR)) data rights, drawings and wiring diagrams. For any components that the Offeror is unable to provide, negotiate with sub vendors to provide the government obsolescence escrow, in accordance with the PWS.

CM Processes – The Offeror shall define the Configuration Control Board processes that enables the Government to identify, adjudicate, and prioritize issues/discrepancy reports related to procured hardware that impacts accepted mission functionality. The Offeror shall provide consideration for leveraging industry partner-driven enhancements as set forth by Offeror’s proposal. The Offeror shall address Government’s ability to identify and prioritize for timely resolution critical latent defects impacting Mission Assurance.

The Offeror shall identify associated documentation required for Government to establish the ability to verify the Quality Assurance of the Sustainable Hardware Configuration Items.

DMSMS - The Offeror shall identify the proposed DMSMS approach and respective responsibilities of the Offeror and Government. This plan shall lay out how much notice the government will receive in advance of component obsolescence. At minimum the offeror’s plan shall ensure 90 days advance notice.

Procurement of Spares - The Offeror shall identify how they will facilitate competitive procurement of hardware spare and repair parts to the maximum extent possible. The Offeror shall address which technical data items (which are currently listed within the CDRLs) will be needed to facilitate the competitive procurement of spare and repair parts. This Offeror shall identify any technical data, or other intellectual property licensing restrictions that will hinder government from executing competitive procurement of spare and repair parts.

Software:

The Offeror shall propose a plan that describes the establishment of organic sustainment no later than four years from Task Order award. A Transition approach for establishing organic support shall be provided to include but not limited to:

A schedule defining the sequence and timelines of events and activities required for facilitating Government Organic Sustainment Capabilities no later than 4 years from Contract Order award. (The schedule shall be excluded from the page count).

Itemization of the necessary Technical Data, Software, Hardware and Software Documentation required for Offeror’s Proposed Level of Organic Support to include but not be limited to training, software, automated tools, firmware, devices, hardware and documentation.

Documented procedures and processes for establishing training for/of Organic support established within Government Resources The range, roles and responsibilities that afford the government the ability to analyze, assess, support executing code updates/enhancement, regression test, as well as integrate baseline changes (i.e. for resolving major to minor fixes).

15.5 -- Volume 4 -- Past Performance Offerors are reminded that while the Government may elect to consider data obtained from other sources, the burden of providing thorough and complete past performance information rests with the offeror.

Offerors shall submit three (3) recent and relevant past performance examples. Each example shall not exceed two (2) pages and shall include the following:

· Contract number, order number if applicable, CAGE code, DUNS number, and North American Industry Classification System (NAICS) code

· Government contracting activity, Contracting Officer name, telephone number, and email address

· Government Contracting Officer Representative (COR) and/or technical representative, telephone number, and email address

· Government contract administration activity, Administrative Contracting Officer (ACO) name, telephone number, and email address

· If offeror performed as a subcontractor, prime contractor company name, point of contact name, telephone number, and email address in lieu of or in addition to the contact information required in (b), (c), and (d) above

· Contract type

· Awarded price/cost

· Final (actual) or projected final (if ongoing) price/cost

· Final (actual) or projected final (if ongoing) start and end dates of the period of performance

· Percentage of effort, based on the total cost of the work required in the referenced contract or order, performed by the offeror as prime contractor or subcontractor at the time of the proposal submission

· Description of the specific tasks or activities performed by the offeror itself under the contract Narrative: Offerors shall provide a narrative for each past performance example. The narrative shall describe the contract listed, the contract objectives achieved by the offeror, and how the contract is relevant to the requirements of this solicitation.

Self-assessment: Offerors shall provide a self-assessment for each past performance example. The self-assessment shall address performance, including if the contractor met the schedule and technical requirements within the original estimated cost. If the original cost, schedule, or technical requirements of the contract were not met, the offeror shall provide a brief explanation of the reason(s) the original requirements were not met and any corrective actions taken by the contractor. The offeror shall identify each time the schedule (period of performance) or cost ceiling was revised and provide an explanation of why each revision was necessary.

Offerors shall submit copies of any and all of the following received on any contracts or orders within the past five (5) years, including those not proposed in response to this solicitation:

Termination for default (including the settlement agreement) Notice of default (including the settlement agreement) No-cost settlement (including the settlement agreement) Show cause notice Cure notice Suspension or Debarment Any security inspection or assessment ratings or reports indicating security programs or facilities are less than satisfactory, and/or any suspensions or revocations of a facility security clearance Notifications received for violations of FAR 32.006 Offerors shall include a narrative explaining each event above, including any corrective actions taken, not to exceed one (1) page per event.

If none of the above were received within the past five (5) years, the offeror shall state so in the proposal.

Offerors shall state if they have no recent or relevant past performance.

Joint ventures. If an offeror proposes as a legal joint venture, the CAGE provided shall be specifically for the joint venture submitting the proposal as the offeror. If an offeror proposes using the CAGE for only one of the companies participating in the joint venture, that company shall be considered the one and only offeror, and the past performance of partners, teammates, or subcontractors shall not be submitted.

Predecessor companies. If the proposed past performance was performed by a predecessor company, provide the information for the recent and relevant contract of the predecessor company and document the history of the evolution from the predecessor company, not to exceed one (1) page.

Offeror shall NOT propose past performance examples of subcontractors or teammates. If an offeror proposes past performance examples of subcontractors or teammates, the offeror shall be ineligible for award.

Section L Page 12 of 12