A23 Attachment A_ Performance Work Statement.pdf

PERFORMANCE WORK STATEMENT

Defense Finance and Accounting Service (DFAS)

Trust Funds Reporting System (TFRS) Analysts & Expansion Support

1. GENERAL: This Purchase Order (P.O.) is to provide Analyst and Developer support for the Trust Funds Reporting System (TFRS) in Indianapolis, Indiana.

1.2 Background: Trust Funds Reporting System (TFRS) is the major application for Trust Fund

Accounting and Reporting (TFAR) organization within DFAS Enterprise Solutions and Standards (ESS). TFRS is utilized for recording and reporting the activities of DoD managed trust and special funds held by TFAR. DoD managed trust and special funds operate in accordance with Public Law 98-94 of United States Code, qualifying DoDFMR Volumes (12, 6A, 4, 6B) and OMB Circular A-

136. This module operates within DoD Special Reporting, Accounting HQ, and uses Microsoft Dynamics GP for recording and reporting activities within the DoD managed trust and special funds:

Military Retirement Fund (MRF) Unfunded Liability Amortization Payment Account, MRF Concurrent Receipt Payment Account, Medicare Eligible Retiree Health Care Fund (MERHCF) Unfunded Liability Amortization Payment Account, Defense Cooperation Special Fund Account, Burden Sharing Special Fund Account, MERHCF Special Fund Account, MRF Trust Fund Account, Education Benefits Trust Fund Account, Defense Gift Trust Fund Account, National Security Education Trust Fund Account, Voluntary Separation Incentive Trust Fund Account, Host Nation Support for Relocation (Japan, Korea, and Kuwait) Trust Fund Account, Host Nation Support for Relocation (Guam) Trust Fund Account, and Mutually Beneficial Activities Special Fund Account.

The Dynamics GP application is also utilized for the Military Housing Privatization Initiative (MHPI). Through MHPI, direct loans and loan guarantees are available to private developers to provide housing options to military families. We are currently moving the application from the DFAS terminal servers to a DFAS hosted web-based environment. Contractor assistance is needed to make this transition.

1.2.1 System Architecture

System Architecture Description o TFRS currently operates in a DFAS terminal server farm environment contained within the DFAS DBCE Blue Cloud. User access to the application is through the DFAS terminal server farm via remote desktop connection. The application is a Microsoft COTS product written in Dexterity. The database engine is SQL.

1.2.2 Hardware

Client Hardware o Currently, site provided equipment must be able to support CAC certificate-based logon to the DFAS terminal server application.

Requirements for access are the HTTP/3 and transport layer security (TLS) 1.3 capable browser (preferably MS-Edge 140.0.3485.94 or newer).

o All sites must request access to the TFRS platform(s) through Defense Finance Accounting Services (DFAS) firewalls.

Server Hardware o TFRS is hosted on equipment located at the DFAS Virgina.

Functional Users o Sites are responsible to provide the functional users equipment capable of supporting an DBCE connection.

Technical Users o Sites are responsible to provide the technical users equipment capable of supporting an DBCE connection.

Communication Environment: End user accesses the TFRS application through an DBCE connection.

1.3 Objectives: The objective of this PWS is to define the tasks necessary to obtain the technical information and technology support services needed to implement and configure the DFAS Trust Funds Reporting System (TFRS).

1.4 Scope: The contractor shall provide all necessary personnel, management, administrative, and technical services to meet the requirements and/or tasks outlined in this PWS for TFRS. In carrying out such efforts, the contractor shall:

Be responsible for performing business case development, requirements analysis, support and elicitation that adheres to the TFRS software implementation, configuration and data migration requirements.

1.5 Period of Performance: The period of performance shall be for one (1) base year of 12 months and two (2) 12-month option years.

Base Period: 3/1/2026 – 2/28/2027 Option Year 1: 3/1/2027 – 2/29/2028 Option Year 2: 3/1/2028 – 2/28/2029

1.6 General Information

1.6.1 Quality Control (QC): 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 is the means by which it assures itself that the work complies with the requirement of the P.O. The contractor shall deliver its proposed quality control plan with their quote. When changes are made, the contractor shall submit a revised plan within 5 working days thereafter. After acceptance of the quality control plan the contractor shall receive the contracting officer’s (CO’s) acceptance in writing of any proposed change to his QC system.

1.6.2 Hours of Operation: The contractor shall conduct business; between the hours of 0600-1800 hours Monday thru Friday Eastern Time except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for any of the above reasons.

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

If the holiday occurs on a Saturday, the holiday will be observed on Friday. If the holiday occurs on Sunday, the holiday will be observed on Monday.

1.6.4 Place of Performance: The work to be performed under this P.O. will be performed via a DFAS provided Pulse Connect Secure or other DFAS provided screen sharing software.

1.6.5 On Call: The contractor shall provide on-call and after-hours support for projects (i.e., TFRS) under this PWS if requested by the System Manager and/or Technical Analyst. On-call means if a contractor receives a telephone call at home after they have completed a normal workday or extended hours at the Government or contractor site. If the problem cannot be resolved from home the contractor personnel working on TFRS projects having to do with testing and production problems shall be required to return to the Government site to resolve the problem. The contractor shall keep an after-hours log of the phone call(s) and time spent related to DFAS systems while researching the problem. The contractor shall submit the after-hours log to the COR for approval when returning to work. The after-hours log must include the following information:

Contractor name(s) Date of the call or required connectivity Start time of the call or required connectivity Stop time of the call or required connectivity Project supported Description of the work accomplished Signature and date for the contract, COR

The approved after-hours log must be submitted to the COR and be included in the Performance and Cost Report documentation.

1.6.6 Type of Contract: The Government will award a firm fixed price.

1.6.7 Security Requirements: Contractor personnel will follow the security and training requirements in DFAS 2000.1, “Force Protection Program,” DoDM 5200.01-V1-4, “DoD Information Security Program,” and DFAS 5200.1-I, “Information Security Program.” Contractor personnel will follow all host security requirements in accordance with DoD 5220.22-M, “National Industrial Security Program Operating Manual (NISPOM),” paragraph 6-105. The contractor shall immediately report any occurrences of violation of stated regulations to the CO or COR.

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 workday, Government facilities, equipment and materials shall be secured.

1.6.8 Post Award Conference/Periodic Progress Meetings: The contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The CO, COR, and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the CO 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.

1.6.9 Identification of Contractor Employees: All contractor personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties shall identify themselves as contractors to avoid creating an impression they are Government officials. Contractor personnel shall ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

1.6.10 Relocation: Relocation costs and travel costs incident to relocation are not allowable and will not be reimbursed hereunder.

1.6.11 Data Rights: Subject to the applicable DFARS clauses in the P.O.

1.6.12 Organizational Conflict of Interest: Contractor personnel performing work under this P.O. may receive, have access to, and/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.). Additionally, contractor personnel performing work under this P.O. may perform evaluation services. Due to the nature of the work associated with TFRS a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5 may exist or be created.

The contractor shall notify the CO 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 CO to avoid or mitigate any such OCI. The contractor’s mitigation plan shall be determined to be acceptable solely at the discretion of the CO. In the event the CO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the CO may affect 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.13 Interaction with Contractor Personnel: The COR shall forward questions or concerns directly to the prime program manager who is directly responsible for managing his or her own employees/subcontractor personnel.

Contractor personnel shall direct their questions or concerns to their contractor management chain and/or company representative.

1.6.14 The COR is the primary point of contact for the contractor. The COR shall interface with DFAS Information and Technology (IT) Point of Contact (POC) as well as the appropriate DFAS Site Force Protection Office POC to maintain the monthly internal system updating to DoD compliance.

To identify Site Force Protection Officers at each DFAS location consult the Agency Force Protection ePortal Page.

https://dfasportal.dfas.mil/ddss/force_protection/Pages/SiteSecurityPortalPages.aspx

Follow the link titled “Site Specific Force Protection/Security Services” in the Additional Points of Contact section near the top right side of the webpage.

The COR is responsible for monitoring all technical aspects of the contract and assisting in contract administration. COR duties include:

Ensure 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 Monitor contractor's performance and notifies both the CO and contractor of any deficiencies Coordinate availability of Government furnished property and 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, or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.7 Section 508 Compliance: This requirement is applicable to Section 508 Compliance EIT Requirements:

1) 36 CFR part 1194.21 (Subpart B) Software applications and operating systems

2) 36 CFR part 1194.41 (Subpart D) Information, Documentation, and Support

Unless the Government invokes an exemption, all EIT products and services proposed shall fully comply with Section 508 of the Rehabilitation Act of 1973, per the 1998 Amendments, and the Architectural and Transportation Barriers Compliance Board’s Electronic and Information Technology Accessibility Standards at 36 CFR 1194. The contractor shall identify all EIT products and services proposed, identify the technical standards applicable to all products and services proposed and state the degree of compliance with the applicable standards. Additionally, the contractor shall clearly indicate where the information pertaining to Section 508 compliance can be found (e.g., contractors or other exact web page location). The contractor shall ensure that the list is easily accessible by typical users beginning at time of award.

The contractor shall ensure that all EIT products and services proposed that are less than fully compliant are offered pursuant to extensive market research, which ensures that they are the most compliant products available to satisfy the solicitation’s requirements.

If any such EIT product or service proposed is not fully compliant with all of the standards, the contractor shall specify each specific standard that is not met; provide a detailed description as to how the EIT product or service does not comply with the identified standard(s); and shall also indicate the degree of compliance.

PART 2

SPECIFIC TASKS

2. SPECIFIC TASKS:

The specific tasks that the contractor shall perform are identified in the Performance Requirement Summary (PRS), which is attached hereto and fully incorporated herein. It sets forth how the contractor’s activities will be monitored and measured. The tasks required are organized into the following system lifecycle categories: program management, requirements management, technical analysis and design, software programming, testing, and production implementation activities. Each category of work has specific detailed tasks that set forth the results the contractor must accomplish and the performance measures for each. A more general description of the work required to be performed and expectations governing how that work will be performed are provided below.

2.1 Program Management

2.1.1 Schedule Reporting: The contractor shall track hours worked on various projects using codes provided to them. The tracking and updating of the above information shall be captured in a Staffing Matrix and detailed in individual project milestone charts. The contractor shall also prepare a monthly Staffing Matrix to include each contractor performing under this P.O. The Staffing Matrix shall highlight any changes from the previous report. The Staffing Matrix shall list the Contractor’s Name, Subcontractor, Start Date, Stop Date and any other information agreed to by the Government and the contractor.

2.1.2 Semi-Annual Status Reports: The contractor shall prepare and deliver a semi-annual Status Report to the COR. The contractor shall report by project/system that details the system, Government team leader, contractor(s) assigned, and summary of activities for the progress, problems encountered and solutions to the problems.

2.1.3 Performance and Cost Report: The contractor shall prepare and deliver a semi-annual Performance and Cost Report, and a Summary Project Status Report to the COR and the Project Manager.

The Contractor shall maintain and report in accordance with the Government approved Cost Breakdown Structure Summary Report, the following:

• The current status of the ongoing task order

• Relevant information regarding problem areas and course of action taken in their resolution

• Potential problems anticipated

• Significant activities, work progress, and contract costs

• Metrics and cost data

• Forecasts

• Analyses

• Achievements of contractor personnel

• Personnel Retention concerns

2.1.4 Management Reviews (MRs): The contractor shall prepare and provide Management Reviews (MRs) to identify and address progress, problems, and other pertinent information. The

Government may require these Management Reviews intermittently in order to address pertinent issues. The contractor shall identify all Subcontractors and address progress, problems, and other pertinent, detailed information. If required, the contractor shall ensure the following topics are available for discussion at the MR: the management of P.O. activities, scheduling, costs, and technical status.

2.2 Software Programming:

2.2.1 Code Programming: The contactor shall provide software programming of system change requests, production trouble reports and test discrepancy reports.

2.2.2 Unit Testing: The contractor shall, as software programing is completed, unit test to determine if functionality executes as expected and fulfills the requirements of the change request.

2.2.3 Test Script Development: The contractor shall develop test script(s) to be utilized during formal test events that exercise the integration and execution of modified source code along with the use case and data setup requirements involved with a change request.

PART 3

APPLICABLE PUBLICATIONS

3. APPLICABLE PUBLICATIONS (CURRENT EDITIONS)

Applicable publications will be provided after P.O. award as required:

3.1 Global Software Development Plan (GSDP)

3.2 Configuration Management Information System (CMIS) User’s Guide

3.3 Software Configuration Management Plan (SCMP)

3.4 DFAS 8430.1-R, December 2007 (Automated Information Systems)

3.5 DFAS 8430.01-I “System Life Cycle (SLC) Management”

3.6 Department of Defense Financial Management Regulation (DoD FMR) 7000.14-R, Vol. 5 – see http://comptroller.defense.gov/fmr/05/index.html

3.7 Various Treasury Management Regulations-see http://fms.treas.gov/regulations.html

Performance Requirements Summary

Task Objective Outcome/ Standard Acceptable Level of Performance

Surveillance Method/Measure

2.1 Program Management

2.1.1 Schedule Reporting

The contractor shall track hours worked on various projects using codes provided to them. The tracking and updating of the above information shall be captured in a Staffing Matrix and detailed in individual project milestone charts.

The contractor shall also prepare a monthly Staffing Matrix to include each contractor performing under this P.O. The Staffing Matrix shall highlight any changes from the previous report.

The Staffing Matrix shall list the Contractor’s Name, Subcontractor, Start Date, Stop Date and any other information agreed to by the Government and the contractor.

New and modified requirements/user stories created that align with the format and standards of the DDRS Requirements.

Deliverables received at least 95% of time on schedule.

Not returned more than once for revisions.

Review of schedule and requirements to assess whether completed to the necessary level of detail.

2.1.2 Semi-Annual Status

Reports

The contractor shall prepare and deliver a monthly Status Report to the COR. The contractor shall report by project/system that details the system, Government team leader, contractor(s) assigned, and summary of activities for the progress, problems encountered and solutions to the problems.

All system and requirements impacts shall be successfully identified and scoped within the appropriate template to present the complete impact of the change request.

Work completed within schedule 95% of the time.

Not returned more than once for revisions.

Review of schedule and requirements to assess whether activity completed to the

2.1.3 Performance and Cost

Reports

The contractor shall prepare and deliver a Semi-annual Performance and Cost Report, and a Summary Project Status Report to the COR and the Project Manager.

The Contractor shall maintain and report in accordance with the Government approved Cost Breakdown Structure Summary Report, the following:

*The current status of the ongoing task order *Relevant information regarding problem areas and course of action taken in their resolution *Potential problems anticipated *Significant activities, work progress, and contract costs *Metrics and cost data Forecasts *Analyses *Achievements of contractor personnel *Personnel Retention concerns

Work completed within schedule 95% of the time.

Review of gate meeting minutes to verify the level of preparedness and questions asked during the gate meeting.

2.1.4 Management Reviews

(MRs)

The contractor shall prepare and provide Management Reviews (MRs) to identify and address progress, problems, and other pertinent information.

The Government may require these Management Reviews intermittently in order to address pertinent issues. The contractor shall identify all Subcontractors and address progress, problems, and other pertinent, detailed information. If required, the contractor shall ensure the following topics are available for discussion at the MR: the management of T.O. activities, scheduling, costs, and technical status.

2.2 Software Programming

2.2.1 Code Programming:

The contractor shall provide software programming of system change requests, production trouble reports and test discrepancy reports.

All source code and system configuration impacts, as well as unit test plan activities, are successfully identified and scoped/estimated within the Technical Analysis to present the complete baseline modification impact of the change request.

Deliverables received at least 95% of time on schedule.

Analysis not returned more than once for revisions.

Review of schedule, TA and requirement to assess whether technical analysis is completed to the

2.2.2 Unit Testing

The contractor shall, as software programing is completed, unit test to determine if functionality executes as expected and fulfills the requirements of the change request.

All use cases, data configurations, and associated testing requirements shall be successfully identified and scoped within the unit, SIT and all other test event test scripts to present the complete testing impact of the change request.

Deliverables received at least 95% of time on schedule.

Analysis not returned more than once for revisions.

Review of schedule, work product and requirement to assess whether testing analysis is completed to the necessary level of detail.

2.2.3 Test Script Development

The contractor shall develop test script(s) to be utilized during formal test events that exercise the integration and execution of modified source code along with the use case and data setup requirements involved with a change request.

Complete reviews of work products and provide feedback as necessary for suggested changes.

Reviews performed following procedure prior to assigned due date with accurate feedback provided.

Review of provided feedback to ensure peer review was completed with accurate feedback.