N00421-12-R-0013_Amendment_1.doc

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 4005

The contract type COST has been deleted.

Lot

Data in support of CLIN 4001 IAW Paragraph 6 of the PBSOW. Not Separately Priced.

FOB: Destination

ESTIMATED COST

SECTION E - INSPECTION AND ACCEPTANCE

The following have been deleted:

SECTION G - CONTRACT ADMINISTRATION DATA

SECTION K - REPRESENTATIONS, CERTIFICATIONS AND OTHER STATEMENTS OF OFFERORS

The following were previously included by reference and are now included by full text:

252.247-7022

REPRESENTATION OF EXTENT OF TRANSPORTATION OF SUPPLIES BY SEA (AUG 1992)

(a) The Offeror shall indicate by checking the appropriate blank in paragraph (b) of this provision whether transportation of supplies by sea is anticipated under the resultant contract. The term "supplies" is defined in the Transportation of Supplies by Sea clause of this solicitation.

(b) Representation. The Offeror represents that it--

____ Does anticipate that supplies will be transported by sea in the performance of any contract or subcontract resulting from this solicitation.

____ Does not anticipate that supplies will be transported by sea in the performance of any contract or subcontract resulting from this solicitation.

(c) Any contract resulting from this solicitation will include the Transportation of Supplies by Sea clause. If the Offeror represents that it will not use ocean transportation, the resulting contract will also include the Defense FAR Supplement clause at 252.247-7024, Notification of Transportation of Supplies by Sea.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L:

L –1 CONTENT OF PROPOSALS (SUPPLIES OR SERVICES)

PART A GENERAL INSTRUCTIONS

1.0 GENERAL

1.1 This contract is anticipated to be awarded based upon full and open competition. The North American Industry Classification Code System (NAICS) designation for this requirement is 488190 with a small business size standard of $30,000,000 and a small business subcontracting goal of 9%.

1.2 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 the Price/Cost volume, no cost or pricing information should appear in any volume. Alternate proposals are not acceptable.

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

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

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

1.6 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. In the event subcontractors are proposed, ensure your price proposal includes the information required by FAR 15.404-3(b).

1.7 Place of Performance. The places of performance for this contract are NTWL Patuxent River, MD and NTWP Pt Mugu, CA and China Lake, CA .

1.8 The incumbent is: Wyle Laboratories, Inc., 7800 Highway 20 West, PO Box 077777, Huntsville, AL 35806-2049. Cage Code 2B360

1.9 Questions: Offerors may submit questions requesting clarification of solicitation requirements by emailing the contract specialist at benjamin.washburn@navy.mil. All questions must be received within 14 calendar days of the date this solicitation is issued.

2.0 PROPOSAL FORMAT

2.1

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.

2.2

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

2.3 The Offeror must present proposal information in a manner that facilitates a one-to-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 subparagraphs. 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 Offeror’s proposal.

3.0 PROPOSAL CONTENT AND VOLUMES

3.1

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.

3.2

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.

2 additional hard copies;

1 electronic CD ROM copy

4 additional hard copies;

1 electronic CD ROM copy

3 additional hard copies;

3 additional hard copies;

3 additional hard copies;

1 electronic CD ROM copy

Annex 1

2 additional hard copies;

1 electronic CD ROM copy

Annex 2

2 additional hard copies;

1 electronic CD ROM copy

Annex 3

2 additional hard copies;

3.3 Each volume shall use tabs and dividers and 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)

3.4

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)

Note: This column shall address all paragraphs in Sections xx and xy of the Performance Specification

Volume 2 Technical

Volume 2 Technical

4.0 PROPOSAL SUBMISSION:

4.1

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 copies of Volume (3) Past Performance information in paragraphs 3.1 and 3.2 and Volume I, Executive Summary “Offeror’s Summary Table”, 1.0 (ii) two weeks prior to the submission date/time specified in Block 9 of Standard Form 33 of the RFP.

4.2

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

Attn: Mr. Benjamin Washburn/Mr. Daniel L. Chambers

Code 2.5.1.7

21983 Bundy Road, Bldg. 441 Unit 7

Patuxent River, MD 20670-1163

Solicitation Number: N00421-12-R-0013 Hand carried proposals may be delivered to the address above, attention Mr. Daniel L. Chambers, PCO and/or Mr. Benjamin M. Washburn, Contract Specialist.

IMPORTANT NOTICE: All packages entering the Consolidated Mail Facility onboard the Naval Air Warfare Center Aircraft Division are being scanned. If the contents of the box/package contains electronic components or media, or otherwise should not be scanned because of potential damage to the contents, the sender/vendor shall mark the box/package with a “DO NOT SCAN” sticker.

5.0 PROPOSAL PACKAGING:

5.1

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.

5.2

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 TECHNICAL LIBRARY/DATA

(1) Technical Library

A Technical Library of information directly related to the requirements of this contract is available to all bidders. The library is located at Patuxent River, MD. The POC is Ms. Lisa Rice (301-342-6764) email lisa.rice@navy.mil. All visit requests and data requests will be coordinated through the site Point of Contacts.

8.0 SOLICITATION CHANGES

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

http://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 5 is not being submitted as part of the proposal.

vi. Corporate Systems Status Table: The Offeror shall complete the table below showing the current/latest status and or determination regarding its business systems. If any item is not applicable, so state and explain why. If any item has been determined to be unapproved/inadequate outline the potential impact on contract execution, mitigation plan, and correction plan. Submit relevant DCAA/DCMA reports, audits, and determinations in Annex 2.

vii. Guarantee the length of proposal validity (for at least 180 days) after proposal submission).

viii. Written consent from principal subcontractors and critical team members that will allow the Government to coordinate potential past performance and/or cost/price issues with the offeror.

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:

Workforce

Understanding of the Work

Management Plan

2.1 Workforce. The workforce identified in Table 1 represents the Government’s best estimate for proposal purposes of the workforce necessary to successfully execute the mission requirements of the Performance-Based Statement of Work. If a contractor’s technical approach requires additional management, supervisory, or administrative personnel, include those personnel and their recommended qualifications in all relevant sections of the proposal in addition to the Government’s estimated requirements.

2.1.1 Workforce Qualifications Spreadsheet. The offeror shall complete the attached Workforce Qualifications spreadsheet (Attachment P-1) for each current, contingent, and prospective hire employee proposed under this effort. All contingent hires shall have a letter of intent submitted under the Cost Volume. The letter of intent is a separate written agreement signed by the potential key employee(s) to work for the offeror effective at contract award. Subcontractors and team members’ information should be included in the prime contractor’s submission of this document.

The following definitions apply:

- A “contingent hire” is an individual who has committed, under a signed letter of intent, to being employed by the Offeror if the Offeror is awarded the contract.

- A “prospective hire” is an individual that the Offeror has committed to hiring if the Offeror is awarded the contract whose identity may not be known until after contract award.

2.1.2 Labor Category Information. The offeror shall propose the labor category titles, functional responsibilities, and minimum qualifications outlined in Section 13.0 of the PBSOW. The labor category title shall be consistent throughout the proposal. Functional responsibilities shall include the principal duties to be performed under that labor category on the proposed order. The labor qualification information proposed will be incorporated by reference into the resulting contract, thereby becoming the standards for use during performance of the effort.

2.1.3 Key Personnel Resumes. 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 for key personnel:

2.1.3.1 For proposed key personnel provide a resume of the work assignments, training, etc., that demonstrates the experience and specialized qualifications of each person proposed. Resumes shall contain, at a minimum, the following information:

· Employee name

· Years of employment/experience in chronological order including narrative description of duties and responsibilities

· Current position, title and employer

· Educational history (if applicable)

· Institution name, degree or certification earned, and year for all degrees or certifications earned (if applicable)

· Current level of security clearance and status (final, interim, or pending) (if applicable)

2.1.3.2 When applicable, the Government may check educational background to verify degrees or certifications received.

2.1.4 Workforce Hour Matrix. (Attachment P-2) The offeror shall provide the following data in the proposal:

2.1.4.1 The offeror shall provide a breakdown of hours for each individual labor category required for the base and each option period of performance. The offeror must submit a labor category breakdown that covers the completion of the tasks in the Performance Work Statement (PBSOW) in Section C of the solicitation in accordance with the format in the Workforce Hour Matrix (Attachment P-2). Subcontractors and team members’ information shall be included under the prime contractor’s submission. Rationale for the proposed labor categories and hours, and mix of personnel shall be provided in a narrative.

2.2 Understanding of the Work.

2.2.1 Performance Work Statement Approach. Provide a written narrative of the offeror’s proposed understanding and capability to perform the requirements of the PBSOW paragraph 2.0 and paragraph 5.0 inclusive of all sub-paragraphs. The narrative shall include, but is not limited to, the elements set forth below:

2.2.1.1 Provide a detailed description of the approach including a detailed step-by-step procedure and methodology which would be used in accomplishing each task.

2.2.1.2 Identify reference documents that would be utilized to perform the PBSOW tasking (paragraph 3.0).

2.2.1.3 Provide a product outline describing what would be the expected deliverable(s) as a result of the tasking, paragraph 6.0 and Exhibits A, B and C .

2.2.1.4 Identify any areas that may impact successful performance.

2.2.1.5 Provide a description of possible areas to be investigated in researching each task.

2.2.1.6 Provide an implementation plan that includes:

2.2.1.6.1 Manpower utilization to maintain an optimum level of support.

2.2.1.6.2 Quality assurance plan to monitor performance based metrics.

2.3 Management Plan.

2.3.1. Offerors shall address in sufficient detail the following:

(a) Adequacy of corporate management and resources to support the technical requirements of the solicitation and ability to function as a viable and productive provider of contracted services to the Government;

(b) Proposed management roles of the Offeror’s proposed workforce for this requirement;

(c) Proposed lines of responsibility, authority, and communication through which the tasks will be managed;

(d) Procedures to be taken to ensure quality and cost control;

(e) Processes for managing the requirement from start to finish, including the role of program manager in product/process quality and how these functions are accommodated in the acquisition and overhead structures;

(f) Plan for early identification and resolution of problems; and

(g) Identification of potential performance risks and proposed risk mitigation strategies.

2.3.2. Usage of Teaming, Personnel, and Subcontractors. Offerors shall present in sufficient detail the following:

(a) Subcontract Management detailing how each subcontractor will be managed to ensure cohesive integration into the overall management approach;

(b) Description of the integration of the team members into the overall management approach in the following areas and how the Offeror will leverage their strengths to increase value to the Government through technical leadership, quality assurance, and process improvement;

(c) How and why selected subcontractor(s) were chosen, which knowledge and skills they will be acquiring through each subcontract, the level of subcontract effort expected; and

(d) How the Offeror will maintain control during the performance of work.

2.3.3. Qualification/Recruitment/Retention. Offerors shall present in sufficient detail the following:

(a) Qualification/recruitment/retention procedures that would provide workforce improvements and upgrade the skills of highly trained and motivated personnel;

(b) Description of their process for qualifying personnel to perform PBWS tasks;

(c) Explanation of approaches for maintaining technical competence to perform the tasks in the PBWS; and

(d) Employee retention plan.

2.3.4. Transition Plan. The services under this solicitation are vital to the Government and must be continued without interruption. The Offeror is required to submit a written narrative delineating a transition plan that ensures a smooth workplace changeover from an incumbent with no loss of service and minimal loss of corporate knowledge. The plan should take into consideration the following elements as well as any additional elements deemed necessary by the Offeror:

(a) Work Turnover

(b) Quality Assurance

(c) Training

(d) Risk Mitigation strategies

(e) Security Requirement to include OPSEC, facility clearances, and base access

(f) Data Transfer

2.3.5 Flight and Ground Operations Program. The offeror shall provide a Flight and Ground Operations Manual IAW with the NAVAIRINST 3710.1 series, Contractors Flight and Ground Operations, and PBSOW paragraph 6.4, as Annex 3. In addition, this paragraph of the Technical Volume provide a plan to achieve GFR certification within 30 days of award.

2.3.6. Small Business Utilization.

2.3.6.1 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 JV, 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. Offerors should demonstrate that they will provide a minimum Small Business Participation goal of 9% of total contract value. In describing its SB Utilization 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, 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 Central Contractor Registration, as a minimum provide evidence of self-certification as a SB Concern. Where possible, provide documentation regarding enforceable commitments to utilize each SB Concern;

Identify what processes have been implemented to correct past inabilities to meet proposed goals and any validated improvements;

· 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. Goals of subcontractors must be listed separately;

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

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.

2.3.6.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 1, unless there is an already approved comprehensive SB Plan. Complete Blocks 2, 3, and the proposed goal percentages in Block 4a of the Small Business Plan Subcontracting Review Checklist at Attachment P-7.. The Subcontracting Plan of the successful Offeror(s) will be reviewed and approved by the PCO prior to contract award. Note that Clause 52.244-2, Subcontracts, as incorporated requires PCO consent to subcontract for all subcontracts regardless of the approval status of the Offeror’s Purchasing System. 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.

3.0 VOLUME 3: PAST PERFORMANCE

3.1 General

The Offeror shall identify on the Past Performance Matrix any contracts performed within five years of the RFP release date which contains efforts similar to those performed by the Offeror, the Offeror’s principal subcontractors, and the Offeror’s critical team members in solicitation. E.g., tasks, complexity, contract type, contract dollar value, etc. Offerors shall not reference an Indefinite Delivery/Indefinite Quantity contract without referencing the appropriate task orders containing the effort similar in nature to this requirement. Commercial contracts may be included. List the contracts in order of relevancy from the most relevant to the least relevant using the definition of “relevancy” in Section M. In general, recent performance will be considered more relevant than older performance. When possible, the Past Performance Matrix 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. If less than the five past performance references are available for team members (i.e., entities that make up a JV or any other partnership or teaming arrangement), each member should submit the five references individually in addition to their team member 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, as well as demonstrated systemic improvements with respect to the solicitation requirements. For each past performance problem identified, describe the status of the demonstrated systemic improvement efforts, and, where applicable, demonstrate the impact that the demonstrated systemic improvement effort had on resolving the problem such that it would not recur.

The Past Performance Information Reporting System (PPIRS) will be used to evaluate Past Performance. For contracts that have CPARS Reports or similar 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 P-4) 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 P-5) 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 concurrently with the Government’s receipt of the Offeror’s Past Performance information submitted as per paragraph 3.1 and 3.2 The Offeror shall include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to Benjamin Washburn at Email benjamin.washburn@navy.mil , thereby allowing the customer approximately two weeks to complete their response. 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 may send any other questionnaires as necessary.

The Offeror shall provide written consent from their principal 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 whom 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. It is incumbent upon the Offeror to explain the relevancy of the data provided by the Offeror. 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:

Past Performance Matrix

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- See definition in Section M. Only list efforts performed within five years of the date of RFP release.

4 - Relevancy – Provide a concise assessment of the degree of relevancy (using the relevancy ratings below) 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. 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. Also, provide the Offeror’s assessment of the contract’s relevancy in terms of one of the following ratings: Relevant (R), or Not Relevant (N) as defined below and in Section M

Past Performance Relevancy Ratings

(b) Past Performance Information-The Offeror shall provide a brief description of performance in delivering quality services 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.

(c) Demonstrated Systemic Improvement Information - Identify those demonstrated 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.

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

(e) Small Business Utilization

The Large Business Offeror shall provide copies of the final or most recent SF 294s/Individual Subcontracting Reports (ISRs) for the three most relevant Government contracts provided in the Past Performance section of their proposal. The Small Business Offeror may provide this information in a format substantially the same as the ISR. If the Offeror is a participant in the DoD Comprehensive Subcontracting Test Program, they shall provide copies of DCMA's most recent Review of Contractor's Comprehensive Subcontracting Program (DCMA Form 640), and three final or most recent SF 295s/Summary Subcontracting Reports (SSRs), and explain how the results shown in these documents demonstrate the realism of their proposed SB Utilization Strategy. If applicable, note whether the contract met or exceeded small business, small disadvantaged business, HUBZone small business, veteran-owned small business, service-disabled veteran-owned small business, and women-owned small business utilization and subcontracting goals. All Offerors providing this information must explain how this information translates to reasonableness of their proposed SB Utilization Strategy goals in the Technical Volume.

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. Offerors are advised that they should contact the points of contact prior to sending a questionnaire or CPARS update to ensure they are current and willing to accommodate the request. Failure to ensure that points of contact are current may prevent the Government from obtaining sufficient information to fully assess the Offeror’s performance, which could result in an “Unknown Confidence (Neutral)” or less than “Substantial Confidence” Performance Confidence Assessment Rating as defined in Section M of this solicitation.

Offeror’s Name (Prime, Principal Sub, Critical Team Member, or Team Member)

1. Contract #

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

2. Questionnaire # __ Sent?

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

Point of Contact Information:

Name;

Phone Number, Fax Number;

E-mail address

2. Prime

2. Questionnaire #1: - Sent 2/23/12

3. N/A

Al (PM)

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

1. CPARS: No

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

3. N/A Sue (PCO)

333-333-3333 fax 222-222-2222

Sue@RTP

1. CPARS: No

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

3. N/A Joe (ACO)

111-111-1111 fax 888-888-8888

Joe@ RYP

2. Sub

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

3. N/A Sue (PCO)

333-333-3333 fax 222-222-2222

Sue@AB

2. Prime

2. Questionnaire: - Not Sent

3. Agreement: Yes Sue (PCO)

333-333-3333 fax 222-222-2222

Sue@NNB

4.0 VOLUME 4: PRICE/COST PROPOSAL

4.1 Volume Content:

(a) 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 using the estimated quantities value in the solicitation and the instructions below. If applicable, the 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 2003 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. Offerors shall submit their cost and/or pricing information using the CLIN Breakout Spreadsheet (Attachment P-6). The Offeror shall submit a fully completed CLIN Breakout Spreadsheet.

(b) All price/cost and price/cost supporting information shall be contained in Section B and the price/cost 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/cost proposal.

4.2 Ground Rules and Assumptions:

(a) As this is a competitive acquisition with adequate price competition anticipated, any price/cost documentation requested shall not be certified cost or pricing data in accordance with FAR 15.403-1. 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 15.403-4, in order to ensure a reasonable and realistic price/cost. 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. The Offeror acknowledges the requirement to provide additional cost or pricing information and certify the data prior to award if/when requested by the Government.

(b) 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 the Contractor's DCAA-approved accounting system, may be directly reimbursed under communication expenses), modems, typewriters, reproduction machines, word processing equipment, personal computers, computer software, Internet access charges, facsimile machines, commercial carrier charges, pagers, and other general purpose office equipment and office supplies.

(c) The Offeror shall provide sufficient information to support its price/cost as well as an explanation of all ground rules and assumptions that affect the price/cost estimates. Any apparent imbalances in the pricing, high or low proposed prices/costs as compared to historical data, or any other anomalies should be fully explained. Topics to be addressed include, but are not limited to, investments, programmatic variables (e.g., inflation/escalation, location, make/buy decisions, prime/subcontractor relationships, and business base concerns), etc.

4.3 Price/Cost Information:

(a) Reasonableness and Consistency between the Technical and Price/Cost Volumes. Demonstrate that the unit prices and the total proposed price/cost are reasonable, realistic, and commensurate with the work required by the solicitation and the technical and management approaches identified in the Technical Volume of the proposal. Show traceability with the CLINS, SubCLINs, the PWS, proposed effort, proposed manning levels, and the prices/costs. Refer to specific sections in the Technical Volume as needed to illustrate the consistency between the Price/Cost Volume and the Technical Volume. The Offeror shall explain any inconsistency between promised performance and price/cost, as well as any appearance of unbalanced pricing, in the proposal.

(b) The Government is not soliciting any investments. However, in order for the Government to properly assess a proposed price/cost that appears low due to a corporate decision to absorb costs, e.g., lower than usual burdens or rates, the Offeror shall fully identify and explain any such investments.

(c) Direct/Indirect Rates: The Offeror shall use and submit Forward Pricing Rate Agreements (FPRAs), Collective Bargaining Agreements (CBAs), and Area Wage Determinations (AWDs) if applicable. The Offeror shall identify whether the labor rates proposed are FPRAs, CBAs, AWDs, ACO/DCAA recommended rates, or Offeror proposed rates. If applicable, the Offeror shall propose in compliance with the current hourly rate set forth in the Department of Labor Wage Determination. The Offeror shall provide Defense Contract Audit Agency (DCAA) Information/Payroll Verification information as follows. A DCAA point of contact, with a current e-mail address, must be provided for the prime and each subcontractor. The Offeror and proposed subcontractors shall provide the most current DCAA Provisional Billing Rate Approval Letter, DCAA Final Billing Rate Approval Letter, and/or DCAA Forward Pricing Rate Agreement recommendation, payroll verification for currently employed proposed personnel, and any other information necessary to substantiate the rates proposed. Payroll verification shall consist of a form containing the title, direct labor rate, and a signed certification by an authorized representative of the company that the information contained in the form is correct. If any of the rates utilized by the Offeror or any subcontractors differ from the DCAA information and/or payroll verification, a justification shall be provided for the difference. If DCAA has not reviewed the rate information for an Offeror or one of its subcontractors, the Offeror must submit a detailed justification of the proposed direct and indirect rates. The Offeror shall also provide documentation verifying that it has a DCAA approved Cost Accounting System or state that its Cost Accounting System has not been approved by DCAA. Prime contractors and all subcontractors shall provide the last three (3) years of actual indirect information. The proposed subcontractors are required to submit their DCAA information and payroll verification under their prime contractor. The Government may review perspective Offeror’s labor category to the average labor rate from industry.

(d) The Offeror shall provide a schedule which contains the proposed burden rates by year for material, direct labor overhead, General and Administrative expense, fee/profit, and any other applicable burden applied to direct cost elements. The Offeror shall also state the number of hours used in determining an employee work year.

(e) 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 Contractor indirect costs and burdens added to the Government estimates for the Cost Reimbursable CLINs in Section B.

(f) Regardless of the type of CLINs (e.g., CPFF, CPIF, CPAF or FFP) under the solicitation, the Offeror…