12-R-0125.pdf

CODE

(Hour)

PAGE(S)

until 03:00 PM local time 06 Sep 2013

X

A X B X C X D

EX

X

G F 57 - 62

63 - 73 X H steven.shultz@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 73

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

N68936 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 Page 2 conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

STEVEN J. SHULTZ (760) 939-8895

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

1 - 2 3 - 5

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

6 - 18 19 - 20

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

21 - 22

23 - 24 X K REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 25 - 31 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 32 - 43 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

44 - 55

PART II - CONTRACT CLAUSES

CDR NAWCWD CODE 254100D

ATTN: S. SHULTZ

(760) 939-8895

429 E BOWEN RD - STOP 4015

CHINA LAKE CA 93555

(760) 939-8895

(760) 939-0528FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.

130XXX

5. DATE ISSUED

07 Aug 2013

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N68936-12-R-0125

Section A - Solicitation/Contract Form

CLAUSES INCORPORATED BY FULL TEXT

FOR YOUR INFORMATION:

The following addresses and points of contact are provided:

Name: Steve Shultz Phone: (760) 939-8895

DSN: 437-8895

FAX: (760) 939-0528

Email address: Steven.Shultz@navy.mil

U.S. Postal Service Mailing Address:

COMMANDER

CODE 254100D (S. Shultz – 760-939-8895)

NAVAIRWARCENWPNDIV

429 E. BOWEN RD. MAIL STOP 4015

CHINA LAKE, CA 93555-6108

Direct Delivery Address (UPS, FedEx, etc):

COMMANDER

CODE 254100D (S. Shultz)

NAVAIRWARCENWPNDIV

BLDG 982, MAIL STOP 4015

CHINA LAKE, CA 93555-6108

CONTRACTING OFFICER

Name: Collin Kyte Phone: (760) 939-2634

DSN: 437-2634

FAX: (760) 939-0528

Email address: Collin.Kyte@navy.mil

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0001 1,090,058 Hours Labor

CPFF

Labor (inclusive of direct subcontractor labor) hours. Specific quantities and required labor categories will be determined at the Order level.

FOB: Destination

PURCHASE REQUEST NUMBER:

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

UNIT UNIT PRICE MAX AMOUNT

0002 UNDEFINED Lot Other Direct Costs (ODCs)

COST

Specific quantities and costs will be determined at the Order level.

UNIT UNIT PRICE MAX AMOUNT

0003 UNDEFINED Lot Travel

COST

Specific quantities and costs will be determined at the Order level.

ITEM NO SUPPLIES/SERVICES AMOUNT

0004 Contract Data Requirements List (CDRLs)

NSP

See Exhibit A.

5252.211-9503 LEVEL OF EFFORT (COST REIMBURSEMENT) (NAVAIR)(DEC 2012)

(a) The level of effort estimated to be ordered during the term of this contract/order is 1,090,056 man-hours of direct labor including authorized subcontract labor, if any. The contractor shall not, under any circumstances, exceed one hundred (100%) percent of the total level of effort specified in the contract/order. The estimated composition of the total man-hours of direct labor by classification is as follows:

Labor Category Total Man-hours RC92 Off-Site 19,200 BPA Design Engineering 5,000 BPA Systems Engineering 10,000 BPA Software Engineer 10,000 BPA Engineering Support 10.000 BPA Engineering Technicians 15,000 BPA Program Management 10,000 BPA Business Management 5,000 BPA Major Subcontract Buyers 5,000 BPA Quality – Engineering 5,000 PM BM - Engineering Support 2,632

PM BM - Program Management 27,962 PM BM - Business Management 7,971 PM BM Major Subcontract Buyers 2,632 PRB RC 88 Prog Mgmt 50,000 PRB RC 91 Eng 109,253 PRB RC 92 Lead Eng 109,253 PRB RC 93 Princ Eng 350,214 PRB RC 94 Sr Eng 95,009 PRB RC 98 Sys Eng 10,000

BAL ADMIN MGMT 7,237

BAL SYS Engineer 48,249

BAL SYS SR. ENG 48,251

BAL SW ENG 64,106

BAL SW SR. ENG 19,612

BAL PM 18,041

AMH ADMIN MGMT 300

AMH SYS Engineer 2,000

AMH SYS SR. ENG 2,000

AMH SW ENG 2,700

AMH SW SR. ENG 800

AMH PM 800

NGTS RC94 16,800

NGTS Cont. 36

Total 1,090,058

(b) FAR Clause 52.232-20, "Limitation of Cost" applies to fully funded orders and FAR Clause 52.232- 22, "Limitation of Funds" applies to incrementally funded orders. Nothing in this clause amends the rights or responsibilities of the parties hereto under either of those two clauses. In addition, the notifications required by this clause are separate and distinct from any specified in either FAR Clause 52.232-20 or FAR Clause 52.232-22.

(c) In the event that less than one hundred (100%) percent of the established level of effort of the contract/order is actually expended by the end of the performance period, the Government shall have the option of:

(1) Requiring the Contractor to continue performance, subject to the provisions of the FAR Clause 52.232-20 or 52.232-22, as applicable, until the effort expended equals 100% of the established Level of Effort; or

(2) Effecting a reduction in the fixed fee by the percentage by which the total expended man-hours is less than one hundred (100%) percent of the established Level of Effort.

(d) The contractor agrees that effort performed in fulfillment of level of effort obligations under this contract shall include only verifiable effort in direct support of the work specified. It shall not include efforts such as work performed in transit to or from an employee's usual workplace, work during lunchtime activities, or effort performed at other non-work locations.

(e) In performing the contract/order, the contractor may use any reasonable combination of hours for the labor categories in support of section C of this contract/order.

Section C - Descriptions and Specifications

HEADER

CLINs 0001, 0002 and 0003 – Work shall be performed in accordance with the Statement of Work.

CLIN 0004 – Data shall be delivered in accordance with the Contract Data Requirements Lists (CDRLs), Exhibit A.

STATEMENT OF WORK

STATEMENT OF WORK (SOW)

FOR

AIRBORNE ELECTRONIC ATTACK (AEA)

AND ELECTRONIC SUPPORT SYSTEMS

30 July 2013

1.0 BACKGROUND/SCOPE

1.1 Background. The AEA Integrated Product Team (IPT) at the Naval Air Warfare Center, Weapons Division (NAWCWD) Point Mugu, CA has been tasked by PMA-234 as the EA-6B Weapon System Support Activity (WSSA) to provide direct fleet support through design, development, integration, and test of updates to the EA-6B avionics and weapons systems.

NAWCWD has been tasked by PMA-265 as the F/A-18 and EA-18G WSSA. The AEA IPT at NAWCWD Point Mugu is the WSSA design agent for the AEA subsystem. The AEA IPT is responsible for the design, development, integration, and test of the EA-18G AEA and related subsystems.

1.2 Scope. The SOW establishes the requirements for Engineering, Technical and Programmatic services for development of products within the AEA IPT located at the NAWCWD, Point Mugu, California.

The major requirement for this effort will result in System Configuration Set (SCS) Implementation for the EA-6B and EA-18G, which will require Northrop Grumman Aerospace Systems (NGAS) to design, develop, and implement upgrades to software and ancillary hardware. These upgrades must be completed prior to the software and hardware being released for Operational Testing (OT). The deliverables for this effort will include, but are not limited to: benches, hardware modifications, weapons replaceable assemblies (WRAs), software models, non-recurring Engineering Change Proposals (ECPs), and studies.

Other deliverables include system improvement and demonstration products such as proposed prototypes, pre-production products, support equipment enhancements, or simulations and models of weapons systems. System improvements will also provide obsolete parts replacements, improved processors, and technology demonstrations. The contractor shall also conduct analysis and definition of statements of requirements identified by the Government and correction of anomalies in software or hardware identified after release to the Government for OT and during fleet utilization of the SCS. Support requirements include updates to the Flight Plan options documents, AEA IPT on-site engineering, and proposal preparation for product or completion orders. Other services will include studies and analyses that will require NGAS to investigate future capabilities, provide analysis of alternatives, and deliver documentation that may result in SCS implementation of system improvement or demonstration products.

Platforms to be supported include EA-6B, EA-18G, EA-18G Royal Australian Air Force (RAAF) Foreign Military Sales (FMS) configuration, and other advanced electronic attack derivatives.

1.3 Contract Work Environment. The contractor shall be required to utilize AEA IPT processes and procedures. In this IPT environment, contractor personnel will be responsible for knowing and using specific Government work processes. The contractor’s consistent and skillful application of these work processes is critical to the NAWCWD Software Process Improvement Initiative described in Section 2.8.

Contractor personnel will be interfacing with other Government and contractor team members, using existing NAWCWD special hardware and lab facilities, and accessing NAWCWD test aircraft on an a regular basis.

2.0 APPLICABLE DOCUMENTS

The following documents are applicable to this SOW. Additional documents may be applicable and will be identified at the task order level.

2.1 Military Standards

MIL-STD-961E (w/Change 1), 2 April 2008, Standard Practice for Defense and Program-Unique Specifications, Format and Content MIL-STD-973, 17 April 1992, Configuration Management MIL-PRF-49506, 11 November 1996, Logistics Management Information MIL-STD-1806, 12 June 1995, Marking Technical Data Prepared by or for the Department of Defense

2.2 Instructions and Guides

NAVAIR 00-25-300, March 2002, Technical Directives Systems MIL-HDBK-61A, 7 February 2001, Configuration Management Guidance NAWCWD 3432.1A, 15 July 2002, Operations Security NAWCWDINST 5500.1, 13 Feb 2012, Command Security Program Regulation

2.3 Industry Standards

Software Development and Documentation IEEE/EIA 12207.0, IEEE/EIA 12207.1 AND IEEE/EIA 12207.2

CMU/SEI-2002-TR-012, 2006, Capability Maturity Model Integration (CMMI), Version 1.1 CMMI for Systems Engineering, Software Engineering, Integrated Product and Process Development, and Supplier Sourcing (CMMI-SE/SW/IPPD/SS, V1.2) Staged Representation, Carnegie Mellon University

The Government will provide all necessary reference documents not generally available to the Contractor as required. Throughout the life of the contract, if any instruction or document is replaced or superseded, the replacement or superseding instruction or document shall be applicable to the requirements defined in this SOW.

2.4 Clinger-Cohen Act

In 1996, Congress enacted the Clinger-Cohen Act (CCA) requiring agencies to use a disciplined capital planning and investment control process to acquire, use, maintain and dispose of information technology.

In accordance with the following Department of Defense Directive (DoDD), Department of Defense Instruction (DoDI), Office of the Secretary of Defense (OSD) memo, and Secretary of the Navy Instruction (SECNAVINST), CCA compliance is required for all programs that contain IT, including IT in weapons and weapons system programs. The law provides authority to the agency’s Chief Information Officer (CIO) to manage IT resources effectively. The authority to grant compliance with CCA and approve the Information Assurance (IA) strategy depends on the Acquisition Category (ACAT).

a. DoDD 5000.01 “The Defense Acquisition System,” 12 May 2003, Certified Current as of 20 November 2007

b. DoDI 5000.02, “Operation of the Defense Acquisition System,” 8 December 2008

c. OSD Memo, “Clinger-Cohen Act Compliance Policy,” 8 March 2002

d. SECNAVINST 5000.2E, “Implementation and Operation of the Defense Acquisition System and the Joint Capabilities Integration and Development System,” 1 September 2011

2.5 Information Assurance (IA)

NAVAIR’s Information Assurance (IA) Program is a unified approach to protect unclassified, sensitive or classified information, and is established to consolidate and focus efforts in securing that information, including its associated systems and resources. IA is required operationally throughout the DON. DON CIO (Chief Information Officer) is responsible for IT within the Navy, as mandated by the Clinger-Cohen Act, and is the lead for departmental compliance with the Federal Information Security Management Act of 2002.

All IA shall be in compliance with the following listed instructions to include those referenced within the below listing:

a. ASD (NII) Directive-Type Memorandum (DTM) 08-027 – Security of Unclassified DoD Information on Non-DoD Information Systems, 31July 2009

b. Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 3170.01 (series), “Joint Capabilities Integration and Development System”, 10 January 2012

c. CJCSI 6211.02 (series) – “Defense Information System Network (DISN): Policy and Responsibilities,” 24 January 2012

d. CJCSI 6212.01 (series) – “Interoperability and Supportability of Information Technology and National Security Systems,”21 March 2012

e. CJCSI 6250.01 (series) – “Satellite Communications,” 30 November 2012

f. CJCSI 6510.01 (series), “Information Assurance (IA) and Computer Network Defense

(CND),” 9 February 2011

g. Chairman of the Joint Chiefs of Staff (CJCSM) 6510.01 (series) – “Cyber Incident Handling

Program”, 10 July 2012

h. Chief of Naval Operations/Headquarters, United States Marine Corps (CNO) N614/HQMC

C4 – “Navy-Marine Corps Unclassified Trusted Network Protection (UTN-Protect) Policy, Version 1.0,” 31 October 2002

i. Defense Acquisition Guidebook – Chapter 7 “Acquiring Information Technology, Including National Security Systems,” Section 7.5 “Information Assurance (IA)”

j. DoD 5220.22-M, “National Industrial Security Program Operating Manual,” February 28, 2006 (NISPOM)

k. DoD 8570.01-M, “Information Assurance Workforce Improvement Program”, 19 Dec 2005 (Incorporating Change 2, Feb 25, 2010)

l. DoDD 8000.01 “Management of the Department of Defense Information Enterprise,” February 10, 2009

m. DoDD 8100.02, “Use of Commercial Wireless Devices, Services, and Technologies in the Department of Defense (DoD) Global Information Grid (GIG), 14 April 2004, Certified Current as of 23 April 2007

n. DoDD 8500.01E (series), “Information Assurance (IA),” October 24, 2002, Certified Current as of April 23, 2007

o. DoDD 8570.01 “Information Assurance Training, Certification, and Workforce Management,” August 15, 2004, Certified Current as of April 23, 2007

p. DoDI 4630.8, “Procedures for Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS),” June 30, 2004

q. DoDI 8500.2, “Information Assurance Implementation,” February 6, 2003

r. DoDI 8510.01, “DoD Information Assurance Certification and Accreditation Process

(DIACAP),” November 28, 2007

s. DoDI 8520.02, “Public Key Infrastructure (PKI) and Public Key (PK) Enabling, 24 May

t. DoDI 8551.1, “Ports, Protocols, and Services Management (PPSM),” August 13, 2004

u. DoDI 8580.1, “Information Assurance in the Defense Acquisition System,” July 9, 2004

v. DoDI 8581.01, “Information Assurance (IA) Policy for Space Systems Used by the

Department of Defense,” June 8, 2010

w. DON CIO Memo 02-10, “Department of the Navy Chief Information Officer Memorandum

02-10 Information Assurance Policy Update for Platform Information Technology,” 26 April

x. DON ltr 5239 NAVAIR 726/2322 of 18 Feb 09, “NAVAIR Data at Rest Policy”

y. Federal Information Processing Standards Publications (FIPS PUB)

[http://www.itl.nist.gov/fipspubs/by-num.htm]

z. (National Security Telecommunications and Information Systems Security Policy) NSTISSP

No. 11, “Revised Fact Sheet National Information Assurance Acquisition Policy,” July 2003.

For more information on determining the applicability of these documents to the specific requirements of your program, contact your local information assurance point of contact for assistance. An IA POC is available via the NAVAIR National Help Desk at https://nhd.navair.navy.mil or 1-888-292-5919

2.6 Enterprise Architecture

Contractor Networks and connections: Contractor-owned and operated networks are prohibited on any Naval Air Systems Command (NAVAIR) facility or site in support of this contract. The contractor may access non-government, external IP space via the NAVAIR-provided VPN Outreach service or NAVAIR CIO approved Internet Protocol (IP) service.

IT Approval: The contractor shall not purchase any IT equipment on behalf of NAVAIR in support of a contract without a NAVAIR CIO signed IT approval.

3.0 REQUIREMENTS

The Government will provide the specific technical documentation, guidelines and delivery requirements under individual task orders. When ordered under individual task orders, the contractor shall provide the following technical services:

3.1 Program Management. The contractor shall provide the personnel, resources and project management necessary for the SCS Implementation for the EA-6B and EA-18G.

3.1.1 The contractor shall develop and maintain plans, milestone charts, reviews, analyses, evaluations, and recommendations, which will provide the technical and scientific evidence necessary to facilitate program development decisions. The contractor shall develop and maintain an on-line reporting system to include earned value tracking and reporting of programmatic planning, tracking and monitoring progress, status and cost reports. (CDRL A001, A002, A00J and A00N)

3.1.2 The contractor shall develop technical engineering and presentation graphics and other visual aid requirements as defined in individual task orders. The contractor will be required to develop and present visual aids reflecting the status of assigned tasks. (CDRL A00A)

3.1.3 The contractor shall develop, review and maintain programmatic documentation.

Documentation shall include:

Software Life-Cycle Management Plan Software Support Transition Plan Software Development Plan Tactical Software Support Plan Software Support Requirements Analysis Quarterly Program Reports Program/Technical Reports Formal and informal Training Plans Integrated Schedules Procedures and Processes Task Order and Contract Summary Reports

(CDRLs A001, A002, A006, A00J, and A00K)

3.1.4 Utilizing a Government-provided Work Breakdown Structure (WBS), the contractor shall develop and deliver a monthly report which provides a by-person and by-WBS task breakout of the hours and burdened cost expended for both the respective reporting period and the cumulative period to date. In addition, the monthly report shall provide the completion percentage of each WBS task. (CDRL A001)

3.1.5 In performance of this contract, the contractor shall be required to host/attend meetings regarding various subjects related to the contract requirements. Meetings will be held at Department of Defense (DOD) activities and contractor’s facilities and may include engineering briefings being conducted at various unclassified and classified DOD and contractor test ranges and facilities. In support of this effort, the contractor shall utilize the IPT's processes and procedures. (CDRLs A003, A004 and A00A)

3.1.6 The contractor shall collect and provide the metric data using the processes/procedures as described in SOW section 2.3. (CDRL A001)

3.2 Modification and Upgrade of Software and Equipment

3.2.1 Engineering: The contractor shall provide modification and upgrade of software and equipment for the EA-18G and EA-6B aircraft AEA and related subsystems in accordance with NAVAIR Systems Engineering Guide, for existing, future, and proof of concept systems. The contractor shall plan, design, develop, procure, fabricate, integrate, test, evaluate, operate, repair, maintain, upgrade, and document the system hardware, software, and firmware. (CDRLs A002, A005, A006, A00B, and A00C)

3.2.2 Software Maturation: The Contractor shall perform research, development, integration, test, evaluation, proof of concept development, and analysis of software and tools. The Contractor shall integrate the developed software into the specified systems environment, including delivery of necessary hardware to the appropriate laboratory, such as hardware modified by the contractor and prototypes developed by the contractor. The Contractor shall follow software development guidelines using applicable Government or industry standards in accordance with paragraph 2.0. The contractor shall submit a Software Development Plan (SDP) subject to Government review and approval. The SDP shall follow the framework of IEEE/EIA Std 12207 regarding subject content, level of detail, and completeness. The contractor shall comply with the SDP during contract performance. The SDP shall serve as the benchmark for the contractor’s software development effort. The contractor shall be required to use only those parts of IEEE/EIA Std 12207 that apply to the software development efforts required under task orders. For work associated with sustainment of fielded software systems, the SDP needs to cover only those parts of IEEE/EIA Std 12207 processes and activities that are associated with the work content (such as the Maintenance Process and the Problem Resolution Process). If any major enhancements are to be made to such systems, the SDP shall cover all processes that are applicable to such efforts. The contractor shall periodically evaluate and update the SDP, as a part of continuous process improvement subject to Government review and approval. (CDRL A00K)

3.2.3 Laboratory Engineering: The contractor shall plan, design, develop, fabricate, integrate, test, evaluate, operate, repair, maintain, upgrade, and document the laboratory system hardware, software, and firmware. Laboratory modifications and upgrades include engineering benches, integration and test benches, development benches, workstations and environments, EA-18G integration test stations (ITS), EA-18G system emulation laboratories (EASELs), EA-6B benches, system and avionics emulations and simulations, RF Threat environment simulators (such as the AMES III), development tools, test tools, analysis tools, monitor tools, debug tools, flight test and analysis tools, etc. The contractor shall maintain, update and create new engineering drawings and documentation for the laboratory systems. These artifacts will become the property of the government upon their acceptance by the COR. (CDRLs A002, A005 and A006)

3.2.4 Process Improvement: The contractor shall improve software development processes in accordance with the initiative identified in paragraph 2.8. The contractor shall improve the processes used to develop the products listed in paragraph 3.1.3 to be more effective and efficient.

3.2.5 On-Call Field Engineering Services: The contractor shall provide field technical engineering services on an “on-call” basis for the purpose of system installation, integration, maintenance, support, troubleshooting and repair. The contractor shall submit a trip report documenting the results of field engineering services. (CDRL A002)

3.2.6 Integration and Test: The contractor shall plan, prepare and conduct system and software integration, tests, experiments, and demonstrations on modified or upgraded software and equipment.

The contractor shall support lab, ground, and flight integration and test events by developing and updating integration and test plans and procedures; verifying system engineering requirements; and troubleshooting, analyzing, recommending, and incorporating corrective actions. The contractor shall evaluate integration and test plans to ensure consistency with systems specifications, including requirements traceability. The contractor shall conduct tests to verify and validate compliance with system specifications. The contractor shall provide support of aircraft system test in the Development Test and Operational Test (DT/OT) environment. (CDRLs A002, A005, A007, A008, A00F and A00G)

3.2.7 Studies and Analyses: The contractor shall provide estimates, design trade-off and risk assessment studies. In each study, the contractor shall include analysis of operations, organization, hardware, software, and support requirements. System analysis will include time and sensitivity analyses.

Technology validation experiments and/or prototyping hardware and software will be identified as appropriate. The contractor shall provide recommendations on the most cost-effective approach to systems development and maintenance through its life cycle. Those areas for application of state-of-the-art methodologies, including Commercial-off-the-Shelf (COTS) and Non-Developmental Item (NDI) will be identified which will provide the highest payoff in system performance, cost, reliability, and maintainability. Studies and analyses shall be prepared and submitted. (CDRLs A002, A00B, and A00C)

3.2.7.1 The contractor shall review, evaluate, and verify that developed system, subsystem, configuration item, and support equipment specifications meet the technical adequacy specified in the individual task orders and provide documentation updates. (CDRLs A002 and A005)

3.2.8 Requirements Analysis: The contractor shall assist in requirements analysis by: (1) conducting studies and analyses to develop system concepts, including functionality and performance requirements for existing, upgraded, and new systems; (2) identifying life cycle support requirements; (3) defining interface requirements; and (4) preparing requirement and functional baseline specifications, plans and documents, in accordance with paragraph 3.1.3 and documentation as required by individual task orders. (CDRLs A002, A005, A006, A00D, and A00M)

3.2.9 Software Requirements: The contractor shall perform Software Requirements Analyses which define and analyze a complete set of functional, performance, interface, operator, and qualification requirements for each Computer Software Configuration Item (CSCI). The requirements discussed shall be derived from the System or Segment Specification or other comparable requirement document.

(CDRLs A002, A005, A006, A00E, and A00M)

3.2.9.1 The contractor shall develop a top-level, detailed, and/or lower level modular design for each CSCI. A detailed design of each CSCI shall be generated and documented. (CDRLs A002, A005, A006, and A00E)

3.2.9.2 The contractor shall code, integrate and test each unit within the detailed design.

3.2.9.3 The contractor shall: (1) evaluate testability of computer program design in development; (2) verify coding to ensure that any changes do not adversely affect weapon system performance and that coding satisfies government approved requirements; (3) perform independent CSCI level tests in accordance with test plans as approved or generated by the Government for each CSCI; (4) evaluate the software test programs in order to ensure that they meet the current software configuration; and (5) provide post test analyses. The contractor shall identify conflicting, not testable, ambiguous requirements affecting software functions, as well as inadequate software data requirements. (CDRLs A002, A005, A006, A007, A008, A00C, and A00G)

3.2.9.4 The contractor shall verify the software by conducting independent testing, code analysis, algorithm analysis, and review of the test procedures and results as specified in the individual orders.

Software portions may include areas critical to safety, equipment selection, mission critical performance, development schedule, and supportability. (CDRLs A002, A005, A006, A007, A008, A00B, A00C, and A00G)

3.2.10 Software Requirements Analysis: The contractor shall provide modifications and upgrades to the developed software through the use of Software Trouble Reports (STRs), Software Change Requests (SCRs), Software Change Proposals (SCPs), Software Problem Reports (SPRs), Discrepancy Reports (DRs), and System Anomaly Reports (SARs). The contractor shall participate in software design reviews, test readiness reviews, audits, code walk-throughs, working group meetings, and monitor qualification tests in accordance with paragraph 3.1.3. (CDRLs A002, A006, A007, A008, and A00G)

3.2.10.1 The contractor shall enter STRs, SCRs, SCPs, DRs, and SARs into the Government tracking system and update status throughout the investigation and resolution process. The contractor shall process these reports by conducting a preliminary engineering investigation to: (1) confirm that a change request is truly a new requirement or confirm that a reported problem is repeatable, and is in fact a software deficiency, not merely a symptom of a hardware malfunction, improper operation procedure or maintenance action; (2) confirm the problem has not been previously reported; (3) determine technical approaches to solving the problem or implementing the enhancement; and (4) provide impact analyses for each approach. Based on the results of the preliminary engineering investigation, the contractor shall prepare a preliminary SCP for SCRs and STRs to be processed through internal review, Technical Review Board (TRB), Software Change Review Board (SCRB), SCP Review, and Deficiency Change Review Board (DCRB) review.

3.2.10.2 The contractor shall develop the correction for the DR or approved software change proposed in the SCP. Developing the correction or approved software change may include detailed software design, coding, debugging, and testing. The SCP may be supported with marked-up requirements documents, specifications, and software design documentation. (CDRLs A002, A005, A006, and A00C)

3.2.10.3 The contractor shall support the testing of SCPs by developing test procedures, executing the test, and documenting the results. (CDRLs A002, A005, A006, A00B, and A00G)

3.2.10.4 The contractor shall propose modifications or upgrades for assigned problems, including source code, object files, and command procedures. (CDRLs A002 and A005)

3.2.10.5 The contractor shall code and debug software changes to implement the approved modifications or upgrades. Software, including source and load files shall be delivered by the contractor.

Software languages may include CMS-2M, TDY-43 assembly, 8080 family assembly, FORTRAN, PLM, PASCAL, C++, ADA and "C". The software delivered shall meet or exceed established defect criteria, and must be loadable and able to run on the applicable system. The contractor shall provide redlined change pages for specifications and user documentation impacted by each engineering solution. (CDRLs A002, A005, A006, and A009)

3.2.10.6 The contractor shall conduct problem investigation and analysis on Operational Flight Programs (OFPs) and Mission Support Programs (MSPs), and databases to identify deficiencies. (CDRLs A002, A005, A006, and A00C)

3.2.11 Engineering Change Proposals (ECPs) and Technical Directives (TDs): The contractor shall develop or evaluate TDs, and ECPs to establish requirements, testability, and technical merit. The contractor's evaluation will include risk assessment and recommendations for acceptance or rejection.

The contractor shall track all ECPs and report status. (CDRLs A002, A005, A006, A00B, and A00C)

3.2.12 Documentation: The contractor shall develop and maintain system documentation in accordance with paragraph 3.1.3. The contractor shall revise or update documentation in accordance with DOD and Military standards. Applicable systems documentation includes:

Mission Systems Operation and Function Description (MSOFD) Functional Operational Specification (FOS) Interface Design Specification (IDS) Program Performance Specification (PPS) Program Design Specification (PDS) Software Design Document (SDD) Interface Design Document (IDD) Software Requirements Analysis (SRA) Systems/Segment Specification (SSS) Independent Verification and Validation (IV&V) Plans Test Plans and Procedures Configuration Management Plans Software Development Plans System Requirements Specifications (SRS)/Systems Requirements Document (SRD)

System documentation shall be updated and maintained. (CDRLs A002, A005, A006, A007. A008, A00D, A00E, A00F, A00G, and A00M)

3.2.13 Data Management: The contractor shall provide data management services that include the identification and control of programmatic documents. This involves the identification, coordination, collation, validation, integration, control of data requirements, planning for the timely and economical acquisition of data, ensuring the adequacy of acquired data for its intended use, and management of data assets after receipt. Efforts shall be as detailed within the following sub-paragraphs. Individual task orders will provide technical guidance and CDRL item development and submittal instructions.

3.2.13.1 The contractor shall check the data for completeness, verify page count, and provide quality assurance review of formatted data. The contractor shall support the distribution of data (including change pages), monitoring of storage, retrieval, and disposal of data.

3.2.13.2 The contractor shall enter data elements into an automated Data Management tracking system. The contractor shall maintain the database and generate reports. (CDRLs A002, and A005)

3.2.14 Configuration Management: The contractor shall provide recommendations on configuration management requirements defined in individual task orders. The contractor shall develop, update, and implement plans, procedures, and actions for identifying, controlling, and verifying the technical aspects of acquisitions. Procedures will be established to: (1) identify and assure the integrity of documentation for the functional and physical characteristics of each Hardware Configuration Item (HWCI) and CSCI;

(2) control the changes to the HWCI and CSCI characteristics; and (3) record and report the processing of changes and the status of their implementation. Efforts shall be as detailed within the following sub-paragraphs. (CDRLs A002 and A005)

3.2.14.1 The contractor shall: (1) assess the impact of changes to system configuration item specifications; (2) determine if configuration item identification conforms to the functional interfaces established by system engineering; (3) ensure that configuration items are physically and logically compatible and can be operated and supported as intended; (4) assess the impact of changes; and (5) perform documentation traceability.

3.2.14.2 The contractor shall upgrade and maintain an automated configuration management and tracking database.

3.2.15 Communications and Data-link Services: The contractor shall design, develop, integrate and test systems, software, support tools, and decision aids to support the integration and maintenance of data, voice, and image link communication systems and networks. Link protocols include Combat Net Radio (CNR), Variable Message Format (VMF), Marine Tactical System (MTS), LINK-16, Joint Tactical Radio Systems (JTRS), Tactical Targeting Network Technology (TTNT), Internet Relay Chat (IRC) and Internet Protocol (IP) based data-link systems, and other advanced data link communication and network systems.

Tactical data broadcasts will include Integrated Broadcast Service (IBS) and Common Integrated Broadcast (CIB). Applications include new developments such as Electronic Warfare (EW) Battle Management, Cooperative Electronic Attack, Precision Targeting, and Time Sensitive Targeting.

(CDRLs A002, A005, A006, and A009)

3.3 Training

3.3.1 The contractor shall provide training services, through which personnel will learn to operate, maintain and provide life-cycle support of the AEA subsystem, including efforts associated with the design, development, and production of training services, devices, accessories, aids, equipment, plans, documentation and parts, as well as the execution of training services. The contractor shall provide Government user training on new program or application features, interfaces, or requirements. User training requirements will be identified within each Task Order. (CDRLs A002, A005, and A00A)

3.4 Fleet Services

The contractor shall provide fleet services such as performing problem resolution relative to aircraft installs, interconnection, software operation; and fleet and government personnel training as it pertains to the AEA subsystem.

3.5 IT Personnel Security Report. The contractor shall submit a status report that includes all employees requiring access to Government IT systems. (CDRL A00L)

4.0 TRAVEL

During performance of a task order, the contractor may be required to perform local and non-local travel to support the tasking. The contractor shall submit a request for travel in support of this contract. Each request will be submitted in advance (a minimum of 1 week) to the Government Contracting Officer's Representative (COR) for approval. Each travel request will minimally consist of:

Date of Request Delivery order number Employee(s) Date and duration of proposed travel Purpose of travel Destination Cost estimate (airfare, per diem, car rental, miscellaneous expenses)

Total travel allowance on the task order Total travel cost expended to date Approval signatures

Upon completion of each trip, the contractor shall submit a trip report in accordance with the technical guidance provided in CDRL A002.

5.0 DELIVERABLES

This section describes the data requested in support of this contract. Requested deliverable data is described using DD Form 1423-1, Contract Data Requirements List (CDRL). Contractor format will be given preference in an effort to secure best value products. Deliverable products and method of delivery shall be specified in individual task orders.

CDRL

ITEM

DESCRIPTION

A001 Contractor’s Progress, Status and Management Report A002 Technical Report – Study/Services A003 Conference Agenda A004 Conference Minutes A005 Revision to Existing Government Documents A006 Technical Data Package (Design Review Data Package) A007 Test/Inspection Report A008 Test Procedures A009 Computer Software Product End Item A00A Presentation Materials A00B Scientific and Technical Report A00C Engineering Change Proposal (ECP) A00D System/Segment Specification (SSS) A00E Software Requirements Specification (SRS) A00F Acceptance Test Plan A00G Software Test Plan (STP) A00H Operations Security (OPSEC) Plan A00J Performance and Cost Report (TO Expense Status) A00K Software Development Plan (SDP) A00L Status Report (Information Technology Personnel

Security) A00M Interface Design Document (IDD) A00N Contracting Officer’s Management Report

6.0 SECURITY

The contractor shall provide personnel with the appropriate security clearance levels for the work to be performed. Access to SECRET information is required in the performance of this contract and shall be in accordance with National Industrial Security Program Operating Manual (NISPOM), DoD 5220.22-M, dated February 2006. The contractor shall provide for the security of the information, hardware, and software in accordance with the NISPOM. Technical documentation shall be marked with the appropriate classification levels and shall include a distribution statement as defined in Distribution Statements on

Technical Documents, DoDD 5230.24, dated August 2012. The contractor shall employ Operational Security (OPSEC) measures to control unclassified information that could be considered mission/program sensitive in accordance with the attached DD Form 254. Unclassified technical information shall be protected from disclosure to unauthorized personnel in accordance with Withholding of Unclassified Technical Data from Public Disclosure, DoDD 5230.25, dated 18 August 1995. The contractor shall submit an OPSEC Plan. (CDRL A00H)

7.0 GOVERNMENT FURNISHED EQUIPMENT (GFE)/FACILITIES

7.1 Equipment. Upon Contractor request and Government approval, Government furnished property and data will be provided under the contract or individual task orders and will be returned to the Government when no longer required for performance of this contract or when requested by the Government.

7.2 Laboratories. The Government will furnish access to Government laboratories to accomplish tasking described in SOW. The Government reserves the right to control laboratory schedule and use of documentation and information required for the performance of this contract. The Government will supply the contractor with information on where and how to send contractor personnel security clearances when visiting these laboratories. Should there be additional forms for the use of contractor equipment in the laboratory, the Government will provide the procedures and forms to the contractor.

8.0 PLACE OF PERFORMANCE

The majority of performance is expected to take place at the contractor’s facilities or Point Mugu, CA at a Government facility. Performance may take place at other Government or contractor installations as identified in task orders. Support for multiple sites, including direct Fleet services that require SECRET clearance will be required. Sites may include the following Military sites:

Naval Air Station, Whidbey Island, Washington Marine Corps Air Station, Cherry Point, North Carolina Naval Air Warfare Center Weapons Division, Point Mugu, California Naval Air Warfare Center Weapons Division, China Lake, California Naval Air Warfare Center Aircraft Division, Patuxent River, Maryland RAAF bases in the Commonwealth of Australia

C-TXT REQUIRED ENTERPRISE-WIDE CONTRACTOR MANPOWER REPORTING

APPLICATION (ECMRA) INFORMATION

The contractor shall report ALL contract labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Airborne Electronic Attack (AEA) and Electronic Support Systems via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address https://doncmra.nmci.navy.mil.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://doncmra.nmci.navy.mil.

Section D - Packaging and Marking

CLIN PACKAGING AND MARKING INFORMATION

CLINS 0002 and 0004 shall be packaged in accordance with Clauses 5252.247-9507 and 5252.247-9508.

Specific packaging and marking instructions will be provided in individual orders, if applicable.

5252.247-9507 PACKAGING AND MARKING OF REPORTS (NAVAIR) (OCT 2005)

(a) All unclassified data shall be prepared for shipment in accordance with best commercial practice. Classified reports, data and documentation, if any, shall be prepared for shipment in accordance with the National Industry Security Program Operating Manual, DoD 5220.22-M.

(b) The contractor shall prominently display on the cover of each report the following information:

(1) Name and business address of contractor.

(2) Contract Number/Delivery/Task order number.

(3) Contract/Delivery/Task order dollar amount.

(4) Whether the contract was competitively or non-competitively awarded.

(5) Name of sponsoring individual.

(6) Name and address of requiring activity.

5252.247-9508 PROHIBITED PACKING MATERIALS (NAVAIR) (JUN 1998)

The use of asbestos, excelsior, newspaper or shredded paper (all types including waxed paper, computer paper and similar hydroscopic or non-neutral material) is prohibited. In addition, loose fill polystyrene is prohibited for shipboard use.

5252.247-9510 PRESERVATION, PACKAGING, PACKING AND MARKING FOR FOREIGN

MILITARY SALES (FMS) REQUIREMENTS (NAVAIR)(OCT 2005)

(a) Unless specified elsewhere in the contract, packing and packaging shall comply with MIL-STD-129 and other applicable DoD regulations. Packing and packaging materials shall provide protection from abuse during handling and from environmental, magnetic, and electrical damage during handling and subsequent future storage, possibly under less than desirable conditions.

(b) Marking: All unit and exterior containers/packs shall as a minimum be marked as follows:

(1) FMS Case Number.

(2) Part Number (with CAGE Code).

(3) For - the organization/address the material is shipped to.

(4) The applicable MILSTRIP number (identified separately for each line item of the contract/delivery order)

(5) Project Code number.

(6) Project Directive Line Item (PDLI) Number.

(7) Requisition Serial Number (RSN).

(8) Quantity.

(9) From - the contractor’s address shipped from.

(10) Ship to - the shipping address provided in the contract.

(11) Transportation Priority

(12) Required Delivery Date

(c) The contractor shall affix labels to the outside of each external pack warning all handlers that fragile, delicate, etc., equipment is contained within and to warn against particular improper handling and storage procedures/conditions as may be applicable to the item(s) ordered.

5252.247-9514 TECHNICAL DATA PACKING INSTRUCTIONS (NAVAIR) (SEP 1999)

Technical Data and Information shall be packed and packaged for domestic shipment in accordance with best commercial practices. The package or envelope should be clearly marked with any special markings specified in this contract (or delivery/task order), e.g., Contract Number, CLIN, Device No., and document title must be on the outside of the package. Classified reports, data and documentation, if applicable, shall be prepared for shipment in accordance with Defense Industrial Manual for Safeguarding Classified Information, DoD 5220.22M.

Section E - Inspection and Acceptance

CLIN INSPECTION AND ACCEPTANCE TERMS

CLINs 0001, 0002 and 0003 shall include Destination inspection of the supplies and services to be furnished under this contract. Specific inspection and acceptance terms/instructions will be provided in individual orders, if applicable.

CLIN 0004 inspection and acceptance of the data to be furnished hereunder shall be made in accordance with applicable Contract Data Requirements List, DD Form 1423, and clause 5252.246-9512.

Inspection and acceptance will be as stated below or as specified in the individual Orders.

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 Destination Government Destination Government 0002 Destination Government Destination Government 0003 Destination Government Destination Government 0004 Destination Government Destination Government

CLAUSES INCORPORATED BY REFERENCE

52.246-3 Inspection Of Supplies Cost-Reimbursement MAY 2001 52.246-5 Inspection Of Services Cost-Reimbursement APR 1984 52.246-16 Responsibility For Supplies APR 1984 252.246-7000 Material Inspection And Receiving Report MAR 2008

5252.246-9512 INSPECTION AND ACCEPTANCE (NAVAIR) (OCT 2005)

(a) Inspection and acceptance of the supplies or services to be furnished hereunder shall be performed by Government Technical Point of Contact and/or the Contracting Officer’s Representative (COR)..

(b) Acceptance of all Contract Line Items/Sub Line Items (CLINs/SLINs) shall be made by signature of the accepting authority on a DD 250 submitted through the WAWF system. Acceptance will only occur when the accepting authority is sure that inspections performed demonstrate compliance with contract requirements.

5252.246-9514 INSPECTION AND ACCEPTANCE OF TECHNICAL DATA AND INFORMATION

(NAVAIR) (FEB 1995)

Inspection and acceptance of technical data and information will be performed by the Procuring Contracting Officer (PCO) or his duly authorized representative.