DRAFT PWS_CDO Data Analytics_18Jul.pdf

Defense Contract Management Agency (DCMA) Performance Work Statement

Chief Data Officer and Analytics Support

Monday, July 17, 2023 Version 3.6

Contents

1. General Description 3

2. Scope of Work 4

3. Performance Requirements 4

4. Transition Period 24

5. Non personal Services 24

6. Period of Performance 25

7. Government Furnished Equipment 25

8. Place of Performance 26

9. Security Requirements 29

10. Data Access and Retention 32

11. Applicable Directives 33

12. Information Assurance Certifications 34

13. Government Rights 35

14. Post Award Conference/Periodic Progress Meeting 35

15. Invoicing 35

16. Section 508 Accessibility Standards 35

17. Related and Associated Documents 36

ADDENDUM A Acronyms 37

Technical Exhibit 1 Performance Requirements Summary 41

Technical Exhibit 2 DELIVERABLES SCHEDULE 54

1 General Description

The objective of this Performance Work Statement is for the Defense Contract Management Agency (DCMA) to obtain contractor support and expertise to support a broad range of analytical and data visualization, data exploitation, management consulting and support services for implementation of Artificial Intelligence/ Machine Learning (AI/ML applications in the Contract Administration field. Specifically, DCMA requires professional consulting and support services to assist with the full range of business intelligence program/project management services necessary to implement the DCMA data strategic direction, expected to evolve over the contract’s period of performance. These capabilities include a wide range of functional data management disciplines including: data exploitation/analysis, data visualization/dashboard strategy, application program/project management, and data management.

The scope of this requirement includes the following DCMA Chief Data Officer areas:

Functional Area 1: Advanced Analytics (includes predictive analytics)

Functional Area 2: Dashboard and Data Visualization

Functional Area 3: Data Application Development (Low code/no code- in POWER BI, POWER APPS, ADVANA, QLIK)

Functional Area 4: Artificial Intelligence and Machine Learning (AI/ML)

Functional Area 5: Enterprise Architecture Support

DCMA CDO requires additional resources and expertise in order to efficiently and effectively execute its responsibility for managing the Agency’s data resources and ensuring that DCMA complies with federal law, DoD Directives and oversight, and internal policy and requirements. Legal and statutory requirements include, but are not limited to, those specified in the Paperwork Reduction Act, Privacy Act, the Federal Records Act, the Freedom of Information Act (FOIA), Clinger-Cohen Act, and Data Quality Act. Federal oversight requirements include policy and guidance documents issued by the OMB, GAO, and the Executive Office of the President.

Internal requirements include, but are not limited to, those issued by the agency's Inspector General, the agency's Director, and the CIO. The Analytic Support Services required by DCMA including the compliance requirements above, are further detailed in the seven functional areas described below. DCMA Background & Mission

As a Department of Defense (DoD) Combat Support Agency, DCMA ensures the integrity of the contracting process, and provides a broad range of contract-procurement management and administrative services to ensure a valued product is being delivered promptly and ready for use by America's Warfighters.

DCMA is a Department of Defense (DoD) component that provides Contract Administration Services (CAS) to the DoD Enterprise.

DCMA works directly with Defense suppliers to ensure that DoD, Federal, and allied Government supplies and services are delivered on time, at projected cost, and meet all performance requirements.

DCMA is headquartered in Fort Gregg-Adams, Virginia and employs approximately 10,000 civilian and military professionals with over 800 distinct and supported employee duty stations worldwide.

DCMA's Chief Data and Analytics Office includes approximately 25 Government and contractor personnel around the world. DCMA has a large technical architecture consisting of approximately 12,000 personal computers, 1,000 virtual desktops, 8,000 smartphones, 210 servers, 2,000 virtual servers, 325 point-to-point circuits of varying sizes, and 600 external Digital Subscriber Line (DSL), cable, and other commercial broadband circuits.

2 Scope of Work

The objective of this performance work statement is to obtain contractor services to provide a broad scope of functional strategic and managerial business consulting and support services on behalf of the DCMA CDO Staff. The Contractor shall provide professional consulting services to manage the full range of data program/data project management services necessary to implement the DCMA Data strategic direction and operational data program direction, each of which are expected to evolve over the contracts period of performance.

3 Performance Requirements

REPORTING REQUIREMENTS

The Contractor shall provide the COR with Monthly and Quarterly Progress Reports. The monthly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved. If problems have not been completely resolved, the Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The Contractor shall monitor performance against the Performance Plan and report any deviations. The Government expects that the Contractor will continually communicate so issues that arise are transparent to both parties to prevent escalation of outstanding issues.

3.1 Advanced Analytics (includes predictive analytics) (Functional Area 1)

The contractor shall provide the following support:

PERFORM STRATEGIC DATA ANALYTICS

Tasks

1. This Strategic Analytics Team serves as a proactive, forward-looking team as well as a strategic response cell to address immediate requirements.

2. The Team proactively surveys the data analytics landscape, cutting edge technologies, and trends in data science as well as defense industry trends and best practices, other Federal agency data analytics initiatives, monitors OSD leadership communications, and reviews Congressional committee testimony and draft legislation to identify strategic trends that could positively influence or negatively impact Acquisition Visibility for senior defense leaders.

3. The contractor provides consulting expertise in the following areas: data analytics and data science, functional subject matter expertise regarding Acquisition Visibility Capabilities, defense acquisition policy, strategic stakeholder communications, training, and customer engagement.

The government estimates that 6 consultants may be required to perform these work processes. This is just an estimate. The Contractor, may thru its own analysis determine that more or fewer personnel are required based on its analysis.

Deliverables:

A001 Monthly Progress Report A002 Quarterly Project Status Briefings A003 Ad-Hoc Reports and Briefings as Required.

A004 Initial Survey of DCMA Data Analytics landscape and how DCMA can utilize other DoD and industry approaches for data monitoring and strategic tend analysis

3.1.1 Data Strategy Development and Implementation

Tasks

1. Develop and update strategic and operational plans in response to policy\emphasis changes, new opportunities and changing market conditions

2. Evaluate DCMA data business processes and identify high risk areas or opportunities for efficiency and automation.

3. Develop and document solutions for improving efficiencies, implementing automation and mitigating risk.

4. Provide solution discovery, service management, risk management and relationship management across all DCMA data sources to identify gaps and potential options for business process improvement and or technology optimization. Typical analysis includes, but is not limited to, capability analysis based on industry standards, and process analysis to implement new initiatives or resolve problems. Analysis documents should describe alternatives based on the research and analysis performed, and makes recommendations on courses of action.

5. Perform Data Science support in order to enable DCMA/DoD tools and capabilities to better extract knowledge and actionable information from acquisition data. The contractor shall investigate complex problems applying expertise in disciplines within the fields of mathematics, statistics, and computer science. The contractor’s data scientists shall identify and interpret rich data sources; recommend means to manage large amounts of data despite hardware, software, and bandwidth constraints;

consolidate data sources; ensure consistency of datasets; create visualizations to aid in understanding data; build mathematical models using the data; and present and communicate the data insights/findings. Obtain raw data and perform Data Analysis, converting it into information useful for decision-making by users. Data is collected and analyzed to answer questions or test hypotheses. Review requirements documents for data structures and content including data definitions, use cases, and business rules sufficiency and completeness. Determine and/or confirm authoritative acquisition data sources.

6. Perform Data Modeling to define and analyze data requirements needed to support acquisition business processes within the scope of corresponding information systems in organizations.

The government estimates that 6 consultants may be required to perform these work processes. This is just an estimate. The Contractor, may thru its own analysis determine that more or fewer personnel are required based on its analysis.

Deliverables:

A005 Strategic and operational plans pertaining to policy changes and new opportunities arising in data exploitation A006 Analytical Reports on Business Process Improvement, Data Automation Implementation/Refinement, A007 Risk Identification and Mitigation Strategy Report

A008 Data Models and Logical Data Diagrams

3.1.2 Performance Management Integration

Tasks

1. Establish strategic planning methodologies and techniques to create goals, capture appropriate performance metrics and assess progress to facilitate delivery of analytical long range planning. Including (but not limited to) monitor and track performance of CDO strategic goals and management initiatives.

The government estimates that 3 consultants will be required to perform these work processes. This is just an estimate. The Contractor, may thru its own analysis determine that more or fewer personnel are required based on its analysis.

A009 Progress reports on CDO strategic goals and management initiatives using established methodologies.

3.1.3 Data Analytics

1. Monitor cutting edge technologies, trends in data science in academic, commercial, federal agency, and the defense industry in order to identify innovations and best practices applicable to Acquisition Visibility. Design and implement analysis infrastructure and tools, assess workflow processes, and prepare complex data visualizations

2. Design and Code scripts to complete ad hoc data extract and reporting tasks as requested by organizational leaders. Perform data extracts and loads from source data systems to analytical data stores

3. Employ DCMA existing Business Intelligence software (eg. Power BI/Power APPS) tools to support data analytics

4. Work with business leaders to solve business problems by understanding, preparing, and analyzing data to predict emerging trends and provide recommendations to optimize business results. Perform in-depth analysis and conduct informational briefings for DCMA and OSD leadership as well as other stakeholders.

5. Identify opportunities to develop and deploy predictive analytics capabilities that enable defense leaders to identify and mitigate acquisition program challenges before a program performance crisis develops

6. Respond to short notice requests for information, supporting data-based decision-making with advanced data analytics

Deliverable

A010 Fully documented and executable data extract scripts A011 Implementation documentation for new/refined predictive data analysis capabilities

3.1.4. Surge

1. Upon issuance of a contract modification, the contractor shall surge within 30 days by one Technical Consultant – Intermediate to support additional data analytics tasks in support of DCMA requirements or other USD (A&S) directed strategic analytics requirements.

Deliverables

A012 White paper report of a detailed analysis of extractable and actionable acquisition data.

A013 White paper report of predictive analytics capabilities.

3.15 Deliverables

DELIVERABLES SCHEDULE

PWS

Task#

Deliverable Number

Deliverable Title Frequency/Tim e-frame/Date

Format and or Template

Quantity

Annually

3.1, 3.2, 3.2.1, 3.3, 3.3.1, 3.5.1.1

A001 Monthly Progress Report Monthly Microsoft Word, Excel, PowerPoint, Visio, PDF

3.1, 3.2, 3.2.1, 3.3, 3.3.1

A002 Quarterly Project Status Briefings

Quarterly Microsoft Word, Excel, PowerPoint, Visio, PDF

3.1, 3.2, 3.2.1, 3.3, 3.3.1, 3.5.1

A003 Ad-Hoc Reports and Briefings as Required

Various Microsoft Word, Excel, PowerPoint, Visio, PDF

NTE: 12

3.1.1- 2 A004 Initial Survey of DCMA Data Analytics landscape and how DCMA can utilize other DoD

Annually, within 45 days of

Microsoft Word, Excel, PowerPoint, NTE: 1

PWS

Task#

Deliverable Number

Deliverable Title Frequency/Tim e-frame/Date

Format and or Template

Quantity

Annually and industry approaches for data monitoring and strategic tend analysis contract start Visio, PDF

3.1.1-1 A005 Strategic and operational plans pertaining to policy changes and new opportunities arising in data exploitation

Quarterly Microsoft Word, Excel, PowerPoint, Visio, PDF

NTE 4

3.1.1-2-5 A006 Analytical Reports on Data Automation Implementation/Refinement, Risk Analysis

Quarterly Microsoft Word, Excel, PowerPoint, Visio, PDF

NTE 4

3.1.1-4 A007 Risk Identification and Mitigation Strategy Report

Monthly, as new Risks are identified

Microsoft Word, Excel, PowerPoint, Visio, PDF

NTE 12

3.1.1-6 A008 Data Models and Logical Data Diagram

Monthly Visio, PDF NTE 10

3.1.2-1 A009 Progress reports on CDO strategic goals and management initiatives

Quarterly Microsoft Word, Excel, PowerPoint, NTE 4

Deliverable Number

Deliverable Title Frequency/Tim e-frame/Date

Format and or Template

Quantity

Annually using established methodologies

Visio, PDF

3.1.3-2 A010 Fully documented and executable data extract scripts

Various Text or other executable file

NTE 26

3.1.3-4-5 A011 Implementation documentation for new/refined predictive data analysis capabilities

Monthly Microsoft Word, Excel, PowerPoint, Visio, PDF

NTE 12

3.1.4-1 A012 White paper report of a detailed analysis of extractable and actionable acquisition data.

Bi-Annually Microsoft Word, PDF

NTE 2

3.1.4-1 A013 White paper report of predictive analytics capabilities

Bi-Annually Microsoft Word, NTE 2

3.2 Dashboard and Data Visualization Support (Functional Area 2) (Low code/no code- in POWER BI, POWER APPS, ADVANA, and QLIK)

The Contractor shall perform the following work streams:

1. Support the creation of data visualizations for a wide variety of acquisition data, and data analytics of structured and/or unstructured acquisition data

2. Conduct data quality analysis, investigate cross-pollination/correlation of data, and support requests for non-standard/ad hoc reporting.

The government estimates that 2 consultants may be required to perform these work processes. The Contractor, may thru its own analysis determine that more or fewer personnel are required based on its analysis.

Deliverables:

A001 Monthly Progress Report A002 Quarterly Project Status Briefings A003 Ad-Hoc Reports and Briefings as Required.

3.2.1 DATA VISUALIZATION SUB-TASKS:

The Contractor shall perform the following sub-tasks:

1. Perform Data Visualization support to communicate information clearly and efficiently to users via the information graphics selected, such as Data Models, tables and charts

2. Review and update the Acquisition Visibility Data Framework. Determine how the AVDF must be updated to govern the data that support the new capability. Review applicable Federal Law as well as DoD Regulations, Policies, and Guidance (LRPG), update the Acquisition Visibility Data Matrix, create business rules and data rules based on the LRPG, and document changes in an initial Data Governance Package

3. Conduct Data Quality and Data Quality Assurance to ensure acquisition data's fitness for use and analysis, verifying the reliability and effectiveness of the data. Data quality factors to monitor include Accuracy, Completeness, Recency, Relevance, Consistency (within and across data sources), Reliability, and Accessibility.

A002 Quarterly Project Status Briefings A003 Ad-Hoc Reports and Briefings as Required A014 Conduct Data Quality and Data Quality Assurance to ensure acquisition data's fitness for use and analysis, verifying the reliability and effectiveness of the data. Document findings in a white paper.

3.3 APPLICATION DEVELOPMENT SUPPORT (Functional Area 3)

The contractor shall support the following work streams:

1. The contractor shall provide information systems engineering expertise, combining an understanding of software engineering, systems architecture, mathematical analysis, data management, and computer science to support the design, development, testing and maintenance of DCMA training/compliance applications identified. Deploy enhancements as identified and scheduled.

2. Employing systems engineering expertise and an understanding of DoD 8000-Series information security requirements, the contractor shall advise on the design and support the applications to work within DoD security requirements and common infrastructures and browsers. Additionally, provide technical advice on implementation of identified processes and data standards within the enterprise procurement environment.

3. Contractor personnel supporting this task must have an adjudicated Tier 3 or equivalent (e.g. Access National Agency Check with Inquiries (ANACI) clearance and be loaded into DoD’s Defense Information System for Security (DISS) prior to starting;

and be able to be assigned a common access card (CAC). While much of the time personnel supporting this task may be able to work at the contractor’s facilities or in a decentralized arrangement; the contractor shall anticipate routine in-person meetings.

In addition, there may be periods of high-priority work that require the contractor team (or part of the team) to be present on-site with the government for several days. While on-site, contractor personnel will not have assigned seats or computers;

personnel would be anticipated to bring their own laptops if needed for the work assignment.

4.

Deliverables

A003 Ad-Hoc Reports and Briefings as Required A015 Contracting personnel will have National Agency Check with Inquiries (NACI) clearance and be loaded into DoD’s Joint Personnel Adjudication System (JPAS) prior to starting; and be able to be assigned a common access card (CAC)

3.3.1. APPLICATION DEVELOPMENT SUPPORT SUB-TASKS:

1. Support DCMA leadership in emerging Federal data sharing initiatives

2. Ensure pilot applications are hosted in proper (e.g., PIEE, ADVANA etc.)

3. Identify systems engineering technical considerations and associated problems, issues or conflicts, evaluate current capabilities for effectiveness, and make recommendations regarding scalability.

A003 Ad-Hoc Reports and Briefings as Required A016 Create a technical security and access strategy for emerging Federal data sharing initiatives A017 Identify systems engineering technical considerations. Provide a white paper report

PWS Task#

Deliverable Number

Deliverable Title Frequency/Time-frame/Date Format and or Template

Quantity Annually

3.2.1 A014 Conduct Data Quality and

Data Quality Assurance to ensure acquisition data's fitness for use and analysis, verifying the reliability and effectiveness of the data.

Document findings in a white paper.

Within 15 calendar days following the end of each Quarter

Microsoft Word, Up to four (4)

Deliverable Number

Deliverable Title Frequency/Time-frame/Date Format and or Template

Quantity Annually

3.3 A015 Contractor personnel will have a

National Agency Check with Inquiries (NACI) clearance and be loaded into DoD’s Joint Personnel Adjudication System (JPAS) prior to starting; and be able to be assigned a common access card (CAC)

As required. Issuance of a common access card

(CAC)

As required.

3.3.1 A016 Create a technical security

and access strategy for emerging Federal data sharing initiatives

Semi-annually Microsoft Word, Excel, PowerPoint, Visio, PDF

Two (2) times per year

3.3.1 A017 Identify systems

engineering technical considerations. Provide a white paper report

Semi-annually white paper report, Microsoft Word

Two (2) times per year

3.4 OPTION 1. Artificial Intelligence and Machine Learning Planning and Implementation (Functional Area Four)

Appraise DCMA existing processes & tools to determine the readiness for ML/AI implementation. Implementing AI programs relies on three essential factors. First, tools that can successfully develop, run, and maintain AI software. Secondly, an abundance of data and the tools to prepare them for training the algorithm. Finally, adequate storage resources, preferably in the cloud, so that all data and machine learning models are organized and readily available.

Task

1. Apply a detailed understanding of the impacts of DOD guidance on and DOD Information Security policies impacting the implementation of artificial Intelligence (AI) and machine learning )ML) software and associated capabilities to DCMA’s systems and data environment.

Deliverables

A0018 Document DCMA’s overall readiness to develop and deploy AI/ML application within DoD guidelines.

Provide findings in white paper report.

A0019 Identify appropriate DoD approved AI/ML software for implementation A0020 Identify adequate storage resources needed for AI/ML implementations A0021 Identify other Acquisition Data opportunities to develop and deploy AI/ML application within DoD guidelines.

Provide findings in white paper report.

Deliverable Number

Deliverable Title Frequency/Time-frame/Date Format and or Template

Quantity Annually

3.4.1 A018 Identify opportunities to

develop and deploy AI/ML application within DoD guidelines

Annually White Paper

Microsoft Word, Excel, PowerPoint, Visio, PDF

Not To Exceed (NTE) : one per year

3.4.1 A019 Identify appropriate DoD

approved AI/ML software for implementation

Semi-annually Microsoft Word, Excel, PowerPoint, Visio, PDF

Not To Exceed (NTE) : two (2) per year

3.4.1 A020 Identify adequate

storage resources needed for AI/ML implementations

Semi-annually White Paper Microsoft Word, Excel, PowerPoint, Visio, PDF

Not To Exceed (NTE) : two (2) per year

3.4.1 A021 Identify other Acquisition

Data opportunities to develop and deploy AI/ML application within DoD guidelines

Semi-annually White Paper Microsoft Word, Excel, PowerPoint, Visio, PDF

Not To Exceed (NTE) : two (2) per year

3.5 OPTION - Enterprise Architecture (Data Architecture, Data Management) (Functional Area 5)

Definition:

Data Architecture provides a description of where data exists and how it travels throughout the organization and its systems. It provides the information and tools the data governance body needs to properly make decisions about data policies and standards. This information supports the enterprise architecture, assist the data governance body, product and process owners, and system owners who perform root cause analysis when enterprise-wide data issues, questions, or concerns arise.

3.5.1 Tasks

1. The Data Architect will assist with the design, creation, deployment, and management of the DCMA data architecture domain to ensure its alignment with the BEA and other key references. The data architecture description will include, but is not limited to Unified Architecture Framework (UAF) domain viewpoints and models. The Data Architect will assist with the collection of business and data requirements, and perform analysis on current and future data strategies.

2. The data architecture will be documented using a variety of artifacts, viewpoints, and models that define services and systems and how they interact with data objects, the attributes of those objects, the relationship among the objects, as well as the flow of data (e.g., data exchanges

3. Research and Analysis of the Current State. The Contractor shall support the Government through discovery sessions with the Enterprise Architecture Team and Data Management Committee intended to:

3.5.1.1. Support the identification, collection, and assembly of all current data architecture artifacts, system design documents, technical specifications, stakeholders, and related business process documentation available across the Agency.

3.5.1.2. Assist with the identification, validation, and alignment of business processes to functional requirements.

3.5.1.3. Assist with the identification, validation, and alignment of functional requirements to technical requirements.

3.5.1.4 Assist with coordination and collaboration with stakeholders to document how data is stored, consumed, integrated, and managed by data entities and IT systems, as well as all applications using or processing data.

3.5.1.5 Align logical and physical data assets with business, application, and technology capabilities.

Deliverables

A001 Monthly Enterprise Architecture Progress Report A003 Ad-Hoc Reports and Briefings on alignment of functional requirements to technical requirements A022 As-Is Architecture and Design Documentation Update

Deliverable Number

Deliverable Title Frequency/Time-frame/Date Format and or Template

Quantity Annually

3.5.1.3 A022 Research and Analysis of

the Current State of all current data architecture artifacts, system design documents, technical specifications, stakeholders, and related business process documentation available across the Agency

Quarterly Microsoft Word, Excel, PowerPoint, Visio, PDF

Not To Exceed (NTE) : two (2) per year

3.5.2 Conceptual Architecture Diagrams and Artifacts

Contractor shall develop hierarchical (levels of abstraction) architecture diagrams and artifacts which define the proposed technology and enterprise architecture.

3.5.2.1 The Contractor shall develop the necessary enterprise architecture diagrams. These diagrams shall be developed as described in the Unified Architecture Framework (UAF).

3.5.2.2 Identify and document how data is stored, consumed, integrated and managed by a variety of data entities and IT systems.

3.5.2.3 Provide technical support in the evaluation of data elements, codes, and business rules and data standards.

3.5.2.4 Support the design, creation, publication, management of the DCMA data architecture to ensure its alignment with Business Enterprise Architecture (BEA).

3.5.2.5. Submit data architecture artifacts that will be maintained within the DCMA Enterprise Architecture Repository.

3.5.2.6. Evaluate proposed data sources, sets, and elements and their attributes to ensure proposed data definitions are clear, concise, technically correct and accurately represented in the business processes.

Deliverables

A001 Monthly Progress Report A023 As-Is Architecture and Design Documentation A024 Quarterly Project Status Briefings on Data Environment Documentation A003 Ad-Hoc Reports and Briefings as Required A025 Support the design, creation, publication, management of the DCMA data architecture to ensure its alignment with

Business Enterprise Architecture (BEA).

A026 Conceptual Architecture and Design white paper on the evaluation of data elements, codes, and business rules and data standards as required.

Deliverable Number

Deliverable Title Frequency/Time-frame/Date Format and or Template

Quantity Annually

3.5.2.1 A023 As-Is Architecture and

Design Documentation

Various Unified Architecture Framework (UAF).

Annually

3.5.2.2 A024 Data Environment

Documentation

Various Microsoft Word, Excel, PowerPoint, Visio, PDF

Quarterly

3.5.2.4 A025 Support the design, creation, publication, management of the

DCMA data architecture to ensure its alignment with Business Enterprise Architecture (BEA).

Various Microsoft Word, Excel, PowerPoint, Visio, PDF

Ongoing/Continuous

3.5.2.3 A026 Provide technical support in the

evaluation of data elements, codes, and business rules and data standards.

Various Microsoft Word, Excel, PowerPoint, Visio, PDF

Ongoing/Continuous

4 Transition Period

4.1 Transition-In

In order to ensure continuity of service for DCMA customers there will be a phased transition period spanning 3 – 8 weeks based on the incumbent’s period of performance end date. On the designated start date, the contractor’s project manager will conduct a “kickoff” meeting with the Government representatives in order to establish transition expectations, contact information and review procedures and processes.

Within five (5) days of contract award, the contractor shall submit to the government a Transition-In Plan that will, as a minimum, contain the following elements:

Staffing plan that outlines how the contractor expects to provide fully qualified and available staff by 2 weeks from the start date.

Plan for Department of Defense Common Access Card (CAC) issuance to all contractor staff requiring CAC’s prior to 30-days from start date.

Milestones and measures for achieving full operational capability.

Any other information requested by the Government at the “kickoff meeting”.

At the end of the transition, the contractor shall provide transition reports that summarizes the contractor’s current status, lessons learned from the transition, and a plan of actions and milestones (POAM) for any remaining incomplete transition in actions.

The Government has three (3) business days to review, comment, and approve the Transition-In Plan. The Contractor shall have three

(3) business days to adjudicate comments.

4.2 Transition Out

To maintain continuity of services when the contract ends, the contractor shall submit a thorough transition plan to support a comprehensive knowledge transfer from the incumbent to the Government and/or follow-on contract personnel. The contractor is expected to research industry best practices for constructing a transition plan and submit a quality product. The contractor shall submit a transition plan to the COR for approval within one week after notification of termination or in the case where termination is not applicable, no later than 120 days prior to contract end. The Government has five (5) days to review, comment, approve. Contractor shall have two (2) days to adjudicate comments.

At a minimum, transition activities shall include

A checklist of all items on the transition plan Instructions on how all procedures and operating processes will be communicated to the personnel taking over incumbent duties Identification of all documentation that will be turned over and where it is maintained Timetable on when all transition events will occur Describe how overall knowledge transfer will occur to the personnel taking over those duties.

Describe how incumbent will transition access to all applications and systems.

List of scheduled reviews and other meetings Continuance of standard operations Instructions on how to obtain required badges or clearances, and obtain access to Government data bases Transition out plan

The transition plan must demonstrate an understanding of what is involved in the transition from the current contractor to the successor contractor. It must address all elements of assumption of service and transition to the required service delivery targets.

At the end of this contract period of performance, the contractor shall execute similar transition/cutover training and support to any new contractor selected.

5 Non-Personal Services

The Government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are personal services in nature, or give the perception of personal services. If the contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the contractor's responsibility to notify the Procuring Contracting Officer (PCO) immediately.

6 Period of Performance

The period of performance is for a one year Base with three (3) one-year Options. The anticipated start date is in FY23.

7 Government Furnished Equipment

The Government will provide the necessary workspace for onsite contractors to include desk/work space, telephones, computers, and other items necessary to maintain an office environment. The Government will provide off-site contractors with laptops. Smart phones will be provided to on-call contractors. Government Furnished Equipment (GFE) including laptops, computers, and smartphones will be provided to contractor personnel at the discretion of the Government.

The Government will retain ownership for all Government-furnished equipment described by this PWS and/or its ATTACHMENTs;

and for such other miscellaneous items, materials, supplies, tools, or equipment as may be already in the Governments possession or control or as the Government may later acquire. The contractor may be held liable for any loss, damage, or destruction of Government property resulting from contractor personnel's malicious or negligent acts.

The contractor will account for property in accordance with FAR 52.245-1: Government Property, 52.245-2: Government Property Installation Operation Services, 52.245-9: Use and Charges, DFAR 252-211-7007 Reporting of Government Furnished Property, DFAR 252.245–7001 Tagging, Labeling, and Marking of Government-Furnished Property DFAR 252.245-7002 Reporting Loss of Government Property, DFAR 252.245-7003 Contractor Property Management System Administration, and DFAR 252.245-7004 Reporting, Reutilization, and Disposal.

The contractor shall report any lost, damaged or destroyed Government property within 24 hours of discovery to the Contracting Officer Representative and follow up with a detailed written report within three (3) business days to the Contracting Officer. If alternate tokens are required for network functions those tokens will be issued at a DCMA facility and the contractor shall be responsible for accounting and safeguarding those tokens.

The Government will provide the contractor with access to all computer and network hardware and software necessary to fulfill the requirements of this PWS including ancillary environments, including the DCMA Service Center trouble ticketing environment.

DCMA, however, expressly reserves the right to add, delete, or modify at its exclusive discretion any hardware, software, or access rights at any time during contract performance, based upon what in DCMA’s judgment is necessary to most effectively and efficiently perform the missions.

8. Location and Hours of Operation

8.1Place of Performance

The primary place of performance is the DCMA Headquarters located at 3901 Adams Ave, Bldg. 10500 Fort Gregg_Adams VA 23801.

Upon approval by the COR the following locations may also be authorized:

Remote (as approved by the COR)

DCMA West Region, 18901 S. Wilmington Ave. Bldg. DH2, Carson, CA 90746

DCMA East Region, Hanscom Air Force Base, Bedford, Massachusetts, USA

It is expected that office space will be available on-site DCMA. Key personnel and vendor project manager may work remotely as work permits but shall occasionally work on-site. Telework may be available for additional personnel.

The contractor shall use DCMA’s remote access tools to administer systems in other locations designated by DCMA.

Contractor locations for levels of effort that do not require onsite presence may be authorized by the COR at no additional expense to the Government. Components noted as ‘Primary’ must be supported at the specified DCMA site, on a daily basis, having full responsibility for execution.

a. Hours of Operations

DCMA work periods are generally Monday through Friday, except US Federal holidays, 8:00AM to 5:00PM local time. Employees are expected to be available during core hours, which are 9:00AM to 3:00PM local time. If requested by the contractor, work hours may start as early as 6:00AM and end as late as 8:00PM local time at the discretion of the COR. Work will occasionally occur before or after business hours to accommodate for planned outage required during off-hours or to support OCONUS locations.

Weekend and non-business hours work may be required occasionally for the following circumstances:

Approved tasks required to meet project deadlines

Holiday Day of Observation

New Year’s Day January 1

Martin Luther King Birthday 3rd Monday in January

Presidents Day 3rd Monday in February

Memorial Day Last Monday in May

Juneteenth Holiday June 19th

Independence Day July 4

Labor Day 1st Monday in September

Columbus Day 2nd Monday in October

Veterans Day November 11

Thanksgiving Day 4th Thursday in November

Christmas Day December 25

8.2 Travel /Temporary Duty (TDY)

All travel will be conducted IAW the Joint Travel Regulation. The Government will reimburse for approved travel IAW FAR 31.205-

46. All travel must be requested in advance and approved by the COR in writing. DCMA estimates that the travel requirement will be approximately 30 trips within the Continental United States for an average duration of three days each, per year.

9. Security Requirements

This section shall be considered in lieu of the U.S. Government provided DD Form 254, Contract Classification Specification. The security requirements below shall apply to this effort.

References:

Industrial Security

Executive Order 10865, Safeguarding Classified Information within Industry

Executive Order 12829, National Industrial Security Program; as amended by Executive Orders 12885 and 13691

32 CFR, Part 117, National Industrial Security Program Operating Manual (NISPOM)

FAR, Part 4 ‐ Administrative and Information Matters, Subpart 4.4 (402,403,404)

FAR, Part 52.204‐2, Security Requirements (clause).

DoD Instruction (DoDI) 5220.22, National Industrial Security Program (NISP)

Information Security

Executive Order 13526, National Security Classified Information

Executive Order 13556, Controlled Unclassified Information

32 CFR, Parts 2001 and 2003, Classified National Security Information

32 CFR, Part 2002, Controlled Unclassified Information

DoDI 5200.48, Controlled Unclassified Information (CUI)

DoDI 5230.24, Distribution Statements on Technical Documents

DoD Manual (DoDM) 5200.01, Volume 1: DoD Information Security Program: Overview, Classification, and Declassification

DoDM 5200.01, Volume 2: DoD Information Security Program: Marking Of Information

DoDM 5200.01, Volume 3: DoD Information Security Program: Protection of Classified Information

DCMA-MAN 3301-08, Information Security

Operations Security

National Security Presidential Memorandum‐28 (NSPM‐28) [13 January 2021]

DoD Directive (DoDD) 3600.01, Information Operations (IO)

DoDD 5205.02E, DoD Operations Security (OPSEC) Program

DoDI 5230.09, Clearance of DoD Information for Public Release

DoDI 5230.29, Security and Policy Review of DoD Information for Public Release

DoD 5205.02‐M, DoD Operations Security (OPSEC) Program Manual

DCMA-MAN 3301-06, Operations Security

Personnel Security

Executive Order 13467, Reforming Processes Related to Suitability for Government Employment, Fitness for Contractor Employees, and Eligibility for Access to Classified National Security Information

Executive Order 13488, Granting Reciprocity on Excepted Service and Federal Contractor Employee Fitness and Reinvestigating Individuals in Positions of Public Trust

DoD Directive 5220.6, Defense Industrial Personnel Security Clearance Review Program

DoDI 5200.02, DoD Personnel Security Program (PSP)

DoDM 5200.02, Procedures for the DoD Personnel Security Program

DCMA-MAN 4201-07, Personnel Security

Physical Security

DoD Instruction 1000.13, Identification (ID) Cards for Members of the Uniformed Services, Their Dependents, and Other Eligible Individuals

DoD Instruction 5200.08, Security of DoD Installations and Resources and the DoD Physical Security Review Board

Federal Information Processing Standard 201-2, Personal Identity Verification of Employees and Contractors

DCMA-MAN 3301-04, Physical Security

Facility Security Clearance.

The work to be performed under this contract/order requires NO access to classified information. No facility security clearance (FCL) is necessary.

Traditional Security

All personnel performing on or supporting this contract/order in any way will be U.S. citizens. Contractor personnel must possess the proper background investigation requirements before performing on the contract. Personnel performing work under this contract must have a favorably adjudicated Tier 3 or equivalent background investigation for access to Controlled Unclassified Information (CUI).

Security investigation (within scope) must be completed commencing work on the contract and must maintain the level of security required for the life of the contract.

Contractor employees with an incident report in Defense Information System for Security (DISS) or an equivalent system who have had their access to classified information suspended will not be permitted to fill positions requiring access to classified information on this contract/order. DCMA retains the right to request removal of contractor personnel regardless of prior clearance or adjudication status, whose actions, while assigned to this contract, clearly conflict with the interest of the U.S. Government.

Personnel must have favorable adjudication as stated in DoDM 5200.02 and in accordance with the Revised Federal Investigative Standards. The Contractor will provide sufficient documentation through their Security Office to the DCMA Security Office to show existing favorable adjudication of required investigations. DCMA security personnel will validate proof of existing investigations and adjudications.

DCMA Security uses the DISS or an equivalent system to verify investigations. DCMA Security will make every effort to confirm the investigation type of vendors not in DISS, however, timely results are not common and delays would not be considered a reason for a U.S. Government caused delay.

New investigative requirements will be processed by DCMA Security Office (Attn: Personnel Security) 3901 Adams Avenue, Building 10500, Fort Gregg-Adams, VA 23801-1809. The Contractor will ensure Contractor support personnel submit the appropriate security forms in a timely manner to meet performance requirements.

The appropriate security investigation (within scope) must have been completed or a current up to date investigation must be in process. This contract/action requires a Tier Three (T3) investigation equivalent (ADP/IT-II). Listed below are categories and associated required investigations:

Tier Five (T5) investigation equivalent (ADP/IT-I) Tier Three (T3) investigation equivalent (ADP/IT-II)

To be allowed access to U.S. Government spaces and IT systems, Contractor employees must obtain a DoD issued Common Access Card (CAC). Contractor employees must first be vetted through his or her employer using the DoD-approved process to receive a CAC as outlined in the following documents:

Federal Information Processing Standards Publication 201- 1, "Personal Identity Verification (PIY) of Federal Employees and Contractors"

DoDI 5200.46, Investigative and Adjudicative Guidelines for Issuing the DOD CAC Directive-Type Memorandum (DTM) 08-003- "Next Generation Common Access Card (CAC) Implementation Guidance"

When Contractor employees are no longer supporting this contract, the Contractor is responsible for ensuring that all CACs are returned to the COR for disposition.

Access to U.S. Government computing assets is a privilege, and not a right. Access to these systems can be monitored at any time.

Violations of established DoD policies and procedures can result in the revocation of those privileges.

Contractor employees shall be required to comply with all U.S. Government security regulations and requirements. Initial and periodic security training or briefings will be provided by U.S. Government personnel. Failure to comply with U.S. Government security regulations and requirements shall require the company to provide the U.S. Government with a written remediation/corrective action plan; furthermore, failure to comply with such requirements can be cause for removal and the contractor shall no longer provide service on this contract/order.

Contractor personnel shall comply with all local security requirements including entry and exit control for personnel and property at the U.S. Government facility. When in U.S. Government-owned or controlled buildings or other facilities, Contractor personnel shall display U.S. Government -issued identification badges in accordance with local policy. Lost or misplaced keys, key cards, or badging credentials must be reported to the COR on the first duty day after the loss is detected.

Data Access and Retention.

Access To and Use of U.S. Government Information.

If the Contractor, in the performance of this contract, obtains access to U.S. Government information contained in plans, policies, reports, studies, financial plans, or other products; or data which has not been released or otherwise made available to the public, the Contractor agrees that without prior written approval of the Contracting Officer, it shall not:

a. use such information for any private purpose unless the information has been released or otherwise made available to the public;

b. compete for work based on such information until such information is released or otherwise made available to the public;

c. submit an unsolicited proposal to the U.S. Government which is based on such information until such information is released or otherwise made available to the public; and d, release such information unless such information has previously been released or otherwise made available to the public by the U.S.

Government.

Access To and Protection of CUI

Contractor personnel will have access to “Covered defense information,” or CUI, as defined in 32 CFR, Part 2002. The contractor shall protect CUI, providing “Adequate security,” to the standards identified in the applicable laws, regulations, and government-wide policies. All Unauthorized Disclosures and violations associated with the mishandling of CUI must be reported to the COR within 24 hours of the occurrence.

Contractor personnel will generate, process, disseminate, store, or otherwise handle documents containing CUI. All contractor deliverables shall be marked in accordance with DoDI 5200.48, unless otherwise directed by the U.S. Government. The contractor shall comply with the provisions of the 32 CFR, Part 117, NISPOM and DCMA-MAN 3301-08 in all instances potentially involving classified information. The Contractor shall have a lawful government purpose to access CUI in the following categories with safeguards above and beyond the Basic safeguard controls:

CUI Category Safeguard Controls Above Basic

CONTRACT NO

FNC NO

MFC NO

PERS NO

PROCURE NO

PROPIN NO

PRVCY NO

COMPT NO

The Contractor agrees that, to the extent CUI is received or access is allowed under this contract, CUI shall not be used or disclosed for any purpose other than providing the contract support services to the U.S. Government. The contractor shall not use or disclose CUI for personal or other commercial purpose outside the purposes of this contract. The Contractor further agrees to enter into a written agreement for the protection of CUI and shall protect CUI from unauthorized use or disclosure. A copy of each written agreement shall be furnished to the Contracting Officer. In addition, the Contractor shall obtain from each employee who has access to CUI under this contract, a written agreement (Non-Disclosure Agreement) which shall in substance provide that such employee shall not, during his/her employment by the Contractor or thereafter, disclose to others or use for their benefit, CUI received in connection with the work under this Contract.

When generating, processing, or otherwise working with CUI, the Contractor shall be aware of the potential to generate classified information

The Contractor shall afford the U.S. Government access to the contractor’s facilities, installations, operations, documentation, databases and personnel used in performance of the contract/order. Access shall be provided to the extent required to carry out a program of IT inspection (to include vulnerability testing), investigation and audit to safeguard against threats and hazards to the integrity, availability and confidentiality of data or to the function of information technology systems operated on behalf of DoD, and to preserve potential evidence of computer crime.

Data Retention

At the end of the period of performance of this contract, all items containing CUI provided to the Contractor in support of this contract must be returned to the COR.

Operations Security (OPSEC): There are no OPSEC requirements associated with this contract. The contractor will adhere to all OPSEC requirements outlined in the National Security Presidential Memorandum‐28 (NSPM‐28), Department of Defense Directive 5205.2, "DoD Operations Security (OPSEC) Program. After award, and before beginning services on this contract the COR will provide Contractor employees the DCMA Critical Information and Indicators List (CIIL). Using the CIIL, contractors handling or generating information identified as Critical Information and Indicators must properly safeguard the information as Controlled Unclassified Information. Baseline countermeasures will be employed in accordance with the CIIL.

Physical Security: The contractor shall be responsible for safeguarding all government equipment, information, and property provided for use during the performance of this contract. Contractor employees will ensure all government facilities, equipment, and materials are properly secured.

The Contractor shall ensure all keys or access cards issued…