14-R-0108_RFP_Amendment_2.docx

N68936-14-R-0108

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been modified:

QUESTIONS AND ANSWERS

Answered in Amendment 1:

Question 1:

When will CDRLs and DD254 be released?

Answer 1:

The CDRLs and DD254 have been provided as attachments along with this amendment.

Question 2:

Is Friday 7 April still the deadline for submission of RFP questions?

Answer 2:

It is requested that all questions be received by April 8th.

Answered in Amendment 2:

Question 3:

On page 5 of the solicitation (5252.211-9503 Level of Effort), it appears the sentence may have been cut off. If so, please provide the missing text.

Answer 3:

The clause has been updated to include the missing text.

Question 4:

Section C, Statement of Work, para. 4.1.1 Contractor Training – "Some technology areas supported by this SOW are continually evolving. The contractor shall attend advanced technology training as required at the task order level."

The first part of the paragraph clearly states that the Contractor is required to provide a properly trained workforce, and we are responsible for the costs of training/certifications, etc. However, the last two sentences imply that there may be additional, unplanned training. There is a cost impact from such additional training that Offerors cannot calculate at this time.

Our interpretation is that if a Task Order requires specific training, the Government will provide it under the TO. Is that correct?

Answer 4:

If a task order requires specific training not otherwise required for the position (such as unique platform training), the training will either be provided to the contractor at no cost or the training cost will be accounted for under the ODC CLIN.

Question 5:

Statement of Work, Section 4.5

“The Contractor shall follow the Software Development Plan (SDP) which it developed and submitted in accordance with CDRL A00D.The SDP shall serve during contract performance as the benchmark for the contractor’s software development effort and shall be periodically evaluated and updated as specified in the CDRL, as a part of continuous process improvement subject to Government review and approval. The SDP will follow the framework of Institute of Electrical & Electronics Engineers (IEEE)/Electronics Industries Association (EIA) IEEE/EIA Std 12207 regarding subject content, level of detail, and completeness” There is no period after the last word of the above paragraph. Has the sentence been truncated?

Answer 5:

A period was added to the final sentence of Section C paragraph 4.5.

Question 6:

Section 5.8 Labor Qualifications (p. 23); FAR 52.222-42 Statement of Equivalent Rates for Federal Hires (May 2014) (p. 58); Section 3.7.2 Labor Hours (p. 94-95)

On page 58, the Equivalent Rates for Federal Hires table lists the General and Operations Manager (Task Order Lead) position as “Junior” level. The Direct Labor table showing BLS mappings on page 23 and the Labor Hours table on pages 94-95 list this position as “Journeyman”.

Will the government please confirm that this position is intended to be proposed at the Journeyman level?

Answer 6:

Please see updated clause.

Question 7:

Section I, Contract Clauses, FAR 52.204-4 Printed or Copied Double-Sided on Postconsumer Fiber Content Paper. This clause is incorporated by reference but no corresponding instructions are provided within the Proposal Format instructions in Section L of the RFP.

Please confirm that this clause does not apply to the production and submittal of this proposal (double-sided printing on recycled paper).

Answer 7:

This clause applies to the production and submittal of this proposal.

Question 8:

Page 85, “All pages should be numbered with section and page numbers.”

Depending on the length of section content, section numbering may not naturally appear on each page. Integrating section numbers into the header/footer or into the page numbering would require each section to start at the top of a page, thereby forcing a break and potentially losing page count to unusable space.

Answer 8:

Section numbers do not need to be repeated if they are continuing on a subsequent page. Whichever section is leading on the top of the page should be the section listed in the header/footer. No page breaks are required between sections.

Question 9:

“Graphs shall be presented in no smaller than a 10 pt. font and should contain a grid, which allows values to be read directly from the graph to the same accuracy that a 10 x 10 to the ½ inch grid provides.”

Certain graphics and tables include information that may not be easily or effectively presented in a grid format. As such, this requirement may restrict the Offerors ability to present information in the clearest and most efficient format.

(a) What specifically is meant by this requirement? Does it apply to all types of graphical illustrations or only to numerical graphs?

(b) Does this requirement apply to tables? If so, please clarify the instructions for providing non-numerical data in this format.

Answer 9:

The purpose of this requirement is to ensure Offerors do not circumvent the page limit restrictions by using graphs to submit information normally submitted in text format. The font restrictions apply to all graphs, graphics, and tables.

Question 10:

“The proposal information instructions are structured by paragraph numbers where first, second, third, and fourth parts correspond to the volume, book, section, and element, etc., in the Offerors proposal.”

Also (same page): “Each volume shall contain the following information: … - Proposal volume/book number”

Are book and volume interchangeable terms (as the second reference would seem to indicate)? If not, could you please clarify what is meant by “book” in the references cited above?

Answer 10:

Section L, paragraph3.0 PROPOSAL CONTENT AND VOLUMES has been revised to remove reference to “book”.

Question 11:

“Written proposals must be formatted using a Times New Roman 12 pt. Normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for standard 8.5 x 11-inch paper.”

(1) Could the Government please confirm that the 1-inch margin excludes headers, footers, and page numbers?

(2) Are headers and footers excluded from the font restrictions?

Answer 11:

1) Correct, the 1-inch margin excludes headers, footers, and page numbers

2) Headers and footers are held to the 12 pt. font size.

Question 12:

“If a discrepancy exists between the original paper copy of the proposal and the disk copy, the paper copy will take precedence.”

Could the Government please confirm that this rule excludes Annex 1 to the Past Performance Volume (which is to be submitted in electronic form only per instructions on pages 85 and 90)?

Answer 12:

Yes, the rule only applies when an electronic and a paper copy are submitted.

Question 13:

Section L, A 3.0 This section states, in part, "Resumes shall be limited to 5 pages per resume and will not be counted toward the Technical volume page limit.”

Because resumes do not count toward the overall 60-page limit for the Technical volume, placing them within the body of the proposal would make it harder for the Government to confirm compliance with the overall page limit.

Would the Government accept placement of the resumes in an Appendix or Annex?

Answer 13:

The RFP has no restrictions on appendices and annexes for resumes.

Question 14:

Section L, A 3.0 This section states, in part, "title and table of contents pages do not count towards the page limit There is no mention of whether an acronym list is required or whether it would count against the page limit. We assume that an acronym list provided as front matter to the Technical volume would not count against the 60-page limit. Is that correct?

Answer 14:

Offerors may choose to provide an acronym list. However, that list will count toward the overall page count of the technical volume. Spelling out an acronym on its first use only is acceptable.

Question 15:

Section L, A 3.0 "1.3 Scenario Response 20 page limit (within the overall 60 page limit It is not clear whether the 20 pages allotted for the Scenario response are segregated from the rest of the Technical response.

Our interpretation is that if our Scenario response is fewer than 20 pages, we could re-allocate the "unused" pages so that the remainder of the Technical volume could be more than 40 pages. Is that correct?

Answer 15:

That is correct.

Question 16:

“The Offerors shall submit a Cross Reference Matrix (CRM) for the Technical Volume. The CRM should be a single integrated matrix and cross-reference the proposal volumes and paragraphs to specific RFP requirements, as well as other parts of the proposal that contain relevant information.”

The CRM is referenced as being “for the Technical Volume” and the example shows only Volume 1 references. However, the same paragraph instructs Offerors that the matrix is to be “a single integrated matrix and cross-reference the proposal volumes and paragraphs.”

(a) Should the CRM include cross-references for all proposal volumes or for the Technical Volume only?

(b) Could the Government please confirm that the CRM is to be submitted within the Technical Volume only (i.e., no copies submitted within Volume 2 and 3)?

Answer 16:

(a) The CRM should address other volumes when applicable.

(b) Correct, Offerors should submit the CRM within the Technical volume only.

Question 17:

Section L, A 3.0 “The Offerors CRM may be identical to the example below or revised such as to add columns…" This statement is unclear regarding whether the Offerors CRM could include *fewer* columns than the example--e.g., omitting the "CLIN Reference" column, since there are only two CLINs for this contract.

Our interpretation is that the CRM in the proposal could omit the "CLIN Reference" column. Is that correct?

Answer 17:

The cross reference matrix should include at a minimum all columns shown in the example matrix.

Question 18:

“Proposal information must be structured such that its Volume/paragraph number matches the Proposal Instructions Volume/paragraph number provided in section “Part B Specific Instructions” to which it is responding, although the Offeror may add lower tier subparagraphs.”

1. The numbering scheme for the subsections does not follow the same pattern (e.g., numbering in the Management Plan would be 1.2.a.1 while numbering for the Sample Scenario would be 1.3.1.a.). Similar differences exist in Volume 3 subsection numbering.

1.2 Management Plan

Offerors shall address the following:

(a) Management:

(1) “The Offeror shall provide an overview of its proposed organization, including an organization chart….”

1.3.1 The offeror’s response to Attachment L-1, Sample Scenario, shall include the following information and outline below:

(a) Team - Identify the Government, military, and contractor team members that need to participate in the effort….

Should Offerors use the letters/number as written or change letters to corresponding numbers (or vice versa)?

Answer 18:

Offerors should use the numbering/lettering scheme as shown in the RFP.

Question 19:

“The Offerors shall complete the Past Performance Information Form, Attachment L-2, for each past performance reference performed within five years of the solicitation release date.” “….. The Offerors shall provide a narrative on each Past Performance Information form in the “Contract Effort Description” area that clearly describes how each contract reference has relevant work effort that matches the relevancy definitions specified in Section M of the solicitation.”

Are Offerors permitted to convert Attachment L-2 into MS Word and reformat it using the proposal font and format requirements provided in the RFP?

Answer 19:

Offerors should use the attachments as provided.

Question 20:

Volume and paragraph numbering includes numbered paragraphs 3.1 Volume Content and 3.2 Ground Rules and Assumptions.

(a) Should Offerors use Volume Content as the title for section 3.1?

(b) Within 3.1, item (c) is informational and does not require direct response within the section. Likewise, section 3.2 (Ground Rules and Assumptions) is informational only and does not request or specify proposal content to be submitted. As these sections are integrated into sequence of the overall numbering scheme for this proposal volume, how should the offeror address this (and other subsequent) paragraphs which are numbered but do not request proposal content?

Answer 20:

a) Yes, Offerors use Volume Content as the title for section 3.1.

b) While not required, Offerors may address or acknowledge paragraphs which are numbered but do not request proposal content.

Question 21:

Section L, B 3.1(a)I, Offerors Summary Table. The last column is labeled "% of Total Proposed Price." Until the contract is awarded, precise figures are not possible.

Would the Government accept ranges in this column?

Answer 21:

No, the offeror must provide the percent of total contract price proposed for the Prime and each JV Team Member or Subcontractor.

Question 22:

Section L, B 3.3(c) states, in part, "All contingent hires shall have a letter of intent submitted under the Cost Volume." Section L, B 3.7.2 states, in part, "The Offeror shall provide a signed letter of intent for each individual proposed as Key Personnel The first statement appears to indicate that LOIs are required for *all* contingent hires, whether Key Personnel or not; the second limits the requirement for LOIs to Key Personnel only. There is an inconsistency.

Our interpretation is that the Government's intent is to require LOIs for Key Personnel *only*, not for all contingent hires. Is that correct?

Answer 22:

Section L, B 3.3(c) has been revised to remove references to contingent hires. Letters of intent are only required for Key Personnel.

Question 23:

After the referenced table, the 3.7.2 Labor Hours text says, “The Offeror shall provide a signed letter of intent for each individual proposed as Key Personnel, including current employees…” A template of that letter is then provided requiring the key person’s hourly wage.

Could you please confirm that completion of this letter is needed only for the Direct Key Person priced in an offeror’ s proposal, and not needed for Indirect Key Personnel because they will not be priced?

Answer 23:

The completion of this letter is required for all Key Personnel (direct and indirect).

Question 24:

Section M, 2.0 "A single contract at ≥ $48M; or, the ability to demonstrate through a single contract or multiple awarded contracts a total annual value of ≥ $16M."

In the table regarding Past Performance relevance, the first two sections (Scope and Complexity) present the information as "Examples." The Magnitude section does not use this terminology. As a result, the impression given is that the $48M/$16M figures are absolute minimum thresholds for Past Performance to be considered relevant in terms of magnitude. Given the scarcity of SB contracts in NAICS 336411 that surpass these thresholds, non-incumbent Offerors will be at a significant disadvantage. Moreover, there is no indication of how the Government would evaluate the relevance of subcontractor Past Performance with regard to magnitude.

a) For consistency with the Scope and Complexity relevance criteria, would the Government clarify that the Magnitude figures listed are Examples only?

b) To facilitate full and fair competition, would the Government lower the thresholds for Magnitude?

c) To facilitate full and fair competition, would the Government add other measures—such as head count as examples of Magnitude measures in the evaluation of Past Performance relevance?

d) Would the Government provide suitable Magnitude examples (e.g., relative to proposed LOE) for evaluation of subcontractor Past Performance?

Answer 24:

Section M-(1) PART B SPECIFIC INFORMATION, 2.0 PAST PERFORMANCE table, Magnitude was revised.

Question 25:

The instructions tab in Attachment L-4 requests ODCs be divided between travel and materials. On page 94 of the RFP, the government gives a total plug number for all ODCs.

Because many Offerors apply different burdens to travel than materials, would the government please consider dividing the total ODC plug number and supplying a plug number for each type?

Answer 25:

SECTION L 3.0 VOLUME 3: PRICE/COST PROPOSAL, 3.7 Government Furnished Information

3.7.1 ODC table was updated with the breakout between ODC material and ODC travel. The total ODC value has been updated due to clerical error.

Question 26:

Most of the labor categories have hours that are not divided evenly by 1,920 annual productive hours (ref. 3.7.2, page 94) so there will be “extra” hours for most of the labor categories. The base period and option periods contain different numbers of hours, making it more difficult to determine the number of part time and full time FTEs per labor category.

How would the government like us to determine FT vs PT in the spreadsheet?

Answer 26:

For proposal purposes, estimate all hours as full time equivalents.

Question 27:

Would the government please revise the Summary tab in the Attachment L-4 to reflect there only being 3 CLINs, instead of 4 CLINs?

Answer 27:

Attachment L-4 has been revised.

Question 28:

Annual Fully Burdened Labor Attachment (Instructions tab) "For each individual Contractor employee proposed, the contractor shall enter the corresponding Position Number as found on Attachment L-4." There is no column on Attachment L-4 labeled "Position Number."

Will the Government either provide a revised version of Attachment L-4 with a "Position Number" column, or remove this element from Attachment L-5?

Answer 28:

Attachment L-5 has been revised to only require disclosure of any individual personnel whose annual fully burdened labor rate proposed is over $300,000. In accordance with this change, SECTION L 3.0 VOLUME 3: PRICE/COST PROPOSAL, 3.3 Price/Cost Information has been updated.

Question 29:

Under the Prime Contractor Direct Labor section of attachment L-4, there are lines for Employee Name. The implication is that this spreadsheet must include the names of specific personnel. Only the incumbent would be able to provide this information; non-incumbent Offerors would be bidding rates by labor categories, not individual-by-individual.

To facilitate full and fair competition, would the Government provide a revised version of Attachment L-4 that does not require the names of specific individuals?

Answer 29:

Please see updated attachment.

Special note:

SECTION L PART B 2.0 VOLUME 2: PAST PERFORMANCE, 2.1 General was updated to: “…In the event a CPAR does not exist for a past performance reference, the Offeror shall request a Contractor Performance Assessment Questionnaire (CPAQ), Attachment L-3, from the Program Manager who is the Assessing Official or a representative of the Government agency.”

SECTION B - SUPPLIES OR SERVICES AND PRICES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

STATEMENT OF WORK

Section C - Descriptions and Specifications

STATEMENT OF WORK (SOW)

FOR

WEAPONS AND SYSTEMS INTEGRATION SUPPORT SERVICES (WSISS) IV

22 February 2017

CLIN 0001 -- Labor CLIN for Weapons and Systems Integration Support Services CLIN 0002 – Other Direct Costs CLIN 0003 – Not Separately Priced CLIN in support of the Contract Data Requirements List

1.0 SCOPE

1.1 Background

The Naval Air Warfare Center Weapons Division (NAWCWD) is the weapons systems integration and software support activity for several aircraft Integrated Product Teams (IPTs). IPTs and Program Support Offices currently operating at the NAWCWD include the F/A18 & EA-18G, AV8B, AH1, F-35, and Unmanned Systems. In addition to the aircraft named above, the contract may support any other aircraft that may be assigned to the NAWCWD in the future, any system carried by or supporting aircraft IPTs assigned to the NAWCWD, and interoperability initiatives involving supported aircraft. The mission of each IPT and Program Support Office is to provide research, development, test, evaluation, systems integration, and programmatic support for weapons systems and associated tactical computer systems embedded within or carried on their aircraft, including related systems, support equipment, and interoperability initiatives. The efforts of NAWCWD’s Aircraft IPTs and Weapons Program Support Offices are integral to the Navy’s ability to achieve Integrated & Interoperable (I&I) Warfighting Capabilities (platforms, sensors and weapons operating seamlessly in a Systems of Systems (SoS) environment) that produce an immediate and sustainable increase in warfighting effectiveness and battlespace dominance.

The term "aircraft weapon system,” in the context of this Statement of Work (SOW), is defined as weapons/trainers/sensors and targeting/mission computer/avionics systems and software, including electronic warfare (EW) systems, integrated into NAWCWD IPT supported aircraft, as well as associated pre and postflight support systems, and/or support equipment hardware and software for any of the above.

1.2 General Scope of Work

The contractor shall provide the following services: Modification of aircraft components, technical support services (including full systems integration) to all NAWCWD aircraft IPTs and their associated aircraft weapons and support systems (including foreign military sales (FMS) versions of each aircraft or system), and technical support services (including full systems integration) to other related and/or interfacing systems (including related test laboratories and equipment). The scope of the contract includes performing related technical functions necessary to satisfactorily complete primary tasking, such as:

1.3 Contract Work Environment

The majority of the contractor’s work force shall be physically located in Government-provided work spaces at China Lake, CA; Point Mugu, CA; Yuma, AZ, Cherry point, NC; and Eglin AFB, FL where contractor tasking is to be performed. Total Government workspaces to be provided are estimated to be 330. Contractor personnel shall adhere to existing IPT work processes referenced within each task order. The Contractor is expected to propose improvements to work processes that result in cost or time savings to the Government. The contractor’s consistent and skillful application of these work processes is critical to the NAWCWD process improvement initiative described in Sections 4.1.2 and 4.5.

2.0 APPLICABLE DOCUMENTS

Standard requirements documents (Government and Industry Specifications and Standards), reference texts, specific design requirements, and other references will be defined by individual Task Orders. The Government will apply commercial specifications and standards to the greatest extent reasonably possible. The Government will provide all necessary reference documents not generally available to the contractor. The following list of general requirements documents and reference texts is a sampling of those that have been imposed by Task Orders in the past. 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. The list is provided here for contractor reference only.

2.1 Government Specifications, Standards, Handbooks, and Publications

Interface with Avionics Systems

Program

2.1.9 NAVAIRINST 8012 Non-Nuclear Ordnance Non-Combat Expenditure Requirements/Allocations

Installed Systems

2.1.15 OPNAV 43P6 Metrology Automated System for Uniform Recall and Reporting (MEASURE) User’s Manual

Vehicles

2.2 System Software / Application Compliance

All Information Technology Systems or software/application development, modification or support shall be performed in accordance with Defense Business Transformation guidance (formerly Business Management Modernization Program (BMMP)), Department of the Navy (DON)/Naval Air Systems Command (NAVAIR) Functional Area Manager (FAM) Policies and Guidance, Network and Server Registration, and Web Enablement mandates.

2.3 Web Sites, Web Enablement and Application / System Development, Modification, and Maintenance Support Services:

All Information Technology systems, software, and website development, modification or support shall be performed in accordance with all applicable Federal, DoD, DON, and NAVAIR policy, guidance, standards, and strategies, and should be integrated within the NAVAIR Enterprise portal and collaboration environment whenever possible. Any Web sites/servers hosted/located in contractor facilities, or outside NAVAIR enclave, will transition to NAVAIR architecture and infrastructure in accordance with Legacy Shutdown guidance. Policies include, but are not limited to:

a. Office of Management and Budget Management of Federal Information Resources, OMB CIRCULAR NO. A-130 Revised. http://www.whitehouse.gov/omb/circulars_a130_a130trans4

b. OMB Policies for Federal Agency Public Websites, OMB M-05-04. http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2005/m05-04.pdf

c. Section 508 Amendments to the Rehabilitation Act of 1973. https://www.section508.gov/Section-508-Of-The-Rehabilitation-Act

d. Department of Defense Web Policies and Guidelines. http://www.defense.gov/webmasters

e. Navy Information Operations Command (NIOC) Norfolk Web Risk Assessment Team Website. http://www.public.navy.mil/fcc-c10f/niocnorfolk/Pages/AboutWRA.aspx

f. DON Policy for Content of Publicly Accessible World Wide Web Sites SECNAVINST 5720.47B. http://www.navy.mil/navydata/internet/secnav5720-47b.pdf

g. NAVAIR CIO Website (NAVAIR specific policy and guidelines). To request this policy contact the NAVAIR CIO office – 7.2.2 Applications Integration team – Web Manager: Shane Malamphy at 301- 342-1825.

h. Defense Information Systems Agency (DISA) Hosting of All Navy Websites (NAVADMIN 061/08). http://www.public.navy.mil/bupers-npc/reference/messages/Documents/NAVADMINS/NAV2008/NAV08061.txt

i. Consolidation of Navy Web Sites - Reduction of IM/IT Footprint NAVADMIN 145/07. http://www.public.navy.mil/bupers-npc/reference/messages/Documents/NAVADMINS/NAV2007/NAV07145.txt

j. DON Web Presence Policy: The Registration, Compliance of, and Investment in, All Unclassified Web Sites and Uniform Resource Locators. http://www.doncio.navy.mil/ContentView.aspx?ID=577

k. Policy and Procedures for Web Risk Assessment (WRA) of Publicly Accessible Navy Sites (ALCOM 129/09). http://www.public.navy.mil/fcc-c10f/niocnorfolk/Documents/NTD-08-09.txt

2.4 Cybersecurity:

The contractor shall conduct investigation and analysis of acquisition program artifacts such as but not limited to Initial Capabilities Document (ICD), Capability Description Document (CDD), Capability Production Document (CPD), Navy urgent operational need (UON) and Marine Corps urgent universal need statement (UUNS), joint urgent operational needs (JUONs), threat assessments and acquisition strategies (AS). Knowledge gained from this analysis shall be used when developing the Cyber Security Strategy (CSS) needed to steer and inform the program’s development of a Security Plan (SP) in accordance with DoDI 8510.01, of 12 March 2014.

As a minimum, hardware, firmware, software, documentation (data deliverables) and/or Information Technology (IT) services delivered by this contract shall be in compliance with the following References:

a. DoDI 8500.01 Cyber Security, 14 March 2014

b. DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), 12 March 2014, incorporating Change 1, May 24, 2016.

c. Committee on National Security Systems Instruction 1253, “Security Categorization and Control Selection for National Security Systems,” March 27, 2014, as amended.

d. DoDD 8140.01, Cyberspace Workforce Management, 11 August 2015.

e. DoD 8570.01-M Information Assurance Workforce Improvement Program, 15 August 2004, Certified Current as of 10 November 2015.

The contractor shall conduct investigation and perform analysis including; criticality analysis, threat assessment and vulnerability assessments. All findings and recommendations shall be reported to the government in technical reviews and submitted as written reports or documents as listed in Contract Data Requirements Lists. The contractor shall support government efforts needed for Information systems (IS) (enclaves or major applications), Platform Information Technology (PIT) or PIT systems to successfully categorize the system, achieve favorable assessment for selection, implementation and testing of security controls and authorization (approval to operate) before use or interconnection in an operating environment in accordance with references (a), (b) and (c). This includes IT that is standalone and IT that is connected to other systems, networks or enclaves. Information systems (IS) (enclaves or major applications), Platform Information Technology (PIT) or PIT systems delivered prior to award of this contract but included in the performance of this contract may have been delivered in compliance with Department of Defense Information Assurance Certification and Accreditation Process (DIACAP) and as such shall require transition to Risk Management Framework Cyber Security compliance. Transition planning proposed or performed under this contract shall be in compliance with reference (b) Enclosure 8, Figure 2 and all hardware, firmware and software deliverables shall be capable of receiving Authorization to Operate in accordance with reference (b).

Information technology services shall only be performed by personnel who are qualified and certified in accordance with reference (d) Cyberspace Workforce management above. Personnel proposed and/or used in the performance of this contract as certified personnel shall be limited to those whose specifically assigned duties and responsibilities require certification.

All Cybersecurity shall be in compliance with the following listed instructions:

aa. SECNAVINST 5239.3C, Department of the Navy Cybersecurity Policy, 2 May 2016.

bb. SECNAVINST 5239.19, Department of the Navy Computer Network Incident Response and Reporting Requirements, 18 March 2008.

cc. The National Security Act of 1947.

dd. Title 40/Clinger-Cohen Act.

ee. Title 44/ Federal Information Security Management Act.

ff. National Institute of Standards and Technology Special Publication 800-53, Security and Privacy Controls for Federal Information Systems and Organizations, Revision 4, April 2013 (Updated 22 Jan 2015).

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

Architecture Compliance. The contractor shall ensure all IT solutions, including database solutions, comply with the appropriate NAE Enterprise Architecture, and are verified by the NAVAIR Enterprise Architect (AIR-7.2.3) prior to build out.

Disclosure of pre-existing networks, circuits or connections. Any and all networks, circuits or connections between the contractor and any NAVAIR site related to previous contracts shall be identified in the MOA. Failure to comply and subsequent discovery of an unregistered network, circuit or connection shall be grounds for immediate disconnection.

2.6 Software Process Improvement Initiative (SPII):

The Contractor shall follow the Software Development Plan (SDP) that they develop and submit in accordance with CDRL A00D. The SDP will follow the framework of Institute of Electrical & Electronics Engineers (IEEE)/Electronics Industries Association (EIA) IEEE/EIA Std 12207 regarding subject content, level of detail, and completeness. The SDP shall serve during contract performance as the benchmark for the contractor’s software development effort and shall be periodically evaluated and updated as specified in the CDRL, as a part of continuous process improvement subject to Government review and approval.

3.0 REQUIREMENTS

3.1 Technical Performance Requirements

Individual Task Orders will specify specific products and services to be delivered. The sections below provide additional definition of the range and types of tasking that the contractor may receive via Task Orders. Each Task Order will include a Statement of Work (SOW), related DD Form 1423, and Contract Data Requirements List (CDRL) for data deliverables. The CDRLs will define the required format, delivery requirements, periodicity, and other requirements for all data deliverables. Task order requirements may require contractor non-local travel (both domestic and foreign, including aboard Government ships-at-sea, aboard Government aircraft). The contractor will not be asked to perform as both the requirements developer and acceptance tester for any product.

3.1.1 Systems Integration

The contractor shall perform system integration relative to NAWCWD aircraft IPT supported platforms as well as how these platforms, systems, and subsystems function as components within Systems of Systems to achieve Integrated Warfighting Capabilities (IWC). Systems to be integrated include but are not limited to; weapons, avionics, sensors, targeting systems, system hardware and software. Work activities deemed primary and ancillary to successful systems integration are further identified in SOW paragraphs 3.1.1.1 through 3.1.1.13 below and generally consist of but are not limited to system analysis, research, development, engineering, testing, test equipment design, fabrication, maintenance, mission simulation, and interoperability assurance.

3.1.1.1 The contractor shall perform research and development and shall provide systems engineering for aircraft and weapons systems. The contractor shall also provide systems analysis consisting of analytical studies of supported systems and analysis of FMS releasability. Additionally, the contractor shall perform system software design and development (D&D) and verification and validation (V&V) testing for supported systems. (CDRL A00F)

3.1.1.2 The contractor shall research, analyze, perform engineering investigations, and document new and/or modified weapons, sensors, targeting systems, aircraft computers, avionics systems, databus architectures, trainers, and related software and systems (including EW systems) being considered for integration into the NAWCWD supported aircraft (or related systems), as well as associated pre- and post-flight support systems, simulators, and/or other test and support equipment hardware and software for any of the above. (CDRL A00F)

3.1.1.3 The contractor shall provide tradeoff studies, analyses, engineering and anomaly investigations and recommendations involving supported aircraft and/or systems. (A00F)

3.1.1.4 The contractor shall research, analyze, and document operational concepts for system and subsystem performance. (CDRL A00F)

3.1.1.5 The contractor shall conduct studies and analyses to support system and subsystem definition requirements, human factors and pilot-vehicle interface considerations. (CDRL A00F)

3.1.1.6 The contractor shall provide weapons delivery and/or kill/effects chain performance analyses and fire control algorithm design, modification, and/or implementation. (CDRL A00G)

3.1.1.7 The contractor shall perform and/or support system, mission, and operational simulations; including documentation, studies, analysis, and recommendations regarding simulations. (CDRL A00F)

3.1.1.8 The contractor shall perform system performance analyses, including, but not limited to, malfunction monitoring, fault location and isolation, loading, optimization, compensation methodologies, reconfiguration, and associated tasks for software and hardware. Software performance analysis shall include the determination of optimum utilization of both hardware and software system assets. (CDRL A00F)

3.1.1.9 The contractor shall provide analysis and reporting of data derived from various levels and stages of testing. As part of this effort, the contractor shall perform research and analysis of advanced tools and methods for data reduction and analysis. The contractor shall design and develop test related tools, methodologies, and test hardware (including building and maintaining of test hardware). (CDRL A00F)

3.1.1.10 The contractor shall perform system D&D and V&V testing for supported systems. The contractor shall conduct laboratory, simulation, and ground testing, provide flight test support (including test planning, safety of flight testing, and regression testing), test design, test procedure development, test preparation, test conduct and monitoring, and post-test data collection, analysis, and reporting) to evaluate system and subsystem operation. The contractor shall perform D&D and V&V review and testing to include the following sampling of typical requirements: (CDRLs A00H and A00J)