14RJT81_sol.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local time 07 Jul 2014

X

A X B X C X D

EX

X

G F 79 - 105

106 - 116 X H 117 - 120 diane.bright@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)

DO A7 1 120

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

N00164 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

BUILDING 3422

conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

DIANE BRIGHT 812-854-2938

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 12

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

13 - 32 33 - 35

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

36 - 37 38 - 39

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 40 - 46 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 47 - 56 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 - REPRESENTATIONS AND INSTRUCTIONS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

57 - 77

PART II - CONTRACT CLAUSES

NAVAL SURFACE WARFARE CENTER CRANE DIV

D. BRIGHT (812-854-2938)

BLDG 3422

300 HIGHWAY 361

CRANE IN 47522-5001

812-854-2938

812-854-5095FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

01 May 2014

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N00164-14-R-JT81

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QTY U/I UNIT PRICE AMOUNT

0001 TECHNOLOGY AREA 1

Tagging, Tracking and locating (TTL) systems.

See Section 1.2.1 of Statement of Work (SOW) in Section C.

1 Lot

FOB: Destination

FFP

0002 TECHNOLOGY AREA 2

Processing, Exploitation, and Dissemination (PED) systems. See Section 1.2.2 of Statement of Work (SOW) in Section C.

0003 TECHNOLOGY AREA 3

Special Communications Enterprise Solutions.

See Section 1.2.3 of Statement of Work (SOW) in Section C.

0004 TECHNOLOGY AREA 4

Mobile SIGINT Solutions. See Section 1.2.4 of Statement of Work (SOW) in Section C.

0005 TECHNOLOGY AREA 5

Sensitive site exploitation technologies. See Section 1.2.5 of Statement of Work (SOW) in Section C.

0006 TECHNOLOGY AREA 6

Persistent Surveillance Systems. See Section

1.2.6 of Statement of Work (SOW) in Section C.

ITEM

NO SUPPLIES/SERVICES QTY U/I UNIT PRICE AMOUNT

0007 CDRLs

Contract Data Requirements Lists (CDRL) -

DD 1423-1

Data/Tech Data Requirements for CLIN(s) 0001-0006 in accordance with the SOW Paragraph(s) 3.0, CDRL(s) A001 thru A033, and applicable DID(s). The Government shall have unlimited rights to all Data/Tech Data generated under this effort IAW DFARS 252.227-7013., unless an assertion is provided and accepted by the Government with the offer IAW DFARS 252.227-7017. The price/costs for all data/tech data generated by the contractor directly or indirectly in its performance of this procurement effort is included in the price/costs paid by the Government under CLIN(s) 0001-0006.

Lot

CLAUSES INCORPORATED BY FULL TEXT

CNIN-B-0005 ORDERING -- ADDITIONAL INFORMATION

The agency authorized to place orders against this BOA is:

Naval Surface Warfare Center, Crane Division (NSWC Crane) – N00164 300 Hwy 361 Crane, IN 47522-5001.

Orders shall be placed against this contract using a DD 1155 or SF 1449 format.

CNIN-B-0008 Data Rights

The Government shall have unlimited data rights to all technical data generated in the performance of this contract, whether required to be delivered or not, in accordance with (IAW) DFARS 252.227-7013; and similarly to all computer software and computer software documentation generated in the performance of this contract, whether required to be delivered or not, IAW DFARS 252.227-7014; unless an assertion is provided and accepted by the Government with the offer IAW DFARS 252.227-7017. Upon creation of an assertion table as directed/applicable, the Offeror will identify the specific CLIN and CDRL to which the assertion applies. No assertion table(s) will be accepted in response to a Basic Ordering Agreement (BOA). If the Government determines that acceptance of an assertion(s) is valid, said assertion(s) will be incorporated into each individual order or resultant contract.

CNIN-B-0010 BOA Contract Types

The following contract types are authorized for use under this BOA:

Firm Fixed Price (FAR 16.202) Cost Plus Fixed Fee (FAR 16.306)

Each individual order will indicate the contract type for each line item.

CNIN-NOTICE-0001 SECTION B NOTES (JAN 2013)

1. Section K herein will be incorporated by reference and made a material part of the contract in accordance with

FAR 15.204-1(b).

2. The System for Award Management (SAM) has replaced Central Contracting Registration (CCR). Offers may obtain information on SAM registration and annual confirmation at the website https://www.sam.gov , or https://www.acquisition.gov and by phone at 1-866-606-8220.

3. Data Item Descriptions (DIDS) referenced in the attached Contract Data Requirements List(s) (CDRLs) are available at the following website: http://www.assistdocs.com

4. The technical data package may contain information that is export controlled. Only those companies that have completed DD Form 2345 and are certified under the Joint Certification Program (JCP) in an active status are authorized to receive export controlled information. Additional information is available at http://www.dlis.dla.mil/jcp/.

5. Technical questions concerning this procurement shall be submitted in writing to arrive at NSWC Crane no later than 2:00 PM EST on the seventh calendar day preceding the closing date shown on page 1 addressed as follows:

COMMANDER

CONTRACTING OFFICER/SPECIALIST Diane M. Bright

NSWC CRANE DIVISION

300 HWY 361

CRANE IN 47522-5000

or E-mail questions to diane.bright@navy.mil

6. Any amendments to the subject solicitation will be posted to NECO (http://www.neco.navy.mil) and

FedBizOps (http://www.fbo.gov). The complete solicitation package, including all amendments, should be received and reviewed prior to submitting a response. It is the responsibility of the offeror to obtain all amendments and/or other applicable documents prior to submission of the offer. Under these circumstances, offerors are reminded to include acknowledgement of acceptance of these amendments in their offer.

7. The Government is not obligated to issue any orders against this Basic Ordering Agreement (BOA); there is NO MINIMUM funded amount or guaranteed minimum for any awardee. The maximum funded amount to be applied across all BOAs for all 5 years is $49,000,000. The Government intends to award multiple BOAs to satisfy agency requirements. Individual requirements will be competed at the Job Order level.

8. If determined necessary to promote competition, the Government intends to add additional BOA awards on a

Rolling Admission basis as emerging agency needs are identified throughout the five year ordering period. See Section H of this Solicitation for additional information on the Rolling Admission procedure.

9. This procurement is NOT set-aside for small business concerns. However, upon award of the Basic Ordering

Agreements (BOA), it is possible that individual job order requirements will be set-aside for small business.

Therefore, the applicable contract clauses have been included in Section I, and will only be invoked in the event of a small-business set-aside requirement.

10. As stated in Clause CNIN-B-0010, multiple contract types are authorized for use under this BOA. It is anticipated that the majority of the job orders will be on a fixed price or cost reimbursement basis.

Furthermore, both non-commercial and modified-commercial requirements are anticipated. Applicable clauses for all of these contract types are included in the solicitation. However, the specifics of the job order requirements will dictate what clause(s) are applicable to each individual job order.

11. Section B contains contract line item numbers (CLINs) for the six (6) technology areas that these BOAs will cover. Offerors may provide proposals for any combination of CLINs. Offerors may propose on as few as one

(1) CLIN or any combination up to and including all six (6) CLINs. Offerors will be required to submit written technical capability documentation to support each CLIN they are proposing on. See Section L. BOA awards will be made by CLIN to the most highly rated offeror’s for each CLIN.

12. An offeror’s proposal is presumed to represent the best effort in response to the solicitation. The Government’s intent is to award multiple basic ordering agreements without discussions, as permitted by FAR 52.215-1.

CNIN-NOTICE-0002 NSWC CRANE GENERAL PROCUREMENT INFORMATION (APR 2014)

1. HANDLING OF INFORMATION BY CONTRACTOR SUPPORT PERSONNEL

Contractors are hereby notified that contractor support personnel within the NSWC Crane Contracting Department may be handling Bid and Proposal or Quote data as well as other correspondence and documentation concerning this action. Non-disclosure statements have been executed by all contractor support personnel participating in the process and are maintained by NSWC Crane.

2. BUSINESS HOURS

NSWC Crane Division allows flexible working hours for its employees. The core time when all employees are scheduled to work is 9:00 am to 3:00 pm (local time).

3. TAX EXEMPTION

Section 39(A) and Section 6 of the Indiana Gross Income Tax Act of 1933, specifically exempts NSWC Crane Division as a government activity from any payment of sales and use taxes.

The assigned Exemption Number is 0018103400015

4. VENDOR SURVEY

NSWC Crane Contracting Department’s mission is to provide responsive, best-value contracting and acquisition support for all customers, accomplished in partnership with industry, academia, and other Government activities, while maintaining the public's trust and fulfilling public policy objectives. In an effort to continually improve our services, the Contracting Office is conducting a survey of our vendors. Your comments will help us determine if we are accomplishing our mission and provide recommendations for ways to improve our processes. Please consider taking the time to complete the survey which can be accessed at the following address:

http://www.navsea.navy.mil/nswc/crane/working/contracting/Lists/Vendor%20Survey/overview.aspx.

5. NSWC CRANE VISITOR INFORMATION: PORTABLE ELECTRONIC DEVICE POLICY

NSWC Crane has implemented full compliance with the NAVSEA Access and Movement Control Instruction 5510.2C, dated 7 August 2012, which restricts the use of portable electronic devices (PEDs) in all NAVSEA spaces. In accordance with NSWC Crane Policy Letter 14-02 dated 20 March 2014, all government civilian, military and contractor personnel assigned to NSWC Crane and all visitors are prohibited from bringing any device or equipment capable of recording, transmitting or exporting photographic images or audible information of any kind into NSWC Crane spaces . This policy prohibits all personal electronic devices other than personal cell phones. For the purpose of this policy, “spaces” include outdoor ranges and test areas.

NSWC Crane areas will be clearly marked. Prohibited devices include: MP3 players, e-readers, digital recording devices, laptop and tablet computers, and/or other electronic devices not provided by the government or specifically authorized. One-way pagers are allowed for fire, safety and security purposes. These devices can be used in non-NSWC Crane areas.

6. RAPIDGate NSA/NSWC CRANE INSTALLATION ACCESS NSA/NSWC Crane is implementing the Navy Commercial Access Control System (NCACS) projects. The NCACS is the standard identity management and perimeter installation access control solution for the access management of vendors, contractors, suppliers and service providers who are not authorized a Common Access Card (CAC). The rationale for implementation of this system is to increase security while reducing impacts to the contractor community by improving efficiencies for base entry.

A new protocol being implemented to fulfill this NCACS requirement is the RAPIDGate system. The system meets Presidential Directive (HSPD-12) requirements by providing background checks of contractor personnel.

A personal badge that affords base access (and/or multiple base access) for one year will be issued to each Contractor employee that meets background check criteria. While Contractors are not required to participate in this program, those Contractors who choose not to participate will be required to obtain daily passes for base access.

For contracts which include the FAR 52.204-9 Personal Identity Verification of Contractor Personnel or will otherwise require frequent access to the Naval Support Activity (NSA)/NSWC Crane site, contractors should consider taking advantage of the benefits available from the RAPIDGate program. A Government Sponsor is required to validate a Contractor’s request for RAPIDGate access, and shall be the Contracting Officer’s Representative (COR). If there is no COR, then the Government Sponsor is the Contracting Officer.

The Government does not guarantee the contractor’s successful enrollment or the successful enrollment of any contractor employees in the RAPIDGate program. Significant delays may result from choosing to access the installation by obtaining a one day pass. The Government will not be held responsible for any access delays associated with using the daily pass process. Please address any questions or concerns regarding RAPIDGate to the COR or the local Base Security Office personnel listed below.

NSA/NSWC Crane RAPIDGate Primary Program Point of Contact is Jon Thomas, and can be reached at Jon.M.Thomas@Navy.mil or at 812-854-5642.

Additional information is available at http://www.rapidgate.com/rapidgate

7. NSWC CRANE RECEIVING FACILITY SCHEDULE

Contractors shall schedule deliveries to ensure arrival at destination only on Monday through Friday (excluding holidays) between the hours of 7:00 A.M. and 2:00 P.M. Eastern Standard Time (EST). The receiving facility is closed on Saturdays and Sundays.

Contractors shall ensure deliveries of EXPLOSIVE MATERIALS arrive at destination only on Monday through Thursday (excluding holidays) between the hours of 7:00 A.M. and 2:00 P.M. EST. The receiving facility for explosives is closed on Fridays, Saturdays and Sundays.

PAYMENT OF FEES(S) (LEVEL OF EFFORT – ALTERNATE I) (NAVSEA) (MAY 2010)

(a) For purposes of this contract, "fee" means "target fee" in cost-plus-incentive-fee type contracts, "base fee" in cost-plus-award-fee type contracts, or "fixed fee" in cost-plus-fixed-fee type contracts for level of effort type contracts.

(b) The Government shall make payments to the Contractor, subject to and in accordance with the clause in this contract entitled "FIXED FEE" (FAR 52.216-8) or "INCENTIVE FEE", (FAR 52.216-10), as applicable. Such payments shall be submitted by and payable to the Contractor pursuant to the clause of this contract entitled "ALLOWABLE COST AND PAYMENT" (FAR 52.216-7), subject to the withholding terms and conditions of the "FIXED FEE" or "INCENTIVE FEE" clause, as applicable, and shall be paid at the hourly rate(s) specified above per man-hour performed and invoiced.

Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract.

HQ B-2-0001 BOA LANGUAGE FOR SECTION B

The Contractor shall furnish the following supplies and services when ordered by the Contracting Officer in accordance with the terms and conditions set forth in this Basic Ordering Agreement (BOA). This agreement shall remain in effect through Five (5) Years from effective date of BOA subject to the special contract requirement entitled "MODIFICATION AND TERMINATION" (NAVSEA 5252.249-9106).

HQ B-2-0004 EXPEDITING CONTRACT CLOSEOUT (NAVSEA) (DEC 1995)

(a) As part of the negotiated fixed price or total estimated amount of this contract, both the Government and the Contractor have agreed to waive any entitlement that otherwise might accrue to either party in any residual dollar amount of $500 or less at the time of final contract closeout. The term "residual dollar amount" shall include all money that would otherwise be owed to either party at the end of the contract, except that, amounts connected in any way with taxation, allegations of fraud and/or antitrust violations shall be excluded. For purposes of determining residual dollar amounts, offsets of money owed by one party against money that would otherwise be paid by that party may be considered to the extent permitted by law.

(b) This agreement to waive entitlement to residual dollar amounts has been considered by both parties. It is agreed that the administrative costs for either party associated with collecting such small dollar amounts could exceed the amount to be recovered.

HQ-B-2-0007 LIMITATION OF COST OR LIMITATION OF FUNDS LANGUAGE

The clause entitled "LIMITATION OF COST" (FAR 52.232-20) or "LIMITATION OF FUNDS" (FAR 52.232-22), as appropriate, shall apply separately and independently to each separately identified estimated cost.

HQ-B-2-0014 PAYMENTS OF FEE(S) (COMPLETION) (NAVSEA) (MAY 1993)

(a) For purposes of this contract, "fee" means "target fee" in cost-plus-incentive-fee type contracts, "base fee" in cost-plus-award-fee type contracts, "fixed fee" in cost-plus-fixed-fee type contracts for completion and phase type contracts.

(b) The Government shall make payments to the Contractor, subject to and in accordance with the clause in this contract entitled "FIXED FEE" (FAR 52.216-8) or "INCENTIVE FEE", (FAR 52.216-10), as applicable. Such payments shall be equal percent ( %) of the allowable cost of each invoice submitted by and payable to the Contractor pursuant to the clause of this contract entitled "ALLOWABLE COST AND PAYMENT" (FAR 52.216-7), subject to the withholding terms and conditions of the "FIXED FEE" or "INCENTIVE FEE" clause, as applicable (percentage of fee is based on fee dollars divided by estimated cost dollars, including facilities capital cost of money). Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract.

(c) In the event of discontinuance of the work under this contract, or any specified phase of the contract, in accordance with the clause of this contract entitled "LIMITATION OF FUNDS" (FAR 52.232-22) or "LIMITATION OF COST" (FAR 52.232-20), as applicable, the fee shall be equitably adjusted by mutual agreement to reflect the diminution of work. If the adjusted fee is less than the sum of all fee payments made to the Contractor under this contract, the Contractor shall repay the excess amount to the Government. If the adjusted fee exceeds all payments made to the Contractor under this contract, the Contractor shall be paid the additional amount, subject to the availability of funds. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract at the time of the discontinuance of work.

(d) Fee(s) withheld pursuant to the terms and conditions of this contract shall not be paid until the contract has been modified to reduce the fee(s) in accordance with paragraph (c) above, or until the Procuring Contracting Officer has advised the paying office in writing that no fee adjustment is required.

NOTE: Percentage of fee is based on fee dollars divided by estimated cost dollars, including facilities capital cost of money.

HQ-B-2-0015 PAYMENTS OF FEE(S) (LEVEL OF EFFORT) (NAVSEA) (MAY 1993)

(a) For purposes of this contract, "fee" means "target fee" in cost-plus-incentive-fee type contracts, "base fee" in cost-plus-award-fee type contracts, or "fixed fee" in cost-plus-fixed-fee type contracts for level of effort type contracts.

(b) The Government shall make payments to the Contractor, subject to and in accordance with the clause in this contract entitled "FIXED FEE" (FAR 52.216-8) or "INCENTIVE FEE", (FAR 52.216-10), as applicable. Such payments shall be equal to percent ( %) of the allowable cost of each invoice submitted by and payable to the Contractor pursuant to the clause of this contract entitled "ALLOWABLE COST AND PAYMENT" (FAR 52.216-7), subject to the withholding terms and conditions of the "FIXED FEE" or "INCENTIVE FEE" clause, as applicable (percentage of fee is based on fee dollars divided by estimated cost dollars, including facilities capital cost of money). Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract.

(c) The fee(s) specified in SECTION B, and payment thereof, is subject to adjustment pursuant to paragraph (g) of the special contract requirement entitled "LEVEL OF EFFORT." If the fee(s) is reduced and the reduced fee(s) is less than the sum of all fee payments made to the Contractor under this contract, the Contractor shall repay the excess amount to the Government. If the final adjusted fee exceeds all fee payments made to the contractor under this contract, the Contractor shall be paid the additional amount, subject to the availability of funds. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract at the time of the discontinuance of work.

(d) Fee(s) withheld pursuant to the terms and conditions of this contract shall not be paid until the contract has been modified to reduce the fee(s) in accordance with the "LEVEL OF EFFORT" special contract requirement, or until the Procuring Contracting Officer has advised the paying office in writing that no fee adjustment is required.

HQ B-2-0020 TRAVEL COSTS - ALTERNATE I (NAVSEA) (DEC 2005)

(a) Except as otherwise provided herein, the Contractor shall be reimbursed for its reasonable actual travel costs in accordance with FAR 31.205-46. The costs to be reimbursed shall be those costs accepted by the cognizant DCAA.

(b) Reimbursable travel costs include only that travel performed from the Contractor's facility to the worksite, in and around the worksite, and from the worksite to the Contractor's facility.

(c) Relocation costs and travel costs incident to relocation are allowable to the extent provided in FAR 31.205-35;

however, Contracting Officer approval shall be required prior to incurring relocation expenses and travel costs incident to relocation.

(d) The Contractor shall not be reimbursed for the following daily local travel costs:

(i) travel at U.S. Military Installations where Government transportation is available,

(ii) travel performed for personal convenience/errands, including commuting to and from work, and

(iii) travel costs incurred in the replacement of personnel when such replacement is accomplished for the Contractor's or employee's convenience.

(End of Text)

HQ B-2-0023 CONTRACT SUMMARY FOR PAYMENT OFFICE (COST AND FIXED PRICE TYPE)(FEB

1997)

This BOA includes the possibility of both cost and firm-fixed price orders. Contract type will be specified at the job level.

Section C - Descriptions and Specifications

STATEMENT OF WORK

Section C: Description and Specification

STATEMENT OF WORK

1.0 SCOPE

This Statement of Work (SOW) defines the effort required for the design, engineering, fabrication, and test of intelligence, surveillance, and reconnaissance components and systems that have met TRL level 6 maturity. The scope of this effort shall include provision of engineering development models (EDM), pre-production units (PPU), and low rate initial production (LRIP). System EDMs, PPUs, and LRIPs shall be designed, engineered, fabricated, and tested to satisfy the individual Job Order statements of work. It is not expected that all Job Orders will require the end to end development described in the contract level SOW due to variations in product maturity and required timelines for development at the Job Order level. Job Orders where end items are intended for combat evaluations or quick reaction capability may have abbreviated testing and schedule requirements. For all Job Orders, final product acceptance will be conduct by the Government Technical Design Agent. The requirement for associated program management is also included in this SOW.

1.1 BACKGROUND

NSWC Crane, Surveillance and Reconnaissance Systems Division (SRSD) provides full spectrum life cycle support for systems engaged in the intelligence, surveillance, and reconnaissance enterprise. SRSD subject matter experts identify emerging Warfighter sensor and collection requirements utilizing a technology surveillance process that identifies opportunities for transition, innovative application, and commercial application in-sourcing. Through close relationships with the requirement managers, resource sponsors, and end user operators, SRSD successfully fields solutions that close technology gaps rapidly and with great effectiveness.

1.2 TECHNOLOGY AREA DESCRIPTIONS

SRSD supports the engineering and development of Intelligence, Surveillance, and Reconnaissance (ISR) enterprise systems and the application development of integrated technology solutions and knowledge management systems to maximize utilization of intelligence data and PED (processing, exploitation, and dissemination) to special operations and intelligence community members. The SRSD portfolio addressed in this SOW includes:

1.2.1 – Technology Area 1 Tagging, tracking, and locating (TTL) systems and their associated situation awareness components that are employed for both friendly, red force, and hostile force tracking. Devices may operate on either commercial or DOD data architectures.

1.2.2 - Technology Area 2 PED systems that are interoperable, fusion capable, and contain cross domain solution innovations that considers Department of Defense (DOD), Other Government Agencies (OGAs), and coalition partner implications. Emphasis on the fusion of all source data, multiple ISR sensor data inputs, open architecture backbone, and advanced algorithm implementations.

1.2.3 - Technology Area 3 Special communications enterprise solutions which are interoperable within the ISR enterprise

1.2.4 - Technology Area 4 Mobile SIGINT solutions including software defined radio, antenna development, precision geo and direction finding technologies across a variety of threats, SIGINT fusion with other intelligence collection systems such as TTL, Special Communications, and Unattended Ground Sensors (UGS); improved system network capabilities.

1.2.5 - Technology Area 5 Sensitive site exploitation technologies for forensic analysis of information technology, mobile communication devices, documents and media exploitation (DOMEX), biometric collections and identification, and physical characterization of site materials/debris.

1.2.6 - Technology Area 6 Persistent surveillance systems including UGS, activity sensors and active sensors, UGS controller devices, data infiltration/exfiltration devices, and device network capability.

1.3 Representative Customers

The following list depicts the representative customers for the projects and programs: USSOCOM HQ, TSOCs, and Service Special Operations Components, Technical Support Working Group, US Navy, US Marine Corps, US

Army, US Air Force, OSD, and COCOMS (CENTCOM, PACOM, AFRICOM, SOUTHCOM, EUCOM), and Other Government Agencies.

2.0 APPLICABLE DOCUMENTS

The following specifications, standards, and handbooks form a part of this SOW to the extent cited herein. Unless otherwise specified, the issue of Government documents is that listed in the current issue of the Department of Defense Index of Specifications and Standards (DoDISS) on the issue date of the solicitation associated with this SOW. Non-Government standards listed are those in effect on the issue date of the solicitation associated with this

SOW.

2.1 Military Specifications, Standards and Handbooks

MIL-STD-31000A Detail Specification, Technical Data Packages, 26 Feb 2013

MIL-HDBK-470A Notice 2 Design and Develop Maintainable Products and Systems, 31 May 2012

MIL-HDBK-781A Reliability Test Methods, Plans, and Environments for Engineering Development, Qualification, and Production, 01 Apr 1996

MIL-HDBK-1785 System Security Program Management requirements, 01 Aug 1995

MIL-STD-881C Work Breakdown Structures for Defense Materiel Items, 03 Oct 2011

MIL-HDBK-29612-1A Guidance for Acquisition of Training Data Products and Services (Part 1 of 5 Parts), 31 Aug 2001

MIL- PRF-29612B Performance Specification, Training Data Products, 31 Aug 2001

MIL-STD-129P (4) DoD Standard for Military Marking for Shipment and Storage, 19 Sept

MIL-STD-130N, CH 1

DoD Standard Practice for Identification Marking of U.S. Military Property, 16 Nov 2012

MIL-STD-461F Requirements for the Control of Electromagnetic Interference Emissions & Susceptibility, including notices, 10 Dec 2007

MIL-STD-882E DoD Standard Practice for System Safety, 11 May 2012

EIA 649B National Consensus Standard for Configuration Management, 17 Jun 2011

GEIA-STD-0007 Logistics Product Data, 15 Oct 2008

MIL-STD-1472G Human Engineering, 10 Jan 2012

MIL-STD-2073-1E DoD Standard Practice for Military Packaging, change notice, 17Jan 2011

MIL-STD-40051-2B DoD Standard Practice Preparation of Digital Technical Information for Page-Based Technical Manuals (TIMs), 30 Nov 2012

MIL-HDBK-61A Configuration Management Guidance, 02 Feb 2001

MIL-STD-3034-Notice 1 Reliability-Centered Maintenance (RCM) Process, 22 Jun 2011

2.1.2 Joint Chiefs of Staff, Department of Defense and DoD Services Documents

DoD 4120.24 M Defense Standardization Program (DSP) Policies and Procedures, Mar 2000

DoDI 5200.39, CH 1 Mandatory Procedures for Research & Technology Protection with the DoD, 28 Dec 2010

DoD MCTL Military Critical Technologies List

DoDI 5000.02 Operation of the Defense Acquisition System, 08 Dec 2008

DoDD 5220.22M, CH 1 National Industrial Security Program Operating Manual, 28 Mar 2013

DoDD 8500.01E Information Assurance (IA), 24 Oct 2002

DoDI 8500.2 Information Assurance (IA) Implementation, 06 Feb 2003

DoDI 8510.01 DoD Information Assurance Certification and Accreditation Process (DIACAP), 28 Nov 2007

DoDD 8570.01-M Information Assurance Workforce Improvement Program

DISA STIG Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIG)

Directive-Type Memorandum

Security of Unclassified DoD Information on Non-DoD Information Systems, 16 Sep 2010

2.1.3 Non-Government and Commercial Standards, Specifications and other applicable publications

AR 700-15 Packaging Of Materiel, 12 Jan 2004

ASME Y14.24M Types and Applications of Engineering Drawings

CMMI-SE/SW/IPPD/SS Capability Maturity Model Integration (CMMISM) for Systems Engineering, Software Engineering, Integrated Product and Process Development, and Supplier Sourcing, 10 Mar 2002

IEEE 1220-2005 IEEE Standard for Application and Management of the Systems Engineering Process, 09 Sept 2005

IEEE/EIA 12207-2008 IEEE Systems and Software Engineering - Software Life Cycle Processes

IEEE STD 1016-2009 IEEE Standard for IT Systems Design Software Design Description, 19 Mar

ISO/IEC-15288 Systems Engineering- System Life Cycle Processes, 01 Nov 2002

ISO 9000 & 9001 Quality Management Systems, 01 Dec 2000

ISO 10007:2003 Quality Management - Guidelines for Configuration Management

NAS 411 National Aerospace Standard (NAS) 411, Hazardous Materials Management Program

NSTISSAM

TEMPEST/1/92

Compromising Emanations Laboratory Test Requirements, Electromagnetics

SAE AS5553 Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, & Disposition

The Contractor shall use the revision effective as of the date of contract award for each of the documents listed in the following subparagraphs and to the extent specified in the requirements of this SOW. Nothing in this document however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

It is the intent of this solicitation and the resulting contract to fully implement the principles of the Department of Defense (DoD) Acquisition Reform initiatives. Specifically, reference is made to the Secretary of Defense policy promulgated by memorandum on 29 June 1994 regarding the use of specifications and standards. When specifications are not practical, non-Government (industry developed) standards shall be used.

In the event of conflict between the documents referenced herein and the contents of this SOW, the Order of precedence shall be:

1) Section 3 of this SOW;

2) Specifications, Standards and Other Documents, listed in Section 2.1 of this SOW.

Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available on the internet at the Department of Defense Single Stock Point (DoDSSP) at https://assist.dla.mil. DoD Directives, Instructions and Publications documents, as well as other services publications at DoD Issuances website at:

http://www.dtic.mil/whs/directives/. Non- Government documents should be obtained from the commercial sources.

Requests for copies of documents not available from sources listed above should be directed to the designated Government technical point of contact for the Basic Ordering Agreement (BOA).

3.0 REQUIREMENTS

Requirements contained herein describe at the contract level the Deliveries that are associated with this SOW. The individual Job orders will further define specific requirements and will provide the necessary details via a statement of objectives, statement of work, or detailed specification.

3.1. Design and Engineering

The Contractor shall provide a hardware design for requirements as detailed in the Job order. The Contractor shall make maximum use of Commercial Off the Shelf (COTS) and Non-Developmental Items (NDI), modified as necessary, to meet the requirements of this SOW. The Contractor shall minimize obsolescence by selecting products that will avoid or resolve hardware and software/firmware obsolescence issues, refer to MIL-HDBK-470A Notice 2.

3.1.1. Design Analysis

The Contractor shall conduct a detailed analysis of the proposed hardware and software design. Detailed physical and performance design characteristics shall be specifically identified including, where applicable, the engineering decision process for using one methodology over another. The Contractor shall include a discussion of alternatives and the ramifications thereof, risk assessments and trade-offs made and proposed logistic support/level of repair.

The Contractor shall present the results of the design analysis at the Preliminary Design Review (PDR), supported by the deliverables listed in this SOW section. The Contractor shall provide a Technical Report – Studies/Services, Drawing Tree identifying each of the major assemblies/sub- assemblies, software modules, manufacturer names, model, and product/part numbers. If the Job order requires, the Contractor shall also provide a Reliability Prediction and Documentation of Supporting Data, Reliability Analysis Report documenting the study’s performance and providing a system reliability prediction.

CDRL A001 - TECHNICAL REPORT – STUDY/SERVICES, DRAWING TREE

CDRL A002 - RELIABILITY PREDICTION AND DOCUMENTATION OF SUPPORTING DATA,

RELIABILITY ANALYSIS REPORT

3.1.2 Software/Firmware Engineering

The Contractor shall perform all necessary software/firmware engineering efforts to design, develop, test, evaluate, and provide software/firmware products, services, and artifacts that implement the capabilities stated in the Job order. The details of those efforts, including the required data deliverables and reviews, are described in the subsequent paragraphs of this SOW. The Government desires unlimited technical data rights for software/firmware, middleware, and modeling artifacts. The Contractor shall minimize the amount of unique non-commercial software/firmware that must be developed/modified in the design of all deliverables.

3.1.2.1 Software/Firmware Design

To the maximum extent possible the Contractor shall implement open, modular software/firmware architecture, composed of Software Components (SC), which minimize coupling and inter-dependencies. If required by Job order, the Contractor shall provide a Software Requirements Specification (SRS). The SRS shall include all middleware/interfaces and software/firmware, with associated details, to ensure requirements are met. If required by Job order, the Contractor shall develop a Software Design Description (SDD) that describes the architectural modularity and detailed design of the software/firmware/middleware component.

CDRL A003 - SOFTWARE REQUIREMENTS SPECIFICATION (SRS)

CDRL A004 - SOFTWARE DESIGN DESCRIPTION (SDD)

3.1.2.2 Software/Firmware Development

The Contractor shall develop any software/firmware/middleware not available in the open market. Per Job order, the Contractor shall develop and deliver a Software Development Plan (SDP), based upon guidance found in IEEE/EIA 12207 and in accordance with (IAW) CMMI requirements such as CMMI-SE/SW/IPPD/SS. The software/firmware/middleware shall include functions as specified by Job order. Open Architecture conventions shall be used in this development and shall be included in the Contractor’s SDP. Any unique support items developed during the software/firmware/middleware development process shall be Government property and any non-unique support items shall be available to the Government for review/approval as required. The SDP shall discuss software/firmware/middleware design integrity, quality and stability addressing Configuration Management (CM), defect tracking, peer reviews and other associated processes. The SDP shall detail the software/firmware build environments. The Contractor shall use software/firmware management indicators and metrics to aid in managing the software/firmware/middleware development process and communicating its status to the Government.

The Contractor shall define a corrective action process for identifying software/firmware/middleware development impacts and resolution when goals are not met. This process shall be documented in the SDP.

The Contractor shall define the software Operating Environment (OE) and manage the OE baseline throughout the development process. Changes to the OE baseline shall be processed in accordance with the Government approved Contractor’s Configuration Management (CM) Plan. The Contractor shall obtain Government approval of any OE change before proceeding with software/firmware/middleware development. The Contractor shall develop a Software Version Description (SVD). The SVD shall detail all Operating Systems with their associated kernel version, configuration, operational libraries and firmware.

CDRL A005 - SOFTWARE DEVELOPMENT PLAN (SDP)

CDRL A006 - SOFTWARE VERSION DESCRIPTION (SVD)

CDRL A007 - CONTRACTOR’S CONFIGURATION MANAGEMENT PLAN

3.1.2.3 Commercial Off-the-Shelf (COTS) Software/Firmware

The Contractor shall provide to the Government all COTS based software/firmware/middleware products, along with supporting documentation and all required runtime licenses. This software/firmware/middleware shall include all COTS software/firmware/middleware incorporated into the OE baseline(s) as well as software/firmware/middleware packages utilized to generate OE baselines but not incorporated into the OE. The Contractor must ensure interoperability of such software/firmware/middleware with the OE and shall document any interdependencies (such as minimal revision required) in the appropriate SVD(s). All licensing requirements/restrictions for each COTS product shall be documented in the SVD. This documentation requirement includes all delivered software/firmware/middleware licenses necessary to provide the system capabilities and support full lifecycle implementation.

CDRL A006 - SOFTWARE VERSION DESCRIPTION (SVD)

3.1.2.4 Software/Firmware Testing

The Contractor shall plan and conduct SC-level tests for all developed and modified COTS software/firmware/middleware SCs. The Contractor shall identify and document test cases describing their purpose, the functions being tested, the test environment, and the test cases as part of the Software Test Plan (STP), Software Test Description (STD) and Software Test Reports (STR). The Contractor shall conduct the SC test and record the results in accordance with the SDP and applicable SRS and SDD documents.

The Contractor shall plan and conduct software/firmware/middleware integration testing. Iterative software/firmware/middleware testing shall include additional Computer Software Configuration Item (CSCI) and external interfaces ensuring requirements compliance and sub-system stability. This process is continued until all

CSCIs and interfaces are integrated and tested. The Contractor shall conduct this testing in accordance with the Contractor’s STP.

CDRL A005 - SOFTWARE DEVELOPMENT PLAN (SDP)

CDRL A008 - SOFTWARE TEST PLAN (STP)

CDRL A009 - SOFTWARE TEST DESCRIPTION (STD)

CDRL A010 - SOFTWARE TEST REPORT (STR)

3.1.2.5 Software/Firmware Products

The Contractor shall develop Software Product Specifications (SPS) for each approved software/firmware/middleware product baseline. The Contractor shall identify all software/firmware/middleware licensing requirements and any software/firmware/middleware usage restrictions. The Contractor shall deliver all required software/firmware/middleware licenses with the final software/firmware/middleware product. The SPS shall ensure software/firmware/middleware and software/firmware revisions are under CM control. The Contractor shall deliver the Computer Software Products including libraries and software/firmware/middleware packages, as well as all software/firmware/middleware tools/utilities. The Contractor shall successfully complete qualification testing of the computer software/firmware/middleware products prior to submission.

CDRL A011 - SOFTWARE PRODUCT SPECIFICATION (SPS)

CDRL A012- COMPUTER SOFTWARE PRODUCT

3.1.2.6 Software/Firmware Delivery and Transition

The Contractor shall prepare a Software/Firmware/Middleware Support Manual (SFSM) as required by individual Job Orders. The SFSM shall contain detailed technical information addressing the processes and resources required to build software/firmware/middleware. In addition, the SFSM shall include file format and data structures used in downloadable datasets and system logs, and describe processes and associated equipment to load and verify software/firmware/middleware on system hardware devices that are not defined in a CSCI. The Contractor shall prepare, with the Government, the Software Transition Plan (STRP) that shall accompany the final Government accepted software/firmware/middleware release products and artifacts. This plan shall also be accompanied with a current SVD and SFSM.

CDRL A006 - SOFTWARE VERSION DESCRIPTION (SVD)

CDRL A013 - FIRMWARE SUPPORT MANUAL (FSM), SOFTWARE FIRMWARE SUPPORT MANUAL

(SFSM)

CDRL A014 - SOFTWARE TRANSITION PLAN (STRP)

3.1.3 Technical Data Package (TDP)

The Contractor shall develop, maintain, and deliver a TDP in accordance with MIL- STD-31000A. The TDP shall include all components, sub-assemblies, and final-assemblies. The Contractor shall document any test requirements on the components, sub-assemblies, and final-assemblies necessary to ensure the characteristics of performance and include these in the TDP. Material and process specifications, special inspection equipment drawings and special tooling drawings and their associated lists shall be included in the TDP for complete product definition and total design disclosure. The TDP shall define the connectors and the pin- outs for all Job Order deliverables.

The TDP shall contain, but not be limited to, drawings, parts lists, data lists, wiring lists, schematics, interconnect diagrams, special tooling drawings, specifications, special packaging instructions that include storage and shipping containers and any requirements per MIL-STD-129P (4), MIL-STD-130N, MIL-STD-2073-1E and AR 700-15 , source control drawings, specification control drawings, cable dressing techniques, software/firmware/middleware version description documents, software/firmware/middleware, source code, gerber files and interface control documents and information for both hardware and software/firmware/middleware, operating systems, and artifacts.

The Contractor shall develop Installation Control Drawing Source Data when applicable.

The Contractor drawings and associated lists shall be developed and structured IAW ASME Y14.24 and MIL-STD- 31000A. Classified portions of the TDP shall be handled in accordance with approved security procedures and the DD Form 254. The Government will take configuration control of the TDP at the end of the Period of Performance (PoP) of each Job Order. The contractor shall modify/revise the TDP as necessary to obtain Government approval of the TDP prior to Government acceptance of each TDP.

CDRL A015 - TECHNICAL DATA PACKAGE

CDRL A016 - INSTALLATION CONTROL DRAWING, SOURCE DATA

3.2 FABRICATION

3.2.1 Engineering Development Models (EDM)

After successful completion of PDR, the Contractor shall fabricate EDMs and associated software elements in support of Contractor in-house testing to verify the system design meets the functional and performance requirements. The Contractor shall complete a Factory Acceptance Test (FAT), as described below, for each EDM.

Upon successful completion of FAT, EDM’S will be delivered as specified in the Job Orders. During the fabrication process, the Contractor shall correct any design characteristics that are found to inhibit or make fabrication unnecessarily costly with the proviso that these corrections do not adversely affect system functional or performance capabilities.

3.2.2 Pre-production Units (PPU)

After successful completion of the EDM testing and CDR , the Contractor shall fabricate PPUs of the approved system design, including both Hardware and Software element, to support Environmental Qualification Testing (EQT), training, system integration tests and Developmental Tests (DT). The Contractor shall complete a Factory Acceptance Test (FAT), as described below, for each PPU prior to EQT. Following EQT, the Contractor shall update the PPUs to incorporate all changes to the design, design documentation and processes resulting from EQT and restore the PPUs to a condition representative of the updated design. The Contractor shall complete a Factory Acceptance Test (FAT), as described below, for each PPU following restoration.

3.2.3 TESTING

The Contractor shall prepare a Test Plan, Master Test Plan (MTP) that employs an integrated test and evaluation strategy designed to provide continuous insight into the design and performance of the EDMs and PPUs. The MTP shall be the top-level working document that addresses all testing anticipated by the Contractor and its subcontractors, and encompasses all major system and component level testing. At a minimum, the MTP shall address asset allocation and sequencing and unique or long lead test support equipment requirements.

The Contractor shall perform all testing in accordance with the MTP and Test Procedure, Master Test Procedure.

The contractor shall reference MIL-HDBK-781A for guidance on testing methods. The Test Procedure, Master Test Procedure shall include procedures for all testing required in this SOW. The Contractor shall develop a Test/Inspection Report for any test performed.

CDRL A017 - TEST PLAN, MASTER TEST PLAN (MTP)

CDRL A018 - TEST PROCEDURE, MASTER TEST PROCEDURE

CDRL A019 - TEST/INSPECTION REPORT

3.2.3.1 Interface Tests

When required by Job Order, the Contractor shall develop an Interface Test Plan as part of the MTP to demonstrate that the components communicate effectively and processes the input/output data correctly.