Amendment_0002.docx

N00421-17-R-0021

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 28-Sep-2017 02:00 PM to 02-Oct-2017 02:00 PM.

The following have been added by full text:

AMENDMENT 02

The purpose of Amendment 02 is:

a. In Section B, add SOW Paragraph 3.15 to CLIN Description for CLINs 0001, 0101, 0201, 0301 and 0401;

b. in Section F, Deliveries or Performance, Page 24, Paragraph 2, add CLIN 0404;

c. in Section J, add Attachment 1-N00421-17-R-0021 FMF APP SOW REV 1 which corrects typo Attachment B in Paragraph 3.3.1, on Page 14, and replaces it with Attachment A;

d. in Section J, add Attachment 6_Cost_Price Worksheets REV 1, and

e. in Section L, Part A, General Instructions, 3.0, Proposal Content and Volumes, add 1 ORIGINAL and 3 Copies to the Copies Required Column for Annex #1 3.0 Technical Data, Computer Software and Computer Software Documentation Rights and add Annex #3 As Required Per Section L, Part B, 2.0 Technical Approach and add 1ORIGINAL AND 5 Copies in the Copies Required Column.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0001

The CLIN extended description has changed from:

Engineering, Technical, and/or Logistics Services in support of FMF App, SOW Paragraphs 3.1 through 3.11, 3.13 and 3.14.

To:

Engineering, Technical, and/or Logistics Services in support of FMF App, SOW Paragraphs 3.1 through 3.11, 3.13 through 3.15.

CLIN 0101

Engineering, Technical, and/or Logistics Services in support of FMF App, SOW Paragraphs 3.1 through 3.11, 3.13 and 3.14

Engineering, Technical, and/or Logistics Services in support of FMF App, SOW Paragraphs 3.1 through 3.11, 3.13 through 3.15

CLIN 0201

Engineering, Technical, and/or Logistics Services in support of FMF App, SOW Paragraphs 3.1 through 3.11, 3.13 and 3.14

Engineering, Technical, and/or Logistics Services in support of FMF App, SOW Paragraphs 3.1 through 3.11, 3.13 through 3.15

CLIN 0301

Engineering, Technical, and/or Logistics Services in support of FMF App, SOW Paragraphs 3.1 through 3.11, 3.13 and 3.14

Engineering, Technical, and/or Logistics Services in support of FMF App, SOW Paragraphs 3.1 through 3.11, 3.13 through 3.15

CLIN 0401

Engineering, Technical, and/or Logistics Services in support of FMF App, SOW Paragraphs 3.1 through 3.11, 3.13 and 3.14

Engineering, Technical, and/or Logistics Services in support of FMF App, SOW Paragraphs 3.1 through 3.11, 3.13 through 3.15

SECTION F - DELIVERIES OR PERFORMANCE

The following have been modified:

DELIVERIES

Items 0004, and Option Items 0104, 0204, 0304, and 0404 - Delivery of the supplies to be provided hereunder shall be accomplished on or before the 20th calendar day of the month. Deliveries shall be accomplished within twelve (12) months from the date of the first delivery, with deliveries evenly distributed across the 12 months. Final delivery schedule shall be based upon negotiated quantities.

Total

TBN

TBN

TBN

Item 0005 - Delivery of the supplies to be provided hereunder shall be accomplished on or before the 20th calendar day of the month. Deliveries shall be accomplished within twelve (12) months from the date of the first delivery, with deliveries evenly distributed across the 12 months. Final delivery schedule shall be based upon negotiated quantities.

Total

Items 0004, and 0005 and Option Items 0104, 0204, 0304, and 0404 – Final destination for the supplies is PMA 209 AIR COMBAT ELECTRONICS FMF APP -SUSAN WHITLEY /ANTHONY STACHOWSKI 47123 BUSE ROAD BLDG 2272 SUITE 351PATUXENT RIVER, MD 20670 TEL: 301-757-6457/301-757-1539. The contractor shall notify the Administrative Contracting Officer via email with any intent to ship supplies early. This notification shall be provided no later than 30 calendar days prior to the anticipated early delivery date.

Item 0006 and Option Items 0106, 0206, 0306 and 0406 - The technical data provided hereunder shall be delivered in accordance with Exhibit A, Contract Data Requirements List (CDRL), DD Form 1423 and associated Data Item Descriptions.

SPECIAL INSTRUCTIONS – Applicable to all CLINs

The Government will consider accelerated deliveries. To the extent the Government has the capacity to support early delivery, or the Contractor agrees to ship early deliveries in place (held in bonded storage with no liability for the item assumed on the part of the government) accelerated deliveries may be accepted provided there is no increase in cost to the Government.

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

ATTACHMENTS

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

FMF APP

L – (1) CONTENT OF PROPOSALS

5252.215-9522 ALT 1 This provision has been replaced with the fully tailorable Section L provision below.

L – [1] CONTENT OF PROPOSALS (18 July 2017)

PART A GENERAL INSTRUCTIONS

1.0 GENERAL

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 into the resulting contract.

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. 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 assessing weaknesses and/or deficiencies.

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. Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

The Government advises the Offeror that taking exception or deviating from any term or condition of the RFP may result in the assessment of a deficiency to the proposal.

Throughout these instructions, “Offeror” is defined as the prime contractor with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award. A “principal subcontractor” is defined as a subcontractor who provides at least 15% of the proposed total price/cost (excluding the Offeror’s profit/fee), for the contract. A “JV Team member” is defined as one of the entities that make up a joint venture (JV) formed for the purpose of responding to this solicitation. The term “entity” is used to mean any or all of the following: prime contractor, JV, JV team members, any subcontractor, and corporate parent, division, subsidiary, or affiliate (e.g., any contractor with a different CAGE Code/DUNS than the Offeror). The following entities are defined as principal entities and only principal entities will be used in the past performance and corporate experience evaluations: (a) the prime contractor; (b) JV Team Members; and (c) principal subcontractors and other entities that are proposed to perform at least 15.00% of the proposed total cost/price for the contract. Offerors are advised that in order to demonstrate work commitment, each principal entity must be identified in Volume 5 Cost/Price and associated with a commensurate dollar value.

Questions: Offerors may submit questions requesting clarification of solicitation requirements by emailing the contract specialist at bonnie.walsh@navy.mil . It is required that all questions be received within 20 calendar days of the date this solicitation is issued.

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. Darwin Government Specifications 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, including such data as tables or charts, should be consistent with the purpose of the data presented.

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

3.0 PROPOSAL CONTENT AND VOLUMES

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 Volume/paragraph number matches the Proposal Instructions Volume/paragraph number provided in section “Part B Specific Instructions” 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.

Each volume of the proposal shall be submitted as one original and additional copies as specified in the table below. 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. Any pages submitted exceeding the page limit shall be disregarded and NOT evaluated.

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. Page limitations for Annexes, if any, are specified below. The authorized Annexes are summarized in the table below.

1 ORIGINAL AND 3 Copies

1 ORIGINAL AND 3 Copies

Annex #2

As Required Per Section L, Part B, 4.0 Past Performance, 1 ORIGINAL AND 2 Copies

Annex #3

As Required Per Section L, Part B, 2.0 Technical Approach

1 ORIGINAL AND 5 Copies

Each volume shall contain the following information:

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)

Volume 2 Technical Example: Para 3.1 Note: This column shall address all paragraphs in Sections xx and xy of the SOW/PWS.

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 the date and time specified in Block 9 of the SF 33 of the RFP.

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 Warfare Center, Aircraft Division Code: AIR-2.5.1.10.3, Bonnie M. Walsh 47123 Buse Road, Bldg. 2272, Rm 350 Patuxent River, MD 20670 Solicitation Number: N00421-17-R-0021

Hand carried proposals may be delivered to the address above, attention Daniel Chambers (PCO) and/or Bonnie M. Walsh (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 Original Proposal volumes including the original/signed documents submitted as part of Volume 5 Cost/Price.

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

Cost or pricing information shall only appear in the Price/Cost volume.

1.0 VOLUME 1: CORPORATE EXPERIENCE

To demonstrate relevant Corporate Experience, the Offeror shall provide written response to the following sub-factors:

1.1 Aviation Navigation Flight Management System Solutions – The Offeror shall document their corporate experience in developing flight management system solutions that have been certified by a civil aviation authority for RNP RNAV operations, including RNAV (GPS) approaches to LNAV minima, in civil airspace.

1.2 Open Modular Software Architecture Solutions –

1.2.1 The Offeror shall document their corporate experience in abstracting capability business logic from software/computing infrastructure. Infrastructure is the operating system, middleware and/or platform specific sensors and buses.

1.2.2 The Offeror shall also document their corporate experience with architectural standards (internal, governmental, and/or open standards) which led to the design of these abstracted components and the internal processes.

1.2.3 The Offeror shall also describe their corporate experience with the evaluation process for introducing modularity to the capability business logic including both technical and business decisions that drove the boundaries for individual Computer Software Components (CSC).

2.0 VOLUME 2: TECHNICAL APPROACH

Cost or pricing information shall only appear in the Price/Cost Volume.

The Offeror shall provide all information and data required to conduct a thorough and complete technical evaluation. The Offeror shall provide written responses to the following technical requirements:

2.1 Systems Engineering.

1) identifies the Government Specification requirements (threshold & objective) that their proposed FMF currently meets, and

2) annotates the Government Specification requirements present in their current FMF, but requiring minor modification, and

3) annotates the Government Specification requirements that their proposed FMF will meet after their proposed NRE period, and

4) annotates additional Capabilities resident in the Offeror's FMF but not in the Government Specification, and the parent requirement for each capability, and

5) identifies verification methods (Inspection, Analysis, Demonstration, & Test) and venues for each Government Specification requirements, and

6) annotate what party (contract/sub-contractor) is responsible for meeting the Government Specification requirements

1) The System Engineering Technical Review events proposed

2) The rationale behind their proposed System Engineering Technical Review events

3) Proposed entry criteria for each System Engineering Technical Review event

4) Artifacts & documents to be provided prior to each event and the supporting rationale for their need

5) Specific information to be presented and a detailed description of the specific SE goals for each event

Sequence of Events The Offeror shall prepare and submit a draft schedule showing major Technical program activities

1) External I/O signals/data from the aircraft required by their FMF App to meet Government Specifications

2) External I/O signals/data from the aircraft required by their FMF App for capabilities outside the scope of the Government Specification and the specific capabilities the external I/O signal(s) supports

3) how they will capture these external signals/data in the FACE Data Model

2.2 Functional Compliance.

The narrative SHALL include tasks, tools (software and hardware (SW&HW)), & timeline required of the Government to process the Digital Aeronautical Flight Information File (navigation database).

The narrative shall include any tasks, tools (SW&HW), & timeline required of the Offeror to process the Digital Aeronautical Flight Information File (navigation database) DAFIF DB.

1) The narrative shall describe how the FMF App will interact with the DAFIF DB i.e. directly (within FACE architecture) or indirectly (externally/outside FACE architecture).

The Offeror SHALL describe process(s) required to provide the FMF application with an updated/revised US/UK Magnetic Model file (five-year coefficient data), this portion of the narrative SHALL also discuss any necessary formatting and/or FMF application recompiling requirements.

The narrative SHALL:

a) Describe any architectural variability mechanisms (e.g., adaptation data, compile-time parameters, variable replication, and so forth), including a description of how and when those mechanisms may be exercised and any constraints on their use.

b) Describe those capabilities/features which are configurable, and who (FMF App Offeror or Government) will have the ability to administer those capabilities/features.

The narrative SHALL be segregated into areas controlled by: Offeror, Government during Integration and Application user; addressing but not limited to the following areas of interest:

1) Fixed vs Rotary Wing

2) Performance modeling i.e. Generic, Specific, aerodynamic, propulsion (source data, limitations, formatting)

3) Feature/Function enabling

4) User enabled/disabled i.e. sensors

5) Configuration tools/methods and any licensing dependencies

The narrative SHALL provide enough detail for the government to assess the level of control an operator (software input) will have over navigation sensor prioritization/selection/usage. Offeror’s providing Kalman filtering algorithms embedded into the FMF application SHALL specify if inputs are present to enable and/or disable filtering and provide insight into design rules employed (weighting, filtering, and error budgets) when blending the available navigation sensors.

2.3 Software.

1) Provide rationale for component decomposition within the software architecture.

2) Describe computing resources and constraints on the computing environment that must be accounted for during integration on a target platform.

3) Describe the treatment of Proprietary or Vendor-Unique Software 4) Describe any interfacing to Proprietary or Vendor-Unique Software 5) Identify what Units Of Conformance (UoCs) are planned for reuse and their functionality

The Offeror shall address in the SDP the following areas for process maturity:

1) Describe previous experience in developing software using the same or similar processes and approaches as proposed for this solicitation

2) Describe how the software developed from subsidiaries/suppliers and subcontractors will be managed and the processes that will be mandated on those entities.

The Offeror shall provide rationale which describes why the specific approach defined in the SDP is appropriate for the system to be procured. This rationale shall detail the chosen methodology (Waterfall, Agile, Hybrid, etc.) including process flow examples. This rationale shall describe why the approach was chosen and provide a description of previous experience with using this approach to develop software of the same or similar nature as being acquired.

a. The plan to qualify software development tools, if any, for use in developing the software.

b. Describe support for Stages of Involvement (SOI) events.

c. Describe your company's approach to training employees in the DO-178 process that will be used as part of this proposal

(a) Source Lines of Code (SLOC) using logical code counting methods shall be broken out by New/Modified/Reuse/Auto-code categories. A description detailing how the size was developed shall also be provided (analogy, function point, requirements analysis, etc.) along with any data justifying the estimate. A typical way to quantify the effort associated with reuse and modified code is to develop an Equivalent SLOC (ESLOC) count using factors to convert reuse and modified into an equivalent new line of code. Should ESLOC be used, the ESLOC computations (i.e. factors used to determine the ESLOC) shall be provided for the estimated software.

(b) The primary language planned.

(c) A relative measure of the complexity of the code broken down as simple, routine, and complex using the definitions provided. Within a CSCI it is possible to have a mix of complexity, for example 10% might be simple, 70% routine and 20% complex; at the CSU level, there will typically be 100% assignment to one of the complexity ratings.

The Offeror SHALL submit, as part of the proposal, the Software Reuse Plan and Analysis (DI-SESS-82042) final, addressing DID sections 3.1, 3.2, 3.3, 3.6, 3.7, 3.8, 3.10, 3.11, 3,12, 3.13, 3.17, 3.19, to identify and characterize reused and modified software supporting this solicitation and the size estimate.

1) Describe communication paths used by software-initiated or software-carried messages, and the software elements that send and receive information along those paths. 2) Detail data required and provided by software elements, and show where that data is stored (when applicable).

3) Detail all inter-UoC dependencies

a. Use of encryption & encryption method.

b. Health and fault monitoring and reporting.

c. FMF degraded states operation.

d. Use of COTS, GOTS, Third-party and open source items code

e. Watchdog timers

2.4 Logistics.

(1) The Offeror shall describe how they will notify the government and address Airworthiness Directives (FAA issued AD's)

(2) analyze software trouble reports

(3) software change requests

(4) software safety critical defects (Per SOW Priority 1 & 2s)

(5) identify and address the stability and supportability of any software development tools or non-vendor software content

2.5 Test.

(1) Description of test methodology to verify the FMF App meets functional requirements,

(2) Description of test processes, tools & artifacts used for test planning, execution, and reporting of test results.

(1) Hardware and software used for verification of specification requirements,

(2) Description of any simulated interfaces or models used to simulate hardware or software,

(3) Description of processes used to develop and validate models,

(4) Description of the configurability of their test environment,

(5) Description of the Cyber Security test strategy to include any vulnerability assessments, redundancies and checks to identify improper operation, hardening or resiliency, or other activities to thwart malicious or unintended operation.

3.0 VOLUME 3: Technical Data (TD), Computer Software (CS), and Computer Software Documentation (CSD) Rights Volume

Cost or pricing information shall only appear in the Price/Cost volume.

3.1 The Offeror shall describe the rights in TD and CS for each proposed CSU/UoC. (The rights described shall be consistent with the assertions in the 252.227-7017 List.)

3.2 The Offeror shall explain the extent to which the rights in TD, CS, and Computer Software Documentation (CSD) offered to the Government ensure unimpeded, innovative, and cost-effective production, operation, maintenance, and upgrade of the FMF App throughout its lifecycle; allow for open and competitive procurement of enhancements; and permit the transfer of the FMF App’s non-proprietary object code and source code to other Contractors for use on other systems or platforms.

3.3 The Offeror shall describe its plan for making design and interface information available as soon as possible after it is defined or established. The Offeror shall establish and maintain a process that will provide “early and often” design disclosure directly to the Government or to third-party Contractors via Government established access, to in-process design documentation and CS. Access and the ability to download this information shall be supported using industry standards.

3.4 The rights in TD,CS, and CSD and licenses offered for the FMF App shall be provided as attachments to the proposal. The Offeror shall describe how the proposed Intellectual Property Rights (IPR) meet the program needs.

3.5 The Offeror shall provide the following information as attachments to its offer:

3.5.1 Pre-Award Identification and Assertion of Restrictions on the Government's Use, Release, or Disclosure of TD and CS:

a. Rights in Non-commercial TD, Non-commercial CS, and Non-commercial CSD.

The Offeror (including its Subcontractors and suppliers at all tiers) shall identify and list all non-commercial TD, CS, and CSD that it proposes to deliver or otherwise furnish with less than/other than unlimited rights pursuant to the procedures and requirements of the DFARS 252.227-7017 Identification and Assertion of Use, Release, or Disclosure Restrictions (the 7017 List) provision incorporated in SECTION K of this solicitation.

b. Supplemental Non-commercial License Information

The Offeror (including its Subcontractors and suppliers at all tiers) shall include copies of, or provide in its proposal website links to, any proposed specifically negotiated license(s) associated with deliverable non-commercial items on the 7017 List. The Offeror shall include such licenses/links with its 7017 List.

c. Rights in Commercial TD, Commercial CS, and Commercial CSD

The Offeror (including its Subcontractors and suppliers at all tiers) shall attach to its proposal a list, entitled “Commercial Technical Data, Commercial Computer Software, and Commercial Computer Software Documentation-Government Use Restrictions” – the Commercial Restrictions List (CRL), that provides the following information regarding all commercial TD, CS, and CSD that the Offeror (or its Subcontractors or suppliers) proposes to deliver with less than/other than unlimited rights:

i. Identification of the commercial TD, CS, or CSD

ii. Name of the person/entity asserting restrictions

iii. The asserted rights category

iv. Identification of the deliverable requirements to which the TD, CS, or CSD pertain.

The Government's rights with respect to certain types of commercial TD are set out in DFARS Clause 252.227-7015. Any proposal submitted by the Offeror should be consistent with this clause.

An example CRL format is provided below. The Offeror shall submit the CRL as Annex 1 to its proposal, dated and signed by an official authorized to contractually obligate the Offeror. If there is no information to be included in the CRL, the Offeror shall submit the list and enter “None” as the body of the list. If the Offeror is awarded a contract, the corresponding CRL will be attached to the contract.

COMMERCIAL TECHNICAL DATA, COMMERCIAL COMPUTER SOFTWARE, AND COMMERCIAL COMPUTER SOFTWARE DOCUMENTATION

GOVERNMENT USE RESTRICTIONS

3.5.2 Rationale and Proposed Use of Proprietary or Vendor-Unique Software

The Offeror shall provide:

a. A description of the proposed use and functionality of commercial, proprietary, or vendor-unique UoCs or software units identified in the 252.227-7017 List and the CRL in the system.

b. A mapping of each TD and CS rights assertion to the corresponding CLIN(s), CDRL(s), or SOW paragraph(s) pertaining to the deliverables which may be subject to each assertion. The Offeror may include a copy of the 252.227-7017 List and add a column with the heading: “Associated Delivery Requirement(s) (Identify CLIN(s), CDRL(s), or SOW Paragraph(s)” to fulfill this requirement, as shown in the CRL.

4.0 VOLUME 4: PAST PERFORMANCE

Cost or pricing information shall only appear in the Price/Cost volume.

Sources of past performance evaluation information include information provided by the Offeror in response to the solicitation, information obtained from questionnaires, and any other sources available to the Government, to include, but not limited to, the Past Performance Information Retrieval System (PPIRS), Federal Awardee Performance and Integrity Information Systems, Electronic Subcontract Reporting System, or other databases; the Defense Contract Management Agency; and interviews with Program Managers, Contracting Officers, and Fee Determining Officials.

The Offeror shall complete the Past Performance Information Form, Attachment 3, for each past performance reference performed within five years of the solicitation release date. The Offeror shall submit no more than five Past Performance Information Forms as the Prime Contractor, no more than two forms for each principal subcontractor, and/or no more than two forms for each JV team member. The Offeror shall submit written consent from its principal subcontractor(s) and JV team member(s) that will allow the Government to coordinate any past performance issues directly with the Offeror. If the Offeror does not submit the written consent, the Government will address any past performance issues directly with the principal subcontractor or JV Team member and the Offeror will forfeit the opportunity to participate in any related discussions. Consequently, for any principal subcontractor and JV team member that does not provide the written consent, the Offeror shall provide the name, address, phone number, and email address with whom the Government may address any past performance issues.

The Offeror shall provide a narrative on each Past Performance Information form in the “Contract Effort Description” area that clearly describes how each contract reference has relevant work effort that matches the relevancy definitions specified in Section M of the solicitation. Additionally, the Offeror shall provide one electronic copy of the Statement of Work/Performance Work Statement for each contract reference as Annex 2.

The primary source of past performance information will be PPIRS. If a Contractor Performance Assessment Report (CPAR) exists for multiple years for the same contract/order, all periods of performance within the recency period specified above, for that contract/order, will be used for evaluation. In the event a CPAR does not exist for a past performance reference, the Offeror shall submit a Contractor Performance Assessment Questionnaire (CPAQ), Attachment 4, to the Government Program Manager who is the Assessing Official. The Offeror shall include instructions for the Program Manager to send completed questionnaires within two weeks of CPAQ receipt via e-mail to Bonnie M. Walsh, Contract Specialist, at Email bonnie.walsh@navy.mil or via fax number 301-995-9461, thereby allowing the customer approximately two weeks to complete their response. All CPAQs should be received by the Government concurrently with the Offeror’s proposal submission.

5.0 VOLUME 5: PRICE/COST PROPOSAL

-If subcontractors are proposed, they shall provide the same information required for the prime contractor, unless otherwise noted below.

5.1 Volume Content:

(a) This Volume shall contain the Contract Compliance information specified below as follows:

i. Offeror Summary Table: The Offeror shall complete the table below (Attachment 5). The Offeror shall include all subcontractors and JV team members who will be involved with the performance of the contract and list all sites where the work will be performed. If a JV 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, JV Team Member, or Sub)

(b) This Volume shall also contain 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. Section B prices shall be provided separately in one digital data copy in MS Office 2010 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.

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

5.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.406-2. However, in the event that adequate price competition does not exist after receipt of proposals, the Government reserves the right to request additional cost or pricing data as necessary from both the Offeror and subcontractors and may conduct negotiations with the Offeror, pursuant to FAR Part 15.403-4, in order to ensure a reasonable and realistic price/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 shall acknowledge the requirement to provide additional cost or pricing information and certify the data prior to award if/when requested by the Government.

(b) 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 as compared to historical data, or any other anomalies should be fully explained. Topics to be addressed include, but are not limited to, investments and programmatic variables (e.g., inflation/escalation, location, make/buy decisions, Offeror/subcontractor relationships, and business base concerns, etc.)

5.3 Cost/Price Instructions/Information:

The Offeror shall identify the proposed prices for each contract line item number (CLIN) or subcontract line item number (SLIN) as specified in Section B of this solicitation.

Offerors shall submit their fully completed cost/price proposal utilizing the Cost Summary Format (Attachment 6, Worksheet 04).

Offeror’s cost proposal shall include proposed License costs/prices for either CLIN 0004: License by Type/Model/Series or CLIN 0005: License – Enterprise wide, but may include both in their cost proposal if they so choose.

Licenses:

License Option Price Information (CLINS 0004 & 0005) For each proposed/expected CSU/UoC that the Offeror asserts with less than GPR and for which the Offeror is willing to sell to the Government greater rights than those identified in the 252.227-7017 List, the Offeror shall identify those greater rights, provide an option price at which the Government may purchase such greater rights, and identify the period of time during which the option is available for the Government to exercise.

Government Preferences

The Offeror may state any license option price as a firm fixed price, a percentage royalty rate (or use fee), or any other comparable compensation scheme, provided that the Government can reasonably calculate a sum-certain price for the license option using the price information and terms and conditions that the Offeror provided.

The spreadsheet shall be formatted on letter size (8.5 X 11) paper and shall be unprotected and unlocked, with formulae intact to show mathematical operations.

(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, PWS, proposed effort, and 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, company investment or management challenge or a contribution of resources and/or equipment), the Offeror shall fully identify and explain any such investments.

(c) Direct/Indirect Rates: The Offeror shall submit Forward Pricing Rate Agreements (FPRAs), Collective Bargaining Agreements (CBAs), and Area Wage Determinations (AWDs) as applicable for all proposed personnel. The Offeror shall identify whether the labor rates proposed are FPRAs, CBAs, AWDs, ACO/DCAA recommended rates (FPRRs), or Offeror’s proposed rates (FPRPs). The Offeror shall propose in compliance with the current hourly rate set forth in the Department of Labor Wage Determination as applicable. 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 a composite rate or other pricing methodology (e.g. cost estimating relationships) is utilized, the Offeror shall demonstrate how those rates were developed. Subcontractors and team members shall provide this information either separately or included in the Offeror’s submission of this document.

(d)…