Draft PMO-OITA-EDP 3 of 4 (002).docx

DRAFT

Enterprise Data Platform – Engineering and Development Support Internal Revenue Service October 8, 2024

1. INTRODUCTION

The objective of this Performance Work Statement (PWS) is to acquire Data Engineering, Data Management and Data Analytics technical expertise. The IRS seeks to acquire proven technical expertise in the Internal Revenue Service (IRS) Domain. This competence is required to successfully create a complex Enterprise Solution for centralized data storage and access to the IRS Enterprise Data Platform (EDP). The contractor shall provide the necessary architecture, engineering, technical advisory, design, development, post deployment and strategic support to the EDP program and build data pipelines, data products, data access, and analytics to support the Information Technology (IT) Modernization at IRS.

The IRS desires to achieve the following EDP objectives:

· Eliminate data related gaps and challenges faced by IRS users and systems

· Build data pipelines to ingest data from source systems, transform as required and load into EDP

· Provide secure access to most current data to users and systems without delay

· Provide self-service reporting and data access capability to users

2. BACKGROUND

The Inflation Reduction Act (IRA) requires the IRS to modernize tax processing systems and enhance taxpayer experience. Some IRA driven key objectives are:

· Enable digital taxpayer services

· Improve analytics and data-driven decision making

· Accelerate IRS’ strategic transformation

The Enterprise Data Platform (EDP) facilitates the integration of data into the enterprise data lake and provides platform services to ensure data accessibility across the organization. EDP is built on a managed service- TCloud (FedRAMP High), provided by the Department of the Treasury. It will ultimately contain source data from all major tax processing systems as well as support the data necessary to conduct the IRS mission. EDP will also serve as the main source of integrated taxpayer data analytical needs. EDP offers below key services and their key components:

· Enterprise Data Services: Centralized storage of taxpayer data in various formats as well as core operations & maintenance and data management services.

· Transactional Data Stores

· Application Data Stores

· Analytical Data Stores

· API Data Stores

· Data Interfaces: Streamlined data access to enable efficient integration and self-service access for employees and taxpayers.

· Internal APIs

· External APIs

· System Connectivity

· Data Extracts

· Business Intelligence and Analytics: Suite of hosting, analytics, software, licensing, and reporting tools & services.

· AI/Machine Learning Tools

· Reporting Tools

EDP will improve IRS taxpayer, employee, business, and technology objectives by modernizing the way data is utilized by providing internal and external stakeholders a single source for data. EDP will enable the IRS to effectively leverage centralized secure storage and access to data to enable transformation and modernization efforts and meet legislative mandates. EDP will:

· Transform tax processing by providing near real-time access to data.

· Inform data-driven decision making by providing secure, trusted access to data.

· Improve compliance and fraud detection by providing analytical data and services.

· Support IRA and modernization goals by providing foundational data services and data products.

To achieve this, the IRS intends to utilize this contract support to provide the necessary Architecture, Engineering, Design, Development, Testing, Deployment, Security, and OneSDLC expertise.

3. SCOPE OF WORK

The Contractor shall provide technical expertise and strategic advisory services to the EDP Program as applicable, including in areas such as strategic planning, architecture, design, solutioning, maintenance and enhancement support.

Outlined below are the support activities that the contractor is expected to support, analyze, and implement. The Contractor shall provide highly qualified personnel with the capability, experience, and understanding of the systems, architecture, principles, tools and technology involved in this work. The personnel supporting this effort are expected to be subject matter experts with past experience in the capabilities IRS looks to achieve and be prepared to deliver services and deliverables that meet or exceed acceptable quality levels outlined within this PWS.

· Create Data Pipelines and provide maintenance and enhancement for a year concerning the assigned data domain/s in both data domain store and universal data hub.

· Create Data Access Services for the data domain/s assigned in both data domain store and the universal data hub.

· Create Unified Data Model for the data domain/s assigned in both the data domain store and universal data hub.

· Support building Semantic layer for EDP.

· Develop security entitlements for data access per IRS Enterprise Cyber Security policies.

· Engage all IRA programs for their needs and onboarding planning.

· Responsible for security assessment, OneSDLC approval including content, updates to the artifacts, and implementing security controls for the data domain assigned.

· Provide Program/Project Management/Release Management/Risk Management support for the assigned data domains.

· Document plans, code, deliverables, status reports as required, provide walk throughs and presentations, and training for the domain assigned.

· Provide advanced analytics support to EDP. This will require building data products in support of data analytics.

· Advanced analytics support includes but is not limited to data ingestion in UDH, Domain Data Store, building data access services if required and building & deploying analytics models.

· Provide end to end development, maintenance, and enhancement support to EDP for the analytics data products.

· Technology including not limited to: AWS RDS Postgres, AWS Redshift, Databricks, MongoDB, DynamoDB, Exploring AWS Aurora, AWS EKS, Data Integration done by on-prem Informatica, EFTU, Databricks ETL, Informatica Metadata (EDC, Axon), Immuta, other supporting AWS services, Advance Analytics Platform (AAP) with Analytics (AI/ML) services, Business intelligence by on-prem Business Objects (BOE), Tableau, IRS PowerBI integration, IBM Rational Suite, IBM Data Architect, and Mainframe Legacy – JCL, COBOL for z/OS, COBOL, and DB2.

4.0 TASKS

4.1 Data Pipelines and Data Access – Development, Modernization, Enhancement (DME) (Task 1)

4.1.1 The Contractor shall:

· Support EDP PM to collect and document software requirements that define the scope of each data pipelines release/s.

· Create logical and physical data models by the data domains assigned by IRS for analytical use case in Databricks.

· Develop document database layout for pipelines feeding transactional / operational databases in MongoDb, RDS PostGreSQL, DynamoDB

· Load historical and incremental data from IRS on-prem modern and legacy mainframe source systems to EDP analytical zone in medallion architecture. The data load tools include but are not limited to Informatica, EFTU, Databricks ETL.

· Follow the standards and guidelines set by EDP and Solution Engineering.

· Support with implementation of data management including metadata, lineage, and data catalog.

· Provide maintenance and enhancement post deployment and provide timely resolution of issues.

· Create data pipelines to load API database where required.

· Build reports/dashboards/SQL in assigned.

· Possess knowledge and experience in developing and implementing semantic layer using tools like Starburst, Dremio etc.

· Engage with all IRA programs and other IRS programs to gather data needs and challenges.

· Have strong PL/SQL skills to convert existing Greenplum, Oracle etc. stored procedures into Databricks compatible code.

· Build data products to support advanced analytics and test using the relevant data analytics models to make sure data product meets the requirements.

· Perform all testing including system testing, integration testing, performance testing, 508 testing etc. as required by IRS policy.

· Coordinate with EDP platform team for planning of platform capacity.

· Make sure data at rest and in transit is secure.

· Make sure UNAX policy is not violated.

· Participate and support security assessments and updates of security artifacts.

· Create unified work requests (UWR) and change requests (CR) and follow through where and when required.

· Provide business intelligence capability, using tools such as Tableau, Business Objects, Jupyter Notebook etc.

4.2 Operations and Maintenance (O&M) (Task 2)

O&M of EDP systems need to be performed to maintain all projects at an optimal level.. O&M support includes providing analytical and technical support to EDP domain applications during scheduled and ad-hoc operations/maintenance windows and assisting in the support and maintenance of EDP Systems in all areas of software configuration management and technical support.

Legislative changes to the tax code, at times, will require changes to existing systems that are under O&M. This section is seeking support that includes the activities needed to support approved development, including routine annual changes. Support includes, but is not limited to, yearly updates to existing capabilities and infrastructure. Support may also include minor business changes and changes that increase efficiency and reliability. Incident Management Process Support of P1 to P4 tickets are also worked, depending on prioritized resource availability.

O&M does NOT include new projects and/or significant changes/modifications to existing IT systems to improve business capabilities, performance levels, IT modernization, and/or process improvement activities. Significant changes are defined as coding and deployment updates in excess of 200 hours. The Contractor shall work as part of an Integrated Project Team (IPT) that consists of project stakeholders, EDP management and staff and representatives from IRS organizations external to EDP.

4.2.1 The Contractor shall:

· Provide post deployment support for Operations and Maintenance (O&M).

· Participate and provide support in the creation of tickets, fix, communication, and documentation concerning the resolution of incidents for their scope of work.

· Aiding and supporting as needed, to sustain the day-to-day operations of production databases and/or applications associated with participation in Service Restoration Team conference calls, outside of normal business hours, i.e., overnight and weekends.

· Providing 24x7x365 support services and routine system operations and data loads as needed. The services included are system administration, help desk, and sustaining engineering (engineering support for operations, including analysis of operational data, and performance of special studies).

· Participating in service restoration, root-cause analysis, and/or corrective action processes. Providing program cost modeling and analysis; service level agreements; tracking and analysis metrics; maintaining performance scorecards; documenting and maintaining service inventories; and providing periodic updates, analysis, and recommendations of the Operations Administration and Maintenance Plan.

· Monitoring and reporting system performance based on workload and statistical analysis, based on system and application activities.

· Performing preventive, predictive, and corrective maintenance including troubleshooting and resolving problems found in the production code, as needed.

· Provide maintenance support to the business intelligence deliveries.

4.3 Program and Project Management - DME (Task 3)

4.3.1 The Contractor shall:

· Provide monthly Program/Project Management/Release Management/Risk Management support for assigned data pipelines and access methods.

· Create individual project schedule that integrates with the integrated master schedule.

· Develop and / or update all oneSDLC artifacts per IRS policies and take the project through OneSDLC exit.

· Create unified work requests (UWR) and change requests (CR) and follow through where and when required.

4.4 Contract Activity and Status Reporting (Task 4)

The Contractor shall:

4.4.1 Deliver weekly progress reports to report status against outcomes, against project budget, and schedule expectations. Weekly reports shall describe the accomplishments (activities and deliverables). The weekly progress shall include a cumulative assessment of performance (Quad-Chart report to be delivered to ACIO-Enterprise Services).

4.4.2 Provide a bi-weekly Report (Quad-Chart) that includes a list of deliverables and submission dates. All deliverables shall be on time, complete, and accurate, requiring no rework. Refer to Deliverables Table in Section 5 for format and frequency of the Contractor Status Report.

4.3 Provide Monthly Status Reports (MSRs) may include the following:

a) Activities during the reporting period, by task (include ongoing activities, new activities, activities completed, unified work request assessments, and development progress with to date completion percentage). Each section shall start with a brief description of the task.

b) Any problems and corrective actions taken. Also include issues, concerns, and proposed resolutions to address them.

c) Staffing Matrix to include understanding staffing issues/concerns and proposed resolutions to address them, personnel gains, losses, and status (security clearance, GFP/E inventory etc.)

d) Schedule (display major tasks, milestones, and deliverables; planned and actual start and completion dates for each)

e) Accumulated invoiced amount for each CLIN up to the previous month allows Contracting Officer, EDP Government Project Managers, and CORs to:

· Validate hours.

· View budget burn rates and financial information.

· Responses to monthly RACF (Resource Access Controls Facilities) Violation Reports, monthly invoice reconciliation reports, and ad hoc reports upon request.

4.5 Contract Start-Up (Task 5)

The contract start-up activities shall be the basis of how the government will provide administrative oversight to this contract.

The Contractor shall:

4.5.1 Provide a Point of Contact (POC) within one (1) business day of the contract award that shall:

· Be assigned to work with the COR concerning the on-boarding process from date of the award.

· Be available by mobile and email in case of unscheduled events such as government closures by the Office of Personnel Management.

4.5.2 Conduct a Kick-Off briefing for the Government within two weeks of the task order award. The Government does not desire an elaborate orientation briefing, nor does it expect the Contractor to expend significant resources in preparation for this briefing. Rather, the intent of the briefing is to initiate the communication process between the Government and Contractor by introducing key task order participants, explaining their roles, reviewing communication ground rules, and assuring a common understanding of task order requirements and objectives.

The orientation briefing shall be held at the Government's facility or virtually and both parties shall mutually agree upon the date and time. The completion of this briefing shall result in the following:

· The contractor and Government personnel who will perform work under this task order will be introduced.

· The Contractor shall demonstrate confirmation of their understanding of the work to be accomplished under this PWS.

· The Government will address any issues concerning the contractor clearances and government furnished property requirements for contractor personnel.

4.5.3 Complete all required security training and paperwork. To date, there has been an average of 60-90 days of processing time for the Minimum Background Investigation (MBI) paperwork. Staff resumes shall be submitted within three business days of coming on board for approval by the government Program Manager. While the MBI paperwork is being processed, the Contractor shall provide support on a labor hour basis during this period, while Contractor Key Personnel and other required Specialists submit the proper paperwork. If Contractor Key Personnel has received government investigation approval, monthly payments will not be affected.

4.5.4 Ensure all staff complete mandatory training within the first 30 days of coming on-board.

4.5.5 During the first 90 days, the Contractor shall start drafting and finalizing policies, plans, processes, procedures, and other related technical documentation needed for this project.

4.5.6 Work with the Government to finalize the Quality Assurance Surveillance Plan (QASP), payment schedule, deliverables official start and end dates, other administrative documents as needed.

4.5.7 Develop a government-furnished Contractor Status Report document and provide to the COR to include MBI requests, Badge numbers, laptop series numbers, parking requests, assigned seating locations, training statuses, and AIRs (actions, issues, risks). Refer to Deliverables Table in Section 6 for frequency and format of Contractor Status Report.

4.6 Transition to Support (Task 6)

The transition to support process shall include, but not be limited to the below tasks. The desired outcome is a Contractor-provided Transition Plan that identifies transition to support knowledge transfer from Contractor to Government personnel and, if applicable, to another Contractor, and executes plan on agreed start date. The Contractor shall provide uninterrupted support services that enable effective transition of services.

4.6.1 The contractor shall provide Knowledge transfer of technical materials and lessons learned to IRS staff upon completion of deliverables.

4.6.2 The contractor shall execute a transfer of complete documentation for all delivered functionalities. Deliverables shall be in softcopy and hardcopy format (as required) and shall be the sole property of the federal government. The format of deliverables shall be provided in a format which shall allow the government to modify and update when/if necessary.

4.6.3 The contractor shall execute Knowledge transfer of configurable data including usernames, passwords, and application settings.

4.6.4 The contractor shall support planning activities, staff management, schedule management, issue and risk tracking and reporting, report generation, quality assurance, management, and technical review support.

4.6.5 The Contractor shall conduct training sessions with training materials, as required by the Contracting Officer’s Representative (COR), during the transition period to ensure uninterrupted performance of on-going support activities.

4.6.6 The Contractor assures that IRS-identified staff receives a complete handoff of all information needed to maintain the programs the Contractor has designed, maintained, tested, and implemented. Knowledge Transfer is limited to on-site experience with the system by IRS-identified staff working with Contractor staff, as well as informal training which the Contractor may perform during the contract.

5. DELIVERABLES

The Contractor shall provide all deliverables to the Government PM and the COR. The format will be agreed upon by the Contractor and Government at the start of performance. Inspection and acceptance of the deliverables shall be performed in accordance with the Quality Assurance Surveillance Plan (QASP). The following table outlines the deliverables:.

4.1.1.0 Build Data Pipelines and Data Access – DME

Every 3 months from the award date

Assigned Govt. Technical Point of Contact and Project Manager

Solution

and corrections delivered and ready for use (go-live for end users)

Following every release Assigned Govt. Technical Point of Contact and Project and Assigned Govt. O&M Lead Manager Assigned Govt. Technical Point of Contact and Project and Assigned Govt. O&M Lead Manager

4.3.1.0

Program and Project Management – DME

As needed

Assigned Govt. Technical Point of Contact and Project Manager

Assigned Govt. Technical Point of Contact and Project Manager

OneSDLC exit checklists oneSDLC: with every release

Assigned Govt. Technical Point of Contact and Project Manager

6.0 QUALITY MEASURES

6.1 General Acceptance Criteria:

The Contractor shall perform all tasks and provide all deliverables identified in this PWS during the Period of Performance. All tasks and deliverables must meet the performance standards or Acceptable Quality Level (AQL) as specified in the contract Quality Assurance Surveillance Plan (QASP). IRS will have ten (10) business days to review and rate deliverables on the timeliness and quality of each product. Subsequently, the Contractor shall update the deliverable within five (5) business days of receiving IRS comments.

The general quality measures as set forth below will be applied to each deliverable received from the contractor under this contract and any resulting orders awarded.

· Accuracy - Deliverables shall be accurate in presentation, technical content, and adherence to accepted elements of style.

· Clarity - Deliverables shall be clear and concise; engineering terms shall be used, as appropriate. All diagrams shall be easy to understand and relevant to the supporting narrative.

· Specifications Validity - All deliverables must satisfy the requirements of the Government as specified herein.

· Format – Deliverables shall be submitted in soft copy (where applicable) and in media defined by the IRS. The deliverable format may be different in each award order. Soft copy formats shall follow Department of the Treasury and IRS Directives and shall be consistent with other similar efforts. All text and diagrammatic files shall be editable by the Government.

· Timeliness - Deliverables shall be submitted on or before the due date specified in the award order, or submitted in accordance with a later, scheduled date determined by the CO.

Build Data Pipelines and Data Access – DME (Task 1)

· Source code in Bitbucket/Github

· Test plan and test scripts

· Deployment scripts

· Functional and non-functional requirements Architecture and design

Customer Satisfaction Live Demonstrations

New/Updated Requirements Documentation delivered by due date

Deliverables are of high quality as measured by changes required for IRS acceptance

Testing with all user requirements addressed with minor bug fixes

Customer Satisfaction; satisfaction on a scale of 1-9, where 1 is dissatisfied and 9 is satisfied.

95%-Acceptable quality level consistent with deliverable acceptance upon contract award

Maintenance and Operations – O&M (Task 2)

· Incident reports

· Analysis, resolution testing documentation Lessons learned

Frequency: Following every release

100% Inspection-Contractor delivers electronically. I

90%-Acceptable quality level consistent with deliverable acceptance upon contract award

Project Management (Task 3)

· Project plans

· Integrated master schedule

· OneSDLC artifacts OneSDLC exit checklists

Deliverables are of high quality as measured by changes required for IRS acceptance

Frequency:

One month after award with continuous updates

OneSDLC: with every release

100% Inspection-Contractor delivers electronically.

Contract Activity and Status Reporting (Task 4)

Reports

Report Generated by due date

Contract Start Up (Task 5)

Presentation briefing

Briefing Delivered by due date

6.2 Acceptance of Deliverables

The Government will perform an initial review of deliverables, and if problems are encountered during the review, the contractor shall correct them at no additional cost. If necessary, a meeting may be convened to resolve any differences. The contractor shall make all required changes to achieve an acceptable deliverable. The Government will perform its review within 10 business days from receipt of the deliverable or as otherwise specified in each award. When the review of a deliverable results in necessary modifications, the Government will provide the necessary documentation to correct the deliverable. It will then be the responsibility of the contractor to properly and consistently incorporate the comments in the final product.

7.0 KEY PERSONNEL

The contractor shall identify positions or roles and associated labor categories considered to be Key Positions for the contract. The Contractor shall submit the name and resume of the Contractor employee proposed in each Key Position.

Contractor employees identified as Key Personnel shall be dedicated to this project. If any changes in proposed key personnel become necessary, the contractor shall provide written notification. as soon as possible. For any substitution, the contractor shall submit justification with a proposed substitute whose qualifications are equal to or greater than the person being replaced.

IT Project Manager

Must have demonstrated experience managing at least 3 data pipeline development and management related projects similar in size and scope with federal agencies, PMP or Agile certification desired.

Data Engineering Specialist

Must have demonstrated experience developing data models for implementation in a data lake architecture for projects similar in size and scope.

Data Pipeline Developer

Must have demonstrated development experience with at least 2 project similar in size and scope to transform and load data into Databricks.

Management Analyst

Must have demonstrated requirements gathering for at least 2 IT data pipeline/data warehousing related projects similar in size and scope.

8.0 GOVERNMENT FURNISHED PROPERTY

Government furnished property (GFP) (e.g., materials, equipment, and/or information) will be provided in conjunction with required performance under this task. The following GFP will be provided to the contractor:

Contractor Identification Badge/Smart ID Card

TBD

Contractor Building Access/Proximity Card

Laptops with Local Area Network Access

Office Space (Desk, Chair, Standard Office Equipment) or Location of Hoteling Office Space

Microsoft: Visio, Word, Excel, PowerPoint, Project Access

All contractor employees provided an IRS laptop or similar equipment are required to fully utilize the government furnished equipment (GFE) and conduct all official IRS business on the IRS issued laptop. Government furnished information (GFI) can only be maintained on GFE.

Contractors shall not conduct any IRS business and related tasks on their corporate or personal computers. IRS information will not be sent to a contractor’s corporate or personal email. This includes removable media (i.e., thumb drives.)

9.0 GOVERNMENT FURNISHED INFORMATION (GFI)

The Government will provide Government-Furnished Information (GFI), as required, to support the contractor’s performance of work under this requirement.

The Government will arrange for Contractor access to IRS contractor/subcontractor data, previous studies or information that was used as a basis for development of the IRS business systems, works in progress, deliverables, and other materials essential to perform independent assessments or other activities in support of this requirement This information will include, but is not limited to, requirements and architecture documentation, budget and expenditures information, and various planning and CONOPS documentation for the projects under study.

10.0 TRAVEL

Travel is not anticipated for this requirement and will not be funded under this contract.

11.0 PERIOD OF PERFORMANCE

Base Year: Twelve months from the date of award

12.0 PLACE OF PERFORMANCE

The contractor shall provide services at government and non-government facilities, as agreed upon by government. As approved by the government, the contractor may participate in meetings where relevant project issues are being discussed.

13.0 OBSERVED FEDERAL HOLIDAYS

No Contractor support is required on the following eleven (11) Federal Government observed holidays:

· New Year’s Day (January 1st)

· Martin Luther King’s Birthday (3rd Monday in January)

· Washington’s Birthday (3rd Monday in February)

· Memorial Day (4th Monday in May)

· Juneteenth National Independence Day (June 19th)

· Independence Day (July 4th)

· Labor Day (1st Monday in September)

· Columbus Day (2nd Monday in October)

· Veterans Day (November 11th)

· Thanksgiving Day (4th Thursday in November)

· Christmas Day (December 25th)

14.0 POINTS OF CONTACT

14.1 Contracting Officer (CO)

Name: TBD Address: IRS Procurement

14.2 Contracting Officer’s Representative (COR)

Name: TBD Address: TBD Email: TBD

APPENDIX A ACRONYMS

APPENDIX B – REFERENCES

Listed below are the references that apply to the work to be performed. The Title and Date are current as of the date of award. The Contractor shall be responsible for complying with updates to these references and any changes these may have to the work performed on this contract/order.

IRM 1.15, Records and Information Management February 5, 2021 https://www.irs.gov/irm/part1/irm_01-015-001

IRM 2.16.1, Enterprise Life Cycle (ELC) August 13, 2021 https://www.irs.gov/irm/part2/irm_02-016-001

IRM 2.17.1, Infrastructure Currency, Infrastructure Currency Policy for Software October 26, 2020 https://www.irs.gov/irm/part2/irm_02-017-001

IRM 2.22.1 Unified Work Request (UWR) Process January 27, 2020 https://www.irs.gov/irm/part2/irm_02-022-001

IRM 2.25.2, IRS Portal and Extranet Usage Standard February 26, 2018 https://www.irs.gov/irm/part2/irm_02-025-002

IRM 2.144 Capacity Management October 01, 2019 https://www.irs.gov/irm/part2/irm_02-144-001

IRM 2.148.2, Incident Management Process May 11, 2020 https://www.irs.gov/irm/part2/irm_02-148-002.html

IRM 2.150.2 Configuration and Change Management, Configuration Management August 19, 2020 https://www.irs.gov/irm/part2/irm_02-150-002.html

IRM 10.8 Security, Privacy and Assurance Information Technology (IT) Security September 28, 2021 https://www.irs.gov/irm/part10/irm_10-008-001r

IRM 10.8.1, IT Security Policy and Guidance September 28, 2021 https://www.irs.gov/irm/part10/index.html

IRM 10.5.2, Privacy and Information Protection, Privacy Compliance and Assurance (PCA) Program January 24, 2020 https://www.irs.gov/irm/part10/irm_10-005-002.html

IRM 10.8.21, Information Technology (IT) Security, Database Security Policy November 30, 2020 https://www.irs.gov/irm/part10/index.html

IRM 10.8.22, Information Technology (IT) Security, Web Server Security Policy July 1, 2020 https://www.irs.gov/irm/part10/index.html

IRM 10.8.24, Cloud Computing Security Policy March 20, 2019 https://www.irs.gov/irm/part10/index.html

IRS IRM 10.8.50, Information Technology (IT) Security, Servicewide Security Patch Management November 25, 2020 https://www.irs.gov/irm/part10/index.html

IRM 10.8.60 IRM IT Service Continuity Management (ITSCM) Policy and Guidance July 16, 2021 https://www.irs.gov/irm/part10/irm_10-008-060r

IRM 10.8.27 Personal Use of Government Furnished Information Technology Equipment and Resources May 24, 2022 https://www.irs.gov/irm/part10/irm_10-008-027

IRM 10.8.62 Information System Contingency Plan (ISCP) and Disaster Recovery (DR) Test, Training, and Exercise (TT&E) Process February 24, 2022 https://www.irs.gov/irm/part10/irm_10-008-062

IRM 10.8.9, Information Technology (IT) Security, Virtualization Security Policy.

April 29, 2016 https://www.irs.gov/irm/part10/index.html

IRM 10.23.2, Contractor Investigations April 22, 2022 https://www.irs.gov/irm/part10/irm_10-023-002

IRM 10.23.3 Personnel Security/Suitability for Employment and Personnel Security Operations May 09, 2019 https://www.irs.gov/irm/part10/irm_10-023-003

IRS Directives and Memorandums:

Publication 1075 Tax Information Security Guidelines For Federal, State and Local Agencies Safeguards for Protecting Federal Tax Returns and Return Information https://www.irs.gov/pub/irs-pdf/p1075.pdf

Office of Management and Budget (OMB):

Federal Acts and Programs:

National Institute of Standards and Technology (NIST) Special Publications and Manuals (as listed or applicable current version)

Information System Contingency Plan (ISCP) Tabletop Exercise

Treasury Acquisition Bulletin 15-03 March 18, 2015 https://home.treasury.gov/system/files/281/Acquisition-Bulletin-%28AB%29-15-03.pdf

Federal Information Processing Standards (FIPS) Publication (PUB)