PWS Treasury Salesforce Services Software_v2.docx

Department of Treasury Performance Work Statement Treasury Enterprise Level Salesforce Software and Services

I. Introduction

Treasury Digital Services (Digital Services) provides public-facing, extranet, and intranet web and Software-As-A-Service (SaaS) solutions via shared service offerings to other Treasury bureaus and offices.

Digital Services will provide Departmental Offices (DO), IRS, Community Development Financial Institutions Fund (CDFI), Bureau of Engraving and Printing (BEP), Financial Crimes Enforcmenet Network (FINCEN), and Bureau of Fiscal Service (BFS) enterprise Low Code Development Platform (LCDP) solutions.

II. Background The Treasury requires the purchase of licenses for BEP, BFS, CDFI, FINCEN, IRS, and DO to implement additional applications using the software, platform, and tools for Salesforce.

III. Statement of Need

Treasury has identified a need for subscription licenses and services for Salesforce applications for BFS, DO, and IRS.

IV. Scope Requirements

Summary The Contractor shall provide the listed products:

A. IRS Business Program Support

1 Background:

Future IRS modernization is predicated on effective execution of Event Driven Architecture, Integration, and Common Services Deliverables. The IRS requires an enterprise platform to accelerate Customer Relationship Management (CRM) capabilities within the IRS customer service and taxpayer domains and to modernize key internal business operations workflows. The Salesforce Public Sector Advanced Foundation Bundle has been identified as the solution that will need to be established and integrated within the IRS in an enterprise compliant and scalable manner. The Salesforce Platform will need to be developed and configured for prioritized IRS use cases as well as scale to future use cases and business needs. Enterprise Services is working with IT and Business partners to lead the design and solutioning of critical platform integrations, programmatic processes, or controls to help the platform abide by recommended integration architecture guidelines and guardrails.

The primary objective of this engagement is to oversee requirements gathering and design, identifying risks, gaps, design alternatives, architecture design, implementation and development services and best practices as they relate to the overall solution design. The contractor will identify and design common application components that can be re-used across the enterprise. The contractor will provide guidance to the implementation team to promote the use of standard application functionality in an effort to avoid overly complex customization and later redesign.

2 Tasks:

Task 1: Shared Support Services The Contractor shall create a Shared Services team to focus on 1) providing functional and technical oversight to all Blueprinting and Build Teams and 2) executing Release Management and Change Management activities across business units. The Shared Services Oversight team will lead program management and technical standards/guidance to the build teams and will be responsible for overseeing that best practices are followed, leveraging solutions built for one business unit to others, and consistent delivery quality across business units.

The Shared Services Team will design and execute the project management strategy and change management strategy and shall scale resources as needed across the various build teams to gain efficiencies and provide specialized support throughout the period of performance and across all task areas. The Shared Services team will manage the Blueprinting Teams and Build Teams

Task 1.1 Program and Project Management The contractor shall provide subject matter expertise, advice, and assistance in support of the overall effort and provide program and project management, including interfacing with IRS leadership in support of all activities related to the day-to-day management and administration of this Task Order. The contractor shall identify corrective actions and areas for increased monitoring of critical path events as well as alternatives to preclude or offset negative variances. The contractor shall provide weekly status reports at the project level and at the program level, aggregating reports from project lines of effort.

The contractor shall keep the program office apprised of progress and results on a weekly basis through engagement in order to enable IRS decision-making before formal work products are delivered. The contractor shall participate in and/or provide input to IRS leadership meetings and engagements as requested. The contractor shall facilitate communications across project lines of effort and ensure information relative to work processes is shared with the project and program teams.

1.2 Blueprinting Team

The contractor shall use “Blueprinting Teams” to develop the necessary documentation, information, and processes related to completing work under this task order. To accomplish this the contractor shall host 1:1 interviews and workshops with executives, IT and Business stakeholders in order to understand current state of people, process, and technology. Where available, the contractor shall review existing requirements documentation for future-state and legacy system architecture. The contractor shall conduct visioning activities to define future state business processes, create the high-level implementation plan, and target architecture.

The contractor shall deliver a Blueprint ahead of development build to ensure alignment with the Business Unit’s vision, requirements, and processes with the contractors’ capabilities on high level architecture, implementation plan, and strategic roadmap ahead of build starting. The contractor shall deliver Blueprints to ensure knowledge sharing and consistency across our teams.

Task 2: Project Build Teams The contractor shall provide functional and technical resources who will deliver features/capabilities every two weeks into a User Acceptance Testing environment for testing by IRS. Build teams shall hold daily stand-up meetings and weekly status update meetings with the IRS BU teams in order to report on daily progress, resolve gaps in understanding, remove impediments and to help progressively clarify User Stories, resolve risks and issues, and re-prioritize refined user stories. The IRS shall have the ability to direct reallocation of support resources and reprioritization of features based on available Build Team capacity.

These Build teams shall provide capacity based, direct support to:

2.1 Office of Chief Counsel (CC)

The Office of Chief Counsel requires a complete platform modernization to replace TLCATS and CASE-MIS while implementing a Litigation Matters Management system as part of its technology modernization efforts over the period of performance for this task order.

The contractor shall provide support for 24 sprints until February 2026, inclusive of support for a nationwide rollout in March 2025 as a continuation of activities started after the January 2025 release.

2.2 Taxpayer Advocate Service (TAS)

The Taxpayer Advocate service is modernizing its internal systems through replacement of these systems with a commercial-off-the-shelf Customer Relationship Management based product. The initial target for this modernization effort will focus on two systems: Taxpayer Advocate Management Information System (TAMIS); which is used internally and is the central system leveraged to document and track all interactions with those seeking support from TAS, and Systemic Advocacy Management System (SAMS) which is used by internal and external submitters to report issues believed to impact multiple taxpayers or involve an IRS system, policy or procedure adversely impacting Taxpayer rights. Additionally, TAS will leverage the inherent capabilities of the CRM solution to expand its online presence through portal functionality implementing new portal capabilities to allow for online submissions, tracking and communication to those it supports.

The contractor shall provide resources to support 7 sprints for an initial production release for Case Advocacy plus 17 additional sprints.

2.3 SPECTRM

SPECTRM needs a CRM that makes use of its existing databases by converting into cloud application would be developed and supported by contractors based on the estimated cost indicated. W&I-CARE-SPEC currently uses the SPECTRM Management Information System (MIS) to plan, coordinate and implement almost all aspects of the Volunteer Income Tax Assistance (VITA) and Tax Counseling for the Elderly (TCE) programs. The new application would use a-Authentication in compliance with SmartlD systems and Cybersecurity standards. The CRM platform should include the ability to receive data automatically from digital VITA/TCE forms in the Taxpayer Digital Communications (TDC) program.

The contractor shall provide resources to support 13 sprints for enhancements.

2.4 Office of Appeals

Appeals Centralized Database System (ACDS) is Appeals' main case management system. It is used by Appeals Officers, Settlement Officers, Managers and Technical Analysts to track case receipts, record case time, document case actions and monitor the progress of the Appeals workload. It contains sensitive information, including Taxpayer identifier information, case status and case action items. It also contains Appeals staffing information, including demographic and experience summaries, time sheets and employee reviews. It also includes the Docket Information Management System (DIMS) which provides an automated listing of docketed cases.

Appeals requires a completely new case management system to replace ACDS and its smaller system Arts Appraisal System as part of its technology modernization efforts over the period of performance.

The contractor shall provide resources to support 18 sprints for an initial production release and support an additional 6 sprints.

2.5 Tax Exempt & Government Entities (TE/GE)

The TE/GE R&A groups will require a comprehensive matter management system that effectively tracks and processes cases including end-to-end processing. This includes appropriate validation, tracking and allocation of user fees; access historic data, receive cases from taxpayers, manually and systemically create cases, assign cases, route cases, work cases, view worklists and case progression, generate letters, link cases, mass printing, review cases, close cases, update Masterfile, customize reports, retain records, and publish disclosable information to Tax Exempt Organization Search (TEOS). The new matter management system will digitalize taxpayer applications and assistance requests within one solution, providing an opportunity to decommission or retire Modified EP/EO Determination System (MEDS), TE/GE Rulings & Agreements Control (TRAC), Letter & Information Network User-Fee System (LINUS), Employee Plans – Exempt Organizations Determination System (EDS) and Employee Plans – Exempt Organization Application Control System (EACS).

The contractor shall provide resources to support 24 sprints and any planned production releases.

2.6 Office of Chief Counsel HQ

Contractor will extend the modernization effort initiated for the Office of Chief Counsel Chicago, Atlanta and Seattle offices, to their Headquarters. This includes identification of IRS CC HQ specific use cases and implementing releases prioritized by IRS CC. IRS HQ processes include published guidance and rulings, as well as the review of significant cases.

The contractor shall provide resources to support 11 sprints for a production release.

2.7 Whistleblower Office (WBO)

Whistleblower Office (WO) e-trak serves as the current case management system. It is used by numerous internal and external stakeholders including WO Analysts, Managers, Program Analysts, Subject Matter Experts (SMEs), Tax Examiners, Tax Exam Technicians, etc. to create a whistleblower claim/s, document all claim actions taken, track claim actions, monitor claim progress, attach supporting documentation to claim, and monitor workloads. It contains sensitive information, including Whistleblower information, Taxpayer identifier information, case status and case action items. It also contains Whistleblower Office staffing information. Whistleblower Office requires a new case management system to replace Whistleblower Office e-Trak as part of its technology modernization efforts.

The contractor shall provide resources to support 24 sprints and any planned production releases.

2.8 Surge Support (Optional Task)

At the direction of the IRS, the Contractor will begin providing the following support for two (2) additional programs:

· User stories: develop the use cases, user stories, and acceptance criteria for the new case management solution through Blueprinting.

· Agile methodology: Utilizing an Agile methodology to deliver the software solution, Work will be performed using industry-standard Agile methods with work planned in two-week sprints.

· Minimum Viable Product: Develop and deliver an MVP. 1) A development environment with the ability to prototype and iteratively build necessary functionality for agreed upon set of WO Use Cases during the blueprint phase 2) Staging environment(s) necessary to iteratively build Integration with impacted core systems and applications outlined during the blueprint phase 3) Provide user access for User Acceptance Testing (UAT) environment necessary to provide preliminary and ongoing feedback

· Develop or configure, test, stage, and release business applications by applying iterative processes utilizing the proposed Agile methodology and a frequent release cycle.

· Design solutions that offer role or attribute-based identity management, authorization, and authentication across all business applications.

Following the Blueprinting phase, the contractor shall provide resources to support 14 sprints for a Project (to be determined by IRS) and another 7 sprints for an additional Project (to be determined by IRS). The contractor shall provide resources to support 18 sprints and any planned production releases.

2.9 Portals

The contractor shall create a single front door approach for external/public facing portals for each of the programs within the IRS Salesforce platform including but not limited to Office of Chief Counsel, Appeals, TEGE, and TAS.

· The approach shall include a scalable model for authenticated access to public taxpayers.

· User interface design and modeling.

Task 3: Enterprise Platform Support

3.1 Platform Operations

The contractor shall provide Platform Operations support with Salesforce Ecosystem expertise to support the IRS IT and Business. The Platform Operations team shall provide industry standard experience and provide recommendations to improve the Salesforce IT and Business implementations in IRS, working in close collaboration with IRS IT and Business. As part of the team the contractor shall:

· Apply Agile methodologies and Human Centered design principles;

· Assist IRS in establishing a Change Control Board for Salesforce ecosystem;

· Assist the IRS Security team in maintaining an enterprise ATO;

· Provide strategic planning advice and guidance related to identifying and supporting new Platform onboarding candidates, including but not limited to, implementation support, meeting facilitation, preparation of analytical papers, and serving as a liaison with Shared Services team members and component business owners;

· Create, monitor, and enforce standards for development on the platform that align with industry best practices.

· Provide Centralized DevOps strategy and pipeline to coordinate development efforts across programs.

· Assist IRS Business and IT with creation of road maps, workflows, slide decks, development of project plans and Agile sprints that support the selection and on-boarding of selected components;

· Support Product Team on-boarding activities, including, but not limited to:

3.2 Platform Execution

The contractor will provide an execution team to implement new enterprise capabilities on the CRM Platform. This will encompass development, deployment, and transition strategies, including planning, designing, scheduling, testing, deploying, and maintaining enterprise software releases. The contractor shall employ a capacity-based agile delivery methodology and collaborate with the IRS to prioritize backlog items, which may include:

· Conducting comprehensive and detailed assessments of the Salesforce CRM platform

· Developing a CRM platform record retention framework

· Establishing and maintaining a single, consolidated enterprise view of CRM architecture within IRS IT

· Developing and implementing a data masking/obfuscation strategy for PII data in lower environments

· Identifying automated regression testing frameworks and tools

· Implementing Shield transactional security policies (e.g., US-only logins) and certificate and key management

· Automating identity management synchronization, including real-time integration with IRS systems of record (e.g., deactivating a user upon termination)

· Implementing proof of concepts (POCs) to validate strategies and approaches (e.g., Kiteworks, ID.me)

· Supporting migration to PingFederate for SSO/identity management

· Supporting the automation of CRM platform onboarding processes

· Implementing and maintaining an enterprise exception logging and reporting framework

· Creating platform-level automation/validation rule bypass mechanisms

· Implementing automatic deactivation of CRM platform users after 90 days of inactivity.

3.3 Tableau Platform Hardening

The contractor shall upgrade and update the IRS’s Tableau Server deployment and provide recommendations to improve the Tableau Server deployment and Business implementations in IRS, working in close collaboration with IRS IT and Business. As part of the team the contractor shall:

· Rearchitect the platform to account for the conversion to role-based offering (RBO)

· Assess workloads on the platform and provide a logical and implement the physical architecture to handle the volume and type of workloads on the system.

· Configure and deploy Data Management + Advanced Management and take these into consideration when architecting platform.

· Develop scripts using the Tableau REST, Metadata, VizPortal API and others to automate key server tasks.

· Conduct knowledge transfer sessions and develop documentation with IRS IT staff as required to facilitate continuity of operations.

· Upgrade the server as appropriate to take advantage of new functionality.

3.4 Analytics Development

The contractor shall provide consultants that will focus on improving existing analytics, designing new analytics, and improving the overall capability of the IRS analytic creator community. Specifically, the contractor shall:

· Rebuild analytics to account for new Data Management functionality (i.e., integrated row level security, prep flows for modeling data, etc.)

· Rebuild analytics to improve performance and visual design.

· Consolidate similar analytics into a cohesive portfolio.

· Custom training and coaching for IRS content creators in best practices to reinforce and expand on eLearning.

· Enabling IRS content creators with best practices to develop analytics in the Tableau ecosystem.

Task 4: Operations and Maintenance The Contractor shall provide Operations and Maintenance following Production stabilization throughout the period of performance. The scope of work includes additional development, testing, management guidance, leadership, and expertise to the IRS team. O&M may also be required to address additional IT mandates, Tax Court changes, modernization efforts, security vulnerabilities, and change requests that cannot be fully planned for ahead of time.

Task 5: Transition Out The contractor will be required to provide assistance to the successor service provider (either the Government or another contractor) to ensure an orderly transition. The Contractor services under this contract are vital to the Government and must be continued without interruption and that, upon contract expiration, a successor, either the Government or another contractor, may continue them.

The Contractor shall develop a transition-out plan for the implementation of project and program management processes and procedures for the Business Systems Planning Office to manage and maintain the new infrastructure.

The Contractor shall execute this plan and enable the transfer of this function from the Contractor personnel to Government personnel. This is to allow the Government to assume responsibility for the project infrastructure support delivered under this PWS. The Contractor shall identify a strategy for accomplishment of this requirement in its Transition Plan (TP). The TP shall describe how the Contractor expects to transfer the knowledge necessary to achieve this objective.

3 Deliverables

4 Agile Build Methodology The Contractor will utilize an agile methodology approach in the MVP, Implementation, and Build Phases. This process will include the creation of a development/scrum team and deliver iteratively in two week build cycles called “sprints.” The number of sprints will be determined by a points driven capacity system based on the complexity of IRS’s prioritized user stories to be completed within 6 months. The contractor will work closely with the IRS to resize and prioritize each sprint to align with the user stories and epics identified during the blueprint process.

As part of the agile methodology, the contractors will conduct daily stand-ups with the IRS to monitor daily process, resolve gaps in understanding, and remove impediments. Each sprint will culminate with a demo where all feedback, defects, and change requests will be documented.

Size each User Story during Sprint Planning Use a standard “Salesforce Point Estimator”, which is a point-based, Fibonacci sequence of numbers (1, 2, 3, 5, 8, or 13) to consider complexity, effort, and doubt. Based on our velocity with similar projects, calculate the expected throughput for each Sprint.

Perform functional testing on each user story to verify working as designed and meets the acceptance criteria outlined in the User Story. User Acceptance Testing is a level of testing in which all aspects of a product are systematically tested to provide IRS with confidence that the system meets its requirements. IRS will conduct testing with resources that, ideally, will be end-users. They will test the system's ability to support the business processes – no changes should be made at this stage unless they are fundamental to their processes. UAT will follow written test scripts provided by Salesforce based on User Stories. The objective of UAT is that the IRS team confirms the system is operating as designed.

Smoke test the newly released application immediately post-deployment.

5 Skills Requirements

The IRS will require contractor capability to provide and demonstrate a high level of expertise, knowledge, and skills related to incident/problem management, project management, development, system administration, requirements engineering, demand management, software development, configuration management, risk management, security management, development toolset management, data-centricity, service orchestrated architecture and industry best practices (such as Agile Methodology) and DevOps to deliver performance-based quality service.

The contractor shall work on the following systems, hardware, and software identified in this PWS. The contractor must demonstrate expertise in the following skill areas:

· Enterprise Case Management solution using IRS selected Salesforce and Mulesoft products

· Business Objects Enterprise (BOE) reports for any Production support related activities

· Enterprise Document and Records Management solution using IRS selected Salesforce, IaaS, and PaaS products

· IRS Authentication Protocols

· HTML page and cascading style sheet (CSS) design

· JavaScript

· General application development technologies and skills

· Relational database theory

· SOAP and RESTful web services

· Authoring materials in XML

· Relational database theory

· Thorough understanding of the FISMA tier and application categorizations.

· Quality Assurance and Business Systems Analysis skills and technologies

· Software testing theory, tools, and automation techniques

· Browser compliance testing

· Section 508 accessibility testing

· Functional and Non-Functional Requirements development

· Requirements Traceability Matrix (RTM) analysis

· Understanding of Agile and DevSecOps principles and frameworks

· Demonstrated understanding of the Agile Scrum framework and deliverables, including the Engineering Workflow Management (EWM) toolset

· Establishing and managing a Program Management Office (PMO)

· Experience creating detailed WBS

· Experience developing Master Project Plans and Integrated Plans

· Experience interfacing with Product Owners and Client Executives

B. Treasury Salesforce Enterprise License Bundle

IRS

Chief Counsel

Taxpayer Advocate Service

IRS Appeals

Tax-Exempt & Government Entities

Innovation Projects (SPECTRUM, TSO, Others)

Customer Community Plus for Public Sector (logins)

BFS/ARC

FINCEN

CDFI

BEP

DO

CLIN 0003 Part Number 2000-SF-02 consists of the following licenses and quantities:Treasury MuleSoft Enterprise License Bundle

Part Number 2000-MULE-02 consists of the following licenses and quantities:

Mulesoft Platform for Counsel and TAS

MuleSoft Platform Expansion

The licenses shall include the following products:

· Products listed above must meet IPv6 requirements

1.1 Government-Furnished Property (GFP)

GFP (to include material, equipment, and/or information) may be provided in the performance of this task order. The following GFP will be provided to the Contractor:

At the end of this task order, disposition of GFP shall be in accordance with FAR 52.245.1.

1.2 Government-Furnished Information

GFI (to include manuals, notes, memos, instruction materials and other information) may be provided in the performance of this task order. See also H.11 and H.27 of the contract. The following GFI will be provided to the Contractor upon task order award.

INFORMATION ITEMS

Corporate Information Model Data Structure

OneSDLC

IRM 2553.35 "Draft Database Design handbook"

IRM Section 2 Information Systems

Network

At the end of this task order, disposition of GFI shall be in accordance with FAR 52.245.5.

1.3 Travel

Travel must be pre-authorized. The COR must pre-approve travel in writing, i.e., in advance of such required travel. Travel and per diem will be reimbursed at actual cost in accordance with the limitations set forth in FAR 31.205-46 and the General Services Administration's Federal Travel Regulations. Profit shall not be applied to the travel costs. Local travel may be required for on-site meetings, etc.

The Contractor shall provide a travel voucher statement for all local travel. The voucher will ensure verification of costs incurred for local travel under the contract is both allowable and reasonable and in accordance with the regulation FAR 31.205.46. The Contractor shall attach the voucher and receipts to the monthly invoice.

For any trip to be authorized, the COR must approve such travel in writing and in advance.

1.4 Reports

The Contractor shall refer to Reports (check only one):

1.5 Access to Government Property and Facilities

The Contractor is allowed limited access to the Government's facilities, as specified below:

Internal Revenue Service New Carrollton Federal Building 5000 Ellin Road New Carrollton, MD 20706

Internal Revenue Service 1111 Constitution Avenue, NW Washington DC 20224

1.6 Inspection and Acceptance

Inspection will be at the same place as performance and delivery unless otherwise specified.

2 General Acceptance Criteria The general quality measures as set forth below will be applied to each work product received from the Contractor under this contract and any resulting task orders awarded.

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

· Clarity - work products 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 work products must satisfy the requirements of the Government as specified herein.

· Format - work products shall be submitted in hard copy (where applicable) and in media defined in the PWS. The work product format may be different in each task order. Hard copy formats shall follow the 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 - work products shall be submitted on or before the due date specified in the task order or submitted in accordance with a later, scheduled date determined by the CO.

Customized Acceptance Criteria (Standard criteria plus the additional elements listed below)

3 Specific Deliverable Acceptance Criteria

3.1 Review of Deliverables

a) The Government will perform an initial review of deliverables, and if problems are encountered during the review, the Contractor must correct them. 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 approximately 15 (fifteen) calendar days from receipt of the deliverable or as otherwise specified in each task order.

b) When the review of a deliverable results in necessary modifications, the Government in accordance with the approved task order schedule shall provide the necessary documentation to correct the deliverable. The Contractor shall be responsible for incorporating the comments in a proper and consistent manner for the final product.

c) These procedures shall not be construed to constitute a waiver on the part of the Government of its rights under FAR Subpart 49.4, entitled "Termination for Default", nor of any other rights or remedies provided by law or under this contract.

3.2 Task Order Period of Performance

3.3 Place of Performance

3.4 Ship To

Unless otherwise specified below, all deliverables/ work products shall be provided to the COR no later than 4:00 p.m. local time on the date(s) specified in the TO.

4 Task Order Administration Data

4.1 Identification Of Government Task Order

The COR designation will be identified by the CO's written designation memo. The CO will identify the (COR/LCOR) via e-mail to the Contractor.

4.2 Key Personnel

The offeror shall identify (in their proposal based on information provided in the table below) certain positions or roles and associated labor categories considered to be Key Positions. The Contractor shall submit the name and resume of the Contractor employee proposed in each Key Position.

The Contractor shall submit the resumes (certified by their respective manager) of the contractor employee(s) that will fill the position(s) identified in the table above.

4.3 Performance Required Beyond Standard Workday

If needed, performance shall be required beyond the standard workday in accordance with (IAW) the contract Section H.10 Standard Workday.

4.4 Security

CO will ensure contractor personnel compliance in accordance with IRS HSPD-12 PIV Procedures Manual.

Incident Reporting (IR): For the licenses, the Vendor must report any security incident to the following Security (POC) Contacts for Treasury Salesforce GSS:

· Name: Kisalya Pathak (K.P.) Title: ISSO Phone: (202) 961-9932 Email: Kisalya.pathak@treasury.gov

· Name: Oluyemisi Omiteru Title: ISSM Phone: (202) 622-2010 Email: Oluyemisi.Omiteru@treasury.gov

· Incidents Inbox: soc@gsoc.treas.gov

4.5 Performance at Government Sites

If any of this task order effort is performed at specified government facilities, the Contractor shall abide by Department of the Treasury Directive (TD) 71-10 regarding provisions for authorized entrance and exit at these facilities.

4.6 Identification/ Badges

The applicable contractor employees shall not begin working under this task order until all security forms have been properly completed and submitted. All contractor employees shall be required to wear identification badges when working in government facilities.

4.7 Personnel Removal and Replacement

The applicable contractor employees are subject to investigation by the Government. Applicable contractor employees who undergo contractor clearances that reveal, but are not limited to, the following, may be unacceptable under this contract: conviction of a felony, a crime of violence or a serious misdemeanor, a record of arrests for continuing offenses, or failure to file or pay federal income tax. The Government reserves the right to determine if a contractor employee assigned to a task shall continue with the task. The Contractor shall agree to remove the person assigned within one day of official notification by the Government and provide a replacement within 5 (five) days. New hires or substitutions of personnel are subject to the contractor clearance requirement.

4.8 Deliverables/ Work Products

All contractor deliverables or work products shall remain categorized as "Official Use Only." The release of any portion must be authorized in writing by the Government.

"The Contractor shall adhere to Section 508 of the Rehabilitation Act of 1973, which requires access to the Federal Government electronic and information technology.

The law applies to all Federal agencies when they develop, procure, maintain, or use electronic and information technology. Federal agencies must ensure that this technology is accessible to employees and members of the public with disabilities. http://www.section508.gov/.

Each Electronic and Information Technology product or service furnished under this contract shall comply with the Electronic and Information Technology (EIT) Accessibility Standards (29 USC section794(d)); this includes all task/delivery orders and product support services furnished in the performance of this contract.

For every EIT product or service accepted under this contract by the Government that does not comply with (29 USC section 794(d)), the Contractor shall, at the discretion of the Government, make every effort to replace or upgrade it with a compliant equivalent product or service, if commercially available and cost neutral, on either the planned refresh cycle of the product or service or on the order renewal date, whichever shall occur first."

4.9 Data Rights

The IRS shall have unlimited rights in all data and products produced in the performance of this Contract, and in all products and data delivered under this Contract (except for restricted purchased products or SaaS solutions), including software, technical data, manuals, or instructional and training material for installation, operation, or routine maintenance and repair of items, components, or processes delivered or furnished for use. "Software," as used in this provision, means computer programs, computer databases, and documentation thereof. The term also includes data identifying its source, functional characteristics, and performance characteristics, and specifically includes the source code, algorithm, processes, formula, and flow charts of the software. The Contractor agrees that all intellectual and data rights in the software shall become the exclusive property of the Internal Revenue Service. With respect to manuals concerning pre-existing Contractor products, the IRS shall have an unlimited license to use copies of these manuals.

If the Contractor creates for the IRS any software ("Developed Software") as specified in the Contract or any task order issued hereunder, all the Contractor's services shall be considered work for hire and the IRS shall have all rights of ownership in the Developed Software. The IRS shall have a non-exclusive right to use any software received from the Contractor to the extent embedded in the Developed Software.

4.10 Restricted Rights Software

Contractor's commercial software and commercial computer software documentation are provided to the IRS in accordance with the terms of the Contractor's written software license that is provided with the Contractor's or third-party equipment purchased by Contractor for the IRS under this Contract. The Contractor represents and warrants that commercial software or computer documentation was developed at private expense and contain confidential information or trade secrets of the Contractor or its suppliers and licensors.

4.11 Quality Control Plan (QCP)

The Contractor shall establish a complete internal QCP for this contract that includes methods for monitoring, identifying, and correcting deficiencies for each performance category. The QCP shall be maintained by the Contractor for them to ensure the requirements are met as specified in the Quality Assurance Surveillance Plan (QASP). The Contractor shall report any performance issues that they found immediately to the COR for discussing remediation options.

4.12 Quality Assurance Surveillance Plan (QASP)

The Government will evaluate the Contractor's performance and software artifacts in accordance with this Quality Assurance Surveillance Plan (QASP) identified herein. The purpose of the QASP is to ensure reliable services and software are provided in accordance with the PWS. This plan shall also ensure acceptable performance and assist in avoiding unnecessary mistakes and delays.

The COR will summarize and document the Contractor's service delivery and software performance utilizing the following categories and standards:

Version-controlled, public repository of code comprising the product, which will remain in the government domain