N68936-14-R-0001_Questions_ _Answers.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to answ er questions received.

1. CONTRACT ID CODE PAGE OF PAGES

U 1 21

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 05-Mar-2014

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N68936-14-R-0001

X 9B. DATED (SEE ITEM 11)

06-Feb-2014

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

05-Mar-2014

CODE

CDR NAWCWD CODE 254100D

ATTN: K. MCCLEAN

(760) 939-8638

429 E BOWEN RD - STOP 4015

CHINA LAKE CA 93555-6108

N68936 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N68936-14-R-0001

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been added by full text:

QUESTIONS AND ANSWERS

Question 1: Section L Part B 1.0 iii-vi- Please confirm that the contract data information contained in Section L Part B 1.0 iii-vi does not count against the page limitation for the executive summary. For instance, the signed Representations, Certifications, and Acknowledgements above the ORCA reference in Section K are 6 pages alone.

Answer 1: Section L Part B 1.0 iii (Signed SF33 or SF1449) and iv (Signed Representations, Certifications, and Acknowledgements or Online Representations and Certifications Application reference) only do not count against the page for the executive summary.

Question 2: Section L Part B 1.0 vii & Section L Part B 3.1- Are offerors to provide letters of consent as an attachment in both the Executive Summary and the Past Performance Volume? If contained in the past performance volume, please confirm such letters are not contained within the page limitation.

Answer 2: Yes letters are to be provided in both the Executive Summary and the Past Performance Volume as stated in Section L. These will not count against page count and referencing the same attachments in both volumes is acceptable.

Questions 3: Please clarify whether electronic files are required in MS Office 2003 format or in MS Office 2007 format.

Answer 3: All files shall be provided in MS Office 2003 format.

Question 4: Please provide guidance on the acceptable font and paper size/standards.

Answer 4: Reminder that no hard copies will be evaluated (except for past performance information from third parties, however, digital versions are preferred) Text Font: 10 pt Times New Roman Graphic/Table Font: 9 pt Arial or Arial Narrow Graphic/Table Title: 10 pt Times New Roman or Arial Max Paper Size-Text: 8-1/2” x 11” with 1 inch margins on all sides Max Paper Size-Graphic/Tables: 11” x 17” folded to 8-1/2” x 11” and counts as 1 page within the document

Question 5: Section Part B L 3.1- Is it correct that an IDIQ contract citation and a Task Order citation that is related to that IDIQ contract will make up 2 of the five citations or are they combined for 1 citation?

Answer 5: Since no work is performed on a basic IDIQ contract, the government suggests that offerors submit more specific information for a past performance reference. However, if only a basic IDIQ contract is cited, the work performed by the offeror on any and/or all of the task/delivery orders issued under the cited contract will be reviewed as one reference. If both a basic IDIQ and a task/deliver order issued under said IDIQ are cited than the task/delivery order will not be counted as a separate reference.

Question 6: Section L Part B 3.2- Is "Customer's Name" (column 3) the same as POC Name in Column 4 or is Column 3 referring to customer's organization name?

Answer 6: Column 3 is referring to the organization’s name, i.e. NAVAIR, NAWCWD, or Mission Engineering Department at NAWCWD.

Question 7: Should the SDP be tailored to the Sample Task or should it be generic?

Answer 7: Generic.

Question 8: Section L, Clauses Incorporated by Full Text, NAVAIR Clause 5252.239-9500.

Please confirm that this information is not required with the proposal, but is to be submitted upon contract award for task orders that require Offerors to engage in the software development of Software Intensive Systems (SIS).

Answer 8: This information is required as a part of the proposal and is to be included in Section

2.0 Technical and 3.0 Past Performance in accordance with NAVAIR Clause 5252.239-9500

Question 9: Section L Part B 4.1 Please clarify that a completed Section B is not required with the proposal.

Answer 9: Section B is only required for the sample task value and not the entire IDIQ value.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

L – [ 1 ] CONTENT OF PROPOSALS (OCT 2012) 31 December 2013

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 and associated risks. The Offeror must respond to all requirements of the solicitation and not alter or rearrange the solicitation. The Offeror is advised that the Government may incorporate any portions of 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.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization shall be emphasized during proposal preparation. The Offeror shall present sufficient 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, can comply with, or will comply with, the specifications, and paraphrasing the requirements or parts thereof without supporting information are considered inadequate by the Government, and may result in a rating of unacceptable. For the purpose of this solicitation, “relevancy” as it pertains to past performance is defined in Section M. Aspects of relevancy include the type of effort (e.g., development, production, repair), the type of requirement (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” as it pertains to past performance is defined in Section M; for this solicitation, performance is considered “recent” if it has been accomplished within 5 years of the Request For Proposal (RFP) release.

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 one of the entities that makes up a joint venture (JV) or any other partnership or teaming arrangement formed for the purpose of responding to this solicitation. “Critical team member” is defined as one of the entities of the Offeror that performs a critical function in the performance of the resulting contract, whether it is technical or financial, and/or that has an important role in any high- or medium-risk areas identified in the Offeror’s proposal.

Questions: Offerors may submit questions requesting clarification of solicitation requirements by emailing the contract specialist at kelley.mcclean@navy.mil and cc: dustin.barros@navy.mil . It is requested that all questions be received within 10 calendar days of the date this solicitation is issued.

2.0 PROPOSAL FORMAT

The Offeror will provide one complete copy of the proposal to the Procuring Contracting Officer (PCO) as electronic files fully compatible with Microsoft Office 2003 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.

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 the Offeror’s proposal.

3.0 PROPOSAL CONTENT AND VOLUMES

Each volume of the proposal shall be submitted as one original. The table below supersedes the copies requested in Block 9 of the Standard Form (SF) 33. 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 the page limit.

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.

Volume Number Volume Title Page Limit Copies Required

1 EXECUTIVE

SUMMARY

5 1 Digital*

2 TECHNICAL 25 1 Digital*

3 PAST PERFORMANCE 20 1 Digital*

4 PRICE/COST No page limit 1 Digital*

5 EXCEPTIONS,

DEVIATIONS,

2 1 Digital*

AND WAIVERS

*Digital Copies submitted as shown above in 2.0 Proposal Format. Offeror’s shall not submit hard copies.

Each volume shall contain the following information:

-Cover and title page (Does not count against page limit) -Title of proposal and proposal number as applicable -Offeror’s name, address, and POC -RFP number -Proposal volume/book number -Table of Contents (The table of contents must provide sufficient detail to enable easy location of important elements) (Does not count against page limit)

Acceptable font and paper size standards:

Text Font: 10 pt Times New Roman Graphic/Table Font: 9 pt Arial or Arial Narrow Graphic/Table Title: 10 pt Times New Roman or Arial Max Paper Size-Text: 8-1/2” x 11” with 1 inch margins on all sides Max Paper Size-Graphic/Tables: 11” x 17” folded to 8-1/2” x 11” and counts as 1 page within the document

4.0 PROPOSAL SUBMISSION:

Clearly mark all packages with the solicitation number. The submission date for all Volumes shall be no later than the date and time specified in Block 9 of the SF 33 of the RFP.

Offeror shall submit proposals (in CD-ROM form only) via United States Postal Service or through a commercial carrier using the address provided below.

Naval Air Systems Command Code: AIR-254100D (Kelley McClean) 429 E. Bowen Rd. Stop 4015 China Lake, CA 93555-6108 Solicitation Number: N68936-14-R-0001

Hand carried proposals (in CD-ROM form only) may be delivered to the address above, attention (PCO) and/or (Specialist).

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 Electronic Proposal volumes.

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 notice of any changes and additional information provided by the Government for the solicitation, please go to www.FedBizOpps.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 addressing management and technical aspects each non-cost evaluation factor/subfactor contained in the solicitation.

ii. Offeror Summary Table: The Offeror shall complete the table below. The Offeror shall include all subcontractors and team members who will be involved with the performance or management of the contract and 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)

Place of Performance/DUNS # if applicable

Brief Work Description and/or Program Responsibility

% of Total Proposed Price

iii. Signed SF33 or SF1449 for basic solicitation and acknowledgment of each amendment, including completion of any RFP clause or provision that requires a fill-in or response. (Does not count against page limit.)

iv. Signed Representations, Certifications, and Acknowledgements or Online Representations and Certifications Application (ORCA) reference. (Does not count against page limit.)

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

vi. Guarantee the length of proposal validity (for at least 120 days after proposal submission).

vii. 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. (Does not count against page limit)

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:

2.1 Elements

2.1.1 Element 1: Management Approach and Mission Accomplishment Capability

2.1.1.1 The Offeror shall demonstrate an understanding of the management necessary to perform the requirements outlined in the contract Statement of Work (SOW) by clearly describing its management approach and capability.

The approach shall include the proposed management plan, risk assessment and mitigation strategy, cost and schedule management methodologies, and any appropriate resources for the contract SOW. The Offeror shall demonstrate, in the context of the SOW requirements, its capability to plan, organize, and direct/control performance at the Prime and Subcontract level to assure compliance with requirements of multiple delivery orders that require concurrent effort (for purposes of this section of the proposal, assume that 3-5 delivery orders similar in delivery, size, scope, and complexity to the sample delivery order will be concurrently performed). This description shall clearly demonstrate how the company’s management efforts will support the NAWCWD mission to provide non-proprietary IETS solutions for deployment throughout the Joint Intelligence Community.

The offeror shall demonstrate the management controls, procedures and methods necessary to assure accomplishment of procurement, subcontracting, status reporting, security, and personnel staffing requirements.

2.1.1.2 The Offeror shall describe its approach for providing personnel to conduct RDT&E activities at NAWCWD, China Lake, CA in a timely manner. Travel to and from NAWCWD will be required at regular intervals (2-3 times per month) and may be required upon short notice (24 hours) depending upon aircraft or other test asset availability.

The proposal should describe the approach for meeting requirements to have qualified personnel on-site at NAWCWD and potential impacts of that approach on proposed costs and schedules.

The Offeror shall describe how their performance would contribute to the NAWCWD mission to continue provision of robust IETS solutions to the Fleet and Joint Service intelligence community. The goal of the procurement is to continue RDT&E efforts that result in capability improvement through technology insertion into IETS used by intelligence analysts, mission planners, and targeteers without proprietary restrictions or limitations posed by restricted data rights or privately held patents. The Mission Engineering and Interoperability (MEI) Division within the Systems Engineering Department (410000D) supports Navy and Joint Service components by fielding IETS that continue to support operational needs and capabilities and improve warfighting effectiveness. The offeror shall describe how their approach to developing and deploying new IETS capabilities will support the NAWCWD Joint Service mission in this area.

Offerors are advised to review 1.0 GENERAL above and follow the guidance therein.

2.1.2 Element 2: Technical Approach and Capabilities

2.1.2.1 The Offeror shall demonstrate an understanding of the technical requirements that are outlined in the contract Statement of Work (SOW) section 3.0 Requirements and clearly describe its technical approach and capability for each paragraph in these sections of the SOW. Responses shall correlate with the paragraph numbers in the SOW.

The approach shall include the proposed development plan, risk assessment and mitigation strategy, cost and schedule management methodologies, and any appropriate resources for the contract SOW.

The Offeror shall present a complete and detailed statement of the selected approach to the SOW requirements, including analyses, experiments, simulations, tests and facilities required in resolving the problem(s) and its elements. For each requirement, include a description or discussion of scientific principles and techniques that the Offeror proposes to use in addressing potential problems. Estimate the extent of subcontracting anticipated with a list of items or effort to be subcontracted. If a teaming approach is being proposed, provide complete information as to the arrangement.

2.1.2.2 The Offeror shall provide a generic draft software development plan (SDP) in the format presented in Contract Data Requirements List (CDRL) A007 and the information required in accordance with NAVAIR provision 5252.239-9500. The SDP shall be submitted as an attachment to volume 2 and does not count towards the page limit. However, the SDP shall be concise, to-the-point, and appropriate to the planned software effort. The Offeror shall include the SDP Rationale to describe why the proposed approach is appropriate for the items to be procured.

Offerors are advised to review 1.0 GENERAL above and follow the guidance therein.

2.1.3 Element 3: Key Personnel and Facilities

2.1.3.1 Personnel Experience and Qualifications. The proposal should describe the experience, qualifications, certifications, and other appropriate information that management and technical key personnel will possess to ensure successful contract performance. Specific names or individual resumes are not required, but experience with prior similar tasking as described in the SOW should be referenced by project name of other identification than contract number. This information could be submitted as a table.

2.1.3.2 The offeror shall provide a description of the facilities and equipment that it anticipates using in order to satisfy the contract requirements. The offeror shall identify whether the equipment and facilities is government owned, corporately owned or the property of a team member. This includes EMI/EMC facilities, electronic fabrication facilities, computer equipment, communication equipment, and automated information systems (AIS) approved for data processing at the SECRET level or higher. It is essential for the offeror to demonstrate that it possesses and will be capable of maintaining a TOP SECRET facility clearance and SECRET storage capabilities. If the offeror does not possess these facility clearances, it shall describe in the proposal their plans for obtaining such within 60 days of contract award (see http://www.dss.mil/isp/index.html for requirements).

2.1.4. Element 4: Sample Task

2.1.4.1 Offerors shall submit a technical description of an approach to the design and implementation of a point mensuration methodology for uncontrolled imagery, i.e., images without any supporting information as in the NITF images commonly used. The approach should encompass some form of registration and/or resection (photogrammetric) capabilities and account for electro-optical (EO), infrared (IR), and synthetic aperture radar (SAR) modalities. The methodology should be described in details sufficient to convey the offeror’s understanding of sensor model development and proper use and explain how circular error (CE) and linear error (LE) values would be predicted and verified. It should also describe the expected accuracy limitations with respect to image type and collection geometry. Image types to be tested using the methodology would be digital aerial photos, single frames captured from video as produced by unmanned aerial vehicles (UAVs) or systems (UAS), or images scanned from other camera or hardcopy sources. The methodology must also account for interfaces to systems that provide weaponeering solutions for targets, systems that provide collateral damage assessments for targets, and the

Modernized Intelligence Data Base (MIDB) used by the Joint Intelligence Community. The technical description should contain architecture diagrams, mathematical formulas, process flowcharts, and sample inputs and outputs. No cost information shall be contained in the technical volume.

2.1.4.2 Technical and Programmatic approach. The Offeror shall demonstrate its understanding of the technical requirements that are outlined in the sample task and clearly describe its technical capability and prior experience in the sample task areas. The Offeror should present a complete and detailed description of its approach to the sample task, including analyses, experiments, simulations, tests and facilities required in developing the required capabilities. For each portion of the task, include a description or discussion of scientific principles and techniques that the Offeror proposes to use in addressing the problem.

2.1.4.3 The Offeror should demonstrate, in the context of the sample task, its capability to plan, organize, and direct/control performance at the Prime and Subcontract level to assure compliance with requirements of multiple delivery orders that require concurrent effort. This description should clearly demonstrate the how the company’s management efforts will enable it to meet performance, cost, and schedule goals. Estimate the extent of subcontracting anticipated with a list of items or effort to be subcontracted. If a teaming approach is being proposed, provide complete information as to the teaming arrangement.

2.1.4.4 Pricing. No pricing information shall be contained in the technical volume, but shall only be included in the price/cost proposal, see 4.0 below. The cost estimate shall address labor and travel requirements as well as estimated for material, equipment, and access to facilities for testing or integration.

3.0 VOLUME 3: PAST PERFORMANCE/EXPERIENCE

3.1 General

The Offeror shall identify on the Past Performance Matrix (see (a) below) any contracts performed within five years of the RFP release date which contains efforts similar to those proposed by the Offeror, the Offeror’s principal subcontractors, and the Offeror’s critical team members. 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 also 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 1) 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 2) 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 Past Performance Data Requirements. The

Offeror shall include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to Kelley McClean, Contract Specialist, at kelley.mcclean@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. Written consent will not count against the page limitation.

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. Contractor Name P1 P2 P3 P4 PX S1 SX

2. Title of contract

3. Contract number/type

4. Procuring agency

5. Description of product or service

6. Period of performance

7. Place of performance and CAGE Code/ DUNs #

8. Dollar value of contract

9. Acquisition Phase(s) of Contract, e.g., SDD, Production

10. CPARs? - CPARS completion date - on DOD PPIRS? 1

11. Recency 2

12. Relevancy 3

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

3 - 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: Very Relevant (V), Relevant (R), Somewhat Relevant (S), or Not Relevant (N) as defined below and in Section M.

Past Performance Relevancy Ratings Rating Definition Very Relevant Present/past performance effort involved essentially the same scope and magnitude of effort and complexities this solicitation requires.

Relevant Present/past performance effort involved similar scope and magnitude of effort and complexities this solicitation requires.

Somewhat Relevant Present/past performance effort involved some of the scope and magnitude of effort and complexities this solicitation requires.

Not Relevant Present/past performance effort involved little or none of the scope and magnitude of effort and complexities this solicitation requires.

(b) Experience-The Offeror shall provide a table that cross references each SOW paragraph to the contracts identified in the Past Performance Matrix required above to demonstrate the required experience. The table shall also cross reference this information with the applicable Volume 2 technical elements to validate experience. See Attachment 3. The Offeror is limited to five past performance references/contracts in the completion of Attachment 3.

The Offeror shall provide a narrative description of its management experience on projects with scientific and technical efforts similar to those required in the SOW. This description shall clearly demonstrate the how the company’s management efforts resulted in its ability to meet contract performance, cost, and schedule goals on projects of similar, or as similar as possible, size and complexity, where detailed technical implementation descriptions, source code, and build instructions (independent of proprietary systems) were provided as deliverables.

The Offeror shall include a description of previous experience in developing software of the same nature as being acquired, and a description of the extent to which personnel who contributed to these previous efforts will be supporting this effort. The Offeror shall provide a description of previous experience in developing software using the same of similar process and approached as they have defined in the SDP, and provide the past performance information required in accordance with NAVAIR provision 5252.239-9500.

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

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

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

1. Contract #

2. Offeror’s Role

Customer’s Name (e.g.,

1. CPARS? Recent?

2. Questionnaire # __

Point of Contact Information:

Sub, Critical Team Member, or Team Member)

(e.g., prime or sub)

NAVAIR or

NAWCWD)

Sent?

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

Name;

Phone Number, Fax Number;

E-mail address

AB (prime) 1. N009,

2. Prime

RYP 1. CPARS: No

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

AB (prime) 1. N008,

2. Sub

L&M 1. CPARS: Yes/No

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

3. N/A

Sue (PCO) 333-333-3333 fax 222-222-2222 Sue@AB

NNB (sub) 1. N007,

2. Prime

RST 1. CPARS: Yes/Yes

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, for evaluation purposes, the Total Prices filled in using the estimated quantities value in the solicitation and the instructions below. 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.

(b) All price/cost and price/cost supporting information for the sample task 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.

(c) Sample Task – The Offeror shall identify the proposed prices/costs for the sample task in the requirement listed in Volume 4 Element 4. In developing the Cost Plus Fixed Fee CLIN, the Offeror shall propose the appropriate direct labor, other direct costs, subcontracts, indirect costs, and fixed fee. The Offeror shall sum up the proposed Total Prices/Costs and provide a total overall price/cost plus fixed fee of the sample task.

(d) Overall Contract Price – The Offeror is not required to price the basic contract Section B, only the sample task is to be priced as noted in (c) above. Contract wills be awarded at the IGCE value with individual delivery orders to be competed among the awardees.

4.2 Ground Rules and Assumptions:

(a) As this is a competitive acquisition any price/cost documentation requested shall not be certified cost or pricing data in accordance with FAR 15.403-1. 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.

(d) The fixed fee rate proposed on the sample delivery order CLIN 0001 will be the maximum fee allowed on CLIN 0001 for all orders.

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. 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. If this requirement contains cost type CLINs, 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) For the Sample Task, the Offeror shall provide a schedule which contains the proposed burden rates by accounting period 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)When completing the required cost/price proposals, the Offeror shall not utilize any fully burdened hourly rates, or “wrap-rates,” when pricing the labor of its employees.

(f) If a subcontractor of the Offeror utilizes fully burdened rates in its proposal to the Offeror, the subcontractor shall provide its own breakout spreadsheet delineating the buildup of those rates to the Government.

(g) Provide a narrative that addresses any assumptions made during the preparation of the cost/price proposal and discuss the basis for the cost elements listed below:

Labor hours per labor category

Direct labor rates by category. The offeror is required to submit labor rates for proposed individuals. If composite or category averages are proposed, provide a breakdown of how rates are developed. If necessary provide a narrative to describe derivation of labor rates, use of uncompensated overtime, pools to which indirect rates are applied, historical /provisional billing rates for indirect rates for the last 3 years and description, and amount of proposed other direct costs.

Escalation on labor

Indirect costs (i.e. Overhead, Fringe Benefits, General & Administrative (G&A), etc.)

Information needed to explain the offeror’s estimating practices

Profit/Fee: Identify profit/fee rate and total amounts proposed and identify the various cost elements to which the profit/fee is being applied. Profit, Base, Award, and Incentive fee rates, as applicable in Section B, must be clearly distinguishable. Profit/Fee shall not be applied to ODCs.

Other Direct Costs (ODCs) by specific cost element (e.g., Travel, Material, NMCI). Reimbursement for Travel will be in accordance with the Joint Travel Regulation. If the offeror chooses to increase the Government estimated amount by applying burdens or for other reasons, the offeror must provide the basis/detail for the variance.

When the offeror elects to claim Cost of Money (COM) as an allowable cost, the offeror must submit a COM form (DD 1861) and show the calculations of the proposed amount.

Professional employee compensation plan in accordance with FAR 22.1103.

4.4 Use of Government Furnished Property:

If the Offeror proposes/requires the use of Government Furnished Equipment (GFE) or Government Furnished Information (GFI), then the Offeror shall provide:

A complete description of the required GFE/GFI including part number and serial number, if applicable.

Where the GFE/GFI is to be located.

The name, organization, completes address and telephone number of a cognizant Government point of contact.

In the case of GFE/GFI accountable to other Government contracts, a copy of the correspondence authorizing use of such GFE/GFI on this contract.

The monetary impact to the Offeror’s proposal if the proposed GFE/GFI is not provided as GFE/GFI.

If no GFE/GFI/GFP is required, the Offeror shall so state.

4.5 Other Costs

The Offeror shall identify additional costs that would be incurred that have not been identified in the solicitation and describe in detail the performance that would cause these costs. Profit or fee shall not be included on ODCs.