N00019-14-R-1004-0003.doc

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

L – [1] CONTENT OF PROPOSALS (SUPPLIES OR SERVICES)(JUN 2011) (October 23, 2014)

PART A

GENERAL INSTRUCTIONS

1.0

GENERAL

The Offeror is required to submit sufficient information concerning the following areas to enable Government personnel to fully ascertain capabilities of the Offeror to perform the requirements. The proposal must be sufficient in detail and scope to permit evaluation and provide the evaluators a clear understanding of the Offeror’s capability to meet or exceed the defined elements as required by the solicitation. All proposals must clearly and convincingly demonstrate that the Offeror has a thorough understanding of the requirements, associated risks and is able, willing and competent to devote the resources necessary to meet the requirements, and that the Offeror has valid and practical solutions for all requirements and potential risk areas. Offeror must respond to all requirements of the solicitation and not alter or rearrange the solicitation. The Offeror has the burden of proof to demonstrate compliance with all the evaluation factors identified in this solicitation. The Offeror is advised that the Government may incorporate into the final contract enhancing features included in the Offeror’s proposal deemed beneficial to the Government. With the exception of the Price volume, no cost or pricing information should appear in any volume. Alternate proposals are not acceptable.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. The Offeror is responsible to present enough information to allow the Government to evaluate the proposed work effort, support, and approach, as well as the price proposal without opening discussions. Statements that the prospective Offeror understands, or can and/or will comply with, the specifications, and paraphrasing the requirements or parts thereof without supporting information are considered inadequate by the Government, and may render a rating of unacceptable. For the purpose of this solicitation, relevance is defined as something that has a logical connection with the matter under consideration. Such aspects of relevance include the type of effort (e.g., development, production, repair), the type of requirements (e.g., weapon systems, information systems, engineering services, scheduled depot maintenance), service similarity, service complexity, contract type, contract dollar value, the division of the company that will perform the work, and degree of participation by principal subcontractors, team members, or critical team members. Recency is defined as performance within 5 years of the date of this proposal submission.

The Offeror must include any data that illustrates the adequacy of the various assumptions, approaches, and solutions to problems. Failure to address a specific factor or subfactor clearly may be considered a deficiency. There is no need to repeat information in more than one volume if an overlap exists; the detailed information must be included in the most logical place and summarized and referenced in other areas. Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

The Offeror is expected to comply with all requirements of the RFP. The Government advises the Offeror that taking exception or deviating from any term or condition of the RFP may make an offer unacceptable, and the proposal unawardable, unless the RFP expressly authorizes such an exception or deviation with regard to that specific term or condition. The Government may consider any exception or deviation to any term or condition of the RFP that is not expressly authorized by the RFP to be a deficiency.

The VH-3D Lighting Upgrade includes controlled unclassified technical information that is designated as “For Official Use Only” (FOUO). In accordance with DODI 5230.24, “Distribution Statements on Technical Documents” (23 August 2012), the Government applies “Distribution Statement D” to all the VH-3D lighting technical publications and “Distribution Statement F” to all VH-3D technical drawings to restrict third party dissemination. Unclassified documentation with distribution statement restrictions will be made available to the offeror through a secure AMRDEC Safe website. The AMRDEC Safe Access File Exchange is an application for securely exchanging files.

In order to receive VH-3D Lighting Upgrade attachment (1) statement of work, attachment (4) specification, technical publications and drawings, offerors must contact the Contract Specialist, Mark Tewell at mark.tewell@navy.mil, with the following information: Company name, mailing address, phone number, e-mail address, current CAGE number, DoD System for Award Management (SAM) number and acknowledgement of the Contractor’s responsibility under the U.S. export control laws and regulations. Please copy Constance Lawson at constance.m.lawson@navy.mil when e-mailing. Potential offerors shall acknowledge that no dissemination of any export-controlled technical data subject to this requirement will occur in a manner that would violate applicable export control laws and regulations via DD Form 2345, Militarily Critical Technical Agreements. Upon review of written request, verification of Offeror’s status and acknowledgement of the Offeror’s responsibility under the U.S. Export laws and regulations, approved offerors will receive an email with a link and unique password to download the package. After the recipient has downloaded files in the package, their password will expire. Offerors must have Lucent Image Viewer 32 and Adobe PDF capabilities to view the AMRDEC documents.

Guarantee length of proposal validity (for at least 180 days after proposal submission)

Questions: Offerors may submit questions requesting clarification of solicitation requirements by emailing the contract specialist, Mark Tewell at Mark.Tewell@navy.mil. All questions shall be submitted no later than 20 January 2015. The questions should not contain any proprietary or business sensitive information. Questions received after this date may not be entertained by the Government. The Government anticipates providing a consolidated list of questions with Government responses via Fed Biz Opps on or about 29 January 2015.

Throughout these instructions, a “principal subcontractor” is defined as a subcontractor who provides at least 20% of the proposed total price/cost (excluding the Offeror’s profit/fee), for the contract. “Team member” is defined as those entities that make up a joint venture or any other partnership or teaming arrangement formed for the purpose of responding to this solicitation. “Critical team member” is defined as those entities of the Offeror that perform a critical function in the performance of the resulting contract, whether it is technical or financial, and/or that have important roles in any high or medium risk areas identified in the Offeror’s proposal.

2.0

PROPOSAL FORMAT

Written proposals must be formatted using a Times New Roman 12 pt normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for standard 8.5 x 11 inch paper. All pages should be numbered with section and page numbers. When foldout pages are used they must not exceed 11 x 17 inches and will be counted as 1 page. Drawings may be provided separately and may be any size but should be folded to approximately 8.5 x 11 inch standard size and will count as 1 page. Graphs shall be presented in no smaller than a 10 pt font and should contain a grid, which allows values to be read directly from the graph to the same accuracy that a 10 x 10 to the ½ inch grid provides. Graphic resolution should be consistent with the purpose of the data presented.

The Offeror will provide one complete copy of the written proposal to the Procuring Contracting Officer PCO as electronic files fully compatible with Microsoft Office 2000 and for information not supported by MS Office products, with the latest Adobe Acrobat reader on a CD-ROM. The Offeror will ensure that the Price/Cost Volume is provided on a separate CD-ROM. Each CD-ROM is to be labeled for content and the Offeror’s name. If a discrepancy exists between the original paper copy of the proposal and the disk copy, the paper copy will take precedence.

3.0

PROPOSAL CONTENT AND VOLUMES

Each volume of the proposal shall be submitted as one original and additional copies as specified in the table below. All volumes of the original proposal shall be delivered to the address provided in Section 4.0 prior to the closing date/time stated in this solicitation Page limitations for each volume if any, are also specified in the table below; title and table of contents pages do not count towards page limit. Proposal pages beyond the specified maximum limit will not be reviewed as part of the evaluation.

Each volume shall contain the following information:

Cover and title page

Title of proposal and proposal number as applicable

Offeror’s name, address and POC

RFP number

Proposal volume/book number

Copy number

Table of Contents (The table of contents must provide sufficient detail to enable easy location of important elements)

Use tabs and dividers

4.0

PROPOSAL SUBMISSION:

Clearly mark all packages with the solicitation number. The submission date for the original proposal shall be no later than the date and time specified in Block 9 of Standard Form 33 of the RFP. However, Offeror shall also submit copies of Volume (3) Past Performance information in paragraphs 3.1 and 3.2 and Volume I, Executive Summary “Offeror’s Summary Table”, 1.0 (ii) two weeks prior to the submission date/time specified in Block 9 of Standard Form 33 of the RFP.

Offeror shall submit proposals via United States Postal Service or through a commercial carrier using the address provided below. Offeror shall not submit proposals by facsimile or electronically via email.

Naval Air Systems Command

Code: AIR-2.3.1.2.6, Mark Tewell

Presidential Helicopters Program (PMA-274)

48202 Bronson RD

Building 2805

Patuxent River, MD 20670

Solicitation Number: N00019-14-R-1004

Hand carried proposals may be delivered to the address above, attention (PCO) and/or (Specialist).

5.0

PROPOSAL PACKAGING:

The Offeror shall package the proposal volumes in cartons or equivalent packaging containers in the most efficient manner possible grouping like volumes to the maximum extent possible. Each container shall be single person portable. One container shall include all Original Proposal volumes including the original/signed documents submitted as part of Volume 1 Executive Summary.

Each box should include a packing slip detailing the contents to include the volume number, title, and copy number. Also, each box should be stamped or marked “For Official Use Only” and “Source Selection Information – See FAR-2.101 and 3.104”.

6.0

CLASSIFIED DATA

All proposals must be UNCLASSIFIED

7.0

SOLICITATION CHANGES

For any changes and additional information for the solicitation please go to website:

http://www.navair.navy.mil/doing_business/open_solicitations http://www.FedBizOpps.gov

PART B

SPECIFIC INSTRUCTIONS

1.0

VOLUME 1: EXECUTIVE SUMMARY

Note: This volume shall not contain any reference to cost or price aspects of the offer.

The purpose of the Executive Summary is to provide the evaluators with an overview of the Offeror’s proposal and strategy. The Offeror shall include the following in this volume:

i.

A concise abstract of the Offeror’s strategy for each of the evaluation criteria contained in the solicitation.

ii.

Offeror Summary Table: The Offeror shall complete the table below. The Offeror should include all subcontractors and team members who will be involved with the performance or management of the program work and should list all sites where the work will be performed. If a teaming or subcontracting arrangement is proposed, identify the work share, distribution elements, and ratios that each contractor will perform using the table below. Also provide a definition of the legal relationship between the entities if it is other than a Prime/subcontractor relationship.

Contractor Name

(Indicate Prime, Team Member or Sub)

iii.

Signed SF33 for basic solicitation and each amendment

iv. Signed Representations, Certifications and Acknowledgements or OnLine Representations and Certifications Application (ORCA) reference

2.0

VOLUME 2: TECHNICAL

Note: This volume shall not contain any reference to price aspects of the offer.

2.1

The Offeror shall provide all information and data required to conduct a thorough and complete technical evaluation. The Offeror shall address the following in the proposal:

2.1.1 The offeror shall provide a detailed step-by-step procedure and methodology which would be used in accomplishing each of the following statement of work (SOW) tasks in Attachment (1):

SOW Paragraphs:

3.1.3

Caution Advisory Panel

3.1.3

Upper Console Backlighting 3.1.3 Horizontal Situation Video Display Control Panel Backlighting

The offeror shall not assume that the Government evaluators possess any knowledge or familiarity with their company or approach in their proposal. The offeror shall therefore fully explain any proposed schedules, processes, or procedures which demonstrate the offeror’s understanding and proposed approach. The offeror shall submit a detailed and comprehensive response which clearly explains the offeror’s understanding of the tasking and the strategy that the offeror is proposing for this effort.

2.1.2 Provide information that describes the Offeror, the Offeror’s principal subcontractors’ and critical team members’ (as defined in Part A, Section 1.0) experience similar to that required for the instant contract. Offeror shall include their experience in any joint ventures, single legal entity arrangements as well as acting as an independent prime. Identify the period of time and the related contracts. No information on individual employee experience (or known as personnel experience) should be submitted as part of this proposal. Individual employee experience (or known as personnel experience) will not be considered in this experience evaluation. In general, recent experience will be considered more applicable than older experience. Provide an experience summary table, which lists the Offeror’s reference contracts on one axis (most recent contract to oldest) versus the areas identified in the paragraphs below. In addition, provide a copy of the Offeror’s Summary Table requested in Part B, Section 1.0 (ii), however, the column entitled “Approximate % of Total Proposed Price” shall not be included.

Specifically describe and provide examples of experience, which demonstrates your ability to perform the required effort as delineated within the specifications/performance work statements. Identify the lights listed in Attachment (2) which you have previously sold to the Government (if applicable) including part number and national stock number, the contract number and delivery dates. Briefly describe what configuration changes will be required to meet the specifications in Attachments (1) through (5). In addition, explain why the experience should be considered relevant and the degree of relevance that the experience has to the solicitation requirements. Specifically describe and compare the type of work, scope of effort, and the product/technology involved. Identify the period of time and the related contracts, as applicable. For each example, provide the contract number and title of the program, and dates under which the experience was gained. Where the Offeror lacks experience in the tasks above, describe the associated risks when considering the proposed technical approach and describe the plan to compensate for these risks.

Include examples of programs that used the same subcontracts, and examples of programs that have been managed by the same program management team and/or program manager proposed for this program. This information need only be provided for the prime Offeror. Also, describe the extent to which the Offeror and the Offeror’s Subcontractors/team members have worked with Government program teams and Government contracting teams, including NAVAIR. Other examples include integration experience, installation experience, performing supply and on-site depot support for similar a/c platforms.

Note: Ensure that experience that is identified for the proposed Prime or Subcontractor applies to the proposed roles and responsibilities of that Prime or Subcontractor; e.g. Subcontractors do not perform subcontract management and therefore their experience in subcontract management would be irrelevant, or a Subcontractor assigned to perform Non-Destructive Test/Inspection has much experience in software development, but its software development experience would not be relevant because someone else would be doing that type of work.

3.0

VOLUME 3: PAST PERFORMANCE

3.1 General

The Offeror shall identify any contracts performed within five years of this proposal submission date which contains efforts similar to those performed by Offeror, Offeror’s principal subcontractors, and critical team members in solicitation. e.g., tasks, complexity, contract type, contract dollar value, etc. Commercial contracts may be included. List the contracts from the most relevant to the least relevant. In general, recent performance will be considered more relevant than older performance. When possible, these contracts should include at least five of the most relevant contracts for the prime contractor, five of the most relevant contracts for each critical team member, and two of the most relevant contracts for each principal subcontractor (as defined in Paragraph I, General Instructions). If proposing as joint venture/single legal entity (JV/SLE), the Offeror should provide the five past performance references for the JV/SLE. If less than the five past performance references are available for the JV/SLE, each member of the JV/SLE should individually submit the five references in addition to their JV/SLE references.

For each contract identified, provide contract data, relevancy, past performance, and systemic improvement information as described below. Demonstrate the relevancy of the Offeror’s, and if applicable, the Offeror’s principal subcontractors’ or critical team members’ past performance and systemic improvements with respect to the solicitation requirements. For each past performance problem identified, describe the status of the systemic improvement efforts and, where applicable, demonstrate the impact that the systemic improvement effort had on resolving the problem such that it would not reoccur.

For contracts that have CPARS Reports that are more than six months old, e.g., the completion date is more than six months before the due date for this Past Performance Volume; the Offeror will forward a copy of the CPARS Update Questionnaire (Attachment 6) to that contract customer’s Program Manager. For all contracts identified which do not have CPARS Reports, the Offeror will forward a copy of the Past Performance Questionnaire (Attachment 7) to that contract customer’s PCO, Administrative Contracting Officer, and Program Manager. All questionnaires shall be forwarded within two weeks from the RFP release date with enough lead-time so that responses can be received by the Government concurrent with the Government’s receipt of the Offeror’s Past Performance information submitted as per paragraph 4.1 and 4.2 The Offeror shall include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to Constance M. Lawson, PCO, at Email constance.m.lawson@navy.mil, thereby allowing the customer approximately 2 weeks to complete their response. This submittal information is provided at the top of the questionnaires to facilitate the Offeror’s effort in meeting these instructions. The Offeror shall not conduct follow-up actions with regard to this questionnaire. The Government will ensure that the customers have received and will respond to the questionnaires. The Government may send any other questionnaires as necessary.

The Offeror shall provide written consent from their principal subcontractors and critical team members that will allow the Government to coordinate their Past Performance issue(s) with the Offeror. If the Offeror does not submit such written consent, then the Government will address any past performance issues directly with the principal subcontractor or critical team member and the Offeror will forfeit the opportunity to participate in any related discussions. Consequently, for any principal subcontractors and critical team members that do not provide such written consent, provide a point of contact (name, address, phone number, and email address) with which the Government may coordinate these issues and obtain any responses as needed.

The Government may use information other than that provided by the Offeror in their proposals to evaluate past performance. The Government may use Past Performance information obtained from sources other than those identified by the Offeror. The Past Performance Information Reporting System (PPIRS) will be the primary method used to evaluate Past Performance. It is incumbent upon the Offeror to explain the relevance of the data provided. The Government has no duty to search for data to cure the problems it finds in the information provided by the Offeror. The Offeror has the burden of providing thorough and complete past performance information..

(a) Contract Data

Provide all the information identified below separately for each contract. Additionally, provide this information electronically as a separate file on CD-ROM, which contains Offeror’s Past Performance proposal in a Word Table in the format depicted below:

Relevant Contract Data

Prime (P), or Sub (S)

1Place of Performance should be the same as being proposed in this solicitation. If different please include an explanation.

2CPARS (yes/no) - CPARS completion date - on DOD PPAIS (yes/no) (Indicate whether or not any CPARS have been completed and identify the last CPARS completion date and if it is currently on DoD PPAIS)

3 Recency-Efforts performed within the last five years.

4Relevancy – Provide a concise assessment of the degree of relevancy that each contract identified has to the solicitation; identifying tasks and/or aspects of the effort undertaken on the contract that are relevant to the program. Also provide the Offeror’s assessment of the relevancy of the contract in terms of one of the following ratings: Relevant (R), or Not Relevant (N) where:

Past Performance Relevancy Ratings

(b) Relevancy - The Offeror shall explain what aspects of the contract are deemed relevant to the proposed contract. At a minimum, identify key or critical tasks of the solicitation and indicate the relevancy of the “past performance” contract to these tasks. Also identify where contract performance took place and provide rationale why it is relevant to the solicitation if the location is different from where the related effort is proposed to take place.

(c) Past Performance Information - The Offeror shall provide a brief description of performance in delivering quality products in each of the following areas: 1) meeting technical requirements, i.e., the quality of technical performance, e.g., performing analysis, design, testing, etc., 2) meeting schedule requirements, i.e., schedule performance, e.g., on time or late delivery, modification of original schedules and reasons for any changes, etc., 3) controlling contract cost, i.e., cost performance, e.g., on time or late delivery, modification of original schedules and reasons for any changes, etc., and 4) managing the contracted effort, i.e., program management, e.g., cooperation with customer, subcontract management.

(d) Systemic improvement Information - Identify those systemic improvement actions taken to resolve past problems. Describe the techniques, elements, and tools used to correct problems and, if applicable, how these techniques, elements, and tools will be used during this contract.

3.2. Past Performance Data Requirements

Provide all the information identified below separately for each contract. Provide a summary of the Customer’s Points of Contact in a MS Word Table using the format below which is illustrated with an example. Include an electronic copy of this table in MS Word on a CD.

Offeror’s Name

Contract #

2. Questionnaire # __ Sent?

3. For Subs - Agreement to allow Coordination with Prime?

4. Offeror’s Role (e.g., prime or sub)

Point of Contact’s Name;

Phone Number, Fax Number and

E-mail address

1.

1. CPARS: No

2. Questionnaire # : - Sent 5/4/05

3. N/A

4. Prime Al (PM)

444-444-4444, fax 555-555-5555, Al@RYP

2.

1. CPARS: No

3. N/A

4. Prime Sue (PCO)

333-333-3333 fax 222-222-2222

Sue@RTP

3.

1. CPARS: No

3. N/A

4. Prime Joe (ACO)

111-111-1111 fax 888-888-8888

Joe@ RYP

4.

1. CPARS: Yes/No

3. N/A

4. Sub Sue (PCO)

333-333-3333 fax 222-222-2222

Sue@AB

5.

1. CPARS: Yes/Yes

2. Questionnaire # : - Not Sent

3. Agreement: Yes

4. Prime Sue (PCO)

333-333-3333 fax 222-222-2222

Sue@NNB

4.0

VOLUME 4: PRICE PROPOSAL

4.1 Volume Content:

The Offeror shall include the following in this volume:

(a) Include a copy of Section B with the Sub-CLIN Unit Prices completed. Section B prices shall be provided separately in hardcopy (1 original, 2 copies) and one digital data copy in MS Office 2007 Excel, Word or Adobe PDF format on a CD-ROM media. The Schedule B Total Price is equal to the proposed unit prices multiplied by the Section B Estimated quantity for that SLIN. There shall be no additional costs incurred that are not identified in Section B. All anticipated costs should be associated with the unit prices proposed for each SLIN in Section B (i.e. shipping). Section B prices shall be provided separately in one digital data copy in MS Office 2000 Excel format on CD-ROM media. Within all Excel spreadsheets, the Offeror shall use formulas and functions to the maximum extent possible and avoid using output type “value only” cells. If links are utilized, supply those referenced files. Spreadsheets shall not be protected.

(b) All price and price supporting information shall be contained in section B and the price proposal. No price or pricing information shall be included in any other technical volume including cover letters. Offerors are responsible for submitting sufficient information to enable the Government to fully evaluate their price proposal.

4.2 Ground Rules and Assumptions:

(a) As this is a competitive acquisition with adequate price competition anticipated, any price documentation requested shall not be certified cost or pricing data in accordance with FAR 15.406-2. However, in the event that adequate price competition does not exist after receipt of proposals, the Government reserves the right to request additional cost or pricing data as necessary from both the Offeror and subcontractors and may conduct negotiations with the Offeror, pursuant to FAR Part 15.403-4, in order to ensure a fair and reasonable price/cost. Further, the Offeror may be required to provide a Certificate of Current Cost or Pricing Data prior to award, pursuant to FAR 15.406-2. Offeror shall acknowledge the requirement to provide additional cost or pricing information and certify the data prior to award if/when requested by the Government.

4.3 Use of Government Furnished Property:

(a) If the Offeror proposes/requires the use of Government Furnished Equipment (GFE) or Government Furnished Information (GFI), then the Offeror shall provide:

A complete description of the required GFE/GFI including part number and serial number, if applicable.

Where the GFE/GFI is to be located.

The name, organization, complete address and telephone number of a cognizant Government point of contact.

In the case of GFE/GFI accountable to other Government contracts, a copy of the correspondence authorizing use of such GFE/GFI on this contract.

The monetary impact to the Offeror’s proposal if the proposed GFE/GFI is not provided as GFE/GFI.

If none, so state.

(End of Summary of Changes)