N00039-19-R-0005-0001.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:

1) Update Section J to provide a revised Attachment 4 - Softw are Development Experience Matrix and a revised Attachment 4-5 - Labor Rate and Qualif ications.

2) Revise Section L Provisions L-317, paragraph 2.1.2. Table 3; L-317, paragraph 3.2.2.; and, L-349, paragraph (b) Table 4.

3) Revise Section M Provision M-307, paragraph (e)(ii).

1. CONTRACT ID CODE PAGE OF PAGES

S 1 25

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

16C. DATE SIGNED

BY 29-Nov-2018

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 N00039-19-R-0005

X 9B. DATED (SEE ITEM 11)

20-Nov-2018

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

28-Nov-2018

CODE

COMMANDER, SPACE AND NAVAL WARFARE

SYSTEMS COMMAND

02 CONTRACTS

4301 PACIFIC HIGHWAY

SAN DIEGO CA 92110-3127

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N00039-19-R-0005

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

ATTACHMENTS

1) Statement of Work, GPNTS Software Support Contract, dated 02 November 2018

2) Technical Data Package

3) Contract Security Classification Specification, DD254, dated 26 September 2018

4) Software Development Experience Matrix, Revision 1

4-1) Reference Information Sheet 4-2) Past Performance Questionnaire 4-3) Cost Summary Format 4-4) Supporting Cost Data 4-5) Labor Rate and Qualification, Revision 1

5) Qualifications

6) GPNTS Work Breakdown Structure (WBS)

7) Single Award Task Ordering Guide, 02 November 2018

8) Quality Assurance Surveillance Plan

9) Consolidated Government Furnished Property (GFP) List

10) Small Business Participation Data Form

Exhibits

A. Contract Data Requirements List (CDRL)

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

L-317 SUBMISSION OF PROPOSALS (COMPLEX) (JUL 1999)

1.0 SOLICITATION OVERVIEW

This solicitation is for the procurement of Global Positioning System (GPS)-based Positioning, Navigation, and Timing Service (GPNTS) Software Support based on Government provided Technical Data Packages (TDPs).

GPNTS receives, processes, and distributes three (3) dimensional position, velocity, acceleration, attitude, time and frequency in the formats required by shipboard user systems. GPNTS is the single Program of Record (POR) for U.S. Navy ships as well as potential U.S. Coast Guard (USCG), Military Sealift Command (MSC), and Foreign Military Sales (FMS) platforms. GPNTS is designed to accommodate back-fit of current legacy PNT systems and forward-fit of new platforms. The GPNTS system was developed using a commercial, open-systems architecture approach, to meet user requirements in a net-centric Service-Oriented Architecture (SOA) environment.

The solicitation is available via the Internet by accessing the SPAWAR Business Opportunities Page at https://e-commerce.spawar.navy.mil. If assistance accessing the solicitation is required, please contact Kenneth Nickel, Contracting Officer, by e-mail at kenneth.nickel@navy.mil or by telephone at (619) 524-7184.

1.1 QUESTIONS: Offerors may submit questions concerning, or request clarification of, any aspect of this RFP.

All questions shall be submitted in writing by electronic means through the GPNTS Software Support solicitation page on the Space and Naval Warfare Systems Command (SPAWAR) e-Commerce website at https://ecommerce.sscno.nmci.navy.mil no later than fifteen (15) calendar days after issuance of this RFP.

Offerors are advised that the Government will make available to the public any offeror questions and comments and the Government’s associated responses; therefore, offerors shall not provide questions or comments of a proprietary nature. The Government will use its best efforts to respond to offeror questions and comments, including questions received more than fifteen (15) calendar days after issuance of this RFP; however, responses are not guaranteed.

All questions and answers will be posted on the SPAWAR e-Commerce website at https://ecommerce.sscno.nmci.navy.mil.

2.0 PROPOSAL REQUIREMENTS:

2.1 PROPOSAL ORGANIZATION, FORMAT AND CONTENT

2.1.1 Proposal Organization: Proposals submitted in response to this RFP shall be unclassified and shall consist of three (3) separate volumes identified as follows:

a. Volume I: Offer

b. Volume II: Technical Proposal

c. Volume III: Price/Cost Proposal

2.1.2 Proposal Format: In addition to all other requirements to this solicitation, each offeror shall demonstrate its capability by means of a detailed written proposal in each of the areas indicated under Section M – Evaluation Factors for Award. Proposals submitted for consideration for award shall address the full scope of the solicitation.

The offeror’s proposal volumes shall include the following:

Table 3.

Item Page Limit

VOLUME I: OFFER

Section 1: Cover Letter/ Executive Summary Five (5) pages Section 2: Exceptions to the RFP No Limit Section 3: Signed SF33 with completed Sections B through K No Limit Section 4: Proprietary Data Protection Agreements (PDPAs) No Limit Section 5: Contractor Responsibility Information No Limit Section 6: Systems and Compliance No Limit Section 7: OCI Mitigation Plan(s) No Limit Section 8: Small Business Subcontracting Plan No Limit

VOLUME II: TECHNICAL

Section 1: Software Development Plan (SDP) and Rationale (Factor 1)

SDP - No Limit SDP Rationale – Limit four (4) pages

Section 2: Software Development Experience (Factor 2) One (1) page Software Development Experience Matrix (Attachment 4);

Five (5) pages Per Attachment 4 - 1

Section 3: Past Performance (Factor 3) No Limit CPARS evaluations, if available, and past performance questionnaires (Attachment 4 - 2) https://ecommerce.sscno.nmci.navy.mil/ https://ecommerce.sscno.nmci.navy.mil/

Section 4: Small Business Commitment (Factor 4) No Limit Section 5: Systems Security Plan (SSP) (Factor 5) No Limit

VOLUME III: PRICE/COST PROPOSAL

Section 1: Attachment 4 - 3 Cost Summary Format No Limit Section 2: Attachment 4 - 4 Supporting Cost Data No Limit Section 3: Attachment 4 - 5 Labor Rate and Qualification No Limit

Information submitted in excess of the established page limits will not be read or evaluated. Page limits do not include cover sheets, table of contents, requirements compliance matrices, lists of figures, lists of drawings, lists of proprietary data, glossaries, tabs, dividers, or blank pages.

DO NOT INCLUDE PRICING INFORMATION IN ANY VOLUME OTHER THAN THE VOLUME I OFFER

DOCUMENTATION AND VOLUME III COST PROPOSAL. If pricing information is found in any other volume, the pricing information will be redacted from that volume prior to evaluation and, therefore, the redacted information will not be evaluated.

2.1.2.1 Format: The electronic proposal shall be prepared, so that if printed, be on 8-1/2" X 11" paper format with single-spaced typed lines, including figures, glossaries, table of contents and cover sheets.

Partial pages count as a full page. Type size shall be Times New Roman and no smaller than 12 point in the text, drawings, figures, and tables, and 10 point in spreadsheets (applicable to the Cost/Price Volume spreadsheets only). Foldouts may be used for tables, so that if printed be no larger than 11" by 17" paper format with single-spaced typed lines, type size Times New Roman and no smaller than 12 point. The foldout shall count as two pages. Standard margins shall be a minimum of one inch, excluding header and footer. The volumes shall contain a glossary of abbreviations and acronyms used and an explanation of each. No pen and ink changes are allowed.

2.1.2.2 Numbering: Pages shall be numbered consecutively within each section to indicate the volume, section, and page. For example, page 19 of Volume I, Section 3 would be numbered I-3-19. Pages in the Price/Cost Proposal volume shall be numbered consecutively.

3.0 PROPOSAL VOLUMES

The offeror must provide sufficient detail to substantiate the validity of all stated claims. An offeror’s proposal is presumed to represent their best efforts to respond to the solicitation. Proposals should be clear, concise and complete. Organization, clarity, accuracy of information, relevance, and completeness are of prime importance.

Sufficient supporting information shall be provided to allow the Government to evaluate the offeror’s approach.

Stating that the offeror understands and complies with this effort or paraphrasing the statements of the RFP is considered inadequate and unacceptable. Phrases such as: “Standard procedures will be employed” and “well known techniques will be used” are also considered inadequate. Elaborate brochures or other presentations beyond that sufficient to present a complete and effective proposal are not desired. Elaborate artwork and expensive visual or other presentation aids are not necessary and if such material is included in the proposal it will be included in the volumes page count.

Proposals shall correlate directly and sequentially with the following specific proposal preparation instructions.

Non-conformance to the instructions may cause rejection of the proposal. Proposals shall be complete and self-sufficient, relate exactly to what is requested and proposed, and strictly adhere to the requirements of this solicitation. Use of documentation by reference, and not incorporated into the proposal, will not be allowed. Where cross-referencing is used, the volume, attachment, exhibit and paragraph numbers, as appropriate, shall be referenced.

The required content for each volume section is described below

3.1 VOLUME I – OFFER. Completion of this volume is a company’s offer for contractual commitment, complete in every respect and ready for acceptance by the Government. The Government’s acceptance of the offer submitted by a company will create a binding contract between the parties. The offer shall be signed by a company official having authority to bind the company contractually.

3.1.1 Section 1: Cover Letter/Executive Summary. The offer shall include a cover letter on company letterhead and signed by an individual authorized to bind the company to the proposal. The cover letter shall acknowledge receipt of all amendments (if any are issued) to the RFP. The cover letter shall identify all enclosures being transmitted as part of the response to the RFP. The letter shall reference the RFP number and acknowledge that it transmits an offer in response to the RFP. It shall state: (1) Commercial and Government Entity (CAGE) number, (2) Data Universal Numbering System (DUNs) number, (3) Taxpayer Identification Number (TIN), (4) address(es) of the location(s) at which the offeror intends to perform the proposed effort, (5) state the name, address and telephone number of the cognizant Defense Contract Audit Agency (DCAA) audit office, (6) the name, address and telephone number of the cognizant DCMA office, and (7) a statement that the proposal is valid for no less than 210 calendar days after the closing date of this solicitation for receipt of offers. The above listed information (items 1-7) shall also be provided for all proposed subcontractors.

3.1.2 Section 2: Exceptions to the RFP. The offeror’s proposal shall include any exceptions to the provisions of the solicitation. The offeror shall clearly state the exceptions and provide references to the applicable RFP page, paragraph or exhibit line item number. The offeror shall provide a full explanation for all exceptions taken to the solicitation. Any material exceptions to the RFP may render the proposal unacceptable and ineligible for award. If the offeror takes no exceptions to the terms and conditions of this RFP, the offeror shall state their unconditional assent to all terms, conditions, and provisions included in the RFP within Volume 1.

3.1.3 Section 3: Signed SF33 with completed Sections B through K. The offeror’s proposal shall complete Sections B through K of the RFP and provide a signed SF33 acknowledging all amendments. Signature by the offeror on the Standard Form 33 constitutes an offer, which the Government may accept.

3.1.3.1 Completion of annual representations and certifications via System Award Management (SAM) is a requirement of solicitation provision 52.204-8, but it is not a sufficient response to Section K of the solicitation. All representations and certifications included in Section K must be completed, including DFARS provision 252.227-7017 which requires completion and signature even for a negative response.

3.1.4 Section 4: Proprietary Data Protection Agreement. Contractor support personnel from Booz Allen

Hamilton will be assisting the Government during source selection by providing administrative support.

This assistance will not include rating, evaluating or scoring of the proposal itself. Booz Allen Hamilton has signed a non-compete letter for the GPNTS program. Responses to this solicitation MUST clearly state whether permission is granted allowing Booz Allen Hamilton access to the offeror’s proposal.

Should such permission not be provided, the Government will review the offeror’s proposal without the administrative contractor support identified. Offerors are encouraged to execute a Proprietary Data Protection Agreement (PDPA) with this company. Subcontractors that provide proposal information separate from the prime contractor’s proposal submittal shall clearly state whether permission is granted allowing the contractor support identified above access to the subcontractor’s proposal. If previous PDPAs have been executed, the offeror shall state whether or not they are applicable under this solicitation. The point of contact for the company is listed below:

Company POC Contact Information BOOZ ALLEN HAMILTON Madison Pelky Email: pelky_madison@bah.com

Phone: 858-382-2442

3.1.5 Section 5: Contractor Responsibility Information. To aid in the determination of contractor responsibility, the following information is required:

(a) Information regarding the general financial condition of your firm and specific plans for financing the proposed contract, including the latest available financial statements. If you are currently being audited, or mailto:pelky_madison@bah.com have been audited by the DCAA, provide the address, current telephone number, and current point of contact for the cognizant DCAA and the cognizant Defense Contract Management Area Office (DCMAO).

(b) A listing of previous and/or ongoing experience in related areas. Include the contracting activity, program/item produced/services provided, contract number, current point of contact, current telephone number, duration of contract, type of contract and total dollar amount of contract. Please ensure information provided is current and up-to-date. If the offeror believes that the information provided under “Past Performance – Factor 3” adequately addresses the requirements of this provision, please state so here.

Repetition of the same information is not necessary.

(c) A summary of your:

(1) Accounting procedures and controls.

(2) Organization.

(3) Software control procedures.

(4) Property control system.

(5) Quality assurance programs.

(6) Equipment and facilities relative to this effort.

(d) If any subcontracting, provide the following information:

(1) Methodology for the selection of proposed subcontractors, if any, and the benefit they would bring to the arrangement.

(2) Analysis performed on the subcontractor’s cost proposal to determine a fair and reasonable price.

(e) A list of credit references, including suppliers. Provide company name, point of contact, and telephone number.

(f) Any other additional information that will assist in a better or complete understanding of your firm and capabilities.

3.1.6 Section 6: Systems and Compliances. The offeror shall provide documentation that demonstrates they currently have an adequate Accounting System, Estimating system, and Purchasing System. If available, the offeror shall include the report number and date of the cognizant DCAA or DCMA office's determination stating that the offeror's accounting system is adequate for the accumulation, reporting, and billing of costs (attach a copy of the report). If the offeror does not have a determination from DCAA or DCMA regarding its accounting system, the offeror shall provide documentation as to why its business systems have not been reviewed or why documentation cannot be provided, and justification as to the adequacy of their accounting system. In making the responsibility determination, the Government may pursue additional reviews of the offeror's business systems to determine adequacy.

3.1.7 Section 7: Organizational Conflict of Interest (OCI) Mitigation Plan(s). The offeror’s attention is directed to FAR Subpart 9.5 relating to organizational conflicts of interest. It is the Government’s intent to avoid, neutralize, or mitigate potential conflicts as early in the acquisition process as possible. The offeror shall submit draft versions of any required OCI Mitigation Plans, consistent with the guidance contained in FAR Subpart 9.5.

3.1.8 Section 8: Small Business Subcontracting Plan. Offerors, unless otherwise exempt, due to being a small business concern or a company performing outside of any State, territory, or possession of the United States, the District of Columbia, and the Commonwealth of Puerto Rico, shall, in accordance with FAR

19.7 and FAR 52.219-9, submit a Small Business Subcontracting Plan (or approved comprehensive plan), as part of Volume I. Failure to submit and negotiate a subcontracting plan acceptable to the Contracting Officer shall make the offer ineligible for award of a contract.

For this solicitation, the subcontracting plan (that is not an approved comprehensive plan) shall be calculated as a percentage of total contract dollars, in addition to the goals established as a percentage of total subcontract dollars as depicted in FAR 19.704(a)(2).

3.2 VOLUME II - TECHNICAL

Each offeror shall submit a written proposal in accordance with evaluation factors 1 through 5 below. No pricing information shall be included in the technical volume.

3.2.1 Factor 1 - Software Development Plan and Rationale:

The offeror shall submit a Software Development Plan (SDP) in conformance with SDP DID DI-IPSC- 81427B and SOW paragraph 3.5. In addition to the SDP, the offeror shall submit a SDP rationale addressing the following:

- Describe why the proposed SDP approach is appropriate for the development and sustainment of

GPNTS software

- Describe the proposed SDP’s process for developing and sustaining software using a Modular

Open Systems Approach (MOSA) while limiting proprietary, vendor unique, or closed elements

- Describe how the proposed SDP processes are, at a minimum, equivalent to those articulated by

CMMI® capability level 3

A concise SDP is preferred to a SDP that is excessively wordy and contains non-essential material/information. Refer to the page limitations of the SDP Rationale above in 2.1.2 Table 3 above.

3.2.2 Factor 2 - Software Development Experience:

The offeror shall describe its recent U.S. Federal Government contract experience performing software development and sustainment efforts corresponding to those required by this solicitation. A maximum of three (3) references may be submitted. The offeror shall submit one (1) Software Development Experience Matrix (Attachment 4), and for each reference, one (1) Reference Information Sheet (Attachment 4 - 1) that clearly describes how the efforts performed correspond to the requirements of the following GPNTS SOW Sections:

3.4.1 Configuration Management and Planning

3.5.5.1 Cybersecurity Engineering

3.5.8 Software Sustainment Support

3.5.10 Software Development

3.5.12 Software Testing

3.5.16.2 System Integration Testing

3.6.3 Military Code (M-Code) Integration Engineering Support

At least one (1) of the references shall be from the offeror (identified as the Prime offeror for this solicitation) as a prime, and no more than one (1) from any individual proposed subcontractor (for this solicitation). Experience information may also include predecessor companies.

Each Reference Information Sheet shall:

- Describe in block 14 the extent to which personnel who contributed to that particular effort are proposed to support the contract effort resulting from this solicitation.

- Describe whether, and to what extent, the Software Development Experience relates to sustainment and continued development of software code developed by another contractor.

- Describe whether, and to what extent, the Software Development Experience utilized the same or similar processes and approaches as proposed in the SDP for this solicitation.

- Describe experience with developing and sustaining software using Java, Linux, and Oracle.

- Describe CMMI® or equivalent model-based process maturity appraisals performed within the last 24 months prior to the issuance date of this solicitation. As a part of this description, offerors shall identify the organizational entity and location where the appraisal was performed, the type of evaluation, the organization performing the evaluation, and the level earned.

Provide the contract statement of work, highlighting the specific areas the offeror (Prime offeror for this solicitation and its proposed subcontractor(s)) performed.

Except for SOWs, the above information shall be provided within the space provided in each Reference Information Sheet. Additional Reference Information Sheet pages will not be evaluated.

“Recent” experience is defined as efforts performed (but not necessarily completed) within five (5) years prior to the issuance date of this solicitation.

3.2.3 Factor 3 - Past Performance

The offeror shall provide past performance information for each U.S. Federal Government contract reference submitted under Factor 2, Software Development Experience. The offeror shall submit the most recent Contractor Performance Assessment Reporting System (CPARS) or the Past Performance Information Retrieval System (PPIRS) evaluations associated with each reference submitted under Factor

2. The offeror shall ensure the references cited in blocks 9a and 9b of the Attachment 4-1 Reference Information Sheet submitted under Factor 2 are current and accurate.

Past performance information may also include predecessor companies who have past performance relevant to the requirements of this RFP.

Offerors that have no relevant record of past performance must submit a signed and dated statement to that effect. Offerors with no relevant past performance will receive a Neutral rating.

Completed questionnaire(s) for each reference submitted under Factor 2 which there is no CPARS or PPIRS evaluations shall be emailed DIRECTLY to kenneth.nickel@navy.mil before the closing date and time of this solicitation. Offerors shall not include completed questionnaires in their proposal. However, the Government reserves the right to evaluate questionnaires received after the due date of the solicitation.

The Government reserves the right to contact references for verification or additional information. The Government reserves the right to utilize other past performance information considered relevant that may be located in CPARS, other reporting systems, or obtained from sources other than those identified by the Offeror. This past performance information may be used for the evaluation of past performance.

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.

3.2.4 Factor 4 - Small Business Commitment (Large and Small Business Offerors) All prime offerors (Large AND Small Businesses) shall submit a completed RFP Attachment 10, Small Business Participation Data Form. Within Attachment 10, offerors also shall describe the extent to which they have identified and committed to provide for participation by Small Business Concerns with the below participation goals based on the Total Acquisition Value (TAV), (i.e., the total proposed cost plus fixed fee of this contract):

Small Business Categories Small Business Participation Goals

(Based upon % of Total Acquisition Value (TAV))

Total Small Business (includes the below) 12% Small Disadvantaged Business (SDB) 4% Woman-Owned Small Business (WOSB) 3% Historically Underutilized Zone (HUBZone) 1% mailto:kenneth.nickel@navy.mil

Veteran Owned Small Business (VOSB) 2% Service-Disabled Veteran Owned Small Business (SDVOSB) 2%

Within Attachment 10, offerors shall describe the tasks each Small Business subcontractor will perform and how the tasks assigned to Small Businesses are meaningful to the overall success of the program.

Offerors shall also provide documentation (copies of subcontracts, letters of intent) to demonstrate commitment to the small business concerns.

Offerors shall also provide evidence of the extent to which they have met small business subcontracting goals on previous contracts. To demonstrate previous goal achievement, the offeror shall submit its two (2) most recently filed Individual Subcontract Reports (formerly SF 294) or other documentation for all prime offeror contracts cited in Factor 2, Software Development Experience. If ISRs are unavailable, offerors may submit other documentation to establish their record of Small Business goal achievement. ISRs for proposed subcontractor experiences listed in Factor 2 are not required. If, historically, the offeror did not meet or exceed small business goals, the offeror shall provide a detailed explanation addressing why goals were not met and what actions will be taken to meet the goals on this effort. Summary Subcontractor Reports (SSRs) (formally SF 295) are not required for subcontractor experiences cited in Factor 2.

3.2.5 Factor 5 – System Security Plan

The offeror shall provide a Systems Security Plan (SSP) as referenced in SOW 3.5.5.2 that implements the security requirements in Defense Federal Acquisition Regulation Supplement (DFARS) Clause 252.204- 7012 and:

(1) Fully implements Multi-factor authentication, including authentication and authorization of users in a manner that is auditable;

(2) Fully implements FIPS 140-2 validated encryption;

(3) Employs the principle of least privilege or “need to know”;

(4) Requires user privileges be reviewed at least annually in a manner that can be audited;

(5) Requires monitoring and controlling remote access sessions and include mechanisms to audit sessions and methods; and

(6) Implements at a minimum, all security requirements in NIST 800-171 (Rev.1) standards 3.1 to

3.14; or ensure that any unimplemented security requirements have been adjudicated by an authorized representative of the DoD Chief Information Officer (CIO) to be non-applicable or to have an alternative, but equally effective security measure in its place, and provide proof of such adjudication by DoD CIO.

3.3 VOLUME III – PRICE/COST PROPOSAL.

(a) This volume shall contain price/cost information only. The guidelines and requirements in this section are provided to (1) aid offerors in preparing their price/cost proposal; and (2) aid the Government in reviewing and evaluating the offeror’s price/cost proposal. The Government’s intent is to provide instructions that will allow the offeror to develop clear, concise, and comprehensible proposals and to minimize the need to enter into discussions in order to obtain additional data. This volume shall not contain any information related to any of the other evaluation factors.

This is a competitive acquisition and adequate competition is anticipated. The supporting cost documentation requested is not considered certified cost or pricing data and shall not be certified in accordance with FAR 15.403-5. However, if after receipt of proposals the PCO determines adequate competition does not exist, the PCO reserves the right to conduct negotiations and obtain certified cost or pricing data pursuant to FAR Part 15.

By submitting a proposal, the offeror grants the PCO, or an authorized representative, the right to examine records that form the basis of the proposal. This examination and review may take place at any time before award.

(b) A Cost-Plus-Fixed-Fee (CPFF) and Cost Only (for ODCs) proposal shall be submitted in response to this solicitation. Offerors and all proposed subcontractors shall ensure their cost proposals are submitted in accordance with RFP Attachment 4 - 3, Cost Summary Format and RFP Attachment 4 - 4, Supporting Cost Data, with MS Excel format/formulas intact. Offerors shall breakout and identify each cost element separately for each year of the contract (first year beginning on the anticipated date of award stated in Section F) and on a cumulative basis for all years.

The Government Estimate for this procurement was developed using the following inputs: 1) the incumbent’s delivered rates, 2) delivered rates from other SPAWAR Software Sustainment Contracts, and

3) escalation of labor rates in each year for inflation.

On the basis of these inputs, the Government Estimate for fully burdened labor over 10 years on this procurement falls within the range of $95M to $110M, which is considered a realistic range for the work to be performed under this contract. Offeror’s proposing below this range maybe considered realistic if adequately substantiated.

(c) Estimated Level of Effort

The quantities of labor hours for each labor category shown below, which are to be used by the offeror for computing total labor costs, represent the Government’s current best estimate of requirements. The Government, however, cannot guarantee, upon award, the estimated quantities of man-hours shown below for individual labor categories nor the total estimated hours. If an offeror does not propose the level of effort specified below, the offer may be considered unacceptable. However, additional labor categories and corresponding hours, if required as direct costs by the offeror’s accounting system or disclosure statement, may be proposed in excess of the Government specified labor mix. In the event the offeror proposes labor categories and hours in addition to those required below, the offeror shall provide an accompanying narrative explanation (including the offeror’s disclosure statement) of the additional categories/hours.

Offerors shall use the labor categories provided by the Government below in the preparation of their RFP Attachment 4 - 3, Cost Summary Format. In the event the offeror’s labor category designations do not align precisely with the Government labor category designations, offerors shall provide a cross reference to the Government labor categories. In order to permit a comparison between the labor categories specified below and the offeror’s labor categories, the Prime offeror must complete RFP Attachment 4 - 5, Labor Rate and Qualification, for all proposed personnel in accordance with (d) below.

For evaluation purposes, the Government will apply any identified telework hours with the offeror’s Contractor Site rate, and adjust to the Contractor Site rate, if necessary during cost realism analysis.

CLIN 0001 CLIN 1001 CLIN 2001

Labor Category Total Yr. 1 Yr. 2 Yr.3 Yr. 4 Yr. 5 Yr. 6 Yr. 7 Yr. 8 Yr. 9 Yr. 10 Program Manager 19,200 1,920 1,920 1,920 1,920 1,920 1,920 1,920 1,920 1,920 1,920 Program Manager (EVM)* 19,200 1,920 1,920 1,920 1,920 1,920 1,920 1,920 1,920 1,920 1,920 Senior Software Engineer 37,440 3,840 3,840 3,840 3,840 3,840 3,840 3,840 3,840 3,840 2,880 Agile SCRUM Master 63,360 5,760 9,600 9,600 9,600 5,760 5,760 5,760 3,840 3,840 3,840 Software Developer 157,248 16,224 39,360 14,592 15,744 15,360 7,680 15,360 15,360 9,408 8,160 Software Test Engineer 62,112 5,760 11,520 11,520 11,520 7,392 3,840 3,840 2,880 1,920 1,920 System/Software Requirement Engineer 47,040 5,760 7,680 7,680 7,680 3,840 3,840 3,840 2,880 1,920 1,920 Hardware Engineer 19,200 1,920 1,920 1,920 1,920 1,920 1,920 1,920 1,920 1,920 1,920 Technician 19,200 1,920 1,920 1,920 1,920 1,920 1,920 1,920 1,920 1,920 1,920 Cybersecurity Engineer 28,800 2,880 2,880 2,880 2,880 2,880 2,880 2,880 2,880 2,880 2,880

CM/QA Engineer 25,920 2,880 2,880 2,880 2,880 2,880 2,880 2,880 1,920 1,920 1,920 Total Per Year 498,720 50,784 85,440 60,672 61,824 49,632 38,400 46,080 41,280 33,408 31,200

*EVM – Earned Value Management. EVM requirements are based on the estimated ceiling of the total IDIQ contract and then are applied to the individual task orders, or group(s) of related task orders, that meet or are expected to meet the conditions of contract type, value, duration, and work scope. EVM requirements will be tailored at the task order level based on the task order value and reporting requirements.

(d) Labor Category Qualifications

All named personnel shall be listed to include how each named person meets the required labor category qualification information listed in Attachment 4 - 5, Labor Rate and Qualification. At a minimum, offerors shall complete the table for each named and contingent hire employee. For To Be Determined (“TBD”) employees, offerors may submit one line per labor category where the offeror is proposing labor category averages for employees with the same qualifications and rates; otherwise, Offerors shall submit a separate line for each TBD employee with different qualifications and/or rates, as applicable.

Attachment 4 - 5, Labor Rate and Qualification shall be completed and provided by the Prime offeror in Microsoft Excel format. PDF versions of Attachment 4 - 5 are not acceptable. Only one Attachment 4 - 5 shall be provided by the Prime offeror that includes data for both the Prime offeror and any proposed subcontractors. Only Prime offeror direct labor rates shall be provided in Attachment 4 - 5; subcontractor direct rates may be left blank. Offerors shall follow the instructions for completing Attachment 4 - 5 provided under the first tab of Attachment 4 - 5, Labor Rate and Qualification.

(e) Direct Labor Rates

The straight time hourly direct labor rates shall use a forty-hour week for the conversion of salaried employees to the hourly basis and shall be exclusive of loading factors; e.g., vacation, sick leave, holidays, overhead, G&A, and fee. Offerors shall ensure that they utilize the annual salary divided by 2,080 hours to equal the unloaded direct hour labor rate. Offerors (Prime and all Subcontractors) shall identify on Attachments 4 - 5 (Labor Rate and Qualification) and 4 - 3 (Cost Summary) the Current Actual Labor Rates. Offerors shall specify whether or not uncompensated overtime is included in their proposal for the Prime and all Subcontractors.

In order to verify the realism of the offeror’s proposed direct labor rates all Offerors (including proposed subcontractors) shall submit, as part of their Cost Proposal, documentation substantiating the accuracy of their proposed direct labor rates. Offerors shall ensure consistency between proposed direct labor rates and supporting documentation. Acceptable documentation may include the following:

(1) Current fiscal year direct labor rate information as a Forward Pricing Rate Agreement (FPRA) on file with DCMA.

(2) Payroll data (if proposing current, named employees).

(3) Copies of signed Letters of Intent that indicate agreed upon annual salary and proposed start date (if proposing named, new hires).

(4) Copies of current or prior fiscal year DCMA FPRA or Forward Pricing Rate Recommendation

(FPRR).

(5) Labor Category Averages. If labor category averages are used as consistent with the offeror’s accounting practice and approved by DCAA, offerors shall provide a detailed narrative and include the calculation used to establish the category average. For example, provide a list of the current salaries for all employees working in that labor category, divided by the number of current employees in that labor category. In accordance with Section M, the Government reserves the right to use other methodologies for comparison if determined more realistic.

(6) For proposed rates that do not fall within one of the above criteria, offerors shall provide a detailed, comprehensive description of the methodology used to establish the proposed direct rate. The description shall include both the source where the rate was obtained and a description of how the resulting rate was calculated. Merely stating a “salary survey” or “market survey” was used is not sufficient. Offerors shall include a detailed description which includes the recognized national/regional compensation surveys and studies of professional, public, and private organizations used in establishing the total compensation structure.

(f) Direct Labor Escalation

Offerors shall provide copies of current or prior fiscal year FPRA, FPRR, or DCAA/DCMA field pricing assistance reports, if available. If FPRAs, FPRRs, or DCAA/DCMA field pricing assistance reports are unavailable, offerors shall provide rationale for proposing any rate below 2%. Rationale shall include detailed forecast information, historical information, and any other relevant information. Offerors proposing lower direct labor escalation rates in the option years risk a cost realism adjustment if the rationale is insufficient and the lower rates are determined to represent a cost risk.

(g) Indirect Rates

If current supported indirect data (e.g., FPRA, FPRR or DCAA audit of the offeror's indirect rates) are not available or do not exist, historical indirect data, to include actual incurred rates, annual incurred cost claims (if submitted), and provisional rates for the three (3) years prior to the offeror’s current fiscal year, shall be submitted with the proposal in addition to completing Attachment 4 - 4, Supporting Cost Data. If a proposed indirect rate (for the base or option periods) is more than 5% below the three-year historical actual incurred average, offerors shall provide a supporting narrative describing the basis for the discrepancy between the historical information and proposed rate. For example, where the three-year historical actual incurred average is 30%, a proposed rate below 25% would require a supporting narrative.

Information provided shall be consistent with the offeror’s disclosed accounting practices and shall identify how the rates were derived. Offerors shall identify the basis for the various cost elements for which each rate is applied.

Fringe: If applicable and in accordance with the Offerors’ normal accounting procedures, Offerors shall identify the fringe benefit rate(s) and total fringe benefit cost being proposed and identify the cost elements for which the fringe benefit rate is being applied.

Overhead (OH): In accordance with the offeror’s normal accounting procedures, offerors shall identify the current and projected overhead rate(s) and total overhead cost being proposed under this solicitation and identify the cost elements for which overhead is being applied. If applicable, identify overhead rates separately for Government-site and Contractor-site.

General & Administrative (G&A): Offerors shall identify the G&A rate(s) and the total G&A cost proposed and identify the various cost elements for which the G&A rate is being applied.

Material & Subcontractor (M&S): Offerors shall identify the M&S rate and the total M&S cost proposed and identify the various cost elements for which the M&S rate is being applied.

Facilities Capital Cost of Money (FCCOM): If FCCOM is proposed, offerors shall submit a completed DD Form 1861 entitled “Contract Facilities Capital Cost of Money” and include documentation supporting the computations with the form.

(h) Fee

Identify the fee rate, the total amount proposed for all years, the total amount per year, and the various cost elements on which the fee is being applied. Do not propose fee on FCCOM, Other Direct Costs (ODCs), or on any indirect costs that are applied to ODCs.

(i) Other Direct Costs (ODCs)

The Government’s best estimate of Other Direct Costs (ODCs) is set forth below. The Government cannot guarantee either the amount for each CLIN or the total estimated amount. Offerors shall include ODCs EXACTLY as specified below. It is anticipated that ODC costs will consist mainly of travel and incidental material costs. Separate lines in the proposal shall identify all indirect rates applied to ODCs. Total ODCs in the proposal represent the sum of the exact ODC values stated below and all indirect costs. Offerors shall not propose fee on ODCs.

CLIN Amount 0002 $1,425,000.00 1002 $855,000.00 2002 $570,000.00

(j) Subcontractors

Prime offerors shall provide a list of all proposed subcontractors by name and specify the type of subcontract (e.g., CPFF, FFP or T&M). Subcontractors with an accounting system adequate for a cost reimbursement type contract should be proposed as CPFF. Subcontractors that do not have an adequate accounting system should be proposed as FFP type or T&M. For each FFP or T&M subcontract proposed, Offerors shall explain in writing why no other contract type is appropriate. The offeror (Prime) shall also provide: (1) Analysis performed on the subcontractor’s cost proposal to determine a fair and reasonable price (see clause 52.244-2); (2) Small Business Subcontracting Plan (if applicable) and (3) If the proposal contains a “contractor team arrangement” as defined in FAR 9.601, information that describes the contractor team arrangement to include any information that will help the Government understand the contractor team arrangement purpose and benefit.

If subcontractors are proposed, each subcontractor shall submit the same detailed level of cost information as the Prime Offeror, regardless of subcontract pricing structure. Subcontractor cost information shall not be submitted via email to the Government. Subcontractor cost information may be submitted by the Prime Offeror, or subcontractors may submit cost information under separate cover via the SPAWAR E-Commerce web-site; see Section L provision Instructions to Offerors. Cost data provided separately by a proposed subcontractor must be received prior to the time and date specified for receipt of proposals and is subject to the same submission requirements of 52.215-1.

The offeror’s attention is directed to Clause Limitations on Subcontracting (Dec 1996) (52.219-14).

Offerors shall ensure their proposals are in accordance with the clause.

(k) Compensation Plan

Prime offerors and all proposed subcontractors shall submit separate total compensation plans describing the non-salary/direct labor compensation of the employees identified in the proposal. Offerors may submit a company-wide plan where all proposed employees are covered by the same compensation plan.

However, where employees are covered by different compensation plans, offerors shall submit all of compensation plans applicable to the personnel proposed under this solicitation. Offerors shall submit supporting information, including data used in establishing the total compensation structure. Offerors are encouraged to review 52.222-46 for further detail regarding the compensation plan.

(l) Uncompensated Overtime and Professional Employees

Proposals that include hourly rates for exempt employees which are based on more than a 2,080 work-year shall be identified as Uncompensated Overtime as defined in provision at FAR 52.237-10, “Identification of Uncompensated Overtime.” If an offeror decides to include uncompensated effort in their proposal, the following requirements shall be met and reflected in the proposal:

1) The offeror must have an established cost accounting system that is adequate for determining costs applicable to the contract, and that records all hours worked, including uncompensated hours, for all employees, and regardless of contract type. The contracting officer is required to make an affirmative determination regarding the adequacy of the offeror’s accounting system prior to the award. If the contracting officer is unable to make such a determination, the offeror will be ineligible for contract award.

2) Uncompensated hours, for all employees, and regardless of contract type, shall be included in the offeror’s base for allocation of indirect costs and meet the requirements of Cost Accounting Standard (CAS) 418, “Allocation of Direct and Indirect Costs.”

3) The proposal shall clearly identify hours of uncompensated effort proposed by labor category.

4) The proposal shall clearly identify the amount of uncompensated effort that will be performed without supervision and without support personnel and shall assess the productivity of such effort.

Additionally, clearly identify the means by which the offeror controls or schedules uncompensated overtime for its employees as well as where the uncompensated effort will be accomplished.

5) The proposal shall describe the extent to which employees are required or encouraged to perform uncompensated effort and the impact the use of uncompensated effort has on work effectiveness.

6) The proposal shall include a copy on the corporate policy addressing the uncompensated effort.

7) The proposal shall include a separate, complete cost breakdown to the same level of detail as the breakdown supporting the cost proposal. The breakdown shall include direct labor rates for all direct labor categories based on the division by 2,080 of exempt employees’ actual annual salary, to represent a standard (as deemed by Fair Labor Standards Act) 40-hour week or 2,080-hour standard year. In addition, the breakdown shall include overhead rates and other costs based on employees working a standard 40-hour workweek or a 2,080-hour standard year. It is the cost breakdown that will be used to perform the cost realism portion of the proposal evaluation.

8) The requirements stated in paragraph (1) through (7) above shall be met for each subcontract which has uncompensated effort included in the proposal.

(m) Accounting System

Offerors are advised that they must have an adequate accounting system for determining costs applicable to this cost reimbursement contract in order to be eligible for award. If available, offerors shall provide a copy of the report from the cognizant DCAA or DCMA office stating that the offeror’s accounting system is adequate for accumulation, reporting, and billing of costs under a cost reimbursement contract.

(n) Purchasing and Estimating System

Offerors shall provide a status of their purchasing and estimating system. Offerors shall provide a copy of the report from the cognizant DCAA or DCMA office as supporting documentation, if available.

(o) Contract Data Requirements List. Data is Not Separately Priced (NSP) so CLIN shall be proposed EXACTLY as follows:

CLIN Amount

0003 NSP

1003 NSP

2003 NSP

The costs associated with producing the contracted data items (CDRLs) should be included in the supporting CLINs.

(End of provision)

L-349 SUBMISSION OF ELECTRONIC PROPOSALS (SEP 2003)

(a) Offerors shall submit their proposals electronically to SPAWAR no later than 1400 San Diego local time on 21

December 2018 under the instructions contained in this provision. Offerors shall submit their signed proposals as Portable Document File (PDF) documents. Electronic copies shall be submitted via the SPAWAR E- Commerce Central (SPAWAR E-CC). Offerors submitting electronic proposals (e-Proposals) shall register in the SPAWAR E-CC and select their own password in order to submit a proposal.