Att 01- ASI TPMS SOW.docx

STATEMENT OF WORK FOR AIRBORNE SYSTEMS INTEGRATION (ASI) TECHNICAL/PROJECT MANAGEMENT SUPPORT (TPMS)

1.0 Scope.

As the organic Lead Systems Integrator® (oLSI®) for the Naval Air Warfare Center Aircraft Division (NAWCAD), Webster Outlying Field (WOLF) operates under a product-based business model whereby NAWCAD WOLF civilians lead and manage the execution of the requirements for defense weapon systems programs with combined Government-Industry teams. Using this oLSI® approach, the Government maintains control of intellectual property and data rights, enabling WOLF to rapidly adapt solutions to the dynamic needs of the warfighter.

The NAWCAD WOLF Airborne Systems Integration (ASI) Division provides the rapid insertion and transition of advanced technologies, systems, sensors, and weapons to enable Programs of Record (PoRs) to successfully execute and deliver the direct insertion of capabilities to meet urgent fleet needs. The ASI Division, operating under the oLSI® model, has requirements for Technical/Project Management Support (TPMS) at the technical/project and Division levels to successfully fulfill the ASI Division mission.

The purpose of this Statement of Work (SOW) is to provide technical Project Management (PM), data management, and acquisition support for ASI TPMS. This includes providing technical support throughout the initiating, planning, executing, monitoring, and closing phases of projects in addition to providing data management support for the Division planning, performance, reporting, data analytics, metrics, and best practices that can be repeatedly executed with high levels of success. This requirement directly supports multiple major defense acquisition programs, other acquisition category designations, and other defense weapons systems to include, but not be limited to, VH-92A Presidential Helicopter; Naval Air Systems Command (NAVAIR) Airborne Strategic Command, Control, and Communications Program Office E-6B aircraft; NAVAIR Unmanned Carrier Aviation Program Office; Counter Uncrewed Systems; NAVAIR V-22 Joint Program Office; and Naval Sea Systems Command Integrated Warfare Systems Program Executive Office.

2.0 Applicable Documents.

2.1 Department of Defense (DoD) Specifications.

2.1.1 DoD National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulation Part 117, NISPOM Rule.

2.1.2 DoDM 5200.01 Vol. 2, Marking of Classified Information, Change 4, 28 Jul 2020.

2.1.3 SECNAVINST 5510.36B, Department of the Navy Information Security Program, 12 Jul 2019.

2.1.4 DoDI 5200.48, Controlled Unclassified Information (CUI), 6 Mar 2020.

2.1.5 DoDD 5400.07, DoD Freedom of Information Act (FOIA) Program, 5 Apr 2019.

2.1.6 DoDI 5230.24, Distribution Statements on Technical Information, 10 Jan 2023.

2.1.7 SECNAVINST 5510.30C, Department of the Navy Personnel Security Program, 24 Jan 2020.

N00421-27-R-1008

Attachment 01 – Statement of Work (SOW)

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

2.1.9 DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT).

2.1.10 DoDD Type Memorandum (DTM) 08-027, Security of Unclassified DoD Information on Non-DoD Information Systems, Change 1, 16 Sep 2010.

2.1.11 SECNAV M-5216.5 CH-1, Department of the Navy Correspondence Manual, 16 May 2018.

2.1.12 DoDD 7045.14, The Planning, Programming, Budgeting, and Execution (PPBE) Process, Change 1, 29 Aug 2017.

2.2 DoD Standards.

2.2.1 DoD 7000.14-R, Financial Management Regulations (FMR), Volume 1-16, Mar 2024.

2.3 Other Government Documents.

2.3.1 NIST Special Publication (SP), 800-53A Rev. 5, Assessing Security and Privacy Controls in Information Systems and Organizations, 25 Jan 2022.

2.3.2 National Security Decision Directive 298, dated 22 January 1988 Public Law 100-235, Section 3(d)(4).

2.3.3 The Joint Travel Regulations (JTR), 1 Jan 2025. 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 Information Technology (IT) environment through the security classification of Secret as specified on the DD Form 254, Contract Security Classification Specification Form, Attachment 02. The current operating environment required for this TO includes:

Microsoft Windows 2011 or greater Microsoft Project 2016 or greater Microsoft Office Professional Plus 2016 or greater Microsoft Visio 2016 or greater Adobe Reader (most current release) Adobe Acrobat Pro (most current release) Adobe Photoshop (most current release) Internet access Flank Speed 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 ASI Division. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with the (ASI Division during working hours whether at contractor work site or on travel.

3.1.2 Work Location, Facilities, and Telework.

3.1.2.1 Work Location. Approximately 85% of work will be performed at Government site and 15% of work to be performed at contractor site.

3.1.2.1.1 Government Site Requirements. Government sites include NAWCAD WOLF, St. Inigoes, MD (estimated at 81% of the 85%) and Naval Air Station Patuxent River, Patuxent River, MD (estimated at 19% of the 85%). Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network access including web servers and applicable databases or other applications necessary to carry out assigned tasks.

3.1.2.1.2 Contractor Site Requirements. The Contractor shall provide its own support facilities needed to perform the tasking of this TO within 50 ground transportable miles of NAWCAD WOLF, St. Inigoes, MD in order to satisfy the daily support and management operations of this TO. The Government will not assume responsibility to retain the facility or take control of the title after the TO is completed. The contractor shall have occupancy of this facility by the base year Period of Performance (PoP) start date specified in Section F.

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 Secret with the capacity to support a minimum of five persons. The meeting space shall have contractor-furnished telephone and Video Teleconference (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 at the contractor facility within 50 ground transportable miles of NAWCAD WOLF.

3.1.2.3 Telework/Remote Work.

The Contractor may allow contractor employees to telework in accordance with (IAW) the information in paragraph 3.4. The Contractor may utilize alternate worksites/locations to telework to support continued performance of SOW tasks IAW company policy. When using telework, the Contractor remains responsible for TO performance and compliance with any applicable cost accounting standards and contract cost principles/procedures.

Telework is defined as an alternative workplace arrangement under which a position performs the duties and responsibilities of the assigned position and other authorized activities from an approved alternative worksite but is required to report to the agency’s worksite on a regular and recurring basis. Telework can be either routine or situational. Routine telework is performed from an alternative worksite on regularly scheduled telework day(s), whereas situational telework is authorized on a case-by-case basis as the need arises or when opting for unscheduled telework and may be authorized for routine teleworkers in such circumstances on regularly scheduled in-office days.

Telework eligible positions require routine on-site performance of at least two days per week. On-site performance may be required outside of routine on-site performance days and shall be provided when requested by the Contracting Officer’s Representative (COR).

In the event that telework tools become unavailable while working off-site, the Contractor shall require positions defined as telework to report on-site in order to access the tools required for performance of this TO.

At any time during TO performance, the COR may determine that a position is no longer eligible for telework by providing a notice 30 calendar days in advance so the Contractor can address changes needed to support mission requirements.

3.1.3 TO 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 IAW the Contract Data Requirements List (CDRL). The report shall include work accomplished since submittal of the last report, both monthly and cumulative work hour labor costs expended by labor category, and material and travel costs. (CDRL A001)

3.1.3.2 Organizational Conflicts of Interest (OCI) and Non-Disclosure Agreement (NDA) Status Certification. The Contractor shall report OCI Mitigation Plan compliance and compliance status changes. (CDRL A002)

3.1.4 Work schedule to include Compressed Work Schedule (CWS), 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 each day (including a 30-minute lunch break), from 0730 to 1600 each Monday through Friday (except on the legal holidays as 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 CWS. CWS is an alternative work schedule to the traditional 5 8.5-hour workdays (which includes a 30-minute lunch break) worked per week. Under a CWS schedule, an employee completes the following schedule within a 2-week period of time: 8 weekdays are worked at 9.5 hours each day (which includes a 30-minute lunch break), 1 weekday is alternately worked at 8.5 hours (which includes a 30-minute lunch break), and 1 weekday is not worked by the employee. The result is 80 hours worked every 2 weeks, with 44 work hours 1 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 TO, any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this TO 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 COR/Alternate Contracting Officer’s Representative (ACOR).

3.1.4.1.2 Holidays. The Government observes the Federal holidays identified on the Office of Personnel Management (OPM) website: https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/. With the exception of the events in paragraph 3.1.4.1.3 below, the Contractor is permitted to observe Federal holidays IAW 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 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 (KO) must concur with any determination that work being performed by contractor personnel is mission essential.

3.1.5 Other Direct Costs (ODCs). Working Capital Fund (WCF); Procurement (PROC); Operations and Maintenance (O&M); Research, Development, Test & Evaluation (RDT&E); Shipbuilding and Conversion, Navy (SCN); Foreign Military Sales (FMS); and Non-Department of Defense (Non-DoD).

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. Temporary travel locations are expected to include Continental United States (CONUS) locations (to include the District of Columbia (D.C.)) and Outside the Continental United States (OCONUS) locations to include Alaska, Canada, Hawaii, and the U.S. Territories. This list is not all inclusive as locations may change over the life of the TO. The COR/ACOR shall approve all travel performed in support of this TO prior to the commencement of the travel and all travel shall result in a trip report. (CDRL A003)

3.1.5.1.2 Synchronized Pre-Deployment & Operational Tracker (SPOT). The Contractor may travel to locations that require the use of SPOT. IAW Clauses 252.225-7040 and 5152.225-5908, SPOT enables the validation of Contractors Authorized to Accompany the Force (CAAF), their authorization and eligibility for access to specific DoD facilities, and their eligibility for specific Government Furnished Support (GFS). The Contractor shall initiate a Letter of Authorization (LOA) for each prospective traveler. The Contractor shall use the SPOT link https://spot.dmdc.mil/privacy.aspx) to enter and maintain data with respect to traveling/deployed personnel and to generate LOAs.

3.1.5.1.2.1 LOA. The KO will provide an LOA for official travel OCONUS, when applicable, in support of the TO. The LOA will identify local authorizations, privileges, etc. as specified by DoD requirements. All defense contractor employees working under this TO shall carry an LOA with them, when applicable, at all times while deployed OCONUS.

3.1.5.2 Material. Incidental material will be required in the performance of this TO, and all incidental material purchases shall be IAW CTXT-242.9520, Procedures and Approvals Required Prior to Incurring Direct Material Costs. All materials not depleted during the performance of this TO shall become Government property upon completion of this TO. The Contractor shall transfer all materials not depleted to the COR by way of a DD Form 250, Material Inspection and Receiving Report. Material costs may include general and administrative expenses but shall not include profit/fee. (CDRL A004)

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

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 actions that give the perception of personal services.

3.1.8 Transition-Out Plan.

The Contractor’s overall transition-out plan shall be built around maintaining the mission of the ASI Division with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Prior to the termination or expiration of the TO, 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 IAW CDRL A005.

̶ 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 Technical Direction Letters (TDLs). When necessary, technical direction or clarification concerning the details of specific tasks set forth in the TO will be given through issuance of written TDLs. TDLs will not, in any manner, alter the scope of the TO. For further direction see HTXT.242-9502, Technical Direction (Variation) in Section H of the TO. The Contractor shall prepare and deliver a COR Management Report for TDLs IAW CDRL A001.

3.2 Security.

3.2.1 Citizenship Requirements. Only U.S. citizens may perform under this TO, unless waived by the Government. 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 on the TO.

3.2.2 Investigative Requirements.

Unclassified: All contractor personnel must be eligible to perform Non-Critical Sensitive work as defined by SECNAVINST 5510.30C, Department of the Navy Personnel Security Program. All contractor personnel are required to have a favorably adjudicated Tier-3 investigation from the OPM. The Contractor shall submit a request for personnel security investigation to the Government Security Office. The Government Security Office shall initiate the contractor employee's Electronic Questionnaire for Investigations Processing (eQIP) and shall perform a preliminary screening of the contractor employee'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 employee access to Government facilities and information and may prohibit the contractor employee from performance of sensitive duties for failure to provide requested information or when derogatory or adverse information is present on the contractor employee's eQIP. In such cases, the contractor employee may not perform on the TO.

Classified: All contractor personnel shall maintain security clearance eligibility commensurate with the level of classification of the work performed as annotated in the TO’s DD Form 254, Contract Security Classification Specification Form. Contractor personnel shall require access to classified information in performance of this TO up to and including Secret facility level, with a safeguarding level of Secret. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated IAW National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulation Part 117, NISPOM Rule. 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 TO.

3.2.2.1 Contractor Personnel Labor Category Security Requirements. The personnel listed below shall have the appropriate DoD Security Clearance Level or Interim Clearance IAW the chart below. All other personnel shall have the ability to obtain a Secret clearance or Interim Clearance within 60 business days of TO award.

LABOR CATEGORY

LEVEL

General and Operations Manager (Program Manager), BLS SOC 11-1021 (Key)

Senior

Secret

Upon Award

3.2.3 Common Access Card (CAC)/Public Key Infrastructure (PKI) and System Authorization Access Request (SAAR).

3.2.3.1 SAAR. All contractor personnel requiring access to Government IT systems shall have an approved DD Form 2875, System Authorization Access Request (SAAR) form on file and complete required Annual Information Awareness Training. New employees must submit their SAAR forms within 30 business days of their first day of work. SAAR forms shall be submitted to the COR, Government Technical Point of Contact (TPOC), or to the assigned Government Mission Partner Identity, Credential, and Access Management (MP ICAM) Trusted Associate (TA).

3.2.3.2 CAC/Local Badges. Contractor CACs and facility-specific identification badges will be issued by the Government to on-site contractor personnel and shall be visible at all times while personnel are at the Government site. The Contractor shall furnish all requested information required to facilitate issuance of identification badges. All CACs and identification badges issued to contractor employees shall be returned to the TA following completion of the TO, relocation or termination of an employee, or upon request from the COR/Procuring Contracting Officer (PCO). The Government will provide the Contractor access to Government facilities, as required, for performance of tasks under this TO.

3.2.3.3 DD Form 254. The Contractor shall comply with security requirements specified in the DD Form 254 attached to this TO. 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 (CUI); Legacy For Official Use Only (FOUO); Covered Defense Information (CDI)). Distribution is authorized to the Requiring Office’s Organization and supported Activity only. Other requests for deliverables under this TO shall be referred to the TPOC/COR of this TO 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 CUI and to control distribution of CUI IAW National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulations Part 117, NISPOM Rule and SECNAVINST 5510.36B, Department of the Navy Information Security Program. If the work is performed at the Government's facility, the Contractor shall comply with that facility’s information and security policies.

All contractor facilities shall provide an appropriate means of storage for CUI and materials. All CUI including legacy FOUO and CDI (meeting the definition DFARS Clause 252.204–7012, Safeguarding Covered Defense Information and Cyber Incident Reporting) generated and/or provided under this TO shall be marked and safeguarded as specified in DoD Instruction 5200.48, Controlled Unclassified Information (CUI) available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF.

Any product containing CDI shall be assigned a distribution statement (distribution statements B through F) using the criteria set forth in DoDI 5230.24, Distribution Statements on Technical Information and have this statement displayed per DoDI 5230.24, Enclosures 3 and 4.

Distribution is authorized to the Requiring Office's Organization and supported Activity only. Other requests for deliverables under this TO shall be referred to the TPOC/COR of this TO for approval.

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

Distribution Statement (Insert Appropriate Letter and Authorization Title), (Insert Appropriate Reason Category) (dated – (Date of Distribution Authorization)). Other requests shall be referred to: Commander, Naval Air Systems Command, Attn: ASI TPMS COR, 17800 Moll’s Cove Road, St. Inigoes, MD 20864.

3.2.4.1 Marking. All information generated by the Contractor shall be properly marked. Classified information shall be marked IAW DoDM 5200.01, Vol 2, Marking of Classified Information. CUI, including legacy FOUO information generated and/or provided under this TO, shall be marked IAW DoDI 5200.48, Controlled Unclassified Information (CUI). Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings IAW DoDI 5230.24, Distribution Statements on Technical Information and program Security Classification Guidance.

3.2.4.2 Public Release. Any CUI pertaining to this TO shall not be released for public dissemination, including posting to any social media sites such as Facebook or X (formerly known as 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 through ASI TPMS COR, 17800 Moll’s Cove Road, St. Inigoes, MD 20864.

3.2.4.3 Loss, compromise, and/or electronic spillage of classified information or CUI. All instances of loss, compromise, and electronic spillage of classified information or CUI shall be reported to the COR, TPOC, and Government Security Office within 72 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 TO. The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. This program may include Information Assurance (IA) and Communications Security (COMSEC). The OPSEC program shall be IAW National Security Decision Directive (NSDD) 298 and at a minimum shall include:

1) Assignment of responsibility for OPSEC direction and implementation.

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

3) Establishment of OPSEC education and awareness training.

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

5) Flow down of OPSEC requirements to subcontractors when applicable.

While performing aboard Naval Air Systems Command (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; and protect sensitive unclassified information and activities that could compromise classified information or operations or degrade the planning and execution of operations performed by the Requirements Owner and Contractor in support of the mission. (CDRL A006)

3.2.6 Antiterrorism Force Protection and Emergency Management. The work performed on this TO is not Emergency Essential IAW OPNAVINST 3440.17A, Navy Installation Emergency Management Program 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.3 Detailed Support Requirements.

3.3.1 Technical PM Support.

3.3.1(a) (WCF) Provide support to technical PM efforts for the ASI Division throughout the project life cycle. Applicable to paragraphs 3.3.1.1 – 3.3.1.16.

3.3.1(b) (PROC) Provide support to technical PM efforts for ASI Division projects that are in production phases or are being modernized, modified, or customized. Applicable to paragraphs

3.3.1.1 – 3.3.1.16.

3.3.1(c) (O&M) Provide support to technical PM efforts for ASI Division projects that are fielded and in-service or require operations and logistics support. Applicable to paragraphs

3.3.1.1 – 3.3.1.16.

3.3.1(d) (RDT&E) Provide support to technical PM efforts for ASI Division projects that are in varying phases of research and development. Applicable to paragraphs 3.3.1.1 – 3.3.1.16.

3.3.1(e) (SCN) Provide support to technical PM efforts for ASI Division projects that are in varying stages of ship construction and ship conversion. Applicable to paragraphs 3.3.1.1 – 3.3.1.16.

3.3.1(f) (FMS) Provide support to technical PM efforts for the ASI Division projects throughout the project life cycle for international support projects. Applicable to paragraphs 3.3.1.1 – 3.3.1.16.

3.3.1(g) (Non-DoD) Provide support to technical PM efforts for ASI Division projects throughout the project life cycle for non-DoD customers. Applicable to paragraphs 3.3.1.1 – 3.3.1.16.

3.3.1.1 The Contractor shall support project initiation, planning, execution, monitoring, controlling, and close-out through documenting the total scope of effort, objectives, and the strategic courses of action required to attain objectives based on Government Project Lead (GPL) and customer specific requirements. (CDRLs A007, A008, & A009)

3.3.1.2 The Contractor shall assist with the interpretation of incoming technical tasking statements and support agreements to quantify the project scope, support the GPL in identifying stakeholders to meet specific mission requirements efficiently and effectively, and support in producing and updating the appropriate project initiation documentation. (CDRL A007)

3.3.1.3 The Contractor shall provide support with the research, creation, and maintenance of project cost estimates, Rough Order of Magnitude (ROM) estimates, and/or Life Cycle Cost Estimates (LCCEs) to communicate the approximate resources required within defined project constraints. (CDRL A007)

3.3.1.4 The Contractor shall provide support by setting project baselines by performing project planning activities; defining Work Breakdown Structures (WBSs), integrated and resource-loaded project schedules, and detailed cost estimates; tracking and reporting key events; creating detailed spend plans; and generating PM and spend plans. (CDRL A007)

3.3.1.5 The Contractor shall support monitoring and tracking of technical project performance against established baselines by generating reports that support cost, schedule, performance projections and controls, project schedule functions (such as identifying variances and evaluating critical paths), resources, and dependencies in order to determine cause and possible mitigations. (CDRL A009)

3.3.1.6 The Contractor shall provide support to the project’s Risk Management Plan by providing inputs and/or suggestions to the Government on technical or non-technical project risks from identification, evaluation, mitigation planning, monitoring, and controlling through risk closure. (CDRL A010)

3.3.1.7 The Contractor shall provide support by defining processes for Government approval and by executing those approved processes for identifying, obtaining, managing, and reporting metrics on project performance by researching key events; performing schedule reviews; conducting project reviews; conducting status updates to ASI leadership; and generating periodic reporting that provide suggestions for risk mitigation, corrective actions, and overall project improvement as a result of customer feedback. (CDRL A010)

3.3.1.8 The Contractor shall support the GPL by evaluating project requirements for the acquisition of hardware, software, and other material by conducting acquisition planning IAW FAR Part 7 to include documenting market research per FAR Part 10, identifying sources, evaluating whether commercial items or non-developmental items are available IAW FAR Part 12, and providing the required acquisition documentation, tracking, and reporting depending on the type of strategy pursued by the Government. (CDRL A011)

3.3.1.9 The Contractor shall provide support by performing financial examinations to quickly and accurately set up project spend plans while considering fiscal sources, appropriations, and accounting data; track and maintain history of funding received and obligated; and support the GPL to provide timely obligations.

3.3.1.10 The Contractor shall support executing Planning, Programming, Budgeting, and Execution (PPBE) processes IAW DoDD 7045.14, The Planning, Programming, Budgeting, and Execution (PPBE) Process to identify funding allocations for projects and ASI Division processes.

3.3.1.11 The Contractor shall provide support by processing, monitoring, and executing incoming and outgoing funding; developing project structure set-up, spend plans, expenditure and reconciliation tracking, and closeout; and preparing weekly reports identifying data for all funding received, committed, obligated, and expended by project, branch, and appropriation type. (CDRL A012)

3.3.1.12 The Contractor shall provide support by monitoring and forecasting the fiscal status of projects, reporting actuals to planned funding, explaining potential causes of significant deviations, and presenting possible solutions to any problems.

3.3.1.13 The Contractor shall provide support by forecasting and tracking budget information, to include execution status and fund reconciliation, and by tracking and reporting on the status of budget execution to ensure proper use of all funds (active, expired, and cancelled). (CDRL A009)

3.3.1.14 The Contractor shall provide support by tracking discrepancies against planned vice actual labor executions and by drafting labor adjustments and reconciliations for Government execution when required.

3.3.1.15 The Contractor shall provide support during meetings, often at customer locations, in support of ASI Division GPLs by supplying project, financial, and acquisition knowledge and preparing and presenting agendas, documentation, briefings, technical data, white papers, and meeting minutes. (CDRLs A007, A008, & A009)

3.3.1.16 The contractor shall assist with Agile Framework implementations (Division, Branch, Project, Command interfaces) and must understand Agile methodologies and principles (Agile, Scrum, Scaling, Kanban) throughout an oLSI® Project lifecycle. Additional knowledge is required with Agile supporting tools (JIRA, DevSecOps, etc.) to ensure project status, blockers, and issues (cost, schedule, performance) are tracked in real-time and captured ensuring transparency across the Command.

3.3.2 Data Management Support.

3.3.2(a) (WCF) Provide data management for the ASI Division throughout the project life cycle. Applicable to paragraphs 3.3.2.1 – 3.3.2.28.

3.3.2(b) (PROC) Provide data management for ASI Division projects that are in production phases or are being modernized, modified, or customized. Applicable to paragraphs 3.3.2.1 – 3.3.2.28.

3.3.2(c) (O&M) Provide data management for ASI Division projects that are fielded and in-service or require operations and logistics support. Applicable to paragraphs 3.3.2.1 – 3.3.2.28.

3.3.2(d) (RDT&E) Provide data management for ASI Division projects that are in varying phases of research and development. Applicable to paragraphs 3.3.2.1 – 3.3.2.28.

3.3.2(e) (SCN) Provide data management support for ASI Division projects that are in varying stages of ship construction and ship conversion. Applicable to paragraphs 3.3.2.1 – 3.3.2.28.

3.3.2(f) (FMS) Provide data management for ASI Division projects throughout the project life cycle for international support projects. Applicable to paragraphs 3.3.2.1 – 3.3.2.28.

3.3.2(g) (Non-DoD) Provide data management for ASI Division projects throughout the project life cycle for non-DoD customers. Applicable to paragraphs 3.3.2.1 – 3.3.2.28.

3.3.2.1 The Contractor shall support the production of graphical or pictorial representations of analytics data to facilitate effective communication of patterns, trends, and complex concepts. (CDRL A013)

3.3.2.2 The Contractor shall support designing, creating, and producing interactive multimedia products utilizing various technologies including digital video, photography, motion graphics, and non-linear video editing. (CDRL A014)

3.3.2.3 The Contractor shall provide support by supplying specific graphics, documentation, and concept visualization. This support includes the creation of briefings, technical reports, inputs to technical deliverables, and information graphic communications including brochures, web designs, and poster displays. Tasks also include creating display materials for high-level briefings, coordinating large or specialized production runs of printed materials with internal or external support, and producing a limited reproduction of printed materials utilizing in-house printing and binding equipment. (CDRLs A013 & A015)

3.3.2.4 The Contractor shall support the planning, initiating, management, maintenance, and rules of ASI Division sites (to include, but not be limited to, SharePoint) that set the conditions for effective collaboration and knowledge management to include demonstrations, training, and/or other support related to these sites. (CDRL A013)

3.3.2.5 The Contractor shall support collaboration across functional areas and project teams to gather key information and forecast metrics required to establish plans and respond to individual Division data calls when requested. (CDRL A016)

3.3.2.6 The Contractor shall provide support by determining feasibility to execute forecasted projects to include project financial trends, project financial execution, project processes, tools, and facilities. (CDRL A016)

3.3.2.7 The Contractor shall provide support by maintaining floor plans of Division buildings and seating charts and by providing evaluations and information related to current and future staffing (Government and Contractor) and facility usage, as based upon the Government requirements.

3.3.2.8 The Contractor shall provide support by maintaining the latest knowledge of FAR, DFARS, NAVAIR, and NAWCAD financial and acquisition Government driven policy changes and impacts to internal Division processes.

3.3.2.9 The Contractor shall provide support by conducting assessments of existing PM business operations, procurements, and fiscal management processes and tools to validate adequacy, recognize deficiencies, and identify opportunities for process improvements to increase effectiveness, efficiency, quality, and performance. (CDRL A016)

3.3.2.10 The Contractor shall support the preparation and documentation of Navy Enterprise Resource Planning (N-ERP) reports identifying data related to commitments, obligations, and expenditures across all Division funds and by preparing and presenting options for issue resolution against financial benchmarks. (CDRL A016)

3.3.2.11 The Contractor shall support the performance of Division planning to include defining, implementing, measuring, maintaining, and reporting effective and efficient structures, processes, tools, and skill sets to ensure the Division and technical/project-level objectives are repeatedly executed with high levels of success. (CDRL A016)

3.3.2.12 The Contractor shall provide support by evaluating and reporting on the status of Unliquidated Obligations (ULOs) and by determining the best path toward the reconciliation of these ULOs to meet fiscal year requirements IAW Division timelines.

3.3.2.13 The Contractor shall support the development, tracking, and execution of incoming and outgoing support agreements, Memorandums of Agreement (MOAs), Memorandums of Understanding (MOUs), and General Terms and Conditions (GT&Cs). Tracking should include ceiling values, usage of agreement to date, and agreement end date.

3.3.2.14 The Contractor shall support the development and implementation of a customer feedback program for the ASI Division. The program should include means to track metrics to include design reviews, installations, demonstrations, integrations, end-user trainings, and maintenance activities performed.

3.3.2.15 The Contractor shall support designing, generating, managing, facilitating, and maintaining training content and courses to support Division and project activities in support of, but not limited to, PM, acquisition, procurement, cost management, business rules/process, and business applications. These training courses will be delivered via on-site and web-based methods. (CDRLs A014 & A017)

3.3.2.16 The Contractor shall provide support by utilizing data mining tools, processes, documentation, and policy to identify, evaluate, measure efficiencies, and provide Division leadership with a sound, scientific, and quantitative basis for solving problems, evaluating alternative solutions, and making decisions. (CDRL A017)

3.3.2.17 The Contractor shall use ASI Division Tools including, but not limited to, Shared Data Warehouse (SDW), Business Objects, and Structured Query Language (SQL) to support manipulating data into specific reports with outputs in Qlik Sense (or similar dashboard platform) and Microsoft Excel spreadsheets. (CDRL A017)

3.3.2.18 The Contractor shall support preparation and review of technical documentation. Technical review and edits shall include, at a minimum, a review of technical accuracy, grammar usage, consistency, completeness, formatting, correct spelling, and must ensure that documents are proofread to verify that they are free of typographical error and omissions. Documentation includes, but is not limited to, acquisition documents, training documents, travel orders, Standard Work Packages (SWPs), Standard Operating Procedures (SOPs), and ASI Division-tailored engineering processes.

3.3.2.19 The Contractor shall provide support by processing, tracking, and entering travel through the use of the Defense Travel System (DTS) to include travel arrangements, travel vouchers, reconciliations, order requests, and receipts and by processing applications submitted by new users for Government travel cards; closing out of cards that are no longer required; and facilitating/coordinating travel approval through sponsors as well as internal and external approving authorities.

3.3.2.20 The Contractor shall provide support by reviewing and documenting internal process changes in support of Government travelers as a result of travel policy changes and impacts with regard to the Joint Travel Regulations (JTR) and additional DoD, Navy, NAVAIR, and local NAWCAD travel directives and guidance.

3.3.2.21 The Contractor shall provide support by processing visit requests for Government and contractor visitors traveling to NAWCAD WOLF into the BASICS system and for NAWCAD WOLF Government personnel traveling to other sites and facilities.

3.3.2.22 The Contractor shall provide visitor control support to various ASI Division buildings to include, but not be limited to, monitoring visitors and answering or referring inquiries.

3.3.2.23 The Contractor shall provide support by maintaining logbooks, checking identification, issuing visitor badges, and coordinating facility end-of-day checks.

3.3.2.24 The Contractor shall provide support by maintaining ASI Division conference-room schedules and by coordinating requests and providing resolution to scheduling conflicts.

3.3.2.25 The Contractor shall provide support by stocking and distributing office supplies.

3.3.2.26 The Contractor shall provide support by providing clerical duties such as photocopying, faxing, scanning, filing, shredding, and collating.

3.3.2.27 The Contractor shall provide support by processing classified and unclassified correspondence and naval messages to include routing correspondence to the appropriate personnel IAW the SECNAV M-5216.5 CH-1, Department of the Navy Correspondence Manual.

3.3.2.28 The Contractor shall support formatting and serialization of official correspondence and by applying appropriate routing procedures IAW the SECNAV M-5216.5 CH-1, Department of the Navy Correspondence Manual.

3.3.3 Acquisition Support.

3.3.3(a) (WCF) Provide acquisition support for the ASI Division throughout the project life cycle. Applicable to paragraphs 3.3.3.1 – 3.3.3.2.

3.3.3(b) (PROC) Provide acquisition support for ASI Division projects that are in production phases or are being modernized, modified, or customized. Applicable to paragraphs 3.3.3.1 – 3.3.3.2.

3.3.3(c) (O&M) Provide acquisition support for ASI Division projects that are fielded and in-service or require operations and logistics support. Applicable to paragraphs 3.3.3.1 – 3.3.3.2.

3.3.3(d) (RDT&E) Provide acquisition support for ASI Division projects that are in varying phases of research and development. Applicable to paragraphs 3.3.3.1 – 3.3.3.2.

3.3.3(e) (SCN) Provide support to acquisition efforts for ASI Division projects that are in varying stages of ship construction and ship conversion. Applicable to paragraphs 3.3.3.1 – 3.3.3.2.

3.3.3(f) (FMS) Provide acquisition support for ASI Division projects throughout the project life cycle for international support projects. Applicable to paragraphs 3.3.3.1 – 3.3.3.2.

3.3.3(g) (Non-DoD) Provide acquisition support for ASI Division projects throughout the project life cycle for non-DoD customers. Applicable to paragraphs 3.3.3.1 – 3.3.3.2.

3.3.3.1 Supply.

3.3.3.1.1 The Contractor shall provide support by translating project requirements into assessments of the most advantageous supply acquisition strategies through conducting evaluations and market research while considering expectations and constraints, historical data, technical characteristics, published regulations, cost, schedule, and risk factors.

3.3.3.1.2 The Contractor shall support the generation of required acquisition documentation based on the procurement strategy IAW DoD policies and Command and Contracting Activity formats and standards.

3.3.3.1.3 The Contractor shall support the Government with the generation of Request for Information (RFI) and Request for Quotation (RFQ) notices for Government review and submission. (CDRL A011)

3.3.3.1.4 The Contractor shall support the generation of the appropriate information for Procurement Initiation Documents (PIDs) in the Navy Acquisition Management System’s (AMS) Procurement Management Tool (PMT) and other related information necessary for the projects to procure supplies.

3.3.3.1.5 The Contractor shall provide support by performing evaluations, gathering information, and making assessments concerning the use and integration of mandatory procurement sources including National Stock Numbers (NSNs) and the federal stock system IAW DoD policies. (CDRL A011)

3.3.3.1.6 The Contractor shall provide support by preparing Purchase Requisitions (PRs) within N-ERP for all pre-award and post-award supply contract requirements with accuracy and within lead times required by the Procurement Group and by interfacing with Business Financial Managers (BFMs) for latest format and processes. (CDRL A019)

3.3.3.1.7 The Contractor shall provide support by initiating and tracking Government Purchase Card (GPC) requests IAW ASI Division workflows, DoD policies, and Command formats and standards.

3.3.3.1.8 The Contractor shall support the maintenance of a current list of required items to be procured for specific projects in the form of a Master Equipment List (MEL) or Master Parts List (MPL). (CDRL A018)

3.3.3.1.9 The Contractor shall support monitoring and tracking of material/equipment during activities in the acquisition process (from procurement planning to delivery of the final product to the Government) within ASI Division tracking tools. (CDRL A018)

3.3.3.1.10 The Contractor shall provide support to the GPLs regarding the management of supply contracts by documenting and reporting on contract ceiling, remaining quantities, funding, N-ERP expenditures, deliverables, delivery status, and by complying with acquisition regulations and policies. (CDRL A008)

3.3.3.2 Services.

The Contractor shall provide support by maintaining and updating a tracking report for post-award Division service contract PRs to facilitate timely and accurate Division process workflows in coordination with Government resources to determine list order/priority adjustments and by maintaining…