Sources Sought QA.pdf
PDF 85 KB Posted
- Attached to
- Standard Contract Reconciliation Tool (SCRT)
- Solicitation number
- 17Mar2026SCRT
- Issued by
-
Defense Finance and Accounting Service
About this file
This is a Sources Sought document and Questions & Answers for the SCRT (System for Contract Registration and Tracking) technical refresh requirement issued by the Defense Finance and Accounting Service (DFAS).
DFAS is seeking to modernize a legacy PowerBuilder 2019 R3 application containing approximately 1,746 objects and an Oracle 19c database. The requirement involves a technical refresh that preserves the existing four-module structure (Registration, Compare, Adjustments, Reports) and maintains like-for-like functionality across 14 external system interfaces. The solution must be based on a non-proprietary, object-oriented codebase with low-code and no-code platforms strictly prohibited. Solutions must be deployable to any IL4/IL5 cloud environment, including DISA Stratus, AWS GovCloud, and Azure Government. DFAS is open to migration to a cloud-native Oracle database provided functionality is converted like-for-like. The refreshed UI should remain visually close to the existing application except for controls native to the target technology. Full PowerBuilder source code and interface specifications will be provided post-award only. No parallel operation with the legacy system is planned, and this is a single-award contract supporting a new requirement with no incumbent contractor.
Minimum staffing expectations include software developers, a project manager, and an analyst. Cleared personnel are required. Remote work is permitted with travel up to one week per month; all development must occur on Government Furnished Equipment within the DoW network. ROM pricing should include licenses but exclude cloud hosting and operations support, with vendors expected to provide estimates at both RFI and RFP stages. Multiple aspects remain to be determined following market research, including contract vehicle, small business set-aside status, contract type, and Industry Day scheduling. No target implementation timeline, program budget, or critical schedule milestones have been defined.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| SCRT_SourcesSought-Mar2026-Final.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sources Sought: SCRT
Question Answer Is there is an incumbent contract or contractor associated to the requirement.
If any, please provide the contractor's name and contract number.
N/A
The document specifies that the solution must be based on a non-proprietary, object-oriented codebase and that low-code/no-code platforms are prohibited.
Could you please confirm whether solutions leveraging platforms like Appian would be considered within scope, or if the intent is to strictly exclude all low-code platforms?
The intent is to strictly exclude all low-code platforms.
Can DFAS provide access to the full PowerBuilder 2019 R3 source code and Oracle 19c schema prior to proposal submission, or will access be granted only post-award?
Access can only be granted post-award.
Of the 1,746 PowerBuilder objects identified, what percentage are actively used versus dormant/deprecated? Will the vendor be expected to modernize all objects regardless of active status?
We don’t currently have a means to identify inactive objects, so all objects would need to be technically refreshed.
Does DFAS intend to preserve the current 4- module structure (Registration, Compare, Adjustments, Reports) exactly, or are functional consolidations or enhancements in scope?
DFAS intends to preserve the 4 module structure. Enhancements are not in scope.
Will the refreshed application be required to run on DISA Stratus exclusively, or will vendors be evaluated on their ability to deploy to additional IL4/IL5 environments (e.g., AWS GovCloud, Azure Government)?
The target solutions should be deployable on any IL4/IL5 cloud.
Is DFAS open to Oracle database modernization (e.g., migration to a cloud-native database) as part of this eƯort, or is Oracle 19c a hard constraint?
DFAS is open to migration to a cloud-native Oracle database, as long as the functionality is converted like-for-like.
What is the current state of documentation for the 14 external system interfaces — are interface specifications, data dictionaries, and message schemas available, or will discovery rely primarily on SME interviews and code inspection?
The interfaces specifications are documented in detail, and this documentation will be provided to the selected vendor post-award.
Does DFAS have an existing RMF package (e.g.,SSP, prior ATO) for SCRT that will be inherited by the vendor, or will the vendor be required to build the ATO package from scratch?
The vendor will be expected to collaborate with the SCRT Information System Security Manager to document the new solution’s security controls and ensure compliance with requirements.
Will the vendor be responsible for obtaining the Authority to Operate (ATO), or will DFAS lead the RMF process with vendor support?
Same answer as above.
Has DFAS identified the specific DISA Enterprise ICAM endpoint and integration method (e.g., SAML, OAuth/OIDC, PIV) that the refreshed SCRT must use for CAC/PKI authentication?
DFAS has not identified a specific E-ICAM endpoint and integration method.
Does DFAS anticipate awarding this as a single prime contract, or is a teaming arrangement (prime + subcontractors) the expected vehicle?
To be determined, based on the responses received from Market Research that supports the best interest in the government.
What contract vehicle(s) does DFAS intend to use for the resulting solicitation (e.g., open market, GSA schedules, SEWP, existing IDIQ)?
To be determined, based on the responses received from Market Research that supports the best interest in the government.
Is DFAS targeting a specific small business set-aside, or will this be a full and open competition?
To be determined, based on the responses received from Market Research that supports the best interest in the government.
Will DFAS provide current system performance baselines (transaction response times, throughput, concurrent user load) for use in parallel testing benchmarks?
Yes, DFAS will provide current system performance baselines post-award.
Will the vendor have access to all 14 external systems in a test/sandbox environment, or will mock interfaces and stubs be acceptable for integration testing prior to production cutover?
DFAS will coordinate testing with interface partners and can provide sample files for inbound interfaces.
Is parallel operation of legacy SCRT and the new system (running simultaneously in production) planned during cutover, and if so, for how long?
No, parallel operation is not feasible.
Is this expected to become a single-award or multiple-award contract?
Single Award
Should ROM pricing include cloud hosting, licenses, and operations support?
ROM pricing should include licenses, but not cloud hosting nor operations support.
Will cleared personnel be required for this eƯort?
Yes
Is the expectation to perform a full UI modernization, or should the refreshed application remain visually identical?
The refreshed UI should remain very close to the existing application, except for user interface controls/objects that are native to the target technology.
Will the Government provide interface documentation for the 14 integrated systems?
Answered above.
Does DFAS have a target implementation timeline for the technical refresh?
There is no target timeline defined yet.
Will the solution remain within DISA Stratus Cloud, or are alternative hosting options allowed?
Answered above
Will subject matter experts (SMEs) be available throughout the project?
Yes – Developers, functional representatives, and the system’s security manager will be available throughout the project.
Will full PowerBuilder source code be provided at project start?
Answered above.
Would DFAS be open to allowing remote development for contractor personnel, or is there an expectation that work be performed onsite or in a hybrid model?
Remote is allowed, however, some travel may be required (up to one week per month). All development must be performed on Government Furnished Equipment and within the DoW network.
Will remote work be permitted for contractor personnel, or will there be an expectation for onsite presence during any phase of the project?
Same question as above.
Does the Government have a target implementation timeline or desired period of performance for the technical refresh eƯort?
Answered above.
Does DFAS have a preferred contract type for this eƯort (e.g., Firm Fixed Price, Time &
To be determined.
Materials, Cost Plus), or is that still under consideration?
The notice requests Rough Order of Magnitude (ROM) pricing. Would it be acceptable for vendors to provide ROM estimates at the RFP stage?
DFAS would prefer to have a ROM at both the RFI and RFP stage for planning and budgeting purposes.
Could you clarify the anticipated place of performance for this eƯort? Specifically, whether the work is expected to be performed onsite, remotely, or in a hybrid model.
Already asked above.
Can DFAS provide an estimated total program budget or funding range for the SCRT technical refresh eƯort?
NA
If an incumbent exists, would the Government be able to provide the current or previous contract value to help vendors better understand the size and scope of the eƯort?
There is no incumbent.
Is there an incumbent contractor currently supporting the SCRT application? If so, could you please share the incumbent contractor name and scope of support?
Answered above.
Would the Government be able to provide expected labor categories or a notional staƯing profile to help vendors align their proposed team structure?
At a minimum, the government would expect software developers, a project manager, and an analyst.
Could you please confirm whether DFAS is planning to host an Industry Day or vendor briefing for this opportunity? If so, would you be able to share the anticipated timeline and format?
To be determined
Is this a new or existing requirement? If this is an existing requirement, can you please provide the contract vehicle / task order information for the current support (i.e. contract / task order #, contract value, period of performance, contract type, etc.)?
This is a new requirement.
What relevant and critical schedule milestones should potential bidders be aware of as part of our response (e.g. if this
No critical schedule milestones have been defined yet.
must meet a certain date to enable DoW audit timelines)?
Which contract type does the Government expect to use for this requirement (i.e. FFP, T&M, etc.)?
To be determined
File details come from the government source that posted it. Updated .