Amendment_0004.docx

N6833517R0129

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

AMENDMENT 0004

The purpose of this Amendment is for the following:

1.) Provide responses to questions.

2.) Provide notification of Technical Data Package Supplement #3 will be sent out.

3.) Incorproate an updated Attachment L-2 Volume 2 Table T-1 Cross Reference Matrix (CRM) 4.) Incorporate the following change to the solicitation:

Section L: Volume 2- Technical, Table T-1 Cross Reference Matrix. The Cross Reference Matrix has been modified to correct the SOW reference for Volume pararaghs 2.4 and 2.5. The SOW reference 3.2.6 has been moved from 2.4 to 2.5 as follows:

Section L Table T-1 Cross Reference Matrix will be changed from:

· 2.4 Program and Schedule: SOW 3.2, 3.2.6

· 2.5 Subcontractor Management and Supportability: SOW 3.2.1

To: Section L Table T-1 Cross Reference Matrix

Section L: Attachment L-2 Volume 2 Table T-1 Cross Reference Matrix (CRM) will be changed from:

· 2.4 Program and Schedule: SOW 3.2

· 2.5 Subcontractor Management and Supportability: 3.2.6

To:

Attachment L-2 Volume 2 Table T-1 Cross Reference Matrix (CRM) will be changed from:

· 2.4 Program and Schedule: SOW 3.2

· 2.5 Subcontractor Management and Supportability: 3.2.1, 3.2.6

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

PROPOSAL INSTRUCTIONS

PART A GENERAL INSTRUCTIONS

1. GENERAL

Offerors are required to submit sufficient information concerning all evaluation factors to enable Government personnel to fully assess the capabilities of the Offeror to perform all requirements. The proposal must be sufficient in detail and scope to enable evaluation and provide the evaluators a clear understanding of the Offeror’s approach, expertise, and capability as required by the solicitation. Proposals must demonstrate that the Offeror has a thorough understanding of all requirements and associated risks and is able, willing, and competent to devote the resources necessary to meet all requirements. The Offeror shall not alter or rearrange the solicitation. The burden of proof for all substantiation within the proposal rests with the Offeror. Offerors are advised that the Government may incorporate any part of the Offeror’s proposal deemed beneficial to the Government, into the final contract. Price information, (e.g., dollar values and/or hourly rates) shall appear only in Annex A (Small Business Subcontracting Plan), and Volume 4 (Price). 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. It is the responsibility of the Offeror to present enough information to allow the Government to evaluate its proposal without discussions. Unsubstantiated statements that the prospective Offeror understands, can or will comply with the specifications, or paraphrasing the requirements or parts thereof are considered inadequate and may render a rating of unacceptable.

The Offeror shall include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. There is no need to repeat information in more than one volume. The detailed information must be included in the most logical place and summarized and referenced in other areas if an overlap exists. Do not provide elaborate brochures or other presentation material beyond that sufficient to present a complete and effective proposal.

Throughout these instructions, “Offeror” is defined as the prime contractor with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award. A “Joint Venture” (JV) is a partnership or teaming arrangement that is formed for the purpose of responding to this solicitation when the prime contractor consists of more than one legal entity. “JV Team Members” are the entities that make up a Joint Venture. The term “entity” is used to mean any or all of the following: prime contractor, JV, JV team members, any subcontractor, and corporate parent, division, subsidiary, or affiliate (e.g., any contractor with a different CAGE Code/DUNS than the Offeror). The following entities are defined as “principal entities” and only principal entities will be used in the past performance evaluation: (a) the prime contractor; (b) JV Team Members; and (c) other entities that are proposed to perform at least 35% of the proposed total price for the contract within the areas of integration, test, or manufacturing.

2. PROPOSAL FORMAT AND SUBMISSION

Proposals should be formatted using a Times New Roman 12 point normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for/printed on standard 8.5 x 11 inch paper. If Government attachments have a different format/font, the Offeror may use the format/font in the attachment as provided. All pages should be numbered with volume, paragraph, and page numbers. When fold-out 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. If the Offeror uses graphs to convey information the graphs must show enough detail to easily discern the information described. Graphs and tables should be presented in no smaller than a 10 pt font. Graphs should contain a grid, which allows values to be read directly from the graph to the same detail that a 10 x 10 to the ½ inch grid provides. Graphic resolution should be consistent with the purpose of the data presented. Text utilized in charts, figures, and graphics should also be no smaller than a 10pt font and may use a font type selected by the Offeror. Each volume, book, or annex should be provided separately in a 3-ring binder. The binders should be of an appropriate thickness for the number of pages it contains (e.g., a 30-page book should not be placed in a 2-inch binder).

2.1 Electronic Submission of Proposal

This section is intended to provide information to the Offeror on the electronic format and application software to be used for submitting proposals. Use of the software and procedures described in this section will reduce the amount of time and effort needed to receive and install proposals onto the electronic evaluation system, and will ensure that the proposals received are suitable for reading electronically. If a discrepancy exists between the original paper copy of the proposal and the original electronic copy on the CD-ROM/DVD disk, the original electronic copy shall take precedence.

2.1.1 Electronic Proposal Media

The Offeror shall submit all volumes of its proposal electronically on CD-ROM/DVD(s) compatible with the operating system and applications defined in Section 2.1.2 (Operating System and Applications). The Offeror should put as much proposal material as possible on each CD-ROM/DVD, keeping the portions of the proposal that contain pricing information on separate CD-ROM/DVD(s) from the portions of the proposal that do not contain pricing information. For this solicitation, Annex A (Small Business Subcontracting Plan), and Volume 4 (Price) contain price information and should be delivered on separate CD-ROM/DVD(s) from the remainder of the proposal.

Table G-3 (Proposal Structure) identifies the proposal structure for each volume. The Offeror should submit two sets of CD-ROM/DVDs. The first set of CD-ROM disks should be marked "Original” and the second set of CD-ROM/DVD disks should be marked "Copy 1”. The sets of CD-ROM/DVD disks should be clearly marked with the Offeror's name and address, the point of contact's name and phone number, the proposal volumes contained therein, and “Source Selection Information – See FAR 2.101 and 3.104”.

2.1.2 Operating System and Applications

The proposals will be accessed utilizing the Microsoft Windows 7 Operating System. Proposal information shall be submitted using the following applications: Microsoft Word 2010, Microsoft Excel 2010, Microsoft PowerPoint 2010, and Microsoft Project 2010; however letters and other signed documents shall be provided as a fully searchable Portable Document Format (.pdf) file. Use of other application software for submission of proposals is prohibited except where specific instructions for non-.pdf or Office 2010 applications are provided.

2.1.3 Hyperlinks

Offerors may use hyperlinks within and among proposal volumes. However, there shall be no links from volumes that do not contain price information to volumes that do contain price information.

2.1.4 Virus Free Electronic Submission

Offerors are responsible for ensuring that its electronic proposal is virus free. The Offeror shall certify, in its proposal cover letter, that all electronic proposal information delivered throughout the evaluation (e.g., original proposal submission, responses to evaluation notices, Final Proposal Revisions) has been or will be checked for viruses and certify that its files are/will be virus free. The Offeror should specify the software, version, and virus definition used/that will be used to check the data.

2.1.5 Multimedia

The Offeror shall not embed sound or video (e.g., MPEG) files within the proposal submission.

2.1.6 Graphics

Large files require greater computer system resources and are discouraged. The Offeror is encouraged to:

a. Simplify the color palette used in creating figures and minimize the use of color print or graphics to the maximum extent possible;

b. Minimize size of graphics files; and

c. Avoid scanned images.

2.1.7 File Naming Conventions

Valid extensions for files using their associated applications are listed below in Table G-1 (file Extensions):

Table G-1 File Extensions

The Offeror shall follow the basic structure of the file naming convention in Table G-2 (Offeror Electronic File Naming Convention) for electronic file submissions (e.g., proposal volumes, attachments, appendices), where "#" represents the sequential numbering of files. Offeror’s shall keep the file name as short as possible (i.e., under 40 characters) so that the files are accessible on Government share drives. Files with longer names may become corrupt or inaccessible.

The Offeror should provide one folder for each volume or annex, containing all electronic files requested within the volume or annex. Please submit each volume, book, or annex as one file if possible. Offerors should not provide each section/paragraph as separate files.

The Offeror shall ensure that the electronically submitted files are directly traceable to paper copy submittals.

Table G-2 Offeror Electronic File Naming Convention

Table ES-1 Offeror Summary Table ES-2 Relevant Contract Summary Vol 1 ES Tables.xlsx

Annexes

Please note: The Offeror should provide both a .pdf and .docx version if they are available.

3. PROPOSAL CONTENT AND VOLUMES

The Offeror must present its proposal information in a manner that facilitates a one for one comparison between the information presented and Section L proposal instructions. Proposal information must be structured such that its paragraph numbers/letters correspond to the proposal instructions paragraph numbers/letters, although the Offeror may add lower tier sub paragraphs.

Each volume and annex of the proposal shall be submitted as original and additional hard and/or electronic copies as specified in Table G-3 (Proposal Structure). The Offeror shall submit all paper and/or electronic copies of the proposal to the address provided in Section 4.0 (Submission and Packaging). Suggested page counts for each volume, if any, are also specified in Table G-3 (Proposal Structure). The title and table of contents pages, as well as tables, are not included in the suggested page count.

Information submitted as an Annex to a particular proposal volume could include manuals, specifications, plans, procedures, and company policies, as well as other information requested in “Part B Specific Instructions” and do not count towards the suggested page count. Additionally, the individual subcontracting reports for the past performance volume are not included in the suggested page count.

Table G-3 Proposal Structure

Each binder must contain the following information using tabs and dividers:

a. Cover and title page;

b. Title of proposal and proposal number as applicable;

c. Offeror’s name, address, and POC;

d. Solicitation number;

e. Proposal volume/annex number;

f. Copy number; and Table of Contents (The table of contents must provide sufficient detail to easily locate important elements). At a minimum it must include the paragraphs identified in the CRM.

Table G-4 lists the attachments provided to the Offeror within Section L.

Table G-4 Section L List of Attachments

4. PROPOSAL SUBMISSION AND PACKAGING

4.1 PROPOSAL SUBMISSION

Clearly mark all packages with the solicitation number N68335-17-R-0129. The submission date for all Volumes of the proposal shall be no later than the date and time specified in Block 9 of Standard Form 33 (Solicitation, Offer and Award) of the solicitation. However, it is requested that one paper copy and two electronic copies on a CD-ROM/DVD of Table ES-1 (Offeror’s Summary), Table ES-2 (Relevant Contract Summary); Table PP-1 (Past Performance Contract Data); and Annex B (Final Versions of Previous SOW/PWSs/Other Supporting Documentation for Past Performance) be submitted two weeks prior to the submission date/time specified on Standard Form 33 (Block 9).

In the official proposal submission, indicate any changes made to the information submitted two weeks earlier than official date and time specified in Block 9 of Standard Form 33 of the solicitation. If no changes are made, please state so at the beginning of Volume 1 (Executive Summary) and Volume 3 (Past Performance).

Method of delivery, such as by hand, United States Postal Service or commercial carrier, shall be coordinated with Ms. Kathryn Scott, the Procuring Contracting Officer (PCO) (732) 323-4643 and/or contract specialist Lisette Behmke (732) 323-2547. Proposals shall be submitted using the address provided below. Proposals shall not be submitted by facsimile or electronically via email.

JOINT BASE - MDL

NAVAL AIR WARFARE CENTER AD (LKE)

SOLICITATION NUMBER: N68335-17-R-0129

CODE: 2.5.2 (MS. LISETTE BEHMKE) – 2.5.2.1.3

BLDG. 562-3 HWY 547

LAKEHURST, NJ 08733-5082

Solicitation Number: N68335-17-R-0129

Hand carried proposals may be delivered to Bldg. 562-1, Rm 134 of the address above, and attention: Ms. Lisette Behmke.

4.2 PROPOSAL PACKAGING:

The Offerors 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 box should identify its contents by including a packing slip detailing each volume/annex number and title, and copy number. Each carton should be double wrapped. The outside of the carton should be plain and shall contain only pertinent shipping /mailing information. The inside carton shall be stamped or marked ― “For Official Use Only”; and “Source Selection Information – See FAR-2.101 and 3.104”, for the intended recipient identified in 4.1 (Proposal Submission). The original set of proposals should be marked for NAVAIR PCO, AIR-2.5.2.1.3 identified in section 4.1 (Proposal Submission). The original set shall include a paper copy of the original proposal, all proposal volumes on CD-ROM/DVD, a completed and original signed Standard Form 33; acknowledgement of all solicitation amendments, if applicable; and Representations, Certifications and Other Statements of Offerors or Respondents (Section K of this solicitation) and other applicable fill-ins.

5. CLASSIFIED DATA

All proposals must be UNCLASSIFIED.

6. CHANGES TO SOLICITATION

For any changes and additional information to the solicitation please go to website: https://www.fbo.gov/

Search the database for the solicitation number N68335-17-R-0129

7. TECHNICAL LIBRARY

The Prime Offeror may request information referenced in the solicitation that cannot be obtained via public access, by contacting the persons listed below. Any information provided will be distributed to Prime Offerors via a CD-ROM/DVD disk. All guidance contained herein with regard to handling, distribution and destruction of the information shall be flowed down to all team members, partners, subcontractors, suppliers and/or vendors. Any information provided shall be the responsibility of the organization that was granted access and shall be limited to a “need to know” basis. Those who take receipt of any information shall comply with all laws, export controls, and distribution statements associated with the information contained on the CD-ROM/DVD disk. All Offerors, other than the successful Offeror, are required to destroy any and all original or copied CD-ROM/DVDs and any and all original or copied files from any and all storage media and provide proof of such destruction via signed letter on corporate letterhead to the PCO at the below listed address.

Joint Base - MDL Naval Air Warfare Center AD (LKE) Solicitation Number: N68335-17-R-0129 Code 2.5.2 (Ms. Kathryn Scott) - 2.5.2.1.3

BLDG. 562-3 HWY 547

Lakehurst, NJ 08733-5082 Email: Kathryn.Scott@navy.mil Phone: (732) 323-4643 Fax: (732) 323-2359 Joint Base - MDL Naval Air Warfare Center AD (LKE) Solicitation Number: N68335-17-R-0129 Code 2.5.2 (Ms. Lisette Behmke) - 2.5.2.1.3

BLDG. 562-3 HWY 547

Lakehurst, NJ 08733-5082 Email: lisette.behmke@navy.mil Phone: (732) 323-2547 Fax: (732) 323-2359

PART B SPECIFIC INSTRUCTIONS

0. VOLUME 1 – EXECUTIVE SUMMARY

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

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

The purpose of the Executive Summary is to provide the Government with an overview of the Offeror’s entire proposal, excluding price. The Executive Summary volume should be divided into the sections outlined below:

a. Offeror Summary Table

(1) The Offeror shall complete Table ES-1 (Offeror Summary), provided in Attachment L-1 (Executive Summary Tables), according to the instructions within the attachment, and submit it within this section and as a separate electronic file. This table summarizes the Offeror and its entities’ proposed type and level of work, indicating a commitment to that effort during contract performance.

(2) For the Past Performance evaluations, contract references that relate to a different CAGE code/DUNS than the proposed entity will be considered if the CAGE code/DUNS was created as a result of a corporate acquisition, reorganization, merger, or other administrative reason and refer to the same division in the same physical location for where the work is being performed or from where the work is being directed in accordance with the proposed roles and responsibilities. All current CAGE Codes/DUNS must appear in Table ES-1(Offeror Summary Table) which indicates a commitment of work for those entities. To facilitate the Relevancy determination for Past Performance, the Offeror shall provide a written explanation if multiple CAGE codes/DUNS for the same physical location are applicable to one entity. The written explanation shall detail the distinct roles and responsibilities for entities with different CAGE codes/DUNS at the same physical location for where the work is being performed or from where the work is being directed. The description shall include all changes in the organization as a result of a corporate acquisition, reorganization, merger, or other administrative reason and explain how the changes impact the relevance of any contract references provided.

Note: “Place of Performance” for this solicitation pertains to the physical location of the prime or other entities that will perform the work.

(3) Additionally, if applicable, the Offeror shall provide a description of the legal relationship between JV entities.

Table ES-1 Offeror Summary

Offeror:

b. Relevant Contract Summary Table The Offeror shall complete the Table ES-2 (Relevant Contract Summary) provided in Attachment L-1 (Executive Summary Tables), for all contracts proposed as relevant for Past Performance for the “principal entities”. The Offeror shall complete the table according to the instructions within the attachment and submit it within this section and as a separate electronic file. The contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing Volume 3 Table PP-1 (Past Performance Contract Data). For example, the contracts identified as P1, T1, S1, or C1 in the Relevant Contract Summary Table are the same P1, T1, S1, or C1 contracts identified in the Past Performance Contract Data Table.

Table ES-2 Relevant Contract Summary For Past Performance

Offeror:

Reference

P2

P3

T2

T3

T4

S2

S3

S5

* Contracts deleted should be identified in a narrative paragraph following Table ES-2.

c. Technical The Offeror shall provide a succinct summary of what is proposed for each element, describing the approach and/or the proposed solution. In general the description should be a short paragraph that provides only the factual description of what is proposed without adjectives or discussions of benefit. In a separate paragraph identify significant features or approaches of its proposal that reduces risk with benefit to the Government. Specifically identity where in the Technical Volume (e.g., paragraph and page number as a minimum) the details of these approaches are provided.

d. Contract Administration The Offeror shall provide the following:

1) Signed SF33 for basic solicitation and each amendment;

2) Signed Representations, Certifications and Acknowledgements or System for Award Management (SAM) reference;

3) Section F Delivery/Performance proposed dates per CLIN/unit (base year and options).

e. Exceptions and Deviations:

All exceptions and deviations that the Offeror takes from the provisions of the solicitation and its applicable documents shall be included in this section.

An exception is where an Offeror states it will not comply with a solicitation requirement, usually involving contract terms and conditions. A deviation is where an Offeror states it will not comply with a solicitation requirement but proposes an alternative to meet the intent of the requirement, usually involving a SOW requirement. An exception or deviation is considered a deficiency.

The Offeror shall provide one of the following two statements in this section. If the Offeror takes any exceptions or deviations to the provisions of the solicitation and its applicable documents, the Offeror shall provide the following statement: “All exceptions and deviations taken from the solicitation terms, conditions or requirements, including any applicable documents, are included in this section”. If the Offeror does not take any such exceptions or deviations, then the Offeror shall provide the following statement: “No exceptions or deviations are taken to the terms and conditions or any requirement of the solicitation.”

If proposing an exception or deviation, the Offeror shall provide a detailed description for each in this section. Indicate the difficulty with the applicable requirement and the proposed solution. Specifically identify the portion of the solicitation and the proposal, which are affected. Also identify any proposed H-clauses containing unique contract terms and conditions not covered by clauses in this solicitation and associated with an exception or deviation identified in this section. The Government will review the information and may elect to clarify the requirement via an amendment or clarify the requirement by holding discussions.

0. VOLUME 2 - TECHNICAL

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

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

Attachment L-2 Volume 2 Table T-1 Cross Reference Matrix (CRM)

The Offeror shall complete Table T-1 (Technical CRM), provided in Attachment (L-2) and submit it as the first page of Volume 2 (Technical), and as a separate electronic file. The Technical CRM is included to help the Offeror develop its proposal and to ensure traceability of Section L paragraphs to the requirements. The Offeror’s Technical CRM may be identical to the one provided or revised to add information. For example, the Offeror’s Technical CRM may cross-reference its proposal volumes, paragraph numbers, and pages to specific solicitation requirements identified within the table, as well as other parts of the proposal that contain relevant information.

Table T-1 Cross Reference Matrix

Att 4 - TDP

Throughout the Technical Volume the Offeror should identify any proposed capability or approach that reduces risk inherent in the program. Specifically, explain the benefits to the Government in technical terms and the degree of impact it will have to risk. The Offeror shall demonstrate the extent to which its proposed capabilities will meet the requirements. The extent and the type of substantiation may vary, but each paragraph in the Technical Volume must be substantiated. The method of demonstration is at the discretion of the Offeror, however Offerors are advised that risk may be assessed based on the level of confidence that the Offeror provides the Government with its substantiating information. The burden of proof rests with the Offeror.

2.1 Manufacturing Capability

a. Manufacturing Capability: The Offeror shall describe their overall Manufacturing Management Program to include manufacturing program planning and manufacturing operational management. The Offeror shall submit a preliminary Manufacturing and Production Plan in accordance with CDRL A002 as Annex C. This plan shall describe the Offeror’s approach to Manufacturing and Production.

b. Calibration: The Offeror shall describe its approach to establishing, implementing, documenting and maintaining a calibration program, obtaining CommSp certification and provide previous CommSP certifications within this section. The Offeror shall describe their internal process of the calibration of production test equipment.

2.2 Manufacturing Quality

The Offeror shall describe the proposed approach for assuring continuous identification, evaluation and timely resolution of manufacturing operations that adversely impact product quality, delivery, or performance. The Offeror shall describe their proposed approach to establish, implement, document and maintain a Quality Management System (QMS). The Offeror shall document and provide detailed information on its quality assurance program and the ability to implement and conform to SAE International Standard (SAE) AS9100, AS9102 and AS9103, International Organization for Standardization (ISO) 9001-2008 or (9001-2015) or American National Standards Institute (ANSI)/ASQC-Q9001. The Offeror shall describe procedures for the identification, reporting, analysis and corrective action for system integration problems and non-conforming material. The Offeror shall describe the overall approach to configuration management and control during the production process, to include drawing control (including drawing changes, the complete ECP process, change implementation and S/N effectivity).

2.3 Obsolescence Management

The Offeror shall describe its approach to proactively survey suppliers, monitor and identify any DMSMS issues with the potential to impact eCASS production affecting availability, application, operation or compatibility. In addition, the Offeror shall address parts counterfeiting prevention.

2.4 Program and Schedule

The Offeror shall provide a resource loaded Execution IMS (submitted electronically) to WBS level 3 for the base year effort as part of their proposal submittal. The IMS shall portray a time-phased schedule that logically portrays how all events in the manufacturing process will occur (in time) to assure contract requirements are met. The IMS need not cover every possible program task, but should describe a realistic and supportable schedule, illustrating the plan to meet all program requirements to achieve the base year delivery schedule, including risk management approaches being used and Schedule Visibility Tasks. The Offeror shall include proposed delivery schedule, including any incremental delivery and dates per CLIN/unit.

2.5 Subcontractor Management and Supportability:

The Offeror shall provide a Subcontract Management Plan as Annex D to its proposa1. The Subcontract Management Plan shall include the following:

(1) Description of the Offeror’s plan for subcontract management and control in the performance of this contract. The Offeror shall describe its approach to subcontract management and the complexity and variety of the work the subcontractors are to perform. The plan should identify what portions of the contract will be allocated to subcontractors.

(2) Description of the subcontractors’ roles and responsibilities. If applicable, describe the extent to which the Offeror has worked with proposed subcontractors prior to this solicitation.

(3) Description of the methods and resources that will be used to ensure subcontractor compliance with contract technical performance and schedule requirements. Identify the metrics and indicators that will be used to monitor subcontractor performance to ensure that the requirements of the SOW are met.

(4) Description of the quality control plan, risk mitigation plan, and conflict resolution plan that the Offeror will use for subcontract management.

(5) Include the details and requirements that will be used as the basis for future agreements between the Offeror and its subcontractors to include work assignments and requirements flow down. If the agreements already exist, the Offeror shall provide copies with the Subcontract Management Plan. Also, describe any long-term agreements already established with potential subcontractors.

2.6 Small Business Management

a. Small Business (SB) Utilization Strategy All Offerors (Large and Small Businesses) shall address their strategies for utilizing SB Concerns in the performance of this contract, whether as a joint venture, teaming arrangement or subcontractor. SB Offerors may meet this requirement using work they perform themselves. For purposes of this solicitation, the term SB Concern shall also include the subcategories of Veteran-Owned Small Business (VOSB), Service-Disabled Veteran-Owned Small Business (SDVOSB), HUBZone Small Business (HUBZone), Small Disadvantaged Business (SDB), and Women-Owned Small Business (WOSB). Each subcategory of SB shall be addressed. This strategy is separate from, but shall be consistent with, the SB Subcontracting Plan, if such a Plan is required. Offerors are advised that while the SB Subcontracting Plan must be submitted to be eligible for award, the acceptability of the content of that plan is part of the responsibility determination assessment and not part of the evaluation. In describing its SB Utilization Strategy for this solicitation, the Offeror shall, as applicable:

(1) Describe its approach to identifying SB Concerns;

(2) Describe the extent of participation of SB Concerns on this contract, including a detailed description of the supplies and services for each SB Concern subcategory, and the complexity and variety of the work SB Concerns are to perform. For each SB Concern specifically identified in the proposal, provide the SB Concern's CAGE Code, or, if the SB Concern is not registered in the System for Award Management (SAM), at a minimum provide evidence of self-certification in accordance FAR 19.703(b) as an SB Concern. Where possible, provide documentation regarding enforceable commitments to utilize each SB Concern.

(3) Identify what processes have been implemented to correct past inabilities to meet proposed goals and any validated improvements;

(4) Describe its specific efforts and new, contract-specific initiatives to ensure the resulting contract meets or exceeds proposed goals. These efforts shall include, but are not limited to: sponsoring program specific outreach events and industry conferences, establishing Mentor-Protégé relationships and market research using websites such as the NAVAIR Office of Small Business Programs website (http://www.navair.navy.mil/osbp ) and the Small Business Administration’s Dynamic Small Business Search tool (http://dsbs.sba.gov/dsbs/search/dsp_dsbs.cfm) to locate small business concerns; and

(5) Demonstrate (Large Businesses only) that it’s SB Utilization Strategy is consistent with its SB Subcontracting Plan. If the Offeror is a participant in the DoD Comprehensive Subcontracting Test Program specified in DFARS 219.7, or if the Offeror submits a Commercial Subcontracting Plan for this proposal, then the Offeror shall describe how SB participation on this contract will contribute to its overall Comprehensive or Commercial Subcontracting Plan goals.

b. Small Business (SB) Subcontracting Plan - Large Business Offerors shall provide their Small Business Subcontracting Plan conforming to the requirements of FAR 19.7 and DFARS 219.7 as part of Annex A (Small Business Subcontracting Plan). The SB Subcontracting Plan of the successful Offeror(s) will be reviewed and approved by the PCO prior to contract award as part of the responsibility determination. See FAR 19.702(a)(1) Statutory requirements, regarding failure of the apparent successful Offeror to negotiate and submit a SB Subcontracting Plan or submit a Comprehensive or Commercial SB Subcontracting Plan acceptable to the Contracting Officer. The successful Offeror’s approved Subcontracting Plan will be incorporated into the resultant contract and contractor performance against the plan will be monitored by the Government during contract execution.

0. VOLUME 3 - PAST PERFORMANCE

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

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

For this volume, the Offeror shall identify all relevant contracts (where for the purpose of these instructions the term contract also refers to delivery order or task order), or those portions of a relevant contract, whose performance is within five years of the proposal due date for the principal entities, identified in Table ES-1 (Offeror Summary). The relevant contracts provided for each principal entity shall be relative to its proposed role and responsibilities identified in Table ES-1 (Offeror Summary). Commercial contracts may be included. Offerors shall also identify relevant contracts within the past five years of the proposal due date that had any show-cause notices, cure notices, or termination for default. The Offeror shall complete Table ES-2 (Relevant Contract Summary For Past Performance) provided in Attachment P-1 (Executive Summary Tables), for all contracts proposed as relevant for Past Performance.

In Annex B (Relevant Portions of Final Versions of Previous Statement of Work (SOW)/Performance Work Statement (PWS)/Other Supporting Documentation for Past Performance), the Offeror shall provide electronic copies of the complete final versions of the SOW/PWS or other supporting solicitation/contract documentation from each contract or delivery/task order reference identified in Table ES-2 (Relevant Contract Summary). Annex B should only be provided in electronic format and should not be provided in paper copy. For contract references that contain delivery/task orders, additionally provide the work description for each specific delivery/task order. For contract references where the Offeror performed as a subcontractor, the Offeror shall also provide a complete electronic copy of the SOW/PWS or other documentation of the agreement between the prime and subcontractor that clearly defines the portions of the work effort of the Prime’s SOW/PWS that the Offeror performed as a subcontractor.

Contract Performance Assessment Reporting System (CPARS) and Questionnaires will be the primary customer feedback data used to evaluate the Offeror’s past performance. The Past Performance Information Reporting System (PPIRS) will be the primary method used to retrieve the CPARS for this source selection. For all contracts identified that do not have a CPARS, the Offeror shall forward a copy of Attachment L-5 Past Performance Questionnaire to that contract’s Procuring Contracting Office (PCO), Administrative Contracting Officer (ACO), and Program Manager (PM); or commercial contractor equivalents. Please forward all questionnaires within two weeks from this solicitation’s release date to allow adequate time for the recipient to respond. Note that the Offeror should not reference this solicitation’s number when distributing the past performance questionnaires to customers. The Offeror should include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to the PCO/Contract Specialist, identified in 4.1 (Proposal Submission). The Offeror shall ensure that all points of contact are current and include an email address and phone number. The Offeror shall not conduct follow-up actions with regard to this questionnaire, other than to confirm receipt by the recipient. The Government may contact customers identified by the Offeror to obtain follow-up Past Performance Information as needed.

Offerors are reminded that the Government reserves the right to use information to evaluate past performance obtained from sources other than those identified by the Offeror. The Government may send additional questionnaires and/or obtain information from sources identified by the Government evaluation team.

0. Authorization Letter(s)

The Offeror should submit a signed “Release of Adverse Past Performance Authorization Letter(s)” with written consent from each principal entity (including JV team members), authorizing the release of adverse past performance information to the Prime. The signed letter(s) should be included in a separate tab within Volume 3 (Past Performance). This authorization letter allows the Government to coordinate past performance issue(s) with the Prime Offeror. For any principal entity (including JV team members) that does not provide an authorization letter with such written consent, the Offeror shall provide point of contact information for each principal entity. This contact information shall include a name, address, phone number, and email address (including JV team members), with whom the Government may coordinate any issues and obtain responses as needed. Offerors are advised that if it does not submit the Release of Adverse Past Performance Authorization Letters with written consent, then the Government will address any past performance issues directly with the principal entity (including JV team members), and the Offeror will forfeit the opportunity to participate in any related discussions.

3.2 Relevant Contract Data

For each contract identified for past performance in Table ES-2 (Relevant Contract Summary) provided in Attachment L-1 (Executive Summary Tables), the Offeror shall complete Attachment L-6 Table PP-1 (Past Performance Contract Data), according to the instructions within the attachment and submit it within this section and as a separate electronic file. Please note that this form is a summary of the principal entities’ relevant contract data. All detailed information and comparative analysis of the past performance contract references to this solicitation’s requirements shall be provided in

Volume 3 (Past Performance) and all contract references shall be numbered the same throughout all of the Offeror’s proposal volumes (i.e., the contracts identified as P1, S1, T1, C1 etc.)

In general, recent performance will be considered a better indicator of future performance. If the Offeror is proposing as a JV, the Offeror should provide the relevant contracts for the JV as a whole, and for each team member of the JV.

Table PP-1 Past Performance Contract Data

Period of performance - End Date

Dollar value of contract (Annualized)

a. PWS/SOW paragraphs from contract reference associated with Scope: Production of Automated Test Equipment. Identify if the ATE is Military or Commercial equipment.

b. PWS/SOW paragraphs from contract reference associated with Magnitude: Annual Production Quantity. Identify the number of systems.

c. PWS/SOW paragraphs from contract reference associated with Complexity: Multiple rack system or multiple instrument single rack system or multiple instrument benchtop system. (State whether multiple rack system or multiple instrument single rack system or multiple instrument benchtop system.)

Phone:

Email:

Phone:

Email:

Phone:

Email:

Title:

Phone:

Email:

3.3 Evaluation

The burden of providing thorough and complete past performance and systemic improvement information remains with the Offeror.

For each contract identified in Attachment L-6 Table PP-1 (Past Performance Contract Data), the Offeror shall provide contract data regarding relevancy, past performance information, and demonstrated systemic improvement, as described below, organized by contract reference. As this information is presented in the proposal, demonstrate the relevancy of the principal entities past performance with respect to this solicitation’s requirements. For any contract references where the principal entities are aware of problems, the Offeror shall describe the issues in section 3.3.b (Past Performance Information). For each past performance problem identified, describe the status of the systemic improvement efforts in section 3.3.c (Demonstrated Systemic Improvement).

a. Relevancy: Offerors are required to explain what aspects of the referenced contracts are deemed relevant, as defined by Section M, to this solicitation’s requirements. To demonstrate relevancy, Offerors shall provide a comparative analysis to the scope, magnitude, and complexity or similarity of this solicitation’s requirements. Within the comparative analysis, Offerors should identify the relevant portions (sections, paragraphs, and page numbers) of the referenced contract’s SOW/PWS (Annex B) to clearly identify how past efforts performed are similar to this solicitation’s requirements. In addition, the referenced sections only need to be identified and the full text does not need to be broken out separately from the complete SOW/PWS.

The offeror is advised that the Government will assess each contract and assign a relevancy rating of Very Relevant, Relevant, Somewhat Relevant, or Not Relevant as defined in Section M, Part III, Definitions.

The reference contract(s) provided should be relative to each principal entity’s proposed role/responsibility identified in Table ES-1 (Offeror Summary) versus relative to the whole solicitation.

For a discussion on CAGE Code/DUNS, refer to section 1.0 Volume 1 (Executive Summary). Offerors should be advised that the CAGE Code/DUNS for each referenced contract is considered as part of the Relevancy determination, which determines if the contract reference will be included in the Past Performance evaluations. Note: Any information regarding CAGE Code/DUNS should be included within Volume 1 (Executive Summary) and does not need to be repeated here.

Offerors are advised that contracts assessed as not relevant by the Government will not be considered in the Past Performance assessments.

b. Past Performance Information: For the relevant contracts provide a brief description of past performance in delivering quality products and services. Include in these descriptions any information that demonstrates the level of performance obtained, where available; provide quantifiable measures/trends to demonstrate past and current performance. Also describe past problems, including when they occurred, what the circumstances were surrounding the situation, and what the consequences were as a result of the problem.

i. Technical Performance: meeting technical requirements (i.e., the quality of your technical performance, e.g., performing analysis, design, testing, etc.);

ii. Schedule Performance: meeting schedule requirements (i.e., schedule performance, e.g., on time or late delivery, modification of original schedules and reasons for any changes, etc.);

iii. Management Performance: managing the contracted effort (i.e., program management, e.g., cooperation with customer, subcontract management); and

iv. Small Business Utilization: The Large Business Offeror shall provide copies of the final or most recent SF 294s/Individual Subcontracting Reports (ISRs) for the three most relevant Government contracts provided in the Past Performance section of its proposal. The Small Business Offeror may provide this information in a format substantially the same as the ISR. If the Offeror is a participant in the DoD Comprehensive Subcontracting Test Program, the Offeror shall provide copies of DCMA's most recent “Review of Contractor's Comprehensive Subcontracting Program” (DCMA Form 640), and three final or most recent SF 295s/Summary Subcontracting Reports (SSRs), and explain how the results shown in these documents demonstrate the feasibility of the offeror’s proposed SB Utilization Strategy. If applicable, note whether the contract met or exceeded Small Business (SB), Veteran-Owned Small Business (VOSB), Service-Disabled Veteran-Owned Small Business (SDVOSB), HUBZone Small Business (HUBZone), Small Disadvantaged Business (SDB), and Women-Owned Small Business (WOSB) small business utilization and subcontracting goals. All Offerors providing this information must explain how this information translates to reasonableness of their proposed SB Utilization Strategy goals provided in the technical Volume.

c. Demonstrated Systemic Improvement: Identify systemic improvement actions taken to resolve any past problems identified in 3.3.b (Past Performance Information).