5000188832 Middleware_Support_PWS_FY24_RRT_final 05012024.doc

PERFORMANCE WORK STATEMENT (PWS)

For Internal Revenue Service

Enterprise Operations (EOps), Infrastructure Services Division (ISD), Middleware Services Branch

Operation and Maintenance (O&M) and Development Support

Part 1

General Information

1. General: This is a service contract to provide Middleware Operation and Maintenance (O&M) and Dev Support to Enterprise Operations (EOPs), Infrastructure Services Division (ISD), Middleware Services Branch (MSB). The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

1.1 Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and services necessary to perform Middleware Operation and Maintenance (O&M) and Development Support for Enterprise Operations (EOPs), Infrastructure Services Division (ISD), Middleware Services Branch (MSB) as defined in this Performance Work Statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

1.2 Background: Enterprise Operations (EOps) is a large, highly distributed organization under IRS Information Technology (IT), with responsibilities that span all parts of the IRS. EOps provides enterprise level 24x7x365 support for business applications and other IRS systems. The environment is complex with all tiers of Information Technology (IT) represented including Unisys/IBM mainframes, and Solaris/Windows/Linux servers of all sizes. Software includes Oracle and DB2 database management systems, Commercial Off-The-Shelf (COTS) (e.g., including MQ Series, Business Objects, Informatica, WebSphere, JBoss, WebLogic, EAIB/webMethods, etc.); and custom code.

Middleware falls under the Infrastructure Services Division (ISD) of EOps. Middleware supports a variety of COTS and custom infrastructure application components within the enterprise. COTS products include: SiteMinder, CA Directory, Informatica, WebMethods, BOE, IBM MQ Series, JBoss, WebSphere, QMail, XML Gateway, etc. These components are shared among business applications: Affordable Care Act (ACT), Foreign Account Tax Compliance Act (FATCA), Modernized eFile (MeF), e-Services, Integrated Financial System (IFS), Internet Refund Fact of Filing (IRFOF), Internet Employer Identification Number (IEIN), CADE2, etc. Each application has unique business requirements and each use different features of the COTS products. This makes COTS product configuration very complex and requires highly skilled technical support staff. Middleware provides technical and O&M support from front-end portals to the back-end systems including infrastructure interfaces between systems, e.g., Security Audit and Analysis System (SAAS), and Error Store. In addition to COTS product configuration and customization.

1.3 Objectives: The Internal Revenue Service Information Technology (IT) office objective is to acquire a contractor to support the ISD Division that will provide contractor personnel who possess significant skills, expertise, knowledge, and experience needed to provide and perform supports tasks highlighted in Part 5 - Tasks.

1.4 Scope: This Performance Work Statement (PWS) outlines the requirements for Infrastructure Services Division (ISD) to be provided with Middleware support. The support covers enterprise level 24x7x365 (Business hours, after hours, weekend and holidays) support to enable interoperability between applications that run on different operating systems, by supplying services so the application can exchange data in a standards-based way. Our mission is to provide business applications and other IRS systems Middleware services as defined in the Tasks section of this PWS.

1.5 Period of Performance: The period of performance shall be a twelve (12) month base period with four (4) twelve (12) month option periods. Performance shall take place at on-site and off-site within commuting distance and with reasonable access to the Customer’s facility (work sites) located at:

Enterprise Computing Center

250 Murall Drive

Martinsburg, WV 25430

Internal Revenue Service

5000 Ellin Road

Lanham, MD 20706

(50%) Government’s site

(50%) Contractor’s site, with reasonable access to government site (contractor personnel can travel to government site for meetings within two hours’ notice and at reasonable travel costs.)

Transition-In Period: POP (3 months)

Base Period: 10/06/2024 – 10/05/2025

Option Period 1: 10/06/2025 – 10/05/2026 Option Period 2: 10/06/2026 – 10/05/2027

Option Period 3: 10/06/2027 – 10/05/2028

Option Period 4: 10/06/2028 – 10/05/2029

1.6 General Information

1.6.1 Quality Control: The contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control program assures work complies with the requirement of the contract. After acceptance of the quality control plan the contractor shall receive the contracting officer’s acceptance in writing of any proposed change to his QC system.

1.6.2 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan. This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.3 Recognized Holidays:

New Year’s Day

Labor Day

Martin Luther King Jr.’s Birthday

Columbus Day

President’s Day

Veteran’s Day

Memorial Day

Thanksgiving Day

Juneteenth

Christmas Day Independence Day

1.6.4 Business Hours of Operation: The contractor is responsible for conducting core business, between the hours of 9am-5pm (EST) Monday thru Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. For other than firm fixed price contracts, the contractor will not be reimbursed when the government facility is closed for the above reasons. The Contractor must always maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

1.6.6 Type of Contract: The government will award a Firm-Fixed Price contract.

1.6.7 Security Requirements: All Contractors employees, providing support under this task order, shall complete Unauthorized Access (UNAX) and IT Security Training annually. In addition, each individual Contractor employee shall sign a non-disclosure form. The Contractor shall conduct Disclosure Awareness training prior to giving officers and employees access to the SBU data and annually thereafter if the contract is renewed or extended. Each participant must sign and date the training roster. The Contractor is to provide written certification to the COR that this training was held.

Due to the requirement for continuous availability of the system, Contractor resources assigned to the contract shall have approved Moderate Background Investigations (MBIs).

Under FISMA, government employees and Contractors are subject to Federal information security laws, regulations, and policies, including annual security awareness training. This training requirement is satisfied by the IRS mandatory Information Protection briefing, which covers computer security, disclosure, privacy, and UNAX.

The Contractor Officer will ensure contractor personnel are in compliance with IRS HSPD-12 PIV Procedures Manual. This manual will be provided to the awardee.

1.6.7.1 Physical Security: The contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.

1.6.7.2 Key Control: The Contractor shall establish and implement methods of making sure all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the Government shall be duplicated. The Contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the Contracting Officer.

In the event keys, other than master keys, are lost or duplicated, the Contractor shall, upon direction of the Contracting Officer, re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the Government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the Contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the Contractor.

The Contractor shall prohibit the use of Government issued keys/key cards by any persons other than the Contractor’s employees. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the Contracting Officer.

1.6.7.3 Lock Combinations: The Contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons. The Contractor shall ensure that lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations. These procedures shall be included in the Contractor’s Quality Control Plan.

1.6.8 Special Qualifications: N/A

1.6.9 Post Award Conference/Periodic Progress Meetings: The Contractor shall attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.6.10 Contracting Officer Representative (COR): The (COR) will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance: maintain written and oral communications with the Contractor concerning technical aspects of the contract: issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

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

Contractor employees identified as Key Personnel will be dedicated to this project. If any changes in proposed key personnel become necessary during actual performance, the contractor will provide written notification 60 days in advance. In the event of a sudden change in key personnel (death, incapacitation, immediate termination, etc.), the contractor will provide written notice to the CO within 3 calendar days of the event. For any substitution, the contractor will submit justification with a proposed substitute whose qualifications are equal to or greater than the person being replaced, along with a 1-to-2-page introductory summary, in sufficient detail to permit evaluation within 10 calendar days of notification of a substitution.

The contractor will provide the following key personnel:

Labor Category

Subject Matter Expert

Senior IT Specialist

IT Specialist

Senior IT Technician

Security Specialist

Application Engineer

Database Analyst/Programmer

Software Developer/Programmer

System Software Engineer

Program Manager

The Contractor will submit the resumes of the contractor employee(s) that will fill the position(s) identified in the table above.

Middleware O&M Labor Categories Position Descriptions Subject Matter Expert

Senior IT Specialist

IT Specialist

Security Specialist

Applications Engineer

Database Analyst/Programmer

Software Developer/Programmer

Systems Software Engineer

Program Manager Functional Requirements

Other duties assigned by supervisor.

Senior IT Technician

1.6.12 Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed. Contractor personnel will be required to obtain and wear badges in the performance of this service.

1.6.13 Contractor Travel: Contractor will be required to travel CONUS and within the NCR during the performance of this contract to attend meetings, conferences, and training. The contractor may be required to travel to off-site training locations and to ship training aids to these locations in support of this PWS. Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. All travel requires Government approval/authorization and notification to the COR.

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

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

Travel and per diem will be reimbursed at actual cost in accordance with the limitations set forth in FAR 31.205-46 and the General Services Administration’s Federal Travel Regulations. Profit will not be applied to the travel costs. Local travel may be required for on-site meetings, etc.

1.6.14 Other Direct Costs: This category includes travel (outlined in 1.6.13), reproduction, and shipping expenses associated with training activities and visits to contractor facilities. It could also entail the renting of suitable training venues.

1.6.15 Data Rights: The Government has unlimited rights to all documents/material produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

1.6.16 Organizational Conflict of Interest: Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications, or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may effect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.6.17 Transition Planning

1.6.17.1 Transition-In/Kick-Off Meeting:

Within seven days of this award, the Government and VENDOR shall conduct a kick-off meeting with all stakeholders. The Government does not desire an elaborate kick-off meeting, nor does it expect VENDOR to expend significant resources in preparation for this meeting. Rather, the intent of the meeting is to initiate the communication process between the Government and VENDOR by introducing key participants, explaining their roles, reviewing communication ground rules, and assuring a common understanding of contract requirements and objectives.

1.6.17.2 Transition-Out

The transition-out period is defined as forty-five (45) business days prior to contract completion or at the end of an option period or if the following option period is not exercised or another IRS designated date (i.e. notice to terminate). Contractor shall remain responsible for the full performance of all efforts identified in this PWS and will cooperate fully with the IRS staff and/or the new incumbent Contractor.

PART 2

DEFINITIONS & ACRONYMS

2. Definitions and Acronyms:

2.1. DEFINITIONS:

2.1.1. CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.

2.1.2. CONTRACTING OFFICER. A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.3. CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.4. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.5. DELIVERABLE. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.1.6. KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.7. PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

2.1.8. QUALITY ASSURANCE. The government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

2.1.9. QUALITY ASSURANCE Surveillance Plan (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.10. QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.11. SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

2.1.12. WORKDAY. The number of hours per day the Contractor provides services in accordance with the contract.

2.1.12. WORK WEEK. Monday through Friday, unless specified otherwise.

2.2. ACRONYMS:

ACOR

Alternate Contracting Officer's Representative

CCE

Contracting Center of Excellence

CFR

Code of Federal Regulations

CONUS

Continental United States (excludes Alaska and Hawaii)

COR

Contracting Officer Representative

COTR

Contracting Officer's Technical Representative

COTS

Commercial-Off-the-Shelf

FAR

Federal Acquisition Regulation

HIPAA

Health Insurance Portability and Accountability Act of 1996

KO

Contracting Officer

OCI

Organizational Conflict of Interest

OCONUS

Outside Continental United States (includes Alaska and Hawaii)

ODC

Other Direct Costs

PIPO

Phase In/Phase Out

POC

Point of Contact

PRS

Performance Requirements Summary

PWS

Performance Work Statement

QA

Quality Assurance

QAP

Quality Assurance Program

QASP

Quality Assurance Surveillance Plan

QC

Quality Control

QCP

Quality Control Program

TE

Technical Exhibit

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3. GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1. Services (If applicable): N/A

3.2 Facilities (If applicable): The Government will provide the necessary workspace for the contractor staff to provide the support outlined in the PWS to include desk space, telephones, computers, and other items necessary to maintain an office environment at the following locations:

Internal Revenue Service (onsite) 5000 Ellin Road

Lanham, MD 20706 Enterprise Computing Center-Martinsburg (remote) 250 Murall Drive

Martinsburg, WV 25430

Enterprise Computing Center-Memphis (remote)

5333 Getwell Road Memphis, TN 38118

3.3 Utilities (If applicable): The Government will provide all utilities in the facility will be available for the contractor’s use in performance of tasks outlined in this PWS. If utilities are furnished, the following is required: The Contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions that preclude the waste of utilities, which include turning off the water faucets or valves after using the required amount to accomplish cleaning vehicles and equipment.

3.4 Equipment (If applicable): The Government will provide Agency issued laptops and access to fax machines, printers, lighting and sound, and standard office equipment when contractor staff is on-site.

3.5 Materials (If applicable): N/A

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1 General (If applicable): The Contractor shall furnish all supplies, equipment, facilities, and services required to perform work under this contract that are not listed under Section 3 of this PWS.

4.2 Secret Facility Clearance (If applicable): N/A

4.3. Materials (If applicable). The Contractor shall furnish all materials, supplies, and equipment necessary to meet the requirements under this PWS.

4.4. Equipment (If applicable). The Contractor shall furnish all equipment not specified to meet the requirements under this PWS.

PART 5

TASKS

5. Tasks:

5.1 Basic Services: The contractor must provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and personnel services necessary to perform Middleware Operation and Maintenance (O&M) and Development Support for Enterprise Operations (EOPs), Infrastructure Services Division (ISD), Middleware Services Branch (MSB)

5.2 Task Heading: The following section specifies the Performance Objectives and Performance Elements for the Tasks the Contractor shall provide to ISD:

Task 1: Troubleshoot COTS and infrastructure applications. Due to the complexity of these products, Middleware SMEs must have an in-depth technical knowledge of the COTS products and applications as well as deep understanding of their related OS systems including Solaris, Linux, Mainframe, and Windows.

Task 2: Develop monitoring, troubleshooting utilities, and installation packages using Perl, ansible playbooks, and shell scripts. Over the last few years, several applications were added to the Middleware support list. As new applications are developed which require existing COTS and custom infrastructure integration, associated support requirements will grow proportionately, and the complexity of Middleware required support will increase.

Task 3: Manage the enterprise integration platform by installing, configuring, and supporting COTS products and corresponding applications on its servers. Additionally, Middleware develops, enhances, and maintains a custom automated process that permits Middleware project builds to be scripted and rapidly deployed to all environments without manual intervention. This involves coordination with other teams including Enterprise Services, EOPS, DBAs, UNS, Directory Management, IRS project teams and vendor support. Utilizing Ansible tower and Openshift for containerization deployments.

Task 4: Provide 24x7x365 production technical support for weekend deployment windows and on-call triage.

Task 5: Provide operations and maintenance support within the pre-production environments.

Task 6: Respond to IRWorks trouble tickets according to their severity within the time frames published by End User Equipment and Services (EUES) in IRWorks Ticket Priorities and C.3.2.1.3 IRWorks Support.

Task 7: Provide Middleware Management with Restoration Critical Assessment (RCA) input to RCA reports as requested by Government.

Task 8: Provide the Middleware POC with a daily written status report indicating support activities performed in the last 24 hours. This report will be rolled up into the monthly project status report for metrics.

Task 9: Support the Government Integrated Project Team (IPT) in monitoring infrastructure production performance and providing O&M support to ensure that system performance is optimized. The contractor will support the IPT to conduct and perform engineering and analysis activities and to develop recommendations and plans to handle peaks for filing periods for all products assigned to MSB.

Task 10: Provide assistance, as directed by the Government, in supporting technical refreshment activities pertaining to middleware components. The work to be performed will support planning, scheduling, testing, and implementing refreshment activities.

Task 11: Provide installation configuration SMEs to configure middleware packages; in support of development, test, and operations. Installations configurations will conform to all applicable policies, procedures, settings, and evaluations necessary to make the system operational.

Task 12: Support Enterprise Operations by maintaining current or applicable versions of installed middleware COTS packages in production.

Task 13: Update and deliver the Middleware documentation for each O&M change to the infrastructure delivered. It is the Government’s desire to be compliant with the One Enterprise Life Cycle (One ELC) or Information technology Infrastructure Library (ITIL) documentation requirements.

Task 14: Participate on IPT teams with SME’s from Government, as requested by the IRS. Both Government and Contractor personnel will accomplish knowledge transfer (communication of technical and non-technical concepts, principles, and activities).

Task 15: At the Government’s request, will provide specific support to Government SME’s in understanding both custom coded such as SSO, EDA, JEDA, SOR, AE and COTS derived middleware.

Task 16: Participate with associated projects in solving integrated development and test environment issues (such as network, firewall, access control, other integrated products) ensuring that they are integrated (end to end) with releases that move out into production at the same time according to the overall release plan.

Task 17: The Contractor’s Program Manager will provide project management support for the Middleware O&M Team. Support will consist of managing and coordinating all Middleware Contractor tasks, submission of reports, presenting briefings on the status of the contract, and participating in meetings with the IRS for the purpose of discussing issues of concern relative to the project. Meetings may be conducted via TEAMS or face-to-face in the Washington, D.C. (NCFB) metropolitan area, the Enterprise Computing Centers – Martinsburg (ECC-MTB) and Memphis (ECC-MEM).

Task 18: Support Government TAD or other testing organization in developing and executing the following:

· System Integration Tests and Functional Integration Tests (SIT/FIT), which includes and satisfies Combined System & Integration Test (CSIT), and System Acceptability Testing (SAT) testing requirements for the full production deployment.

· IEP and EUP System Integration Test, which satisfies all testing requirements for the production deployment of IEP and EUP. This, in conjunction with an EITE version of the system, will provide Business capability for early testing with registered third-party users.

· The scope of the above testing will include the application, and cross-project dependencies (e.g., MeF and e-Services) including support across mainframe and server domains.

· Provide deployment planning and Development Site Readiness Test (DSRT)

Task 19: Provide Security Test & Evaluation (ST&E) support, understanding of IRS IRM and STIG requirements.

Task 20: Test plans will address all functional requirements, as wells as system performance, volume processing, and environment test setup

Task 21: Test reports will identify all test and requirement issues and related steps taken or recommended to correct them.

Task 22: Testing will be in accordance with the test documentation.

Task 23: Testing will satisfy all project requirements

Task 24: All DR’s issued as a result of the integrated test will be entered and tracked to closure in the Government IRWorks.

Task 25: Support and follow Government CM processes for all components, including promotion into production.

Task 26: Develop and submit a monthly status report. This report will include information as to the status of: Production Support, Problem Analysis, and Infrastructure Application O&M Development.

Task 27: Provide support to the Government in the development of a Middleware strategic plan. This plan will be updated on a semi-annual basis.

Task 28: Develop custom code which is used in conjunction with COTS products to satisfy the requirements of applications that cannot be met by the “out-of-box” COTS features.

Task 29: Knowledge in C/C++, Java, .net, COBOL using DB2, CICS, and MQ Series, LDAP, J2EE and Database APIs. They execute on Solaris, Linux, Mainframe and Windows platforms.

Task 30: Support the analysis, design, development; testing, deployment and troubleshooting for the various projects that utilize Webmethods. This effort is based upon the projects functional requirements. This includes but not limited to having an in-depth knowledge of Webmethods and API Gateway. Provide support for ACA applications that use the SiteMinder Agent for JBoss.

Task 31: Provide webmethods SME support to testing teams and ACA RLTS team to resolve issues in webmethods test and production environments. Support ACA using current SDK. Troubleshoot any Siteminder Authentication related issues for ACA on a needed base.

Task 32: Manage developed middleware custom code to ensue software and hardware compatibility with the current or anticipated production environment.

Task 33: Support the infrastructure application design effort to ensure proper integration of application functionality.

Task 34: Perform installation of the infrastructure application software, whether custom code or COTS.

Task 35: Support the infrastructure application development within the guidelines of the OneELC.

Task 36: Install GFE infrastructure application updates or enhancements.

Task 37: Installation and Configuration of SAP BOE and Informatica in IRS environment.

Task 38: Troubleshoot, identify root causes, and provide solutions for BOE and ETL issues.

Task 39: Implement BOE, Informatica and ETL best practices based on IRS implementation.

Task 40: Maintain multiple Oracle rack datasources and work with the DBA on the regular driver updates.

Task 41: Build and deploy latest code from RTC and GitHub.

The contractor will provide support to agency personnel in a collaborative rapid delivery software development environment. Daily and Weekly Team meetings, in addition to Monthly status reports and meetings are required to monitor performance. Collaboration, product metrics, and data shall be provided on an ongoing basis for input into two key information areas 1) product quality, and 2) service quality to ensure the IRS acceptable technical support.

5.3 SUB-TASKS – LABOR HOUR

5.3.1 SUB-TASK 1, Kick-off Meeting

Standard

The kick-off meeting will be held at the Government's facility and both parties will mutually agree upon the date and time 7 days after award, the contractor will 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 completion of this briefing will result in the following:

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

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

3. The Government may provide any GFP to the contractor at this time.

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

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

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

Customized (Standard briefing plus the additional elements listed below).

Not desired (If checked, please discuss with the Procurement Staff).

5.3.2 SUB-TASK 2, RAMP-UP KNOWLEDGE TRANSFER

The contractor shall participate on IPT (transition like) teams with SME’s from Government, as requested by the IRS. Current Contractor personnel will accomplish knowledge transfer (communication of technical and non-technical concepts, principles, and activities).

Where appropriate, the contractor should work to enhance the knowledge and skills of the employee. The Contractor, at the Government’s request, will provide specific support to SME’s in understanding both custom coded and COTS derived middleware. Additionally, the Contractor shall support Government management in the development and delivery of custom presentations on specific products, processes, projects, status, and new ways of doing business. The contractor shall provide the following:

· Provide subject matter expertise in defining Infrastructure training

· Conduct technical meetings and briefings with receiving organizations’ SMEs

· Conduct Knowledge Enhancement Seminar(s) to describe specific infrastructure changes in release

A semi-annual or as required, schedule and format will be produced jointly by Government and Contractor management that identifies appropriate topics to be presented. Presentation material on technical subjects will be in a format mutually agreed upon by Government and the Contractor.

5.3.2.1 Transition Planning

The Contractor shall appoint a Transition Manager to lead and oversee the transition from the incumbent Contractor. The Government will review the Contractor proposed O&M Transition Plan to develop and deliver any detailed changes to the Transition Plan. The proposed draft Transition Plan will identify the Contractor resources and roles involved in the transition process (including for in-process activities), provide a list of risks and mitigation strategies for the transition, and contain a detailed, resource balanced project schedule developed with Microsoft Project. The project schedule will identify the work to be performed, dependencies, deliverables, and milestones, and include milestones for dependencies to other project stakeholders.

The Government will have 2 days to review the draft Transition Plan and provide comments to the Contractor. Government and Contractor representatives will then meet to discuss the comments after which the Contractor will have 2 days to incorporate the agreed-upon changes and deliver a final transition plan.

At contract award, the Contractor will also deliver the project team staff roster and contact information by when-within how many days? – Should be a part of the transition plan noted in the paragraph above. The IRS TPOC/COR will provide to the contractor in electronic format the Strategic Forecasting and Analysis and/or other required security investigation forms. At no time prior to the contractor’s staff receiving their “Interim Staff Like Access” memo, are they permitted to work on and access project information. The contract award has to be done at least 90 days prior to the end of the current contract to perform a full transition.

5.3.2.2 Transition Execution

Upon project start, the Contractor will begin executing against the Transition Plan. The contractor will provide a status to the Government that will include, at a minimum:

1) an updated project status with percent complete, actual start, and actual finish updated;

2) any issues encountered and associated mitigation strategies;

3) any risks identified and associated mitigation strategies; and

4) updates to action items assigned.

The Contractor’s key representatives will attend daily stakeholder meetings to discuss the status of the transition.

5.3.2.3 Transition Deliverables

The following table lists the deliverables and expected timeframes associated with the Middleware Transition work area. Deliverables listed below will be required in accordance with the Middleware project schedule.

5.3.3 SUB-TASK 3, TRANSITION TO SUPPORT (T2S)

The transition to support process will 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.

· Monitor and report system performance and workload.

· Transfer of complete documentation for all delivered functionality. Deliverables will be in softcopy and hardcopy format and will 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 configurable data including usernames and passwords and application settings.

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

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

The Contractor shall provide the following within a Transition Plan:

· Training material, if appropriate

· All Technical support, activities and documentation should be transferred to enable Government personnel to effectively continue the current level of support and activities.

· Status report

· Planned activities

· Issues encountered

· Risks Identified

· Updates to action items assigned

· Contractor’s key representatives to attend bi-weekly stakeholder’s meetings to discuss the status of the knowledge transfer. This includes, but is not limited to the following:

· Supporting team members and other IRS staff working on the assignment

· Sharing information and considerations…