Amendment_2_18Dec14.doc

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been added by full text:

PROPOSAL VALIDITY

Contractors shall make their proposal valid for at least 180 days from the proposal due date.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

INSTRUCTIONS, CONDITIONS, NOTE

L-1

PROPOSAL INSTRUCTIONS

PART A GENERAL INSTRUCTIONS

1.0 GENERAL

Offerors are required to submit sufficient information concerning all evaluation factors to enable Government personnel to fully ascertain 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, experience and capability as required by the solicitation. All proposals must clearly and convincingly demonstrate that the Offeror has a thorough understanding of all requirements and associated risks; is able, willing and competent to devote the resources necessary to meet all requirements and has valid and practical solutions for all requirements and potential risk areas. 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. With the exception of the Volume 5 Price, Volume 6 Contract Administration and Section L Annex E Small Business Subcontracting Plan, no prices should appear in any volume.

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 various work efforts, support, and management approaches, as well as price, to be meaningfully evaluated 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. Unnecessarily elaborate brochures or other presentation beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

Offerors are expected to comply with all requirements of the RFP. The Government advises Offerors that taking exception to or deviating from any term or condition of the RFP may make an offer unacceptable, and the Offeror ineligible for award, unless the RFP expressly authorizes such an exception or deviation with regard to that specific term or condition. The Government may consider any exception or deviation to any term or condition of the RFP that is not expressly authorized by the RFP to be a deficiency, as defined in FAR 15.001.

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 than the Offeror). Only the following entities will be used in the past performance and corporate experience evaluation: (a) the prime contractor; and (b) entities that perform at least 30% of the proposed Firm Fixed Price CLINs, also referred to as principal subcontractors and other principal entities. These entities are considered relevant entities and only relevant entities will be used in the past performance and corporate experience evaluation. However, the Offeror must demonstrate through the price proposal and/or other proposal information that these entities meet the definition of a relevant entity, or the Government may deem the entity to be not relevant and thereby not include them in the past performance and corporate experience evaluations.

2.0 PROPOSAL FORMAT AND SUBMISSION

Proposals must be formatted using a Times New Roman 12 pt normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for/printed on standard 8.5 x 11 inch paper. 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 2 pages. 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 2 pages. If the Offeror uses graphs to convey information the graphs must show enough detail to easily discern the information described. Graphs and tables shall 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 accuracy 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 shall also be no smaller than a 10 pt font and may use a font type selected by the Offeror. Each volume, book, or annex shall 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 shall 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 help ensure that the proposals received are suitable for reading electronically.

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 below. 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 E (Small Business Subcontracting Plan and Table T-1 Small Business Goals); Volume 5 Price; and Volume 6 Contract Administration contain price information and should be delivered on separate CD-ROMs from the remainder of the proposal. The Offeror should submit two sets of CD-ROMs that contain its proposal. One set of CD-ROM disks should be marked "Master," the other should be marked "Copy 1." Both 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, and proposal volumes contained therein. The Offeror is responsible for ensuring electronic proposals are virus free in accordance with Section 2.1.4. If a discrepancy exists between the original paper copy of the proposal and the original disk copy, the original disk copy shall take precedence.

2.1.2 Operating System and Applications

The proposals will be accessed utilizing the Microsoft (MS) Windows 7 Operating System. The Offeror shall submit two identical proposals in separate, electronic versions: one version in Portable Document Format (PDF) and one version in MS Office 2007 or later Applications (MS Word, Excel, PowerPoint, and Project). The PDF documents must be fully searchable. The Offeror is responsible for ensuring that the PDF and the appropriate MS Office versions contain identical information. The Government shall have the discretion to use the information in either version, and shall not be responsible for any differences in content between the two proposal formats submitted by the Offeror. Use of other application software for submission of proposals is prohibited except where specific instructions for non-PDF or Office applications are provided.

2.1.3 Hyperlinks

Offerors may use hyperlinks within and among proposal volumes that do not include price information. However, there shall be no links from any other volume into Volume 5 Price or any portion of the proposal that contains cost/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 has been checked for viruses, and specify the software, version, and virus definition used to check the data. With each subsequent submission of proposal information (e.g., responses to Evaluation Notices, Final Proposal Revisions, etc.), the Offeror shall ensure and certify that its files are virus free.

2.1.5 Multimedia

The Offeror shall not embed sound or video files into the proposal documents.

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,

b. Minimize size of graphics file,

c. Avoid scanned images.

2.1.7 Evaluation Hardware

The source selection facility will use the following type workstation computer systems and printers.

2.94 GB RAM

CD-ROM Drive

Microsoft Windows® 7 Operating System

2.1.8 File Naming Conventions

There is no limit to the number of files that may be submitted. However, it is preferable that each volume, book, or annex not be broken up into multiple electronic files. Valid extensions for files using their associated applications follow:

Files should have the following naming convention ("#" represents the sequential numbering of files and the suffix is for illustration, and may be .pdf, .docx, .xlsx, .pptx, or .mpp). For electronic file submissions (e.g. proposal volumes, annexes, appendices, enclosures) the Offeror should follow the basic structure of the file naming convention suggested in Table L-1 “Offeror Electronic File Naming Convention”. Offerors shall keep the file name as short as possible (under 40 characters) so that it is accessible on Government share drives. The Offeror shall ensure that the electronically submitted file names are directly traceable to hard copy submittals. In general, the Offeror should provide each binder (e.g. volume, book, or annex) as one separate file (i.e. do not provide each section/paragraph as separate files).

Table L-1 Offeror Electronic File Naming Convention

Table ES-1 Offeror Summary

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

Table CE-1 Evaluation Area Summary;

Table CE-2 Corporate Experience Summary; and

Table CE-3 Contract Comparative Analysis by Evaluation Area Vol 3 CE Tables.xlsx and Vol 3 CE Tables.pdf

Annexes

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

Resumes#.pdf

Annex E

3.0 PROPOSAL CONTENT AND VOLUMES

The Offeror shall present its proposal information in a manner that facilitates a one for one comparison between the information presented and these 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.

3.1 Page Count

In addition to the electronic copies requested in paragraph, 2.1, “Electronic Submission of Proposals,” each volume, book, and annex of the proposal shall be submitted as one paper original and additional paper copies as specified in Table L-2 Proposal Structure. The Offeror shall submit all paper and electronic copies of the proposal to the address provided in section 4.0. Suggested page counts for each volume, if any, are also specified in Table L-2 Proposal Structure (title and table of contents pages are not included in the suggested page count).

Table L-2 Proposal Structure

1 Copy

1 Copy

1 Copy

TECHNICAL

1 Copy

1 Copy

1 Copy

1 Copy

1 Copy

Annex

D

1 Copy

1 Copy

3.2 Contents

Each binder must contain the following information:

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/book/annex number;

f. Copy number;

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; and

h. Tabs and dividers.

3.3 Attachments

The following table L-3 lists the attachments provided to the Offeror with Section L, to assist with proposal development.

Table L-3 Section L List of Attachments

Table CE-2 Corporate Experience Summary; and

Table CE-3 Contract Comparative Analysis by Evaluation Area

3.4 Cross Reference Matrix

A Cross Reference Matrix (CRM), Table L-4, is included to help the Offeror develop its proposal and to ensure traceability of Section L paragraphs to the requirements. The Offeror’s CRM may be identical to the one provided or revised to add information. For example, the Offeror’s 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 L-4 Cross Reference Matrix

4.5 Personnel Process

3.5 Pricing

No price information, (e.g., dollar values and / or hourly rates) shall be included in any volume other than Annex E (Small Business Subcontracting Plan and Table T-1 Small Business Goals); Volume 5 Price, or Volume 6 Contract Administration.

4.0 PROPOSAL PACKAGING AND SUBMISSION

For proposal validity information, see Section A (Solicitation/Contract Form).

4.1 PROPOSAL MARKING

Clearly mark all packages with the solicitation number. The submission date for all Volumes shall be no later than the date and time specified in Block 9 of Standard Form 33 (Solicitation, Offer, and Award) of the RFP. However it is requested that Volume 1 (Executive Summary), Table ES-1 (Offeror’s Summary); Volume 1 (Executive Summary), Table ES-2 (Relevant Contract Summary); Volume 2 (Past Performance) Table PP-1 (Past Performance Contract Data); and Annex A (Final Versions of Previous SOW/PWSs for Past Performance) be submitted three weeks prior to the submission date/time specified on Standard Form 33 (Solicitation, Offer, and Award Block 9). Offerors that desire to update information submitted prior to the submission date/time specified on Standard Form 33 Standard Form 33 (Solicitation, Offer, and Award Block 9) may do so any time up to the date/time specified.

Original proposals shall be submitted via the United States Postal Service, a commercial carrier, or preferably hand delivered to the address provided below (Caution to Offerors: see FAR 52.215-1 regarding late proposals). Proposals shall not be submitted by facsimile or electronically via email.

NAVAIR

DEPARTMENT OF THE NAVY

Naval Air Systems Command

Source Selection Building

Attn: AIR-2.3.5.4.2, Ms Kerry Harding

22244 Cedar Point Rd, Building 460

Patuxent River, MD 20670

Solicitation Number: N00019-14-R-1007

Ms Kerry Harding, Contract Specialist, phone: (301) 342-4426

4.2 PROPOSAL PACKAGING

All proposals must be UNCLASSIFIED.

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/book number and title, and copy number. Each carton should be double wrapped. The outside of the carton should be plain and the inside carton shall be stamped or marked ― “For Official Use Only; and Source Selection Information – See FAR-2.101 and 3.104”, marked for the intended recipient as identified below, and should only contain those proposals intended for that person. The master set of proposals will be marked for NAVAIR PCO, AIR-2.3.5.4. The Master Set shall include all original proposal volumes (except Annex A (Final Versions of Previous SOW/PWSs for Past Performance) which is only to be submitted electronically), 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 RFP) and other applicable fill-ins. Note: Any documents which contain cost data shall be on a separate disk(s) from the other disks.

5.0 CHANGES TO SOLICITATION

All amendments to this solicitation shall be posted at https://www.fbo.gov/.

Search the database for the solicitation number N00019-14-R-1007

PART B SPECIFIC INSTRUCTIONS

1.0 VOLUME 1- EXECUTIVE SUMMARY

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

The purpose of the Executive Summary is to provide the evaluators with an overview of the Offeror’s entire proposal, excluding price. Each section within the Executive Summary shall contain the salient points contained in each of the proposal volumes. In addition, this volume should be used by the Offeror to identify and highlight significant features of its proposal. The Executive Summary volume should be divided into the areas 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.

(2) The Offeror shall provide a written explanation if multiple CAGE codes for the same physical location are provided in Table ES-1 (Offeror Summary). The written explanation shall detail the distinct roles and responsibilities for entities with different CAGE codes 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.

Note: Place of Performance for this solicitation pertains to the physical location of the prime, all subcontractors, and Joint Venture (JV) team members 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.

ES-1 Offeror Summary Table

b. Relevant Contract Summary Table

The Offeror shall complete the Table ES-2 (Relevant Contract Summary) provided also in Attachment L-1 (Executive Summary Tables), for all contracts proposed as relevant for Past Performance and/or Corporate Experience for the relevant entities. 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 2 Table PP-1 (Past Performance Contract Data), and Volume 3 Table CE-1 (Evaluation Area Summary) (i.e., the contract identified as P1 in the Relevant Contract Summary Table is the same P1 contract identified in Past Performance and the same P1 contract identified in Corporate Experience);

ES-2 Relevant Contract Summary Table

Offeror:

Referenced in:

Reference

(Corporate Experience) Volume 2 (Past Performance)

P2

P3

T2

T3

T4

S2

S3

S5

c. Signed SF33 for basic solicitation and each amendment;

d. Signed Representations, Certifications, and Acknowledgements or Online Representations and Certifications Application (ORCA) reference;

e. Past Performance

The Offeror shall provide a summary of the Prime’s, principal subcontractors’, corporate entities’ and JV team members’ past performance and systemic improvements which pertains to the tasks required by this solicitation;

f. Corporate Experience

The Offeror shall provide a summary of the Prime’s, principal subcontractors, corporate entities’, and JV team members’ relevant corporate experience, which pertains to the tasks required by this solicitation;

g. Technical - The Offeror shall describe the technical approach and identify how it addresses the requirements of this solicitation as well as the salient features of the Offeror’s management approach; and

h. Contract Administration

The Offeror shall provide a summary of any exceptions or deviations, and proposed Section H clauses addressed in Volume 6 Contract Administration.

2.0 VOLUME 2- 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 utilize to provide information for this volume:

Attachment L-2 Past Performance Questionnaire (PPQ)

Attachment L-3 Past Performance Contract Data (PP-1)

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 Prime, principal subcontractors, corporate entities, and JV team members, identified in Table ES-1 (Offeror Summary). Offerors shall also identify relevant contracts within the past five years from proposal due date that had any show-cause notices, cure notices, or termination for default. The contracts and their descriptions provided in this volume must correspond to the contracts and descriptions of the Offeror’s corporate experience provided in Volume 3 Corporate Experience.

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 paperless 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-2 Past Performance Questionnaire to that contract’s Procuring Contracting Office (PCO), Administrative Contracting Officer (ACO), and Contracting Officer’s Representative (COR)/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 shall include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to AIR-2.3.5.4.2 Ms. Kerry Harding, at kerry.harding@navy.mil. 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.

2.1 Authorization Letter(s)

Within this section, the Offeror should submit a signed “Release of Adverse Past Performance Authorization Letter(s)” with written consent from each participating principal subcontractor, corporate entity, and JV team member, authorizing the release of adverse past performance information to the prime. This authorization letter allows the Government to coordinate past performance issue(s) with the Prime Offeror. For any subcontractors or JV team members that do not provide an authorization letter with such written consent, the Offeror shall state that adverse past performance issues shall be coordinated directly with the subcontractor and past performance contact information shall be provided. The point of contact information shall include a name, address, phone number, and email address for each subcontractor, or JV team member, with whom the Government may coordinate any issues and obtain responses as needed. Offerors are advised that if Offerors do 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 subcontractor or JV team member, and the Offeror will forfeit the opportunity to participate in any related discussions.

2.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-3 Table PP-1 (Past Performance Contract Data), following the instructions provided 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 prime’s, principal subcontractors’, corporate entities’, and JV team members’ relevant contract data. All detailed information and comparative analysis of the past performance references to this solicitation’s requirements shall be provided in Volume 2, Section 2.3 (Evaluation), of the Offeror’s proposal. The 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, C1, S1, T1 etc.). In general, recent performance will be considered more relevant than older performance. Commercial contracts may be included. 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. Contracts detailed in this volume shall be the same as contracts identified in Volume 3 Corporate Experience.

Table PP-1 Past Performance Contract Data

2.3 Evaluation

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

For each contract or delivery order or task order identified in Attachment L-3 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. Use a separate table (Excel Worksheet) for each individual contract, or Delivery Order or Task Order. Each of these references should be a separate tab (worksheet) in the Excel Spreadsheet. As this information is presented in the proposal, demonstrate the relevancy of the Prime’s, principal subcontractors’ corporate entities’ and JV team members’ past performance with respect to this solicitation’s requirements. For any contracts referenced where the Prime, principal subcontractors, corporate entities, and/or JV team members are aware of problems, the Offeror shall describe the issues in section 2.3.b (Past Performance Information). For each past performance problem identified, describe the status of the systemic improvement efforts in section 2.3.c (Demonstrated Systemic Improvement).

a. Relevancy: Offerors are required to explain what aspects of the contracts are deemed relevant to this solicitation’s requirements. To demonstrate relevancy, Offerors should provide a comparative analysis to this solicitation’s requirements. In Annex A, Offerors should provide two electronic copies of the Statement of Work/Performance Work Statements (SOW/PWS) from each of the referenced contracts identified in Table ES-2. Within the comparative analysis, Offerors should identify the relevant portions (sections, paragraphs and page numbers) of the referenced contract’s SOW/PWS to clearly identify how past tasks performed are similar to this solicitation’s requirements. Annex A should only be provided in electronic format and should not be provided in hard copy. In addition, the referenced sections only need to be referenced/identified, and do not need to be broken out separately from the complete SOW/PWS. Where applicable, the Offeror may use the information in this Relevancy paragraph in responding to the instructions under Corporate Experience.

(1) Offerors are advised that contracts assessed as not relevant by the Government will not be considered in the Past Performance assessment and not considered in the Corporate Experience assessment. Contracts or the portion of those contracts submitted by the Offeror that meet any of the conditions below will be assessed as Not Relevant:

i. Contracts from an entity that does not have a defined role and responsibility identified in Table ES-1 (Offeror Summary);

ii. Contracts from not relevant entities;

iii. Contracts from an entity that does not have any work that match with the entity’s role and responsibility identified in Table ES-1 (Offeror Summary);

iv. Contracts from a different physical location (e.g., with different CAGE code) than the entity proposed in Table ES-1 (Offeror Summary);

v. Contracts that involve little to none of the scope, magnitude of effort and/or complexities required by this solicitation;

vi. Contracts, or those portions of the contract, whose performance is older than 5 years from the proposal due date. (If only a portion of a contract is older than 5 years, then only that portion is not relevant for reasons of recency); or

vii. Any work that does not include performing supply chain management (such as inventory control, material forecasting, or warehousing).

(2) Past performance of any entity with multiple CAGE codes will be considered if they are at the same physical location with distinct roles and responsibilities identified in Table ES-1 (Offeror Summary), or the current and previous CAGE codes were 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. However, all current CAGE Codes must appear in Table ES-1 which indicates a commitment of work for those entities. To facilitate the relevancy determination, the Offeror shall provide an explanation of why multiple CAGE codes are proposed; identify all applicable CAGE codes along with their defined roles and responsibilities, and a description of all such changes in the organization of the company within Volume 1.0, Executive Summary if past performance for a previous CAGE code is submitted. In addition, the Offeror shall provide a narrative within this section explaining how the changes impact the relevance of any past performance contracts provided.

(3) The comparative analysis utilized to determine relevancy should show how similar the past performance contract reference is to this solicitation with regard to scope of effort (consider SOO/SOW/PWS tasks), magnitude of effort (consider dollar amount), and complexity (consider attributes of the work being performed such as type of effort, end product, frequency such as turn-around-time or delivery rate, number of sites, skills, processes, contract type, etc.)

b. Past Performance Information: Provide a brief description of performance in delivering quality products in each of the areas identified below. 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.

(1) Technical Performance: meeting technical requirements (i.e., the quality of your technical performance, e.g., performing inventory control, material forecasting, or warehousing);

(2) 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.);

(3) Cost Performance: controlling contract cost (i.e., cost performance e.g., within the budget, actual vs. contract cost, and cost metrics);

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

(5) 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 their 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 realism of their 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 2.3.b Past Performance Information. Provide the records of such results and indicate where they are documented, preferably in Government record systems. Describe the techniques, elements, and tools used to correct problems on the contract and, if applicable, how these techniques, elements, and tools may be used for this contract. Provide quantifiable evidence or metrics that substantiate or demonstrate claims of improvement and to demonstrate that the past problem will not occur on this contract. It is incumbent upon the Offeror to explain the relevance of the data provided and substantiate that improvements from past performance problems are being made. The Government does not assume the duty to search for data to cure the problems it finds in the information provided by the Offeror. Consideration for discounting problems may be given when those problems are addressed through Demonstrated Systemic Improvement. Demonstrated Systemic Improvement may be indicated by information as it relates to preventing recurrence of past problems, including: identification of the root cause of a problem, a corrective action plan that systemically addresses the past problem, how and when the plan was implemented, documented timeframe to demonstrate when corrective action was implemented and became successful; and performance data, preferably through Government records, to show performance improvements.

3.0 VOLUME 3 - CORPORATE EXPERIENCE

Note: This volume shall not contain any reference to the cost or price 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-4 Corporate Experience Tables (CE-1, CE-2, and CE-3)

The Offeror shall provide information that describes the Prime’s, principal subcontractors’, corporate entities’, and JV team members’ relevant corporate experience similar to the requirements of this solicitation, occurring within 5 years of proposal due date. The experience provided shall only relate to corporate experience, which is the experience gained through contracted work. The experience of the Prime’s, principal subcontractors’, corporate entities’, and JV team members’ 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, recent corporate experience will be considered more relevant than older corporate experience.

Corporate experience information provided shall be: for similar programs/contracts (as defined in section 3.2); at the same place of performance (e.g., with the same CAGE code) (as referenced in Table ES-1 (Offeror Summary); and related to the roles and responsibilities identified in Table ES-1 (Offeror Summary). The roles and responsibilities provided in this volume shall correspond to the descriptions of the Prime’s, principal subcontractors’, corporate entities’, and JV team members’ work descriptions provided in Table ES-1 (Offeror Summary) and Volume 2 Past Performance. For example, if a JV team member 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 an assigned role/responsibility for the JV team member. Note that proposed corporate experience for any entity that does not have a defined role and responsibility identified in Table ES-1 (Offeror Summary) will be deemed not relevant. Any contract assessed as not relevant will not be considered in the corporate experience assessment. See Section L Part B, Volume 2 Past Performance, paragraph 2.3a, Relevancy.

Corporate experience of any entity with multiple CAGE codes will be considered if they are at the same physical location if they have distinct roles and responsibilities identified in Table ES-1 (Offeror Summary), or the current and previous CAGE codes were 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 must appear in Table ES-1 (Offeror Summary) which indicates a commitment of work for those entities. The Offeror shall provide an explanation of why multiple CAGE codes are proposed, identify all applicable CAGE codes along with their defined roles and responsibilities, and provide a description of all such changes in the organization of the company within Volume 1.0, Executive Summary if Corporate Experience for a previous CAGE code/DUNs is submitted.

The Offeror shall summarize the written proposal by completing Tables CE-1 (Evaluation Area Summary), CE-2 (Corporate Experience Summary), and CE-3 (Contract Comparative Analysis Summary), provided in Attachment L-4 (Corporate Experience Tables). Complete the tables following the instructions provided within the attachment. Submit the tables within this volume as well as electronically. The 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.).

3.1 Evaluation Area Summary Table

The Offeror shall complete Table CE-1 (Evaluation Area Summary), provided in Attachment L-4 (Corporate Experience Tables). Table CE-1 (Evaluation Area Summary) should provide a list of the Prime’s, principal subcontractors’, corporate entities’, and JV team members’ referenced contracts that provide examples of corporate experience performing tasks similar to those required for evaluation elements 3.2.1 through 3.2.3. Use only those contract references specified in Table ES-2 (Relevant Contract Summary).

Table CE-1 Evaluation Area Summary

Offeror:

P1 (Prime #1)

S1 (Principal Sub #1)

Sn (Principal Sub #n)

Tn (Team member #n)

3.2 Evaluation Areas

1) The Offeror shall provide a detailed comparative analysis, within each subparagraph 3.2.1 through 3.2.3, between the Primes’, principal subcontractors’, corporate entities’, and JV team members’ roles and responsibilities identified in Table ES-1 (Offeror Summary) and the corporate experience requested in the evaluation areas located in subparagraphs 3.2.1 through 3.2.3. A cross reference matrix, L-4, is provided to relate PWS paragraphs to sections 3.2.1, 3.2.2 and 3.2.3.

In Annex A, Offerors should provide two electronic copies of the Statement of Objectives/Statement of Work/Performance Work Statements (SOO/SOW/PWS) from each of the referenced contracts identified in Table ES-2. Within the comparative analysis, Offerors should identify the relevant portions (sections, paragraphs and page numbers) of the referenced contract’s SOO/SOW/PWS to clearly explain how the experience will be leveraged during the conduct of the future work required by this solicitation. The comparative analysis should contain a cross reference between the corporate experience evaluation areas (e.g., 3.2.1 through 3.2.3) and the specific sections and paragraph numbers of the final versions of the SOO/SOW/PWS. Annex A should only be provided in electronic format and should not be provided in hard copy. In addition, the referenced sections only need to be referenced/identified, and do not need to be broken out separately from the complete SOO/SOW/PWS.

In the comparative analysis the Offeror shall describe the breadth and depth of work performed that is similar to the PWS requirements of this solicitation. Breadth is the degree to which the Prime, principal subcontractors, corporate entities, and JV team members have performed/managed all activities/tasks similar in scope, magnitude and complexity as those under this solicitation. Specifically, describe the breadth of experience gained from each contract and the aggregate of contracts. For each element below, provide descriptions and substantiating information that demonstrates their accomplishment during the performance of the identified contract. This information shall include a description and comparison to the solicitation of the type of work, scope of effort, magnitude, complexity, physical location of effort and the product/technology involved in each of the identified past contracts. Depth is the extent to which each activity/task of the effort was performed (e.g. frequency, amount of time, etc.). Specifically describe the depth of experience gained from each contract and the aggregate of contracts. For each element below, explain the extent to which each activity/task of the effort was performed (e.g. frequency, amount of time, etc.). Include an assessment of the level of proficiency obtained by the proposed Prime contractor, principal subcontractor, corporate entity or JV Team Member in being able to successfully perform the activity/task. In the assessment, consider the frequency and/or amount of time of performance, the complexity of the task and any other applicable attributes.

3.2.1 Supply Support in a DoD environment

The Offeror shall provide examples of its experience in performing supply support in a DoD environment as outlined in PWS 3.0 including, the handling of classified equipment (PWS 2.5), and complying with personnel requirements (PWS 2.1).

3.2.2 Experience with the 4790.2 NAMP

The Offeror shall provide examples of its experience using the NAMP 4790.2 with respect to PWS 2.1, 2.3, 2.4, and 4.3.

3.2.3 Managing subcontractors on relevant contracts

This section need only be answered by the Prime Contractor. Describe experience in managing subcontractors, with similar type of work, scope of effort, and complexity to that required by the solicitation. Discuss the requirement to ensure subcontractor adherence to cost and schedule, and to maintain quality services and products from all tiers of subcontractors. Describe experience in negotiating subcontracts, to include cost control efforts under a cost reimbursable prime contract, PWS 3.2.12.

3.3 Corporate Experience Summary Table

The Offeror shall complete Table CE-2 (Corporate Experience Summary), provided in Attachment L-4 (Corporate Experience Tables). Table CE-2 (Corporate Experience Summary Table) should summarize the Prime’s, principal subcontractors’ corporate entities’, and JV team members’ relevant corporate experience, across all evaluation areas. When completing the table, please note that the gray areas represent the current solicitation efforts and should include the Prime’s, principal subcontractors’, corporate entities’ and JV team members’ proposed data that represents the future work to be conducted. The un-shaded fields are for the referenced contracts and should include data that supports corporate experience conducting tasks that are relevant to the future work.

Table CE-2 Corporate Experience Summary

3.4 Contract Comparative Analysis

The Offeror shall complete Table CE-3 (Contract Comparative Analysis by Evaluation Area) provided in Attachment L-4 (Corporate Experience Tables). The Offeror shall summarize the detailed comparative analysis provided in subparagraphs 3.2.1 through 3.2.3, utilizing a separate worksheet for each of the evaluation areas located in subparagraphs 3.2.1 through 3.2.3.