UNCLASSIFIED

STATEMENT OF WORK FOR

BUSINESS INTELLIGENCE

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 Integrated Command, Control and Intel Systems (IC2&IS) Division. The

IC2&IS Division, operating under the oLSI® model, has requirements for comprehensive business intelligence platforms to translate operational data into valuable command-level assets.

This platform will empower leadership with actionable intelligence through performance dashboards, trend analysis, and key performance indicators (KPIs). The objective is to provide a holistic view of organizational performance, supporting long-range planning and enhancing the effectiveness of decision-making processes. This requirement is in direct support of projects related to multiple major defense acquisition programs, other acquisition category designations, and/or other defense weapons systems.

Applicable Documents.

The documentation listed below are presented only as representative sources of the technological interface details that may be required during Task Order (TO) performance. Likewise, the documentation listed is not all-inclusive but is representative of the type of information that may be necessary to perform the work. The applicable document version is the latest version at time of award. Documents may be added and/or updated to the latest applicable revision as required during the execution of this TO.

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.

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

2014.

2.1.9 SECNAVINST 5239.20A, Department of the Navy Cyberspace Information Technology and Cybersecurity Workforce Management and Qualification, 10 Feb 2016.

2.1.10 DoDD 8140.01, Cyberspace Workforce Management, 5 Oct 2020.

2.1.11 DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology, 19 Jul 2022.

2.2 Other Government Documents.

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

Requirements.

3.1 General Requirements.

General Requirements. Paragraph 3.1 from the Basic Multiple Award Contract (MAC) Contract, N00421-22-D-0006 through N00421-22-D-0068, and its deliverable products are required in support of this TO, unless specifically stated otherwise below to provide more detailed requirements or to provide Contract Line Item Number (CLIN) references.

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 Top Secret as specified on the DD Form 254, Contract

Security Classification Specification Form (Attachment XX). The current operating environment required for this TO includes:

Microsoft Windows 10/16

Microsoft Project 2010/2016

Microsoft Office Professional Plus 2010/2016

Adobe Reader

Adobe Acrobat Pro

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 IC2&IS Division. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with the IC2&IS Division during working hours whether at contractor work site or on travel.

3.1.2 Work Location, Facilities, and Telework/Remote Work.

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

3.1.2.1.1 Government Site Requirements. 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 100 drivable miles of NAWCAD WOLF, St.

Inigoes, MD to satisfy the requirements of this TO. The Government will not assume responsibility to retain the facilities or take control of the title after the TO is completed.

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 10 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 section 3.1.1. This support shall be provided at the support facility detailed in section 3.1.2.1.2.

3.1.2.3 Telework/Remote Work.

The Contractor may allow contractor employees to telework and/or work remotely in accordance with (IAW) the information in section 3.4. The Contractor may utilize alternate worksites/locations to telework and/or work from a remote location to support continued performance of SOW tasks IAW company policy. When using telework and/or remote work, 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. On-site performance may be required outside of routine on-site performance days, and shall be provided when requested by the COR.

Remote work is an alternative work arrangement that allows for a position to perform official duties at an approved alternative worksite away from an agency worksite, without regularly returning to the agency worksite during each pay period. Remote work can be either local or distant.

Local remote work is defined as a position that does not require regular and recurring on-site performance but includes enough required on-site performance that the position is required to be staffed within 100 drivable miles of NAWCAD WOLF, St. Inigoes, MD.

Distant remote work is defined as a position that does not require regular and recurring on-site performance and is not required to be staffed within 100 drivable miles of NAWCAD WOLF, St.

Inigoes, MD but shall be staffed within the contiguous United States.

In the event that telework tools become unavailable while working off-site, the Contractor shall require positions defined as telework and local remote work 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 and/or local remote work by providing a notice 30 calendar days in advance and/or for distant remote telework positions by providing a notice 90 calendar days in advance so the

Contractor can address changes needed to support mission requirements.

3.1.2.4 Special Facilities.

3.1.2.4.1 Reserved.

3.1.2.4.2 Reserved.

3.1.2.5 Reserved.

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 Financial Progress Report. (CDRL A001)

3.1.3.3 Contractor’s Personnel Roster – Workforce Report. (CDRL A001)

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

Contracting Officer’s Representative (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/#url=Overview. With the exception of the events in section 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 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 (KO) 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 COR.

3.1.4.1.5 Reserved.

3.1.5 Other Direct Costs (ODCs). Working Capital Fund (WCF); Operations and

Maintenance (O&M); Procurement (PROC); Research, Development, Test & Evaluation

(RDT&E); Non-DoD; and Foreign Military Sales (FMS).

3.1.5.1 Travel.

3.1.5.1.1 General and administrative expenses. Travel may include general and administrative expenses, but shall not include profit. Temporary travel requirements, locations, and authorization request procedures will be determined by the TO. If required, temporary travel locations include Continental United States (CONUS) locations and Outside the Continental

United States (OCONUS) locations to include Alaska and Hawaii. Travel authorization requests shall be prepared and submitted for COR approval IAW TO guidance and NAVAIR clause

5252.232-9509. The Contractor shall provide a trip report for all travel IAW the CDRL defined in the TO. (CDRL A002)

3.1.5.1.2 Reserved.

3.1.5.1.3 Reserved.

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. (CDRL A019) Material costs may include general and administrative expenses but shall not include profit/fee.

3.1.5.3 Field Services. Field services provide shipping and freight supplies, services, and other related services. Shipping and freight supplies and services include shipment and delivery services, such as Federal Express (FedEx), United Parcel Service (UPS), and U.S. Postal Service.

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. The Contractor shall submit a Small

Business Participation Commitment Document (SBPCD). (CDRL A00X)

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

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

̶ Work turnover. The Contractor shall provide a plan of action to effectively transfer tasked work that is in process at the expiration or termination of the TO to the successor company and establish and maintain effective communication with the incoming

Contractor or Government personnel for the period of transition via weekly status meetings.

̶ Quality Assurance (QA). 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 Training Requirements.

3.1.9.1 Certification and training: The Contractor is responsible for ensuring all employees have the required training and certification by verifying experience, special training, and qualifications.

3.1.9.2 Reserved.

3.1.9.3 Reserved.

3.1.9.4 Reserved.

3.1.10 Reserved.

3.1.11 Technical Direction Letters (TDLs). When necessary, technical direction or clarification concerning the details of specific tasks set forth in the TOs 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 an.

3.2 Security.

Paragraph 3.2 from the Basic MAC Contract, N00421-22-D-0006 through N00421-22-D-0068, is required in support of this TO, unless specifically stated otherwise below to provide more detailed requirements.

3.2.2.2 Contractor Personnel Labor Category Security Requirements. All personnel shall have at a minimum, interim Secret clearances within 60 days of award with the exceptions noted in the table below.

LABOR CATEGORY

DoD SECURITY

CLEARANCE LEVEL

(INTERIM CLEARANCE

ACCEPTABLE)

FTE

REQUIRED

BUSINESS DAYS

AFTER ISSUANCE

OF TO

Computer Systems Analysts, Advanced TS 1 Within 120 Business

Days of Award

General and Operations Managers, Senior

(Key)

TS 1

Within 120 Business

Days of Award

Information Security Analysts

(Cybersecurity), Advanced

TS 1

Within 120 Business

Days of Award

Operations Research Analysts, Senior TS 1 Within 120 Business

Days of 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 IAW 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 the facility security procedures and controls.

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: IC2&IS TPMS COR, 17640 NESEA Way, Building 8103, St. Inigoes, MD 20684.

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 NAWCAD WOLF IC2&IS Division, COR, 17100 Webster Field Road, St. Inigoes, MD

20684.

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 NSPM-28 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 A004)

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.2.7 Reserved.

3.2.8 Reserved.

3.2.9 Reserved.

3.2.10 Reserved.

3.2.11 Reserved.

3.2.12 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 A005)

3.2.13 Reserved.

3.3 Specific Requirements.

3.3.1 Technical and Project Management Support.

3.3.1(a) (WCF) Provide operations and sustainment support efforts to Business Intelligence work activities. Provide planning and execution efforts to support the development of new and the modernization and modifications of existing Business Intelligence work activities. Provide planning and execution of Business Intelligence work activities for researching, developing, testing, and evaluating end item products. Applicable to paragraphs 3.3.1.1 – 3.3.1.7.

3.3.1(b) (O&M) Provide operations and sustainment support efforts to Business Intelligence work activities. Applicable to paragraphs 3.3.1.1 – 3.3.1.7.

3.3.1(c) (PROC) Provide planning and execution efforts to support the development of new and the modernization and modifications of existing Business Intelligence work activities.

Applicable to paragraphs 3.3.1.1 – 3.3.1.7.

3.3.1(d) (RDT&E) Provide planning and execution of Business Intelligence work activities for researching, developing, testing, and evaluating end item products. Applicable to paragraphs

3.3.1.1 – 3.3.1.7.

3.3.1(e) (Non-DoD) Provide operations and sustainment support efforts to Business Intelligence work activities. Provide planning and execution efforts to support the development of new and the modernization and modifications of existing Business Intelligence work activities. Provide planning and execution of Business Intelligence work activities for researching, developing, testing, and evaluating end item products. Applicable to paragraphs 3.3.1.1 – 3.3.1.7.

3.3.1(f) (FMS) Provide Business Intelligence work activities support to support FMS customers. Applicable to paragraphs 3.3.1.1 – 3.3.1.7.

3.3.1.1 The Contractor shall support the Government by providing the necessary planning and coordination efforts with the IC2&IS Division to monitor and control costs and resources of work performed, as it pertains to Business Intelligence work activities.

3.3.1.2 The Contractor shall assist the Government by developing and maintaining Work

Breakdown Structure (WBS) documentation and by supporting the planning efforts necessary to identify, schedule, execute, and monitor Business Intelligence work activities including the generation of a list of a project terminal work elements with intended start and finish dates, a resource list with availability, and detailed program milestones. (CDRL A006)

3.3.1.3 The Contractor shall support the Government by participating with designated

Government technical representatives in Business Intelligence work activities design review meetings, technical reviews, and conferences/presentations where component and system design expertise are required. (CDRL A007)

3.3.1.4 The Contractor shall support the Government by providing customer-focused agile teams with multi-disciplinary skillsets to collaborate with the IC2&IS Division to research and plan Business Intelligence work activities and functions, identify system collaborations, identify consistent practices and identify risks and challenges. (CDRL A008)

3.3.1.5 The Contractor shall assist the Government by monitoring the scope throughout the duration of the Business Intelligence work activities to ensure effective and adequate methods are in place to proactively address and manage changes in project scope, schedule, and cost.

3.3.1.6 The Contractor shall assist the Government with analyzing and providing support regarding the execution of processes and methods to effectively research, evaluate, identify, communicate, and manage risks associated with Business Intelligence work activities.

3.3.1.7 The Contractor shall assist the Government with identifying risks to enable the

Government to factor these risks into decisions affecting other technical management areas and cost, scope, and schedule as related to IC2&IS products.

3.3.2 Analytics Application Development

3.3.2(a) (WCF) Provide operations, maintenance, or sustainment efforts for analytical applications in support Business Intelligence work activities. Provide integrated development efforts for analytical applications in support Business Intelligence work activities. Provide research and development efforts to include concept development, planning, design, prototyping, and testing for analytical applications in support Business Intelligence work activities.

Applicable to paragraphs 3.3.2.1 – 3.3.2.14.

3.3.2(b) (O&M) Provide operations, maintenance, or sustainment efforts for analytical applications in support Business Intelligence work activities. Applicable to paragraphs 3.3.2.1 –

3.3.2.14.

3.3.2(c) (PROC) Provide integrated development efforts for analytical applications in support

Business Intelligence work activities. Applicable to paragraphs 3.3.2.1 – 3.3.2.14.

3.3.2(d) (RDT&E) Provide research and development efforts to include concept development, planning, design, prototyping, and testing for analytical applications in support Business

Intelligence work activities. Applicable to paragraphs 3.3.2.1 – 3.3.2.14.

3.3.2(e) (Non-DoD) Provide operations, maintenance, or sustainment efforts for analytical applications in support Business Intelligence work activities. Provide integrated development efforts for analytical applications in support Business Intelligence work activities. Provide research and development efforts to include concept development, planning, design, prototyping, and testing for analytical applications in support Business Intelligence work activities.

Applicable to paragraphs 3.3.2.1 – 3.3.2.14.

3.3.2(f) (FMS) Provide Business Intelligence integrated analytics application support to the

IC2&IS Division in all phases of the project life cycle to support FMS customers. Applicable to paragraphs 3.3.2.1 – 3.3.2.14.

3.3.2.1 The Contractor shall assist the Government in the development and delivery of new platform features and automation capabilities focused on continuous modernization while maintaining security, compliance, and operational resilience. (CDRL A008)

3.3.2.2 The Contractor shall assist the Government in providing platform operations engineering, monitoring, and application management.

3.3.2.3 The Contractor shall assist the Government in the integration of customized software and commercial software products into enterprise platforms using the best in class agile or other similar methodologies for application development, where the development is organized into one or more releases consisting of multiple sprints. (CDRLs A009, A010, A011)

3.3.2.4 The Contractor shall assist the Government by developing use case and application-specific data products that follow all data mesh principles, policies, and procedures provided by

DoD CDAO.

3.3.2.4.1 The Contractor shall assist the Government with the delivery of use-case specific applications using enterprise tools and capabilities as well as custom software, as required.

(CDRL A012)

3.3.2.4.2 The Contractor shall assist the Government by leveraging enterprise Continuous

Integration (CI)/Continuous Delivery (CD) pipelines and processes to deploy software and integrate web application content.

3.3.2.4.3 The Contractor shall support the Government by developing and deploying web applications and other containerized data analytics applications, covering the entire IT engineering lifecycle including requirements gathering, system design and development, installation, integration and testing, and sustainment. (CDRL A013)

3.3.2.4.4 The Contractor shall support the Government by optimizing prototypes and converting proven ideas into robust capabilities for delivery.

3.3.2.5 The Contractor shall assist the Government by delivering on-demand data science capabilities to allow DoD organizations to continuously and persistently use data science to positively impact the operating mission, leveraging a team comprised of both highly experienced data science experts and functional expertise with deep rooted knowledge of the business domain, mission space, and data.

3.3.2.6 The Contractor shall assist the Government by obtaining, integrating and cleaning/preparing data for building customized analytic, AI, and decision products.

3.3.2.7 The Contractor shall assist the Government by researching, analyzing and summarizing large, diverse datasets through multiple technologies and techniques to enable decision-making.

3.3.2.8 The Contractor shall assist the Government by researching, acquiring, and applying data fusion methods and techniques that address analysis and protection of personally identifiable information (PII). (CDRL A013)

3.3.2.9 The Contractor shall assist the Government by creating data products accessible via

APIs, leveraging DoD-authorized system platforms, for internal and external application use.

3.3.2.10 The Contractor shall assist the Government by coordinating with functional and technical stakeholders to define methods for enriching, aggregating, and exposing data in a curated form to support analytics at scale in support of use cases of various maturity levels.

(CDRL A014)

3.3.2.11 The Contractor shall assist the Government by leveraging master data management tools and services for the development of products to include, but limited to, lookup tables, business glossaries, and data profile information. (CDRL A013)

3.3.2.12 The Contractor shall assist the Government by deploying validated models into production to support the development of decision support tools, dashboards, workflows and use cases.

3.3.2.13 The Contractor shall assist the Government by leveraging user-centered design methods to provide support for User Interface/User Experience (UI/UX) software development efforts to design and creating applications with User Centered Design (UCD) methodologies to develop the right solutions.

3.3.2.14 The Contractor shall assist the Government by leveraging automated DevSecOps solutions to design, build, and deliver customized solutions to DoD customers.

3.3.3 Data Engineering Services

3.3.3(a) (WCF) Provide operations, maintenance, or sustainment efforts for data engineering in support Business Intelligence work activities. Provide operations, maintenance, or sustainment efforts for data engineering in support Business Intelligence work activities. Provide research and development efforts to include concept development, planning, design, prototyping, and testing for data engineering in support Business Intelligence work activities. Applicable to paragraphs 3.3.3.1 – 3.3.3.9.2.

3.3.3(b) (O&M) Provide operations, maintenance, or sustainment efforts for data engineering in support Business Intelligence work activities. Applicable to paragraphs 3.3.3.1 – 3.3.3.9.2.

3.3.3(c) (PROC) Provide integrated development efforts for data engineering in support

Business Intelligence work activities. Applicable to paragraphs 3.3.3.1 – 3.3.3.9.2.

3.3.3(d) (RDT&E) Provide research and development efforts to include concept development, planning, design, prototyping, and testing for data engineering in support Business Intelligence work activities. Applicable to paragraphs 3.3.3.1 – 3.3.3.9.2.

3.3.3(e) (Non-DoD) Provide operations, maintenance, or sustainment efforts for data engineering in support Business Intelligence work activities. Provide operations, maintenance, or sustainment efforts for data engineering in support Business Intelligence work activities. Provide research and development efforts to include concept development, planning, design, prototyping, and testing for data engineering in support Business Intelligence work activities. Applicable to paragraphs 3.3.3.1 – 3.3.3.9.2..

3.3.3(f) (FMS) Provide Business Intelligence integrated data engineering support to the IC2&IS

Division in all phases of the project life cycle to support FMS customers. Applicable to paragraphs 3.3.3.1 – 3.3.3.9.2.

3.3.3.1 The Contractor shall assist the Government by support provide support services to ensure reliable, discoverable, and mission-ready data products that support analytics and AI workloads.

3.3.3.2 The Contractor shall assist the Government with designing, implementing and maintaining policy-based governance mechanisms for managing the access and use of enterprise platform resources including cloud capacity, tools and services, pipelines, data, analytics, AI models, and visualization applications to ensure compliance, auditability and scalability.

(CDRLs A006, A008)

3.3.3.2.1 The Contractor shall support the Government with end-to-end data pipeline design, development, and automation.

3.3.3.3 The Contractor shall assist the Government to secure data integration across heterogeneous data sources and platforms.

3.3.3.4 The Contractor shall assist the Government with cataloging Enterprise data and metadata management aligned with DoD federated data guidance. (CDRL A013)

3.3.3.5 The Contractor shall support the Government by providing training to enable customer teams to scale and sustain data engineering capabilities. (CDRL A015)

3.3.3.6 The Contractor shall assist the Government with establishing data sharing agreements between DoD data providers and DoD CDAO systems and platform owners. (CDRL A014)

3.3.3.7 The Contractor shall assist the Government with designing, implementing, testing, authorizing, and operating enterprise data tagging capabilities for enterprise data imported into

CDAO systems and platforms. (CDRL A013)

3.3.3.8 The Contractor shall assist the Government with designing, implementing, testing, authorizing, and operating enterprise data cleaning and quality control capabilities for enterprise data imported into CDAO systems and platforms. (CDRL A013)

3.3.3.9 Cybersecurity

3.3.3.9.1 The Contractor shall assist the Government by defining, designing, implementing, testing, authorizing, and maintaining appropriate NIST security controls for CDAO systems, platforms and solutions.

3.3.3.9.2 The Contractor shall assist the Government by generating, preparing, and maintaining

IATT, ATO, and Change Request (CR) engineering artifacts and documents for CDAO systems, platforms, and solutions using the DoD Risk Management Process (RMF). (CDRL A016)

3.3.4 Artificial Intelligence (AI) Engineering Services

3.3.4(a) (WCF) Provide operations, maintenance, or sustainment efforts for artificial intelligence engineering in support Business Intelligence work activities. Provide integrated development efforts for artificial intelligence engineering in support Business Intelligence work activities. Provide research and development efforts to include concept development, planning, design, prototyping, and testing for artificial intelligence engineering in support Business

Intelligence work activities. Applicable to paragraphs 3.3.4.1 – 3.3.4.5.

3.3.4(b) (O&M) Provide operations, maintenance, or sustainment efforts for artificial intelligence engineering in support Business Intelligence work activities. Applicable to paragraphs 3.3.4.1 – 3.3.4.5.

3.3.4(c) (PROC) Provide integrated development efforts for artificial intelligence engineering in support Business Intelligence work activities. Applicable to paragraphs 3.3.4.1 – 3.3.4.5.

3.3.4(d) (RDT&E) Provide research and development efforts to include concept development, planning, design, prototyping, and testing for artificial intelligence engineering in support

Business Intelligence work activities. Applicable to paragraphs 3.3.4.1 – 3.3.4.5.

3.3.4(e) (Non-DoD) Provide operations, maintenance, or sustainment efforts for artificial intelligence engineering in support Business Intelligence work activities. Provide integrated development efforts for artificial intelligence engineering in support Business Intelligence work activities. Provide research and development efforts to include concept development, planning, design, prototyping, and testing for artificial intelligence engineering in support Business

Intelligence work activities. Applicable to paragraphs 3.3.4.1 – 3.3.4.5.

3.3.4(f) (FMS) Provide Business Intelligence integrated data engineering support to the IC2&IS

Division in all phases of the project life cycle to support FMS customers. Applicable to paragraphs 3.3.4.1 – 3.3.4.5.

3.3.4.1 The Contractor shall assist the Government with designing, developing, integrating, and delivering AI models enabling the support of enterprise decision advantage, algorithmic workflows, and mission-critical automation at scale.

3.3.4.2 The Contractor shall support the Government with the Advanced model experimentation, testing, and rapid DevSecOps workflows.

3.3.4.3 The Contractor shall assist the Government by providing Independent AI model testing and evaluation to validate performance, reliability, and compliance. (CDRLs A009, A010, and

A011)

3.3.4.4 The Contractor shall assist the Government by integrating AI/ML models into existing platforms and operational workflows.

3.3.4.5 The Contractor shall assist the Government in defining, scoping, planning, implementing, testing, authorizing, and delivering Robotic Process Automation (RPA) Solutions.

(CDRLs A017 and A018)

3.4 Personnel Qualifications. Paragraph 3.4 from the Basic MAC Contract, N00421-22-D-

0006 through N00421-22-D-0068, is required in support of this TO, unless specifically stated otherwise below to provide more detailed requirements and to define the required labor categories.

3.4.1 The following defines the minimum education and experience for each non-Service

Contract Act (non-SCA) labor category and further describes the functional description for each labor category. The Contractor shall be responsible for employing personnel having at least the minimum level of education, training, and experience as stated under each labor category specified herein. All personnel shall have the required security clearance identified in paragraph

3.2.2.1.

3.4.2 Key Personnel. Key personnel are those who will be performing in key labor categories as specified for applicable labor categories below. All other labor categories and Full Time

Equivalent (FTE) employees (defined as 1,920 hours) are considered non-key. Key personnel are subject to the substitution restrictions clause within CTXT.237-9501, Addition or Substitution of

Key Personnel (Services).

KEY LABOR CATEGORY LEVEL

BUREAU OF LABOR STATISTICS

(BLS) STANDARD OCCUPATIONAL

CLASSIFICATION (SOC) CODE

NUMBER OF

KEY

PERSONNEL

REQUIRED

General and Operations Managers Senior 11-1021 1

Operations Research Analysts Senior 15-2031 1

3.4.3 Definitions.

3.4.3.1.1 “Years of experience” shall mean full, productive years of participation.

3.4.3.1.2 “Productive years” shall mean 52 weeks of work reduced by reasonable amounts of time for holiday, annual, and sick leave.

3.4.3.1.3 “Part-time” shall mean if participation was part-time or if less than one-half of the standard work week was spent performing qualifying functions. The actual time spent performing qualifying functions may be accumulated to arrive at full years of experience.

3.4.3.1.4 “College degree” shall mean all degrees shall be obtained from an accredited college or university as recognized by the U.S. Department of Education (ED). This includes Associate of Arts (A.A.), Associate of Science (A.S.), Bachelor of Arts (B.A.), Bachelor of Science (B.S.), Master of Arts (M.A.), Master of Science (M.S.), and/or Doctorate (Ph.D.) degrees.

3.4.3.1.5 “Degree major” shall mean the specific major field required, which will be noted under the applicable labor category.

3.4.3.1.6 “Engineering or engineering discipline,” when used in relation to educational or work experience requirements, shall mean any of the following specific subjects, disciplines, or areas of work experience only: computer, electrical, electronics, mechanical, information systems, or engineering technology.

3.4.3.1.7 “Technical discipline,” when used in relation to educational or work experience requirements, shall mean any of the following specific subjects, disciplines, or areas of work experience only: computer science, information systems management, computer engineering, mathematics, physics, electrical engineering, or mechanical engineering.

3.4.3.1.8 “Computer science or IT discipline,” when used in relation to educational or work experience requirements, shall mean any of the following specific subjects, disciplines, or areas of work experience only: computer science, computer engineering, software engineering, network engineering, information systems, cybersecurity, or management information systems technology.

3.4.3.1.9 “Business or business discipline,” when used in relation to educational or work experience requirements, shall mean any of the following specific subjects, disciplines, or areas of work experience only: business administration, business management, technical management, economics, finance, or accounting.

3.4.3.1.10 “Technical certification training” shall mean the specified certification training noted under the applicable labor category.

3.4.3.1.11 “Active or current certification” shall mean individuals must be able to demonstrate that they possess a valid certification, per vendor recertification standards, at the time of proposal submission and at the time of TO award.

3.4.7 Non-SCA and non-CSWF labor categories experience and education level definitions:

If required, specialized experience and associated years of that particular experience are specified under the applicable labor category qualifications.

3.4.7.1 Junior. A junior level person within a labor category has less than three years of experience and a bachelor’s degree or a qualifying substitution, if identified. However, experience may exceed three years if performing a junior level function. A junior level person is responsible for assisting more senior positions and/or performing functional duties under the oversight of more senior positions.

3.4.7.2 Journeyman. A journeyman level person within a labor category has at least three years of experience and a bachelor’s degree or a qualifying substitution, if identified. A journeyman level person typically performs all functional duties independently.

3.4.7.3 Senior. A senior level person has at least 10 years of experience and a master’s degree or a qualifying substitution, if identified. A senior level person typically works on high-visibility or mission critical aspects of a given program and performs all functional duties independently.

A senior level person may oversee the efforts of less senior staff and/or be responsible for the efforts of all staff assigned to a specific job.

3.4.7.4 Qualification substitution chart. The following standard qualification substitution chart provides allowable standard experience/education substitutions. Specific qualifications for each labor category are contained in the detailed labor qualification sections below (3.4.14, 3.4.15 and

3.4.16).

Bachelor's Degree

Associate degree plus four years of additional work experience related to the applicable labor category’s required experience may be substituted for a bachelor's degree.

OR

Six years of additional work experience related to the applicable labor category’s required experience may be substituted for a bachelor's degree.

Master's Degree

Bachelor's degree plus four years of additional work experience related to the applicable labor category’s required experience may be substituted for a master's degree.

OR

Ten years of additional work experience related to the applicable labor category’s required experience may be substituted for a master's degree.

3.4.14 Cyber Security Work Force (CSWF) Designation Positions.

3.4.14.1 The labor category levels for designated positions are specified as Entry/Basic, Intermediate, and…