N0042118R0038-0005.docx

N0042118R0038

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

SECTION J

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

2.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. Cost information, (e.g., dollar values and/or hourly rates) shall appear only in Annex A ((Small Business Subcontracting Plan) and Table SB-1 (Small Business Requirement)), Volume 5 (Cost), and Volume 6 (Contract Administration). 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 and Corporate Experience evaluations: (a) the Prime Contractor; (b) JV Team Members; (c) other entities that are proposed to perform at least 20% of the proposed total price for the contract; or (d) entities that are proposed to perform a critical function, in the performance of the resulting contract. Critical functions include: Electronic Warfare, Radar Cross Section Measurement, Aerial Targets, Vessel Operations. Offerors are advised that in order to demonstrate work commitment, each principal entity must be identified in Volume 5 Cost and associated with a commensurate dollar value.

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 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. 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 disk, the original electronic copy shall take precedence.

2.1.1 Electronic Proposal Media

The Offeror should submit all volumes of its proposal electronically on CD-ROM(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, keeping the portions of the proposal that contain pricing information on separate CD-ROM(s) from the portions of the proposal that do not contain pricing information. For this solicitation, Annex A ((Small Business Subcontracting Plan) and Table SB-1 (Small Business Requirement)); Volume 5 Cost; Volume 6 Contract Administration; contain cost information and should be delivered on separate CD-ROM(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-ROMs. The first set of CD-ROM disks should be marked "Original” and the second set of CD-ROM disks should be marked "Backup”. The sets of CD-ROM 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 10 Operating System. Proposal information shall be submitted using the following applications: Microsoft Word 2016, Microsoft Excel 2016, Microsoft PowerPoint 2016, and Microsoft Project 2016; 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 2016 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 cost information to volumes that do contain cost 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 should 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.

Note: The Offeror should provide both a .pdf and .docx version if they are available. If not, a .pdf version only is acceptable.

Table G-2 Offeror Electronic File Naming Convention

Table ES-1 Offeror Summary Table ES-2 Relevant Contract Summary Vol 1 Att L-1 ES Tables.xlsx and Vol 1 Att L-1 ES Tables.pdf

Vol 5 Att L-6 CA.xlsx

Annexes

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.1 (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.

Cost information, (e.g., dollar values and/or hourly rates) shall not be included in any volume other than Annex A ((Small Business Subcontracting Plan and Table SB-1Small Business Requirement)); Volume 5 Cost, Volume 6 Contract Administration.

Table G-3 Proposal Structure

EXECUTIVE SUMMARY

MISSION SUPPORT

As Needed

1 Original/1 Copy

1 Original/1 Copy

As Needed

Not Applicable

1 Original/1 Copy

As Needed

1 Original

1 Original/1 Copy

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 or annex number;

f) Copy number; and

g) 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 Section L List of Attachments

L-3

Vol 3 Att L-3 CE Table.xlsx Table CE-1 Applicable Contracts for Each Corporate Experience Element

L-6

Vol 5 Att L-6 CA.xlsx

4. PROPOSAL SUBMISSION AND PACKAGING

4.1 PROPOSAL SUBMISSION

A. UNCLASSIFIED DATA

Clearly mark all packages with the solicitation number, N00421-18-R-0038. 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 one electronic copy on a CD-ROM of Table PP-1 (Past Performance Contract Data); Table CE-1 (Corporate Experience Element Contract Reference Matrix); and Annex B (Final Versions of Previous SOW/PWSs/Other Supporting Documentation for Past Performance and Corporate Experience) be submitted two weeks prior to the submission date/time specified on Standard Form 33 (Block 9).

In the official proposal submission, please indicate any changes made to the information delivered two (2) weeks early in the submission provided on the 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), Volume 3 (Corporate Experience), and Volume 4 (Past Performance). Submissions shall be delivered to:

Naval Air Warfare Center – Aircraft Division Ms. Lauren Farmer 21983 Bundy Road, Bldg 3272 Patuxent River, MD 20670 Phone: (301) 757-9788 Fax: (301) 995-0426 lauren.farmer@navy.mil

B. CLASSIFIED DATA

If classified data is necessary to be submitted due to the Offeror’s proposed approach, it should be provided in a separate addendum and should be referenced in and be traceable to the unclassified proposal. Classified material shall be packaged separately. Packaging and handling of the classified material must be in compliance with SECNAV M-5510.36 and associated DoD directives and procedures. Classified data submitted via United States Postal Service or through an overnight express carrier must be in accordance with paragraph 4.2B.

Hand delivery of classified data is only permitted with prior coordination with the PCO and requires display of a valid courier card prior to handover of information. Couriers must possess a current security clearance and background investigation required to handle the information within their possession. Contact Mr. John Tomechko, the PCO at (301) 757-7032 a minimum of three working days prior to intended delivery date to arrange for a delivery appointment.

Prior to submitting any information classified beyond the Secret Collateral level, please coordinate with Ms. Lauren Farmer, (301) 757-9788.

4.2 PROPOSAL PACKAGING:

A. UNCLASSIFIED DATA

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 NAWCAD, AIR-2.5.1.11 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, 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. Note: Any documents, which contain cost data, shall be on a separate CD-ROM disk(s) from the non-cost proposal information.

B. CLASSIFIED PACKAGING

Outer Wrap:

Naval Air Warfare Center – Aircraft Division ATTN: Ms. Lauren Farmer 21983 Bundy Road, Bldg 3272 Patuxent River, MD 20670 Phone: (301) 757-9788 Fax: (301) 995-0426 lauren.farmer@navy.mil

Inner Wrap:

Naval Air Warfare Center – Aircraft Division ATTN: Ms. Lauren Farmer Solicitation N00421-18-R-0038 21983 Bundy Road, Bldg 3272 Patuxent River, MD 20670

5. 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: N00421-18-R-0038

6. TECHNICAL LIBRARY

The Library of information directly related to the requirements of this contract is available upon request to Contracts Specialist Ms. Lauren Farmer, lauren.farmer@navy.mil. The delivery method will be coordinated with the Contracts Specialist.

PART B SPECIFIC INSTRUCTIONS

1. VOLUME 1 – EXECUTIVE SUMMARY

Note: This volume shall not contain any reference to cost 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 cost. 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. This table summarizes the Offeror and its entities’ proposed type and level of work, indicating a commitment to that effort during contract performance. Offerors are advised that in order to demonstrate work commitment, each entity identified in Table ES-1 (Offeror Summary) must be identified in Volume 5 (Cost) and associated with a dollar value commensurate with the Percent of Total Proposed Cost identified in Table ES-1 (Offeror Summary). Therefore, this table must be a reflection of what is proposed in Volume 5 (Cost).

2) For the Volume 3 (Corporate Experience) and Volume 4 (Past Performance) factor 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 Volume 3 (Corporate Experience) and Volume 4 (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 are deploying personnel or responsible for the work; not the Government site where the work is being performed. If work is being performed at a contractor site, then that would also pertain to Place of Performance.

3) If applicable, Offerors shall submit the legal document and associated agreements that established the Joint Venture and identifies the roles of each member of the JV. Note: All joint ventures that are proposed shall provide the Joint Venture legal document with agreement(s) in Annex D (Joint Venture Agreement & Teaming Agreements).

4) Additionally, Prime Offerors shall provide a copy of all teaming arrangements in accordance with Section H Clause 5252.215-9505. All teaming arrangements shall be provided in Annex D (Joint Ventures & Teaming Agreements).

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 Volume 3 (Corporate Experience) and Volume 4 (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. The contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing Attachment L-3 (Table CE-1 Applicable Contracts for Each Corporate Experience Element) and Attachment L-5 (Table PP-1 Past Performance Contract Data). For example, the contracts identified as P1, T1, or S1 in the Relevant Contract Summary Table are the same P1, T1, or S1 contracts identified in the Past Performance Contract Data Table, which are the same P1, T1, or S1 contracts identified in Table CE-1 (Applicable Contracts for Each Corporate Experience Element).

2. VOLUME 2 – MISSION SUPPORT

Note: This volume shall not contain any reference to cost 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 Offeror shall complete Table MS-1 (Mission Support CRM), provided in Attachment (L-2) and submit it as the first page of Volume 2 (Mission Support), and as a separate electronic file. The Mission Support CRM is included to help the Offeror develop its proposal and to ensure traceability of Section L paragraphs to the requirements. The Offeror’s Mission Support CRM may be identical to the one provided or revised to add information. For example, the Offeror’s Mission Support 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.

Throughout the Mission Support Volume, the Offeror should identify any proposed capability, approach or feature 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 performance, operations and/or risk. Offerors are advised that any offer to exceed a requirement or to provide a feature with performance and/or operational benefits may be included in the resulting applicable Contract within the proposed cost.

2.1 Management Approach

Describe the approach to managing the effort on this future contract in accordance with the SOW. This approach may be incorporated into the contract and become part of the Management Plan CDRL. Address the following:

2.1.1 Organization

Provide an Organizational Chart and a short description of the proposed roles of the Offeror’s management structure for the resulting contract. The description shall include the following:

a) Identify the management structure beginning with the first manager (e.g. team lead) level above ‘worker’ and continue through two levels above the General Operations Manager, Senior (GOM).

b) Identify major responsibilities for each management role relating to the management of the contract. Include a discussion for any potential conflicts of interest under this contract.

c) Identify the authority each management role shall have (e.g. hire, fire, contract signature authority, travel approval, purchase approval, etc.).

d) Identify communication lines through which major tasks will be managed.

e) Identify the city and state where each manager will be located.

f) If subcontractors or JV team members are part of your proposal, explicitly identify management roles that will be filled by subcontractors or JV team members. Discuss how the subcontracts and subcontractors will be incorporated into your management approach in the above items.

2.1.2 Recruitment

Demonstrate the ability to hire personnel needed to support the Range Technical Support Services effort.

a) Identify your approach to filling vacant positions with qualified personnel to support the Government requirement in the most responsive way.

b) Describe potential challenges in finding qualified personnel for hard to fill labor categories (e.g., Radar Cross Section Engineer, Computer Programmer/Scientist, Aerial Targets Operations Manager, and Information Security Analyst) that could occur and risk mitigation strategies that could be utilized.

c) Address your ability to hire short-term (less than one year) and/or part-time personnel to fill a temporary need due to temporary surge in requirements or absence (e.g. vacation, sick leave, family leave, military leave, and as a stop-gap for someone that retires, quits, etc.). Discuss your experiences with this scenario and the approach/tools utilized.

2.1.3 Personnel Certification/ Qualification

The Offeror shall provide a detailed plan/approach to track and ensure personnel achieve and maintain proficiency to meet the requirements in SOW Section 3.1.10 Training and Certifications and to meet the license, certifications, and special training requirements in SOW Section 3.4 Labor Category Descriptions & Qualifications. (This does not relate to addressing training new or incumbent personnel during the Phase-In Transition.) Address initial training, licensing, and certification of newly hired personnel, cross training of existing personnel to become proficient/licensed/certified on multiple range instrumentation systems and vessels, and periodic retraining to maintain proficiency.

2.1.4 Key Personnel

For the proposed Key Personnel; (i) Engineer, Radar Cross Section, Senior; (ii) General Operations Manager, Senior; and (iii) Operations Manager, Aerial Targets Site Lead, Journeyman, the Offeror shall identify them as such and NAVAIR 5252.237-9501 Addition or Substitution of Key Personnel shall apply. The Offeror shall provide letters of intent for all Key Personnel who are proposed as contingency hires. The contractor shall demonstrate relevant experience of the proposed Key Personnel in tasks similar to those outlined in the SOW by submitting resumes, contractor format acceptable. The following minimum information shall be contained within contractor submitted resumes:

· Employee name

· Years of professional experience

· Current position/title

· Educational history

· Chronology of professional experience

· Current level of security clearance

2.2 Transition Phase-In Plan

Offerors shall submit a detailed plan covering the transition phase-in period of 90 days, prior to the start of the base period of performance that describes its approach and risk mitigation strategies for minimizing disruptions of range operations due to contract transition and assumption of service requirements described in SOW Section 3.0 Requirements. The Transition Phase-In Plan shall include the following at a minimum:

a) A hiring approach with timeline for staffing the positions with the incumbent workforce and new (non-incumbent) support personnel on the contract during the transition. If there is a difference between hiring SCA and non-SCA positions, the approach shall provide two timelines - one for SCA positions and one for non-SCA positions. If only one timeline is provided, it will be viewed as the same timeline for both. The approach shall address how the Offeror will ensure the personnel hired are available, trained, and qualified to meet the labor qualifications of SOW Section 3.4 Labor Categories & Qualifications on day one of the base period of performance. Provide a plan for hiring personnel while complying with FAR Clause 52.222-17. This hiring plan should also account for new requirements, as well as, a plan for positions where incumbent personnel do not transition to the follow on contract.

b) Discuss the Offeror’s detailed approach, including a transition plan and schedule, for assuming full contractual responsibility without disruption or degradation of performance. The approach shall demonstrate the ability to provide the Other Direct Cost support services including but not limited to:

i. Aircraft Support Services

a. Address how Aircraft Support Services will be completed and certified safe for flight by the FAA, with the installation of GFE, to ensure the aircraft are operational and ready to support Range test and training events. (Note: Assume that all GFE and associated materials such as cables and antennas, equipment documentation such as specifications, operating manuals and drawings, and technical assistance are provided by the Government on day one of the transition period.)

ii. Vessel Support Services

c) An identification of risks and proposed risk mitigation strategies that will be implemented to minimize disruptions of range operations;

d) An approach working with Government Flight Representatives to ensure ground and flight operation compliance with the requirement of SOW Section 3.3.34.1a Ground Operating Procedures to enable Aerial Target operation on day one of contract period of performance.

2.3 Technology/Systems/Process Approach

Describe the Offeror’s engineering and management tools or resources, systems engineering processes, and quality improvement processes to meet existing or emergent requirements in response to future test, training, and Fleet experimentation requirements. Describe how those tools and processes would benefit and be used to assist the Government with operating, maintaining and enhancing range systems or processes in a safe, effective, and efficient manner. Describe advantages and disadvantages and any cost or schedule savings resulting from the proposed approach(s).

(a) At a minimum, address the Offeror’s approach to the following areas:

1. Describe the Offeror’s proposed approach to implement the Management Information System (MIS) requirement (Section C, paragraph 3.1.3), specifically, provide the process to plan, control costs, measure performance, and generate timely, reliable and accurate management information for this program.

2. Provide the Offeror’s approach to identify, collect, consolidate, track, and maintain configuration management of existing documentation (e.g., System Technical Manuals, Publications, Standard Operating Procedures, etc.).

3. Provide the Offeror’s approach to identify, document, track, and maintain configuration management of existing material (e.g., Test equipment, Parts Inventory, spares).

4. Provide the Offeror’s approach to collect, track, record, and assess Reliability, Availability, and Maintainability (RAM) information (e.g., MTBF, System Failure Rate).

(b) Offerors may propose up to two additional areas of technology/systems/process approaches not identified above.

Note: Offerors shall provide enough detail in the description of the technology/systems/process approach(es) so as to ensure that all parties fully understand the proposed approach(es) and any assumptions or caveats being made by the Offeror. Any additional costs to the Government related to the procurement or the implementation of the proposed approach(es) shall be included in Volume 5 Cost as described in paragraph 5.1 (General Information).

2.4 Small Business Management

a) Small Business (SB) Utilization Strategy

In Annex A, all Offerors 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. 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) The Offeror shall provide Annex A (Small Business Subcontracting Plan and Table SB-1 Small Business Requirement).

a. The Offeror shall provide how they will meet the Small Business requirement of 30% of total proposed subcontracted dollars. In addition, describe the Offeror’s approach for how the 30% of total proposed subcontracted dollars will be allocated to the Socioeconomic Small Business Concerns.

5) Describe its specific efforts and new, contract-specific initiatives to ensure the resulting contract meets or exceeds the proposed requirement. 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

6) Demonstrate that its 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.

3. VOLUME 3 – CORPORATE EXPERIENCE

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

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

Attachment L-3 Table CE-1 Applicable Contracts for Each Corporate Experience Element

For this Volume, the Offeror shall complete Table CE-1 (Applicable Contracts for Each Corporate Experience Element) below, provided in Attachment L-3, according to the instructions within the attachment, and submit it as the first section of Volume 3 (Corporate Experience) as a separate electronic file. Within Table CE-1 (Applicable Contracts For Each Corporate Experience Element) the Offeror shall identify the relevant portions (sections and paragraphs) of the contract reference’s SOW/PWS or other supporting solicitation/contract documentation to clearly identify how Corporate Experience performing past tasks are similar to evaluation elements 3.1.1 through 3.1.6. If the Offeror performed as a subcontractor for a contact reference, identify relevant portions (sections and paragraphs) of the SOW/PWS or other documentation of the agreement between the prime and subcontractor. Only contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing this Volume 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, etc.). All contracts evaluated for Corporate Experience will also be evaluated for Past Performance. However, not all past performance contract references need to be used by the Offeror to demonstrate Corporate Experience and therefore do not need to be identified in this volume.

For this Volume, the Offeror shall identify relevant contracts, or those portions of a relevant contract, whose performance is within five years of the proposal due date and contains efforts similar to those efforts (e.g., end product or service, type effort, contract tasks, contract type, contract dollar value, etc.) required by this solicitation for the principal entities identified in Table ES-1 (Offeror Summary). The experience provided shall only relate to Corporate Experience, which is the experience gained through contracted work. The experience of the principal entities personnel or any personnel will not be considered in this Corporate Experience evaluation. If proposing as a JV team, Offerors should include the Corporate Experience of the JV as a whole, as well as the Corporate Experience for each JV Team Member. In general, more recent Corporate Experience will be considered a better indicator of future performance than older Corporate Experience.

Corporate experience information provided shall be: for similar programs/contracts (as defined in section 3.1 (Evaluation Elements)); for the same corporate entity (e.g., with the same CAGE code/DUNS) as referenced in Table ES-1 (Offeror Summary); and related to the roles and responsibilities identified in Table ES-1 (Offeror Summary). For example, if a principal entity is assigned to perform Non-Destructive Test/Inspection and submits information regarding software development, the software development experience would not be relevant as it was not proposed as an assigned role/responsibility for the principal entity.

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 and Corporate Experience evaluations. Note: Any information regarding CAGE Code/DUNS should be included within Volume 1 (Executive Summary) and does not need to be repeated here.

Contract relevancy will be determined in the Past Performance evaluation. Only contract references identified in the Volume 3(Corporate Experience) and determined relevant in the past performance evaluation will be evaluated in Corporate Experience.

3.1 Evaluation Elements

The Offeror shall provide a comparative analysis between the principal entities’ roles and responsibilities identified in Table ES-1 (Offeror Summary) and the Corporate Experience requested in subparagraphs 3.1.1 through 3.1.6. In a paragraph to a page per contract reference, for each element in 3.1.1 through 3.1.6 below, describe the extent to which previous Corporate Experience performing requirements similar to this solicitation can be leveraged in future performance of work. Similarity is the extent to which the Offeror’s contract references (or documented work efforts) correspond to the specific tasks required by this solicitation. At a minimum, address the specific items within each element, however, when drafting each element description, consider the contract reference’s period of performance, the amount of time in performance, recency of the performance, frequency of the applicable activities, the technical nature of the work in comparison to the proposed effort, and the entity’s proposed role and responsibility.

3.1.1 Range Operations and Maintenance- The Offeror shall demonstrate experience providing technical support services related to operation and maintenance of Range Systems. Additionally, address Range Telemetry and Time Space Position Information (TSPI) support.

3.1.2 Deployments- The Offeror shall demonstrate experience providing technical support services related to deployments for training or test and evaluation training programs. Describe the frequency (specify if any deployments were conducted concurrently), location (CONUS, OCONUS, and maritime), and duration.

3.1.3 Electronic Warfare- The Offeror shall demonstrate experience providing technical support services related to electronic warfare in the following mission areas:

a. EW threat analysis, mission planning, and conduct data analysis and reporting for use by training or test and evaluation programs.

b. Fixed and Mobile EW signal generation and reception at Outdoor Ranges. Consideration will be given for experience in Indoor Anechoic Chamber facilities.

c. Simultaneous EW operations at multiple sites supporting diverse EW assets to include remote site and seaborne operations.

3.1.4 Radar Cross Section Measurement- The Offeror shall demonstrate experience providing technical support services related to performing RCS Measurement, mission planning, data analysis and reporting for use by test and training programs. While ATR performs Dynamic RCS measurement, consideration will be given for Static Outdoor RCS Measurement, Compact Ranges, and Indoor Anechoic Chamber facilities.

3.1.5 Aerial Targets- The Offeror shall demonstrate maintenance and operational experience providing technical support services related to Aerial Targets.

Describe the type of Aerial Targets supported, nature of support, and location.

The Offeror shall demonstrate its experience in developing GOPs/FOPs, training required personnel to ensure compliance with GOPs, and maintaining and updating those GOPs within the scope of contract activities in accordance with DCMA INST 8210.1. Offerors must also demonstrate GOPs/FOPs were approved by providing the cover sheet signed by the Government Flight Representative (GFR) for each applicable contract referenced.

3.1.6 Vessel Operations- The Offeror shall demonstrate experience operating and maintaining Vessels. Describe the type of off-shore and in-shore vessels operated, nature of support, and location. Off-shore vessels are defined as 140’ or greater.

4. VOLUME 4 - PAST PERFORMANCE

Note: This volume shall not contain any reference to the cost 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 (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 Attachment L-1 Table ES-1 (Offeror Summary). The relevant contracts provided for each principal entity shall be relative to its proposed role and responsibilities identified in Attachment L-1 Table ES-1 (Offeror Summary). Commercial contracts on similar range services 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 Attachment L-1 Table ES-2 (Relevant Contract Summary), for all contracts proposed as relevant for Past Performance and Corporate Experience.

In Annex B (Final Versions of Previous Statement of Work (SOW)/Performance Work Statement (PWS)/Other Supporting Documentation for Past Performance and Corporate Experience), the Offeror shall provide two 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 Attachment L-1 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 in Attachment L-5 (Past Performance Contract Data (PP-1)). 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-4 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.