BPA Attachment III -Sample Task Order - PWS.pdf

EDOS Performance Work Statement (PWS) for SAMPLE TASK ORDER

Project: Sample EDOS PWS

1.0 INTRODUCTION AND BACKGROUND

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. Within AD, support is required for the following area:

The objective of Foreign Account Tax Compliance Act (FATCA) is the reporting of foreign financial assets;

withholding is the cost of not reporting. FATCA targets tax non-compliance by U.S. taxpayers with foreign accounts. FATCA focuses on reporting:

• By U.S. taxpayers about certain foreign financial accounts and offshore assets

• By foreign financial institutions about financial accounts held by U.S. taxpayers or foreign entities in which U.S. taxpayers hold a substantial ownership interest.

In order to support this legislation, the IRS has a number of systems and applications that are used to interface with the taxpayer. Support is needed to ensure that any new work emerging form this legislation is supported, as well as enhancements made to existing systems. Additionally, current systems and application must also be maintained during normal processing while updates are being made to enact new and emerging legislation relating to this work.

2.0 TASK ORDER OBJECTIVES

The scope of work for this requirement is set forth as a collection of task areas necessary for successful project planning, management, and execution for both Sustainment – Operations & Maintenance (O&M) and Development, Modernization and Enhancement (DME) activities.

The Contractor shall provide technical services and subject matter expertise to support requirements as defined in PWS Section 3.0. These services and expertise will include the following:

• Provide general project management oversight and reporting

• 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 forms and applications for receipt and processing of high-volume financial data in alignment with existing IRS security, reliability, performance, and capacity requirements

• Ensure International forms and applications mutually agreed upon Application Programming Interfaces

(APIs) to enable integration with the current IRS processing environment and legacy systems

• Design and validate enterprise security features, reliability, performance, and capacity requirements

• Advance taxpayer service by improving service options for the tax paying public, facilitate participation in the tax system by all sectors of the public and simplify the tax process.

• Modernize information systems to improve service and enforcement

• Modernize business processes and align the infrastructure support to maximize resources devoted to front-line operations.

• Knowledge sharing and skill transfer is encouraged.

3.0 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, and application development in support of IRS IT missions. 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 shall support and accommodate changes and enhancements for FATCA. This will include supporting business processes. Contractor shall support, enhance, upgrade, maintain, and sustain day-to-day O&M, project management, software development, and developmental O&M sustainment. The Contractor shall assist the Government in their effort to provide highly reliable and secure IT services and integrated business services support that meets or exceeds customer requirements and expectations.

The activities and responsibilities of the contractor will include those identified under the task areas listed below.

PART ONE: FIRM FIXED PRICE (FFP) SUB-TASKS

TASK 1 - EDOS Project/ Program Management Support (Reference EDOS BPA Task Area 1: Project and Program Management Support)

SUB-TASK 1.1, Orientation Briefing Within 5 business days of task order award, the contractor shall conduct an orientation briefing for the Government. The Government does not desire an elaborate orientation briefing nor does it expect the contractor to expend significant resources in preparation for this briefing. Rather, the intent of the briefing is to initiate the communication process between the Government and contractor by introducing key task order participants, explaining their roles, reviewing communication ground rules, and assuring a common understanding of task order requirements and objectives.

The orientation briefing shall be held at a Government's facility or virtually and both parties shall mutually agree upon the date and time.

The completion of this briefing shall result in the following:

1. Agenda items will be created by the Contracting Officer’s Representative (COR) and presented to the Contractor within one day after award. The Contractor shall send the COR any additional agenda items they would like on the schedule.

2. The briefing will be 3 hours maximum, not including two 15-minute breaks.

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

4. The Government will show the applicable facilities to the contractor if the contractor will be performing work on the Government's site.

5. The Government may provide Agency authorized GFP to the contractor upon receiving clearances.

6. Any issues concerning the contractor clearances for contractor personnel will be discussed.

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

8. The contractor shall provide the accounting period end dates to be used for the term of this task order.

The Contractor shall take Meeting Minutes and Attendance Roster and deliver these along with an electronic copy of the Orientation Briefing materials to the COR within 5 business days after conducting of Orientation Briefing.

SUB-TASK 1.2 Period of Performance Summary Report The Contractor shall provide the Government with financial and progress reports that are accurate and timely and aid the Government in monitoring project performance from a perspective that balances cost, schedule, technical requirements, and customer satisfaction.

The Government reserves the right to request this report at any point during the performance of the order at the discretion of the Contracting Officer. This ad hoc report, if desired, will only be requested once during the life of the task order and is in addition to the regularly scheduled Period of Performance Summary report.

SUB-TASK 1.3 Program Management Support All tasks identified in Program Management shall be completed throughout the lifecycle of the project to include project close-out. Project Management tasks shall be performed for all Applications Development (AD) efforts identified in the scope of this Task Order.

SUB-TASK 1.3.1 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 and meets the performance objectives of defined requirements.

Contractor support shall include, but is not limited to, the following:

• Monthly tracking and reporting of costs, to be issued with monthly status reports,

• Configuration management support,

• Quality Management and support:

• Risk management and risk mitigation plan development:

• 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

• Provide training on the software development tools, languages, and applications once a month or as required and requested by the government project manager, not to exceed three sessions per month.

• Demonstrate an in depth understanding of planning, managing, and executing a project under the industry standards related to the agile methodology.

• Prepare and conduct bi-weekly risks and issues status meetings/reports.

o Reporting shall incorporate all functional areas, identifying progress and 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.

o Coordination of change requests (CR) and submissions to Training Review Board (TRB)/Change Control Board (CCB), as needed

• Transfer knowledge of technical skills and lessons learned from resolving incident reports, efforts to streamline old code basis, and defining requirements accurately to IRS staff upon completion of deliverables and work products.

SUB-TASK 1.3.2 Project Management Governance Services 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 apply global leading practices to achieve the most efficient, effective, and comprehensive business analysis, design, development, and implementation. The contractor shall possess global knowledge and depth, regarding achieving organizational readiness and effective large-scale change management and bring ideas and concepts to implement leading practices.

Contractor support shall include but is not limited to:

• 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 TO.

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

• The Contractor shall adhere to all IRS Privacy Information Protection and Data Security standards as referenced in IRM 10.5.4. Detailed information about IRS IRM 10.5.4 will be provided to the Contractor upon TO 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.2 will be provided to the Contractor upon Task Order award.

SUB-TASK 1.4 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 validate and update the strategic direction for the International Information Processing & Exchange (IIPE) and database by communicating and keeping up to date with new emerging technologies within and outside of the Government. The Contractor shall assist in the development of new programs as identified by the program office to deliver emerging technology solutions that adhere to IRS (IRM 21.3.7.7) and Treasury regulatory guidance (Treasury Regulation 1.6012-2) on International Tax Processing. 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

• Presentations on relevant topics for consideration in developing service requirements, usually two per year, one for Mid-Year and One for Filing Season or as needed for new, emerging, and late legislation.

• Research on industry best practices and commercial service offerings, usually two per year, one for Mid-Year and One for Filing Season or as needed for new, emerging, and late legislation.

• Requirement’s consensus briefings, and meeting minutes.

SUB-TASK 1.5 Stakeholder Coordination & Management The Contractor shall perform tasks on-schedule and on-budget as well as integrate efforts with designated IRS project team(s).

SUB-TASK 1.6 Quality Management & Support The Contractor shall utilize designated IRS ELC processes, in compliance with IRS guidelines and by CMMI Level 3 process standards or a like model. With quality gate reviews defined throughout the ELC including production support, IRS will use defect data from quality assurance activities to control quality defect levels and performance.

SUB-TASK 1.7 Status Reports & Meetings The Contractor shall monitor, manage, and report the multifaceted release development efforts and provide updates to the integrated master schedule maintained by the FATCA PMO 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 FATCA PMO and technical stakeholders to support any additional status reporting requirements that result from subsequent ELC 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.

• 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.

DESIRED OUTCOMES:

The Contractor shall perform tasks on-schedule and on-budget, integrate efforts with FATCA PMO, business and technical stakeholders and conform to the designated IRS Enterprise Life Cycle (ELC) development path and methodology, as tailored for this program. The Contractor shall complete the tasks and provide the deliverables based upon agreed schedule.

TASK 2 - OPERATIONS AND MAINTENANCE (O&M) (Reference EDOS BPA Task Area 4:

Operations & Maintenance (O&M) Support)

This section addresses Operations & Maintenance (O&M) Tasks as they relate to each specific application and/or program area.

SUB-TASK 2.1 Foreign Account Tax Compliance Act (FATCA) Contractor shall provide support to the Applications Development (AD) to sustain systems and applications designed to support the . Operations and Maintenance (O&M) provides continuous, high-availability services as established by operating agreements. Contractor shall provide technical expertise to identify, document and implement disciplined, repeatable procedures to operate, sustain, and manage International Forms Submission Processing and Storage Support.

The operations and maintenance processes shall include, but not be limited, to the following:

• Knowledge transfer of technical skills and lessons learned to IRS staff upon completion of deliverables and work products

• 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

SUB-TASK 2.1.1 Program Performance Management The Contractor shall provide program cost modeling and analysis, adhere to Internal Revenue Manuals (IRM) (IAW IRM 2.148.1 IT Support Services Management Directive, https://www.irs.gov/irm/part2/irm_02-148-001 and 2.148.2 Incident Management Process, https://www.irs.gov/irm/part2/irm_02-148-002), track and analyze metrics, maintain performance scorecards, document and maintain service inventories, and provide periodic updates, analyses, and recommendations of the Operations Administration and Maintenance Plan. Performance management reports shall be generated for those areas of International forms and applications requiring oversight.

In addition, the Contractor shall provide cost modeling and comparison analyses of new technology, service, and management initiatives. White papers and position papers shall be developed in the areas of International Forms Submission Processing and Storage Support. Also, recommended pricing policies and cost recovery mechanisms shall be developed and documented.

SUB-TASK 2.1.2 Program Enhancement (System Upgrades, Technology Refresh) The Contractor shall assist in the analysis of potential program upgrades and enhancements. This includes, but is not limited to developing technical evaluations, identifying, and documenting requirements, and performing preliminary architectural designs.

The Contractor shall develop alternative analyses and business cases. Business cases shall be properly documented, and briefings and presentations will be authored summarizing the analyses and business cases.

The Contractor shall develop, document, and maintain program, project, and transition plans during the life of the Task Order. The Contractor shall edit existing data and create or write code so that applications UWR, programs, or software are capable of interfacing with IRS specific applications, programs, or software for analytical and statistical purposes.

SUB-TASK 2.1.3 Transition and Implementation Support The Contractor shall provide project support for the transition and implementation of International Forms Submission Processing and Storage Support. The Contractor shall conduct assessments of implementation and operations requirements, testing, and assist in providing implementation planning, program management, and the development of test and acceptance criteria. The Contractor shall maintain and update a contract-based list of documents, schedules, and information needed to assist in tracking and achieving operational and other transitional activities. The Contractor shall also develop Concepts of Operations (CONOPS) documentation for International Forms Submission Processing and Storage Support.

Deliverables shall include, but are not limited to:

• Site Survey Template(s) https://www.irs.gov/irm/part2/irm_02-148-001 https://www.irs.gov/irm/part2/irm_02-148-002

• Gap Analysis and Mitigation Plan(s) capturing IT and FM service gaps

• Transition Site and Project Plan(s). Plan(s) shall include transition template(s), detailed steps, schedules, and phases of transition.

• Test and acceptance Plan(s)

• Quality and Security Assurance Plan(s)

• Disaster Recovery Plan(s)

• Risk Management Plan(s)

• Staffing and Training Plan(s)

SUB-TASK 2.1.4 Training, Communications, and Marketing The Contractor shall provide market survey support, plans, and materials for IRS programs to include but not limited to customer and market surveys. The development of a training plan on the software development tools, languages, techniques and procedures used during the software development, enhancement, and maintenance process for work being performed on projects. This training plan shall be included as part of program transition as required.

• The Contractor shall complete the tasks and provide the deliverables based upon agreed schedule at the expected level of detail needed for continued programmatic support.

SUB-TASK 2.1.4(a) (optional)

• Provide knowledge sharing and lessons learned training to designated Government personnel in the form of job-shadowing and observation on current systems application software, program support, configurable data including usernames, passwords, and application settings is integral in preparing IRS employees to assume the role of System Owners or Administrators as appropriate.

• Provide training and knowledge transfer activities to include, but not limited to: on-site experience with the FATCA, 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:

o Conduct refresher training sessions o All technical support, activities and documentation should be transferred to enable Government personnel to effectively continue the Current Systems Programs support.

o Provide examples of Issues encountered and measures taken to mitigate/fix identified issues o Provide examples of potential risks Identified Identify any prerequisite system access or permissions Maintaining documentation of standards and procedures for ongoing training and measures taken to mitigate identified risk

SUB-TASK 2.2 Business Systems Modernization (BSM) focused on revolutionizing the way taxpayers transact and communicate with the IRS using a Web-based approach to expand the existing third-party tools and data collection processes.

The Contractor shall support development, modernization, enhancements, and developmental O&M upgrades, maintain, and sustain the day-to-day operations of the production BSM applications systems and services, which includes but is not limited to:

• The commercial-off-the-shelf (COTS) setup and BSM applications extension code and scripts.

• COTS setup and BSM applications extension code or scripts that execute within the two access portals

(the portal for tax practitioners and non-IRS employees and the portal for IRS employees).

• COTS setup and BSM applications code or scripts in support of shared support services that provide common shared function products, such as transaction and user authentication, security enhanced communications, data access, security enhanced mailbox access, audit trails of user activity, application management services.

• Capacity Management – perform capacity planning and performance engineering functions with the infrastructure organization to ensure applications have sufficient capacity and can meet performance requirements.

• Availability Management – provide support on design and implementation for availability and support the operations to sustain application availability.

• IT Service Continuity Management – provide support on the continuity of BSM application services and provide support to the Disaster Recovery environment, the deployment of code to servers, and testing applications.

• Configuration Management – perform configuration management functions, including baseline maintenance, configuration control, status accounting, and configuration audit.

• Release Management – coordinate with stakeholders and manage release management activities of build process, production testing, and deployment.

• Incident Resolution – support the production P1-P4 incidents through the standard IRS Incident Management Process adhering to all IRMs associated with each priority of ticket.

• Job scheduling and execution support – provide support to operations on the job scheduling and execution of BSM applications.

• Change Management – comply with change management processes diligently, which activities include change impact assessment, the support of Configuration Control Board (CCB) activities, implementation, testing and deployment of changes, and the distribution of emergency changes.

• Problem Management – provide support on problem investigation and diagnosis, analysis and trending of problems including root cause analysis, and resolve problems in accordance with IRM 2.14.2 Enterprise Problem Management Standards.

Table 1 Contractor shall use tools for the below processes:

The Contractor shall support the following practices:

• The Contractor shall comply with all IRS standards and procedures, including but not limited to, Internal Revenue Manuals (IRMs) (including project management methodologies), and standard processes, such as, Enterprise Architecture, Operational Requirements, Security (FISMA/NIST 800 series requirements) and Privacy process.

• The Contractor shall use an already built data repository that houses information about returns processed by the system (accepted and rejected).

• Provide a Subject Matter Expert (SME) when needed to assist with Transition Management activities.

• The Contractor shall provide knowledge transfer to the Government and/or IRS Government

Representative. This knowledge transfer may consist of providing information to the IRS developers working with Contractor developers or may be in the form of documenting processes, document repositories, expert interviews, job aids, presentations, and/or briefings, but shall be in the format most applicable to the subject matter to be transferred

• The Contractor shall provide the following support for the BSM environments:

Process Tool Requirements Management Rational Team Concert Source Code & Design Material Test Plans Rational Rose Collaborative Lifecycle

Management (CLM) Configuration Management Rational ClearCase Schedule Management MS Project o Development Integration and Testing Environment (DITE) - Support software installation and configuration o Development/Unit Testing (DEV) - A simulated environment that mirrors the functionality of production and is limited to segments of the programming. What the programmers use to unit test.

o High Volume test environments o Application Qualification Test (AQT) - A simulated environment that mirrors the functionality of production and encompasses all of the programming. What the programmers use to finally certify the code before passing off to another team to test independently.

o System Acceptability Test (SAT) – Maintained by another entity that tests a simulated environment that is replicated to production.

o System Integration Test (SIT) - Maintained by another entity that tests how the code interfaces with other programs associated with the entire production suite of programs.

SUB-TASK 2.3 PROGRAM OPERATIONAL SECURITY SUPPORT

The Contractor shall assist the Government in providing information security to ensure that IRS services, programs, and related infrastructure are compliant with the applicable Government regulatory requirements.

This task consists of three activities, as follows:

2.3.1 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 and Accreditation Letters

2.3.2 Implementation Support for Modifications to Facilities and Systems

The Contractor shall provide implementation support for security modifications to Internal Revenue Service’s International Forms Submission Processing and Storage Support, programs, and related infrastructure.

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

• Test Plans and Reports

• SA&A Packages and Briefings

2.3.3 Risk Assessment, Vulnerability Assessment, and Policy Development

To establish consistent and repeatable IT security processes and procedures across IRS’s operational environment, the Contractor shall provide technical and IT security program development and management expertise to facilitate the development and implementation of IRS security goals, objectives, and visions. The Contractor shall conduct analyses, develop requirements, and make recommendations to improve the security posture of IRS’s security programmatic activities.

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

• Risk Assessment Reports

• Security Policies,

• FISMA submissions

• POA&M Procedures

• NIST 800-26 Assessments

DESIRED OUTCOME:

Complete all tasks and provide deliverables based upon agreed schedule at the and meets the performance objectives of defined requirements.

Successfully maintains and supports the development, modernization, enhancements, and developmental O&M upgrades of the day-to-day operations of the production BSM applications, systems, and services. The applications referenced above include all the applications listed in Section 1.0 and non-BSM applications that include, but not limited to Common Business Service (CBS) and external/internal Application Programming Interfaces (APIs) that are developed/supported within BSM.

Knowledge Sharing and training has prepared IRS employees to assume the role of System Owners or Administrators as appropriate.

TASK 4 - Earned Value Management System (EVMS) Reporting Requirements (Optional)(Reference EDOS BPA Task Area 8: Earned Value Management (EVM) Support)

The Contractor shall comply with FAR 52.234-4 Earned Value Management System (EVMS) and IRS EVM policy regarding ANSI/EIA STD -748A or an equivalent process. 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 IRS and IRS EVM policies and guidance will be provided as Government Furnished Information (GFI).

Representative Activities include:

• Providing for the completion of an Integrated Baseline Review(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.

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

• Establishing and maintaining 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.

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.

PART TWO LABOR HOUR AND/OR SERVICE POINTS SUB-TASKS –

This section addresses Labor Hours Tasks as they relate to each specific application and/or program area.

TASK 3 - Transition Services (Reference EDOS BPA Task Area 6: Transition Services)

SUB-TASK 3.1 Ramp-up Knowledge Transfer/Transition-In Support (Optional) Ramp-Up Knowledge Transfer is defined as the Contractor acquiring and understanding the necessary documentation, information, and processes related to any work in progress. This task includes frequent meetings with IRS designated Subject Matter Experts, incumbent contractor personnel, and incoming contractor to gather any tacit knowledge related to the core systems, Compliance Document Matching and Solutions Engineering/Enterprise Services tasks or programs in development. The government estimates this task will take approximately 60-90 days to complete after the Task Order is awarded for all task areas included in the scope of effort.

The Contractor shall appoint a knowledge transfer manager to oversee the transfer of knowledge and ensure all areas are accounted for. If desired, this can be the Project Manager (PjM) or Project Scheduler. Prior to the transfer of knowledge, the Contractor shall develop and deliver a draft Knowledge Transfer Plan (KTP) within 3 calendar days after orientation briefing. The KTP shall 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 with Microsoft Project. 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 business days).

The Government shall have 10 business days to review the draft KTP and provide comments to the Contractor.

Government and Contractor representatives will then meet to discuss the comments after which the Contractor shall incorporate the agreed-upon changes and deliver a final KTP within five working days of the government’s feedback.

The contractor shall meet with the IRS bi-weekly (twice a month) to discuss the progress of the knowledge transfer. The Contractor shall provide an updated MS Project Schedule and discuss any risks or concerns at this time.

The Contractor shall perform the following activities during the transition-in period:

• Assign personnel and submit security papers within 2 business 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

• Offerors shall provide Ramp-Up Staffing Plan and describe how they will bring resources on board in coordination with the ramp down efforts of the incumbent.

• Offerors shall provide Knowledge Transfer Plan/Checklist

SUB-TASK 3.2 Ramp-Down Knowledge Transfer/Transition-Out Support (KTS) (Optional)

Within 60 calendar days of the completion of performance of this task order (or as designated by the IRS), the contractor shall fully support the transition of the contractor’s work that is turned over to another entity, either government or a successor contractor. The contractor shall assist with transition planning and shall comply with transition milestones and schedules of events.

The contractor shall be responsible for the implementation of the transition and application cutover activities.

The transition shall cause no disruption in development services or operations. To ensure the necessary continuity of services and to maintain the current level of support, IRS may retain services of the incumbent contractor for some, or all, the transition period, as may be required.

The contractor shall be responsible for the transition of all technical activities identified in this task order. As part of the transition, the contractor shall be responsible for but not limited to the following:

• Inventory and orderly transfer of all GFP, to include hardware, software, and licenses, Contractor Acquired Government Property, and Government Furnished Information (GFI)

• Transfer of documentation currently in process

• Transfer of all software code in process

• 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

• Provide members to and participate in transition management team

• Develop, maintain and update a Knowledge Transfer Plan for IRS staff outlining Submission

Processing Management capabilities and functions.

• Operations and maintenance processes and procedures.

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

Additionally, it is further understood that knowledge transfer from the Contractor to IRS employees in the form of job-shadowing and observation is an integral and inherent part of the scope of work. Such knowledge transfer is critical to prepare IRS employees to assume the role of System Owners or Administrators as appropriate.

DESIRED OUTCOMES:

The Contractor provides a Knowledge Transfer Plan that is accepted by the Government and successfully completes knowledge transfer in accordance with the plan. Transition-in Plan/Checklist are accepted and completed.

Contractor shall provide a Knowledge Transfer Plan to encompass at a minimum all aspects of delivered functionalities, major tax reform changes and is accepted by the Government and successfully completes knowledge transfer out in accordance with the plan. Contractor shall walkthrough detailed instruction on artifacts, location, and pertinent notes on decisions. Documentation of work assignments to contractor personnel for maintenance, modification, and development responsibilities for various Programs under this PWS shall be developed, maintained, recorded, and provided to the Government.

Task 5 Development, Modernization & Enhancement (DME) Support (Reference EDOS BPA Task Area 3: Development, Modernization & Enhancement (DME) Support)

SUB-TASK 5.1 FATCA DATABASE

The FATCA Database will store the source data submitted for International Information Processing & Exchange (IIPE) forms processing.

The Contractor shall:

• Identify, assess, develop, test, and manage the inter-dependencies necessary to meet FATCA Database delivery objectives for International Information Processing & Exchange (IIPE) processing. Under the direction of the FATCA PMO, the FATCA Database shall meet all standards, policies, and procedures as laid out in relevant Internal Revenue Manuals (IRM) (https://www.irs.gov/irm) and other IRS Enterprise Architecture standards.

SUB-TASK 5.1.1 Design, Coding, Testing, & Integration The Contractor shall produce an efficient transactional Database designed to act as the data repository of record for all International Information Processing & Exchange (IIPE) processing. The FATCA Database shall receive export processing from the International Forms Submission Processing and Storage Support, identifying source information and receive large data batches directly from the authoritative sources.

SUB-TASK 5.1.2 Database Architecture Capabilities The Contractor shall produce a modular architecture that ensures the reuse of existing data structures, operational reporting, and data integration with external systems. The architecture must provide performance, scalability, and transaction processing to accommodate identified customers. The Database must also provide flexibility to support future policy changes. Support in conducting functionality, capacity and performance testing (processing high data volume) on supporting application(s). Initial testing has been performed and baseline established. Once architectural design accepted, further testing will be conducted onsite IRS location.

Document the functionality and performance test results in an agreed upon format, that will meet IRS standards, and include an acceptable level of detail that can be referenced and compared to performance testing for future system enhancements.

SUB-TASK 5.2 BSM System Enhancements, Modernization, DEVOPS The Contractor, at the option of the Government, may be tasked to work System Enhancements, Modernization and Monitoring that are aligned to BSM to both direct and indirect applications which can include, but not limited to Common Business Services (CBS), and Application Programming Interface (API) scope.

Optional system improvements, developmental software upgrades, maintains enterprise level, entity services to support AD applications requiring the update of legacy and modernized data stores that provide incremental improvements in system capabilities within the BSM suite of web-based, self-assisted services that allow authorized individuals to do business with the IRS electronically. Examples of the activities to be considered in the efforts includes, but is not limited to:

• Supporting analysis of requirements/changes specified in change requests (CRs), Break Fix or Unified Work Request (UWR).

• Supporting current CBS infrastructure Linux/JBoss EAP 6.6 with FUSE 6.2 with supporting Oracle databases.

• Implementing impacting mandated changes to the application suite as required

• Supporting desired conversions of the application suite to align and integrate with outside BSM applications

• Integrating with current IRS on-line enterprise solutions, which includes WebApps (Online Accounts)

BSM needs to align with the enterprise Modernization and DevOps strategies. The Contractor may be requested to support these tasks. Examples of the activities to be considered in the efforts includes, but are not limited to:

• Developing and implementing additional enterprise Application Programming Interface (API) strategies.

http://irm.web.irs.gov/ https://www.irs.gov/irm

• Incorporating Development, Testing, and Production enterprise monitoring tools and techniques to BSM

• Implementing Automation Testing for the BSM Application suite

• Implementing Automated Deployments to align with Continuous Integration / Continuous Development strategy

• Migration of BSM Software Development Lifecycle to Agile methodologies and adoption of the enterprise Agile toolset

SUB-TASK 5.3 Phone and Communications System Enhancements, Modernization, DEVOPS The Contractor shall support development, modernization, enhancements, and developmental O&M upgrades, maintain, and sustain the day-to-day operations in support of IRS phone and communications applications systems and services, which includes but is not limited to:

The commercial-off-the-shelf (COTS) setup and communication applications extension code and scripts

1. Responsible for the maintenance of the set-up and custom COTS applications code, scripts and any other code or software that provides communications functionality beyond the standard COTS product. The Contractor is not responsible for the installation and daily operations of the actual production environment other than to support problem and performance resolution.

2. Actively participate in planning, scheduling, and installation with other support organizations of updates to underlying COTS products utilized in the communications applications.

3. At the direction of the IRS, the development, integration, testing, deployment, and subsequent evaluation of enhancements to the production communications systems to comply with current and/or future Unified Work Request (UWR) requirements.

4. Problem Management – provide support on problem investigation and diagnosis, analysis and trending of problems including root cause analysis, and resolve problems in accordance with IRM 2.14.2 Enterprise Problem Management Standards.

5. Need resources that know Angular, REACT, Node.js. JQuery, JavaScript, Splunk, Spring Framework, DevOps Tools (Jenkins, SonarCube, Appscan, Openshift, Containers etc.)

Successfully turn around responses to and perform UWR workload. Provide alternate solutions that offer a more efficient process to perform the solutions being proposed by the Government.

Provide a design concept for the FATCA Database incorporation with the existing modernized Information Returns Database (IRDB) structure. Management is specified in O&M, limited to file and form management, reciprocal exchange of data monitoring for overall process flow. Identify requirements for future release, case selection and management, as needed. Contractor shall propose an improvement recommendation for database performance.

TASK 6 - Operations and Maintenance (O&M) (Reference EDOS BPA Task Area 4: Operations & Maintenance (O&M) Support) – These labor hour subtasks shall be optional, as needed, to support current & additional international application forms are received for systems supported under this Task Order.

SUB-TASK 6.1 International Forms International Forms Submission Processing and Storage Support shall be completed throughout the lifecycle of the project.

For new International Forms or under existing international forms, the Contractor shall:

• Support IRS business systems requirements definition and documentation, including linkage to requirements traceability matrix (RTVM)

• Configure submission receipt, validation, error processing, status and log processing, data transformation and storage capabilities

• Update the International forms and applications COHs to reflect incremental functionality

• Update, maintain, and integrate new and updated international forms into the IRS Enterprise

• Aggregate, package and reuse transmitted domestic reporting data under existing infrastructure which exchange international data with treaty countries

• Update/maintain application with security remediation changes per Cybersecurity findings, guidance, and recommendations.

SUB-TASK 6.1.1 Unit Testing

• Conduct unit tests on all system-level and application specific changes

• Conduct DIT and DSIT testing prior to transmittal to SAT

• Create Unit Test Reports in such a way that it can be easily associated with the software version provided in the transmittal and listed in the Transmittal Memorandum

• Plan and conduct Application Quality Testing (AQT), Testing will be coordinated with other impacted stakeholders, International Information Processing & Exchange (IIPE) and will be completed prior to transmittal to EST

• Provide support during Unit Testing, including an orientation session, as necessary to familiarize IRS test personnel with the functionality of the software in accordance with the requirements and any process/application/system changes required for the new software version

• Provide development support and project level testing of application functionalities through defect resolution

SUB-TASK 6.1.2 Systems Analysis The Contractor shall perform systems analysis. This analysis may include trade studies, performance analysis, simulations, prototypes, life cycle cost and labor analysis, spares analysis, logistics analysis and personnel staffing analysis, as required.

SUB-TASK 6.1.3 Software Engineering Support The Contractor shall analyze software concepts, approaches, and requirements to support the system design, and generate software specifications as required.

SUB-TASK 6.1.4 Interface Design The Contractor shall support the design and implementation of new/modified system interfaces (both external and internal) and define the characteristics of studies required for this effort.

SUB-TASK 6.1.5 Specialty Engineering Support The Contractor shall provide specialty engineering as required. Specialty engineering activity may include analysis and documentation of system security requirements, human factors requirements; operator, user, and maintainer staffing requirements; Section 508 accessibility compliance; and survivability and/or vulnerability of the system design.

SUB-TASK 6.1.6 Technical Reviews The Contractor shall support and participate in technical reviews, to include preparation of presentation material, review of documentation pertinent to the review, attendance at review meetings, and completion of review action items.

SUB-TASK 6.1.7 Process Design The Contractor shall perform top-level design or process level design of software. This applies to top-level design of the Computer Software Configuration Items (CSCIs).

SUB-TASK 6.1.8 Design Analysis/Validation The Contractor shall perform analysis of alternate design approaches and design validated studies for the total software system. Use of IRS approved open-source software is authorized with no negative impact to the performance and cost and the solution meets all guidelines.

SUB-TASK 6.1.9 Prototyping/ Demonstrations The Contractor shall prototype critical items, as directed. This includes design, implementation, testing and demonstrations of prototypes.

SUB-TASK 6.1.10 COTS Software Procurement The Contractor shall analyze and recommend COTS products for incorporation in the International Information Processing & Exchange (IIPE) software. Approval of all COTS system software used on IRS information systems must be obtained by the Director of Enterprise Architecture and be within scope of the overall Enterprise Data Strategy initiatives. See Enterprise Architecture Standards Profile link:

http://ea.web.irs.gov/ESP/Search/Search.aspx?searchmode=basic

SUB-TASK 6.1.11 Development Tools Implementation The Contractor shall implement tools and development environment required for software development.