L_and_M_Lowest_Price_Technically_Acceptable_v2.pdf

PR: FD2060-14-30523

7 August 2015 1

L-900. INSTRUCTIONS TO OFFERORS

A. The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation. To assure timely and equitable evaluation of proposals, offerors must follow the instructions contained herein. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined unacceptable and therefore not considered eligible for award. If a joint venture arrangement exists for this acquisition, the offeror shall provide a copy of the joint venture agreement that is signed and dated by all joint venture members as part of the proposal submission. Proposals shall be submitted to the Government in three (3) separate volumes as set forth below:

PAGE NUMBER

VOLUME LIMITS OF COPIES DESCRIPTION

I N/A 2 paper/1electronic* Completed RFP and Clauses II 30 2 paper/1 electronic* Written Technical Proposal

*All proposal information shall be submitted in written form (2 copies) and CD-R or DVD-R (write once/read only copy) that is “closed” so that no further writes can be made to the media. CD-R/W or DVD-R/W media types are not acceptable. Media must be virus scanned by the offeror prior to submitting to the Government.

In addition to the page limitations set forth above, proposals should comply with the following format:

(1) The sealed package used to submit the proposal package must show the time and date specified for receipt. Each volume shall be marked with the RFP number and the offeror’s name and address, and the number of the Volume, i.e. I, II, etc. Proposals shall be in the English language and all monies shall be proposed in United States dollars.

(2) Print shall be no smaller than a font size of 12 and should be on 8 1/2 x 11 inch paper, excluding any charts, graphs, drawings, diagrams, supporting illustrations, or spreadsheets, etc. Charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc. shall not be greater than 11” x 17”. Each volume within the proposal shall be separately tabbed and identified. Margins shall be no smaller than 1 inch and each page within a volume shall be numbered consecutively. Elaborate formats, bindings, or color presentations are not desired or required.

(3) The page limitation for Volume II, Written Technical Proposal, is 30 pages. The page limitation includes any charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc.,but excludes any cover page, table of contents or list of acronyms (if utilized). Offerors are cautioned that any pages that exceed the page limitations shall not be read but shall be removed and either retained in the contract file without being considered in the evaluation, or, sent back to the offeror.

(4) Page limitations may be placed on Evaluation Notices (ENs), if issued. The specified limits for EN responses will be identified in the letters forwarding the ENs to the offerors or on the EN form itself.

(5) Each page containing proprietary information should be so marked.

(6) Each page should contain the following legend at the bottom of each sheet:

SOURCE SELECTION INFORMATION--SEE FAR 2.101 and 3.104

FOR OFFICIAL USE ONLY

(7) Submission of the initial proposal packages via electronic mail will not be accepted. Initial proposal packages shall either be mailed or hand-delivered.

Offerors are cautioned that Warner Robins Air Logistics Complex has visitor control procedures requiring individuals not affiliated with the installation to obtain a visitor pass prior to entrance. Some delay should be

7 August 2015 2 anticipated when hand-delivering proposal packages. Offerors should allow for sufficient time to obtain a visitor pass and arrive at the specified office PRIOR to the time specified for receipt of proposals.

Communications:

Exchanges of source selection information between Government and offerors will be controlled by the Contracting Officer/Contract Specialist. Email may be used to transmit such information, only if the email can be sent encrypted, and must include “Source Selection Information – See FAR 2.101 and 3.104” in the subject line of the email. Otherwise, source selection information will be transmitted via direct mailing or facsimile. In order to facilitate the sending and receiving of encrypted emails, offerors must use MS Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption. If you intend to submit your source selection information via encrypted email, you will need to contact the Buyer/Contracting Officer indicated on the face page of the solicitation prior to that first submittal in order to exchange certificates used for encryption. To ensure the process is working correctly, send a test encrypted message first (without including any source selection information). When submitting source selection information via email, file suppression utilities, to include but not limited to zip files, will not be accepted.

B. Volume I, Completed RFP and Clauses will consist of the completed and signed RFP with a cover letter delineating any exceptions taken to the RFP terms and conditions with accompanying rationale. However, offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined unacceptable and therefore not considered eligible for award. Offerors shall ensure that all clauses and provisions that require “fill-in” information are appropriately completed, including the proposed prices associated with the contract line items in the Schedule of the RFP.

The Government intends to award without discussions, but reserves the right to conduct discussions if determined necessary. Any discussions will be conducted in accordance with FAR 15.306. Proposals received are subject to the requirements specified in FAR 52.215-1, unless otherwise tailored in the Addendum to the solicitation. Proposals must be received by ALFCMC/WNYKA, 235 Byron Street, Suite 19A, Robins AFB, GA Attention:Brandi Moody, by the date and time specified in Block 8 on the face page of the RFP.

C. Volume II, Written Technical Proposal:

1. The written technical proposal shall be clear, concise, and include all the information required by this provision in sufficient detail for effective evaluation. 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. Offerors shall assume the Government has no prior knowledge of their capabilities, work processes, facilities, and experience and will base its evaluation on the information presented in the offeror’s technical proposal.

2. The following information shall be provided in the technical proposal and will be evaluated to assess technical acceptability (which includes the consideration of technical risk) in accordance with Section M-900, Evaluation Basis for Award. The technical proposal address each of the following subfactors to describe the offeror’s proposed approach to performing the requirements set forth in the Performance Work Statement (PWS).

For each subfactor, the offeror shall identify risks, if any, associated with the proposed approach and actions the offeror will take to mitigate the identified risks. If no risks/mitigations are identified in the offeror’s proposal, it indicates the offeror does not consider there to be any risk associated with their proposed approach.

Subfactor One: Technical Requirements The technical proposal shall specially address/provide the following:

i. How will you meet the technical requirements as defined in the following PWS paragraphs?

a) 4.2.2 Level of Repair - what steps will you take to repair Pocket-J LRUs?

b) 4.2.5 Configuration Management (CM)- how will you implement Pocket-J CM?

c) 4.13 Technical Data - how are you postured to write Technical Orders

7 August 2015 3

d) 4.13 Technical Data - how are you postured to complete Engineering Drawings?

e) 4.14 Provisioning - describe your experience with provisioning

f) 5.2 Clearances - describe how many of your team have the required security clearances and how your facility meets the requirements for facility security

ii. The narrative discussion and supporting documentation shall include but are not limited to the qualifications, security clearances and level of experience with regards to the engineering and technical personnel to perform the technical requirements, and the method for providing the required services where technical data is limited and/or not available.

Subfactor Two: Government Furnished Equipment (GFE) Management

i. How will you manage the GFE as defined in the following PWS paragraphs?

a) 4.3 GFE management - methods used to account for and maintain inventory stock levels

b) 4.3.3 MILSTRIP Repair - methods of shipping classified and unclassified materiel

ii. The narrative discussion and supporting documents shall include but are not limited to identification of physical storage location(s), method of shipping, method of tracking and monitoring of incoming and outgoing assets and quality assurance provisions for ensuring proper configuration and functionality for use within the Pocket J system.

Subfactor Three: Repair and Maintenance Requirements

i. How will you manage the the repair and maintenance requirement in the following PWS paragraphs?

a) 4.5 Help Desk - state your plan for providing help desk services

b) 4.6 Unscheduled Maintenance - describe your expertise to meet this requirement (trouble shooting, system knowledge, experience with Link-16 and SADL, experience with networks)

c) 4.7 Scheduled Maintenance - detail your experience in performing preventative maintenance

d) 4.12 Travel - describe your policies to ensure compliance with FAR 31.205-46

e) 4.17 Hardware, Inspections and Repair - what oversight mechanism will be used for subcontractors performing repairs

ii. The narrative discussion and supporting documents shall include but are not limited to quality assurance provisions for ensuring proper configuration and functionality for use within the Pocket J system, and method for supporting the replacement of non-reparable, consumable parts where technical data is limited and/or not available.

Subfactor Four: Information Assurance Requirements

i. How will you manage Information Assurance (IA) requirement in the following PWS

a) 6.1 IATO/ATO - describe your experience with obtaining ATO.

b) 6.1 IATO/ATO - state your experience with RMF.

c) 6.2 Contractor Responsibilities - detail your experience with SSP and testing.

d) 6.3 IA Scans - describe your previous use of SSC scans.

e) 6.4 Urgently Required IA Fixes - detail your plan to evaluate IAVAs .

ii. The narrative discussion and supporting documents shall include but are not limited to the method for supporting the Program Office IA Manager on IA actions.

7 August 2015 4

Subfactor Five: Block Cycle Upgrade Requirements

i. How will you meet the block cycle upgrade requirement as defined in the following PWS paragraphs ?

a) 8.1 Block Upgrade Requirements - describe your experience with the support documents associated with block cycle upgrades .

b) 8.1.1 Engineering Change Proposals (ECPs) - describe yor experience with ECPs.

c) 8.1.3 Acceptance Criteria -state your experience with AF testing

d) 8.1.6 Test Environment Support - how are you postured to set up a test bed?

e) 8.1.8 Software Maintenance and Update - state your familiarity with Simple Network Management Protocol (SNMP).

f) 8.1.9 Documentation/Trouble Reports - describe familiarity with Government trouble reports and fixes based on categorization

The narrative discussion and supporting documents shall include but are not limited to the method for supporting, testing and implementing software updates.

7 August 2015 5

M-900. EVALUATION BASIS FOR AWARD

1. Basis for Contract Award.

A. This acquisition will utilize the Lowest Price Technically Acceptable (LPTA) source selection procedure in accordance with FAR 15.101-2 and 15.3 as supplemented by the DoD Source Selection Procedures referenced in DFARS 215.300 to make an integrated assessment for a best value award decision. The Government intends to award one contract as a result of this solicitation. A decision on the technical acceptability of each offeror’s proposal will be made. Among those offerors who are determined to be technically acceptable, award will be made to the offeror having the lowest total evaluated price. Award will be made to the responsible offeror whose proposal is technically acceptable, conforms to all solicitation requirements, such as terms and conditions, representations and certifications, technical requirements, and also provides the best value to the Government based on the results of the evaluation described in paragraph 2 below. Contract terms and conditions consistent with customary commercial practices are specified in the solicitation/contract, with otherwise tailored terms and conditions specified in the Addendum to the solicitation/contract.

B. The Government intends to award without discussions, but reserves the right to conduct discussions if determined necessary. Any discussions will be conducted in accordance with FAR 15.306. If the Contracting Officer determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the Contracting Officer, with the concurrence of the Source Selection Authority, may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals. Award will be made to one responsible offeror whose proposal conforms to all solicitation requirements such as terms and conditions, meets all of the requirements set forth in the RFP, technical requirements, provides representations and certifications as required, and provides the best value to the Government based on the results of the evaluation described in this provision.

2. Proposal Evaluation. The evaluation process will be accomplished as follows.

A. Technical Factor.

Each offeror’s written technical proposal shall be evaluated , based on the subfactors below, to determine if the offeror provides a sound, compliant approach that meets the requirements of the performance work statement and demonstrates a thorough knowledge and understanding of those requirements and their associated risks.

The technical proposal addresses each of the following subfactors in sufficient detail. For each subfactor, the offeror identifies risks, if any, associated with the proposed approach and actions the offeror will take to mitigate the identified risks. If no risks/mitigations are identified in the offeror’s proposal, it indicates the offeror does not consider there to be any risk associated with their proposed approach.

Subfactor One: Technical Requirements

iii. How will you meet the technical requirements as defined in the following PWS paragraphs?

a) 4.2.2 Level of Repair - what steps will you take to repair Pocket-J LRUs?

b) 4.2.5 Configuration Management (CM)- how will you implement Pocket-J CM?

c) 4.13 Technical Data - how are you postured to write Technical Orders?

d) 4.13 Technical Data - how are you postured to complete Engineering Drawings?

e) 4.14 Provisioning - describe your experience with provisioning.

f) 5.2 Clearances - describe how many of your team members have the required security clearances and how your facility meets the requirements for facility security

iv. The narrative discussion and supporting documentation shall include but are not limited to the qualifications, security clearances and level of experience with regards to the engineering and

7 August 2015 6 technical personnel to perform the technical requirements, and the method for providing the required services where technical data is limited and/or not available.

Subfactor Two: Government Furnished Equipment Management

iii. How will you manage the GFE as defined in the following PWS paragraphs?

a) 4.3 GFE management - methods used to account for and maintain inventory stock levels

b) 4.3.3 MILSTRIP Repair - methods of shipping classified and unclassified materiel

iv. The narrative discussion and supporting documents shall include but are not limited to identification of physical storage location(s), method of shipping, method of tracking and monitoring of incoming and outgoing assets and quality assurance provisions for ensuring proper configuration and functionality for use within the Pocket J system.

Subfactor Three: Repair and Maintenance Requirements

iii. How will you manage the the repair and maintenance requirement in the following PWS

a) 4.5 Help Desk - state your plan for providing help desk services.

b) 4.6 Unscheduled Maintenance - describe your expertise to meet this requirement (trouble shooting, system knowledge, experience with Link-16 and SADL, experience with networks).

c) 4.7 Scheduled Maintenance - detail your experience in performing preventative maintenance.

d) 4.12 Travel - describe your policies to ensure compliance with FAR 31.205-46.

e) 4.17 Hardware, Inspections and Repair - what oversight mechanism will be used for subcontractors performing repairs.

iv. The narrative discussion and supporting documents shall include but are not limited to quality assurance provisions for ensuring proper configuration and functionality for use within the Pocket J system, and method for supporting the replacement of non-reparable, consumable parts where technical data is limited and/or not available.

Subfactor Four: Information Assurance Requirements

iii. How will you manage Information Assurance (IA) requirement in the following PWS

a) 6.1 IATO/ATO - describe your experience with obtaining ATO.

b) 6.1 IATO/ATO - state your experience with RMF.

c) 6.2 Contractor Responsibilities - detail your experience with SSP and testing.

d) 6.3 IA Scans - describe your previous use of SSC scans.

e) 6.4 Urgently Required IA Fixes - detail your plan to evaluate IAVAs.

iv. The narrative discussion and supporting documents shall include but are not limited to the method for supporting the Program Office IA Manager on IA actions.

Subfactor Five: Block Cycle Upgrade Requirements

ii. How will you meet the block cycle upgrade requirement as defined in the following PWS

7 August 2015 7

a) 8.1 Block Upgrade Requirements - describe your experience with the support documents associated with block cycle upgrades.

b) 8.1.1 Engineering Change Proposals (ECPs) - describe your experience with ECPs.

c) 8.1.3 Acceptance Criteria -state your experience with AF testing.

d) 8.1.6 Test Environment Support - how are you postured to set up a test bed?

e) 8.1.8 Software Maintenance and Update - state your familiarity with Simple Network Management Protocol (SNMP).

f) 8.1.9 Documentation/Trouble Reports - describe familiarity with Government trouble reports and fixes based on categorization.

iii. The narrative discussion and supporting documents shall include but are not limited to the method for supporting, testing and implementing software updates.

The technical rating reflects the evaluation of the acceptability of the offeror’s technical approach for meeting the Government’s requirement. The technical risk associated with the offeror’s proposed technical approach will also be considered as part of the technical acceptability decision. technical risk, which is manifested by the identification of weaknesses, assesses the degree to which an offeror’s proposed approach for the requirements of the solicitation may cause disruption of schedule, increased costs, degraded performance, the need for increased government oversight, and the likelihood of unsuccessful contract performance. The evaluation shall address the Government’s identification of any weakness as well as the offeror’s identified risks and proposed mitigation (if applicable) and document why that is or is not acceptable. The Government may independently identify risks not identified by the offeror and assess its impact to the successful performance of the contract.

Should the Government determine that any risks identified by either the offeror or the Government poses too great a risk to the program and does not address a suitable mitigation, the Government may consider the proposal technically unacceptable. The offeror’s proposal shall be evaluated to determine whether the proposal is acceptable or unacceptable, using the ratings and descriptions outlined in the table below. One technical rating will be assigned to each technical subfactor. In order to be considered awardable, there must be an “acceptable” rating in every subfactor.

Technical Acceptable/Unacceptable Ratings:

Rating Description Acceptable Proposal clearly meets the minimum requirements of the solicitation.

Unacceptable Proposal does not clearly meet the minimum requirements of the solicitation.

B. Price Factor

The Government will evaluate each offeror’s proposed prices submitted in Volume I, Completed RFP and Clauses, for reasonableness and balance as discussed in paragraphs (i) and (ii) below. Offerors are reminded that in order to maintain reasonable/balanced pricing, the Government will not accept “Not Separately Priced (NSP),” No Charge (NC), $0, etc. on any line items other than those already designated as “NSP” in the Schedule. Offerors are advised to review all data items and ensure that they are proposing to the specific data requirements and level of effort involved. For data items, where the quantity of one (1) lot is specified, the quantity of one (1) shall be used. The Government will calculate a Total Evaluated Price (TEP) for each offeror’s proposed prices in accordance with paragraph (iii) below.

(i). Reasonableness: The existence of adequate price competition is expected to support a determination of reasonableness. Price analysis techniques may be used to further validate price reasonableness. If adequate price competition is not obtained and/or if price reasonableness cannot be determined using price analysis of Government obtained information, additional information in accordance with FAR 15.4 may be required to support the proposed price.

7 August 2015 8

(ii). Balance: Unbalanced pricing exists when, despite an acceptable total evaluated price, the price of one or more contract line items is significantly overstated or understated as indicated by the application of proposal analysis techniques. The Government shall analyze the proposed prices to determine whether there are unbalanced separately priced line items or sub-line items. Prices submitted will be compared and evaluated to assure that a logical progression exists as related to price and quantity changes within each offeror’s response to the pricing structure in Section B (The Schedule). Offerors are cautioned against submitting an offer that contains unbalanced pricing; offers that are determined to be unbalanced may be rejected if the lack of balance poses an unacceptable risk to the Government.

(iii). Total Evaluated Price (TEP). The Government will utilize the following methodology to determine the TEP of each proposal. All unit prices shall be rounded to the nearest whole dollar. The TEP will be calculated for evaluation purposes only. Offerors are reminded that the evaluation of options shall not obligate the Government to exercise the option. The TEP will be calculated as follows:

(a) For those proposals that do not have quantity ranges for any CLINs, the Government will multiply the identified quantity by the proposed unit price to obtain an extended price for each CLIN (and Sub-CLIN). For those proposals that do not identify specific quantity ranges and propose only one price for the entire BEQ amount, the Government will consider that range to be 1 to the BEQ amount. The sum of all the CLINs (and Sub-CLINs) will represent the evaluated price for the basic and option contract period.

(b) For those proposals that have quantity ranges for CLINs, the Government will multiply the proposed range unit price(s) by the quantity included in each range to obtain an evaluated price for that CLIN (and Sub-CLIN). For the CLINs that do not utilize quantity ranges, the Government will multiply the identified quantity by the proposed unit price to obtain an evaluated price for each CLIN (and Sub-CLIN). The sum of all of the CLINs (and Sub- CLINs) will represent the evaluated price for the basic and option contract period.

(c) The sum of all the CLINs’ evaluated prices (Basic Year and all Options) will represent the total evaluated price. Offeror’s are required to price all CLINs (and Sub-CLINs), unless designated Not Separately Priced (NSP), with reasonable and balanced prices. All unit prices shall be rounded to the nearest whole dollar.

For Illustration Purposes Only:

QUANTITY RANGE EXAMPLE

CLIN From To Quantity Per Range Unit Price

Total Price

X00X 1 10 10 $100 $1,000 11 30 20 $90 $1,800 31 60 30 $85 $2,550 Evaluated Price for

CLIN

$5,350

The Government intends to award without discussions, but reserves the right to conduct discussions if determined necessary. Any discussions will be conducted in accordance with FAR 15.306. Proposals received are subject to the requirements specified i...