CMMARS_Amendment_0001.docx

N6134018R1199

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L INSTRUCTIONS

Section L – Instructions to Offerors

PART A GENERAL INSTRUCTIONS

1. GENERAL

Offerors are required to submit sufficient information concerning the technical evaluation factor to enable Government personnel to fully assess whether the Offeror meets 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 capability to meet the requirements of the solicitation. Proposals must demonstrate that the Offeror is able and competent 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. 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 Offeror understands, can or will comply with the requirements, has the aircraft maintenance experience, 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 proposal meets the requirements of the solicitation. There is no need to repeat information in more than one volume. The detailed information must be included in the most logical place, 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 between two or more companies that form a separate legal entity to propose as a Prime contractor for the purpose of responding to this solicitation. “JV Members” are the entities that make up a Joint Venture. For this solicitation, the term “entity” is used to mean any or all of the following: Prime contractor, JV, and JV members. The following entities are defined as “principal entities” (a) the Prime contractor (which includes the JV) and (b) JV Members and only principal entities will be used in the Technical evaluation.

2. PROPOSAL FORMAT AND SUBMISSION

Proposals should be formatted using a Times New Roman 12 point normal font, single-spaced with 1-inch margins all around, and formatted for/printed on standard 8.5 x 11 inch paper. If Government attachments have a different format/font, the Offeror may use the format/font in the attachment as provided. All pages should be numbered with volume, paragraph, and page numbers. When fold-out pages are used, they should not exceed 11 x 17 inches. Drawings may be provided separately and may be any size but should be folded to approximately 8.5 x 11 inch standard size. 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. 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 10 pt font and may use a font type selected by the Offeror.

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).

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 "Copy.”

2.1.2 Operating System and Applications

The proposals will be accessed utilizing the Microsoft Windows 10 Operating System. Proposal information should be submitted using the following applications: Microsoft Word 2016, Microsoft Excel 2016, Microsoft PowerPoint 2016, and Microsoft Project 2016 and must be accessible to the Government; however, letters and other signed documents should be provided as a fully searchable Portable Document Format (.pdf) file. Use of other application software for submission of proposals is discouraged 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.

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, or annex as one file if possible. Offerors should not provide each section/paragraph as separate files.

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

Table G-2 - CMMARS Offeror Electronic File Naming Convention

Vol 1 Tech#.pdf

Vol 1 T Tables.pdf

Table T-2 Contract Summary

Vol 1 T-3 CAME.pdf

Table T-3a DO/TO Sub-references

Vol 2 CA#.pdf

Annexes

AnnA SDfAME#.docx

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

(i.e. Small Business Subcontracting Plan and Small Business Utilization Plan) AnnB SB SP.docx and AnnB SB SP. pdf AnnB SB UP.docx and AnnB SB UP.pdf

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 paper and/or electronic copies as specified in Table G-3 (Proposal Structure). 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). Each binder must contain the following information using tabs and dividers:

a. Cover and title page;

b. Title of proposal and proposal number as applicable;

c. Offeror’s name, address and POC;

d. Solicitation number;

e. Proposal volume/annex number;

f. Copy number; and

g. Table of Contents (The table of contents must provide sufficient detail to easily locate important elements).

Table G-3 Proposal Structure

(Please provide only the portions of documents needed to demonstrate the contract reference meets the requirements identified) 1 Original/1 Copy

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

Table G-4 Section L List of Attachments

4. PROPOSAL SUBMISSION AND PACKAGING

4.1 PROPOSAL SUBMISSION

All Proposals shall be UNCLASSIFIED.

Offerors are responsible for submitting all proposal information by the proposal submission date. 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.

Method of delivery, such as by hand, United States Postal Service or commercial carrier, shall be coordinated with the Procuring Contracting Officer (PCO), Lisa Nelson, AIR-2.5.3E. Offeror shall submit all paper and/or electronic copies of the proposal to the addresses provided below. Proposals shall not be submitted by facsimile or electronically via email.

(Paper Original) Naval Air Warfare Center Training Systems Division ATTN: AIR 2.5.3E (Lisa Nelson) Solicitation: N6134018R1199 12211 Science Drive Orlando, FL 32826-3224

(Paper Copy and All Electronic Copies) Naval Air Systems Command ATTN: AIR- 4.0E (Brianna Shaw) Solicitation Number: N6134018R1199 22244 Cedar Point Road, Bldg. 460 Patuxent River, MD 20670

4.2 PROPOSAL PACKAGING

UNCLASSIFIED PACKAGING

The Offeror shall package the proposal volumes in cartons or equivalent packaging containers in the most efficient manner possible, grouping like volumes to the maximum extent possible. Clearly mark all packages with the solicitation number.

The outside and inside of the carton(s), the front cover of the proposal volumes, and the CD-ROMs should be clearly stamped or marked ― “For Official Use Only”; and “Source Selection Information – See FAR-2.101 and 3.104.”

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.

Each carton 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 should contain only pertinent shipping /mailing information including the intended recipient identified in 4.1 (Proposal Submission).

5. CHANGES TO SOLICITATION

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

PART B SPECIFIC INSTRUCTIONS

1. VOLUME 1 – TECHNICAL

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

1.1 Offeror Summary Table

The Offeror shall complete Table T-1 (Offeror Summary), provided in Attachment L-1, according to the instructions within the attachment, and submit it within this section and as a separate electronic file. This table summarizes the prime contractor (which includes the JV) with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award and the JV Members proposed for this solicitation.

Table T-1 Offeror Summary

Offeror:

Prime (includes Joint Venture)

JV Member A (where applicable)

JV Member N (where applicable)

1.2 Contract Summary Table

1.2.1 The Offeror shall complete Table T-2 (Contract Summary) provided in Attachment L-1, for all contract references proposed for 1.3 (Evaluation Elements) for the prime contractor (which includes the JV) and the JV Members identified in T-1 (Offeror Summary). The Offeror shall complete the table according to the instructions within the attachment and submit it within this section and as a separate electronic file. Please designate the contract references in a sequential order from the most relevant (e.g., P1, T1) to those that meet the requirements. A contract reference is defined as:

a. Contracts of all types except indefinite-delivery contracts (see subpart 16.5) (position 9 of Procurement Instrument Identifier instrument “C” type);

b. An order under a basic ordering agreement (BOA);

c. A delivery order (DO) or a task order (TO) under a single or multiple award Indefinite-Delivery (ID) contract; or

d. Aggregated DOs/TOs (e.g., two or more) under a single or multiple award Indefinite-Delivery (ID) contract.

When aggregating DOs/TOs:

i. The ID contract is the contract reference (e.g., P1, T1);

ii. The DOs/TOs submitted for evaluation in Table T-3a (DO/TO Sub-references) are defined as sub-referenced DOs/TOs;

iii. The Offeror shall submit sub-referenced DOs/TOs executed under the same ID contract reference in Table T-3a (DO/TO Sub-references) provided in Attachment L-2;

iv. The Offeror may aggregate sub-referenced DOs/TOs under one contract reference to meet the criteria of 1.3.1.d and 1.3.2.b; however, each DO/TO sub-referenced must separately meet all other criteria of 1.3.1, 1.3.2, and 1.3.3; and

v. The Offeror may not submit an ID type contract as a contract reference without providing sub-referenced DOs/TOs.

1.2.2 For the Technical evaluation, a contract reference will only be considered if:

a. The contractor with the CAGE code/DUNS identified on the contract reference is the same as the Offeror (prime contractor) with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award and identified in Table T-1 (Offeror Summary);

b. The contractor with the CAGE code/DUNS identified on the contract reference is a part of the Offeror (prime contractor) with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award and identified in Table T-1 (Offeror Summary) as a result of a corporate acquisition, reorganization, merger, or other administrative reason. The Offeror must demonstrate that the organizational entity who performed the work in the contract reference is currently a part of the Offeror identified in (organized in) in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award and identified in Table T-1 (Offeror Summary); or

c. The JV with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award may submit contract references performed by the individual JV Members identified in Table T-1 (Offeror Summary) if the CAGE code/DUNS identified in Table T-1 (Offeror Summary) is the same as the CAGE code/DUNS identified in the contract reference or the contractor with the CAGE code/DUNS identified on the contract reference became a part of the JV Member identified in Table T-1 (Offeror Summary) as a result of a corporate acquisition, reorganization, merger, or other administrative reason. The Offeror must demonstrate that the organizational entity who performed the work in the contract reference is currently a part of the JV Member identified in (organized in) in Table T-1 (Offeror Summary).

1.2.3 For the Technical evaluation, a contract reference will not be considered if:

a. The contractor (including JV) with the CAGE code/DUNS identified on the contract reference is different than the Offeror (including JV) with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award and identified in Table T-1 (Offeror Summary) and 1.2.2.b. does not apply; or

b. The contractor with the CAGE code/DUNS identified on the contract reference is different than the JV Member with the CAGE code/DUNS identified in Table T-1 (Offeror Summary) and 1.2.2.c. does not apply.

All current CAGE Codes/DUNS should appear in Table T-1 (Offeror Summary). The Offeror shall provide a written explanation if multiple CAGE codes/DUNS are applicable. The description shall include all changes in the organization as a result of a corporate acquisition, reorganization, merger, or other administrative reason and must demonstrate that the organizational entity who performed the work in the contract reference is currently a part of the Prime (including JV) or JV Member.

1.2.4 Additionally, if applicable, the Offeror shall provide documentation identifying the Joint Venture Members and demonstrating the JV is a legal entity.

Table T-2 Contract Summary Offeror:

Reference Number

P2

P3

P4

T2

T3

T4

1.3 Evaluation Elements

The Offeror shall complete Table T-3 (Contracts for Aircraft Maintenance Experience) for each contract reference proposed for 1.3 (Evaluation Elements) for the principal entities identified in Table T-1 (Offeror Summary). Only include a contract reference that meets all of the requirements identified in 1.3.1 (Contract Reference Requirements), 1.3.2 (Aircraft Maintenance Experience Requirements), and 1.3.3 (Management Experience Requirements).

The Offeror shall complete Table T-3 (Contracts for Aircraft Maintenance Experience), provided in Attachment L-2, according to the instructions within the attachment and submit it within this section and as a separate electronic file. Only contract references (e.g., P1, T1) designated in Table T-2 (Contract Summary) should be used in completing Table T-3 (Contracts for Aircraft Maintenance Experience). Provide a separate tab in T-3 (Contracts for Aircraft Maintenance Experience) for each contract reference. For each contract reference that is an ID type contract with DO/TO sub-references, the Offeror shall additionally complete Table T-3a (DO/TO Sub-references) provided in Attachment L-2, according to the instructions within the attachment and submit it within this section and as a separate electronic file.

For each contract reference submitted in Table T-3 (Contracts for Aircraft Maintenance Experience) and each sub-referenced DO/TO submitted in Table T-3a (DO/TO Sub-references), the Offeror shall provide copies of supporting documentation in Annex A (Supporting Documentation for Aircraft Maintenance Experience) that clearly demonstrates that the contract reference and, if applicable each sub-referenced DO/TO meets the requirements identified in Evaluation Elements 1.3.1 (Contract Reference Requirements), 1.3.2 (Aircraft Maintenance Experience Requirements), and 1.3.3 (Management Experience Requirement).

In Annex A (Supporting Documentation for Aircraft Maintenance Experience), the Offeror shall provide a complete copy of a contractually executed final version(s) of the SOW/PWS (drafts SOW/PWS are not acceptable). The Government does not need more than one version of the SOW/PWS. Additionally, the Offeror shall provide the portions of supporting contract documentation which includes plans (e.g., Monthly Maintenance Plans), documents (e.g., designation, assignment, certification, or appointment), and/or letters delivered to, signed, or accepted by the Government that clearly show that the contract reference, or in the case of an ID type contract that each sub-referenced DO/TO, meets the requirements identified in Evaluation Elements 1.3.1 - 1.3.3. Additionally, provide the work description for each delivery order, task order, or order submitted for evaluation as a contract reference in Table T-3 (Contracts for Aircraft Maintenance Experience) or sub-referenced in Table T-3a (DO/TO Sub-references). A requirement not specifically identified in the SOW/PWS or otherwise demonstrated through documents as discussed here will not be considered.

Annex A (Supporting Documentation for Aircraft Maintenance Experience) should follow the structure identified in 1.3 (Evaluation Elements). Within Annex A, the Offeror shall highlight, in yellow, the portions of the documents that clearly identify that the contract reference meets each of the requirements identified in Evaluation Elements 1.3.1 - 1.3.3; the Offeror shall denote which highlighted areas correspond to each requirement. Additionally, within Table T-3 (Contracts for Aircraft Maintenance Experience) and T-3a (DO/TO Sub-references), the Offeror shall identify the document name, page numbers, and paragraphs that show the contract reference and/or sub-referenced DO/TO meets the requirements identified in Evaluation Elements 1.3.1 – 1.3.3. There is not a suggested page count for the electronic copy of Annex A. However, for the printed copy of Annex A, please provide only the portions of the documents needed to demonstrate the contract reference meets the requirements identified in Evaluation Elements 1.3.1 – 1.3.3.

Table T-3 Contracts for Aircraft Maintenance Experience

Provide the name, page numbers, and paragraphs of the documents provided in Annex A that show the contract reference clearly meets each of the requirements identified in Evaluation Elements:

1.3.1 (Contract Reference Requirements);

1.3.2 (Aircraft Maintenance Experience Requirements);

1.3.3 (Management Experience Requirement); and

1.3.4 (Cumulative Aircraft Maintenance Experience)

1.3.1 Contract Reference Requirements

e.g., 12345 Hollywood RD Hollywood, California 20619

1.3.2 Aircraft Maintenance Experience Requirements

Phone:

Email:

Title:

1.3.1 Contract Reference Requirements

The Offeror shall demonstrate (using authoritative documentation provided in Annex A) that contract reference(s) identified in Table T-2 (Contract Summary) and submitted for evaluation in Table T-3 (Contracts for Aircraft Maintenance Experience) meet the requirements identified below. The Offeror may aggregate sub-referenced DOs/TOs under one contract reference to meet the criteria of 1.3.1.d and 1.3.2.b; however, each DO/TO sub-referenced must separately meet all other criteria of 1.3.1, 1.3.2, and 1.3.3.

a. Performed as the prime on a US Government contract;

b. Contract reference at the same physical location and the same CAGE code/DUNS as the entities identified in Table T-1 (Offeror Summary) unless the Offeror provides an acceptable explanation based on the considerations in Volume 1 (Technical), Section 1.2.2.

If the contract reference is for the prime identified in Table T-1 (Offeror Summary), the contract reference shall additionally be at the same physical location and shall have the same CAGE code identified in the award form (e.g., Block 7 on Standard Form (SF) 26 Award/Contract; Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award; Block 9 on Department of Defense (DD) 1155, Order for Supplies or Services).

c. Performance within five years of the solicitation release date; and

d. Annualized dollar value of work (same or similar to the scope of the Section J Attachment 1 CMMARS PWS) awarded shall be greater than or equal to $10M for each contract reference. (Annualized dollar value will be the total awarded value of a: single contract, DO, TO, or the sum of all sub-referenced DOs/TOs identified under one (1) ID type performed contract reference provided in Table T-3a, divided by the period of performance (please see the “Aggregation Example” provided in Table T-3a).

1.3.2 Aircraft Maintenance Experience Requirements

The Offeror shall demonstrate (using authoritative documentation provided in Annex A) that contract reference(s) identified in Table T-2 (Contract Summary) and submitted for evaluation in Table T-3 (Contracts for Aircraft Maintenance Experience) meet the requirements identified below. The Offeror may aggregate sub-referenced DOs/TOs under one contract reference to meet the criteria of 1.3.1.d and 1.3.2.b; however, each DO/TO sub-referenced must separately meet all other criteria of 1.3.1, 1.3.2, and 1.3.3.

a. Performed aviation platform maintenance in accordance with Federal Aviation Regulations (e.g., 14 CFR Parts 21, or 43, or 91, or 145); or Department of Defense Instructions (Navy (e.g., COMNAVAIRFORINST 4790.2 series, or NAVAIRINST 3710.1 series); or Air Force (e.g., AFI -21-101, AFI 21-102, AFI 10-220 IP); or Army (e.g., AR 95-1, AR 70-62, AR 385-10, AR 750-6, AR 95-20)); or DCMA INST 8210.1 series; and

b. Performed Organizational (O), and/or Intermediate (I), and/or Depot (D) maintenance (as defined in Section J Attachment 1 (CMMARS PWS)) for at least one of the following:

1. Four (4) or more types/models simultaneously;

2. Equivalent to 25,000 or more annual flight hours;

3. Three (3) or more main operating bases simultaneously;

4. At least 40 aircraft simultaneously; or

5. Depot maintenance of aircraft (e.g., E-6, P-8, V-22, H-1); where the entire aircraft platform is inducted.

1.3.3 Management Experience Requirement

The Offeror shall provide a narrative demonstrating (citing authoritative documentation provided in Annex A (Supporting Documentation for Aircraft Maintenance Experience)) that contract reference(s) identified in Table T-2 (Contract Summary) and submitted for evaluation in Table T-3 (Contracts for Aircraft Maintenance Experience) require the Offeror to perform and manage maintenance for the aircraft to be Safe for Flight/Ready for Issue and to meet scheduled availability. The contract reference must place management responsibility for meeting the maintenance requirements on the Offeror.

For example, the contract reference must require the Offeror to manage and be responsible for planning (how the Offeror meets contract requirements), controlling (implementation of standards to meet contract requirements), and organizing and staffing qualified personnel to meet contract requirements. Examples outside of this definition are contract references requiring manpower without the responsibility of managing maintenance for the aircraft to be Safe for Flight/Ready for Issue to meet schedule availability (e.g., TOs under the Air Force CFT).

Key programs and processes such as Maintenance Control, Quality Assurance, and contractor responsibility for the determination of Safe for Flight/Ready for Issue provide evidence of contactor management responsibility. Examples of artifacts that may provide evidence of management responsibility for meeting maintenance requirements include: explicit scope within the contract reference, Logs and Records, Monthly Maintenance Plan/Report, letter of designation, letter of assignment, letter of certification or letter of appointment, or equivalent documentation, where the Offeror is specified as the responsible party such as the Program Manager (as defined in COMNAVAIRFORINST 4790.2 series) for the maintenance programs.

Additionally, the Offeror shall provide a narrative demonstrating (citing authoritative documentation provided in Annex A (Supporting Documentation for Aircraft Maintenance Experience)) that each sub-referenced DO/TO submitted meets the Management Experience Requirements if an Indefinite-Delivery (ID) type contract is submitted as a contract reference.

1.3.4 Cumulative Aircraft Maintenance Experience

The Offeror shall demonstrate (using authoritative documentation regarding contract performance) that the contract reference(s) identified in Table T-2 (Contract Summary) and submitted for evaluation in Table T-3 (Contracts for Aircraft Maintenance Experience) contain a minimum of three years of cumulative aircraft maintenance experience within the five years prior to the solicitation release date. Specifically, the Offeror is required to provide contract reference(s) demonstrating a minimum of three years of cumulative aircraft maintenance experience meeting all of the requirements identified in element 1.3.1 (Contract Reference Requirements) and 1.3.2 (Aircraft Maintenance Experience Requirements) and 1.3.3 (Management Experience Requirement) within five years of the solicitation release date. The three years of cumulative aircraft maintenance experience can be demonstrated through one contract reference or the accumulation of multiple contract references.

Cumulative aircraft maintenance experience is calculated based on the number of years and months of experience each contract reference (e.g., P1, T1) provides meeting all of the requirements identified in Evaluation Elements 1.3.1 (Contract Reference Requirements) and 1.3.2 (Aircraft Maintenance Experience Requirements), and 1.3.3 (Management Experience Requirement) within five years of the solicitation release date.

When aggregating sub-referenced DOs/TOs under one contract reference, the cumulative aircraft maintenance experience of the contract reference is calculated based on the total period of performance which is defined as the length of all aggregated DO/TOs, not the separate periods of performance for each individual DO/TO used in aggregation. i.e. the start date of the first DO/TO or the start of contract relevancy period, whichever is later, through the end date of the last DO/TO or the end date of the contract relevancy period, whichever is sooner. The aggregated DO/TO periods of performance must be continuous and any period of performance gaps between individual DOs/TOs shall not exceed 30 days.

1.3.5 Small Business Utilization Plan

The Offeror (Large and Small Businesses) shall provide a Small Business Utilization Plan, at this acquisition phase, which addresses a strategy for utilizing SB Concerns during task order performance in Annex B (Small Business).

For purposes of this solicitation, the term SB Concern includes 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).

The Small Business Utilization Plan is separate from, but shall be consistent with, the SB Subcontracting Plan. Large Business 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.

The Small Business Utilization Plan should address actions you will take in preparing to propose for task orders under this MAC and shall include the following elements:

a. Approach to identifying SB Concerns;

b. Process for determining the extent of participation of SB Concerns. The Offeror may include: 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

c. Any processes improvements based on lessons learned that have been implemented to correct past inabilities to meet proposed goals.

7. VOLUME 2 – CONTRACT ADMINISTRATION

The Offeror shall provide the following contract administration information.

2.1 Offeror Representatives and Information: The Offeror shall provide a summary sheet comprised of the information listed below for the Prime (includes JV) identified in Table T-1 (Offeror Summary).

a. Prime (includes JV)

i. Business Name;

ii. Address;

iii. Primary point of contact for this solicitation (Name, title, phone number, email);

iv. Secondary point of contact for this solicitation (Name, title, phone number, email);

v. Individuals authorized to negotiate with the Government and contractually bind the Offeror (Name, title, phone number, email);

vi. DUNS; and

vii. CAGE code.

2.2 Government Agency Information: Provide the mailing address, telephone, email address and facility codes for the Offeror’s local Defense Contract Management Agency (DCMA), Defense Contract Audit Agency (DCAA), and Government Paying Office. In addition, provide the name, telephone number, and email address for the Administrative Contracting Officer (ACO) at DCMA.

2.3 Small Business (SB) Subcontracting Plan (SP) - Large Business Offerors shall provide their Small Business Subcontracting Plan conforming to the requirements of FAR 19.7 and DFARS 219.7 as part of Annex B (Small Business). The SB SP of the apparent successful Offeror(s) will be reviewed and approved by the PCO prior to contract award as part of the responsibility determination. See FAR 19.702(a)(1) Statutory requirements, regarding failure of the apparent successful Offeror to negotiate and submit a SB Subcontracting Plan or submit a Comprehensive SB Subcontracting Plan acceptable to the Contracting Officer. The successful Offeror’s approved Subcontracting Plan will be incorporated into the resultant contract and contractor performance against the plan will be monitored by the Government during contract execution. Unless the Large Business Offeror has an approved Comprehensive Subcontracting Plan, all goals identified in the proposed Subcontracting Plan shall conform to the DoD’s Subcontracting Goals for FY18 as follows: SB—33%, SDB—5%, SDVOSB—3%, HUBZone—3%, and WOSB—5%. These goals will serve as placeholders and are not negotiable at the IDIQ level at time of award.

2.4 Terms and Conditions:

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

An exception is where an Offeror states it will not comply with a solicitation requirement, usually involving contract terms and conditions.

Non-compliance with the terms, conditions, or requirements set forth in the solicitation may result in an Offeror being considered unawardable. The Government may consider an Offeror ineligible for award who proposes any exception or deviation to any term or condition of the solicitation that is not expressly authorized by the solicitation.

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

2.5 Model Contract Documents: The Offeror shall provide the model contract documents as a separate electronic file and as a separate section in this volume. In the event there is any discrepancy between these contract documents and any other volume, Volume 2 (Contract Administration) shall take precedence. The Offeror shall provide the following documents within this section:

a. Original signed SF33 (Solicitation, Offer, and Award) cover page of the solicitation and a signed SF30 cover page of each amendment (as applicable) with all applicable Blocks completed and acknowledgement of receipt of each amendment (as applicable) to this solicitation. The SF-33 Block 12 “fill-in” (proposal validity date) shall be completed to read “250” (valid 250 days from proposal due date); and

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

(End of Summary of Changes) image1.wmf