N61340-11-R-0039 Amendment 0004.doc

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

CONTENT OF PROPOSAL

L-1

CONTENT OF PROPOSALS (SERVICES) (FEB 2011)

PART A GENERAL INSTRUCTIONS

1.0 GENERAL

Offerors are required to submit sufficient information concerning the following to enable Government personnel to fully ascertain capabilities of the offeror to perform the requirements. The proposal must be sufficient in detail and scope to permit evaluation and provide the evaluators a clear understanding of the offeror’s approach, expertise, experience and capability as required by the solicitation. All proposals must clearly and convincingly demonstrate that the offeror has a thorough understanding of the requirements, associated risks and is able, willing and competent to devote the resources necessary to meet the requirements and has valid and practical solutions for all requirements and potential risk areas. Respond to all requirements of the solicitation. Do not alter or rearrange the solicitation. The burden of proof for all the evaluation factors identified in this solicitation rests with the offeror. The offerors are 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 volume, no cost or pricing information should appear in any other volume. Alternate proposals are not acceptable.

In presenting material in the proposal, the offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. It is the responsibility of the offeror to present enough information to allow the various work efforts, support, and management approaches, as well as price, to be meaningfully evaluated without discussions. Though the Government reserves the right to hold discussions, award may be based upon initial offers. Statements that the prospective offeror understands, can or will comply with the specifications, and paraphrasing the requirements or parts thereof without supporting information are considered inadequate and may render a rating of unsatisfactory. For the purpose of this acquisition, 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 participation of Principal Subcontractors, Team Members, or Critical Team Members.

The offeror must include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. Failure to clearly and positively address a specific factor 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.

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

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

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

The offeror must present its 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

Each volume of the proposal shall be submitted as one original and additional copies as specified in the table below. Submission of all volumes of the Original proposal to the address provided in section 4.0. will determine timeliness of receipt. Page limitations for each volume if any, are also specified in the table below as follows (title and table of contents pages do not count towards page limit). Proposal pages beyond a specified maximum limit, if any, will not be reviewed as part of the evaluation.

AND WAIVERS

*Subparagraph iii of Part B, Volume I, “Executive Summary,” does not count toward Written Page Limit.

**Manning Charts (Attachment 12), Lists of Figures/Tables/Illustrations and Acronyms, and Key Personnel Resumes do not count toward Written Page Limit.

Each volume must 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. 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:

Clearly mark all packages with the solicitation number. The submission date for all Volumes shall be no later than 12:00 pm Eastern Daylight Time (EDT), 03 May 2011 . However, it is requested that the Volume 3, Past Performance information should be submitted two (2) weeks after the RFP release date to coincide with past performance questionnaires being sent out as identified in Part B, paragraph 3.0.

Proposals shall be submitted via United States Postal Service or through a commercial carrier to the address provided below. Proposals are not to be submitted by facsimile or electronically via email.

Naval Air Warfare Center Training Systems Division (NAWCTSD)

John J. Warren, AIR-2.5.3.3.2 12350 Research Parkway

Orlando, FL 32826-3275

Primary POC: John J. Warren, Contract Specialist, AIR-2.5.3.3.2, Phone: 407-380-4556

Alternate POC: Kathleen Dougherty, Contracting Officer, AIR-2.5.3.3.2, Phone: 407-380-8189

The outside shipping container shall be marked with the Request for Proposal number N61340-11-R-0039.

IMPORTANT NOTICE: All packages entering the Consolidated Mail Facility onboard the Naval Air Warfare Center Training Systems 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.

Submission of telegraphic, facsimile, or electronic commerce offers is not authorized for this solicitation. Proposals shall be submitted either by mail or hand carried as specified below. If the Proposal or Final Proposal Revision (if and when a Final Proposal Revision is requested) is hand carried, the offeror shall notify the cognizant Contract Specialist at least one (1) business day prior to the closing date/time specified in Section L, Part A, paragraph 4.0 or as specified in the amendment/letter requesting Final Proposal Revisions. Offerors will be required to supply the Contract Specialist (or alternate POC listed in Section L, Part A, paragraph 4.0) with the name, citizenship, and telephone number of all the individuals that will be present to hand deliver the proposal in order to prepare the necessary Visit Request(s) prior to arrival. Hand deliveries shall be made to the following address: Naval Air Warfare Center Training Systems Division (NAWCTSD), DeFlorez Building, 12350 Research Parkway, Orlando, FL 32826. NAWCTSD is a secure facility and all visitors will be stopped by security personnel upon entrance. Only authorized visitors will be permitted to enter. Upon admittance, offerors are required to report to the lobby of the DeFlorez Building and contact the cognizant Contract Specialist to accept the proposal submission (a telephone is available in the lobby to place calls within the building). Please note center security personnel are not authorized to accept proposals. Do NOT use the Bid Box in or near the Business Information Center to deposit hand carried proposals. The Contract Specialist will provide the offeror with documentation reflecting the date and time the proposal submission was received for the offeror’s record.

5.0 SOLICITATION QUESTIONS

The Contract Specialist is the sole point of contact for this acquisition. Address any questions, concerns, or requests for clarification you may have, in writing, to:

NAWCTSD

John J. Warren, AIR-2.5.3.3.2

12350 Research Parkway

Orlando, FL 32826-3275

Email: john.j.warren@navy.mil Questions regarding this solicitation shall be submitted in writing utilizing RFP Attachment 8. It is requested that each question reference the applicable document, paragraph, and page. Questions containing proprietary information shall not be submitted because for all questions answered by the Government, answers will be provided to all potential offerors via an amendment to the solicitation. All questions must be submitted no later than 2:00 PM EST, 15 days prior to the deadline for proposal submission. Written questions may be submitted by electronic mail and addressed to the point of contact identified above.

The Government reserves the right not to respond to any questions received concerning this solicitation after the question receipt date above. Accordingly, Offerors are encouraged to carefully review all solicitation requirements and submit questions to the Government early in the proposal cycle. It is not anticipated that the closing date for receipt of offers will be extended.

6.0 PRE-PROPOSAL CONFERENCE/SITE VISIT

(a) A Pre-Proposal Conference/Site Visit will be conducted as follows:

Site POC/Address/

Pre-Proposal Conference/Site Visit

Location:

email/Phone/Fax:

Date/Time/Bldg

Patuxent River, MD Byron Gundacker

06 April 2011/0900 a.m.

Hanger 301, Suite 203W

Hanger 301, Suite 203W

Patuxent River, MD 20670-1612 byron.gundaker@navy.mil

(301) 342-0644 (phone)

(301) 342-3385 (fax)

(b) All prospective offerors are urged to attend the Pre-Proposal Conference/Site Visit. However, each company is restricted to three (3) attendees at the Pre-Proposal Conference/Site Visit. Exact building/room number location for the Pre-Proposal Conference/Site Visit (if changed from above) will be provided by the POC in paragraph (a) above upon receipt of visitor requests (see paragraph (c) below for Visit Request information). Subcontractor requests are to be requested through the Prime Contractor and Subcontractor attendees count toward the limit of three attendees.

(c) In order to attend the Pre-Proposal Conference/Site Visit, each offeror shall submit visit requests for those company officials who will attend. Send electronic Visit Requests for the Pre-Proposal Conference/Site Visit a minimum of five (5) business days prior to the scheduled visit to the POC listed in paragraph 6.0(a) above.

(d) Questions generated at the Pre-Proposal Conference/Site Visit shall be submitted in writing IAW paragraph 5.0 above. At no time will the Government answer questions regarding the solicitation to a single potential offeror without providing the answer to all potential offerors. The Government will not engage in “side-bar” question and answer sessions with any individual or potential offeror. Questions submitted formerly (by the date noted in paragraph 5.0) will be answered and distributed to offerors through RFP amendment.

(e) Failure of a prospective offeror to attend the conference or to submit any questions will be construed to mean that the offeror fully understands all requirements of the solicitation. Prospective offerors are advised that the conference will be held solely for the purpose of explaining the specifications and terms and conditions of this solicitation. The Pre-Proposal Conference/Site Visit will be the only opportunity afforded to any prospective offeror to visit the site. All prospective offerors are advised that this solicitation will remain unchanged at the conclusion of the conference, unless this solicitation is amended in writing. If an amendment is issued, normal procedures relating to the acknowledgement and receipt of any such amendment shall be applicable. In no event will failure to attend the conference constitute grounds for a claim after award of the contract.

(f) The Government is not responsible for, nor will the Government pay, any portion of the costs associated with attendance at the respective site visit by prospective contractor personnel.

7.0 PROPOSAL PACKAGING:

The offerors shall package the proposal volumes in cartons or equivalent packaging containers in the most efficient manner possible grouping like volumes to the maximum extent possible. Also each carton shall be single person portable. However, the Master Set, as described below, shall be packaged separately and marked as the Master Set. 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”. The Master Set shall include all original proposal volumes including the original/signed documents submitted as part of Volume 1 Executive Summary.

8.0 CLASSIFIED DATA

All proposals must be UNCLASSIFIED.

9.0 SOLICITATION CHANGES

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

http://nawctsd.navair.navy.mil/EBusiness/BusOps/Index.cfm 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 contained in Section K and 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.

vi.

Government Agency Information. Provide the points of contact, including mailing address, telephone number, email address, facility code/UIC, for the offeror’s Defense Contract Management Agency (DCMA), Defense Contract Audit Agency (DCAA), and Government Pay offices. This information shall also be included for each subcontractor proposed.

vii.

Period of Acceptance. The offeror shall include an acceptance period stating how long the offeror agrees to honor the proposed prices. This period shall be, at a minimum, 120 calendar days from the date specified for receipt of offers.

viii.

Completion of Clause 5252.201-9502 CONTRACTOR’S AUTHORIZED CONTRACT COORDINATOR AND TECHNICAL LIAISON (NAVAIR)(OCT 2005) found in Section G.

2.0 VOLUME 2 - TECHNICAL/MANAGEMENT

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/managerial evaluation. The offeror shall address the following elements in the proposal:

The Technical/Management volume of the proposal shall include a title page, table of contents, list of figures/tables/illustrations, and a list of acronyms (if not used in the SOW).

2.1 Elements

2.1.1 Understanding of the SOW.

The offeror shall provide a clear, concise overview that demonstrates it has a sound understanding of the SOW’s requirements and a sound understanding of all the governing documents/instructions/directives/requirements and their applications. The offeror shall present its understanding of :

- Work center requirements

- Safety requirements

- Quality Control/Assurance requirements

- Inventory requirements

- Security requirements (i.e., security clearances/CAC-CVS/ IT/OPSEC)

- Reports and CDRLs requirements (content, applicable period, periodicity, and recipient(s))

2.1.2 Manning/Staffing.

2.1.2.1 Manning/Staffing Level. In its proposal, the offeror shall fully complete and provide a separate On-Site Manning Chart (RFP Section J, Attachment 12) for the Mobilization Phase, LOT I from Contract Support Date (CSD) to the end of LOT I, and all subsequent LOTS. For LOTS with identical data, one chart may be submitted (i.e., the one On-Site Manning Chart would apply for each LOT II-V). All data blocks on the On-site Manning Charts shall be completed. Any abbreviations shall be identified. The offeror shall describe its manning approach and rational. The offeror shall describe how premium time requirements will be met.

2.1.2.2 Key Personnel Resumes. The offeror shall identify and include in its proposal resumes for each person the offeror will employ to fill each specific key personnel position identified in the SOW. The offeror shall include written letters of intent for employment from each proposed key personnel individual.

2.1.2.3 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 SOW 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.1.2.4 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 SOW. 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.1.3 Corporate On-site and Subcontractor Structure/Plan/Authority. The offeror’s proposal shall clearly delineate the offeror’s corporate support structure, organization, and define lines and level of authority in support of this contract effort (a flow chart may be used). The offeror’s proposal shall clearly identify the use and extent of subcontractors. The offeror shall specify the legal nature of any agreements/working relationships between the prime and a subcontractor, the degree of subcontractor effort compared to the prime, and delineation of how managerial/supervisory responsibilities and authority will apply to prime and subcontractor personnel. The offeror (prime) shall address how it will meet the requirements of this contract in the event of the loss of its subcontractor. If the prime uses a subcontractor, the offeror shall explain how and why it selected its subcontractor(s) and how the prime/subcontractor relationship will be managed to ensure cohesive integration into the overall management approach. The offeror shall specify how the lines or authority and communications between the Contractor (prime and subcontractors) and the site will optimize expedient responsiveness and cooperation. The proposal shall include the offeror’s understanding of how Government representatives (NAWCTSD, FRCMA-PAX) and offeror’s corporate communications and interface will functionally occur.

2.1.4 Recruitment and Retention. The offeror shall provide its plan/approach to retain experienced employees/subject matter experts and managers/supervisors to meet SOW 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 highly-skilled workforce personnel.

2.1.5 Mobilization and Transition Plans. The offeror shall provide Mobilization and Transition plans. The plans shall include a plan-of-action and milestones (POA&M) that includes all SOW requirements for each of the phases (i.e., key dates/events, training/certification, personnel resumes, reports/CDRLs, security clearances/CAC-CVS/ IT/OPSEC/NMCI account requirements, inventories, meetings, personnel on-site dates, start/end dates, and cognizant action point-of-contact).

2.1.6 Risk Mitigation Strategy. 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 SOW requirements will be fulfilled.

3.0 VOLUME 3: PAST PERFORMANCE

3.1 General

The offeror shall identify contracts whose performance is within five years of this proposal submission date and contains efforts similar to those efforts, e.g., tasks, contract type, location, contract dollar value, etc., required by this solicitation for you, your principal subcontractors, and critical team members. 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, three 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 a joint venture/single legal entity (JV/SLE), the offeror should provide 5 past performance references for the JV/SLE. If less than 5 past performance references are available for the JV/SLE, each member of the JV/SLE should individually submit 5 references in addition to their JV/SLE references.

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

3.3 For contracts that have CPARs that are more than 6 months old, i.e., the completion date is more than 6 months before the due date for this Past Performance Volume; the offeror will forward a copy of the CPARs Update Questionnaire (Attachment 7A) to that contract customer’s Program Manager. For all contracts identified which do not have CPARs, the offeror will forward a copy of the Past Performance Questionnaire (Attachment 7B) to that contract customer’s PCO, Administrative Contracting Officer, Program Manager or other point of contact with knowledge and familiarity of the contract. 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 concurrent with the Government’s receipt of the offeror’s Past Performance information submitted as per paragraph 4.1 and 4.2 The offeror shall include instructions for the customers to send the completed questionnaires via e-mail to John J. Warren, at Email; john.j.warren@navy.mil or via fax number 407-380-8406. This submittal information is provided at the top of the questionnaires to facilitate the offeror’s effort in meeting these instructions.

3.4 Offerors 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 you as the Prime offeror. If Offerors do 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.

3.5 Offerors are reminded that the Government may use information other than that provided by the offerors 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 does not assume the duty to search for data to cure the problems it finds in the information provided by the Offeror. The burden of providing thorough and complete past performance information remains with the Offeror.

(a) Contract Data

Please complete the chart contained below for each Past Performance contract reference provided.

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

1 – Prime (P) or Sub (S): Indicate role of contractor for referenced contract effort. If the contractor listed in the chart acted in the Prime contractor role for the reference, indicate such with (P) after contract name in Line 1. If the contractor acted in the Subcontractor role, indicate such with (S) after contract name in Line 1. (A prime contractor means one that had the contract directly with the procuring agency. A subcontractor means any supplier, distributor, vendor or firm that furnishes supplies or services to or for a prime contractor or another subcontractor.)

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

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

4 - Relevancy – Concise assessment of the degree of relevancy the past performance for that contract has to the solicitation, identifying tasks and/or aspects of the effort undertaken on the contract that are relevant to the program. Also provide your assessment of the relevancy of the contract in terms of one of the following ratings: Somewhat Relevant (S), or Very Relevant (V).

(b) Relevancy

Offerors 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

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

3.6 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, Principle Sub, or Critical Team Member, JV/SLE, JV/SLE 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’s Name;

Phone Number, Fax Number and

E-mail address

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

2. Sub

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

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 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) Unit Prices and for evaluation purposes, the Total Prices filled in using the values in the solicitation. Offeror's labor classifications should cross-reference to Department of Labor (DOL) wage determination classifications as much as possible. Section B prices shall be provided separately in one (1) digital data copy in MS Office 2000 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.

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

4.2 Ground Rules and Assumptions:

As this is a competitive acquisition with adequate price competition anticipated, the price documentation requested is not considered cost or pricing data and shall not be certified in accordance with FAR 15.406-2. However, in the event that adequate price competition does not exist after receipt of proposals, the PCO will need to obtain cost or pricing data pursuant to FAR Part 15.

4.3 Price Information:

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

(b) Identify the proposed prices for each following contract line item numbers (CLINs) as specified in Section B of this solicitation; 0001, 1000, 2000, 3000, 4000, and 5000.

(c) The offeror shall propose in compliance with the current hourly rates set forth in the Department of Labor Wage Determination or CBA and rates shall not be escalated for adjustments under the Service Contract Act.

(d) Completion of DOL/CBA Wage Adjustment Baseline Form (Attachment 3).

5.0 VOLUME 5 - EXCEPTIONS, DEVIATIONS AND WAIVERS:

This volume must include a certification that it contains all exceptions, deviations, and waivers that the offeror takes from the provisions of the solicitation and its applicable documents. An exception is where an offeror states it will not comply with a requirement, usually involving contract terms and conditions. A deviation is where an offeror states it will not comply with a requirement but proposes an alternative to meet the intent of the requirement, usually involving a specification. A waiver is where an offeror requests authorization for the Government to accept an item, which will depart from specified requirements, but would nevertheless be considered suitable. Exceptions, deviations, and requests for waivers may cause proposals to be considered deficient and, thus, unawardable.

Provide a detailed description for each exception, deviation or request for waiver. Indicate your difficulty with the applicable requirement and your proposed solution. Specifically identify the portion of the solicitation and your proposal, which are affected. If there are no exceptions, deviations or waivers, provide a one page Volume 5 in the Executive Summary (Volume 1) stating so.

(End of Summary of Changes)