T-45_L1 M1_20130128.docx

L - 1 CONTENT OF PROPOSALS (SUPPLIES OR SERVICES)(JUN 2011) (OCT 2012)

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 capabilities of the Offeror to perform the requirements. The proposal must be sufficient in detail and scope to permit evaluation and provide the evaluators a clear understanding of the Offeror’s 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 the requirements, associated risks and is able, willing and competent to devote the resources necessary to meet the requirements and has valid and practical solutions for all requirements and potential risk areas. Respond to all requirements of the solicitation. Do not alter or rearrange the solicitation. The burden of proof for all substantiation within the proposal rests with the Offeror. The Offerors are advised that the Government may incorporate into the final contract any part of the Offeror’s proposal deemed beneficial to the Government. With the exception of Annex B Small Business Subcontracting Plan and Table T-1 (Small Business Goals); Volume 3 Price; and Volume 6 Contract Administration, no price should appear in any other volume. Alternate proposals are not acceptable.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. 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 made by the Offeror that it understands, can or will comply with the specifications, or paraphrases the requirements or parts thereof are considered inadequate and may render a rating of unacceptable.

The Offeror must include any data necessary to illustrate the adequacy of the various techniques, 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. The Offeror shall explain assumptions used to develop the proposal.

Offerors are expected to comply with all requirements of the solicitation. The Government advises Offerors that taking exception or deviating from any term or condition of the solicitation may make an offer unacceptable, and the Offeror ineligible for award. The Government may consider any exception or deviation to any term or condition of the solicitation that is not expressly authorized by the solicitation to be a deficiency, as defined in FAR 15.001. Additionally, any approach that relies on Government resources or operations (e.g. Government Property, Government personnel/actions, Government Concept of Operation changes, etc) in order to comply with a requirement, unless otherwise allowed, may be considered non-compliant.

Throughout these instructions, Offeror is defined as the prime. “Principal Subcontractors” are defined as a subcontractor who provides at least 10% of the proposed total price (excluding the Offeror’s profit/fee), for the contract. “Joint Venture (JV) Team Members” are the entities that make up a Joint Venture or any other partnership or teaming arrangement that is formed for the purpose of responding to this solicitation. “Critical Subcontractors” are entities of the Offeror that perform a critical function in the performance of the resulting contract, whether it is technical or financial, and/or have important roles in any high or medium risk areas identified in the Offeror’s proposal. Critical functions include but are not limited to: Integration and Test Support, Aircraft Depot Level Maintenance, and Supply Chain Management. The Government reserves the right to determine if a subcontractor proposed performs a critical function.

2.0 PROPOSAL FORMAT

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 section and page numbers. When foldout pages are used they must not exceed 11 x 17 inches and will be counted as 1 page. Drawings may be provided separately and may be any size but should be folded to approximately 8.5 x 11 inch standard size and will count as 1 page. If the Offeror uses graphs to convey information the graphs must show enough accuracy to easily discern the information shown. 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 10pt font and may use a font type selected by the Offeror. Each volume or book shall be provided separately in a 3-ring binder. The binders shall 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

In addition to the paper copies (discussed in Section 3), 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 B Small Business Subcontracting Plan and Table T-1 (Small Business Goals); Volume 3 Price; and Volume 6 Contract Administration contain price information and should be delivered on separate CD-ROM(s) from the remainder of the proposal. The Offeror should submit five copies of its proposal on CD-ROM. One set of CD-ROM disks should be marked "Master." The four backup sets should be individually packaged and marked as “set 1, 2, 3, or 4”. All 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 disk copy, the paper copy shall take precedence.

2.1.2 Operating System and Applications

The proposals will be accessed via Navy Marine Corps Intranet server network on workstations utilizing the Microsoft XP Professional Operating System. The Offeror shall submit two identical proposals in separate, paperless versions: one version in Adobe Acrobat Reader 8.0 (.pdf) and one version in Microsoft Office 2007 Applications (Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and Microsoft Project). The .pdf document must be fully searchable. The Microsoft Office 2007 applications version may vary slightly from the page suggestions, discussed in Section 3.0, as a result of print drivers or formatting. However, the Offeror is responsible for ensuring that the .pdf and Microsoft Office 2007 applications 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 2007 applications are provided. However, other applications (e.g., non-Microsoft drawing programs) can be used in proposal preparation as long as the electronic product can still be viewed by the Microsoft application as an object embedded within the document (i.e., Word, Excel, PowerPoint, or Project). The source selection network uses Microsoft Internet Explorer 7.0.

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 the Volume 5 Price.

2.1.4 Virus Free Electronic Submission

Offerors are responsible for ensuring that it’s electronic proposal is virus free. The Offeror should certify, in it’s proposal cover letter, that all electronic proposal information has been checked for viruses, and specify the software, version, and virus definition that were used to check the data. The Offeror should also ensure and certify that any subsequent proposal information (e.g., evaluation notices, Final Proposal Revisions, etc.) is also virus free.

2.1.5 Multimedia

The Offeror should not embed sound or video (e.g., MPEG) 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 files; and

c. Avoid scanned images.

2.1.7 Evaluation Hardware

The source selection facility uses the following type of workstation computer systems and printers.

2.94 GB RAM

19” Monitors

CD-ROM Drive

Windows XP Professional Operating System

2.1.8 File Naming Conventions

There is no limit to the number of files that may be submitted.

Valid extensions for all files using their associated applications are:

Note: the 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 2.1 (Offeror Electronic File Naming Convention). The Government suggests that the Offeror keep the file name as short as possible (under 40 characters is suggested) so that it is accessible on Government share drives. Please note that the Offeror should ensure that the electronically submitted filenames are directly traceable to hard copy submittals.

Table 2.1 Offeror Electronic File Naming Convention

CE Tables:

Table CE-1 (Evaluation Area Summary);

Table CE-2 (Corporate Experience Summary); and Table CE-3 (Contract Comparative Analysis by Evaluation Area).

Vol 5 CETables.xlsx and CETables.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.

3.0 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 this Proposal Instruction. Proposal information must be structured such that its paragraph number/letter is identical to the Proposal Instructions paragraph number to which it is responding, although the Offeror may add lower tier sub paragraphs. The Offeror must provide reasons it will not provide information for a particular paragraph. The proposal information instructions are structured by paragraph numbers where first, second, third and fourth parts correspond to the volume, book, section, and element, etc., in the Offeror’s proposal.

Each volume of the proposal shall be submitted as one original and additional copies as specified in the table below. Submission of all volumes of the Original proposal to the address provided in section 4.0. will determine timeliness of receipt. Suggested page counts for each volume, if any, are also specified in the table below as follows (title and table of contents pages do not count towards page suggestions):

Information submitted as an Annex to the proposal includes manuals, specifications, plans, procedures, and policies that exist as an official document of the company or facility, as well as other information requested in Section B Specific Instructions. Annexes do not have suggested page counts and do not count towards the suggested page count for any of the volumes. The authorized Annexes are summarized in the table below.

Table 3.1 Proposal Structure

Table CE-1 (Evaluation Area Summary);

Table CE-2 (Corporate Experience Summary); and Table CE-3 (Contract Comparative Analysis by Evaluation Area).

Annex A

Annex B

Small Business Subcontracting Plan and Table T-1 (Small Business Goals)

Annex C

Annex D

*Note 1: Not included in the suggested page count

Each volume must contain the following information:

a. Title of proposal and proposal number as applicable

b. Offeror’s name, address and POC

c. Solicitation number

d. Proposal volume/book number

e. Copy number

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

g. Use tabs and dividers

Catalog Card - Each volume must contain an 8 1/2" x 11" Catalog Card containing the information required for the cover and title page. The back of the card must be formatted with three columns entitled "Name", "Date Out", and "Date In". This card must be removable from the back of each book.

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

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

Section L List of Attachments

Table CE-2 Corporate Experience Summary; and Table CE-3 Contract Comparative Analysis by Evaluation Area

A Cross Reference Matrix (CRM), Table 3.2, is provided to help the Offeror ensure that all requirements are addressed, are easily accessible to the evaluators, and to aid in ensuring accurate format and mapping of its proposal. An electronic version of Table 3.2 (Cross Reference Matrix) is provided as Attachment L-1. The Offeror shall fill in the volume, paragraph, and page location column of the CRM with references from the Offeror’s proposal and place a copy of the CRM at the beginning of the technical and corporate experience volumes. Please note that additional CRMs may be developed as needed for other volumes by the Offeror. The Offeror’s CRM shall 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. The CRM provided in Volume 2 Technical and Volume 4 Corporate Experience as well as the individual subcontracting reports for the past performance volume are not included in the suggested page count. The Offeror’s technical CRM may be identical to the one provided below or revised to add columns (such as section, paragraph, and page numbers of where other relevant information in the proposal is located, revise requirement references, or provide other comments).

Table 3.2 Cross Reference Matrix (CRM)

No price information, (e.g., DOLLAR VALUES AND / OR HOURLY RATES) shall be included in any volume other than Annex B Small Business Subcontracting Plan and Table T-1 (Small Business Goals); Volume 3 Price; or Volume 6 Contract Administration.

4.0 PROPOSAL SUBMISSION:

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 of the solicitation. However it is requested that one hard copy and one electronic copy on a CD-ROM of Volume 4 Past Performance, Table PP-1 (Past Performance Contract Data), as well as Volume 1 Executive Summary, Table ES-1 (Offeror’s Summary), and Volume 1 Executive Summary, Table ES-2 (Relevant Contract Summary) be submitted three weeks prior to the submission date/time specified on Standard Form 33 (Block 9). Please indicate all changes made to these sections in the submission provided on the proposal due date. If no changes are made, please state so at the beginning of Volume 4 Past Performance.

4.1 Unclassified Data

Method of delivery, such as by hand, United States Postal Service or commercial carrier, shall be coordinated with Jessica McGee, (301) 757-1953, jessica.mcgee@navy.mil. Proposals shall be submitted using the address provided below. Initial and Final Proposals shall not be submitted by facsimile or electronically via email.

Department of the Navy Naval Air Systems Command (HQ) Trainer Aircraft Branch Attn: Dee Peters, PCO, Code Air-2.2.4.1B 47123 Buse Road, BLDG 2272 Room 453 Patuxent River, MD 20670-1127 Solicitation Number: N00019-12-R-0001

5.0 PROPOSAL PACKAGING:

The Offerors shall package the proposal volumes in cartons or equivalent packaging containers in the most efficient manner possible, grouping like volumes to the maximum extent possible. Each box should identify its contents by including a packing slip detailing each volume/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 3.104 and 2.101,” marked for the intended recipient as identified below, and should only contain those proposals intended for that person. The master set of proposals and set No. 1 copy will be marked for NAVAIR Procuring Contracting Officer (PCO), AIR-2.2.4.1B. The Offeror shall provide a hard copy and a CD-ROM with a Master Set which shall include all original proposal volumes; a completed and original signed Standard Form 33; all signed solicitation amendments, if applicable; and other applicable fill-ins. Note: Any documents which contain price data shall be on a separate disk(s) from the other disks.

6.0 CLASSIFIED DATA

All proposals must be UNCLASSIFIED

7.0 CHANGES TO SOLICITATION

For any changes and additional information prior to proposal due date for this solicitation, please go to the following website:

https://www.fbo.gov/

Search the database for the solicitation number N00019-12-R-0001.

8.0 TECHNICAL LIBRARY

The T-45 CLS N00019-12-R-0001 Competition Library is hosted on a Department of Defense (DoD) Information System. Access to the library requires a DoD Common Access Card (CAC) or External Certification Authority (ECA) certificate. An ECA certificate can be obtained from IdenTrust, Inc., Operational Research Consultants, Inc. (ORC) or VeriSign, Inc. Additional information on obtaining an ECA certificate is available at http://iase.disa.mil/pki/eca/index.html

The link to the library is: https://pma273.navair.navy.mil/

Each individual requesting access will be required to have a DoD Common Access Card (CAC) or External Certification Authority (ECA) certificate. Once the request information is received, recorded, and validated by the Government, notification of access will be provided via e-mail.

PART B SPECIFIC INSTRUCTIONS

1.0 VOLUME 1 – EXECUTIVE SUMMARY

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

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

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, it must be used by the Offeror to identify and highlight significant features of the proposal. The Executive Summary volume should be divided into sections defined below:

a. The Offeror shall complete Table ES-1 (Offeror Summary), using the following instructions for each of the respective columns. An electronic version of Table ES-1 (Offeror Summary) is provided as Attachment L-2 and is to be submitted within this section.

(1) List itself as well as all subcontractors (principal subcontractors, critical subcontractors, and all other subcontractors) as well as JV team members who will be involved with performance or management of the requirements of this solicitation.

(2) List all Places of Performance, being careful to include accurate physical locations. *Note: Place of Performance for this solicitation pertains to the physical location of the prime, principal subcontractor, critical subcontractor, and 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.

(3) Provide the CAGE Codes/DUNS numbers associated with the entity that is proposing to perform the work for this solicitation.

**Note: If multiple CAGE codes/DUNS for the same physical location will be involved with performance or management of the requirements of this solicitation, ensure they are identified on separate lines in Table ES-1 (Offeror Summary). Or, if there are current and previous CAGE codes/DUNS as a result of a corporate acquisition, reorganization, merger, or other administrative reason, that 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, ensure all CAGE codes/DUNS are identified in the table below. Further, provide a written explanation, within this section, that includes a description of all such changes in the organization;

(4) Provide a brief work description and/or program responsibility. Additionally, provide a definition of the legal relationship between the entities if it is other than a Prime/subcontractor relationship in the “Brief Work Description and/or Program Responsibility” column; and

Provide the percentage of total proposed price being careful to include all subcontractors (principal subcontractors, critical subcontractors, and all other subcontractors) and team members so that the total proposed price adds up to 100% of the contract price.

Table ES-1 Offeror Summary

b. Technical – Provide a summary of the effort and identify how its approach addresses the requirements of this solicitation as well as the salient features of the Offeror’s management approach;

c. Past Performance - Provide a summary of the Offeror’s (and Offeror’s principal subcontractors, critical subcontractors, and JV team members) past performance and systemic improvements which pertains to the tasks required by this solicitation;

d. Corporate Experience – Provide a summary of the Offeror’s (and Offeror’s principal subcontractors, critical subcontractors, and JV team members) relevant corporate experience, which pertains to the tasks required by this solicitation;

e. Contract Administration – Provide a summary of any exceptions or deviations and proposed Section H clauses addressed in Volume 6 Contract Administration; and

f. The Offeror shall complete Attachment L-3 (Table ES-2 Relevant Contract Summary) for all contracts proposed as relevant for Past Performance and/or Corporate Experience for the prime, principal subcontractors, critical subcontractors, and JV team members. An electronic version of Table ES-2 (Relevant Contract Summary) is provided as Attachment L-3 and is to be submitted within this section and as a separate electronic file. Each contract shall be given a unique contract reference number where prime contractors references (regardless if the prime contractor noted in the Table ES-1 (Offeror Summary) performed previously as a prime contractor or subcontractor) are denoted by P1...Pn (where n is the total number of contracts referenced for each type of entity, where entity is defined as the prime, principal subcontractors, critical subcontractors, or JV team member), subcontractor contracts will be denoted as S1...Sn (regardless if the subcontractor noted in the Table ES-1 (Offeror Summary) performed previously as a prime contractor or subcontractor), and JV team member contracts will be denoted as T1...Tn (only include contract references labeled as T1…Tn where the same Joint Venture Team members previously performed as a Joint Venture Team). The contract references shall be numbered consecutively across all subcontractors and also JV Team Members (as illustrated by the example below). Ensure that contracts identified in Past Performance are numbered consistently with those identified in Corporate Experience (i.e. P1 in Past Performance is the same as P1 in Corporate Experience, etc.). The references designated in the table below shall be used in completing Volume 3 Table PP-1 (Past Performance Relevant Contract Summary and Data), and Volume 4 Table CE-1 (Evaluation Area Summary), and should be consistent throughout;

Reference

(Past Performance) Volume 4 (Corporate Experience)

P2

P3

T2

T3

T4

S2

S3

S5

2.0 VOLUME 2 - TECHNICAL PROPOSAL

Note: This volume shall not contain any reference to 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:

Throughout the Technical Volume the Offeror should identify any capability, approach or feature that is being proposed as exceeding a requirement or provides merit associated with a performance or operational benefit to the Government or being proposed as reducing 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. Appreciably exceeding requirements that are expressed as a minimum or threshold requirement can potentially produce performance or operational benefits. Beyond the point where there is performance or operational benefit, there may be risk reduction benefits. Additionally, a proposal that provides the Government with a capability, service or resource that is not specifically required, but benefits the Government can have merit if it appreciably enhances performance and/or operations to benefit the Government. 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 price.

Please provide a printed copy of Attachment L-1 (General Instruction section Table 3.2 Cross Reference Matrix), as the first page of this volume.

2.1 Management

2.1.1 Management Support Approach

The Offeror shall:

a. Management Approach Provide a brief overview of the management approach, identifying the major challenges and inherent risks associated with the proposal. The Offeror shall also describe the lines of authority and the levels of responsibility of management personnel proposed for this solicitation.

b. Organization

(1) Provide a high level organizational chart that clearly reflects the position of this program within the structure of the corporate organization.

(2) Provide a detailed organization chart for each site. Clearly differentiate between management and direct personnel, and highlight positions filled by key subcontractors. For each site, the detailed organization chart shall provide the number of full time equivalent (FTE) personnel by:

i. Labor category (e.g. Aircraft Life Support System Technician, Egress Technician, Avionics Technician, Aircraft Mechanic etc.);

ii. CNAF 4790.2B Appendix E work center code; and

iii. Work shift.

(3) For each management/supervisory position in the organization, the Offeror shall describe the following:

i. position descriptions;

ii. qualifications/ certifications; and

iii. supervisory and technical training.

2.1.2 Subcontract Management

Describe the Offeror’s strategy for subcontract management and control of the performance of this contract. In describing its strategy, the Offeror shall describe its approach and the complexity and variety of the work the subcontractors are to perform. Identify what portion of the contract, or specific tasks, shall be passed to the subcontractors to ensure compliance with contract technical performance, price, and schedule requirements.

2.1.3 Transition-In Management

Submit a detailed plan that will ensure a smooth and phased transition to full performance. The Transition Plan should include the following:

a. A time phased manning plan that indicates staffing by site, work center and function during transition in order to demonstrate a "ramp-up" to achieve full manning levels and performance. Analysis should account for workload requirements/fluctuations, operational commitments/tempo, work in progress, and other area impacts;

b. A program to train key maintenance and management personnel during transition, including a method for incorporation of lessons learned at previous site transition(s); and

c. A training plan for personnel whose job requires formal certification/licensing prior to assumption of tasks, by site.

2.1.4 Small Business Management

a. Small Business (SB) Utilization Strategy All Offerors (Large and Small Businesses) shall address their strategies for utilizing SB Concerns in the performance of this contract, whether as a joint venture, teaming arrangement or subcontractor. SB Offerors may meet this requirement using work they perform themselves. For purposes of this solicitation, the term SB Concern shall also include the subcategories of Small Disadvantaged Business, Women-Owned SB, HUBZone SB, Veteran-Owned SB, and Service-Disabled Veteran-Owned SB. Each subcategory of SB shall be addressed. This strategy is separate from, but shall be consistent with, the SB Subcontracting Plan, if such a Plan is required. 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), as a minimum provide evidence of self-certification in accordance FAR 19.703(b) as a 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) Provide goals, expressed as dollars and percentages of total contract values and percentages of total subcontract values for SB Concerns and each subcategory of SB, using the format depicted below and provided electronically in Attachment L-4 (Table T-1 Small Business Goals). The Offeror shall provide Table T-1 as part of Annex B ((Small Business Subcontracting Plan) and Table T-1 (Small Business Goals)). Use tab 1 for the prime and tab 2 etc for each subcontractor as goals of subcontractors must be listed separately;

Table T-1 Small Business Goals Offeror Name

Large Business

Small Business (SB)

Total

100%

Small Disadvantaged

Women-Owned SB

HUBZone SB

Veteran-Owned SB (VOSB)

Service-Disabled VOSB

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

(6) Demonstrate (Large Business only) 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, the Offeror shall describe how SB participation on this contract will contribute to its overall Comprehensive Subcontracting Plan goals.

b. Small Business Subcontracting Plans The Large Business Offeror shall provide its Small Business Subcontracting Plan conforming to the requirements of FAR 19.7 and DFARS 219.7 as part of Annex B. The SB Subcontracting Plan of the successful Offeror(s) will be reviewed and approved by the PCO prior to contract award. See FAR 19.702(a)(1) Statutory Requirements, regarding failure of the apparent successful Offeror to negotiate and submit a SB Subcontracting Plan or a Comprehensive SB Subcontraction Plan acceptable to the Contracting Officer. The successful Offeror’s approved Subcontracting Plan will be incorporated into the resultant contract.

2.2 Maintenance Support Concept

2.2.1 Maintenance, Ground and Flight Operations

a. The Offeror shall describe the approach to support diverse aircraft types i.e. T-45A, T-45C, and T-45C(VMTS), operations, and locations as well as manage the timely execution of routine and non-routine aircraft flight operations including:

(1) Normal flight operations, night operations and weekend/ holiday operations;

(2) Off-station/cross-country operations;

(3) Detachment support;

(4) Crash damage support and/or downed aircraft retrieval;

(5) Flight hour surge capability support requirements;

b. Describe the Offeror’s approach in the management of the NALCOMIS OOMA/OIMA based maintenance department;

c. Provide a block diagram or flow chart, and procedures indicating how the maintenance control organization shall function and control maintenance processes. The block diagram or flow chart and procedures shall:

(1) Include the planned on-site or off-site maintenance which relates to and/or supplements the provided narrative information and

(2) Identify critical maintenance processes and the proposed approach to control these processes

2.2.2 Quality Control

The Offeror shall describe its Quality Control Program in accordance with CNAFINST 4790.2 Series, and illustrate the extent to which that program shall ensure compliance with solicitation requirements and contract performance. The Offeror shall provide a Quality Control Program Plan, Annex C. Provide a brief overview of the information provided in the Quality Control Program Plan and identify any major challenges and inherent risks. The Quality Control Program Plan, Annex C, shall also be included as part of the Volume 6 Contract Administration. Also include the following information in the proposal:

a. Quality System - Describe the proposed Quality System and demonstrate the degree to which it satisfies each element of AS9100C, Quality Management System Requirements. Describe the approach to ensuring compliance with the CNAFINST 4790.2 Series requirements. Demonstrate the effectiveness of the proposed system’s capability/functions by providing historical data and analysis of that data.

b. Quality Cost Data - Describe the proposed system for maintaining and using quality cost data and describe how it is to be used as a management element of the quality program. Identify the specific data to be maintained and describe the degree of accessibility that the Government shall have to this data.

c. Risk Management Data – Describe the proposed system for maintaining and using trend data and describe how it is to be used for accomplishing risk management on high and moderate risk systems, processes, and characteristics.

d. Management Review - Identify defined review intervals. Describe the process for ensuring distribution of defined intervals, identified concerns and actions taken to contractor corporate level management, the ACO and PMA-273.

2.2.3 Patuxent River Test and Maintenance Support

a. The Offeror shall describe its approach to management of test aircraft to include configuration management and non-standard aircraft modifications; and

b. The Offeror shall describe its approach to managing prioritization of maintenance efforts, ground and flight tests, and project modifications and installations.

2.2.4 Depot Maintenance and Modification

Provide the following information for Aircraft Depot Maintenance and Modifications (Integrated Maintenance Program (IMP), Strip and Paint (S&P), Technical Directive (TD), Required Avionics Modernization Program (RAMP), Virtual Mission Training System (VMTS), and Digital Data Set (DDS) and Component Depot Overhaul and Modification).

a. Aircraft and Component Depot Maintenance and Modifications The Offeror shall:

(1) Describe the Offeror’s approach for performing aircraft maintenance with respect to work flow, e.g. moving product line, work stations, etc.

(2) Demonstrate how the aircraft maintenance required by the PWS will be accomplished given the Offeror’s approach. Illustrate the planned aircraft maintenance process by means of a flow or block diagram. For each level of aircraft maintenance, identify critical aircraft maintenance processes, and the proposed approach to controlling these processes. Identify critical points in the process that will be monitored to measure process efficiency, determine corrective action needs, and measure continuous improvement progress. Where adequate technical documentation/instructions do not exist, describe how and when specific work instructions will be developed and implemented.

2.3 Supply Support Concept

2.3.1 Supply Chain Information System (Inventory Management and Asset Visibility) The Offeror shall:

a. Provide flowcharts and procedures indicating how the supply support organization will function and control supply processes.

b. Describe its approach to performing supply support functions and identify when and where vendors/off-site activities are involved in the process and show how it is handled within the supply process with regards to the following:

(1) Total Asset Visibility;

(2) Component Repair Status;

(3) Repairable Component Disposition;

(4) Physical Inventory Management;

(5) Parts Requisition;

(6) Failure and Trend Analysis;

(7) Configuration Management;

(8) Component and Material Forecasting;

(9) Shelf-Life Management;

(10) Warranty Management;

(11) Export License Management; and

(12) Diminishing Manufacturing Sources and Materials Shortages (DMSMS):

a. Management of parts obsolescence and Diminishing Manufacturing Sources and Material Shortages (DMSMS) for T-45 aircraft components; and

b. Mitigation of obsolescence and/or DMSMS risks with regards to the use of predictive forecasting tool(s), parts list screening, and bill of materials (BOMs).

2.3.2 Repair of Repairables

The Offeror shall:

a. Describe the Offeror’s approach to procure T-45 unique consumable parts and repairable parts not provisioned in the Navy Supply System;

b. Describe how parts will be procured and repaired for which the Government does not own the technical data package. Specifically address those parts that have never been repaired or replaced on the aircraft; and

c. Provide a description of the documentation and controls at the point in the process where a part is sent to a vendor or off-site activities for additional work or inspection and at the point in the process where these parts are returned to supply. Explain how the Offeror will provide the Government information or data on component/sub-component failure causal modes and repair actions and show the process(es) using flow chart(s) or diagrams.

2.4 Manpower Management

The Offeror shall:

a. Describe the process for determining proposed staffing levels to meet the requirements of this solicitation. Further, the Offeror shall describe the process for recruiting and retaining employees; Specifically, a comprehensive workload/work-year analysis to support site-staffing levels for a Naval Aviation Logistics Command Management Information System (NALCOMIS) Optimized Organizational Maintenance Activity (OOMA)/Optimized Intermediate Maintenance Activity (OIMA) based maintenance department.

b. Show how skilled positions, including Sustaining Engineering, requiring a type of special licensing or certification are identified. Describe their integration, duties, responsibilities, and authority within the on-site maintenance organization. Provide certification and skill level distribution logic. Describe how lesser skilled and non-licensed personnel will be integrated into the maintenance process, and how their efforts will be overseen and supervised. Submit narrative descriptions of the composition and responsibilities of on-site work centers, division, and departments. Fully identify all indirect labor classifications, titles and responsibilities and how they will be integrated at these sites; and

c. Provide the basis for determining the proposed staffing levels. Include historical data, or comparison analysis with other aircraft maintenance services. General statements such as “estimates were derived from engineering judgment” or “estimates were derived from comparison with similar services” are not acceptable substantiation unless the details of the analysis are provided. If “new or improved” methods or standards are the basis for work-hour assessments, a detailed discussion shall be provided describing any process efficiencies that were used and how improvements over the established standards will be achieved. The impact of “learning” and “efficiencies” must also be discussed and assumptions or conclusions must be substantiated. Describe the method by which the work-hours, work loading and work shifts were calculated or determined and identify data or standards used. Describe adjustments from data or standards and the rationale used to develop the work-hours, work loading and work shifts for each process step identified on the flow chart. Provide a definition of work year capabilities of the work force (equivalent man hours/year analysis) that are the basis of the productive man-year rate.

d. Describe workforce management plans for recruitment, retention, incentives, and education/development.

2.4.1 Manning

Based on the requirements of the PWS, submit the proposed manning plan indicating numbers of people and requisite skill level mix for all periods of performance associated with this effort. Describe how the proposed on-site maintenance manning plan will accomplish the requirements of this program. Provide an overview of the major challenges and inherent risks associated with the manning proposal. Ensure management personnel are included within the respective work center breakdowns. The Offeror should be advised that the manning requirements for on-site maintenance need to include the requirements to perform detachment(s) as required in the PWS.

The Offeror shall utilize Attachment L-5 (Manning Analysis) to provide the proposed manning to meet the requirements based on the solicitation for all Contract Line Items, including…