4. SC 5000181885 IRA-END - PWS (updated).docx

DRAFT

PERFORMANCE WORK STATEMENT (PWS)

Internal Revenue Service (IRS)-Enterprise Notices Digital (END)

1.0 INTRODUCTION

The Application Development-Information Technology offices, of the Internal Revenue Service (IRS) seeks support for Development, Modernization and Enhancement (DME) and Operations and Maintenance (O&M) of the Enterprise Notices Digital project in Correspondence Composition System (CCS). The Contractor shall work together with IRS to review, develop, modify and maintain the program in compliance with the IRS’ "OneSDLC".

The IRS is tasked with generating print and digital notices,letters and forms, maintain the enterprise-wide system Correspondence Composition System (CCS) and expand its capabilities (e.g., multi-lingual) for individual and, business taxpayers and tax professionals/preparers as a means of enhancing the taxpayers experience. The Agency is adopting a Vendor-Built model to obtain products and/or services to enable outcomes outlined in the Inflation Reduction Act (IRA). The purpose of this acquisition is to obtain a Contractor provided comprehensive solution and develop new and migrate existing notices, letters and forms using OpenText Exstream software The intent is to obtain a fully functional and operational project that implements print and digital Notices capabilities. The project also addresses external testing of user interfaces, solid correspondence composition solution for generating print and digital communications. The contractor shall adhere to the new delivery model and shall enable the agency to deliver an enhanced customer experience in accordance with the IRS processes.

2.0 BACKGROUND

On July 1, 2019, Congress enacted the Taxpayer First Act (TFA) to amend the Internal Revenue Code of 1986 to codify, expand, and strengthen taxpayer rights and transform the IRS into a more taxpayer-friendly agency by, among other things, developing a comprehensive customer service strategy that includes a more modern technology, and enhanced cybersecurity.

The TFA mandates that the IRS prepare strategic plans affecting the agency's core missions and activities. On January 11, 2021, the IRS sent the Taxpayer First Act Report to Congress; a comprehensive set of recommendations on how the agency can transform the IRS into a modern, efficient, and taxpayer-centric centered agency. The report outlines three (3) overarching strategies:

· Strategy 1: Enhance the taxpayer experience

· Strategy 2: Enhance the employee experience

· Strategy 3: Improve operational efficiencies Strategy 1: Enhance the taxpayer experience.

The Taxpayer Experience Strategy (TXS) identified the taxpayer experience as the “cornerstone” of IRS’ mission and goes beyond customer service to solving problems. TXS encompasses all taxpayer transactions within the IRS; additionally, it crosses services, compliance, and other program areas throughout the lifetime of interactions with the organization.

In 2019, the IRS processed more than 253 million tax returns. As part of tax return processing, IRS corresponds with taxpayers, businesses, and tax preparers by various channels such as web interfaces and postal mail. Figure 1 provides key online correspondence metrics with taxpayers.

Figure 1-IRS Business

3.0 OBJECTIVES

The purpose of this PWS is to obtain Contractor technical support services and subject matter expertise to design, configure, customize, develop, integrate, implement, and support the project in enhancements, upgrade, migrate, maintain, and sustain day-to-day O&M, project management, software development, and developmental O&M works for the Enterprise Notices Digital project in Correspondence Composition System (CCS) which leverages Opentext Exstream software to produce the Notices, Letters and Forms for end user taxpayers. Additionally, PostrgreSQL is used by OT for underlying metadata and data received from calling applications. The notices use the object buckets in Enterprise Container Platform (ECP), similar to AWS S3 services. The solution will be in IRS/treasury cloud utilizing several AWS services. The project will be developed and maintained on IRS/Treasury Cloud environments and/or on premises.

The enhancement Enterprise Notices Digital Correspondence Composition System (END-CCS) is a component of Notices Conversion that will implement Print and Digital Notices capabilities at the IRS for letters, notices and forms. The current notice generation product is called OpenText xPression which is being phased out, and the project team will be leveraging the OpenText Exstream product to deliver a 508-compliant correspondence solution that provides multi-lingual capabilities in both print and digital format. The project team has to migrate all existing xPression IRS notices utilizing the new product and maintain the notices in the IRS/Treasury cloud. The project team will develop Java-based microservices on premises and then move to Treasury Cloud AWS.

The project identifies various stakeholders that rely on the IRS for information and services. The IRS will generate customized taxpayer notices and letters accessible through online accounts.

3.1 Expanded Digital Services

IRS online accounts and services will allow taxpayers to access and view their notifications (Notices and Letters) in a digital format.

· Digital Notifications: Generate customized taxpayer notices and letters accessible through online accounts. Online accounts allow Taxpayers to opt-in to receive personalized notifications about changes to their tax situation, payment reminders and status updates on refunds or audits.

Desired Results:

· Notifications about changes to tax situation, and audit status and payments through Business Online Account (BOLA), Individual Online Account (OLA), and Tax Preparer Online Account (TaxPro)

· Secure upload and sharing of files with the IRS

· Communication in preferred language through preferred communication channels

The CCS solution will enhance print and digitization of notices and expand the languages currently supported, thereby enabling taxpayers to obtain status in near to real time in numerous ways.

3.2 Focus Strategies for Reaching Underserved Communities

Provide online services to underserved communities include but not limited to:

· Multilingual Forms, Publications, and Notices: Support multilingual publications Notices, Letters and forms, issued to taxpayers with limited English proficiency. Increase the languages (Spanish, Chinese Traditional/Simplified, Korean, Russian, Vietnamese) available online in a digital format.

· 508 Compliance: Support taxpayers with disabilities, including taxpaying populations needing special assistance due to sigh, hearing, dexterity, limited mobility, and cognitive challenges.

Desired Results:

· Communication in preferred language through preferred communication channels

· Understanding of tax obligations and easier access to the tools that lead to compliance.

3.3 Taxpayer Experience Office (TXO)

On March 4, 2022, the agency created The Taxpayer Experience Office (TXO), dedicated to delivering and improving taxpayer transactions with the IRS across the service, compliance, and other program areas, working in conjunction with all IRS business units and coordinating closely with the Taxpayer Advocate Service. To help drive the IRS strategic direction for improving the taxpayers experienced, TXO has identified key capabilities the IRS is focusing on over the next five years and captured this in the Taxpayer Experience Strategy (TXS) Roadmap. The roadmap outlines a high-level plan to advance TXS capabilities from FY2022- 2025. Business Online Account (BOLA) and Digital Notifications were identified as two (2) of the top capabilities to be implemented starting in FY23.

· Objective: Increase Access and Promote Transparency and expand digital services

· Capability Group: New Service Channel

· Business Online Account: Provide online accounts and services for businesses.

· Digital Notifications: Enable users to view digital notices associated with their business; Modernize notice processing (i.e., new digitization tool) to increase the pace of digitization (15-20 top priority notices) In addition to the TXS and associated TXO Roadmap, the IRS Modernization Plan (April 2019) included initiatives to improve how the agency interacts with taxpayers and the community, while continuing to strengthen cybersecurity protections and information technology systems. The modernization plan needs to be used in conjunction with the TXS for the proposed Digitized Notices solution.

Figure 2-Taxpayer Experience Framework

3.4 Inflation Reduction Act (IRA) and Enterprise Modernization Goals On August 16, 2022, Congress enacted the Inflation Reduction Act (IRA) which aims to curb inflation by reducing the deficit. The historic down payment will help the IRS cover new and reinstated tax laws that will affect individuals and businesses, including several credits and deductions, over the next 10 years. These funds will help in many areas, including adding critical resources to not just close the tax gap, but meaningfully improve taxpayer service and technology. This will allow the IRS to provide services to taxpayers in the manner they expect and deserve.

With the enactment of the IRA, the IRS is looking to efficiently and effectively upgrade systems, taxpayer services and compliance. The replacement of the current legacy CCS solution will support capabilities to enhance the taxpayer experience. Future opportunities to enable enterprise modernization goals include:

· Deployment of Modern technology solution that aligns with business and technical requirements.

· Utilization of Dynamic resource allocation and smart queuing to handle jobs of various sizes.

· Deployment and operations of a new technical solution that meets needs of digital notice delivery including Universal Accessibility (UA) Portable Document Formats (PDFs), which will allow the Agency to consolidate Notice Composition to one commercial- off-the-shelf (COTS) product.

· Technical Support that delivers dynamic notice content including multilingual support and 2D barcodes

· Alignment with current technology standards including IRS/Treasury cloud readiness and web service integration.

· Integration with version control tools

3.5 Desired CCS System

The desired end state is a CCS system that generates digital and print notices, forms and letters for online accounts and services which will allow taxpayers to access and view their notifications (Notices and Letters) online digitally. The system will generate notices for taxpayers and support Taxpayers in opting to receive personalized notifications about changes to their tax situation, payment reminders and status updates on refunds or audits. The CCS solution will enhance digitization of notices and expand the languages currently supported, thereby enabling taxpayers to obtain status in near to real time in numerous ways. The system will generate, and support multilingual notices, letters and forms issued to taxpayers with limited English proficiency. Increase the languages (Spanish, Chinese Traditional/Simplified, Korean, Russian, Vietnamese) available online in a digital format that are 508 Compliant. The system will be on premises and then move to IRS/Treasury cloud AWS environments.

The Contractor shall provide technical services and subject matter expertise to support requirements defined below. Further development of requirements will be performed during the tailored Enterprise OneSDLC. These services and expertise will include the following:

· Provide general project management oversight and reporting: i.e., Conducting the Integrated Project Team Meetings (IPT), User stories and design meetings, managing and maintaining Integrated Master Schedule for the END projects.

· Support Legislative changes requirements.

· Support all Infrastructure Currency and environment upgrade activities.

· Participate in the IRS requirements gathering process to develop and define business system-level requirements and business rules.

· Determine data validation, correction, return error notice processing, or augmentation required by IRS.

· Design the Notices, forms and letter whose templates are provided by OTC in alignment with IRS guidelines on reliability, performance and capacity requirements.

· Design and validate enterprise security features, reliability, performance, and capacity requirements.

· Support the resolution of any potential Privacy Impact issues and changes related notices, forms and letters to include but not limited to design and changes for the Operations and Maintenance (O&M) tasks.

· Design, configure, develop notices, letters and forms in print and digital formats, and database/storage and maintain capability for transmitting the notices, forms and letters to its destination servers as specified by the IRS.

· Support OneSDLC documentation updates, if required.

· Support 508 development and testing

· Support Performance Testing

· Support Multi-lingual notice generation and testing

· Support and integrate with latest Configuration Management (CM)/Ansible/DevOps/Continuous Integration and Continuous Development Pipeline (CICD) processes.

· Provide verification support after application patching in all environments, including after hours, Sunday Build Window and weekends.

· Establish the IRS/Treasury Cloud environment for the CCS project

· Support all IRS/Treasury Cloud environments for the project

· Provide support on Penetration Testing & Code Analysis (PTCA) and (Advanced Application Analysis) (AAA) Code scans and resolve and findings.

· Support review, assessment and resolve any security findings reported on security reports, i.e., Qualys VMDR, Splunk and Guardium Report.

· Coordinate and provide support for filing season readiness activities, including, SSL certificate renewal, Service Accounts password resets, etc.

· Fix all systems and software for service continuity and SLA.

· Support all infrastructure currency and environment upgrade activities.

· Respond to END-CCS systems & software related technical data calls.

· Provide ETL support as needed including ETL Ansible deployments & execution.

· Initiate IRWorks ServiceNow tickets, including REQ, CHG, etc.

· Support all systems & software deployment activities.

· Support ELM (Engineering Lifecycle Management) activities to open user stories for product business log.

The Contractor shall employ a tailored OneSDLC development path and methodology, as determined by IRS. The Contractor shall coordinate all development, testing and integration work through the IRS Program Manager (PgM), Project Manager (PjM) or designee. The Contractor shall collaborate with the designated IRS PgM/PjM to establish and maintain an appropriate schedule that meets the needs of the IRS. The Contractor shall compose a development and testing schedule identifying IRS or third-party dependencies to meet mutually agreed schedules. The Contractor shall provide weekly report on the status of each component of the project, on design, configuration, development, integration, testing, and operation and maintenance work. In the event, Contractor dependencies are not met in accordance with the due dates for each, as identified in the schedule, the designated IRS PgM or PjM will provide notification to the Contractor regarding any issues which impact final delivery dates and coordinate schedule updates with the Contractor accordingly. In the event, delays persist contractors shall follow the IRS guidelines on the escalation process for an appropriate channel for resolution.

4.0 SCOPE OF WORK

The contractor shall provide technical support personnel and supervision necessary, that are MBI cleared on Day-1, for the definition, development, and implementation, operations, and support (O&M) of the Enterprise Notices Digital (END) project applications and Database in IRS Environments (IRS/Treasury cloud or On Premise). The Contractor will accommodate changes and enhancements to business processes, including IRS, legislative and executive mandates but not limited to END project. This support for the business processes and their interrelated systems/services for END shall include the following task areas:

1.1 Project and Program Management/Operational Security Support, status reports

1.2 Agile Portfolio Management Support

1.3 Enterprise Service

1.4 Earned Value Management (EVM) Support

Contractor shall provide orientation Briefing to the END project team (IRS and Contractors). Contractor shall attain the complete ramp-up Knowledge from the present incumbent contractor such that the contractor shall ensure there is no break in or delay in the start of the project on time. The contractor shall schedule meetings with the incumbent contractor and arrange for all meetings that are needed to gain the knowledge from the incumbent contractor. The contractor shall perform all requested Project and Program Management, Operational Security Support and status reports when asked by IRS Management Personnel. Contractor shall follow the Agile Portfolio Management for all DME and O&M work and further provide Agile Portfolio Management Support. Contractor shall provide Enterprise services for the project such as servers/ cloud service acquisitions, maintenance and deployment process but not limited to these alone. Contractor Shall provide status reports, and Quad Charts pertinent to the project along with Earned Value Management (EVM) metrics and further Support EVM throughout the project.

The contractor shall provide Development, Modernization and Enhancement (DME) Support. Contractor shall design and development of Notices/ Forms/ Letters generation in print and digital with 508 compliance and enterprise reporting to support the project. The contractor shall develop minimum 25 Notices (in print and digital formats) each month in IRS Premises or IRS/Treasury Cloud(s), preferably Cloud(s) and shall start the work of developing the notices within thirty – sixty (30-60) days of the start of the project (after kickoff). Contractor shall provide a complete schedule on the planned work, with tasks, task start dates, task completion dates, and resources within 30 days of the of the start of the project (after kickoff).

The END-CCS project is a modernization project with fast paced delivery (development, test, deploy) and maintenance. The project will require to generate and maintain a minimum 25 notices per Month to a minimum of 300 Notices, letters and forms in print and digital, that are 508 compliant, in multiple languages in the IRS/Treasury cloud in the base year using new modernized tool such as Opentext Exstream or a better tool that is identified. Subsequently, IRS wants to migrate at a minimum 25 notices per month to a minimum of 300 notices each optional year until all the notices are converted from legacy to the modernized tool. The vendor shall support all the efforts of migration, development of new notices, enhancements for the existing notices and maintenance of the notices.

The vendor shall provide a work break down structure (WBS) with recommended timelines (schedule) for the work they will be performing. All Milestones with the list of accomplishments within the schedule should be clearly mentioned. IRS would like to have a minimum of 300 notices, letters and forms in production in the base year. IRS will migrate at a minimum of 300 notices each optional year until all the notices are converted from legacy to the modernized tool.

The contractor shall provide Operations and Maintenance (O&M) Support. Contractor shall Support the maintenance of existing forms for a minimum of 300 Notices that are in print and digitized. The Notices for maintenance will initially start with a minimum of 25 notices and will increase each month throughout the life of the project for a minimum of 300 notices. Contractor should plan to begin with maintenance of 25 Notices and be ready to maintain the notices that are implemented into production incrementally each month. Contractor shall support in maintenance of the design and development of Notices, Letters and forms generation in print and digital that adhere to the Section-508 compliancy guidelines and enterprise reporting to support the project.

The contractor shall provide DME support. The contractor shall develop and maintain minimum of 25 additional new Notices in print and digital each month within IRS/Treasury Cloud(s) and shall start the work of developing the notices within thirty – sixty (30-60) days of the start of the project (after kickoff). Contractor shall provide a complete schedule on the planned work, with tasks, task start dates, task completion dates, resources and environments the task will be completed within 30 days of the of the start of the project (after kickoff).

The Contractor shall validate and update the strategic direction for the END by communicating and keeping up to date with new emerging technologies. The Contractor shall assist in the development of new requirements (System software updates and updates to notices, letters, and forms) as identified by the program office to deliver in emerging technology solutions to the IRS. Work products shall include business case development, customer requirements development, and implementation plan development. Contractor shall assist in the development of new programs as identified by the program office and may include some legislative and executive mandates. Contractor shall support in development and maintenance of the programs identified by the IRS program office.

All tasks identified in Project Management shall be completed throughout the lifecycle of the project to include project close-out. All tasks are to be performed in the IRS environment.

Contractor shall extend full support in complete/full Training of the IRS personnel with supporting documents, be active in Knowledge Transfer when requested within the lifetime of the project with supporting documents. Contractor shall extend full and complete cooperation and transition out and provide complete documentation of the project. Contractor shall perform all the close out Services that are required by IRS. All activities shall be documented and presented to the IRS team when requested.

Contractor shall coordinate with relevant IRS groups for completing a task and follow IRS guidelines.

Contractor shall update and maintain the Interface Control Document (ICD) and related forms and applications interface development and integration with the following IRS systems, but not limited to:

· Splunk

· Any future upstream or downstream IRS system as required. For example, integrate with Individual On-Line Accounts (IOLA) and Business Taxpayer Accounts (BTA) projects.

5.0 PERFORMANCE REQUIREMENTS

The contractor shall successfully integrate and coordinate all activity needed to execute the contract requirements as described below. The contractor shall manage the timeliness, completeness, and quality of END Project. The contractor shall complete the project to the satisfaction of the IRS END program management team. All invoices will be approved by the IRS END project team after verifying completion of each deliverable and subsequently paid. Incomplete deliverables will delay the payment of an invoice. The project team shall report the deliverables state to the COR for payment. The acceptable delivery of the products will be communicated to the contractor regularly in daily and/or weekly meetings. IRS END project team expects the quality of the product, quantity of the product to be submitted in a timely manner. The performance requirements are specified in the QASP. The deliverable tasks/products are listed for each section with timelines. In the places the timelines are not mentioned, the contractor shall ask for the timelines and the environment the product/task must be delivered and shall deliver the same to the satisfaction of the IRS END project Team. Completed payments based on monthly invoiced amounts are subject to meeting full monthly delivery requirements.

5. 1 Task Area 1: Orientation Briefing/ Ramp-Up Knowledge Transfer/Transition In/Program Management/ Operational Security

5. 1.1 Task Area 1: Orientation Briefing/ Ramp-Up Knowledge Transfer/Transition In

5.1.1.1 Orientation Briefing

Within one week of task order award, the Contractor will conduct an orientation briefing for the Government. 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 award requirements and objectives.

The orientation briefing will be held at the Government’s facility or virtually and both parties will 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 award will be introduced.

· The Government may provide information on how to obtain any GFP that will be issued to the contractor.

· Any issues concerning the Contractor clearances for Contractor personnel will be discussed.

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

· The Contractor shall provide the accounting period end dates to be used for the term of this award.

DESIRED OUTCOME - The objective of the briefing is to initiate the communication process between the Government and Contractor to assure a common understanding of award requirements and objectives. Contractor delivers Orientation Briefing Minutes to COR within 5 business days after Briefing. Contractor delivers Quality Assurance Surveillance Plan (QASP) to the COR within 30 business days after the Briefing.

5.1.1.2 Ramp-Up /Knowledge Transfer/Transition In

Ramp-Up Knowledge Transfer/Transition In is defined as the contractor acquiring and understanding the necessary documentation, information, and processes related to any work in progress from the Government. This task includes meeting with the IRS Subject Matter Experts frequently to gather any tacit knowledge related to the Core Systems, Compliance Document Matching, Corporate Notices END project related activities and Solutions Engineering/Enterprise Services tasks or programs in development. Transition-In shall be worked concurrently with Ramp-Up Knowledge Transfer. Successful transition can be defined by its capacity to maintain full continuity of operations, high productivity, and exemplary service quality.

The government estimates these tasks will take approximately ninety (90) calendar days to complete after award. Offerors shall review the tasks required in the PWS when establishing required knowledge transfer time/transition-in time.

The contractor shall appoint a knowledge transfer SME to oversee the transfer of knowledge and ensure all areas are accounted for. If desired, this can be the Project Manager (PM) or Project Scheduler. Prior to the transfer of knowledge, the contractor shall develop a Knowledge Transfer Plan (KTP) to identify the contractor resources and roles involved in the transfer process, provide a list of risks and mitigation strategies for the transfer, and contain a detailed resource balanced project schedule developed utilizing IRS approved COE software tools. The project schedule shall identify tasks, dependencies, deliverables and milestones. The project schedule shall be at a sufficient level of detail to track progress on a bi-weekly basis, (i.e., all tasks will be detailed to a level such that no task has duration of more than ten working days).

The contractor shall meet with the IRS Weekly to discuss the progress of the knowledge transfer. The contractor shall show an updated MS Project Schedule and discuss any risks or concerns at this time.

The Knowledge Transfer in process shall include, but not limited to the following:

a) Knowledge transfer of technical skills and lessons learned to IRS staff.

b) Operations and maintenance processes and procedures, if applicable.

c) Monitor and report system performance workload.

d) Transfer of complete documentation for all delivered functionalities. Deliverables shall be in softcopy format and shall be the sole property of the federal government. The format for deliverables will be provided in a format which will allow the government to modify and update when/if necessary.

e) Knowledge of configurable data including usernames, passwords, and application settings.

f) Support planning activities, staff management, schedule management, issue and risk tracking and reporting, report generation, configuration management, quality assurance and management, and technical review support; and

g) Includes engineering support for the operations, including analysis of operational data, performance of special studies, and user group support.

5.1.2 Task Area 2: Project and Program Management/Operational Security Support, Status Reports The contractor shall provide support to IRS END Project team/Program Management Office for schedule management, communication across multiple workstreams, track changes to project delivery and scope, continuous project level reporting (e.g., delivery progress, Quad Charts, risk/issues, UWR status, accomplishments, milestones, environment readiness), executive level reporting (e.g., project status, milestones, roadblocks), Enterprise OneSDLC artifact documentation and coordination, risk management support, configuration and change management support, and UWR tracking and traceability. The contractor will serve the role as a bridging mechanism between project and program management, on the one hand, and IT and enterprise strategy, on the other. The contractor shall leverage principles and practices such as Lean and Agile Portfolio Management to ensure modernization programs and projects at the IRS are managed for strategic alignment.

5.1.2.1 Program/Project Planning and Management Support

The Contractor shall:

a) Create a charter capturing the program management roles, responsibilities, and functions vested in the CCS program management team.

b) Provide general project management oversight on a day-to-day basis and reporting for work under this task.

c) Partner with the Program Office, Delivery Partners (e.g., EOPS, AD, ES and S&P) and Business Partner with requirements and scope analysis in the effort to define and clarify business capabilities and Use Cases

d) Work with Delivery Partners to establish and maintain the framework, structure and operating model (e.g., roles / responsibilities) for the Integrated Project Team (IPT), scope analysis for the effort (e.g., Inflation Reduction Act (IRA)) to define and clarify required business capabilities and Use Cases

e) Support integration with other IRS organizations (e.g., Engineering Services (ES), Program Management Team, Technical Integration Office (TIO), support efficient and aligned execution of project deliverables, executive reporting, and stakeholder communications.

f) Develop an integrated project plan using the project priorities to sequence activities. Monitor progress against the plan on a weekly basis. Identify execution issues/risks and track to closure.

g) Participate and contribute to the Daily Leadership Stand-up, Daily Development Team SCRUMs, Weekly IPTs, Weekly Executive Briefing, Executive Steering Committee (ESC) reporting as required.

h) Development and Management of the requirements process (Business Process Management (BPM) Development, Scheduling, Requirement Traceability)

i) Align processes, operating model, and delivery framework with the Agile Scrum methodology where possible and use of the Rational Team Concert (RTC) to manage backlog.

j) Perform approximately 12 monthly sprints per year each at 2-4 weeks sprint cycles.

k) Create a set of monthly sprint metrics and dashboards that allows the team to measure their progress related to the execution of agile/scrum delivery; Metrics to understand the Development velocity that shows the speed at which the team is producing. Sprint metrics should not be limited to Sprint Burn Down Chart, Sprint Velocity Chart, Sprint Status Chart, Stories accomplished by Category, O&M vs New Development Metrics, # of changes.

l) Support integration with other IRS organizations (e.g., EOPS, AD, ES etc.) to support efficient and aligned execution of project deliverables, code deliveries, executive reporting, and stakeholder communications.

· Developing of the Executive reporting and Stakeholder communications include but are not limited to the weekly Project Production Status Briefing, bi-weekly Project Status Update, monthly Project Priority Project Dashboard, Governance Board review for decisions/approval.

m) Develop the integrated master schedule (IMS) on project planned releases.

n) Develop Project Roadmap for Project Releases which contain critical delivery milestones as well as OneSDLC milestones.

o) Identify execution issues/risks and work with project management team to enter risks/issues into ITRAC if required. Provide mitigation plans on risks and resolution plans on issues.

p) The Contractor shall develop and maintain the overall Project(s) Work Breakdown Structure (WBS) and Project Schedule in Microsoft Project.

q) The Contractor shall support planning of development activities and releases; system integration and testing; and program level coordination with other IRS projects and stakeholders across the enterprise requiring interface and/or alignment.

r) The Contractor shall be responsible for developing, maintaining, and reviewing project artifacts for accuracy and assessing impact on Release deliverables.

s) The Contractor shall support the management of the project interdependencies, ensure that the deliverables satisfy the business and technical requirements, and ensure that the deliverables and the overall logical and physical design solution comply with the infrastructure, privacy, security, Enterprise Architecture (EA), Enterprise life Cycle (ELC), OneSDLC and/or Agile, and Section 508 requirements.

t) The Contractor shall utilize enterprise tools to manage all aspects of workload to align with IBM Collaborative Lifecyle Management (CLM), Engineering Lifecycle Management (ELM), and any other IRS collaboration tools.

u) The Contractor shall coordinate with a wide stakeholder audience for submission of ELC\OneSDLC deliverables in accordance with the integrated master schedule.

v) Contractor shall support the transition of all existing ELC project and application documents in adoption of OneSDLC lifecycle.

5.1.2.2 Program Development Support

All tasks identified in Project Management shall be completed throughout the lifecycle of the project to include project close-out. The Contractor shall assist in the development of new programs as identified by the program office to deliver emerging technology solutions to IRS. Work products shall include business case development, customer requirements development, and implementation plan development.

The deliverables shall include, but are not limited to:

· Complete Requirements Traceability Matrices (RTMs) that capture service requirements for the planned service and that will be used for monitoring and reporting test results

· Program/service development project plans delineating the steps,

· Milestones and processes that will be used in developing the program;

· Presentations on relevant topics for consideration in developing service requirements;

· Research on industry best practices and commercial service offerings;

· Facilitation of special topic and consensus meetings to develop program requirements;

· Facilitation of industry exchange meetings to discuss the state of commercial service offerings;

· Requirements consensus briefings, meeting minutes, and reports; and

· Preliminary program and service concept of operations (CONOPS).

5.1.2.3 Project Management Services/Oversight & Reporting

The Contractor shall provide management and technical support services to the IRS ensuring effective delivery of services. The Contractor shall implement a best practice program management methodology consistent with Project Management Institute’s (PMI) Book of Knowledge (PMBOK) to ensure that all tasks are completed on time, within budget with the approved scope and quality. Contractor support shall include, but is not limited to, the following:

· Staff assignment tracking

· Monthly tracking and reporting of costs

· Creation of processes to enhance the IT and FM program(s)

· Prototyping

· Architecture, Design and Development and support

· Periodic program management review briefings for program and executive staff

· Configuration management support

· Quality assurance plan development

· Risk management and risk mitigation plan development

· Schedule management

· Communications Management

· IPT

· Lessons Learned

The Contractor shall organize, establish, and manage the functions to ensure comprehensive coverage of all requirements and integration of the management functions for efficient, effective project operations.

The Contractor shall manage the communications, interactions, and agendas of applicable END stakeholders and work closely with business and technical stakeholders to manage the complex interdependencies.

5.1.2.4 Stakeholder Coordination & Management

The Contractor shall coordinate with stake holders and management to perform tasks on-schedule and on-budget, integrate efforts with designated IRS project team(s), and conform to the IRS OneSDLC Iterative development path and methodologies. Contractor shall coordinate meetings with stakeholders and management for requirements, as required on tasks pertinent to the project, and status meetings.

5.1.2.5 Quality Management & Support

The Contractor shall utilize designated IRS OneSDLC processes, in compliance with IRS guidelines and influenced by our CMMI Level 3 appraised standards. With quality gate reviews defined throughout the OneSDLC including production support, IRS will use defect data from quality assurance activities to control quality defect levels and performance.

5.1.2.6 Risk Management

The Contractor shall pro-actively identify, document, analyze, prevent, or mitigate risk throughout the project lifecycle. The contractor shall keep the IRS team informed of all activities. All risks have to be brought to IRS team’s attention and should be tracked in ITRAC and work toward closures.

5.1.2.7 Status Reports & Meetings

The Contractor agrees to attend any post award conference (i.e., Kickoff Meeting) convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5.

The Contractor shall monitor, manage, and report the multifaceted release development efforts and provide updates to the integrated master schedule maintained by the END Program Office and technical stakeholders.

The Contractor shall also support bi-weekly status meetings, reporting of all functional areas, identifying progress, accomplishments schedule/resource changes, and discuss any unresolved issues and action items. Project data shall be reported in meeting presentation decks one day prior to the scheduled meeting. The Contractor shall work with the END Program Office and technical stakeholders to support any additional status reporting requirements that result from subsequent OneSDLC milestone reviews.

Specific tasks shall include the following:

· The Contractor Project Manager (PjM) shall report to an IRS Program Manager (PgM) or Project Manager (PjM), as designated. The Contractor PjM shall provide guidance, oversight, and control on the work performed under this contract.

· The Contractor shall manage the deliverables, activities, and costs for the project team to ensure timely delivery of services.

· Develop a Project Management Plan addressing Contractor tasks that provides at a minimum, Project Management, Configuration Management, Quality Management, Communications Management

· Conduct customer status meetings on a bi-weekly basis

· The Contractor shall monitor, report and provide input related to project status using IRS agreed reporting formats and schedules, to include project Work Breakdown Structure (WBS); Integrated Master Schedule (IMS); and other IRS requested program management information.

· The Contractor shall adhere to all IRS Privacy Information Protection and Data Security standards as referenced in IRM 10.5. Detailed information about IRS IRM 10.5 will be provided to the Contractor upon Contract award

· The Contractor shall adhere to IRM 2.25.2, Web Services, IRS Portal and Extranet Usage Standard. Detailed information about IRS IRM 2.25.2will be provided to the Contractor upon Contract award.

DESIRED OUTCOMES – The Contractor shall perform tasks on-schedule and on-budget, integrate efforts with END Program Office, business and technical stakeholders and conform to the designated IRS OneSDLC development path and methodology, as tailored for this program. The Contractor shall complete the tasks and provide the deliverables based upon agreed schedule at the expected level of detail and quality.

5.1.2.8 Investment Funding

a) Contractor shall focus on existing assets and distinctive competencies resident in the product and service solutions that derive from each portfolio.

b) Contractor shall work with project and financial managers to develop lean budgets, which eliminate the need for traditional project-based funding and cost accounting.

c) Contractor shall perform analysis and define value streams particular to the program. These value streams such as the sequence of activities required to design, produce, and deliver a specific product or service, along with information, materials, and work flows – support investment funding by enabling the AD and ES to define and analyze the current state and design a future state for the series of events that will take product or service from its beginning through to the customer.

d) Contractor shall work with Government and other stakeholders to know the total capacity for each release in the portfolio, as well as understanding how much funding is available for new development work, versus ongoing maintenance and support activities. With this is understood, the AD and ES shall be an improved position to evaluate and originate portfolio level initiatives in a logical, objective, practical sequence, and at less cost. The contractor shall work to ensure strategic alignment and reduce enterprise and program risks and costs.

Desired Outcomes: The Contractor shall perform all Program Management Office/Technical Integration support services associated with this task in accordance with IRS requirements outlined in the PWS. The Contractor shall submit all associated work products and deliverables associated with this task to the IRS timely and within the acceptable level of quality.

5.1.2.9 Program Operational Security Support

The Contractor shall assist the Government in providing information security to ensure that Treasury’s services, programs, and related infrastructure are compliant with the applicable Government regulatory requirements. This task consists of three activities, as follows:

· System Security Assessment & Accreditation Support:

The Contractor shall provide security support to achieve System Security Assessment & Accreditation (SA&A) as required by OMB and NIST guidance. This support may encompass developing system security documentation as well as assessing the security posture of the systems.

The deliverables shall include, but are not limited to, the following:

· System Security Plans

· Security Test and Evaluation Reports

· Plans of Action and Milestones (POA&M)

· Certification…