N00421-16-R-0089-0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

See Section A - Amendment 0001

1. CONTRACT ID CODE PAGE OF PAGES

S 1 48

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

16C. DATE SIGNED

BY 24-May-2017

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N00421-16-R-0089

X 9B. DATED (SEE ITEM 11)

05-May-2017

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

24-May-2017

CODE

NAVAL AIR WARFARE CENTER AD (PAX)

CODE 2.5.1.5

22473 MILLSTONE ROAD

BLDG 505

PATUXENT RIVER MD 20670

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N00421-16-R-0089

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 05-Jun-2017 01:00 PM to 16-Jun-2017 01:00 PM.

The following have been modified:

POINTS OF CONTACT

AMENDMENT 0001

This purpose of this amendment is to make revisions to the solicitation as outlined below. All questions received by industry have been addressed.

SF33

- Block 9 - The closing date and time is changed to 16 June 1:00 p.m. EST.

Section C

- Paragraph 3.1 is revised to remove the last sentence in the first paragraph with reference to the contractor facility location.

- Paragraph 4.4 is revised to delete the last sentence “The NAVAIR NMCI Clause, 5252.237-9503, will be added by 2.0 to Section H of the solicitation and contract.”

- Paragraph 4.5.1 is revised to read “Capabilities Development Document (CDD).”

- Paragraph 7.1 is revised to add “…NMCI computer as necessary…”

- Paragraph 11.7 is revised to change the BLS SOC from 15-1252 to BLS SOC 15-1130 for the Software

Engineer, Journey labor category.

- Paragraph 11.8 is revised to change the BLS SOC from 15-1253 to BLS SOC 15-1121 for the Systems

Specialist, Senior labor category.

- Paragraph 11.9 is revised to read “At least ten (10) years of recent and relevant experience in an engineering or operations analysis position…” for the Operations Research Analyst, Senior labor category.

- Paragraph 11.10 is revised to read “At least three (3) years of recent and relevant experience in an engineering or operations analysis position…” for the Operations Research Analyst, Journey Level labor category.

- Paragraph 11.11 is revised to add BLS SOC 13-1151 to the Engineering Training Specialist labor category.

- Paragraph 11.14 and 11.15 are revised to change the BLS SOC from 13-1111 to BLS SOC 11-3021 for the

Systems Analyst, Senior and the Systems Analyst Journey labor categories.

Section L

- Part A, paragraph 2.0 is revised to read “…Foldout pages shall only be utilized for drawings, charts, tables, graphs, and spreadsheets. When foldout pages are used they must not exceed 11 x 17 inches and will be counted as 1 page. Drawings may be provided separately and may be any size but should be folded to approximately 8.5 x 11 inch standard size and will count as 1 page. Graphs, charts, tables, and spreadsheets shall be presented in no smaller than a 10 pt font. 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. Graphic resolution, including such data as tables or charts, should be consistent with the purpose of the data presented.

There is no page limit for foldout pages.”

- Part A, paragraph 3.0, section 2.0 of the table is revised to include the language “not including Attachment P4 and P5” and is revised to include an Annex 1.

- Part B, paragraph 1.1.3 is revised to read “Offerors shall present…”

- Part B, paragraph 1.1.4 is revised to show the anticipated transition period is approximately 90 days.

- Part B, paragraph 1.3.2.1 is revised to include the following: “NOTE: During performance, the contractor shall be compliant with the terms of NAVAIR Clause 5252.237-9501 Addition or Substitution of Key Personnel.”

- Part B, paragraph 1.3.2.2 will be revised to change the reference to “Volume 4” to “Volume 3”.

- Part B, the third paragraph under 2.1 is revised to add: “Additionally, the Offeror shall state whether the work under the Past Performance was provided as a Prime, Subcontractor, or Team Member. Due to the printing limitations in the Attachment P4 form, the Offeror may utilize Annex 1 under Volume 2 to include an exact copy of the full text from the “Contract Effort Description” block of Attachment P4.”

- Part B, the second paragraph under 3.3 is revised to change the reference from Attachment 6 to Attachment P8.

- Part B, paragraph 3.3(c) is changed to read “…For contingent hires, the Offeror shall provide letters of intent outlining salary information for contingent hire employees…”

Section M

- Section M, Part B, paragraph 5.0 is renumbered as 4.0.

Attachments

- Attachment P6 is revised to represent contract Year I and is replaced in its entirety.

Note – In accordance with Section L, Part A, paragraph 1.0 additional questions may not be accepted.

All other terms and conditions remain unchanged.

CONTRACT SPECIALIST: Jeffrey Smith

TELEPHONE NUMBER: 301-757-1996

EMAIL ADDRESS: jeffrey.t.smith6@navy.mil

CONTRACTING OFFICER: Melinda Stann

TELEPHONE NUMBER: 301-757-0008

EMAIL ADDRESS: melinda.stann@navy.mil

CONTRACTING OFFICER REPRESENTATIVE:

TO BE DETERMINED AT CONTRACT AWARD

SUMMARY

mailto:jeffrey.t.smith6@navy.mil mailto:melinda.stann@navy

(1) This acquisition is a Small Business Set-Aside that will result in the placement of a Single Award Indefinite

Delivery/Indefinite Quantity (IDIQ) contract. This IDIQ contract vehicle will permit specific term task orders to be issued, based on the general tasking outlined in the Statement of Work (SOW).

(2) NAVAIR clause 5252.211-9503 LEVEL OF EFFORT (COST REIMBURSEMENT)(NAVAIR)(DEC 2012) will be included in all LOE Task Orders.

(3) The NAICS for this procurement is 541330.

(4) The Product Service Code (PSC) for this procurement is R425.

(5) The resulting Single Award IDIQ contract will have an ordering period of five (5) years.

(6) This contract will have cost-plus-fixed-fee (CPFF) and cost reimbursement (non-fee bearing) line items.

(7) Task Orders issued from this contract award will reflect CLINs by funding type.

(8) The Government aniticipates issuing twelve (12) Task Orders at the time of award.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

SECTION C DESCRIPTION

Item 0001-0006 – The contractor shall provide SERVICES in accordance with the SOW. Contract services shall be performed in accordance with the SOW as detailed in individual task orders. The task order SOW will detail which tasks within the scope of the basic contract will be performed.

Item 0007-0012 – The contractor shall provide TRAVEL & MATERIAL as follows: TRAVEL shall be provided in accordance the SOW and NAVAIR Clause 5252.232-9509. MATERIAL shall be provided in accordance with the

SOW and H Clause 5252.242-9515 “Restriction on The Direct Charging of Material”.

Item 0013 – The DATA reports to be furnished hereunder shall be in accordance with Exhibit A, DD Form 1423, Contract Data Requirements Lists (CDRLs), CDRLs A001-A00B, and the SOW as required by the individual Task

Order.

STATEMENT OF WORK

SUSTAINMENT ENGINEERING, TRAINING AND TOOLS SERVICES

1.0 INTRODUCTION

The Naval Air Warfare Center Aircraft Division (NAWCAD) Code AIR-4.1 is tasked to perform systems sustainment engineering, analysis, development, integration, testing and fleet introduction and support of warfare systems into Naval Aircraft. This includes direct systems engineering support throughout the full life cycle of a weapon system from concept development to disposal and is applied to all Naval Aircraft (Tactical, Vertical Lift, Maritime, UAV's, Targets and advanced weapons), Foreign Military Sales (FMS) and support systems.

Aircraft Programs supported under this solicitation will include, but not be limited to, programs such as the Joint

Strike Fighter (JSF), F/A-18, EA-6, AV-8, V-22, Navy Commercial Derivative Aircraft, Tactical Reconnaissance

Unmanned Air Systems (UAS), Aerial Targets Systems, E-2, C-130, KC-130, P-3, P-8, H-1, H-60, H-53, Scan

Eagle UAS, Fire Scout UAS, Triton UAS, Shadow UAS, Joint Tactical Combat Training Systems, Night Vision

Devices, Integral Cockpit Lighting, Mission Planning, Advanced Avionics Technology Demonstration, Common

Avionics, Electronic Warfare (EW) Systems, Communication, Navigation, Advanced Tactical Surveillance, Integrated Tactical Decision Aids, Undergraduate Flight Training Systems, Weapon Engagement Rehearsal Aids

(E&RA), Theater Ballistic Missile Defense and Aircraft/Weapon Integration, Joint Precision Approach Landing

System (JPALS), Electro-Magnetic Aircraft Launch Systems (EMALS) and other Externally Directed Programs.

NAWCAD also supports Joint Service Programs in addition to JSF, such as LH-X, Advanced Tactical Airborne

Reconnaissance System and Operations Aircraft.

2.0 SCOPE

The Systems Engineering Department (AIR-4.1) requires systems sustainment engineering and technical efforts to be performed under this contract in the functional area of Systems Engineering Management (AIR-4.1, AIR-4.1.1 and the Systems Engineering Development and Implementation Center (SEDIC)). These efforts are focused across a broad business base comprised of Integrated Program Teams (IPT's), Externally Directed Teams (EDT's) and

Enterprise Teams (ET's), which support all Naval Air Programs.

The mission of AIR-4.1 is to apply systems sustainment engineering knowledge and skills to provide support to

Program Executive Offices (PEOs) and Program Manager, Air (PMAs) by providing assessments of Aircraft, Weapon and Integrated Systems’ technical performance, mission suitability and associated acquisition risks throughout the full acquisition process and life cycle of a program.

3.0 REQUIREMENTS

This Statement of Work (SOW) defines the overarching scope for AIR-4.1 Systems Engineering efforts. Each Task

Order (TO) awarded under this contract will include a unique SOW with the detailed requirements that fit within the scope of the basic contract.

The following matrix outlines per SOW paragraph the anticipated CLINs to be established on contract for these efforts.

Paragraph Number

CLIN

CLIN

CLIN

CLIN

CLIN

3.1: Contract Project Management X X X X X

3.2.1: Technical Reviews X X X X X

3.2.2: Requirements Management X X X X X

3.2.3: Risk Management X X X X X

3.2.4: SEDIC X X X

3.2.5: Systems Engineering Policies, Processes, Training and

Education

X X X

3.2.6: Sustainment Engineering X X X X X

3.2.7: Information Technology

X X

3.2.8: Administrative Support of Technical Staff

X X

3.2.9: Progress, Status and Management Report X X X X X

3.2.10: Routine Status Reviews X X X X X

The requirements under this SOW cover a broad spectrum of support to Naval Air Systems Command (NAVAIR)

PEO and PMA activities. The Contractor shall provide support for integrated, capability-based warfighting assessments that will ultimately provide the analytic underpinning to support the acquisition of naval aviation systems and the Office of the Secretary of Defense (OSD) investment decisions.

Information security classifications ranging from unclassified up to and including TOP SECRET shall be supported and appropriately protected.

All Contractor personnel under this SOW shall maintain an up to date Common Access Card (CAC) to ensure access to the Naval Systems Engineering Resource Center (NSERC) and Navy Marine Corps Intranet (NMCI) services.

3.1 CONTRACT PROJECT MANAGEMENT

The Program Manager shall be the primary point of contact within the company for the contract. The Program

Manager is cognizant of the contract and aspects of the contract implementation within the prime Contractors’ organization. This role is not intended to circumvent company policy and when prime contract administrator to

PCO / contract administer communication is required this does not seek to alter that. However, the Program

Manager shall be cognizant, conversant and up-to-date in the details of the contract. The Program Manager shall be the Governments source for financial and technical progress data and status. The Program Manager shall call upon other departments within the company for data and status and will maintain and report this data to the Government.

The Program Manager shall provide monitoring, tracking and reporting progress required by the monthly status reports for technical and financial progress. In addition, processes for the annual transition of Task Order years shall be established along with processes for adding, executing and removing tasks from the contract. A new process, when identified shall be established, executed and improved as required. The Program Manager shall provide reporting documents as specified by Contract Data Requirements List (CDRL). (CDRL A005)

The Program Manager shall present a robust project management process which tracks obligations and expenditures by customer, funding type, fiscal year, SOW paragraph, subcontractor and person. (CDRL A001)

3.2 SYSTEMS SUSTAINMENT ENGINEERING

The Contractor shall provide systems sustainment engineering functions to support the requirements of various projects in support of NAVAIR Activities. The systems engineering functions include performance of the system analysis, functional allocations, synthesis and evaluation efforts necessary to transform an operational need into an effective and affordable operational system throughout the system life cycle. Included is the overall integration of all requirements in a manner that optimizes total system performance, quality, cost-effectiveness and supportability.

The Contractor shall prepare and deliver Scientific and Technical Reports (CDRL A002) as needed. In support of the AIR-4.1 Division Head, the Contractor, using provided data, shall be required to perform the following systems sustainment engineering functions:

3.2.1 Technical Reviews. The Contractor shall use the NAVAIR technical review process to outline the process and assign responsibilities for the planning and conduct of Systems Engineering Technical Reviews (SETRs) of

NAVAIR programs in accordance with NAVAIRINST 4355.19 (NAVAIR Instruction – SETR Process). The

Contractor shall research, analyze, collect and develop presentations to support the technical review process for the air platforms, weapon systems and related subsystems they will be supporting. (CDRL A004)

3.2.2 Requirements Management. Requirements Management includes requirements at the Operational

Requirements Document (ORD) / Capabilities Development Document (CDD) / Key Performance Parameter (KPP) level. It also includes the performance or contracted specification, functional baseline requirements, allocated baseline requirements, preliminary product baseline requirements and the product baseline requirements. Software requirement specifications and software and hardware interface documents are also included. Change management processes are included in requirements management to include specification change notices and deviations. The

Contractor shall support the requirements management process by researching, analyzing, collecting and developing presentations in support the development of the technical requirements for the air platforms, weapon systems and related subsystems they will be supporting. (CDRL A004)

3.2.3 Risk Management Support. The Contractor shall support the risk management process in accordance with NAVAIRINST 5000.21B (Naval SYSCOM Risk Management Policy) and the latest applicable PEO guidance memo, that will be implemented to support issue, risk and opportunity identification; documentation in terms of root causes, current effects for issues and future affects for risks and opportunities; and analysis including likelihood (for risks and opportunities), severity of impact, prioritization according to urgency and required visibility (tier level) through researching, analyzing, collecting and developing presentations to support the risk management process for the applicable air platforms, weapons systems and subsystems they are assigned to support. The process will support the development and execution of issue handling plans via analysis of alternative solutions and cost effective strategies to successfully reduce the impact of an existing problem. The process will include the periodic review of risks, issues and opportunities as directed by the Government to improve the ability to make optimal technical, schedule and cost trade-off decisions.

3.2.4 Systems Engineering Development and Implementation Center (SEDIC). The SEDIC is a major part of the revitalization of Systems Engineering that researches, develops, maintains and practices systems engineering policy and processes for the NAVAIR. The SEDIC is in the process of developing framework, methodologies, practices and training material for NAVAIR to transition to a Model Based Systems Engineering organization. This function requires interactions across competencies within NAVAIR and potentially across all Navy commands and at the DoD level. The systems engineering processes, procedures, methods and tools are relevant across the entire life cycle of a program from the Material Solution Analysis phase through the development and production phases as well as the Operations and Support and Sustainment Phases until disposal. The Contractor shall:

1) Study, analyze and develop systems engineering policies and practices that apply for all Navy programs across the entire life cycle of the program, based on current processes and practices during the transition, in support of the following: (CDRL A004)

a) Provide systems engineering expertise to enhance systems engineering processes to meet the needs of emerging programs and the needs of existing programs.

b) Develop and document processes and methods to improve system development efficiency.

c) Maintain, modify and enhance the systems engineering policy documents, processes, procedures, methods, systems engineering web site and system engineering tools (e.g., SETR Manager).

2) Provide teams, that when deployed to programs, are capable of assisting with, conducting, maintaining and communicating all the systems engineering processes and tools to accelerate program execution. The teams will be constructed based on the program and the life cycle phase the program is currently executing.

3) Analyze developments in Model Based System Engineering. Provide systems engineering analysis to ensure systems engineering processes, methods and tools can transition to the Model Centric Engineering methodology per the Systems Engineering Transformation. (CDRL A004)

4) Maintain, enhance and expand the functionality of the Integrated Systems Engineering Environment.

3.2.5 Systems Engineering Policies, Processes, Training and Education. The Contractor shall interface across

NAVAIR competencies, programs and sites; with other Navy Systems Commands, Navy Post Graduate School, Navy secretariat and OPNAV organizations; and with other military Services and OSD staff to review, analyze, comment and develop recommended changes to NAVAIR, DoN and DoD policies, procedures, practices and guidance related to Systems Engineering. The Contractor shall support NAVAIR PMAs and IPTs/EDTs in understanding and implementing core systems engineering policies, processes, training, education and guidance.

The Contractor shall develop, review and deliver training plans related to systems engineering. Examples of such plans include, but are not limited to: techniques and tools for identifying and ensuring traceability of system requirements; developing architectures; managing system requirements data; preparing systems engineering plans and system design specifications; managing program risks, engineering change control and configuration management; conducting Systems Engineering Technical Reviews and similar core systems engineering processes.

The Contractor shall develop, review and deliver applicable training and educational materials and courses.

Training material shall not be identified as company proprietary. The Contractor shall provide instructors and/or facilitators for the training courses and conduct training for government civilian personnel at NAVAIR activity sites such as, but not limited to, NAS PAX; NAVAIR Lakehurst, Lakehurst, NJ; Naval Air Weapons Station (NAWS)

China Lake, Ridgecrest, CA; NAS Point Mugu, Oxnard, CA; Marine Corps Air Station (MCAS) Cherry Point, Cherry Point, NC; NAS Jacksonville, Jacksonville, FL; and NAS North Island, San Diego, CA.

3.2.6 Sustainment Engineering. The Contractor shall provide systems engineering support in response to a continuing increase in the average age of legacy aircraft and systems, increasing operating and support (O&S) costs and a reduction in acquisition of new / replacement aircraft.

The Contractor shall review available data to evaluate specific or common obsolescence related issues as identified using data from such sources as reliability, failure, supply, usage and operational reports and data bases. Reports shall be delivered along with appropriate recommendations on mitigation solutions including, but not be limited to, alternative sources, lifetime buy, redesign, reverse engineer, reclamation or substitution. (CDRL A004)

The Contractor shall conduct a review to determine diminished sources of supply, missing or inadequate data and/or high replacement cost. The Contractor shall provide alternatives in the form of reports, studies, analysis of alternatives, business case analysis, POA&M for readiness degraders to legacy aircraft, parts, sub-systems and systems impacted. (CDRLs A002 and A004)

The Contractor shall conduct assessments of available solutions from government and industry sources to support engineering, testing, production and retrofit incorporation of items, subsystems and systems for legacy aircraft where readiness and/or safety is affected.

The Contractor shall develop and maintain a list of readiness degraders across the Naval Aviation inventory. This list shall include any new degraders identified and a record of all identified degraders that have been mitigated along with the solution.

The Contractor shall maintain a database of system deficiencies and the priority of each deficiency. As funding comes available for the correction of deficiencies the Contractor shall monitor progress and update the status of each deficiency being corrected.

The Contractor shall support the assessment of commercial obsolescence tools consisting of, but not be limited to, links to manufacturing sources, automated assessment tools and prediction models in support of Naval Aviation

Sustainment Engineering.

The Contractor shall support Engineering Investigations (EIs), which includes on-site support, by performing engineering analysis, testing, data review and report writing. EIs will be conducted for the applicable air platforms, weapons systems and subsystems they are supporting to determine cause and effect of any malfunction, failure, lifecycle limitations and any other technical issue that requires analysis. The Contractor shall support the analysis of the EIs to support potential corrective, preventive and technical actions for the applicable air platforms, weapons systems and subsystems they are supporting.

The Contractor shall support the writing and staffing of the technical sections of Grounding Bulletins and the associated Red Stripe Memo’s. Specifically, the Contractor, when asked, shall draft the initial technical framework of a Red Stripe Memo per NAVAIRINST 5100.11 (Research and Engineering Technical Review of Risk Process and Procedures for Processing Grounding Bulletins). The Contractor shall contact competency Subject Matter

Experts as identified and record technical assessments from System Safety and other as needed competencies to allow the assessment of technical and safety risk.

The Contractor shall review redesign integration approaches within Engineering Change Proposals (ECPs) and associated forced retrofit incorporation/installation schedules and provide recommendations regarding impacts to operational availability, mod line capabilities/limitations and programmatic areas of risk.

The Contractor shall provide retrofit incorporation depot mod planning; perform trade-off analysis, engineering approach analysis for integration of subsystems, new functions, modes, architectures or modifications as specified in

ECPs. Based on these analyses, the Contractor shall recommend specific system development / engineering efforts and task requirements necessary to meet program objectives and milestones. The Contractor shall provide support in performing trade-off studies and prepare position papers, including risk assessments, for alternative retrofit incorporation considerations.

The Contractor shall support the definition, implementation and operation of government controlled websites, databases and similar informational sources for collection and dissemination of information related to the reliability, failure, supply, usage and operational data of Naval Aviation parts, subsystems and systems. This support shall be extended to other areas in support of aging Naval Aviation assets.

3.2.7 Information Technology (IT). The Contractor shall provide IT support to manage the computer assets for

AIR-4.1 Systems Engineering Department. The Contractor shall prepare, coordinate and obtain approval for processes relating to verification of Navy and Marine Corps Intranet (NMCI) seat requirements, purchase authorization, funding and contract compliance. Once approved, the Contractor shall coordinate all the requirements for all users, including the specification, ordering, acceptance, assignment, inventory and disposal of all approved

NMCI assets. The Contractor shall provide support in obtaining all required IT approvals for the department. The

Contractor shall support the provisioning of standard office supplies and equipment as required and utilized by the

DoD Electronic Mall (EMALL) system.

3.2.8 Administrative Support of Technical Staff. The Contractor shall provide general office support to the

AIR-4.1 Systems Engineering team. Efforts include the preparation of letters, various documentation, reports and forms. The Contractor shall prepare and track travel orders and plan and provide support in the execution of meetings and conferences, including Video Teleconferencing (VTC) and remote conferencing support. The

Contractor shall provide data entry or transcription, graphics presentation support, filing, reproduction and office operation support. The Contractor shall provide support in procuring vendor support for complex documents, drafting, presentation and graphics support as required. The Contractor shall support the provisioning of standard office supplies and equipment as required and utilized by the DoD Electronic Mall (EMALL) system.

3.2.9 The Contractor shall support the identification of any technical problems associated with performance of requested systems sustainment, training and tooling engineering services. The Contractor shall document such issues and identify potential solutions in the Contractor's Progress, Status and Management Report. (CDRL A005)

3.2.10 The Contractor shall support routine status reviews with the appropriate program Technical Point of

Contact (TPOC) regarding overall progress, status, risks, issues, travel and financials and also document the findings in the Contractor's Progress, Status and Management Report. (CDRL A005)

3.3 DELIVERABLES AND DOCUMENTATION

Deliverables shall be task dependent and may include one or more of the following:

A001 Management Plans

A002 Plan of Action & Milestones (POA&M)

A003 Scientific and Technical Reports

A004 Technical Report – Study/Services

A005 Contractor’s Progress, Status and Management Report

A006 Non-Disclosure Agreement (Company)

A007 Non-Disclosure Agreement (Individual)

A008 Program Protection Implementation Plan

3.4 OTHER DIRECT COSTS (ODC): TRAVEL AND MATERIAL

ODCs necessary for performance of this contract shall be reimbursed in accordance with NAVAIR clauses

5252.232-9509 (Reimbursement for Travel, Per Diem and Special Material Costs) and clause 5252.242-9515

(Restrictions on the Direct Charging of Material). ODCs may include general and administrative (G&A) expenses as allowed by the Contractor’s accounting standards, but shall not include profit. Any material remaining after completion of the contract, the cost of which has been reimbursed by the Government, will remain Government property and the Contractor will seek disposition instructions from the PCO.

3.4.1 Travel. Continental United States (CONUS) and Outside the Continental United States (OCONUS) travel may be required in support of this contract to perform services at other DoD, industry and related locations as approved by the government in individual task orders. OCONUS travel may be required to the following countries:

Canada, England, France, Germany, Italy, Sweden, Denmark, Israel, Turkey, Japan and Australia. The number and types of trips, including the number of persons traveling, shall be limited to the minimum required to accomplish work requirements and shall be coordinated with and approved by the Government TPOC and the COR for each individual trip prior to travel. Costs associated with travel and lodging shall be reimbursed in accordance with

Federal Joint Travel Regulations (JTR).

3.4.2 Material. Per NAVAIR clause 5252.242.9515 (Restriction on the Direct Charging of Material), Material may be purchased incidental to the tasking. The material costs may include such items as: photocopying, postage, office supplies, briefing materials, and video and voice conferencing services. COR approval shall be obtained for all material purchases.

4.0 INFORMATION TECHNOLOGY (IT)

The Contractor may be required to access Government IT Systems. Contractor personnel requiring access to

Government IT Systems shall comply with NAVAIR clause 5252.204-9505 (System Authorization Access Request

Navy). The Government will provide all necessary obsolete reference documents and those not generally available to the Contractor as requested.

The Contractor shall not purchase any IT equipment on behalf of NAVAIR in support of this Contract, which reports to Program Budget Information System for Information Technology (PBIS-IT), without a NAVAIR

Command Information Officer (CIO) approved Navy Information Approval System IT Procurement Request (NAV-

IDAS ITPR).

4.1 CLINGER-COHEN ACT (CCA)

4.1.1 The Contractor shall conduct analysis of program/project needs, acquisition strategy and program artifacts to identify and capture specific factors required to satisfy the 11 elements of CCA compliance listed in DoDI

5000.02, Enclosure 1, Table 10. Using Microsoft Word, the Contractor shall prepare a CCA compliance matrix following the organization and appearance of Table 10 with additional separate columns for the display of artifact:

titles, date(s) of approval, page number(s) and paragraph or section number(s). The right-hand column shall include an embedded object permitting the reader to open unclassified artifacts. The column shall identify classified artifacts and shall describe approved classified channels for access of classified artifacts. The Contractor shall support the program manager during CCA compliance review and assist in responding to reviewer comments if and when additional supporting information or revisions are required; to the extent the Government has access to such documents.

4.1.2 Updating approved CCA compliance packages: For updates of approved CCA compliance packages, the

Contractor shall conduct analysis of program/project needs, acquisition strategy and program artifacts to identify and to determine if each of the Eleven Elements of CCA has changed and if no change has occurred, a notation stating

“no change” shall be entered in the CCA compliance matrix. If changes have been found, the Contractor shall update the CCA compliance matrix to reflect the changes.

4.1.3 The Contractor shall support the program manager during CCA compliance review and assist in responding to reviewer comments if and when additional supporting information or revisions are required.

4.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)/NAVAIR Functional Area Manager (FAM)

Policies and Guidance, Network and Server Registration and Web Enablement mandates.

4.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. Potential 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 Amendment to the Rehabilitation Act of 1973. https://www.section508.gov/ content/ learn/ laws-and-policies

d. Department of Defense Web Policies and Guidelines. http://dodcio.defense.gov/dodwebpolicy

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

www.public.navy.mil/fcc-c10f/niocnorfolk/Documents/NTD-08-09.txt

4.4 SOFTWARE DEVELOPMENT / SERVER PROCUREMENT

Any tools developed that will be hosted by the Navy Marine Corps Intranet (NMCI) or run on NMCI workstations will be certified for NMCI and comply with NMCI policy. Additionally, any servers supporting this effort will be transitioned to meet the requirements of the current NAVAIR Server Consolidation effort.

4.5 CYBERSECURITY

4.5.1 The Contractor shall conduct investigation and analysis of acquisition program artifacts such as, but not limited to, Initial Capabilities Document (ICD), Capability Development 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 Cybersecurity Strategy (CS) needed to steer and inform the program’s development of a Security Plan (SP) in accordance with DoDI 8510.01, of 12 March 2014.

4.5.2 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 Cybersecurity, 14 March 2014.

b. DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), 12 March 2014.

http://www.whitehouse.gov/omb/circulars_a130_a130trans4 https://www.section508.gov/ http://dodcio.defense.gov/dodwebpolicy http://www.public.navy.mil/fcc-c10f/niocnorfolk/Pages/AboutWRA.aspx http://www.navy.mil/navydata/internet/secnav5720-47b.pdf http://www.public.navy.mil/bupers-npc/reference/messages/Documents/NAVADMINS/ http://www.public.navy.mil/bupers-npc/reference/messages/Documents/NAVADMINS/%20NAV2007/NAV07145.txt http://www.doncio.navy.mil/ContentView.aspx?ID=577 http://www.public.navy.mil/fcc-c10f/niocnorfolk/Documents/NTD-08-09.txt

c. Committee on National Security Systems Instruction 1253, “Security Categorization and Control Selection for

National Security Systems,” March 15, 2012, as amended.

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

4.5.3 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 CDRLs A002 and A003. 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) listed in 4.5.2 above. This includes IT that is standalone and IT that is connected to other systems, networks or enclaves. Information systems

(IS) (enclaves or major applications), 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 cybersecurity compliance. Transition planning proposed or performed under this contract shall be in compliance with the above paragraph 4.5.2 reference (b) Enclosure 8, Figure 2 and all hardware, firmware and software deliverables shall be capable of receiving Authorization to Operate in accordance with the above paragraph 4.5.2 reference (b).

4.5.4 Information technology services shall only be performed by personnel who are qualified and certified in accordance with the above paragraph 4.5.2 reference (d). 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.

4.5.5 The Contractor shall investigate and conduct analysis in order to provide technical reviews to make a recommendation with data supporting the proposal(s) for the need for designation (or not) of the system, network or enclave as PIT or a PIT system in accordance with DoDI 8500.01, Cybersecurity, 14 March 2014. The proposal shall include all technical data required to engage in collaboration with the security control assessor, the authorizing official (staff) and PIT designating official(s). In the event the collaboration results in redesign or follow-up action after collaboration requiring additional or revised documentation, the Contractor shall continue to assist the collaboration process.

4.5.6 The Contractor shall investigate and conduct analysis in order to provide technical reviews to make a recommendation with data supporting characterization and selection of security controls in accordance with DoDI

8500.01, Risk Management Framework (RMF) for DoD Information Technology (IT), 12 March 2014, National

Institute of Standards and Technology (NIST) Special Publication (SP) 800-53, Security and Privacy Controls for

Federal Information Systems and Organizations, Revision 4, April 2013, NIST SP 800-37 Revision 1, Guide for

Applying the Risk Management Framework to Federal Information Systems, February 2010, Federal Information

Processing Standards Publication (FIPS 199, February 2004. Contractor performed analysis shall include; criticality analysis, threat assessment and vulnerability assessments. The Contractor shall propose characterization of the system and selection of security controls use Committee on National Security Systems Instruction (CNSSI) 1253, Security Categorization and Control Selection for National Security Systems, 27 March 2014 to tailor the NIST guidance. The proposal shall include all technical data required to engage in collaboration with the security control assessor and the authorizing official (staff). In the event the collaboration results in redesign or follow-up action after collaboration requiring additional or revised documentation, the Contractor shall continue to assist the collaboration process.

4.5.7 The Contractor shall investigate and conduct analysis in order to provide technical reviews to make a recommendation with data supporting the development of the Security Plan. Contractor performed analysis shall include; criticality analysis, threat assessment and vulnerability assessments. The security Plan shall be prepared for the first program/project decision point and updated for each subsequent decision point. The proposal shall include all technical data required to engage in collaboration with the security control assessor and the authorizing official

(staff). In the event the collaboration results in redesign or follow-up action after collaboration requiring additional or revised documentation, the Contractor shall continue to assist the collaboration process.

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

a. DoDI 8582.01, ASD (NII) Directive-Type Memorandum (DTM) 08-027 – Security of Unclassified DoD

Information on Non-DoD Information Systems, 06 June 2012.

b. Chairman of the Joint Chiefs of Staff Instruction CJCSI 3170.01H (series), Joint Capabilities Integration and

Development System, 10 January 2012.

c. CJCSI 6211.02D, Defense Information System Network (DISN): Policy and Responsibilities, 24 Jan 2012.

d. CJCSI 6212.01F, Net Ready Key Performance Parameter (NR KPP), 21 March 2012.

e. CJCSI 6251.01D, Narrowband Satellite Communications Requirements, 30 Nov 2012.

f. CJCSI 6510.01F, Information Assurance (IA) and Support to Computer Network Defense (CND), 09 Feb 2011, certified current 10 Oct 2013.

g. Chairman of the Joint Chiefs of Staff Manual CJCSM 6510.01B – Cyber Incident Handling Program, 10 July

2012.

h. Navy Ports, Protocols and Services (NPPS) Manual, Version 1.5, 16 November 2010.

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 3, 24 Jan 2012).

l. DoDD 8000.01, Management of the Department of Defense Information Enterprise, 10 February 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, 23 April 2007.

n. DoDD 8570.01, Information Assurance Training, Certification and Workforce Management, 15 August 2004, Certified Current, 23 April 2007.

o. DoDI 8330.01, Procedures for Interoperability and Supportability of Information Technology (IT) and National

Security Systems (NSS), 21 May 2014.

p. DoDI8500.01, Cybersecurity, 14 March 2014.

q. DoDI 8520.02, Public Key Infrastructure (PKI) and Public Key (PK) Enabling, 01 April 2004.

r. DoDI 8551.01, Ports, Protocols and Services Management (PPSM), 28 May 2014.

s. DoDI 8581.01, Information Assurance (IA) Policy for Space Systems Used by the Department of Defense, 8

June 2010.

t. 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 2010.

u. DON letter 5239 NAVAIR 726/2322 of 18 Feb 09, NAVAIR Data at Rest Policy.

v. Federal Information Processing Standards Publications (FIPS PUB)-199, February 2004.

w. National Security Telecommunications and Information Systems Security Policy NSTISSP No. 11, Revised

Fact Sheet National Information Assurance Acquisition Policy, July 2003.

x. Office of the Chief of Naval Operations OPNAV INST 5239.1C, Navy Information Assurance (IA) Program, 20 Aug 08.

y. SECNAV M-5239.1, Department of the Navy Information Assurance Program; Information Assurance Manual, November 2005.

z. SECNAVINST 5230.15, Information Management/Information Technology Policy for Fielding of Commercial

Off the Shelf Software, 10 April 2009.

aa. SECNAVINST 5239.3B, Department of the Navy Information Assurance Policy, 17 June 2009.

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 of the U.S. Code/Clinger-Cohen Act.

ee. Title 44 of the U.S. Code/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.

4.5.9 Provided that IT approval is received, all IT procured on behalf of this contract shall meet all DoD/DON and NAVAIR cybersecurity polices. Failure to follow these policies will result in denied access to NMCI, One Net, Integrated Shipboard Network System (ISNS) and other DON, DoD and Joint Networks. These cybersecurity policies are standard across the Department and ensure cybersecurity compatibility and interoperability.

IT systems and or networks operated by Contractors pursuant to a NAVAIR contract, regardless of the level of data processed, shall be operated in accordance with the NISPOM. Approved Contractor-owned equipment shall be permitted connections to NAVAIR/DoD networks in order to carry out the performance of this contract. All

Contractor-owned hardware and/or software shall meet DoDI 8500.1 Cybersecurity (CS), is subject to validation scanning and must be approved by the NAVAIR site CS Program Manager prior to connection.

4.5.10 The following specific criteria must be met before the Contractor can be connected to any DoD or

NAVAIR network in support of this contract. Requirements include:

a. Network Vulnerability Scanning. NAVAIR Deputy CIO for Information Assurance maintains authorized auditing tools and shall provide for firewall/port scans, device discovery scan, vulnerability assessment and other requirements as required to ensure secure interoperability with DoD networks.