N66001-17-R-0067-0002 conformed.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local time 26 Sep 2017

X

A

X B

X C X D

EX

X

G

F 63 - 71

72 - 85

X H 86 oralee.martin@navy .mil

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA

FAR (48 CFR) 53.214(c)

1 90

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

N66001 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 1 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and

See Clause L-TXT-38 conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

ORALEE MARTIN 619 553-5347

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

1 - 5

6 - 10

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

11 - 26

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 30 - 34 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 35 - 46 X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIO NS AND INSTRUCTIO NS

PART III - LIST O F DO CUMENTS, EXHIBITS AND O THER ATTACHMENTS

47 - 61

PART II - CO NTRACT CLAUSES

SPAWAR SYSTEMS CENTER PACIFIC

ORALEE MARTIN, CODE 22710

ORALEE.MARTIN@NAVY.MIL

53560 HULL STREET

SAN DIEGO CA 92152-2001

FAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

24 Aug 2017

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N6600117R0067

Section SF 30 - BLOCK 14 CONTINUATION PAGE

QUESTIONS & ANSWERS

AMENDMENT 0002 Q&A

Question 1: Please explain how the Government will determine TBD in the following from the RFP "The combined/overall ceiling for all awardees under this Multiple Award Contract is $ TBD; however, no MAC awardee can exceed the value of its contract maximum quantity."

Answer: The combined/overall ceiling for all awardees under this Multiple Award Contract will be based on whichever value is higher between (1) the Government Estimate, and (2) the highest single contract value.

Question 2: Will the government move the due date to September 29th?

Answer: No.

AMENDMENT 0001 Q&A

Question 1: Please confirm that Past Performance Questionnaires are only required if a CPAR is not available.

Answer: Confirmed. Reference Section L-TXT-12 Submission of Proposals, paragraph 3.3 (b);

Attachment #7 Past Performance Questionnaires are only required if a CPARS is not available.

Question 2: The labor categories listed in Column A of Attachment 2 do not match the labor categories provided in Attachment 3 and in the table found on page 73 of the solicitation. The offeror is unable to modify the text in Column A to show the correct labor categories being proposed in accordance with the solicitation. Please provide an updated Attachment 2.

Answer: See Amendment 0001; a revised Attachment 2 Rate Sheet is provided.

Question 3: Per page 80 of the solicitation, section titled L-TXT-38 - SUBMISSION OF ELECTRONIC

PROPOSALS JUN 2017 for Volume 2 requires volume I, II, and III submitted as a pdf file. Does each sheet in

Attachment 2 need to be included as a PDF?

Answer: As stated in L-TXT-38 - SUBMISSION OF ELECTRONIC PROPOSALS paragraph (a), Volume II requires a PDF version of Volume II Price/Cost Information and a Microsoft Excel or compatible format version of Volume II Price/Cost Information. Volume II consists of a Cost Proposal which may contain additional sheets and Attachment 2 Rate sheet (each prime offeror and subcontractor shall complete and submit one copy of the Attachment 2 Rate Sheet table).

Question 4: For Attachment 2 will the Government provide instructions for Sheet 2?

Answer: See L-TXT-12 paragraph 2.1(e)(6) with regard to RFP Attachment 2. This attachment includes instructions for completion. No instructions are needed for Sheet 2, which lists the labor categories used in Column A of Sheet 1.

Question 5: Please confirm if the offeror is allowed to add additional sheets to Attachment 2 to provide the cost data required in Section L i.e., section 2.1, 2.6.

Answer: The SECOND VERSION of the Cost Proposal (Microsoft Excel or compatible format) may contain additional sheets. In addition, each prime offeror and subcontractor shall complete ONE copy of

Attachment 2 Rate Sheet in Microsoft Excel or compatible format). Reminder: the first version of Volume II

(Cost Proposal and Attachment 2 Rate Sheet) is to be submitted in PDF format.

Question 6: Will Government provide a two week extension based on the clarification required for Attachment

2 and the desired personnel qualifications?

Answer: No. The RFP closing date remains 26 September 2017.

Question 7: Attachment 3, Desired Personnel Qualifications appears to have an error for the Financial Analyst and Administrative Analyst. Each of these labor categories includes requirements for instructors. Will the government update these labor categories to reflect the requirements in the SOW?

Answer: See revised Attachment 3 Desired Personnel Qualifications provided in Amendment 0001.

The requirements for instructors are deleted.

Question 8: Section L, paragraph 3.2 requires references for work performed by the prime offeror. If the prime offeror has no references, as in the case of a newly formed Joint Venture, will references performed by one of the JV members suffice, or should it be a reference from the Joint Venture itself

Answer: Per 13 CFR 125.8(e), the evaluation of past performance will consider work done individually by each partner to the joint venture as well as any work done by the joint venture itself previously.

Question 9: When evaluating the proposal of a Joint Venture, will the past performance of each JV member be considered the past performance of the “prime” contractor?

Answer: Yes, if the Joint Venture is proposed as the prime contractor. Also see the response to

Question #8 above.

Question 10: Are both populated and unpopulated JVs permitted as part of this solicitation?

Answer: Joint Ventures may not be populated with individuals intended to perform contracts awarded to the joint venture (see 13 CFR 121.103(h)).

Question 11: In Section F of the Government RFP for N66001-17-R-0067 the period of performance is listed as

2 years for the Base Period and 3 years for the Option Period; in Section L of the RFP on pages 73 & 74 the hours and ODCs are listed as 3 years for the Base Period and 2 years for the Option Period. Would the Government please confirm the correct Base and Option Year period of performance.

Answer: The Base period is two years; the Option period is three years. See Amendment 0001.

Question 12: The Government provided Attachment 7 – Past Performance Questionnaire in pdf format; would the Government consider providing the attachment as a word document or can offeror’s convert it to word format?

Answer: The Government will provide a word format version. See RFP attachments at SPAWAR e-cc.

Question 13: What is the incumbent current support regarding facilities, administration, office space, computers

- SIPR/NIPR access at SSC/LA (i.e. permanent/visiting contractors)?

Answer: The current incumbent support at SSC Pacific includes designated work spaces while at SSC

Pacific. This includes access to the SSC Pacific Division Code 523's laboratory work areas to execute specific tasking related to testing and access to non-laboratory work spaces for all other tasking not performed at the contractor's facility. The Government's best estimate for the place of performance at SSC Pacific is 65%.

Office space, computers (SIPR/NIPR), administration are not provided, unless there is a bona fide need and would be identified in individual task orders. Support at the LA AFB is estimated to be 10% and would consist of meeting support for SSC Pacific employees.

Question 14: Regarding SOW para. 3.5.7, Information Repositories: Will all hardware/systems be provided as

GFE?

Answer: GFP, GFE and GFI, if deemed necessary will be specified at the Task Order level. It is anticipated that repositories will be on Government computers/servers in Government spaces. Contractor will been given access to these computers/servers as required to successfully complete tasking.

Question 15: Regarding SOW para. 3.2, 3.2.4 Laboratory Enhancements/Procedures: Will all the government furnished equipment (GFE) required for laboratory operations be made available to the contractor for the full period of performance and be maintained by the government.

Answer: GFP, GFE and GFI, if deemed necessary, will be specified at the Task Order level and provided for the full performance of the Task Order.

Question 16: What percentage of equipment, if any, will not be GFE and, if so, will it be the responsibility of the contractor to provide and maintain?

Answer: Any Contractor Furnished Equipment (CFE), if deemed necessary, will be specified at the

Task Order level.

Question 17: Regarding SOW para. 6.0, Government Furnished Property, Equipment and Information: How much lead time will be made available to the contractor at the Task Order Level?

Answer: The contractor will be made aware of the requirement during the task order RFP process.

GFE, if available to the government, would be provided at the time of award.

Question 18: In L-TXT-12 the solicitation states that there is a page count for Volume III without any page count for a Volume Cover and Table of Contents. Does Volume III require or allow a Cover and Table of Contents and Cover separate from the specified page count?

Answer: If desired Volume III may include a Cover and / or Table of Contents in addition to the specified page count. Nothing written in the table of contents or cover will be considered in the evaluation of offeror proposals

Question 19: Page 73: Section L 2.3 (a): Accordingly, in order to permit a rapid comparison between the anticipated labor team shown below and the offeror’s actual labor mix, each proposal must provide the following:

“(1) A statement of the offeror’s normally used nomenclature for each labor category included herein, together with a copy of the offeror’s position description for each labor category. Attachment 3, “Desired Personnel

Qualifications,” is provided to offerors for use as a guide in the preparation of cost proposals. The qualifications identified in Attachment 3 represent the Government’s estimation of the knowledge and experience necessary for successful contract performance.”

Request confirm that the offeror proposes is only required to submit a position description for LCATs that are different from the Government LCATS and that no position descriptions need to be submitted if the offeror proposes the Government labor categories.

Answer: The offeror is to provide a statement of its normally used nomenclature for each labor category proposed herein, together with a copy of the offeror’s position description for each labor category.

If the labor category nomenclature and/or position description proposed by the contractor are identical to the

Government’s labor category nomenclature and position description of knowledge and experience estimated for successful contractor performance, the contractor shall so state in the proposal submission for each labor category. No further information is requested for labor categories where the oferor indicated that the labor category nomenclature and/or position description proposed by the contractor are identical to the

Government’s labor category nomenclature and position description.

Question 20: Attachment 1 DD254 block 1b indicates Level of Safeguarding Required NONE, implying that personnel working at contractor site will not require contractor site access to classified material. Request confirmation that this is correct.

Answer: Attachment 1 DD254 block 1b is correct.

Question 21: Attachment 3 indicates the personnel qualifications are “desired.” How will the government ensure cost realism in view of this?

Answer: The Government shall evaluate the cost factor in accordance with M-TXT-06-Evaluation

Criteria and Basis for Award, specifically M-TXT-06 (d) and 2.0 Cost.

Question 22: Attachment 3 indicates Secret level security clearances are “desired” not “required.” Request confirmation.

Answer: The lack of a clearance would restrict the contractor from executing task orders that require access to classified information.

Question 23: In PWS 1.1: Within the Scope, it states: “develop/leverage a range of miniaturized and scalable

PNT solutions for small–unit manned and/unmanned platforms.” Where will this development and leveraging occur within the Acquisition process/phase?

Answer: Reference Paragraph 3.1, PNT Technology Gaps where the contractor shall investigate PNT gaps, user requirements and operational requirements. The contractor shall conduct analysis of these gaps and requirements and identify innovative/emergent PNT technology applications to address the technology gaps and requirements to satisfy Urgent Operational Needs (UONs), user needs, and other warfighting deficiencies. Tasking, if required, will be specified at the Task Order level.

Question 24: Several of the Desired Labor Qualifications do not seem to match the Labor Category. Can the government review the below five (5) labor category qualifications for accuracy against the PWS? (1)Logistics

Analyst: This qualification looks like a Technical Writer Qualification; (2) Financial Analyst: Is the Finical Analyst required to have all these Instructor/Facilitator qualifications?

(3) Administrative Analyst: This qualification looks like a Training Analyst qualification; (4) Engineering

Technician: This also looks like a Training Analyst qualification; and (5) Technical writer: This qualification looks like a Logistics Analyst qualification.

Answer: See revised Attachment 3 Desired Personnel Qualifications provided in Amendment 0001.

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 Lot Engineering Services

CPFF

Base period of two years. Provide services in accordance with the Statement of

Work, Section C, as specified in individual task orders.

FOB: Destination

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

0002 Lot Other Direct Costs (ODC)

COST

Base period of two years. ODC including but not limited to travel, materials, and equipment.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and

Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

0003 Lot Data-Base Period-Not Separately Priced

0004 Lot OPTION Engineering Services

CPFF

Option period of three years. Provide services in accordance with the Statement of Work, Section C, as specified in individual task orders.

FIXED FEE

TOTAL EST COST + FEE

0005 Lot Other Direct Costs (ODC)

COST

Option period of three years. ODC including but not limited to travel, materials, and equipment.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and

Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

OPTION

0006 Lot OPTION Data-Option Period-Not Separately Priced

CLAUSES INCORPORATED BY FULL TEXT

B-TXT-01 PAYMENT OF FIXED FEE (COMPLETION TYPE) (JUN 2017)

***This clause shall be used in completion type task orders.***

FIXED FEE: $*. The Government shall make payment to the Contractor when requested as work progresses, but no more frequently than biweekly, on account of the fixed fee, equal to ** percent of the amounts invoiced by the

Contractor under the “Allowable Cost and Payment” clause hereof for the related period, subject to the withholding provisions of paragraph (b) of the “Fixed Fee” clause. In the event of discontinuance of the work in accordance with clause of this contract entitled “Limitation of *** the fixed fee shall be redetermined by mutual agreement equitably to reflect the diminution of the work performed; the amount by which such fixed fee is less than, or exceeds payments previously made on account of fee, shall be paid, or repaid by, the Contractor, as the case may be.

*To be completed upon award of the contract

**To be determined at the Task Order level. The allowable fee percentage will be negotiated at the Task

Order level, and shall not exceed the percentage proposed at the basic contract level.

***To be determined at the Task Order level.

(End of clause)

B-TXT-04 LEVEL OF EFFORT--FEE ADJUSTMENT FORMULA (JUN 2017)

***This clause shall be used in term/level-of-effort task orders.***

(a) Subject to the provisions of the “Limitation of Cost” or “Limitation of Funds” clause (whichever is applicable to this contract), it is hereby understood and agreed that the fixed fee is based upon the Contractor providing the below listed number of staff-hours of direct labor, hereinafter referred to as X, at the estimated cost and during the term of this contract specified elsewhere herein:

[Contracting officer insert number of estimated direct labor staff hours]

CLIN Total Staff-hours of Direct Labor (X)

The Contractor agrees to provide the total level of effort specified above in performance of work described in

Sections “B” and “C” of this contract. The total staff-hours of direct labor shall include subcontractor direct labor hours for those subcontractors identified in the Contractor’s proposal as having hours included in the proposed level of effort.

(b) Of the total staff-hours of direct labor set forth above, it is estimated that [Contracting officer insert number of estimated direct staff hours identified as competitive (uncompensated overtime) hours] staff-hours are competitive time (uncompensated overtime). Competitive time (uncompensated overtime) is defined as hours provided by personnel in excess of 40 hours per week without additional compensation for such excess work. All other effort is defined as compensated effort. If no amount is indicated in the first sentence of this paragraph, competitive time

(uncompensated overtime) effort performed by the contractor shall not be counted in fulfillment of the level of effort obligations under this contract.

(c) Effort performed in fulfilling the total level of effort obligations specified above shall only include effort performed in direct support of this contract and shall not include time and effort expended on such things as local travel from an employee’s residence to their usual work location, uncompensated effort while on travel status, truncated lunch periods, or other time and effort which does not have a specific and direct contribution to the tasks described in Section B.

(d) It is understood and agreed that various conditions may exist prior to or upon expiration of the term of the contract, with regard to the expenditure of labor staff-hours and/or costs thereunder which may require adjustment to the aggregate fixed fee. The following actions shall be dictated by the existence of said conditions:

(1) If the Contractor has provided not more than 105 % of X or not less than 95 % of X, within the estimated cost, and at the term of the contract, then the fee shall remain as set forth in Section B.

(2) If the Contractor has provided X-staff-hours, within the term, and has not exceeded the estimated cost then the Contracting Officer may require the Contractor to continue performance until the expiration of the term, or until the expenditure of the estimated cost of the contract except that, in the case of any items or tasks funded with

O&MN funds, performance shall not extend beyond 30 September. In no event shall the Contractor be required to provide more than 105 % of X within the term and estimated cost of this contract. The fee shall remain as set forth in Section B.

(3) If the Contractor expends the estimated cost of the contract, during the term of the contract and has provided less than X staff-hours, the Government may require the Contractor to continue performance, by providing cost growth funding, without adjusting the fixed fee, until such time as the Contractor has provided X staff-hours.

(4) If the Contracting Officer does not elect to exercise the Government’s rights as set forth in paragraph

(d)(2) and (d)(3) above, and the Contractor has not expended more than 95 % of X staff-hours, the fixed fee shall be equitably adjusted downward to reflect the diminution of work.

(5) Nothing herein contained shall, in any way, abrogate the Contractor’s responsibilities, and/or the

Government’s rights within the terms of the contract provision entitled “Limitation of Cost” or “Limitation of

Funds” as they shall apply throughout the term of the contract, based upon the total amount of funding allotted to the contract during its specified term.

(e) Within 45 days after completion of the work under each separately identified period of performance hereunder, the Contractor shall submit the following information in writing to the Contracting Officer with copies to the cognizant Contract Administration Office and DCAA office to which vouchers are submitted:

(1) The total number of staff-hours of direct labor expended during the applicable period.

(2) A breakdown of this total showing the number of staff-hours expended in each direct labor classification and associated direct and indirect costs.

(3) A breakdown of other costs incurred.

(4) The Contractor’s estimate of the total allowable cost incurred under the contract for the period.

In the case of a cost under-run, the Contractor shall submit the following information in addition to that required above:

(5) The amount by which the estimated cost of this contract may be reduced to recover excess funds and the total amount of staff-hours not expended, if any.

(6) A calculation of the appropriate fee reduction in accordance with this clause.

All submissions required by this paragraph shall include subcontractor information, if any.

(f) SPECIAL INSTRUCTION TO THE PAYING OFFICE REGARDING WITHHELD FEE

Fees withheld pursuant to the provisions of this contract, such as the withholding provided by the “Allowable Cost and Payment” and “Fixed Fee” clauses, shall not be paid until the contract has been modified to reduce the fixed fee in accordance with paragraph (d) above, except that no such action is required if the total level of effort provided falls within the limits established in paragraph (d) above.

B-TXT-08 MINIMUM AND MAXIMUM QUANTITIES (JUN 2017)

As referred to in paragraph (b) of the “Indefinite Quantity” clause of this contract, the contract minimum quantity is a total of $ 25,000 worth of orders. The maximum quantity is the total estimated amount of the contract. The maximum quantity is not to be exceeded without prior approval of the Procuring Contracting Officer.

The combined/overall ceiling for all awardees under this Multiple Award Contract is $ TBD; however, no MAC awardee can exceed the value of its contract maximum quantity.

B-TXT-10 ALLOTMENT OF FUNDS (JUN 2017)

***This clause shall be used in incrementally funded task orders.***

(a) This contract is incrementally funded with respect to both cost and fee.

(b) The amounts presently available and allotted to this contract for payment of fee, as provided in the Section I clause of this contract entitled “Fixed Fee”, are as follows:

[Contracting officer under “Items” insert the item numbers for which incremental funding is provided and under

“Allotted to Fixed Fee” insert the amount of incremental funding allocated to fixed fee]

ITEM(S) ALLOTTED TO FIXED FEE

(c) The amounts presently available and allotted to this contract for payment of cost, subject to the Section I

“Limitation of Funds” clause, the items covered thereby and the period of performance which it is estimated the allotted amount will cover are as follows:

[Contracting officer under “Items” insert the item numbers for which incremental funding is provided, under

“Allotment of Cost” insert the amount of incremental funding allocated to total estimated cost, and under “Period of Performance” insert date by which funding expended]

ITEM(S) ALLOTTED TO COST PERIOD OF PERFORMANCE

(d) The parties contemplate that the Government will allot additional amounts to this contract from time to time by unilateral contract modification, and any such modification shall state separately the amounts allotted for cost and for fee, the items covered thereby, and the period of performance the amounts are expected to cover.

Section C - Descriptions and Specifications

STATEMENT OF WORK

Title: ENGINEERING SERVICES FOR EMERGING POSITIONING, NAVIGATION AND TIMING (PNT)

TECHNOLOGIES FOR C4ISR APPLICATIONS

1.0 INTRODUCTION

Space and Naval Warfare (SPAWAR) Systems Center Pacific (SSC PAC), System of Systems and Platform

Integration Division (Code 52300) is acquiring technical engineering services to support Position, Navigation, and

Timing (PNT) systems to meet the Department of Defense (DoD), Joint, Coalition, and Navy’s needs for secure, functional, interoperable, and sustainable GPS-PNT capabilities.

1.1 Scope. As referenced in the U.S. Navy Information Dominance Science and Technology Objectives, “PNT capabilities provide common and precise position and time references to surface, sub-surface, air and space-borne assets, enabling safety of navigation, communications, command and control, combat and weapon systems.

Technology investments in this area are focused on hardening and modernizing existing Global Positioning System

(GPS)-dependent PNT capabilities, developing GPS-independent PNT solutions, and miniaturized and scalable PNT solutions.”

For protected GPS dependent PNT capabilities, the focus is to develop/leverage technologies that counter threats, providing protection of conventional GPS dependent systems to enable assured GPS-based operations.

For GPS-independent solutions, the focus is to develop/leverage technologies and to integrate software algorithms that provide alternatives to existing GPS-dependent PNT systems, enabling mission sustainment and warfighting capabilities in stressed operational environments.

For miniaturized and scalable PNT solutions, the focus is to develop/leverage a range of miniaturized and scalable

PNT solutions that can be utilized on small-unit manned/unmanned platforms in reduced size, weight and power

(SWAP) enabling sustained operationally relevant PNT accuracies. This includes the development of diverse multi-sensor, integrations of software algorithms, and improvements to existing systems that complement legacy navigation sensors and dependent navigation decision aids.

The purpose of this acquisition is to provide technical engineering services for:

Investigating and analyzing PNT technology gaps and innovative/emergent PNT technology applications to fulfill those identified gaps.

Identifying, planning, designing, and implementing laboratory enhancements required to develop and/or evaluate enabling technologies for PNT to be demonstrated in relevant operational environments to determine their military utility.

Identifying impacts to current and future PNT-based systems involving emerging/evolving threats and determining systems architectures, designs and technical solutions that mitigate these threats.

Investigating and evaluating integration impacts of evolving technologies to ensure they meet operational requirements and user needs as well as to ensure integrity of navigation signals and minimal impact to the platform installations.

Planning and executing necessary processes and management controls to provide cost effective maintenance, sustainment, and fleet engineering support of the PNT technologies.

1.2 Background. The Space and Naval Warfare Systems Center, Pacific (SSC Pacific), System of Systems and

Platform Integration Division is the principal Navy Research and Development (R&D) Center for PNT development, verification/validation, integration and sustainment. As the Navy’s lead R&D activity, SSC Pacific is responsible for developing navigation systems, sensors, receivers, antennas, and other supporting equipment for all

Navy platforms, including aircraft, ships, submarines, ground, and expeditionary systems. The System of Systems and Platform Integration Division is the Navy’s lead developer that provides full spectrum support of navigation systems. The support includes research and development, innovative science and technology, verification and evaluation, fleet installation and engineering, in-service engineering agent services, test and evaluation, configuration management, integrated logistics and spare parts, training and more for the Navy, Marine, and Joint

C4ISR missions. It serves as the PNT integration Central Engineering Activity (CEA) for three of the Navy’s major systems commands and respective Program Executive Offices (PEOs): 1) Space and Naval Warfare Systems

Command (SPAWAR) who is responsible for the hardware and software integration of all navigation/C4I data and systems, 2) Naval Sea Systems Command (NAVSEA) who is responsible for developing and testing of all navigation sensors and systems used on Navy’s ships and submarines, and 3) Navy Air Systems Command

(NAVAIR) who is responsible for all Navy aircraft and aircraft carriers. The Division supports other organizations such as the Office of Naval Research (ONR), Defense Advanced Research Project Agency (DARPA), other military departments (MILDEPs), federal government agencies and departments, and international communities in development of the PNT capabilities. Because the Office Secretary of Defense (OSD) has designated the U.S. Air

Force as the lead service for the PNT efforts, the System of Systems Platform Integration Division works closely with the Air Force Space Command’s Global Positioning Systems Directorate (GPSD), located at the Los Angeles

Air Force Base (LAAFB), and they are the primary organization for the development of PNT systems and components for the Department of Defense (DoD).

2.0 APPLICABLE DOCUMENTS (ADs)

In the event of a conflict between the text of this SOW and the document(s) cited herein, the text of this SOW shall take precedence. Nothing in the document or in this SOW, however, shall supersede applicable laws and regulations, unless exemption has been obtained. The following documents are for reference only, except where invoked for a specific section of the document.

2.1 SPAWARINST 5400.3, Systems Engineering Technical Review Process, 09 OCT 2007

2.2 DoDD 8500.01E, Information Assurance (IA), April 23, 2007

2.3 DoDI 8500.2, Information Assurance (IA) Implementation, 06 FEB 2003

2.4 DOT&E Memorandum on Operational Cybersecurity Testing Procedures, 19 AUG 2014

2.5 OSD Memorandum, Procedures for Operational Test and Evaluation of Cybersecurity in Acquisition

Programs, 01 AUG 2014

2.6 U.S. Navy Information Dominance Roadmap 2013-2014

2.7 U.S. Navy Information Dominance Science and Technology Objectives 2014

2.8 SECNAV Manual 5510.30 (Series), Department of Navy Personnel Security Program, June 2006

2.9 SECNAV Manual 5510.36 (Series), Department of Navy Information Security Program, June 2006

2.10 OPNAVINST F3300.53C (Series), Navy Antiterrorism Program

2.11 DOD 5200.01 Volumes 1 through 4 (Series), DOD Security Program

2.12 DOD 5220.22-M (Series), National Industrial Security Program Operating Manual (NISPOM), 28 February

2006, CH 1 28 March 2013

2.13 National Security Decision Directive 298 (Series), National Operations Security Program (NSDD) 298, 22

January 1988

2.14 DOD 5205.02 (Series), DOD Operations Security (OPSEC) Program, 03 November 1988

2.15 OPNAVINST 3432.1 (Series), DON Operations Security, 04 November 2011

2.16 MIL-HDBK-61A(SE), Configuration Management Guidance, 07 FEB 2001

3.0 TECHNICAL REQUIREMENTS

The engineering services include systems acquisition support, project management, systems engineering, integration, systems requirements analysis, planning, basic and applied research, development, testing, implementation, installation and fielding, security, and full life-cycle sustainment support of both software and hardware directly related to PNT technologies.

3.1 PNT Technology Gaps. The contractor shall investigate PNT technology gaps, user requirements, and operational requirements. The contractor shall conduct analysis of these gaps and requirements and identify innovative/emergent PNT technology applications to address the technology gaps and requirements to satisfy Urgent

Operational Needs (UONs), user needs, and other warfighting deficiencies.

3.1.1. C4I Concepts. The contractor shall investigate, track, and report on the status of evolving GPS signal integrity, navigation and C4I concepts. The investigation shall focus on impacts upon current and future technology needs and integrations.

3.1.2. Review Pertinent and Relevant Literatures. The contractor shall review pertinent and relevant literatures to identify performance parameters, algorithm techniques or processing techniques of interest to PNT concepts and development.

3.1.3 Requirements Management. The contractor shall conduct requirements management, translating technology gaps, user requirements, and operational requirements into functional and performance requirements that lead to design and development of technology. The requirements management should include traceability of requirements to higher requirements and demonstration of dependencies with other systems/components internal and external to the PNT systems.

3.1.4 Systems Requirements Analyses. The contractor shall provide systems requirements analyses support for prototype integration based upon Military (Navy/Marine/Army/Air Force/US Coast Guard etc.) requirements, Federal Aviation Agency (FAA) regulations, and platform unique requirements.

3.1.5 Technical Expertise. The contractor shall provide technical expertise for determining suitable technology components required for fabrication as well as their availability and acquisition methods.

3.1.6 Emerging Technology Alternatives. The contractor shall investigate and analyze the practicality of implementing navigation signal integrity and emerging technology alternatives into new and existing systems by conducting concepts exploration of PNT systems in respect to security and vulnerabilities. Included in the implementation are the quality conformance, management, and control of systems/components and adherence to specified requirements.

3.1.7 Modeling and Simulation (M&S). The contractor shall use M&S to evaluate technology and capability gaps to address technical performance and functional needs as well as integration specifications within the PNT architecture.

3.1.8 Demonstration. The contractor shall conduct feasibility demonstrations of conceptual approaches, evaluations of design risks, identification of design alternatives, comparisons and analysis of trade-offs, and estimation of operational requirements satisfaction to generate future capabilities to be fulfilled by PNT technologies.

3.2. Laboratory Enhancements. The contractor shall identify, plan, design, and implement laboratory enhancements required to develop and/or evaluate enabling and existing PNT technologies. This includes the preparation of the laboratory to conduct evaluations, assessments, analyses, and testing of PNT technologies that will support technical demonstrations in relevant operational environments, experiments, and military exercises.

3.2.1 Test Plans. The contractor shall develop test plans to include processes, resources, and identification of systems under test; determination of test objectives; identification of test requirements, test data, and facility configuration; testability of systems/components; schedule; technical measurements for purpose of evaluation to include measure of performance (MOP) and measure of effectiveness (MOE); and test scenarios in which the PNT will be tested. The test plan shall support emerging/innovative technology, current/legacy systems, and others generated by technology gaps and user requirements.

3.2.2 Testing. The contractor shall conduct test executions and provide test reports that verify and validate performances of the systems under test. This includes testing of individual systems/components, commercial off the shelf (COTS) and non-developmental item (NDI) systems, Foreign Comparative Testing (FCT), North Atlantic

Treaty Organization (NATO) Comparative Testing (NCT) and International Testing Operations Procedure (ITOP), Joint Interoperability Test Certification (JITC), integration and interoperability; and software and information technology (IT) items. Integration testing and reports should allow for sharing of test events/data from a single test point or mission to satisfy multiple test objectives to remove duplications of tests and test resources.

3.2.3 Documentation. The contractor shall provide test documentation using designed templates and/or the DoD test documentation or other formats as well as edits, compilation, data collection, reviews, and comments of format written materials received from various sources. These materials may include architecture diagrams, test procedures, test plans, test reports, test data, schedules, and briefing materials to support test documentation.

3.2.4 Laboratory Procedures. The contractor shall identify laboratory procedures to validate the effects of developmental changes made to remedy design deficiencies and/or improve performance parameters of existing products as well as to identify procedures to validate the performance parameters of the evolving technologies.

3.2.5 Test Analysis. The contractor shall conduct analysis of test data for performance, integration, interoperability, cost effectiveness, and enhancement requirements as process improvement.

3.2.6 Configuration Management Library. The contractor shall maintain a configuration management library of test and evaluation (T&E) documentation and all software used.

3.2.7 Test Factors. The contractor shall consider design of experiment (DOE), and application of scientific test and analysis technique (STAT), to determine successful performance drivers, number of tests, assets required and interaction between test factors.

3.2.8 Test Support Equipment. The contractor shall identify and develop test support equipment such as emulators, stimulators and Smart Buffer Boxes (SBB) and/or modify and develop test tools to meet specific test requirements.

M&S should be used where tests cannot be conducted under reasonable conditions. When M&S is utilized, the contractor shall conduct verification, validation, and accreditation (VV&A) to assure the results of the M&S are accurate and correct.

3.2.9 Testing Components. The contractor shall conduct material assessments of testing components and production equipment to support PNT integration and interoperability testing and enhancements to the laboratory.

3.2.10 Cyber Security. The contractor shall conduct cyber security certification and accreditation (C&A) and validation testing as required by DoDD 8500.01E, DoDI 8500.2, DOT&E Memorandum on Operational Security

Testing Procedures, and the ODS Memorandum, Procedures for Operational Test and Evaluation of Cybersecurity in Acquisition Programs. The cyber security testing shall include anti-tampering requirements; all COTS/NDI items used an integral part of the PNT system.

3.2.11 Certification and Accreditation. The contractor shall support cyber security certification and accreditation of the laboratories in which PNT systems are tested in accordance with (IAW) DOT&E Memorandum on Operational

Security Testing Procedures, and the ODS Memorandum, Procedures for Operational Test and Evaluation of

Cybersecurity in Acquisition Programs.

3.3 Systems Architecture and Design. The contractor shall assist in identifying systems architecture and design to minimize impacts to current and future PNT-based systems to include involving emerging/evolving threats and to provide evaluated technical solutions that mitigate these threats. The systems architecture, design, and development are an integral part of the technical management and implementation process. Specific tasks are:

3.3.1 Technical Management Plan. The contractor shall provide technical management to include technical plan such as systems engineering plans (SEPs), architecture and design development processes, and measures and metrics to monitor the progress. The technical management plan shall include computer aided/automated design tools and other tools necessary to develop and design the PNT systems.

3.3.2 Prototype Installation. The contractor shall perform systems integration, engineering, product improvement modifications, and analyses for prototype installation on various DoD/DON platforms and shall conform to all

Government standards and functionality requirements identified in the individual task orders.

3.3.3 PNT Architecture. The contractor shall propose PNT architecture to include functional designs, hardware and software interface characteristics, data evaluation requirements, and data analysis procedures.

3.3.4 Net-ready Key Performance Parameters. The contractor shall provide net-ready key performance parameters

(NR-KPP) compliance that leads to the production of DoD Architecture Framework (DoDAF) to include, but not be limited to: documentation of requirements traceability, identification of systems relationships, interface specifications and controls, interoperability requirements, and data dependencies.

3.3.5 Reviews. The contractor shall support all technical reviews and program management reviews, by participating in Preliminary Design Review (PDR), Critical Design Review (CDR), System Requirements Review

(SSR)’s, Test Readiness Review (TRR)’s, provide subject matter experts (SME’s), conference reviews, agenda’s and minutes.

3.3.6 Integrity. The contractor shall identify, review, and analyze advanced algorithms and techniques for implementing integrity within these integrated systems. The contractor shall design and develop engineering drawings for prototype platform integration architectures.

3.3.7 Implementation. The contractor shall assess strategies of implementing emerging technologies and alternatives into new and existing navigation and C4I systems, Navy’s visions and roadmaps, and DoD initiatives:

Global Information Grid (GIG), Intelligent Composability, and Joint Information Exchange (JIE). The contractor’s strategy should comply with all regulatory and statutory regulations as well as security requirements applicable to the PNT systems.

3.3.8 Capabilities. The contractor shall assess the capabilities of SSC Pacific facilities in order to meet the evolving technology integration requirements. The contractor shall identify design refinements necessary to modify both hardware and software functions. The contractor shall identify developmental additions to existing facilities as well as technical cost (material and labor) required to implement design changes.

3.3.9 Configuration Management. The contractor shall perform configuration management on C4I emerging and existing technology, IAW MIL-HDBK-61A(SE).

3.3.10 Assembly. The contractor shall assemble prototype systems or engineering development models to ensure the systems/models comply with technical requirements, standards, and specifications.

3.4 Integration Impacts. The contractor shall investigate and evaluate the integration impacts of evolving technologies to ensure they meet operational requirements and user needs as well as ensure integrity of navigation signals and minimal impact to the platform installations. The integration includes systems of systems (SoS), systems, components, and equipment integrations that promote interoperability. These integrations shall generate appropriate levels of documentation to ensure all future systems can be easily integrated and interoperable.

3.4.1 Application. The contractor shall apply Open Systems Architecture, open standards, and open specifications.

3.4.2 Impact Documentation. The contractor shall investigate and document the PNT implementation and integration impacts to determine readiness and availability of the systems while optimizing life cycle cost. This includes the coordination of interface requirements with MILDEPs, inter-agencies, and international organizations to ensure integration and interoperability of systems.

3.4.3 Interface Definition. The contractor shall identify interface definition of the PNT as SoS, system, component, and technology. This includes all emerging, future, existing, legacy, and COTS/NDI components. The contractor shall identify interface definition and compliance of PNT with COTS and NDI.

3.4.4 Technical Interface Risks. The contractor shall identify technical interface risks and issues and recommend mitigation strategies if/when systems deviate from interface standards and/or requirements.

3.4.5 Specifications. The contractor shall develop systems interface specifications and interface controls documents

(ICDs) describing function and performance integration of all PNT systems and related systems. The ICDs shall include, but not be limited to: wiring, logical, physical, and functional diagrams.

3.4.6 Verification. The contractor shall verify the conformity of existing interfaces to emerging and future PNT systems as well as with dependent systems and sub-systems.

3.5 Management Controls. The contractor shall support planning and executing necessary processes and management controls to implement emerging, existing, and legacy technologies to provide cost effective maintenance, sustainment, and fleet engineering support.

3.5.1 Life Cycle Testing. The contractor shall perform system life cycle testing and assessment for the purpose of understanding cause and effect of long term exposure of the PNT products on various air, ship, sub-surface, and ground environments to be used for process and technology improvements.

3.5.2 In-Service Engineering Agent (ISEA). The contractor shall provide ISEA support by conducting analysis and trouble-shooting failures of operational systems (Navy-311 and CASREPS) both on site and in the laboratory, provide solutions and fixes, and document issues.

3.5.3 Acquisition Tracking. The contractor shall track the status of Government acquisitions involving new technologies to include, but not be limited to: project/program scope, schedule, budget, and operational requirements. The contractor shall review associated acquisition documentation including, but not limited to:

functional area analysis, functional needs analysis, engineering changes proposals (ECPs), software changes proposals, value engineering, advance change study notices, specifications, test plans, and other similar documentation.

3.5.4 Implementation and Capabilities. The contractor shall investigate, document, develop, and implement features and capabilities of system performance, reliability, maintainability, availability, survivability, safety, security, protection, cost/life cycle considerations, and training as they apply to software and hardware design, fabrication, integration, and operation.

3.5.5 Life Cycle Support. The contractor shall provide life cycle support to include, but not be limited to:

technology refreshes, engineering maintenance, installation support, integrated logistics support, and Configuration

Data Managers Database – Open Architecture (CDMD-OA).

3.5.6 Maintenance Planning. The contractor shall identify and implement requirements necessary to support maintenance planning, spare parts planning and procurement, diminishing technology replacements, support equipment, technical data computer resources support, and design interface.

3.5.7 Information Repositories. The contractor shall design, develop, implement, operate, and sustain computer based and web-enabled data and information repositories for data collection and retrieval of navigation, C4ISR, and system sustainment information as well as for the collection and dissemination of PNT data.

3.5.8 Working…