Procurement and evaluation
Define the evaluation and delivery scope. Agree on costs and ongoing support for the program.
Evaluate the working capability
A buyer needs evidence that the system can support the work they plan to move into it. Use the requirements index to choose the workflows to evaluate. Agree on the users and input data. State the expected result before running the test.
DART is a custom platform. Agency delivery includes configuration and integration work. A feature in the application is separate from a live agency connection or accepted deployment.
Define delivery and ongoing costs
The cost of a delivered system includes both getting it ready and keeping it running. The agreement defines what USATII will deliver and operate. It separates the initial work from ongoing costs.
A one-time cost may cover data migration or a new connection. Recurring costs may cover hosting and support. One-, five-, and ten-year estimates show how those costs change over time.
Pricing is set for the program. This documentation does not publish a per-user federal price or claim a contract vehicle.
| Cost area | What changes the estimate |
|---|---|
| Implementation | The workflows to configure and the custom work to test. |
| Migration | The amount of history to move and the data problems to resolve. |
| Integrations | The source interfaces and the work needed to connect them. |
| Hosting and security | The approved environment and the controls it needs. |
| Training and support | The user groups to train and the hours of support. |
| Sustainment | The ongoing updates and changes to maintain. |
Agree on the service model
Once the system is in use, users need to know who will help and when. The support agreement defines coverage hours and escalation. It states how incidents are reported and how updates reach the customer.
Response and recovery targets need an agreed environment. Tests must show that the setup can support them. Provider and agency responsibilities belong in the same plan.
Resolve delivery risks early
A delivery plan should address problems while there is still time to respond to them. Resolve the largest risks early. Poor source data can delay migration. Missing interface access can block integration. Security review can affect activation.
Each risk needs an owner and a test or decision. The plan states what happens if the risk becomes a problem.
Discuss a DART evaluation
A useful demonstration follows a buyer’s own work rather than a general tour. A DART evaluation starts with the mission workflow and expected users. Bring the relevant source systems and intended hosting environment. USATII can then define a demonstration around the work.