NBO ERP SOW.doc

Statement of Work for

NAVAIR Navy Enterprise Resource Planning Business Office

1.0 Scope.

Navy Enterprise Resource Planning (ERP) is the Department of the Navy (DON) financial and supply chain system of record. Navy ERP streamlines the Navy's financial and supply chain functions and provides critical information which enables the Naval Air Systems Command (NAVAIR) programs to support budgets, milestone reviews and supply chain functionality. Navy ERP ensures statutory and regulatory policy compliance and enables mandatory external reporting. NAVAIR Navy ERP Business Office (NBO) is the primary location for NAVAIR Navy ERP expertise. The NBO provides a central point for resolution of NAVAIR Navy ERP requirements and serves as the Center of Excellence (COE) for issue resolution.

The NBO organization is comprised of the following areas: Business Solutions Management Support (functional expertise); Data Management (reporting and analytics); User Management (Customer Liaison Support); and NBO Operational Support (internal business operations). The Business Process Management (BPM) Team provides technical and functional expertise to ensure the Navy ERP solution supports NAVAIR Acquisition and Program Management, Financial Accounting, Inventory and Asset Management, and Workforce Management business operations requirements. The Data Management Team supports all aspects of business intelligence, to include reporting, analytics, and data management and warehousing. The team supports the planning, analysis, transformation, and migration of data into and out of Navy ERP and associated systems. The Customer Liaison Team (CLT) provides technical and functional expertise to ensure NAVAIR end-users have the appropriate access to Navy ERP systems. The CLT works collaboratively with BPM team members, stakeholders and end-users to manage Navy ERP system compliance requirements, to resolve issues and provide knowledge sharing for issues, work-arounds and instruction. The NBO Operations Team provides strategic planning and execution, resource management and technical program support to ensure NBO business operations are secure, effective, timely, efficient and in compliance with overarching policies. The Operations Team is designed to execute management-directed activities and complement and enhance work performed by the other NBO teams.

The objective of this Statement of Work (SOW) is to procure contractor support services to perform tasks within the scope established in this specification. This contract shall provide services and products to support the NBO. Services and/or products shall include: Business Solutions Management, Reporting and Analysis, User Management and NBO Operational Support.

2.0 Applicable documents:

Throughout the life of the contract, if any policy, instruction, or regulation is replaced or superseded, the replacement or superseding version shall apply. Updated documents can be found at http://doni.daps.dla.mil and / or http://directives.navair.navy.mil/index.cfm. The contractor shall review, exercise an understanding and ensure compliance of the regulatory documents listed below. The contractor is responsible for researching and complying with any additional regulations, policies, instructions etc. applicable to the task areas in which they are involved.

2.1 Department of Defense specifications

2.1.1 DOD 5220.22-M, National Industrial Security Program: Industrial Security Procedures for Government Activities, 01 AUG 2018

2.1.2 DODINST 5220.22, National Industrial Security Program (NISP), 01 MAY 2018

2.1.3 DOD 5500.7-R, including CH 1 – 7, Joint Ethics Regulations (JER). 17 NOV 2011

2.1.4 OPNAVINST 3432.1A, Operations Security, 04 AUG 2011

2.1.5 SECNAVINST 5211.5F, Department of the Navy (DON) Privacy Act Program 20 MAY 2019

2.1.6 SECNAVINST 5239.3C, Department of the Navy (DON) Cybersecurity Policy, 2 MAY 2016

2.1.7 SECNAV M-5239.1, Department of the Navy (DON) Information Assurance Manual, 01 Nov 2005

2.1.8 SECNAVINST 5510.30B, Department of the Navy (DON) Personnel Security Program (PSP) Instruction, 06 OCT 2006

2.1.9 SECNAVINST 5510.36B, Department of the Navy (DON) Information Security Program (ISP) Instruction, 12 JUL 2019

2.2 Department of Defense Standards -Reserved

2.3 Other Government Documents (e.g. NAVAIR Documents)

2.3.1 Federal Travel Regulation (FTR), Implements statutory requirements and Executive branch policies for travel by federal civilian employees and others authorized to travel at Government expense. The FTR is contained in 41 Code of Federal Regulations (CFR), Chapters 300 through 304.

2.2.1 NASPAXRIVINST 5510.15Q, Regulations Governing Admission to the Naval Air Station Patuxent River (NAS PAX RIVER), Webster Field Annex, and Navy Recreation Center (NRC) Solomons, Maryland, 07 MAR 2012

2.2.2 NASPAXRIVINST 12610.7H, PERSONNEL REPORTING PROCEDURES DURING EMERGENCY CONDITIONS, 06 Dec 2016

2.2.3 NAVAIRINST 5230, Official and Personal Use of Government Property – Voice, Video and Data Systems and Equipment, 13 AUG 2018

2.2.4 NAVAIRINST 12620.1 CH-1, Compressed Work Schedule, 23 OCT 2012

2.2.5 NAVAIRINST 5211.5A, Naval Air Systems Command Privacy Act Program, 10 NOV 2016

2.2.6 NAVAIRINST 5239.2A, CYBERSECURITY PROGRAM, 29 MAR 2018

2.4 Industry Documents – Reserved

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 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 maintain state-of the-art anti-virus software and ensure that all media are virus free when delivered. The Contractor shall be capable of Internet and LAN communications with the Navair Navy ERP Business Office Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with NAVAIR Navy ERP Business Office 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 95 percent of work will be performed at Government site and 5 percent of work to be performed at Contractor site. Government site includes Patuxent River, Maryland and Webster Field. 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.3 Contract Status reporting - The contractor shall prepare and submit the below data items in accordance with the Contract Data Requirements List (CDRL) and any associated attachments. All deliverable documentation should be formatted appropriately for printing purposes.

3.1.3.1 Monthly Progress/Cost and Tasking Hours Report (A001) - The contractor shall provide, electronically, a monthly labor, material and other direct cost matrix detailing reporting period, team/product sub-team (following Section 3.3 Detailed Support Requirements) and, in order, within each team/product sub team: contract line item number (if applicable); labor categories; employee names; awarded, current, cumulative and remaining labor hours; and awarded, current, cumulative and remaining labor dollars for each labor category. Footnotes are to be used to indicate reporting period of performance for subcontractor labor hours, roll off dates for named employees leaving, and start dates and names for new hires. The contractor shall also receive prior approval from the TPOC/ATPOC for excess hours, following the NBO Contractor Support Personnel Authorization process. The contractor shall provide electronically, a Monthly Material Report detailing materials billed during the period. The report shall reflect the item(s) or service(s) procured, description, cost (unit and total), source, date of procurement, date of TPOC/ATPOC concurrence for procurement, and purpose of material/service. Copies of receipts must be provided with invoices.

3.1.3.2 - Monthly Progress/Status Report (A002) - The contractor shall provide, electronically, a monthly narrative progress report detailing: 1) Work Performed (following Section 3.3 Detailed Support Requirements) and Significant Meetings; 2) Problems Encountered and Recommended Solutions; 3) Issues Requiring Government Action and 4) Recommendations for Process Improvements. The narrative should also include: data calls; status of efforts; progress made since the prior report; and milestones reached. If training is applicable to any delivery order the Contractor and the COR shall agree on a Plan of Action and Milestone (POA&M) to establish scheduled time frame. If reports and analysis is applicable to any delivery order the contractor and the COR shall agree on a POA&M for all testing to establish scheduled time frame. The contractor shall also provide an updated Production Interface Schedule Contact List quarterly.

3.1.3.3 - Trip Report (A003) - The contractor shall provide a Trip Report for each trip performed during the reporting period to include: traveler’s name; departure and return dates; purpose of travel; destination (city, state) from and to; destination POC (name, phone number); airfare, hotel, car rental, per diem, mileage, gas, other and total cost estimates; and trip findings. The contractor shall receive prior approval from the TPOC/ATPOC for travel to be performed, following the NBO Contractor Support Personnel Authorization process. The NBO Approved Travel Tracking Number issued during the approval process shall also be identified on the Trip Report.

3.1.3.4 Standard Operating Procedures (SOPs) and Desk Guides for NAVAIR NBO (A004) - The contractor shall create/review and maintain, electronically on an annual basis, SOPs and Desk Guides and store to the appropriate NBO collaboration site. The Government shall be given an opportunity to review and provide input to each SOP/Desk Guide on an annual basis at a minimum. The contractor shall support documentation of NBO processes as required. The Government will provide a listing of required documents and delivery dates for each identified SOP/Desk Guide. All required documents should be posted to the appropriate NBO collaboration site on or before the deliverable due date and in accordance with established processes.

3.1.3.5 Non-Disclosure Forms (A005) - The contractor will provide the TPOC/ATPOC and/or COR with a signed non-disclosure agreement from each individual contractor employee within two (2) business days of performance start.

3.1.3.6 - Contractor Employee Work Schedule (A006) - The contractor will provide the TPOC/ATPOC and/or COR with a consolidated work schedule for personnel within 30 days of contract start and annually thereafter.

3.1.3.7 – Exit Transition Plan (A007) - The contractor shall document the activities and roles and responsibilities, as well as the timetable, documentation and data, required for completing an orderly transition to the Government Organization and/or Contractor, following terminiation or expiration of the Contract regardless of the cause.

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 Monday through Friday and in accordance with NAVAIRINST 12620.1. Normal working hours are 8.5 hours (including a 30-minute lunch), from 0730-1600 each Monday through Friday (except on Government holidays). Some areas may require coverage until 1700 to support users at other NAVAIR locations. Services and staffing shall be provided at least 8 hours per day (during the 8.5 hour workday which includes the 30-minute lunch).

Core working hours for contractor personnel working either the basic or CWS work schedule are 0830 – 1500. This is the designated period each workday when all personnel must either be on duty or on leave. Non-Core time bands under the CWS work schedule are 0600 – 0830 and 1500 – 1800. This is the portion of the workday during which starting and ending times are established. Exceptions to core hours will be during limited periods of time, in which work schedules may be temporarily altered to support critical activities (such as Fiscal Year Close); otherwise the NBO will not require support prior to 0600 or after 1800.

Contractor work schedules shall be coordinated with the TPOC/ATPOC to ensure coverage during critical periods, coordination of tasks involving other contractors, coordination of coverage for tasking, and security compliance for buildings/areas where access is controlled. Work schedules may be required beyond the normal 40 hour work week dependent on critical periods. Limited periods of time may require the NAVAIR NBO to operate 24/7, seven days a week. This period usually is at Fiscal Year Close (September/October) with a timeframe lasting as long as two or more weeks, dependent upon Navy closing schedules and Navy ERP processing times and also during implementation of new Navy ERP releases. The TPOC/ATPOC will attempt to notify the contractor in advance of the requirement. All contractors shall comply with the requirements of the Fair Labor Standards Act and particularly with Section 7 regarding compensatory overtime.

3.1.4.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 time period: eight weekdays are worked at 9.5 hours each (which includes a 30-minute lunch), one Friday is alternately worked at 8.5 hours (which includes a 30-minute lunch), and one Friday 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. When a holiday occurs on the CWS “off” Friday, the employee’s day off will be Thursday, the day preceding the holiday.

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, the contractor agrees that any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable under this order and will not be reimbursed by the Government. Additionally, the CWS schedule shall not prevent the contractor from providing the necessary staffing and services coverage as required by the Government to the ACOR/COR. Any other alternate work schedules must be approved in advance by the TPOC/ATPOC and COR.

3.1.4.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.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 Contracting Officer.

3.1.5 Other Direct Costs:

3.1.5.1 Travel: Travel may include general and administrative expenses, but shall not include profit. Temporary travel to other locations in support of program tasking is required. If required, temporary travel locations include Washington D.C., Mechanicsburg, PA, China Lake, CA, Orlanda, FL, Cherry Point, FL, Jacksonville, FL, and San Diego, CA. 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. Title vests in the Government for all property acquired or fabricated by the contractor. Oversight and visibility of contractor-acquired property (CAP) is accomplished through reviews and audits of contractor business systems. Upon delivery and acceptance by the Government, and when retained by the contractor for use under a contract, the delivered CAP items become GFP and shall be added to the contract GFP attachment.The contractor shall transfer all materials not depleted to the COR by way of Material Inspection and Receiving Report (DD Form 250). Material costs may include general and administrative expenses but shall not include profit/fee.

3.1.6 Subcontractors and Consultants: 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 NBO 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 0007

- 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.9 Program Unique Requirements:

3.1.9.1 Government Provided Resources.

The Government will provide required access to corporate computer systems and other computer systems including authorizations, account numbers, and passwords as necessary for performance. The NMCI/NGEN contract provides device and network connectivity for software, hardware and applications. Software and applications must be tested and certified for execution within the NMCI/NGEN environment prior to installation. The contractor will be required to coordinate with NMCI/NGEN prior to installation of devices or software.

Performance under this task order will require IT resources including desktop computers, software, and peripherals that are included under the NMCI/NGEN 'seat management' concept. The Government will provide these resources for contractor personnel who are seated in Government provided spaces

The Government will provide other IT and telecommunications equipment and supplies (excluding general office supplies) required for job performance.

3.2 Security Provisions

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:

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.

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.

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.cnrc.navy.mil/publications/Forms/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. All CACs and identification badges issued to Contractor employees shall be returned to the Government Security Department at the Government site 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. Contractor personnel shall comply with NASPAXRIVINST 5510.15, ‘Regulations Governing Admission to the Naval Air Station, Patuxent River, Webster Field Annex and Navy Recreation Center Solomons, Maryland.

3.2.3.3 DD-254: 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 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.

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 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 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.5 Operations Security (OPSEC) ): The Contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed 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 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 officials 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 Control of Contractor Personnel: To ensure contractor employees supporting this contract are vetted and processed in compliance with Government security and safety policies, the contractor shall perform the following:

3.2.7.1.1 Contract Start - No later than five (5) business days prior to contract start, the contractor will provide the TPOC/TPOC with the following electronic information:

· Comprehensive list of all employees supporting the contract, and their start date

· Consolidated work schedule listing of all employees supporting the contract (CWS/Non-CWS, Start/End Times)

· Competed BASICS request form for access to the Government site

· Contractor Verification System (CVS) request form for Common Access Card (CAC) issuance

· SARR-N form

· Signed Non-Disclosure form

· Information Awareness (IA)/Cyber Awareness Challenge training certificate for each employee

3.2.7.1.2 During Contract Execution - After contract start and throughout the duration of the contract, the contractor will provide the Government TPOC and ATPOC written notification (email is acceptable) of new hires no later than five (5) business days prior to the employee start date. The contractor will provide the following information in the notification

· Employee Name

· Employee Start Date

· Company (include sub-contractor)

· Proposed work schedule (CWS/Non-CWS, Start/End Times)

· Competed BASICS request form for access to the Government site

· Contractor Verification System (CVS) request form for Common Access Card (CAC) issuance

· A non-disclosure agreement must be signed by the employee on or before his/her start date and a copy shall be provided to the TPOC/ATPOC within two (2) business days of employee performance start.

· Completed SAAR-N forms and IA/Cyber Awareness Challenge training certificates shall be provided to the COR by the contractor no later than five (5) business days prior to the employee start date for access to Government networks, systems and applications.

3.2.7.1.3 The contractor will provide written notification (email is acceptable) to the COR, ACOR, TPOC and ATPOC of departing employees as soon as possible. A minimum of two weeks’ notice is acceptable; longer may be more applicable in some cases to ensure adequate time for pass-down/knowledge transfer. The contractor shall follow the internal NBO process for processing of new hires and departing employees.

3.3 Detailed Support Requirements: This section provides the detailed support to be provided by the contractor. Approximately 90 percent of the tasks will be funded by Navy Working Captital Fund (NWCF), 10 percent by Operations and Maintenance, Navy (O&MN).

3.3.1 Technical and functional Support expertise to ensure the Navy ERP solution supports NAVAIR Acquisition and Program Management, Financial Accounting, Inventory and Warehouse Management, Asset Management, and Workforce Management business operations requirements. Functional areas supported by the NAVAIR Navy ERP Business Office teams include, but are not limited to, the following:

(list is not all encompassing and not prioritized)

In support of the functional areas identified above, the Contractor shall monitor and resolve user trouble calls, support data calls, develop and maintain process documentation, training materials and knowledge management articles, and develop, collect, and analyze business metrics. Support includes participation in NAVAIR and Navy ERP working groups and requires coordination and communication with principle command stakeholders, NAVAIR end users, and external stakeholders. Following are specific tasks required in support of Business Solutions Management:

3.3.1.1 Business Solutions Sustainment Support

3.3.1.1,1 Perform analysis and provide recommendations for resolution, and/or workarounds, for system deficiencies

3.3.1.1.2 Support the analysis and coordination of NAVAIR business needs and develop white papers, justification, and/or system engineering documents for new/enhanced functional capabilities

3.3.1.1.3 Evaluate Navy ERP requirements to determine impacts to NAVAIR business operations

3.3.1.1.4 Assess outstanding Navy ERP work items for relevance and impact to NAVAIR business operations to provide work prioritization recommendations in support of Navy ERP monthly/quarterly release planning

3.3.1.1.5 Perform and coordinate review with key NAVAIR stakeholders of Navy ERP functional design change documentation to ensure accurate and complete business requirements definition; consolidate NAVAIR feedback to Navy ERP functional team

3.3.1.1.6 Evaluate Navy ERP releases and coordinate activities to identify and minimize impacts of system changes on NAVAIR business operations

3.3.1.1.7 Coordinate quality assurance and test activities in support of changes to Navy ERP software, NAVAIR or Navy business process changes, and/or Navy ERP Software Upgrades to assess impacts to NAVAIR and recommend corrective actions

3.3.1.1.8 Identify test candidates to the NBO Test Manager via the provided tools, and ensure testing methods, test dates and test plans are in place for testing. Track status and record progress and results in the NBO provided tools or other format as necessary.

3.3.1.1.9 Perform analysis and provide recommendations for resolution or mitigation of risks related to Segregation of Duties conflicts

3.3.1.1.10 Support the development/maintenance of NAVAIR end user training documentation and activities to update/maintain the NAVAIR Navy ERP training environment (e.g., master data build and troubleshoot functional issues) for NAVAIR end user training

3.3.1.1.11 Maintain NAVAIR Business Process Rules

3.3.1.2 Production Operations Support 3.3.1.2.1 Support development and implementation of interface processes

3.3.1.2.2 Support research and resolution of issues discovered during interface processing.

3.3.1.2.3 Inform command stakeholders of batch or interface processing issues, resolution actions, and status

3.3.1.2.4 Work with command stakeholders to integrate and maintain the Navy ERP solution into Business Contingency Plans that can be invoked as needed in the event of production system downtime

3.3.1.2.5 Monitor the Navy ERP production schedule for job failures and deviations 3.3.1.3 Business Initiatives Support 3.3.1.3.1 Perform analysis to evaluate impacts of current and emerging internal and external business initiatives affecting NAVAIR business operations within the Navy ERP solution (e.g., Business Process Standardization, Audit Readiness, Cost Management, Material Acquisition and Management)

3.3.1.3.2 Support the implementation of process changes and/or Navy ERP capabilities in support of current and emerging internal and external business initiatives

3.3.1.3.3 Evaluate opportunities for NAVAIR utilization of Navy ERP capabilities to support continual process improvement activities

3.3.1.3.4 Perform assessment of future functionality deployments usability/applicability to the NAVAIR command (e.g., asset management, inventory management, warehouse management, material management, depot, supply deployments)

3.3.1.3.5 Participate in NAVAIR and Navy level working groups and facilitate collaboration among NAVAIR key stakeholders, other Navy Commands and Navy Process Owners to address business requirements supported by the Navy ERP system

3.3.1.3.6 Participate with the implementation and sustainment of processes to ensure full financial statement audibility

3.3.1.3.7 Support the Navy ERP Technical Upgrade and the subsequent move from SAP ECC 6.0 and SCM to SAP S/4 HANA Business Suite to include the development of test scenarios, execution of test scripts, and identification and resolution of issues or defects encountered during testing

3.3.1.3.8 Support the development, implementation and sustainment of business processes focused on capturing labor actuals (i.e., hours and cost execution) in Navy ERP

3.3.1.3.9 Support the integration of the Command’s property and inventory portfolios and functions into the Navy ERP solution

3.3.2 Reporting and Analysis Support to include reporting/analytics/dashboards, data warehousing, data integration, data mapping, data management, data governance, archiving, security, and metadata management. The Contractor shall also support the planning, analysis, transformation, and migration of reporting from systems (such as the Navy Data Platform (NDP), NAVAIR Warehouse Analytical Reporting System (WARS), etc.) to SAP HANA. The Contractor shall develop and maintain process documentation. Following are specific tasks required in support of Reporting and Analysis:

3.3.2.1 Business Intelligence Support

3.3.2.1.1 Analyze reports (Navy ERP delivered and local) to ensure data integrity and verify with appropriate Command representatives, that mandatory reporting (internal & external to the NAVAIR command) is functioning and accurate

3.3.2.1.2 Perform data retrieval as requested by NAVAIR customers; data retrieval may be in the form of standard Navy ERP provided reports or those arising from custom query development for data extraction and report generation from Navy ERP and/or NBIS

3.3.2.1.3 Participate in the creation of enterprise level reporting requirements and identify alternative reporting methods

3.3.2.1.4 Perform data reconciliation and data cleansing activities and recommend corrective actions for data integrity issues

3.3.2.1.5 Support the analysis and coordinate the use of Business Intelligence tools and data to enable data mining and reporting for NAVAIR users

3.3.2.1.6 Consult on the design and development of a data warehousing environment to provide reporting flexibility utilizing both ERP and non-ERP data sources

3.3.2.1.7 Support data calls using Navy ERP, NBIS, and/or other NAVAIR data sources

3.3.2.1.8 Support Navy ERP Business Intelligence Community of Excellence (BI CoE) activities

3.3.2.1.9 Support the consolidation and migration of legacy data warehouses and business intelligence reporting environments to a Self Service Business Intelligency (SSBI) solution on SAP HANA.

3.3.2.2 Data Management Support

3.3.2.2.1 Support NAVAIR in the management of NAVAIR Navy ERP master data to include entry of master data in coordination with competency personnel

3.3.2.2.2 Support review of data archiving strategies and develop recommendations for an enterprise approach

3.3.2.2.3 Analyze data extracts provided by Navy ERP NBIS, and/or other NAVAIR data sources to ensure data accuracy and completeness

3.3.2.2.4 Support the development of procedures that govern the use and release of NAVAIR Navy ERP data and/or NBIS data

3.3.3 User Management Support to include technical and functional expertise to ensure NAVAIR end-users have the correct access to Navy ERP systems to perform their job duties. The Contractor shall monitor and resolve user access trouble calls, support data calls and audit related activity, develop and maintain process documentation, and develop, collect and analyze user metrics. The following are specific tasks required in support of User Management:

3.3.3.1 Role Management Support

3.3.3.1.1 Assist users with the submission, tracking and reviewing of Access Enforcer requests and instruction of available tools in accordance with established NBO processes

3.3.3.1.2 Serve as the Information Assurance Manager (IAM) for the NAVAIR Navy ERP Business Office to ensure compliance with Information Security procedures and guidance

3.3.3.1.3 Support activities to maintain Governance, Risk, and Compliance (GRC) mitigations

3.3.3.1.4 Serve as the Government Security Manager (GSM)/ Facility Security Officer (FSO) delegate for Access Enforcer request processing and ensure access is granted based on DoD and Local Security policies

3.3.3.1.5 Assist command with role mapping validation and reviews

3.3.3.1.6 Monitor Segregation of Duties and coordinate with key stakeholders and users for resolution

3.3.3.1.7 Identify changes to Navy ERP roles in support of NAVAIR reorganizations, and ensure the changes are completed by the reorganization effective date

3.3.3.2 Training Support

3.3.3.2.1 Support Competency Designated Role Administrator (CDRA) training and the development of associated materials.

3.3.3.2.2 Develop, maintain and distribute documentation and reports to support NAVAIR Navy ERP training activities as needed via provided tools, processes and schedules

3.3.3.2.3 Support NAVAIR Navy ERP Training environment (e.g., coordination of master data build, troubleshoot problems, and issue training client assignments)

3.3.3.3 General User Support

3.3.3.3.1 Coordinate, review and distribute end user communications in accordance with established NBO processes

3.3.3.3.2 Coordinate, review and publish Knowledge Management articles for use by end users and Navy ERP Help Desk

3.3.4 NBO Operational Support to include project coordination and strategic planning, operational requirements and technical support, and program support for NBO daily activities, management-driven efforts and emerging initiatives. Support is designed to complement and enhance work performed by the other NBO teams. The Contractor shall assist with development and maintenance of process documentation, utilize established collaboration tools to ensure knowledge sharing amongst teammates, and apply continuous process improvement methodologies to their tasking approach. The following are specific tasks required in support of NBO Operations:

3.3.4.1 NBO Project Coordination and Strategic Planning Support 3.3.4.1.1 Assist with coordination, facilitation and execution of NBO management-level strategic activities, tasks, meetings and events

3.3.4.1.2 Coordinate, develop materials and facilitate actions for NBO leadership participating in senior-level briefings and meetings

3.3.4.1.3 Support NBO metrics collection, analysis and reporting in response to internal/external audits and data calls utilizing established processes

3.3.4.1.4 Develop and maintain Leadership management products and NBO tools 3.3.4.1.4.1 Maintain Leadership management tools weekly: hot list; operational calendar; etc.

3.3.4.1.4.2 Maintain organized workspace collaboration tools for NBO: SharePoint; Share Drive, etc.

3.3.4.1.4.3 Update and maintain the NBO web site to include coordination of content, posting, interface with NAWCAD 7.2 and perform annual review

3.3.4.2 Operational Requirements and Technical Support 3.3.4.2.1 Serve as a NMCI/NGEN POC, responsible for management of NMCI/NGEN hardware/software services and technical equipment, and analysis and coordination of technical requirements for Government and contractor resources supporting the NBO and for non-NBO resources physically located in the facility

3.3.4.2.1.1 Support NMCI/NGEN efforts, communicate impacts and issues

3.3.4.2.1.2 Coordinate hardware and software needs/upgrades via Move/Add/Change (MAC) request process for NBO employees utilizing NMCI/NGEN systems and tools

3.3.4.2.1.3 Plan for and ensure unassigned hardware assets receive maintenance software upgrades/pushes on a bi-weekly basis

3.3.4.2.1.4 Assist end-users with technical issues and escalate unresolved problems to higher authority as needed

3.3.4.2.1.5 Perform research and analysis to respond to NMCI/NGEN-related data calls as required

3.3.4.2.1.6 Maintain a close working relationship with NMCI/NGEN POCs that support other end users in the facility to effectively coordinate and/or communicate technical needs requiring action or awareness

3.3.4.2.1.7 Attend NMCI/NGEN POC meetings and other technical meetings as required

3.3.4.2.2 Identify and manage a listing of technical elements utilized to support facility resources following established processes (to include Government Furnished Equipment, hardware/software assets, network connections, phone jacks, space assignments, etc.)

3.3.4.2.3 Add/delete users and troubleshoot issues for internal NBO tools (email Distribution Lists, Share Drive, Share Point, etc.)

3.3.4.2.4 Coordinate with internal and external entities to support and/or troubleshoot facility infrastructure, equipment and space management

3.3.4.2.4.1 Liaison with NAWCAD Information Technology/Cyber Security Department (7.2) infrastructure personnel to support Voice and Audio/Visual requirements and on-going upgrade/maintenance/troubleshooting efforts

3.3.4.2.4.2 Liaison with Corporate Office Properties Trust (COPT): enter facility requests via Workspeed system; facilitate building/suite issues; and escalate issues as needed

3.3.4.2.4.3 Liaison with NAVAIR-7.10 (facilities management) to coordinate government-owned facility equipment improvements and needs

3.3.4.2.4.4 Disseminate facility-related communiques

3.3.4.2.4.5 Troubleshoot issues with equipment (telephones, video teleconferencing, copier, printers, fax, shredders, projectors, etc.)

3.3.4.2.4.6 Maintain space map

3.3.4.2.5 Execute Physical Security and Emergency Management program for the facility, ensuring compliance with NAS Patuxent River and other overarching safety/security policies

3.3.4.3 Program Support 3.3.4.3.1 Provide Office Reception and execute Visitor Control, Key Control and Emergency Response procedures (in compliance with Physical Security and Emergency Management program). Support required Monday through Thursday, 0700 – 1630 and Friday, 0700 – 1530 (excluding Government holidays and closures) for processing and vetting of visitors to the government facility.

3.3.4.3.1.1 If contractor is unable to provide support during the required hours for longer than a one-hour period, the Program Manager will notify the Government lead in a timely manner to collaborate on a solution

3.3.4.3.2 Perform on-boarding and off-boarding activities utilizing established processes for all personnel located in the facility

3.3.4.3.2.1 Coordinate, track, and report mandatory training requirements for NBO personnel

3.3.4.3.3…