SOW_CBO_Support_Draft_RFP_(Final).pdf

RECOMMENDED SECTION B ‐ CLIN STRUCTURE

CLIN 0001 LABOR ‐ Ceiling for CLINs 0002‐0005

CLIN 0002 NSP Labor – O&M

CLIN 0003 NSP Labor – RDT&E

CLIN 0004 NSP Labor – OP

CLIN 0005 NSP Labor – AP

CLIN 0011 OTHER DIRECT COST (ODC) Travel and Material – Ceiling for CLINs 0012 ‐ 0015

CLIN 0012 NSP ODC – O&M

CLIN 0013 NSP ODC – RDT&E

CLIN 0014 NSP ODC – OP

CLIN 0015 NSP ODC – AP

CLIN 0021 Technical Data for CLINS 0001 – 0005 and 0011 – 0015 NSP

Items 0001‐0005 – The Contractor shall provide SERVICES in accordance with the Statement of Work (SOW) as detailed in individual task orders. Each task order will include a SOW that details which tasks within the scope of the basic contract that are to be performed.

Items 0011‐0015 – 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 NAVAIR Clause 5252.242‐9515 “Restriction on The Direct Charging of Material.” ODC CLINs are Cost Reimbursable (no fee).

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

STATEMENT OF WORK FOR

AIR 6.0 LOGISTICS ACQUISITION CELL /

AIR‐6.8 CORPORATE BUSINESS OFFICE (CBO)

1.0 Scope: This Statement of Work (SOW) supports the mission of the Naval Air Systems Command (NAVAIR) AIR 6.0 Logistics Acquisition Cell and AIR 6.8 Corporate Business Office (CBO). The AIR 6.0 Logistics Acquisition Cell / AIR 6.8 CBO supports NAVAIR and other Department of Defense (DoD) Commands and Activities providing acquisition, management, implementation, sustainment services, and information technology (IT) for DoD customers. Current customers include AIR 6.0 (Logistics and Industrial Operations Group), Fleet Readiness Center (FRC) Headquarters and Depots, NAVAIR 6.0 financial activities, and other DoD entities.

Types of support to be provided under this requirement include acquisition management, acquisition planning and execution, administration, program management, systems engineering, process automation, financial management, software development/ maintenance, and support services. In the execution of these tasks, the Contractor shall ensure smooth integration of workflow and communication within the program office and externally with customers.

2.0 Applicable Documents: NOTE: Throughout the life of the contract, if any instruction or document referenced in section 2.0 is replaced or superseded, the replacement or superseding instruction or document shall be applicable to the requirements defined in this SOW.

2.1 Department of Defense 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.2 Department of Defense Standards.

The Contractor shall be responsible for researching and complying with any additional regulations applicable to the task areas in which they are involved.

2.3 Other Government Documents.

2.3.1 AIR‐6.8 Corporate Business Office (CBO) Program Operating Guide (POG), 16 April 2018

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 UNCLASSIFIED. The current operating environment required for this contract includes:

Microsoft Windows 10 Microsoft Project 2010 Microsoft Office Professional Plus 2010 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 Local Area Network (LAN) communications with the Government Customers. Contractor personnel shall be capable of maintaining real‐time communications, both voice and data transfer capabilities, with the Government Customers 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 74 percent of work will be performed at the Government site and 26 percent of work will be performed at the Contractor site located within a ten (10) mile driving vicinity of NAVAIR/NAWCAD, Patuxent River MD. Software Developers and Information Technology Specialists can meet the requirements of Paragraph 3.3 via telework; therefore, the ten mile driving vicinity does not apply to these labor categories. Additional opportunities for requirements of Paragraph 3.3 to be met via telework may be identified at the task order level. Telework, if approved, may occur outside of the ten mile driving vicinity.

Government site(s) include NAVAIR/NAWCAD Patuxent River, MD. Contractors performing on‐site support will be provided access to workspaces, telephones, printers, 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 Meeting 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 the UNCLASSIFIED level with the capacity to support a minimum of twenty (20) persons and have contractor furnished telephone and VTC capability as well as sufficient equipment to conduct meetings with presentations including compatible software as required in Paragraph 3.1.1. This support shall be provided within a ten (10) mile driving vicinity of NAVAIR/NAWCAD, Patuxent River MD.

3.1.3 Contract Status Reporting. The Contractor shall provide the following documentation.

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

CDRL A001 Monthly Progress and Financial Status Report

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

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

Some supported Government offices have flexibility to start as early as 0600 and end as late as 1800, Monday

– Friday.

3.1.4.1.1 Compressed Work Schedule (CWS): CWS is an alternative work schedule to the traditional five (5), 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 of time: eight (8) weekdays are worked at 9.5 hours each (which includes a 30‐minute lunch), one (1) weekday is alternately worked as 8.5 hours (which includes a 30‐minute lunch) and one (1) weekday is not worked by the employee. The result is 80 hours worked every two (2) 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 SOW 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 to the ACOR/COR.

3.1.4.1.2 Holidays: The Government observes the following holidays:

New Year’s Day, January 1 Martin Luther King’s Birthday, Third Monday in January President’s Birthday, Third Monday in February Memorial Day, Last Monday in May Independence Day, July 4

Labor Day, First Monday in September Columbus Day, Second Monday in October Veteran’s Day, November 11 Thanksgiving Day, Fourth Thursday in November Christmas Day, December 25

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

3.1.4.1.3 Installation Closure: When Federal facilities are closed by the Government, or 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 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 oversight 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.4.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.5 Other Direct Costs:

3.1.5.1 Travel: Temporary travel to other locations in support of program tasking is required. Temporary travel locations may include FRC Jacksonville, Jacksonville FL; FRC North Island, San Diego CA; FRC Cherry Point, Cherry Point NC, Lakehurst, NJ, and Crystal City, VA. This list is not all inclusive as locations may change over the life of the contract.

3.1.5.2 Material: All materials not depleted during the performance of this contract shall become Government property upon completion of this contract. The Contractor shall transfer all materials not depleted to the COR by way of Material Inspection and Receiving Report (DD Form 250).

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

3.1.7 Management of Contractor Personnel: The Government will neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances will 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.1.8 Transition Out Strategy

The Contractor’s overall transition out strategy shall be built around maintaining the mission of the AIR 6.0 Logistics Acquisition Cell / AIR 6.8 CBO and its customers 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 A002.

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

CDRL A002 Transition Out Plan

3.2 Security

3.2.1 Citizenship Requirements: Only U.S. citizens may perform under this contract. If the Contractor cannot find qualified U.S. citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request should include:

a. The individual's name, date, and place of birth, position title, and current citizenship.

b. A statement that a qualified U.S. citizen cannot be hired in sufficient time to meet the contractual requirements.

c. A statement of the unusual expertise possessed by the applicant.

d. A statement that access will be limited to a specific Government contract (specify contract number).

e. A statement that the Contractor has obtained an export license for the information required to perform the 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 shall initiate the Contractor’s Electronic Questionnaire for Investigations Processing (eQIP)), shall 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.

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. Instructions for processing the SAAR‐ N forms are available at: http://www.navsea.navy.mil/Portals/103/Documents/NSWC_Carderock/OPNAV‐ 5239‐14‐SAAR‐N.pdf.. SAAR‐N forms shall be submitted to the Contracting Officer’s Representative (COR), Government Technical Point of Contact (TPOC), or to the assigned Government Trusted Associate Sponsorship System (TASS) Trusted Associate.

3.2.3.2 Command Access Cards (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 NAVAIRINST 5510.15N Regulations Governing Admissions to the Naval Air Station, Patuxent River and Webster Field, Maryland. All CACs and identification badges issued to Contractor employees shall be returned to the Government Security Department at the Government site in accordance with NAVAIRINST 5510.15N Regulations Governing Admissions to the Naval Air Station, Patuxent River and Webster Field, Maryland following completion of the contract, relocation, or termination of an employee, or upon request from the Contracting Officer’s Representative. The Government will provide the Contractor access to Government facilities, as required, for performance of tasks under this contract.

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.

3.2.4.1 Marking: All information generated by the Contractor shall be properly marked. For Official Use Only information generated and/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: No information pertaining to this contract shall 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 the appropriate U.S. Government authority in accordance with DFARS clause 252.204‐7000.

Proposed public releases shall be submitted for approval prior to release through the servicing agency’s Public Affairs Office via the PCO.

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

All instances of loss, compromise, and 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 occurring.

3.2.4.4 Information/Data Handling: Information or data that the Contractor accesses shall be handled at the appropriate classification level, with 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 PCO of this contract for approval.

3.2.5 Operations Security (OPSEC): The Contractor shall comply with activity OPSEC program instructions, guidance, and contribute to organization‐level OPSEC efforts. The Contractor shall include OPSEC as part of its ongoing security awareness program and take all required activity OPSEC training. The Contractor shall protect identified critical information, sensitive unclassified information, and activities, which, if divulged, could further compromise classified or sensitive information or operations, or degrade the planning and execution of operations performed by the RO and Contractor in support of the mission.

While performing aboard NAVAIR 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.2.6 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/or 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 Government official’s direct 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.7 Program Unique Requirements

3.2.7.1 Physical Security: The Contractor shall be responsible for safeguarding all Government property provided for their use. At the end of each work period, all Government facilities, equipment, and materials shall be secured.

3.2.7.2 Performance Requirements: The Contractor shall be familiar with DoD, DoN, and/or NAVAIR policy and concepts including but not limited to IT Consolidation, Functional Area Management (FAM), Navy Networks, Navy Enterprise Licensing Agreements, Navy Information Dominance Approval Process (NAV‐IDAS), and Competency Aligned Organization (CAO). An understanding of these policies and concepts will be required to ensure stability and continuity of the workforce when hiring personnel and during execution of this Statement of Work.

The Contractor shall comply with Command Initiatives such as legacy application reduction, and shall be performed in accordance with DoD, DoN, and NAVAIR initiatives, standards, policies, and mandates such as Application Portfolio Management, Defense Business Transformation Guidance, Navy Enterprise Application Developer’s Guide (NEADG), Clinger Cohen Act (CCA), Federal Information Security Act (FISMA), Web Enablement, and 508 Compliance. Any systems/applications or tools that will reside on NMCI, Continuity of Services Contract (COSC), Next Generation Enterprise Network (NGEN) or run on these workstations must be certified for NMCI, COSC, NGEN and comply with NMCI, COSC, and NGEN policies.

3.2.7.3 Data Rights: For all technical data produced or delivered under this contract, the Contractor shall grant the Government rights, as per Defense Federal Acquisition Regulation (DFAR) 252.227‐7013 Rights in Technical Data‐‐Noncommercial Items. For all computer software produced or delivered under this contract, the Contractor shall grant the Government rights, as per Defense Federal Acquisition Regulation (DFAR) 252.227‐7014 Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation. This includes the source code (including Interface Description Language (IDL) / Web Service Description Language (WSDL) files and all required interops (technology that enables Common Object Model (COM) objects to interact with .NET objects and vice versa)), build scripts and procedures, install scripts and procedures, minimal data required to build, install, and start application, and executable code, which shall be Government property. Contractor shall flow these data rights down to all subcontractors and suppliers. These rights are IAW Federal Acquisition Regulation (DFARS) 252.227‐7014 (June, 1987), Rights in Data – General and Defense Federal Acquisition Regulation Supplement (DFARS) 252.227‐7020, Rights in Data – Special Works (DFARS) 252.227‐7021, Rights in Data—Existing Works.

3.2.7.4 Government Furnished Property, Equipment, and Information: The Government reserves the right to provide Government Furnished Property, Equipment, and Information on an as needed basis at the task order level.

3.2.7.5 Contractor Acquired Material/Property: The Contractor shall document the transfer of the materials and property in the monthly status report and appropriate Government documentation.

3.2.7.6 Organizational Conflict of Interest. The Government requires that a Contractor‐provided Organizational Conflict of Interest (OCI) Mitigation Plan (CDRL A003) be submitted within 15 days after contract award. All Contractor personnel working this contract must receive company sponsored OCI training within fourteen (14) calendar days after contract award.

CDRL A003 OCI Mitigation Plan

3.2.7.7 Non‐Disclosure Agreements: In the performance of the contract, the Contractor may have access to non‐public proprietary information. If the Government determines that the Contractor will have access to non‐public proprietary information at a task order level, then the Contractor shall require that any employee performing services under that task order sign a Non‐Disclosure Agreement (NDA). The NDA shall acknowledge the Contractor and employees’ duties and promise to comply with those obligations. A copy of the executed NDA shall be provided to the PCO and Government COR.

3.2.7.8 Disclosure of Information: Contractor employees shall not discuss nor disclose any information to which they are exposed during the execution of tasks to parties other than the originator of the information, authorized Government investigative personnel, the Contracting Officer, or COR personnel. Improper disclosure of sensitive information may be grounds for removal of contractor personnel. The Contractor shall provide the TPOC and COR a signed non‐ disclosure agreement (NDA) for each individual contractor employee before the employee begins performance, as required by individual task orders.

3.2.7.9 Training. The Contractor shall provide qualified personnel who are capable of assuming their duties at contract award. Training for contractor personnel shall be at the contractor’s expense. In the event the Contractor must attend training, the Contractor must coordinate training dates with the Government to ensure continuity of operations.

3.2.7.10 Quality Assurance. The Government shall evaluate the Contractor’s performance under this contract and orders in accordance with the Contract Surveillance Plan (CSP). The principal evaluator of Contractor work quality is the Government COR/ACOR in coordination with TPOC/ATPOC. This plan is primarily focused on what the Government must do to ensure that the Contractor has performed in accordance with the performance standards. It defines how the plan will survey, observe, test, sample, evaluate, and document the Contractor’s performance standards identified in the Contract and Orders.

3.2.8 Cybersecurity

3.2.8.1. Cybersecurity Plan

For Cybersecurity (CS) requirements see the Cybersecurity Plan (CP), Attachment [TBD]. Specific mentioned policies in the CS Plan can be accessed via the Cybersecurity Policy Chart at the following link:

http://iac.dtic.mil/csiac/ia_policychart.html

The Contractor shall be required to deliver a Program Cybersecurity Implementation Plan (CSIP) or Annex CSIP to address each of the sections of the Cybersecurity Plan (CP). The contractor shall demonstrate its understanding of the CP and describe how the requirement of each of the sections of the CP will be achieved by the contractor. Sections of the CP that are NOT applicable are required to be addressed.

The contractor shall describe why a particular section is not applicable. The final Program CSIP shall be in Adobe Acrobat format with a digital signature from the contractor cognizant authority.

If no approved Program CSIP currently exists between the contractor and the Government, then one must be created and submitted. If an approved Program CSIP already exists and sufficiently satisfies the CP requirements for the contract, then no new CSIP delivery is required. In such cases, the Contractor in consultation with the Government shall only submit a Contract Letter to the Government stating that all CP requirements are satisfied by the existing Program CSIP.

If CP requirements are NOT adequately addressed by the existing Program CSIP, then an update to the Program CSIP or a supplemental CSIP document referred to as an “Annex CSIP” shall be created to satisfy the CP requirements. An Annex CSIP shall address unique CP Section "G" Assessment and Authorization requirements if a system is being delivered under the contract and unique Section "Q" Software requirements if software is being delivered. These Program CSIP updates or Annex CSIPs shall be submitted on a semi‐annual (twice per year) basis in accordance with CDRL A011.

3.2.8.2 Cybersecurity System/Software Assurance Report

If a system or software is to be delivered to the Government then the Contractor shall address these requirements within the Cyber Sec System/Software Assurance Report (CDRL A012, Cyber Sec System/Software Assurance Report).

3.3 Detailed Support:

Funding of Functional Performance Requirements: Functional performance requirements – the function required to execute TO requirements – are outlined below in Section 3.3.1 through 3.3.7. The applicability of each functional performance requirement to funding types is indicated in the table below.

SOW # Description O&M AP OP RDT&E OTHER

3.3.1 Acquisition Management

3.3.1.1 Project Planning and Control X X X X X

3.3.1.2 Acquisition Risk Management X X X X X

3.3.1.3 Stakeholder Coordination X X X X X

3.3.2 Acquisition Planning and Execution

3.3.2.1 Requirements Management X X X X X

3.3.2.2 Procurement Planning and Documentation X X X X X

3.3.2.3 Acquisition Pre‐Award / Post‐ Award /

Modification Support

X X X X X

3.3.2.4 Action Item Tracking X X X X X

3.3.3 Acquisition Administration

3.3.3.1 Administration Activities X X X X X

3.3.3.2 Post Award Reporting X X X X X

3.3.3.3 Invoice Processing X X X X X

3.3.3.4 Contract Management Reviews (CMR) X X X X X

3.3.4 Program Management

3.3.4.1 Metric Analysis and Reporting X X X X X

3.3.4.2 Program Data Call Support X X X X X

3.3.4.3 Organizational Process Improvement X X X X X

3.3.4.4 Program Documentation X X X X X

3.3.4.5 Meeting Support X X X X X

3.3.5 Systems Engineering

3.3.5.1 Functional / Technical Requirements

Support

X X X X X

3.3.5.2 User Readiness Support X X X X X

3.3.5.3 DoD Software Compliance Support X X X X X

3.3.5.4 Configuration Management X X X X X

3.3.5.5 Acquisition Systems Engineering X X X X X

3.3.6 Process Automation / Help Desk / Security /

Share Point / .net Administration

3.3.6.1 Process Automation X X X X X

3.3.6.2 Help Desk X X X X X

3.3.6.3 Security X X X X X

3.3.6.4 Share Point and .NET Administration X X X X X

3.3.7 Financial Management

3.3.7.1 Business Financial Management (BFM) X X X X X

3.3.1 Acquisition Management (CLINS 0002, 0003, 0004, and 0005)

3.3.1.1 Project Planning and Control. The Contractor shall provide project management support throughout the acquisition process. The Contractor shall ensure that projects are conducted using the CBO defined processes. The Contractor shall monitor and support the acquisition process to help ensure that appropriate resources are being applied and that acquisition activities are progressing according to plan. The Contractor shall support the coordination of internal processes, plans, work products, schedule completion dates, and monitor status and completion.

3.3.1.2 Acquisition Risk Management. The Contractor shall provide risk identification and mitigation support throughout the acquisition process. The Contractor shall recommend corrective actions when project performance deviates from the plan. The Contractor shall document and provide alternatives for corrective actions and will close action items once corrective measures are completed.

3.3.1.3 Stakeholder Coordination. The Contractor shall coordinate and collaborate with relevant stakeholders throughout the acquisition process. The contractor shall identify, monitor, and coordinate stakeholder activities that include critical dependencies.

3.3.2 Acquisition Planning and Execution (CLINS 0002, 0003, 0004, and 0005)

3.3.2.1 Requirements Management Support. The Contractor shall solicit customer needs, expectations, and constraints for all phases of the acquisition process. The Contractor shall coordinate and consolidate requirements and assist in analysis, refinement, and validation activities. The Contractor shall also assist in managing requirement changes and assess relative impacts to acquisition project activities.

3.3.2.2 Procurement Planning and Documentation. The Contractor shall participate in procurement planning initiatives focused on acquiring products and services to support program goals and objectives. These services shall include, but are not limited to: the research of industry trends and capabilities, strategy alternatives and documentation, and requirements cost estimates as defined by DoD customers.

3.3.2.3 Acquisition Pre‐Award / Post‐Award / Modification Support. The Contractor shall ensure timely completion of project actions. The Contractor shall interface with the customer and other representatives throughout the acquisition process. The Contractor shall research requirements and present alternatives based upon scope and ceiling availability. The Contractor shall assist in the completion of various DoD compliance documentation (i.e., IT Approval, Determination & Findings, Justification & Approvals, etc.). The

Contractor shall draft Acquisition Packages, to include: SOWs, CDRLs, CLIN Structures, Plan of Action and Milestones, project plans, etc., and submit documentation to a CBO Government representative for action.

The Contractor shall monitor the funding process and interface with the customer’s business financial manager to expedite needs. The Contractor shall present alternatives for issue resolution and the risks associated with each contract action. The Contractor shall ensure data accuracy in all acquisition activities.

The Contractor shall utilize the Project Execution Management (PEM) toolset for applicable tasking.

3.3.2.4 Action Item Tracking. The Contractor shall maintain and update the contract action item tracking list and the non‐contract action item list. The Contractor shall participate in routine team meetings to facilitate timely and accurate action updates. The Contractor shall update the contract action item tracking list and coordinate with Government resource(s) to determine list order / priority adjustments. The contract action item tracker shall be maintained to ensure it provides current and detailed status on all planned contract actions and shall include completion dates for each major work area (need date, ARP completion, funds acceptance, etc.). The non‐contract action item list shall include effort description, assignee, due date, plan, and rolling status. The Contractor shall utilize the PEM toolset for applicable tasking.

CDRL A005 Acquisition Documentation

3.3.3 Acquisition Administration (CLINS 0002, 0003, 0004, and 0005)

3.3.3.1 Administrative Activities. The Contractor shall conduct cradle to grave contract administration activities. The contractor shall assign a Task Order Manager (TOM) for each acquisition project who will be knowledgeable on scope, ceiling, contract execution status, financial status, issues, risks, etc.

3.3.3.2 Post Award Reporting. The Contractor shall maintain and update the PEM toolset with all contract data. At a minimum, the Contractor shall update the following information for each contract action to ensure timely information availability:

3.3.3.2.1 Summary obligations versus expenditures, burn rates, fund depletion dates, hours worked, etc.;

3.3.3.2.2 Provide a snapshot moment‐in‐time and overall view of the financial position on each project (ceiling, obligations, customer / product activity, summary, etc.);

3.3.3.2.3 Provide a summary of planned versus actual obligations per fiscal and contract years;

3.3.3.2.4 Provide a program overview of DoD Service Participation, fiscal year contract costs, and cumulative program obligations;

3.3.3.2.5 Provide a program level summary of all service and software contracts.

3.3.3.3 Invoice Processing. The Contractor shall review all invoices for accuracy, noting any discrepancies found in the documentation for the COR’s approval. The Contractor shall facilitate timely workflow routing of invoices and deliver packages to appropriate team members. Invoice processing support shall include verification of labor hours, travel, ODCs, delivery submissions, etc. The Contractor shall coordinate with the vendor, COR, and Defense Financial Accounting Service (DFAS) POCs. The Government COR only is the party authorized to approve these invoices. The Contractor shall maintain and update the PEM toolset to:

3.3.3.3.1 Provide a snapshot of the team workflow tasks (from invoice receipt through COR signature) and completion dates (total turn times) for each invoice processed;

3.3.3.3.2 Summarize obligations versus expenditures, burn rates, fund depletion dates, hours worked, etc.

on a given contract;

3.3.3.3.3 Ensure travel charges are appropriate and aligned to approved labor charges;

3.3.3.3.4 Provide a snapshot of all discrepancies and resolutions throughout the invoice verification process to the Government.

3.3.3.4 Contract Management Reviews (CMR). The Contractor shall monitor and document cost, schedule, and performance of each project. Utilizing the PEM toolset, the Contractor shall provide a CMR briefing to report status for each project monthly. The Contractor shall perform reviews of all data to ensure accuracy, completeness, and consistency. Information provided shall include, but is not limited to, the following:

contract profile, used and available ceiling, obligated and expended dollars, funds depletion date(s), task/delivery order schedules, delivery assessment information, TPOC comments, planned versus actual financial information, trend analysis, risk / issue assessments, and alternatives.

3.3.4 Program Management (CLINS 0002, 0003, 0004, and 0005)

3.3.4.1 Metric Analysis and Reporting. The Contractor shall develop processes for Government approval and execute those approved processes for identifying, obtaining, managing, and reporting performance measures/ metrics pertaining to the program and related projects. The Contractor shall collect and report measurement results that are aligned with identified information needs and objectives. The measurement results shall provide insight into the effectiveness of project processes and CBO operations.

3.3.4.2 Program Data Call Support. The Contractor shall assist with analysis and response to ad hoc data calls.

Data call support shall include, but is not limited to: developing briefings such as Program Management Reviews (PMRs), IT, or other compliance documentation; Defense Contract Management Agency (DCMA) requests; Government audit actions; customer activity reports; DoD customer information requests; as well as various financial and data reconciliation requests. All contacts with personnel external to the CBO be coordinated through the COR.

3.3.4.3 Organizational Process Improvement. The Contractor shall maintain a strong process culture within the CBO. The Contractor shall define, implement, measure, and maintain effective and efficient practices that enable workload to be repeatedly executed with high levels of success. The Contractor shall update existing processes and build and develop new processes for Government approval.

CDRL A006, Organizational Process Improvement

3.3.4.4 Program Documentation. The Contractor shall update and maintain program documentation as the program evolves to respond to changing customer requirements and DoD, Navy, and NAVAIR policies. These documents define the policies and specific processes that will be utilized to maintain the program. Examples of required documentation include the AIR 6.8 CBO Program Operating Guide (POG) and underlying business processes. The Contractor shall maintain a comprehensive, auditable program office library, including reporting documentation, action items, document inventory database, etc.

3.3.4.5 Meeting Support. The Contractor shall coordinate and facilitate internal and external program office meetings, to include user conferences. Facilitation support shall include meeting preparation, execution, and documentation. The Contractor shall support the program office at meetings and document the proceedings in a summary report.

CDRL A007 Program Management Documentation

3.3.5 Systems Engineering (CLINS 0002, 0003, 0004, and 0005) All works created under this paragraph are subject to DFARs 252.227‐7020.

3.3.5.1 Functional / Technical Requirements Support. The Contractor shall work with the DoD user community and the CBO to develop user functional, technical, and performance requirements. The Contractor shall support the CBO in discussions and meetings. The Contractor shall review system technical and functional architecture issues and keep the CBO aware of implications and impact. The Contractor shall work with the users to develop and maintain testing schemes and databases, and plan and oversee toolset testing.

The Contractor shall coordinate and participate in Technical Interchange Meetings (TIMs) to review and resolve outstanding issues.

3.3.5.2 User Readiness Support. The Contractor shall participate in overall system technical and functional insertion and readiness planning. The Contractor shall review the overall implementation schedules and assist users in readiness determination. The Contractor shall provide an understanding, assessment, and planning for new capability.

3.3.5.3 DoD Software Compliance Support. The Contractor shall review and document Government instructions, directives, and mandates to assure toolset and CBO compliance. The Contractor shall maintain program software security posture and associated compliance documentation.

3.3.5.4 Configuration Management. Using commercial best practices, the Contractor shall support the CBO and customer configuration management initiatives. The Contractor shall maintain software and documentation configuration management databases, ensuring the artifacts are filed and available in a user‐ friendly manner and that the inventory database is updated as new data becomes available.

3.3.5.5 Acquisition Systems Engineering. The Contractor shall work with CBO customers to coordinate the capture of system and program requirements in sufficient detail to enable the determination of most suitable acquisition strategy(s) and creation of applicable acquisition packages. The Contractor shall perform the following activities:

• Translation of program and system / sub‐system requirements into executable requirements document(s);

• Identification of most suitable acquisition strategy options;

• Market research to establish the availability of products and vendors which can meet potential needs of the customers;

• Preparation of the acquisition packages with all needed documentation to acquire material and/or services to satisfy approved customer requirements in a timely, efficient manner and at the most reasonable cost to the Government; and

• Coordination of Government and industry interactions to ensure both parties have a common understanding of Government requirements and industry technical capabilities and limitations.

The Contractor shall coordinate with technical and programmatic staff in understanding the project and system related requirements including, but not limited to, system performance and material requirements, system integration requirements, system sustainment and maintenance requirements, and program cost and schedule requirements. The Contractor shall analyze gathered requirements and work with appropriate stakeholders to identify any gaps and obtain necessary data from various specialty engineers required for package completeness.

CDRL A008 System Engineering Documentation

3.3.6 Process Automation / Help Desk / Security / Share Point/ .net Administration (CLINS 0002, 0003, 0004, and 0005) All works created under this paragraph are subject to DFARs 252.227‐7020.

3.3.6.1 Process Automation: The Contractor shall provide Information Systems services that include software development and maintenance to support and extend existing business practices including: pre‐ award processing, post‐award processing, administrative functions, and analytics. These services shall include the planning, design, development, testing, documentation, integration, transition, training, support, providing all necessary documentation (CDRL A009), and implementation efforts necessary to fully implement solutions in .NET, SharePoint, and Qlik Sense environments. The Contractor shall coordinate with AIR 7.2 IT and industry on technology, toolsets, IT security, etc. to ensure the CBO remains current with NAVAIR IT policies and solution direction(s). The Contractor shall migrate CBO solutions to Government approved architecture(s). The Contractor shall deploy and support toolsets to CBO customers.

CDRL A009 Toolset Artifacts

3.3.6.2 Help Desk. The Contractor shall perform CBO Help Desk operations. The Contractor shall coordinate with the IT Administrator in supporting the Help Desk application and Help Desk Service Request Process, including vetting needs and providing development support for fixes and enhancements.

3.3.6.3 Security. The Contractor shall support all needed software security processes including, but not limited to, Security Assessments and Security Technical Information Guides (STIGS) to implement and maintain Software Applications in all directed computer environments.

3.3.6.4 SharePoint and .NET Administration. The Contractor shall:

3.3.6.4.1 Maintain and check the overall health, functionality, and administration of site collection to include moving/copying the sites;

3.3.6.4.2 Ensure site(s) are backed up and can be restored in an efficient manner;

3.3.6.4.3 Monitor disk space usage through the built‐in reports for each site collection. Analyze and report usage and activity;

3.3.6.4.4 Monitor trends (e.g. site usage and growth, disk space usage and growth);

3.3.6.4.5 Maintain permissions;

3.3.6.4.6 Regularly review events and messages reported in Event Viewer and Performance Monitor. Clean‐ up, maintain, and configure accounts and sites;

3.3.6.4.7 Set alerts and enforce CBO and NAVAIR policies;

3.3.6.4.8 Regularly monitor the CBO site usage;

3.3.6.4.9 Maintain additions, deletions, and modifications to the CBO lists and their associated workflows, input forms, and reports;

3.3.6.4.10 Ensure changes to the CBO capability follows CBO software enhancement policies (in accordance with CBO program operating guide);

3.3.6.4.11 Maintain all CBO documentation (e.g. list architecture, workflows, table content, design documents, user manuals, training documentation, interface documentation, capabilities used, additional tools used in development etc.);

3.3.6.4.12 Monitor and present alternatives to the CBO tools and NAVAIR’s implementation as it impacts the

CBO;

3.3.6.4.13 Coordinate with the CBO developers to ensure new capabilities don’t introduce unnecessary risk to the current implementation(s); and

3.3.6.4.14 Coordinate with staff to ensure proper education needs are satisfied and users know how to utilize the CBO implementation.

3.3.7 Financial Management. The Contractor shall have a working knowledge of NAVAIR / NAWCAD budgetary and financial policies, methods, procedures, and regulations to forecast program funding activities with different sources and types of funding to identify, analyze, and evaluate funding problems and present alternative solutions. The Contractor shall have a working knowledge of the Navy Enterprise Resource Planning (ERP) system. (CLINS 0002, 0003, 0004, and 0005)

3.3.7.1 Business Financial Management (BFM). The Contractor shall:

3.4.7.1.1 Provide Planning, Programming, and Budget System alternatives.

3.4.7.1.2 Create alternatives for budget documents for Government review/approval.

3.4.7.1.3 Collect, compile, and analyze financial, project, and cost data for incorporation into team work plans, data calls, financial addendum, budgetary support documentation, and other financial sheets.

3.4.7.1.4 Develop financial production reports for review at financial production reviews by senior leadership.

3.4.7.1.5 Compile, correlate, and consolidate budget estimates for out‐year requirements to include tracking of requirements, controls, and developing spends plans based on validated requirements.

3.4.7.1.6 Project cost estimates based on revised schedules in order to incorporate cost savings strategy into the normal budget process.

3.4.7.1.7 Utilize the Navy Enterprise Resource Planning (ERP) system to track and reconcile program obligations, expenditures, and fund status.

3.4.7.1.8 Maintain program financial tracking databases based on information provided through Navy ERP.

3.4.7.1.9 Track status of obligations, expenditures in detail by year, appropriation, and target program or any other logical break so that data can be easily updated as changes occur or are reported to management.

3.4.7.1.10 Track detailed financial status of assigned Navy ERP program resources.

3.4.7.1.11 Provide support on fiscal year budget planning, program execution, and out‐year planning to include development and preparation of funds execution documents through Navy ERP.

3.4.7.1.12 Compile, correlate, and consolidate budget estimates for Future Years Defense Program requirements for Government Approval to include tracking of requirements and controls, and developing spend plans based on validated requirements.

CDRL A010 BFM Documentation

3.3.8.13 Contract Deliverables: (CLIN 0021)

Contract deliverables may be submitted in Contractor format unless otherwise specified in the CDRL.