Application Support

DTS provides ongoing support for the applications it builds, and for other applications already in service, keeping systems maintained and connected to an organization's broader operational path.

The challenge

An application that goes unmaintained after launch tends to drift away from the operational path it was built to serve, as underlying systems, requirements, and dependencies change around it.

Who this is for

Organizations that need ongoing support for an application DTS built, or for an existing application that needs to stay connected to their broader systems.

Our approach

DTS applies its Capture, Structure, Route, Resolve operating model to support work: an application's connection to the systems and workflows around it is treated as something to be maintained, not assumed to hold on its own.

What you can expect

Typical work in this track includes maintenance, monitoring, and keeping an application connected to the operational systems around it, scoped to what a specific engagement needs.

How we engage

Engagements begin with understanding the application's current state and its role in an organization's broader operational path, move through scoping, and continue as ongoing support.

Security, accessibility, and operations

DTS supports applications with the same accessibility and operational-continuity principles reflected across this site (see the accessibility statement), and security and compliance requirements are scoped explicitly for each engagement, not assumed.

Frequently asked questions

Does DTS support applications it didn't originally build?
This can be scoped depending on the application and an organization's needs -- reach out through the project enquiry link below to discuss.
Is application support a fixed-term or ongoing engagement?
This is scoped per engagement based on what an organization's systems actually need, not a fixed default term.