N00019-11-R-0024 Amendment 0001.doc

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

SECTION J - List of Documents, Exhibits, and Other Attachments

*Attachments 12, 19-25 are specific to the solicitation only and shall be removed prior to execution of the contract award.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

L-1 CONTENT OF PROPOSALS (SUPPLIES OR SERVICES)(31 OCTOBER 2011)

PART A GENERAL INSTRUCTIONS

1.0 GENERAL

The Offeror is required to submit sufficient information concerning the following areas 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 capability to meet or exceed the defined elements 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 that the Offeror has valid and practical solutions for all requirements and potential risk areas. Offeror must respond to all requirements of the solicitation and not alter or rearrange the solicitation. The Offeror has the burden of proof to demonstrate compliance with all the evaluation factors and or subfactors identified in this solicitation. The Offeror is advised that the Government may incorporate into the final contract enhancing features included in the Offeror’s proposal deemed beneficial to the Government. With the exception of Volume 5 Price, Small Business Subcontracting Plan (Annex C), and Volume 7 Model Contract Documents, no cost or pricing information should appear in any 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. The Offeror is responsible to present enough information to allow the Government to evaluate the proposed work effort, support, and approach, as well as the price/cost proposal without opening discussions. Statements that the prospective Offeror understands, or can and/or will comply with, the specifications, and paraphrasing the requirements or parts thereof without supporting information are considered inadequate by the Government, and may render a rating of unacceptable. For the purpose of this solicitation, relevance is defined as something that has a logical connection with the matter under consideration. Such aspects of relevance include the type of effort (e.g., development, production, repair), the type of requirements (e.g., weapon systems, information systems, engineering services, scheduled depot maintenance), service similarity, service complexity, contract type, contract dollar value, the division of the company that will perform the work, and degree of participation by principal subcontractors, team members, or critical team members. Recency is defined as performance within 5 years of the date of this proposal submission.

The Offeror must include any data that illustrates the adequacy of the various assumptions, approaches, and solutions to problems. Failure to address a specific factor or subfactor clearly may be considered a deficiency. There is no need to repeat information in more than one volume if an overlap exists; the detailed information must be included in the most logical place and summarized and referenced in other areas. Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

The Offeror is expected to comply with all requirements of the RFP. The Government advises the Offeror that taking exception or deviating from any term or condition of the RFP may make an offer unacceptable, and the proposal unawardable, 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.

Throughout these instructions, a “principal subcontractor” is defined as a subcontractor who provides at least 10% of the proposed total price/cost (excluding the Offeror’s profit/fee), for the contract. “Team member” is defined as those entities that make up a joint venture or any other partnership or teaming arrangement formed for the purpose of responding to this solicitation. “Critical team member” is defined as those entities of the Offeror that perform a critical function in the performance of the resulting contract, whether it is technical or financial, and/or that have important roles in any high or medium risk areas identified in the Offeror’s proposal.

2.0 PROPOSAL FORMAT

Written 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 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. Graphs shall be presented in no smaller than a 10 pt font and 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.

The Offeror will provide one complete copy of the written proposal to the Procuring Contracting Officer PCO as electronic files fully compatible with Microsoft Office 2007 and for information not supported by MS Office products, with the latest Adobe Acrobat reader on a CD-ROM. The Offeror will ensure that the Price/Cost Volume is provided on a separate CD-ROM. Each CD-ROM is to be labeled for content and the Offeror’s name. If a discrepancy exists between the original paper copy of the proposal and the disk copy, the paper copy will take precedence.

3.0 PROPOSAL CONTENT AND VOLUMES

Each volume of the proposal shall be submitted as one original and additional copies as specified in the table below. All volumes of the original proposal shall be delivered to the address provided in Section 4.0 prior to the closing date/time stated in this solicitation Page limitations for each volume if any, are also specified in the table below; title and table of contents pages do not count towards page limit. Proposal pages beyond the specified maximum limit will not be reviewed as part of the evaluation.

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 Part B Specific Instructions. Annexes do not have page limitations. The authorized Annexes are summarized in the table below.

(L-1, Part B 2.1 Management Plan through 2.1.6.6 Transition)

To include Proposed Manning Excel Workbook—Attachment 21 TECHNICAL ONLY

To include Quality Control Plan as a Attachment

To include Small Business Subcontracting Plan as a Attachment

Each volume shall contain the following information:

Cover and title page

Title of proposal and proposal number as applicable

Offeror’s name, address and POC

RFP number

Proposal volume/book number

Copy number

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

Use tabs and dividers

The Offeror shall submit a Cross Reference Matrix (CRM) for the Technical Volume, similar to the example below, to help ensure that all solicitation requirements are addressed and to facilitate the evaluators’ review of the Offeror’s proposal. The CRM should be a single integrated matrix and cross-reference the proposal volumes and paragraphs to specific RFP requirements, as well as other parts of the proposal that contain relevant information. The Offeror’s CRM may be identical to the example below or revised such as to add columns to indicate the page number on which information may be found, identify where other relevant information in the proposal is located, or provide other comments. The CRM does not count against any of the proposal page limitations.

EXAMPLE OF A CROSS REFERENCE MATRIX (CRM)

0x02, 0x08

0x02, 0x08

0x02, 0x08

0x02, 0x08

0001,0007 (OPTION 0414, 0415)

0x02, 0x08

0x02, 0x08

0x02, 0x08

4.0 PROPOSAL SUBMISSION:

Clearly mark all packages with the solicitation number. The submission date for the original proposal, shall be no later than the date and time specified in Block 9 of Standard Form 33 of the RFP. However, Offeror shall also submit a copy of Volume I, Executive Summary “Offeror’s Summary Table”, 1.0 (ii) on 23 December 2011. Proposals shall also be clearly marked with a validity date. Proposals shall remain valid through 31 October 2012 at a minimum.

Offeror shall submit proposals via United States Postal Service or through a commercial carrier using the address provided below. Offeror shall not submit proposals by facsimile or electronically via email.

Naval Air Systems Command

Code: AIR-2.2.4.2.1 (Bernard K. Gross)

Address 21936 Bundy Road, Bldg 442 Patuxent River, MD 20670

Solicitation Number: N00019-11-R-0024

Hand carried proposals may be delivered to the address above, attention Dee A. Peters and/or Bernard K. Gross.

5.0 PROPOSAL 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. Each container shall be single person portable. One container shall include all Original Proposal volumes including the original/signed documents submitted as part of Volume 1 Executive Summary.

Each box should include a packing slip detailing the contents to include the volume number, title, and copy number. Also, each box should be stamped or marked “For Official Use Only” and “Source Selection Information – See FAR-2.101 and 3.104”.

6.0 CLASSIFIED DATA

All proposals must be UNCLASSIFIED

7.0 SOLICITATION CHANGES

For any changes and additional information for the solicitation please go to website:

https://www.fbo.gov

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 purpose of the Executive Summary is to provide the evaluators with an overview of the Offeror’s proposal and strategy. The Offeror shall include the following in this volume:

i.

A concise abstract of the Offeror’s strategy for each of the evaluation criteria contained in the solicitation.

ii.

Offeror Summary Table: The Offeror shall complete the table below. The Offeror should include all subcontractors and team members who will be involved with the performance or management of the program work and should list all sites where the work will be performed. If a teaming or subcontracting arrangement is proposed, identify the work share, distribution elements, and ratios that each contractor will perform using the table below. Also provide a definition of the legal relationship between the entities if it is other than a Prime/subcontractor relationship.

Contractor Name

(Indicate Prime, Team Member or Sub)

iii.

Signed SF33 for basic solicitation and each amendment

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

Affirmation of no Exceptions, Deviations or Waivers if Volume 6 is not being submitted as part of the proposal.

2.0 VOLUME 2: TECHNICAL

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

The Offeror shall provide all information and data required to conduct a thorough and complete technical evaluation. The Offeror shall address the following in the proposal, at a minimum:

2.1 Management Plan, including Transition and Small Business Utilization

2.2 Staffing Plan

2.3 Quality Control Plan

2.1. Management Plan

2.1.1 Risk Management -- 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. The Offeror’s proposal shall identify potential problems/pitfalls that could impact performance/services associated with this effort and describe specific actions of how the Offeror intends to minimize the pitfall impact, to include the following: Description of the problem/pitfall; Risk assessment of degree of risk the problem posses; and Offeror’s mitigation and control impact, and how PWS requirements will be fulfilled.

2.1.2 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.1.3 Management Information System-- Describe the system and how it shall be used to plan and control costs, plan and control maintenance, measure performance, and generate timely, reliable and accurate management information for this program. State any differences between your existing system and the system being proposed. Provide a Plan of Action and Milestones (POA&M) for completion of any changes to your existing system or development of a new system. Provide evidence that the system is, or shall be used internally to manage contract performance and demonstrate its capabilities. Explain how this system provides the capability to plan, control and manage the workload required by this solicitation. If applicable, explain how the system is used to manage workload in conjunction with other competing work. Provide examples of output from the existing systems. Include the following:

2.1.3.1 Maintenance Management-- Describe the tools, technology and methodology to manage and control workload associated with repair, preventive maintenance, predictive maintenance and maintenance resources including collection and reporting of maintenance data. Describe the work process and documentation for reviewing, approving and assigning workload priorities including management of the ICRL. Describe the procedures to improve overall maintenance program and conduction of maintenance meeting with supported activities. Describe the tools and methods for measuring quality, efficiency and performance to meeting or exceeding contractual requirements. Describe how Government will be provided access to to this information.

2.1.3.2 Financial Management -- Describe the system for obtaining and accounting for all costs and man-hours associated with the performance of this program, including field team efforts. Show the extent to which the system can account for all costs and man-hours associated with this effort. Identify any changes to the existing system in producing the cost and man-hour accounting reports required by this solicitation or as needed to provide the management planning, direction and control necessary for this program.

2.1.3.3 Data Management-- Describe the data management capabilities for facilitating the planning, direction and control of this program and for fulfilling the data requirements of this RFP including maintaining the technical library and control of drawings. Provide a description of the existing data collection and reporting system. Describe the capabilities such as information resources that shall be used to communicate, record and report information. Identify any changes planned for this system due to the needs of this program. Describe procedures for ensuring that current technical data shall be maintained and for ensuring that outdated technical data shall not be used.

2.1.4 Environmental Compliances-- Describe the Offeror’s approach for ensuring compliance with base, local, State and Federal requirements regarding air quality emissions limitations and safety, hazardous material and hazardous waste handling, storage and disposal.

2.1.5 Performance Measurement -- Describe the Offeror’s approach to achieve threshold and maximum contract performance as measured by the Government’s Performance Measurement Requirements, detailed in Attachment (1) PWS, Section VIII. Indicate how the metrics shall be used to manage the program. Show trigger points that prompt action.

2.1.6 Transition (In to and Out of) Full Performance (PWS Section XV)-- Submit a detailed Phase-In Transition Plan that shall ensure a smooth and phased transition to full performance. The Phase-Out Transition Plan should address cooperation with the succeeding Contractor to ensure an orderly transition and how they will continue to maintain accountability of all property in the inventory until delivered and accepted. The Phase-In Transition Plan should address the following:

2.1.6.1 Time Phased Manning Plan-- Submit a time phased manning plan that indicates staffing by site, work center and function during transition. Indicate an eventual "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.

2.1.6.2 Key Maintenance and Management Training-- Describe the program to train key maintenance and management positions during transition, including method for incorporation of lessons learned at previous site transition(s).

2.1.6.3 Formal Certification/Licensing-- Describe the training plan for those jobs requiring formal certification/licensing prior to assumption of tasks, by site.

2.1.6.4 Start-Up Considerations-- Identify the major challenges with regard to start-up and “learning”. Describe your approach to minimizing start-up time as well as the effects of learning on accomplishing the work effort. Address formal and/or on the job training specific to the efforts required by this solicitation. Illustrate that start-up and learning considerations are reflected in the overall schedule.

2.1.6.5 Work Instructions, Procedures, and Planning Documents-- Provide a Plan of Action and Milestones (POA&M) for the development of the work instructions, procedures, and planning documents needed to begin the program. Demonstrate that the work instructions, procedures and plans required to perform the work of this solicitation shall be completed prior to full performance and that the artisans shall be trained to use these work instructions, procedures, and plans prior to its use. Describe the type of directions that work instructions shall provide artisans. If available, provide an example of a work instruction used on a similar program. If not, provide an example of what these work instructions shall look like for this program.

2.1.6.6 Quality Control Program Plan Implementation-- Describe the implementation of the Quality Control Program Plan during transition. Include how the Quality Control Program Plan shall be implemented with the subcontractors to ensure compliance with contract technical performance, price, and schedule requirements.

2.1.7 Small Business Utilization

2.1.7.1 Strategies for using Small Business (SB) Concerns-- 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. For purposes of this solicitation, SB shall also include Small Disadvantaged Business, Veteran-Owned SB, Service-Disabled Veteran-Owned SB, HUBZone SB, Women-Owned SB, and Historically Black Colleges or Universities (HBCU) and Minority Institutions (MI). Each subcategory of SB shall be addressed. (This strategy is separate from, but shall be consistent with, the Small Business Subcontracting Plan, if the Plan is required.) In describing its strategy for this solicitation, the Offeror shall, as applicable:

Describe its approach to identifying SB Concerns;

Describe the extent of participation of SB Concerns on this contract, especially as principal subcontractors;

Describe the extent of commitment to use such SB Concerns;

Describe the complexity and variety of the work SB Concerns are to perform;

Identify what processes have been implemented to correct past inabilities to meet proposed goals;

Demonstrate (Large Business only) that its SB strategy is consistent with its SB Subcontracting Plan.

Provide targets, expressed as dollars and percentages of total contract values for SB participation. Targets of subcontractors must be listed separately. Note: This calculation is different from the calculation required by FAR 52.219-9 in the Subcontracting Plan, as the Plan requires percentage of subcontracting value;

Demonstrating Realism through Submission of Reports: To demonstrate the realism of the utilization strategy, the Large Business Offeror shall provide copies of the final or most recent SF 294s/Individual Subcontracting Reports (ISRs) for the most current three relevant contracts, that best demonstrate the Offeror's ability to achieve the proposed subcontracting goals. If the Offeror is a participant in the DoD Comprehensive Subcontracting Test Program, they shall provide copies of three final or most recent SF 295s/Summary Subcontracting Reports (SSRs). Explain how the results shown in the recent SF 295/SSR demonstrates the realism of the plan. The Small Business Offeror may provide this information in a format substantially the same as the ISR or SSR.

2.1.7.2 SB Subcontracting Plans-- The Large Business Offeror shall provide its SB Subcontracting Plan conforming to the requirements of FAR 19.7 and DFARS 219.7 as Annex C. 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 goals. The Offeror shall 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 programs and industry conferences, establishing Mentor-Protégé relationships and using the NAVAIR Office of Small Business Programs website (http://www.navair.navy.mil/osbp ) to locate small business concerns.

(Note: The Subcontracting Plan of the successful Offeror(s) will be reviewed and approved by the PCO prior to contract award. See FAR 19.702 Statutory Requirements (a)(1) regarding failure of the apparent successful Offeror to negotiate and submit a Plan acceptable to the Contracting Officer.) The successful Offeror’s Subcontracting Plan will be incorporated as an attachment to the resultant contract.

2.2 Staffing Plan

2.2.1 Manning/Staffing Level-- In its proposal, the Offeror shall fully complete and provide a separate On-Site Manning Chart (Solicitation Section J, Attachment (21), On Site Manning Chart TECHNICAL ONLY) for the NASP and NASCC AIMD annual Support, based on historical data as provided in Attachments (14.1), (14.2), and (12). For Option Years with identical data, one chart may be submitted (i.e., the one On-Site Manning Chart would apply for each option year). All data blocks on the On-site Manning Charts shall be completed. No Price information shall be provided in the Attachment (21) Manning Chart. Any abbreviations shall be identified. The Offeror shall describe its manning approach, subcontracting strategy and rationale. The Offeror shall describe how premium time requirements will be met, and how they will staff/plan for the non-routine requirements of the PWS.

2.2.2 Qualifications and Certification-- The Offeror’s proposal shall identify how it will ensure stability and uninterrupted on-site Contractor Maintenance Support Service performance. The Offeror’s proposal shall identify its approach/plan for ensuring fulfillment of personnel qualifications and certifications per PWS requirements. The approach/plan shall include a remedial plan that addresses poor/declining contractor employee performance. The Offeror’s proposal shall identify how it will ensure qualified and certified personnel are provided in the event of the employee loss and in the case of an incumbent employee from the previous contract not returning to work for the Offeror. If part-time personnel are proposed, the Offeror’s proposal shall delineate how expertise and continuity will be maintained.

2.2.3 Training-- The Offeror’s proposal shall identify its plan for training new workforce personnel. The Offeror shall identify any training approach that will ensure initially-hired and current workforce expertise is maintained and/or improved. The Offeror’s proposal shall identify its plan for ensuring its workforce is trained and kept current with the expertise necessary to meet the requirements of the PWS. The Offeror’s proposal shall specify how it will ensure the necessary expertise will be provided in instances when modification of equipment or addition of added equipment causes maintenance changes and/or new documentation procedures.

2.2.4 Recruitment and Retention-- The Offeror shall provide its plan/approach to retain experienced employees/subject matter experts and managers/supervisors to meet PWS requirements and retain site performance stability. The Offeror shall provide a plan for how it will minimize loss of performance caused by short notice losses/termination of workforce personnel. The Offeror shall identify any procedures or approaches/plans for attracting and retaining appropriately-skilled workforce personnel.

2.3 Quality Control Plan

2.3.1 Quality Control Program Plan-- The Offeror shall describe its Quality Control Program Plan (PWS paragraph 9.1.2.2 and CDRL A003) 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 A, in accordance with the instructions in CDRL A003. Provide a brief overview of the information provided in the Quality Control Program Plan and identify any major challenges and inherent risks. Also include the following information in the proposal:

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

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

3.0 VOLUME 3: PAST PERFORMANCE

3.1 General

The Offeror shall identify any contracts performed within five years of this proposal submission date which contains efforts similar to those performed by Offeror, Offeror’s principal subcontractors, and critical team members in solicitation. e.g., tasks, complexity, contract type, contract dollar value, etc. Commercial contracts may be included. List the contracts from the most relevant to the least relevant. In general, recent performance will be considered more relevant than older performance. When possible, these contracts should include at least five of the most relevant contracts for the prime contractor, five of the most relevant contracts for each critical team member, and two of the most relevant contracts for each principal subcontractor (as defined in Paragraph I, General Instructions). If proposing as Joint Venture/Single Legal Entity (JV/SLE), the Offeror should provide the five past performance references for the JV/SLE. If less than the five past performance references are available for the JV/SLE, each member of the JV/SLE should individually submit the five references in addition to their JV/SLE references.

For each contract identified, provide contract data, relevancy, past performance, and systemic improvement information as described below. Demonstrate the relevancy of the Offeror’s, and if applicable, the Offeror’s principal subcontractors’ or critical team members’ past performance and systemic improvements with respect to the solicitation requirements. For each past performance problem identified, describe the status of the systemic improvement efforts and, where applicable, demonstrate the impact that the systemic improvement effort had on resolving the problem such that it would not reoccur.

For contracts that have CPARS Reports that are more than six months old, e.g., the completion date is more than six months before the due date for this Past Performance Volume; the Offeror will forward a copy of the CPARS Update Questionnaire (Attachment (19)) to that contract customer’s Program Manager. For all contracts identified which do not have CPARS Reports, the Offeror will forward a copy of the Past Performance Questionnaire (Attachment (20)) to that contract customer’s PCO, Administrative Contracting Officer, and Program Manager. All questionnaires shall be forwarded within two weeks from the RFP release date with enough lead-time so that responses can be received by the Government prior to the Government’s receipt of the Offeror’s Past Performance information. The Offeror shall include instructions for the customers to send completed questionnaires no later than 23 December 2011 via e-mail to Bernard Gross, at Email bernard.gross@navy.mil or via fax number 301-757-2276. This submittal information is provided at the top of the questionnaires to facilitate the Offeror’s effort in meeting these instructions. The Offeror shall not conduct follow-up actions with regard to this questionnaire. The Government will ensure that the customers have received and will respond to the questionnaires. The Government may send any other questionnaires as necessary.

The Offeror shall provide written consent from their principle subcontractors and critical team members that will allow the Government to coordinate their Past Performance issue(s) with the Offeror. If the Offeror does not submit such written consent, then the Government will address any past performance issues directly with the principal subcontractor or critical team member and the Offeror will forfeit the opportunity to participate in any related discussions. Consequently, for any principal subcontractors and critical team members that do not provide such written consent, provide a point of contact (name, address, phone number, and email address) with which the Government may coordinate these issues and obtain any responses as needed.

The Government may use information other than that provided by the Offeror in their proposals to evaluate past performance. The Government may use Past Performance information obtained from sources other than those identified by the Offeror. The Past Performance Information Reporting System (PPIRS) will be the primary method used to evaluate Past Performance. It is incumbent upon the Offeror to explain the relevance of the data provided. The Government has no duty to search for data to cure the problems it finds in the information provided by the Offeror. The Offeror has the burden of providing thorough and complete past performance information.

(a) Contract Data

Provide all the information identified below separately for each contract. Additionally, provide this information electronically as a separate file on CD-ROM, which contains Offeror’s Past Performance proposal in a Word Table in the format depicted below:

Relevant Contract Data

Prime (P), or Sub (S)

1 – Place of Performance should be the same as being proposed in this solicitation. If different please include an explanation.

2 - CPARS (yes/no) - CPARS completion date - on DOD PPAIS (yes/no) (Indicate whether or not any CPARS have been completed and identify the last CPARS completion date and if it is currently on DoD PPAIS)

3 Recency-Efforts performed within the last five years.

4 - Relevancy – Provide a concise assessment of the degree of relevancy that each contract identified has to the solicitation; identifying tasks and/or aspects of the effort undertaken on the contract that are relevant to the program. Also provide the Offeror’s assessment of the relevancy of the contract in terms of one of the following ratings: Very Relevant (V), Relevant (R), Somewhat Relevant (S), or Not Relevant (N) where:

Past Performance Relevancy Ratings

(b) Relevancy -The Offeror shall explain what aspects of the contract are deemed relevant to the proposed contract. At a minimum, identify key or critical tasks of the solicitation and indicate the relevancy of the “past performance” contract to these tasks. Also identify where contract performance took place and provide rationale why it is relevant to the solicitation if the location is different from where the related effort is proposed to take place.

(c) Past Performance Information-The Offeror shall provide a brief description of performance in delivering quality products in each of the following areas: 1) meeting technical requirements, i.e., the quality of technical performance, e.g., performing analysis, design, testing, etc., 2) 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) controlling contract cost, i.e., cost performance, e.g., on time or late delivery, modification of original schedules and reasons for any changes, etc., and 4) managing the contracted effort, i.e., program management, e.g., cooperation with customer, subcontract management.

(d) Systemic improvement Information-Identify those systemic improvement actions taken to resolve past problems. Describe the techniques, elements, and tools used to correct problems and, if applicable, how these techniques, elements, and tools will be used during this contract.

Earned Value (If applicable): Provide earned value data generated for that contract, such as Cost Performance Report Format I, with variances, Cost Performance Index, and Schedule Performance Index. Identify if there were any Over Target Baselines or restructures, and how performance data was impacted. For CPARS data, explain significant differences between earned value measure and CPARS rating, e.g., Exceptional CPARS rating under Schedule and SPI of 0.85.

Award Fee (If applicable): Provide a summary of the award fee available and earned for each evaluation period over the past three years of an on-going contract, or last three years of a completed contract (both in dollars earned and percentage of available award fee received).

Small Business Concerns Participation Goals (if applicable): Note whether the contract met or exceeded small business, small disadvantaged business, small business HUB Zone, veteran-owned small business, service disabled veteran owned small business, women-owned small business participation and subcontracting goals.

3.2. Past Performance Data Requirements

Provide all the information identified below separately for each contract. Provide a summary of the Customer’s Points of Contact in a MS Word Table using the format below which is illustrated with an example. Include an electronic copy of this table in MS Word on a CD.

1. Offeror’s Name (Prime, Principal Sub, or Critical Team Member, JV/SLE, JV/SLE Member)

1. Contract #,

4. Offeror’s Role (e.g., prime or sub)

2. Questionnaire # __ Sent?

3. For Subs - Agreement to allow Coordination with Prime?

Point of Contact’s Name;

Phone Number, Fax Number and

E-mail address

4. Prime

2. Questionnaire #1: - Sent 5/4/05

3. N/A

Al (PM)

444-444-4444, fax 555-555-5555, Al@RYP

1. CPARS: No

2. Questionnaire #2: - Sent 5/4/05

3. N/A Sue (PCO)

333-333-3333 fax 222-222-2222

Sue@RTP

1. CPARS: No

2. Questionnaire #3: - Sent 5/4/05

3. N/A Joe (ACO)

111-111-1111 fax 888-888-8888

Joe@ RYP

4. Sub

2. Questionnaire # 1: - Sent 5/4/05

3. N/A Sue (PCO)

333-333-3333 fax 222-222-2222

Sue@AB

4. Prime

2. Questionnaire: - Not Sent

3. Agreement: Yes Sue (PCO)

333-333-3333 fax 222-222-2222

Sue@NNB

4.0 VOLUME 4 CORPORATE EXPERIENCE:

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

The following is the Section L Corporate Experience Attachment that the Offeror shall utilize to provide corporate experience information as required for this volume:

Attachment 24 Corporate Experience Table In this Volume, provide information that describes the Offeror, the Offeror’s principal subcontractors’, critical subcontractors, and JV/SLE team members’ (as defined in Part A, General Instructions) experience, similar to that required for the Performance Work Statement. The experience provided should only relate to “Corporate” experience, which is the experience that an entity (proposed prime, principal subcontractor, critical subcontractor, and JV/SLE team member) has gained through contracted work vice the experience of its personnel. Offerors shall include their experience in any joint ventures as well as acting as an independent Prime. Identify the period of time and the related contracts. Recent experience will be considered more relevant than older experience.

Provide a separate experience summary table by completing Attachment 24 Corporate Experience Table (as outlined below). Complete a separate worksheet for each subtask area and entity (prime, principal subcontractor, critical subcontractor, and JV/SLE team member), where the subtask areas are each subparagraph letter under experience elements A through J, below. For each worksheet provided, submit only those contracts and other information related to that experience in that task area. Ensure that experience is identified only for that which the Offeror is proposed to perform (e.g., a JV/SLE team member assigned to perform Non-Destructive Test/Inspection has much experience in software development, but its software development experience would not be relevant because another entity would be doing that type of work.)

Provide the requested Corporate Experience information in an Excel Spreadsheet as provided in Attachment 24“Corporate Experience Table.” The Offeror should include tabs in Attachment 24 for each subtask area (A through J, below). Provide the completed Attachment 24 electronically in a single spreadsheet, as a separate file (Annex D) in the Corporate Experience Volume CD-ROM and as part of the Offeror’s Volume 4 Corporate Experience proposal. Please note that this form is a summary of your experience data. All detailed information and comparative analysis of the corporate experience references to the solicitation requirements shall be provided in Volume 4 of the Offeror’s proposal.

In addition, provide the table requested in section 1.0 paragraph ii, Volume I, Executive Summary, however, the column entitled “Approximate % of Total Proposed Cost” is not needed for this volume.

In the below areas (A through J), the Offeror should provide examples of experience performing the efforts. The Offeror should describe the breadth and depth of the work performed where breadth is the degree to which the Offeror has performed all activities/tasks of a given effort and depth is the extent to which each activity/task of the effort was performed, e.g., frequency of occurrence (number of iterations), the degree to which sustained activity was performed, or the amount of rigor (detail) applied to the activity. Experience noted should be relative to proposed roles and responsibilities of the Offeror or Offeror’s principle subcontractors, critical subcontractors, and JV/SLE team members in this solicitation.

The Offeror should provide a comparative analysis between the Offeror’s experience and the AIMD PWS for each area/subtask below. The Offeror should describe the degree of relevance that the experience has to the PWS requirements as implemented by the Offeror’s approach. The Offeror should also explain why the experience is considered relevant; specifically, the Offeror should describe and compare the type of work, scope of effort, location of effort, and the product/technology involved. Note that contract experience for any entity without a defined role and responsibility will be deemed not relevant. Also, show the depth of experience by comparing the activities/tasks performed in the past to those that would be required for the efforts identified in areas A through J of this section.

The Offeror should provide the contract number and title of the program, dates, and location under which the experience was gained for each example. Also, the Offeror should specifically identify the number of years performing the contract at time of proposal submittal and how recent the contract performance is (currently on-going or number of years from proposal submittal). In general, recent experience will be considered more relevant than older experience.

Where the Offeror lacks experience in the tasks below, describe the associated risks when considering the proposed technical approach and if needed, describe the risk mitigation plan to compensate for these risks. The experience that you provide should only relate to "Corporate" experience [which is the experience that an entity (the Offeror, the Offeror’s principal subcontractors, critical subcontractors, and JV/SLE team members) has gained through contracted work vice the experience of its personnel].

The experience examples shall be specific to the requirements of the Performance Work Statement (PWS) for this Aircraft Intermediate-Level Maintenance Department (Attachment (1)). This experience should include, but is not limited to, I-level maintenance on the following types of equipment, or management of the following requirements:

a. Airframes

b. Avionics and/or Electrical Systems Precision Measurement Equipment (PME)

c. Aviation Life Support System (ALSS)

d. Support Equipment (SE)

e. I-Level Supply Support

f. Quality Assurance

g. Technical Library

h. Non-Destructive Inspection

i. Calibration Management

j. Hazardous Material and Hazardous Waste Management

5.0 VOLUME 5: PRICE PROPOSAL

5.1 Volume Content:

This Volume shall contain the information requested below and shall include a copy of Section B with the Contract Line Item (CLIN) and Sub-CLIN Unit Prices and for evaluation purposes, the Total Prices filled in (Supplies and/or Services and Prices and/or Costs) using the estimated quantities value in the solicitation and the instructions below. If applicable, Offeror's labor classifications should cross-reference to Department of Labor (DOL) wage determination classifications as much as possible. In addition, the Offeror shall provide a percentage breakdown of the Offeror’s indirect costs and burdens added to the Government estimates for any and all Cost Reimbursable CLINs in section B. Section B prices shall be provided separately in one digital data copy in MS Office 2007 Excel format on CD-ROM media. Within all Excel spreadsheets, the Offeror shall use formulas and functions to the maximum extent possible and avoid using output type “value only” cells. If links are utilized, supply those referenced files. Spreadsheets shall not be protected.

All price and price supporting information shall be contained in section B and the price proposal. No price or pricing information shall be included in any other technical volume including cover letters. Offerors are responsible for submitting sufficient information to enable the Government to fully evaluate their price proposal.

5.2 Ground Rules and Assumptions:

As this is a competitive acquisition with adequate price competition anticipated, any price documentation requested shall not be certified cost or pricing data in accordance with FAR 15.406-2. However, in the event that adequate price competition does not exist after receipt of proposals, the Government reserves the right to request additional cost or pricing data as necessary from both the Offeror and subcontractors and may conduct negotiations with the Offeror, pursuant to FAR Part 15.403-4, in order to ensure a reasonable and realistic price. Further, the Offeror may be required to provide a Certificate of Current Cost or Pricing Data prior to award, pursuant to FAR 15.406-2. Offeror shall acknowledge the requirement to provide additional cost or pricing information and certify the data prior to award if/when requested by the Government.

The cost of general purpose items required to conduct normal business operations will not be considered allowable Other Direct Charges. The following types of general purpose costs required to conduct normal business operations are not directly reimbursable: the cost and associated costs for telephones and telephone charges (except for project-related telephone charges for performance of this contract which, per contractor's…