Request for Quotation_EDOS.pdf

PDF 1 MB Posted

Attached to
Enterprise Development Operations Services Notice
Solicitation number
Not on record
Issued by

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

The Department of the Treasury Internal Revenue Service (IRS)

IRS Blanket Purchase Agreement Request for Quotation for Enterprise Development Operations Services (EDOS)

RFQ#: 2032H5-22-Q-00058

P a g e 2 | 104

GSA MAS Information Technology Category Holders/Prospective Quoters:

The Internal Revenue Service (IRS) is issuing this Request for Quotation (RFQ) in support of the IRS requirement for Enterprise Development Operations Services (EDOS). The IRS anticipates establishing multiple Blanket Purchase Agreements (BPAs) for services described in the Performance Work Statement (PWS). The IRS is providing its minimum requirements. Quoters are encouraged to quote their best possible solution to meet or exceed the requirements as stated in the BPA PWS.

Included within this RFQ are the PWS, BPA terms and conditions, Quality Assurance Surveillance Plan, Pricing template, Sample task order, Sample pricing template and Award Term Plan. Instructions for preparing and submitting both the price and technical responses are included in Section II of the RFQ.

The IRS is competing this requirement among General Services Administration (GSA) Multiple Award Schedule, IT Category holders. The resulting BPA’s will be awarded to the quoters whose quotation represents the best value to the IRS. The Government intends to establish multiple BPA’s. As such, the IRS encourages a comprehensive solution to meet the requirements as stated in the PWS. The resulting BPA will allow for orders on a Firm–Fixed-Price (FFP), Labor-Hours (L-H) and Service points basis only (designated by CLIN).

Questions: Draft documents were released on SAM.gov on February 08, 2022. The draft solicitation was posted to SAM.gov on or about Thursday, May 19, 2022. An Industry Day was later held on June 08, 2022 and a Q&A period was held to discuss the draft solicitation. Therefore, any additional questions submitted regarding this solicitation will be responded to at the discretion of the Government.

Quoters are prohibited from communicating directly with IRS personnel (other than the Contracting Officer) about this procurement action.

Quotation Due Date: Quotes in response to this RFQ shall be submitted via email to the Contracting Officer – Michael.R.Villano@irs.gov and Contract Specialist, Travis.T.Kelson@irs.gov no later than 12:00 pm, Eastern Time, August 03, 2022 with the subject line of "Responses for RFQ IRS EDOS”.

Late quotes will not be considered.

Sincerely, Michael R.Villano Contracting Officer Office of Information Technology Acquisition (OITA)

RFQ Attachments:

Attachment I – BPA Pricing Template (excel file) Attachment II – Quality Assurance Surveillance Plan (QASP) Attachment III – Sample Task Order Attachment IV – Sample Task Order Pricing Template (excel file) Attachment V – Award Term Plan mailto:Michael.R.Villano@irs.gov mailto:Travis.Kelson@irs.gov

P a g e 3 | 104

SECTION I – GENERAL INFORMATION

1.0 INTRODUCTION

This BPA RFQ seeks to obtain the best value quote to support the IRS requirements for EDOS. The value of BPA orders to be placed under the BPA(s) is estimated at $2.6 billion over the course of eighty-four (84) months (7 years) if all optional ordering periods are exercised.

The primary purpose of this acquisition is to establish multiple BPA’s for EDOS in support of the IRS HQ.

EDOS services includes a wide range of design, development, implementation, operations, and maintenance tasks.

The IRS is competing this requirement among the General Services Administration (GSA) Multiple Award Schedule (MAS), Information Technology (IT) Category contract holders.

The Quoters whose quotes represent the best value to the IRS will be awarded a BPA.

1.1 RFQ Date of Issue

July 13, 2022

1.2 Issued By

Internal Revenue Service Office of Information Technology Acquisition (OITA) Corporate Services Branch

P a g e 4 | 104

SECTION II: SCHEDULE OF SERVICES AND PRICES

1. GENERAL

The Contractor shall perform the effort required by this Request for Quote (RFQ) on a Firm Fixed Price (FFP), Labor-Hours (L-H) and/or Service points basis, as applicable. The work shall be performed in accordance with the terms and conditions of this RFQ, the Contractor’s Schedule Contract, and the resultant BPA. The resultant BPA outlines and provides for specific pricing and terms and conditions, beyond what is set forth in the GSA Schedule. The pricing and terms conditions set forth in the resultant BPA are not superseded by the terms and conditions of the GSA Schedule. In the event a specific term and/or condition of the BPA conflicts with a specific term and/or condition of the GSA, then the specific terms and conditions of the resulting BPA will prevail. Unless otherwise mutually agreed to in writing by the Government and the Contractor, the terms and conditions of the GSA contract will remain in effect. The Contractor shall not change, condition, or deviate from the resulting BPA pricing, terms and conditions, or cause such to occur by virtue of not strictly complying with the terms and conditions of the resultant BPA(s).

The Government estimates, but does not guarantee, that the volume of purchases under the resulting BPA at $2.6B for the entire potential period of performance (one (1) base year with four (4) one year option periods and two (2) one-year award term years). The Government is obligated only to the extent of authorized purchases made under the BPA. There is no minimum order guarantee.

2. SERVICES AND PRICES/COSTS

Quoters are required to submit a price for a base period of 12 months with four (4), 12-month option periods, and two (2) 12-month award term periods as identified below. The proposed rates must not exceed the rates awarded in the Contractor’s GSA Schedule. Discounted rates are strongly encouraged.

This BPA is not a contract. If the BPA holder fails to perform in a manner satisfactory to the BPA Contracting Officer, this BPA may be canceled with a (60) day written notice to the BPA holder by the BPA Contracting Officer.

2.1 CONTRACT LINE ITEMS (CLINs)

Refer to the Performance Work Statement (PWS) under Section III for a complete description of the requirements. Quoters are required to utilize the Government provided pricing template when preparing their pricing quotations. The Government reserves the right to make an award for any or all the contract line items listed below.

IRS EDOS

RFQ# 2032H5-22-Q-00058

Refer to BPA Pricing Template for the list of CLINs

SECTION III – PERFORMANCE WORK STATEMENT

3.0 Performance Work Statement

The IRS Information Technology (IT) Application Development (AD) Office provides support for established and new tax law for examination, collection, and criminal investigation activities.

The mission of AD is to build, test, deliver and maintain integrated information systems that support modernized systems and the production environment to achieve the vision and objectives of the IRS. AD is organized in nine domains: Delivery Management Quality Assurance, Compliance, Data Delivery Services, Technical Integration, Internal Management, Submission Processing, and Identity and Access Management requiring contractor support in broad areas of responsibility for the development and maintenance of software.

To assist AD in its mission, the IRS requires professional expertise to provide end to-end support to deliver IT capabilities related to Enterprise Development, Operations Services (EDOS). The IRS is seeking contractor support to provide a full range of development and associated services necessary to plan, coordinate and execute technical and management approaches in alignment with requirements and scheduling demands for the AD delivery partners and other business stakeholders.

3.1 OBJECTIVES

The Contractor shall support the objectives for EDOS developing, modernizing, and maintaining IT capabilities with a full range of services. Support collaboration with internal and external IRS stakeholders to fulfill the EDOS mission.

• Empower and enable all taxpayers to meet their tax obligation, simplify the process of filing, correction, and payment for all taxpayers and their representatives; develop secure digital options for taxpayers and professionals to interact efficiently with the IRS, while maintaining and improving traditional service options

• Protect the integrity of the tax system, develop and maintain a secure applications fitting the needs of the EDOS mission; ensure compliance through administering and enforcing the tax code; identify and plan for compliance risks; investigate violations of the tax code and maximize deterrence.

• Advance data access, usability, and analytics to inform decision making and improve operational outcomes.

• Update data collection and retrieval capabilities and processes to provide faster authorized access to information; improve analytic tools; emphasize the use of data analytics and qualitative information to select high priority work

• Drive increased agility, efficiency, effectiveness, and security in IRS operations.

Modernize and integrate technologies and systems that support secure, flexible, and accurate work across IRS functions; safeguard taxpayer data and protect the IRS against internal and external threats, with an emphasis on cyber defense; simplify policies and processes to improve operational efficiency and coordination across business units.

The scope of work for this requirement is set forth as a collection of task areas necessary for successful project planning, management, and execution. This Blanket Purchase Agreement (BPA) does not include support for 1) issuance of a task order exclusively for Project Management support (outside of EDOS specific tasks); 2) the purchase of hardware or development, modernizing enhancement or operation and maintenance of hardware; 3) technical and operational support for networks. For this BPA, Project Management Support is defined as internal support to each respective task-order. The BPA task areas are:

Task Area 1: Project and Program Management Support Task Area 2: Agile Portfolio Management Support Task Area 3: Development, Modernization & Enhancement (DME) Support Task Area 4: Operations & Maintenance (O&M) Support Task Area 5: Service Management Task Area 6: Transition Services Task Area 7: Surge Support Task Area 8: Earned Value Management (EVM) Support Task Area 9: Enterprise Service Task Area 10: Managed Service

3.1.1 Adherence to Regulations and Policies. All work performed shall be in conformance with all Government regulations and policies including the Federal Acquisition Regulation (FAR), Department of the Treasury Acquisition Regulation (DTAR) and other agency supplemental regulations and policies as appropriate.

3.1.2 The contractor shall provide support services regardless of the selected engineering lifecycle path, methodology or approach for development and delivery of program capabilities.

IRS development paths may include Agile, Waterfall, Iterative, Commercial-Off the-Shelf (COTS), Mobile Apps, Managed Services, or other IRS approved paths.

Capability development and delivery may be accomplished using traditional, largely sequential or waterfall-based approaches, as well as more iterative and incremental approaches that include leveraging Agile and Development Operations (DevOps) principles, methodologies, practices and tools. The contractor shall assist the IRS in defining, managing and executing strategies that result in the delivery of high-value, high-quality IT services and capabilities to meet both current and emerging IRS business needs.

3.2 SCOPE OF WORK AND DESCRIPTION OF TASKS

The scope of this PWS encompasses Contractor support for AD and IRS IT activities including, but not limited to, project management, customer consultation/coordination, web design, requirements specification analysis, planning, application development, Enterprise Life Cycle (ELC) processes and documentation, and similar complex services in support of IRS IT missions, cybersecurity, and future studies such as cloud, architecture, and infrastructure.

The IRS mission requires a Contractor who has expertise in such areas as program and project planning, creating web-based applications, databases, and associated utilities for service-wide communications, program management and administration, performance measurements, cost reporting, and recommended solutions based on understanding of IRS’s information architecture, infrastructure, and organization.

As the federal agency that collects taxes and administers internal revenue laws, the Internal Revenue Service (IRS) is required to administer the tax provisions included in all legislation.

The Contractor will provide services to support current tax code applications and build new processes that do not exist in tax administration today.

The contractor will be responsible for operating and maintaining systems and upgrading more than a dozen key enterprise IT Systems and overseeing several tax systems, designed to carry out legislative changes.

3.3 DESCRIPTION OF TASKS

The contractor will provide expertise, knowledge, and skills relating to software maintenance, system software maintenance engineering support, software development, and specialized GFE hardware maintenance to deliver performance in accordance with the Performance Work Statement (PWS). It should be noted that the referenced hardware that maintenance is to be performed on will be purchased and provided to the supporting vendor by the government as Government Furchased Equipment (GFE). There is no hardware/equipment that the government expects the vendor to purchase on its behalf under the EDOS BPA. This does not preclude the vendor from purchasing hardware solutions required to meet requirements such as providing support in the form of a managed service. The Contractor shall be able to provide expertise using collaborative tools such as Microsoft SharePoint, Teams and/or Skype.

The activities and responsibilities of the contractor will include those identified under the task areas listed below. Specific activities and deliverables shall be fully defined in individual task orders.

3.3.1 Task Area 1, Project and Program Management Support

The contractor shall provide project/program management support to successfully facilitate planning, management and execution of tasks associated with planned and awarded task orders under this BPA. Any approach must focus on managing/overseeing Cost, Schedule, and Scope.

This support consists of activities and artifacts consistent with the IRS Enterprise Lifecycle path.

These artifacts may include:

• Regularly updated (weekly) dashboard of EDOS BPA activity data to include on-boarding of new contractors, small business goals vs actuals, performance monitoring and reporting

• Regularly updated (weekly) dashboard of BPA Task Order activity data to include performance monitoring and reporting to support intake, requirements, and delivery partner integration for key initiatives and to ensure tracking, reporting, and execution of BPA task order intake, in process, and completed activities

• Continuous process improvement and communications to achieve and maintain effective service delivery and alignment recommendations

• An annual, planning baseline of activities and criteria to assist the Government in planning for orders transitioning in from other ordering vehicles or out of the BPA

• Quarterly Program and Fiscal Reviews of the EDOS BPA task order activity

Representative Activities shall include but is not limited to:

• Meet with COR bi-weekly to discuss ongoing task matters and resources to support the contract.

• Review and approved subcontractor invoices.

• Review and signed off on all new requirements

• Coordinate with COR to get SMART ID badges and minimum background investigations (MBIs) renewals for all team members.

• Create Tracker, forecasting and invoice reports

• Review and audit EDOS Task Order (TO) process documentation.

• Provide Enterprise Life Cycle (ELC) support to include as a minimum Capability

Maturity Model Integration process guidelines are met, or a like model, and all data is recorded and archived based on task order needs.

• Prepare and submit Status Reports

• Provide timesheet reports via Excel workbook

• Develop an Integrated program schedule and work breakdown structure (WBS)

• Financial project tracking reporting

• Review, comment, and coordinate responses to draft deliverables.

• Develop and manage IT project specific schedules.

• Create, manage, and maintain the program Integrated Master Schedule (IMS).

• Provide schedule analysis, including critical path analysis.

• Provide updates for project issues and action items in a weekly status report to AD managers.

• Meetings will include, but not be limited to:

o Bi-weekly Meetings with CORs to discuss invoicing, subtask assignments, projections, etc.

o Status Meetings with project leads

• Develop, update, and document all processes in use on the program, and facilitate regular reviews and updates to ensure currency and accuracy.

• Address and document or update for existing programs, the critical success factors, associated metrics, technical performance measures and criteria, and the methods by which validation will occur in accordance with IRS guidelines.

• Implement a test plan(s) that conform to IRS test procedures. The primary objective of the system test is to validate that the software and database meet the specified requirements of the customer and will perform satisfactorily in the customer’s environment.

• Prepare Task Order Status Report (TOSRs) for all subtasks and Government Furnished Equipment (GFE) inventory and Burn Rate report.

• Address RACF (Resource Access Controls Facilities) Violation Reports.

• Develop invoice reconciliation reports

DESIRED OUTCOMES – Provide technical capability to support multiple development team efforts and the goals of the Program.

• Successfully support the project management office with required documentation by agreed upon due dates.

• Project/Program management support activities are effective and completed on schedule and in accordance with the business requirements.

• Program control, billing functions, scheduling and quality management is provided to ensure successful management of all EDOS tasks.

• Labor mix is controlled in an efficient and effective manner, maintaining personnel with skillsets to meet task orders desired outcomes, and maintain a maximum personnel turnover below 50% except to add to the Government’s new or updated requirements.

3.3.2 Task Area 2, Agile Portfolio Management Support

The contractor shall provide subject matter expertise in various Agile methodologies and frameworks and can articulate their usage within Agile software development. The contractor shall be able to interface with domain area leads (including ACIOs) to effectively navigate change and develop the ability to work within a transforming Agile system.

Agile Portfolio The contractor shall provide services to support identification, prioritization, organization, rationalization, and management of the AD agile development portfolio. The contractor shall provide roadmaps that include incremental releases to deliver on Product Visions provided by the government. As part of incremental releases, the contractor shall deliver Minimal Viable Products according to government priorities and planned releases. The contractor shall provide training, coaching and guidance to the government in developing and revising product and other types of backlogs according to Agile industry best practices to foster effective use of agile methodologies.

Agile Approach using Non-Points (L-H and/or FFP) The IRS is seeking to emphasize the use of agile software development methodologies characterized by incremental and iterative processes where releases are produced in close customer collaboration with a focus on continuous integration, continuous deployment, continuous test and continuous security to deliver code and functionality. Agile teams will own a feature from start to finish – regardless of how many layers of the architecture it crosses and will develop a ready-to-ship feature package. Teams will continually synchronize activities to manage project and product development dependencies through regularly scheduled Cadence Meetings. Team sizes will be structured around the work to be performed and the required skillsets to get to the definition of done, with the expectation that more teams will be added to handle new products rather than increasing the team size. As teams are added synchronization techniques (e.g., Common Iteration / Sprint Cadences, Product Release Planning) will be used to identify dependencies and risks.

The Contractor shall work closely and collaboratively with the IRS community performing a wide range of product development support necessary to assist them in successful development of solutions. IRS will manage stakeholder relationships and will provide direction to the Contractor, regarding these relationships, as necessary. The IRS anticipates team facilitation as follows:

• This Agile approach under the BPA will be managed via either Labor Hours or Firm Fixed Price Task Orders (TO) (or hybrid) depending on the type of work that will be required. For instance, break fix would be appropriate for FFP, whereas legislative enhancements coupled with maintenance would use L-H. Work under projects in O&M will be issued from existing product backlog items. For systems under DME, work will be issued based on requirements that will be used to formulate the product backlog items.

o The IRS Product Owner will manage the backlog for Agile product delivery, but overall scope may be reduced, or increased depending on the contractor team’s performance and velocity.

• Delivery PM will coordinate activities at the PMO level and with all delivery partners.

• All Federated Delivery Teams (FDTs) will be under the direction of an IRS Release

Manager which will provide all supervisory direction. The Release Manager will coordinate activities across multiple FDTs for a single product or release and the Scrum Master(s) will specifically coordinate development activities within the FDT's. Each FDT will be self-directed teams with no direct team lead. Self-direct teams are defined as a group of people working together in their own ways, toward a common goal, which the team defines.

a) Solution project planning, scheduling, collaboration, communication, and reporting using techniques appropriate for projects using agile methodologies

i) User story management – documenting, vetting and refining business requirements into user stories, use cases or technical requirements, as well as identifying a standardized approach for requirements management

ii) Facilitating/ participating in customer feedback sessions to ensure solution alignment with customer needs/ requirements

b) User interface development

c) Designing, developing, testing and deploying project code

d) Integration - working with other IRS organizations and contractors to support integration efforts as well as identifying best practices for facilitating integration for system engineering solutions. Support implementation and integration of engineered designs into operational systems using operational (EOps) processes and procedures

e) Testing - coordinating and performing demonstrations and conducting unit level, system, and user testing to be performed before the conclusion of each iteration

i) Documenting and reporting testing results using agile standards while adhering to

IRS requirements relative to product quality requirements

ii) Identifying agile test results reports that are appropriate for IRS iterative delivery projects

f) Conducting 508 Compliance activities such as designing, testing to ensure that products meet all applicable Section 508 provisions

Service Points A Service Point is an alternate unit (vs. labor hours and cost in dollars) used for standardizing and documenting development estimate ceilings and funding for applications which are using agile development methodology or teaming. Additional teams may be created by the Government, using established rates.

Using service points within a Task Order can provide Task Orders the flexibility and agility in managing development contracts. Service points are akin to a unit of currency, because each point represents a fixed number of dollars.

The government has the option to use the product or another type of backlog to fund resources using Service Points on an incremental basis upon review and acceptance of software delivery or releases. Service Points shall be utilized/consumed based on usage as documented within the established contract rates. This methodology will be utilized by the Government to allow the funding of resources the same flexibility as Agile Development Methodology.

NOTE: Service Points are defined and used to indicate a method/process for estimates and funding and is not the same as Agile Story Points.

Reporting and Monitoring The contractor shall use a web-based tool to track, monitor and report on Agile Development Team velocity, burndown chart based on Service Points and other metrics used to monitor quality and efficiencies in software delivery using agile methodologies.

• Analyze AD applications software portfolio to identify areas of consolidation and component redundancy.

• Incorporate DevSecOps principles into the AD software delivery methodology.

• Support Agile project transitions to product-centric operating environments.

• Create prioritization criteria to implement service points development effectively and consistently.

• Manage workflow processes for Agile DME efforts.

• Support project planning activities.

• Identify project risks.

• Identify and diagnose process issues.

• Drive business value and retain the project goal and objectives.

• Partner with business stakeholders to make more strategic recommendations.

• Support Agile Teams in meeting preparation, including the pre-planning, planning, Scrum, and review stages.

• Instruct managers on the basics of Agile tools, such as Scrum and Kanban.

• Partner with Agile Central organization on Agile Acquisition to document and implement best practices.

• Provide hands-on support to engineering teams in adopting an agile mindset and practices with a focus on growing capabilities.

• Provide oversight and monitoring throughout the project and report on Agile program performance.

• Prioritize portfolio of IRS products that can be used to plan releases and Service Points for funding resources, efficiently and effectively.

DESIRED OUTCOME - The Contractor shall provide a strategy and solution for Service Portfolio Management. The Contractor will provide Portfolio Management to support tasks and assignments. The Contractor shall provide a tool to support tracking all requirements and activities. The Contractor is to coordinate and facilitate scrum meetings, such as, Sprint planning, Backlog Refinement, Sprint Reviews and Sprint Retrospectives. The Government and Contractor define acceptance of the deliverables as follows:

• Deliverable passes all new automated and manual acceptance tests that were defined before the most recent iteration.

• Deliverable passes all prior automated and manual acceptance tests, verifying that no regression has occurred.

• Deliverable conforms to the “definition of done” that was defined before the iteration.

The Contractor ensures that the Web Applications delivery organization has the appropriate Agile coaching, project management resources and project team members to plan for and manage the delivery of Web Applications products, specifically working software code at the end of each iteration.

3.3.3 Task Area 3, Development, Modernization and Enhancement (DME) Support

The contractor shall support and advise technical development activities across AD Domains for key initiatives. The contractor shall provide DME support as it relates to the following:

• Current Production Environment (CPE) systems

• Processing Pipeline Legacy systems

• Modernization Systems

• IRS business requirements, processes, and applications development

• Developer and Test Execution activities

• Integrated and Project Scheduling

• AD security tasks

• Section 508 Compliance and Accessibility Testing

• Creation & maintenance of End-User support materials

• Cybersecurity scanning and testing support

• Automated Testing

• Modernization & Transformation task

• Support legislative mandates and critical system changes using cutting edge technology including, but not limited to, Cloud Computing, DevOps, commercial platforms, and support of contingency operations.

• Design, develop, deploy, and implement new interfaces/data sources that do not currently exist to ensure data received/data delivered can be interpreted/translated/accepted.

• Design, develop, deploy, and implement new forms not currently processed to ensure data received/data delivered can be interpreted/translated/accepted.

• Design, develop, deploy, and implement new credits as the outcome of tax law changes.

• Design, develop, deploy, and implement new functionality based on business requirements not currently existing to ensure data received/data delivered can be interpreted/translated/accepted

• Develop and document software requirements, and perform other necessary analytical, software engineering, and/or development life cycle tasks.

• Support thought leadership, information sharing and data driven/executive decision-making; as well as contribute to IRS initiatives such as, but not limited to, resiliency and continuity.

• Identify and present common or leading practices from federal and commercial applications and/or development organizations that may serve as solutions to the IRS DME requirements.

• Use current best practices and/or develop innovative techniques to provide continuous improvement to support AD initiatives, processes and practices.

• Support application deployment coordination between AD and other departments throughout the IRS.

• Conduct requirements analysis, definition and decomposition activities as required.

• Maintain constant communication and coordination between with the Government to ensure the requirements are clear and understood.

• Develop code using modern / legacy / emerging programming languages and technologies such as, but not limited to: Java, ACL, COBOL, C, C++, C#, SQL, Python, XML, Oracle, Java, .NET, ADA; all required executable commands, scripts, and interface routines using standard communication protocols following life cycle methodology standards and guidelines.

• Create, maintain, and revise design documentation and business rules or processes.

• Provide services, including project management, system processes and capabilities, daily, weekly, monthly, and annual load processing, requirements management and security support.

• Develop processes to support applications or components after delivery to correct defects, maintain performance and compatibility with other elements in the technical environment.

• Support system fault, defect or bug fixing and the associated regression testing to ensure critical defects have been corrected prior to deployment.

• Provide analysis, design and development services to gradually retire identified stovepipe legacy projects and convert business required functions to modernized capabilities based on the IRS Strategic Plan and IT Modernization Plan.

• Provide analytical and technical support for applications to include support for annual updates to the Application Program Registry, drafting, reviewing, revising ELC and Capability Maturity Model Integration (CMMI) Level 3, or like model, artifacts, support for annual Functional Configuration Audit (FCA) and Physical Configuration Audit

(PCA), including collecting and authoring required documentation, resolving issues identified by auditors, attending CCB meetings and addressing issues identified by CCB that impact IRS Systems.

• Provide impact assessments of proposed changes to established baselines, testing strategies, and captured metrics.

• Development of new or updated application code for the components in response to work requests, change requests, or support of technical assessments, problem management and resolution of production defects.

• Development of scripts and related artifacts for movement of data between tiers.

• Conduct unit, integration, and regression testing for application code changes, creating test data, and conducting and documenting development of manual automated test cases, and support Government acceptance testing.

• Correct any problems uncovered during Enterprise Systems Testing (EST) efforts.

• Support post-implementation analyses to determine if application implementation goals have been achieved.

• Successfully complete the development, integration, test and deployment of programs and any future legislative initiatives.

• Support in requirements and user story development, decomposition, and planning

• Participate in joint reviews to refine the Product Backlog

• Utilize tools that support use of agile methodology to include visualization of product portfolio, product backlogs, iterative planning and performance reporting and monitoring

3.3.3.1 Training

The contractor assures that IRS and/or contractor identified staff receive the knowledge and skills needed to maintain all assigned programs/applications that require the knowledge and use of software tools needed for maintaining, testing and implementing software updates, modifications, and execution. This is an enduring and ongoing task that can be utilized on an as needed/adHoc basis. These training and knowledge transfer activities include but are not limited to on-site experience with the system by IRS-identified staff working with contractor staff, as well as informal training which the contractor shall perform during the contract. This activity includes the review of key components within identified applications within IRS IT. The contractor shall provide the following:

• Conduct mentoring sessions

• All technical support, activities and documentation should be transferred to enable

Government personnel to effectively continue the Current Systems Programs support.

• Current status report

• Planned activities

• Provide examples of Issues encountered

• Provide examples of potential risks Identified Identify any prerequisite system access or permissions Maintaining documentation of standards and procedures for ongoing training

DESIRED OUTCOME – The Contractor shall increase quality and sustainability of IT solutions and application support with no degradation of application functionality, or performance from the current levels. The Contractor shall provide Development, Modernization and Enhancement practices and controls that allow programs to effectively establish and maintain control of program status, execution, costs, and schedule. The Contractor shall successfully complete the deployment of scheduled releases to include receiving milestone exit approval for deployment.

The contractor must have experience with Information Technology Infrastructure Library (ITIL) to provide Metrics leadership support that enhances code delivery as measured by portfolio-wide efficiencies, visibility into application-level development to include velocity and testing.

Knowledge sharing and training should adequately prepare IRS employees to assume the role of System Owners or Administrators as appropriate

3.3.4 Task Area 4, Sustainment – Operations and Maintenance (O&M) Support

The contractor shall provide sustainment, operations and maintenance support to the IRS AD programs. Support shall include O&M services under the following areas, which are, but not limited to:

• Product End-of-Life including but not limited to activities such as decommissioning support, and disposal

• Section 508 Compliance and Accessibility Testing

• COTS Software (SW) Maintenance Services

• Specialized COTS GFE Hardware (HW) Maintenance Services

• Creation & Maintenance of End-User support materials

• Network Support

• Cybersecurity scanning and testing support

• Automated Testing

• Provide O&M services for system processes and capabilities, daily, weekly, monthly, and annual load processing, requirements management and security support.

• Develop processes to support applications or components after delivery to correct defects, maintain performance and maintain compatibility with other elements in the technical environment.

• Support bug fixing and the associated regression testing to ensure known critical defects have been corrected prior to deployment.

• Provide analysis, design, and development services to gradually retire identified stovepipe legacy projects and convert business required functions to modernized capabilities based on the IRS Strategic Plan.

• Provide analytical and technical support for applications during operations and maintenance, to include:

o Impact assessments of proposed changes to established baselines, testing strategies, and captured metrics.

o Development of new or updated application code for the components in response to work requests, change requests, production defects technical assessments, problem management and resolution of product defects.

o Development and maintenance of scripts and related artifacts for movement of data between tiers.

o Conducting unit, integration, and regression testing for application code changes, creating test data, and conducting and documenting development manual and automated test cases, and support of Government acceptance testing.

o Correct any problems uncovered during EST efforts.

o Support post-implementation analyses to determine if application implementation goals have been met, reports distributed, and key stakeholders appraised.

o Support the IRS’s established Configuration Control Board (CCB) for controlling the functional and allocated baselines and the development configuration.

o Adhere to the IRS Enterprise Lifecycle (ELC), Internal Revenue Manuals

(IRMs), applicable agency and Government regulations and guidance.

o Legislative Mandates support.

Desired Outcome: Sustainment Operations to include O&M and related efforts are adequately supported, ensuring minimization and mitigation of program risks and deficiencies. The contractor must have experience with Information Technology Infrastructure Library (ITIL) to provide Metrics leadership support that enhances code delivery as measured by portfolio-wide efficiencies, visibility into application-level development to include velocity and testing.

Knowledge sharing and training should adequately prepare IRS employees to assume the role of System Owners or Administrators as appropriate.

3.3.5 Task Area 5, Service Management

The contractor shall support Configuration Management (CM) functions including Unified Work Request (UWR) activities, Engineering Review Board (ERB) activities, Change Control Board (CCB) activities, business rule changes, configuration identification, configuration control, configuration status accounting and configuration audits.

• Track and document all configuration items included in baseline releases during design integration, testing, fielding and sustainment.

• Provide CM, quality assurance, and sustainment of all documentation.

• Update Implementation Packages accordingly.

• Develop Audit Plans and Reports, prepare and perform Audit Checklist activities.

• Meet Government acceptance criteria for configuration management.

• Service Desk Support for software application repairs/fixes

Desired Outcome: Consistent configuration management that implements standard documentation and reporting methods and provides a single logical view of all IT components and connections needed to effectively deliver IT services to customers. The contractor must have experience with Information Technology Infrastructure Library (ITIL) to provide Metrics leadership support that enhances code delivery as measured by portfolio-wide efficiencies, visibility into application-level development to include velocity and testing.

3.3.6 Task Area 6, Transition Services

The contractor must provide transition services defined as transition-in and transition-out.

Transition Services is required to accomplish ramp up and ramp down activities to develop, operate and manage the IRS IT programs. It is imperative that the incoming contractor works with the incumbent contractor(s) to ensure a smooth transition with minimal disruption to services and support for the Program Office, internal and external stakeholders, and delivery partners. The purpose of the transition is to transfer expert knowledge, data and artifacts that are used to support the programs from the incumbent contractor to the incoming contractor and/or the Government efficiently.

• Transfer knowledge of technical skills and lessons learned to IRS staff upon completion of deliverables and work products.

• Transfer knowledge of operations and maintenance processes and procedures.

• Support transition efforts to assist the Government with the transition of work from incumbent contractor to Government or incoming contractor.

• Develop a Transition Plan that includes training material, current status report, planned activities, issues encountered and identified risks.

• Transfer complete documentation for all delivered functionalities. Deliverables shall be in softcopy and hardcopy format and shall be the sole property of the federal government.

• The format of deliverables will be provided in a format which will allow the government to modify and update when/if necessary.

• Knowledge transfer of all configurable data including application settings, integrations, and interfaces.

• Assign personnel and submit security papers within 2 business days following award, to start the background investigations process.

• Request access to tools and documentation after receiving Approval of Staff Like Access

• Review and understand all the technical and process documentation

• Review and understand the existing data and solution’s product security policies in place

• Provide Ramp-Up Staffing Plan

• Provide Knowledge Transfer Plan/Checklist

• Maintain an inventory for orderly transfer of all GFP, to include GFE hardware, software, and licenses, Contractor Acquired Government Property, and Government Furnished Information (GFI)

• Transfer of all software code and documentation

• Certification that all non-public IRS information has been purged from any contractor-owned system

• Participate in knowledge transfer activities in accordance with the transition plan

• Develop, maintain, and update the Knowledge Transfer Plan

• Transfer of complete documentation for all delivered functionalities. Deliverables shall be in softcopy and hardcopy format which allows the government to modify and update when/if necessary and shall be the sole property of the government.

• Knowledge transfer of configurable data including usernames and passwords and application settings.

Desired Outcome: All task order efforts are transitioned timely, seamlessly, and completely from the incumbent contractor to the successor contractor and/or Government personnel without a disruption in services or delays in scheduled performance.

Knowledge Transfer Plan is accepted by the Government and at a minimum shall include a Transition checklist, address all aspects of delivered functionalities, major tax changes, usernames, passwords, artifacts location, and pertinent notes on decisions

3.3.7 Task Area 7, Surge Support

The Contractor shall be capable of providing surge support during the base or any option period, for unplanned, in-scope work. In the event the Government determines that an increased quantity of support is required for the task areas defined in the PWS, the Government reserves the right to exercise the Surge Option unilaterally.

Surge Support is defined as additional unplanned support generally needed for immediate action on an abbreviated timeline. Examples include legislation to implement Emergency Impact Payments and Advanced Child Tax Credit. The requirements that came out of this last minute, emerging legislation required implementation on a very short, constrained timeline and took precedence over all current work activities that were in flight when the legislation was enacted.

These types of activities required a “surge” in the available workforce to implement the late coming requirements as well as ensure the current work was also addressed.

Desired Outcome: The contractor will be able to rapidly respond to Government requirements of unplanned, in-scope work with the appropriate teams & qualified resources capable of delivering capabilities across all task areas. The contractor must have experience with Information Technology Infrastructure Library (ITIL) to provide Metrics leadership support that enhances code delivery as measured by portfolio-wide efficiencies, visibility into application-level development to include velocity and testing.

3.3.8 Task Area 8, Earned Value Management System (EVMS) Reporting Requirements

The Contractor shall comply with FAR 52.234-4 Earned Value Management System (EVMS) and Treasury EVM policy regarding ANSI/EIA STD -748A. Compliance includes documenting in the business proposal, a description of the EVM System (EVMS) to be used; in sufficient detail to enable independent assessment of the Contractor’s understanding and conformity with the requirements of the ANSI/EIA-748-A standard. The EVMS description will address all salient factors, including the key EVM measures and metrics and how the EVMS integrates with general cost accounting and budgeting systems. It will also address criteria used to determine applicability and means of verifying and monitoring flow down requirements to fully integrate subcontractor EVM data with the Contractor’s EVMS. Copies of referenced Treasury and IRS EVM policies and guidance will be provided as Government Furnished Information

(GFI).

• Provide for the completion of an IBR, or, as appropriate, (for subcontracts with DME less than $20 million, an IBR (Core) that meets the Government standard and that the Contractor provide periodic reporting of the EVM data.

• Define the authorized work elements for the program. A work breakdown structure (WBS), tailored for effective internal management control, is commonly used in this process.

• Establish and maintain a time-phased budget baseline, at the control account level, against which program performance can be measured. Initial budgets established for performance measurement will be based on either internal management goals or the external customer negotiated target cost including estimates for authorized but vaguely defined work. Budget for far-term efforts may be held in higher-level accounts until an appropriate time for allocation at the control account level. On government contracts, if an over-target baseline is used for performance measurement reporting purposes, prior notification must be provided to the customer.

Desired Outcomes Implementation and adoption of Performance-based acquisition management practices and processes, including integration of program scope, schedule and cost objectives, establishment of a baseline plan for accomplishment of program objectives, and use of earned value techniques for performance measurement during execution of the program. A performance-based acquisition (as defined in the Federal Acquisition Regulation 37.102) or an acquisition with a defined quality assurance plan that includes performance standards/measures should be the basis for monitoring the contractor.

3.3.9 Task Area 9, Enterprise Services

The Contractor shall advise and provide Engineering Design with respect to Systems, Technology Shared Services, Data Engineering, Platform Engineering, Software Engineering, Architectural, Program and Project Tasks and initiative Management support for legislative and regulatory critical systems, Demand, Governance, Program and Project support. Provide systems analysis and design, solution concept, logical and physical engineering design, interface, XML Schema, performance and infrastructure design content delivery, and engineering analysis of alternatives.

The Contractor shall advise and provide Enterprise Services with architecture and infrastructure service delivery mechanisms and shall advise on and support performance of applications and systems testing in the following areas:

• Functional Testing of IRS tax administration, financial, and other corporate applications.

• Integration Testing of IRS tax administration systems (groups of inter-related applications) to ensure data integrity and anticipated outputs as information is shared across related applications during simulated Production processing.

• Regression Testing of IRS tax administration, financial, and other corporate applications to verify correction of defects identified during initial rounds of Functional Testing.

• 508 Accessibility Testing of IRS tax administration, financial, and other corporate applications to verify correction of defects.

• Exploratory Testing of IRS tax administration, financial, and other corporate applications to verify correction of defects.

• Performance Testing of IRS tax administration, financial, and other corporate applications to verify correction of defects.

• Usability/UX Testing of IRS tax administration, financial, and other corporate applications to verify correction of defects.

• Creation and Maintenance of Synthetic Data for use in IRS tax administration, financial, and other corporate applications to verify correction of defects.

• Engineering of Enterprise Informatica Platform (EIP) for Informatica Suite of Products v10 and above

• Engineering of Enterprise Document Management Platform (EDMP) for Documentum

Suite of Products v20 and above

• Engineering of Tableau Enterprise Visualization (TEV) for Tableau suite of products v2022 and above (may include other Visualization tools in the future)

• Engineering of Business Objects Enterprise (BOE) for SAP BI v4.3 and Crystal Reports v2016 and above

• Develop tools and documentation, to level and align Demand including time boxing build and delivery phases

• O&M…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .