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

1. CONTRACT ID CODE PAGE OF PAGES

S 1 34

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

16C. DATE SIGNED

BY 04-Sep-2019

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 N0042119R0018

X 9B. DATED (SEE ITEM 11)

23-Aug-2019

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 is extended, X 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 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

04-Sep-2019

CODE

NAVAL AIR WARFARE CENTER AD-PAX-

CODE 2.5.1.14

21983 BUNDY ROAD

BLDG 441

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:

N0042119R0018

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been modified:

Amendment 0003:

The purpose of this amendment is as follows:

1) Section C, Statement of Work paragraph 3.1.2.2, Physical Facilities, is revised to remove the requirement for facilities to maintain a SECRET clearance. No classified storage is required.

2) Attachment P6 Cost Summary, and Attachment P7 Fully Burdened Labor Rates are revised to correspond with the labor category titles, hours, and locations specified in the solicitation.

3) Section J, List of Documents, Exhibits and Other Attachments, Description for Attachment P6 has changed from Cost Summary to Cost Summary_Rev1.

4) Section J, List of Documents, Exhibits and Other Attachments, Description for Attachment P7 has changed from Fully Burdened Rates to Fully Burdened Rates_Rev1.

Amendment 0002:

The purpose of this amendment is to update/revise:

1) Updated language in Section L, Part A, 4.0.

Amendment 0001:

The purpose of this amendment is to update/revise:

1) Updated resume page limit in Section L, Part A, 3.0, paragraph 3, table 1.2,

2) Clarified language in Section L, Part B, 2.0, paragraph 4 and

3) Updated magnitude contract dollar value in Section M, Part B, 2.0, paragraph 2.

Government Points of Contact:

Contract Specialist: Erik Seastrand

Phone: 301-757-2532

Email: erik.seastrand@navy.mil

Contracting Officer: Lynn Kaniss

Phone: 301-757-3421

Email: lynn.kaniss@navy.mil

Contract Type:

The contract resulting from this solicitation will be a Single Award Indefinite Delivery Indefinite Quantity (IDIQ).

Product Service Code:

The Product Service Code (PSC) for this solicitation is R706, Support – Management: Logistics Support.

Small Business Set-Aside:

This solicitation is reserved as a Total Small Business Set-Aside under NAICS Code 541330.

Proposal shall remain valid for 180 days after proposal due date, in accordance with Section L.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

Items 0001-0003: The Contractor shall provide services in accordance with the Section C, Statement of Work

(SOW). Contract services shall be performed in accordance with the Statement of Work (SOW) as detailed in individual task orders. The task order Statement of Work (SOW) will detail tasks that fall within the scope of the basic contract.

Items 0004-0006: The Contractor shall provide ODCs in accordance with the Section C, Statement of Work (SOW) and 5252.232-9509, Travel Approval and Reimbursement Procedures (NAVAIR) (OCT 2013).

Item 0007: The data to be furnished hereunder shall be in accordance with Exhibit A, DD Form 1423, Contract Data

Requirements List (CDRL), and the Section C, Statement of Work (SOW).

Statement of Work Statement

Aviation Logistics Environment (ALE), Program Management and Lifecycle Support Services

Date: 21 August 2019

Naval Air Systems Command (NAVAIR)

Naval Air Warfare Center Aircraft Division (NAWCAD)

1.0 Background

The Naval Aircraft Warfare Center – Aircraft Division (NAWC-AD) Aviation Logistics Environment (ALE) has the overall responsibility to research, analyze and evaluate solutions in order to implement and deploy the best Naval

Aviation Logistics Information Technology (IT) solutions across the Naval Aviation Enterprise (NAE). This

Logistics support includes both new logistics Information Technology (IT) solution sets and sustaining existing IT solution sets in the strategic and tactical domains. The Aviation Logistics Environment (ALE) is the NAVAIR

Logistics Information Technology (IT) Defense Business System (DBS) delivering full lifecycle weapon system logistics and maintenance capabilities in support of the Naval Aviation Enterprise. The ALE delivers these capabilities via a net-centric, shared, data environment supporting shore based, afloat and expeditionary operations.

ALE integrates IT Services plane-side and interfaces with infrastructure systems, enabling data analysis in support of aircraft availability and Ready Basic Aircraft (RBA) status.

ALE is a Tech Refresh Program, modernizing current systems in the Logistics IT Portfolio, and adding new capabilities as the Integration IPT for the Aviation Readiness Digital Integration Working Group (DIWG) with a current focus on Sustainment Vision 2020. As Tech Refresh progresses, a reduction in the number of systems in the

Logistics IT Portfolio will be achieved as Business Process Reengineering (BPR) and System Integration efforts are completed. ALE contributes to reduction of Total Ownership Costs by reducing work force resulting from centrally managed Logistics IT solutions and providing Enterprise Logistics IT Solutions (off-aircraft) to PMAs reducing unnecessary development of platform unique IT solutions.

1.1 General

This Statement of Work (SOW) supports the mission of Naval Air Systems Command (NAVAIR) to maintain fleet production readiness by providing integrated Program Management Office (PMO) and Functional Manager (FM) support.

The SOW also supports Department of Navy (DoN), Headquarters Marine Corps (HQMC), United States Fleet

Forces Command (USFF), and Program Executive Office – Enterprise Information Systems (PEO-EIS) IT programmatic support that aligns with Naval Aviation Environment (NAE) objectives, or supports command level fleet readiness initiatives.

1.2 Scope

The scope of this SOW includes support of the NAWC-AD, Aviation Readiness & Resource Analysis Aviation

Logistics Environment (ALE) with programmatic functional support and governance of NAVAIR Logistics

Initiatives, enterprise programmatic support of NAVAIR Sustainment Vision (SV)2020 Initiatives, and the Aviation

Logistics Environment (ALE) inclusive of the following Capability Areas: Ground Station, Integration, Product

Lifecycle Management (PLM)/Enterprise Service Bus (ESB), Data Transport and Infrastructure, Deficiency

Reporting, Engineering and Tech Data Management, and Maintenance Data Management and Warehousing.

Additional management governance support will include the Maintenance Enterprise Ground Station for Aviation

(MEGA), Marine Aviation Logistics – Enterprise IT (MAL-EIT) Family of Systems (FOS) and the Naval

Operational Business Logistics Enterprise (NOBLE) Family of Programs, including the Naval Aviation

Maintenance System (NAMS).

Specific support service tasking includes:

1.2.1 Program Management, to include:

1.2.1.1 Project Planning and Program Management Support

1.2.1.2 Monitoring and Control

1.2.1.2 Portfolio Management

1.2.1.4 Risk Management

1.2.1.5 Configuration Management

1.2.1.6 Financial Management

1.2.1.7 Facilitation and Training

1.2.1.8 System Documentation.

1.2.2 Lifecycle Logistics

1.2.3 Business Process Improvement, to include:

1.2.3.1 Business Transformation

1.2.3.2 Business Environment

1.2.3.3 Business Process Reengineering

1.2.3.4 Business Analysis

1.2.4 Functional Assessment/Data/Gap Analysis

1.2.5 Requirements engineering, including requirements management and requirements analysis.

2.0 Applicable Documents

2.1 Department of Defense (DoD) Specifications

2.1.1 DoD 5220.22-M, National Industrial Security Program Operating Manual, (NISPOM) 28 Feb 2006.

2.1.2 SECNAV M-5510.36, Information Security Program, 30 Jun 2006.

2.1.3 DoDM 5200.01 (DoD Information Security Program: Controlled Unclassified Information (CUI)) Vol. 4

(enclosure 3 pages 11-18) 24 Feb 2012.

2.1.4 DoD 5400.7-R, Freedom of Information Program Chapter 3 (pages 31-42) Sep 1998

2.1.5 DoDD 5230.24 Distribution Statements on Technical Documents, Change 1, Effective 28 Apr 2016.

2.1.6 SECNAV M-5510.30 Personnel Security Program Jun 2006.

2.1.7 OPNAVINST 3440.17A Navy Installation Emergency Management Program, 1 Aug 2014.

2.1.8 DoDI 5000.75 Business System Requirements and Acquisition

2.1.9 DoDI 5000.02 Operation of the Defense Acquisition System

2.1.10 DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT)

2.1.11 SECNAVINST 5239.3B, DON Information Assurance Policy

2.1.12 SECNAV M-5239.1, DON Information Assurance Manual

2.1.13 SECNAVINST 5510.30B, DON Personnel Security Program (PSP) Instruction, 6 Oct 2006

2.1.14 DoDI 5230.24, Distribution Statements on Technical Documents

Additional applicable documents and DoD specifications may be included at the task order level.

2.2 Industry Documents

2.2.1 International Organization for Standards (ISO) Standard-9001-2015

3.0 Requirements

3.1 General Requirements

3.1.1 Compatibility

The Contractor shall maintain the capability to prepare documents and software packages compatible with the

Government IT environment through the security classification of Secret. The current operating environment required for this contract includes:

Microsoft Windows 10

Microsoft Project 2010

Microsoft Office Professional Plus 2016

Adobe Acrobat XI (reader)

Internet access

The Contractor shall maintain the ability to interface with and transfer data to and from requiring office software applications and their upgraded versions. The Contractor shall ensure that all media are virus free when delivered.

The Contractor shall be capable of Internet and LAN communications with NAVAIR. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with NAVAIR during working hours whether at Contractor work site or on travel.

3.1.2 Work Location and Facilities

3.1.2.1 Work location

Approximately 10 percent of work will be performed at Government sites and 90 percent of work will be performed at the Contractor’s and/or sub-contractor sites. Government sites include NAVAIR/NAWC-AD at Naval Air Station, Patuxent River, MD, and MCAS Miramar in San Diego, CA, and the United States Fleet Forces (USFF) Command, Norfolk, VA. Requirements for additional USFF command locations are anticipated, and will be specified at the task order level. As necessary, contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network access, including web servers and applicable databases or other applications necessary to carry out assigned tasks.

3.1.2.2 Physical Facilities

The Contractor shall, within 30-days of contract award, maintain facilities located within a fifty (50) miles radius of the Patuxent River Air Station, MD and within a fifty (50) mile radius of the Naval Station Norfolk, VA to facilitate close coordination with USFF and other fleet activities. Contractor facilities shall have accommodations for working groups with at least 30 participants.

3.1.2.3 Meeting and Conference Room Support

In support of the tasking outlined in this SOW, the Contractor shall have the capability to host and conduct meetings at the classification levels up to UNCLASSIFIED with the capacity to support a minimum of 30 people. The facility shall have projectors and/or TV displays, computer(s) with compatible software as required in Paragraph 3.1.1 and telephone(s). This support shall be provided at the Contractor’s Patuxent River, MD and Norfolk, VA locations.

3.1.3 Basic Contract Data Deliverables

The Contractor shall provide the following documentation.

3.1.3.1 Monthly Progress and Financial Status Report (CDRL A001)

The Contractor shall provide a progress and financial status report in the Monthly Status Report in accordance with the Contract Data Requirement List (CDRL) A001. The report shall include work accomplished since submittal of the last report, monthly and cumulative man-hour labor costs expended by labor category, and travel costs.

3.1.3.2 Integrated Master Schedule (CDRL A002)

The Contractor shall develop an Integrated Master Schedule (IMS) that aligns with PMO project schedules that reflects and addresses all PMO and FM support requirements. The IMS shall show the allocation of resources (staff, facilities, and equipment) by each task order.

3.1.3.3 Transition Out Strategy (CDRL A003)

The Contractor’s overall transition out strategy shall be built around maintaining the mission of the program/division with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Upon termination or expiration of the contract, the Contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation. The Contractor shall submit a Transition

Out Plan, to include the minimum elements listed below in accordance with CDRL A003.

- Work Turnover. The Contractor shall provide a plan of action to effectively transfer tasked work that is in process at the expiration or termination of the contract to the successor company. Establish and maintain effective communication with the incoming Contractor or Government personnel for the period of transition via weekly status meetings.

- Quality Assurance. The Contractor shall provide a plan of action to ensure continuation of quality review processes during the transition period to the successor company.

- Risk Mitigation Strategies. The Contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period.

- Data/Information Transfer. The Contractor shall provide a plan of action for the efficient inventory and transfer of program data to the successor company.

3.1.3.4 Operations Security (CDRL A004)

Operational Security (OPSEC). The Contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used by the Contractor and any subcontractor during performance of the contract. The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. This program may include Information Assurance and

Communications Security (COMSEC). The OPSEC program shall be in accordance with National Security

Decision Directive (NSDD) 298, and at a minimum shall include:

a. Assignment of responsibility for OPSEC direction and implementation.

b. Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.

c. Establishment of OPSEC education and awareness training.

d. Provisions for management, annual review, and evaluation of OPSEC programs.

e. Flow down of OPSEC requirements to subcontractors when applicable.

While performing aboard Navy and/or NAVAIR sites, the Contractor shall comply with facility OPSEC program instructions and contribute to organization-level OPSEC efforts. Include OPSEC as part of its ongoing security awareness program and take all required Agency training. Be responsive to the Supporting OPSEC Manager on a non-interference basis. Protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the RO and Contractor in support of the mission.

3.1.4 Task Order Data Deliverables

Additional CDRLs are anticipated and will be specified in the individual task orders. The following is a non-exclusive list of anticipated task order CDRLs:

Programmatic Logistical Documentation, to include analysis, planning, implementation, sustainment, and retirement artifacts.

Business Process Models

Requirements Specifications

Business Solution Functional Analysis

Requirements Traceability Matrix

Business Rules Implementation and Lessons Learned

Project Management Plan

Financial Management

Quality Management Plan

Risk Management Plan

Communications Plan

Conference Agenda

Conference Minutes

ALE Integrated Product Team (IPT) program support artifacts as designated in individual task orders.

3.1.5 Work Schedule to include Compressed Work Schedule (CWS), overtime, holidays, and installation closure.

3.1.5.1 Work Schedule

The Contractor shall provide the required services and staffing coverage during normal working hours. Normal working hours are usually 8.5 hours (including a 30-minute lunch break), from 0800 to 1630 each Monday through

Friday (except on the legal holidays specified in paragraph 3.1.5.1.2). Some supported Government offices have flexibility to start as early as 0600/0630 and end as late as 1800, Monday – Friday. Specific working hours will be provided at the task order level.

3.1.5.1.1 Compressed Work Schedule (CWS)

CWS is an alternative work schedule to the traditional five 8.5-hour workdays (which includes a 30-minute lunch) worked per week. Under a CWS schedule, an employee completes the following schedule within a two-week period:

eight weekdays are worked at 9.5 hours each (which includes a 30-minute lunch), one weekday is alternately worked as 8.5 hours (which includes a 30-minute lunch) and one weekday is not worked by the employee. The result is 80 hours worked every two weeks, with 44 work hours one week and 36 work hours the other.

The Contractor may allow its employees to work a CWS schedule provided the requirements of this contract and subsequent task orders are met. If the Contractor chooses to allow its employees to work a CWS schedule in support of this contract, any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the Government. Additionally, the

CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage as required by the Government.

3.1.5.1.2 Holidays

The Government observes the following holidays:

New Year’s Day, January 1

Martin Luther King’s Birthday, the third Monday in January

President’s Birthday, the third Monday in February

Memorial Day, the last Monday in May

Independence Day, July 4

Labor Day, the first Monday in September

Columbus Day, the second Monday in October

Veteran’s Day, November 11

Thanksgiving Day, the fourth Thursday in November

Christmas Day, December 25

With the exception of the events in section 3.1.5.1.3 below, the Contractor is permitted to observe the above holidays in accordance with its corporate policy.

3.1.5.1.3 Installation Closure

When Federal employees are officially excused from work due to a holiday or a special event, severe weather, a security threat, or any other Government facility related problem that prevents Federal personnel from working at the Government facility, Contractor personnel assigned to work at that facility performing non-mission essential work in support of such Federal employees shall follow their parent company’s policies.

While generally, Contractor personnel may not perform work on-site at a Government facility without supervision from Federal personnel, in very limited circumstances, work being performed by Contractor personnel may be deemed mission essential and performance of such mission essential work may be authorized to continue at the

Government facility despite the facility being otherwise closed for normal operations. The circumstances permitting work being performed by Contractor personnel to be deemed mission essential are extremely limited and generally only apply to performance of efforts related to public health, safety, or matters related to national security. The cognizant Contracting Officer must concur with any determination that work being performed by Contractor personnel is mission essential.

3.1.5.1.4 Overtime

Overtime cannot be charged directly to the contract unless first approved in writing by the Chief of the Contracting

Office.

3.1.6 Other Direct Costs

ODCs are based on a per annum amount. COR approval shall be obtained prior to incurring any travel expenses.

3.1.6.1 Travel

Travel may include general and administrative expenses, but shall not include profit. Temporary travel to other locations in support of program tasking may be required. If required, temporary OCONUS travel locations include

Japan, Australia, and Bahrain, and CONUS locations include Norfolk, VA, Patuxent River, MD, San Diego, CA, and Cherry Point, NC. This list is not all inclusive and travel locations will be specified in the individual task orders.

3.1.7 Subcontractors

Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this contract. Contractor shall flow down all provisions of this SOW to subcontractors providing support under this contract.

3.1.8 Management of Contractor Personnel

The Government shall neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual Contractor employees. The Contractor shall manage its employees and guard against any actions that are of the nature of personal services, or give the perception of personal services.

3.2 Security

3.2.1 Citizenship Requirements

Only U.S. citizens shall perform under this contract.

3.2.2 Investigative Requirements

Unclassified: All Contractor personnel must be eligible to perform Non-Critical Sensitive work as defined by

SECNAV M-5510.30. All Contractor personnel are required to have a favorably adjudicated Tier-3 investigation from the Office of Personnel Management. The Contractor shall submit a request for personnel security investigation to the Government Security Office. The Government Security Office will initiate the Contractor's

Electronic Questionnaire for Investigations Processing (eQIP)), and do a preliminary screening of the Contractor's eQIP for suitability and derogatory information. The Contractor employee shall provide all requested information pursuant to the Privacy Act of 1974. The Government Security Office may deny the Contractor access to

Government facilities and information and may prohibit the Contractor from performance of sensitive duties for failure to provide requested information or when derogatory or adverse information is present on the Contractor's eQIP, in such cases, the Contractor employee may not perform on the Contract.

The Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified information and to control distribution of controlled unclassified information in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), and SECNAV M-

5510.36. All Contractor facilities shall provide an appropriate means of storage for controlled unclassified information and materials. All controlled unclassified information shall be appropriately identified and marked as

For Official Use Only in accordance with DoDM 5200.01, Information Security Program: Controlled Unclassified

Information (CUI) Volume 4 (enclosure 3).

Controlled Unclassified Information including For Official Use Only and Covered Defense Information (meeting the definition of 48 CFR 252.204–7012(a)) generated and/or provided under this contract shall be marked and safeguarded as specified in DoDM 5200.01 (DoD Information Security Program: Controlled Unclassified

Information (CUI)) Vol. 4 (enclosure 3 pages 11-18) available at http://www.dtic.mil/whs/directives/corres/pdf/520001_vol4.pdf. Any product containing Covered Defense

Information shall be assigned a distribution statement (distribution statements B through F) using the criteria set forth in DoDI 5230.24 (Distribution Statements on Technical Documents); and have this statement displayed per

DoDI 5230.24, Enclosure 3.

All controlled unclassified technical information shall be appropriately identified and marked with the following distribution statement(s):

Distribution Statement D: Distribution authorized to the Department of Defense and U.S. DoD Contractors only

(Critical Technology) (dated - _______). Other requests shall be referred to: Commander, Naval Air Systems

Command, Attn: (- _______)

Classified: All Contractor personnel shall maintain security clearance eligibility commensurate with the level of classification of the work performed as annotated in the Contract's DD-254, Contract Security Classification

Specification Form.

Contractor personnel shall require access to classified information in performance of this contract up to and including (Secret), with a safeguarding level of (Secret). The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated in accordance with DoDM 5220.22, National Industrial Security Program Operating Manual. Contractor employees who fail to meet security clearance requirements may not access classified information or perform sensitive duties. In such cases, the Contractor employee may not perform on the contract.

The Contractor shall comply with security requirements specified in the DD-254 attached to this contract.

Information or data that the Contractor accesses shall be handled at the appropriate classification level. Unclassified information shall be handled in accordance with the appropriate designation (Controlled Unclassified Information;

For Official Use Only; Covered Defense Information). Distribution is authorized to the Requiring Office's

Organization and supported Activity only. Other requests for deliverables under this contract shall be referred to the

TPOC/COR of this contract for approval.

3.2.3 Common Access Card (CAC)/Public Key Infrastructure (PKI), System Authorization Access Request

(SAAR-N).

3.2.3.1 SAAR-N

All Contractor personnel requiring access to Government Information Technology (IT) systems shall have an approved System Authorization Access Request (SAAR-N) Form OPNAV 5239/14 (Rev Sep 2011) on file, and complete required Annual Information Awareness Training. New employees must submit their SAAR forms within thirty (30) days of their first day of work.

SAAR-N forms shall be submitted to the COR, Government TPOC, or to the assigned government Trusted

Associate Sponsorship System (TASS) Trusted Associate.

3.2.3.2 CAC / Local Badges

Contractor CACs and facility specific identification badges will be issued by the Government to on-site Contractor personnel and shall be visible at all times while personnel are at the Government site. The Contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to NAVAIR security requirements. All CACs and identification badges issued to Contractor employees shall be returned to the

Government Security Department at the NAVAIR security office following completion of the contract, relocation or termination of an employee, or upon request from the COR. The Government will provide the Contractor access to

Government facilities, as required, for performance of task orders under this contract. Contractor personnel shall comply with facility and security requirements to work in the Government building space.

3.2.3.3 DD-254

The Contractor shall comply with security requirements specified in the DD-254, Attachment 1, in Section J of this contract. Information or data that the Contractor accesses shall be handled at the appropriate classification level, unclassified information shall be handled as “For Official Use Only.” Distribution is authorized to the Requiring

Office’s Organization and supported Activity only. Other requests for deliverables under this contract shall be referred to the TPOC/COR of this contract for approval.

3.2.4 Information Security

If the work is performed at the Contractor’s facility, the Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and controlled unclassified information (CUI) and to control distribution of CUI in accordance with DoD 5220.22-M (NISPOM), and SECNAV

M-5510.36. If the work is performed at the Government’s facility, the Contractor shall comply with facility and security requirements to work in the Government building space.

3.2.4.1 Marking

All information generated by the Contractor shall be properly marked. For Official Use Only information generated or provided under this contract shall be marked in accordance with DoDM 5200.01. Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings in accordance with DoDD

5230.24 and program Security Classification Guidance.

3.2.4.2 Public Release

Public Release for Classified and Unclassified Information: Any controlled information pertaining to this contract shall not be released for public dissemination, including posting to any social media sites such as Facebook or

Twitter, unless it has been approved for public release by appropriate U.S. government authority. Proposed public releases shall be submitted for approval prior to release via the PEO, and through the Public Affairs Office, 47123

Buse Road, RADM William A. Moffett Building, Patuxent River, MD 20670-1547.

3.2.4.3 Loss, Compromise and/or Electronic Spillage of Classified or Controlled Unclassified Information

All instances of loss, compromise or electronic spillage of classified or controlled unclassified information shall be reported to the COR, TPOC and Government Security Office within 24 hours of the incident.

3.2.5 Anti-Terrorism Force Protection and Emergency Management

The work performed on this contract is not Emergency Essential in accordance with OPNAVINST 3440.17A and

Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans. Contractor personnel shall comply with all Government Emergency Management, Antiterrorism and Continuity of Operations Plans and directives. Contractor personnel shall not report for work at Government facilities upon declaration of Force

Protection Condition CHARLIE or in any event or emergency where the Government directs curtailment of operations to “Mission Essential Only.” All Contractor personnel assigned to a government facility shall complete annual Antiterrorism (Level One) and Active Shooter training.

3.2.6 Program Unique Requirements

This SOW solicits program management support services that directly support the mission and production readiness for NAVAIR SV 2020, ALE, MAL-EIT and other Naval Aviation Maintenance and Logistics initiatives. The

Contractor shall support Naval Aviation and Logistics support programs, ALE IPT Leads, ALE functional management, functional requirements, and the functional certification process. The Contractor shall support the program support artifacts as defined by the acquisition lifecycle to include: Defense Business Systems (DBS) business process reengineering, portfolio management, problem statement development, analysis of alternatives, identification of program performance metrics, trade-off analyses, project planning, cost control, capability and functional requirements, systems engineering documentation, implementation strategy, sustainment and operations, and program performance data analysis.

The Contractor shall support the current NAVAIR ALE program, projects and systems as well as initiatives that will deliver Results Based Accountability (RBA) metrics. RBA metrics requirements will be specified in the individual task orders. Further, the Contractor shall support the logistics and maintenance capabilities of the functional Naval

Aviation Support Process (NASP), ALE, NAMS and related NOBLE concepts, including business rules, reporting strategies, sustainment requirements, and business processes.

The Contractor shall be familiar with DoD, DoN and NAVAIR policies and concepts including, but not limited to:

Federal Information Security Modernization Act (FISMA), Financial Improvement and Audit Readiness (FIAR), National Institute of Standards and Technology (NIST) standards, Risk Management Framework (RMF) for DoD

IT, Cyberspace Workforce Management, Federal Information System Controls Audit Manual (FISCAM), Functional Area Management (FAM), OPNAV N4 Program of Record (PoR) Strategy and other IT Enterprise

Initiatives, Program/Budget initiative System for Information Technology (PBIS-IT), Navy Enterprise Licensing agreements, Navy Information Dominance Approval process (NAV-IDAS), BPR and Mission Aligned Organization

(MAO). An understanding of these policies and concepts will be required to ensure the stability and continuity of the workforce when hiring personnel and during execution of this SOW.

The Contractor shall be ISO 9001:2015 certified and shall have obtained certification from an accredited Registrar approved by the International Accreditation Forum (IAF) or the ANSI-ASQ National Accreditation Board. The

Contractor shall be certified at the contract performance start date listed in Section F and shall maintain this certification throughout the duration of the contract.

The Contractor shall perform as a “Covered Government Support Contractor" (See DFARS 252.227-7013 and

DFARS 225.227-7025) which means the Contractor furnishes independent and impartial advice or technical assistance directly to the Government in support of the Government’s management and oversight of a program or effort rather than to directly furnish an end item or service.

DOD and DON IA Program outlined in Secretary of the Navy Instruction (SECNAVINST) 5239.3B, 'DON

Information Assurance Policy' and SECNAV M-5239.1, 'DON Information Assurance Manual,' apply to efforts under this contract. Contractor personnel providing support under this contract shall comply with all federal, DOD, DON, and NAVAIR IA policies. The Contractor shall comply with SECNAVINST 5510.30B and SECNAV M-

5510.30 to assure that the proper security investigation is conducted for those Contractor personnel performing services under this contract. The Contractor shall coordinate with the COR/TPOC to identify applicable positions.

3.3 Detailed Support

3.3.1 Program Management

3.3.1.1 Project Planning and Program Management Support

The Contractor shall provide project management support to manage the cost, schedule, and performance of this effort. The Contractor shall assign a single point of contact, also known as the Program Manager (PM), who shall work closely with the government lead.

The Contractor shall also assist the government in the execution of aviation logistics systems related IT program management functions to include identifying program scope, defining objectives, and developing the course of action to achieve defined acquisition milestones. This work is accomplish in accordance with DoD Instruction

5000.02 and 5000.75 requirements, including all phases of the Business Capability Acquisition Cycle (BCAC) for business systems requirements and acquisition.

The Contractor shall support the five BCAC phases as identified below:

Capability Need Identification

Business Solution Analysis

Business System Functional Requirements and Acquisition Planning

Business System Acquisition, Testing and Development

Capability Support

The Contractor shall:

3.3.1.1.1 Integrate with the government program management office to successfully support each phase of the project life cycle to monitor and report the status of software vendor projects.

3.3.1.1.2 Provide program and project management support to include: the application of program and project management concepts, processes, techniques for successful execution and delivery of ALE work product/capability artifacts.

3.3.1.1.3 Provide acquisition management support required to establish Business Systems Category II and III

Programs of Record (POR) and move the maintenance community in the direction of enterprise, net-centric, IT solutions.

3.3.1.1.4 Provide recommendations to the Integrated Product Team (IPTs) to achieve defined acquisition milestones through the coordinated delivery of defined products and processes.

3.3.1.1.5 Provide logistics management support to the Defense System Acquisition Framework. Assist in the development of DBS integrated plans, processes and documentation.

3.3.1.1.6 Support the Government’s DBS requirements management process, which includes stakeholder identification, requirements definition, development, testing, production, deployment and sustainment.

3.3.1.1.7 Assist in the development of the management plan and associated Project, Program and Portfolio (PPP) documentation (i.e. quality management plan, risk management plan, communications plan), which are utilized to execute the effort.

3.3.1.1.8 Assist in the development and provide support for the iterative change control process, including assessment and documentation. Derive Work Breakdown Structures (WBS) using approved requirements and other management planning and reporting methods and documentation, such as milestone charts, work packages, and associated tasks.

3.3.1.1.9 Prepare for and help the government execute program defined Program Management Reviews (PMRs) such as Preliminary Design Reviews (PDRs), Critical Design Reviews (CDR), Test Readiness Reviews (TRR), Release Readiness Reviews (RRR), and Sprint reviews with system developers and integrators when requested by the government.

3.3.1.2 Project Monitoring and Control

Throughout the project life cycle, the Contractor shall measure progress against plans, conduct reviews and quality audits, and provide regular project updates and status reports in accordance with the deliverables schedule. The

Contractor shall support the management of cost, schedule, risk(s)/issue(s), and resource plans, and realign and add resources, as necessary.

3.3.1.2.1 The Contractor shall assist the government with oversight and change control of other contracted efforts, such as development or integration and performance requirements for management and change control throughout the execution of the contract. This commencing with requirements identification and proceeding through design, development, integration, test and sustainment.

3.3.1.2.2 The Contractor shall assist in the preparation of corrective action plans when performance does not meet established parameters or is outside of the variance thresholds established during the planning phase.

3.3.1.2.3 The Contractor shall participate in and provide input to activities required to identify and resolve risks, issues, and internal/external dependencies.

3.3.1.2.4 The Contractor shall report the project management metrics to the government and report on variances during progress meetings and in monthly status reports, in accordance with the deliverables schedule.

3.3.1.3 Strategic Planning

The Contractor shall support strategic development work products that align with the guidance and initiatives set forth by NAVAIR SV2020, ALE, the OPNAV N411 Logistics Functional Area Manager (FAM), OPNAV N98

Requirements Officer, and other Echelon I and II level enterprise initiatives. This includes developing Aviation

Maintenance and related Logistics Strategic Plans and IT Roadmaps to support and defined strategies. The

Contractor shall support the Government’s project and program oversight of defined strategy execution and assist in the planning, development, documentation and implementation of plans and strategies to include:

3.3.1.3.1 Assist with documentation to support the development of logistics strategies with clear alignment to business mission and objectives that provides a clear way forward for afloat and ashore logistics maintenance and planning support.

3.3.1.3.2 Analyze gaps between current state and desired future state.

3.3.1.3.3 Assist with programmatic documentation to support the planning, implementation, and sustainment of ALE through the definition and creation of program artifacts supporting governance, rigor, cost and schedule efficiencies, and processes to transform the NAE to a streamlined and efficient logistics support capability.

3.3.1.3.4 Evaluate command level initiatives, portfolio governance, policy and compliance support, and internal logistics support business processes to recommend alignment of aviation maintenance requirements with the

OPNAV Program Objective Memoranda (POM) process.

3.3.1.3.5 Facilitate the implementation of results oriented programmatic support principles that enable the success of major command initiatives that include Business Process Reengineering, Data Center Consolidation, FIAR compliance, Cloud Computing, Application Rationalization and Enterprise Resource Planning (ERP), Activity

Based Costing and AIRSpeed. These solutions are designed to facilitate improved management effectiveness, enhanced productivity and increased efficiency.

3.3.1.4 Portfolio Management

The Contractor shall design, implement and operate, after government review and approval, an Enterprise Portfolio

PMO process by which the Government can continually and consistently evaluate, select, prioritize, budget, plan and manage the documentation of program investments. In addition, the Contractor shall:

3.3.1.4.1 Assist with the implementation and management of the ALE Portfolio Management processes and artifacts.

3.3.1.4.2 Participate in the development of various documents to ensure ALE processes and business rules are fully documented, integrated and supportive of mission requirements.

3.3.1.4.3 Conduct investment analysis and make recommendations regarding whether investments are aligned to the command’s strategic/business plan and priorities and are compliant with applicable laws, regulations, policies, and standards.

3.3.1.4.4 Conduct analysis of Aviation Maintenance and Logistics related Programs and Initiatives and submit draft recommendations, briefs, formal presentations and plan of action documents for approval by the Government

Requirements Owner.

3.3.1.4.5 Support the program office with implementation plans, processes and procedures of new functional capabilities and user requirements that align to the vision of an enterprise integrated solution set.

3.3.1.5 Project Planning and Support Management

The Contractor shall provide both administrative support and subject matter expertise in the gathering of information for the preparation and development of presentations to support team meetings, management reviews, logistics team reviews, audits and other requests for presentation/briefing information. Specially, the Contractor shall:

3.3.1.5.1 Track command action items from internal and external sources and coordinate with appropriate action officers and other directorates, echelons II and III, and industry partners to ensure dissemination of information as appropriate and track progress through completion.

3.3.1.5.2 Provide support in the preparation, scheduling and documentation of logistics meetings to include: Tactical

Maintenance and Operations (TMO), Product Lifecycle Management (PLM) and Product Data Management (PDM)

Program Management Reviews (PMRs), Naval Aviation Logistics Command Management Information System

(NALCOMIS) IPT, and Fleet Guidance Team (FGT) reviews, modification review meetings, maintenance engineering logistics reviews, critical parts reviews, affordable readiness initiatives, logistics documentation reviews, data calls, and conference calls or other directed program meetings, conferences, teleconferences, or technical coordination meetings or reviews.

3.3.1.5.3 Review and analyze draft Government instructions, notices, technical documents, and manuals, and provide revision recommendations for Government review and approval.

3.3.1.5.4 Support technical and business processes such as acquisition planning, financial reporting, engineering, solution fielding, strategic and operational planning, engineering, training, operations, risk assessment, and customer support.

3.3.1.5.5 Prepare presentations, charters, analysis, recommendations, correspondence, and plans of action and milestones. Preparation and development of presentations will range in scope from detailed in-house briefings to

Senior Executive briefings outside the supported organization.

3.3.1.5.6 Support the development of schedules and implementation plans that identify defined deliverables and project milestones, parallel and interdependent tasks where required, technical approaches and a description of anticipated solution results.

3.3.1.5.7 Provide administrative support for fleet maintenance initiatives, programs and directorate to include managing calendars and travel requirements, tracking training requirements, scheduling meetings, performing command specific data calls, and ordering required program supplies.

3.3.1.6 Risk Management

The Contractor shall develop, and upon Government review and approval, execute a risk management program that consists of: Risk Planning; Risk Identification; Risk Analysis and Risk Control. The Contractor shall be responsible for periodic inputs and updates to Risk Radar based upon direction from the Government project managers. The

Contractor shall establish processes such as risk qualification and quantification, and maintain tools such as Risk

Radar in support of the Government Risk Management function. The Contractor will participate in project reviews to evaluate the risks inherent in assigned projects and programs.

3.3.1.6.1 Assist the government in verifying the risks associated with projects using reliable performance measurement baselines, which include the entire scope of work, are consistent with project schedules, and have adequate resources assigned.

3.3.1.6.2 Perform qualitative analysis of risks and conditions and recommend prioritizing their effects on Project objectives, as well as measuring the probability and consequences of risks and evaluating their impact on Project execution. Support the government in the execution and maintenance of a Risk Management Program including the maintenance of a risk review schedule, execution of portfolio level risk reviews, preparation of a risk watch list, and the identification of cross-program/enterprise-level risks.

3.3.1.6.3 Conduct program/project risk assessments and prepare documentation containing the assessed prioritized risks.

3.3.1.6.4 Provide risk inputs in support of monthly ALE program, project, and IPT reviews.

3.3.1.7 Configuration Management

The Contractor shall support configuration management initiatives utilizing commercial best practices and tools. In support of the Configuration Management (CM) functions, the Contractor shall:

3.3.1.7.1 Establish, subject to Government approval, guidelines and practices for the operation of Configuration

Control Board (CCB). Prepare associated configuration management policies and procedures for Government review and approval.

3.3.1.7.2 Monitor and report software vendors’ compliance with established CM policies and procedures. Ensure

CM plans, CM charters, and documentation libraries align with PMO requirements.

3.3.1.7.3 Support the implementation and maintenance of project CM processes. Support services shall also include implementation, and operation services for CM (or program related) software tools.

3.3.1.7.4 Ensure a managed and documented discipline is in place to ensure configuration management, tracking, and monitoring of ALE requirements remain auditable using established baselines.

3.3.1.8 Financial Management

The Contractor shall assist in preparing and updating mandated financial…