DSDillon / Business applications
Custom Software Support and Maintenance
Agree software support hours, monitoring, incident handling, access controls, updates, backups and restoration arrangements.
Know who responds when work stops
The support agreement names the application, hosting, device and provider responsibilities. It states coverage hours, severity levels, response targets and escalation. Around the clock coverage is a separate arrangement.
Operators need a clear first check and a point at which to stop retrying. A pending payment, unavailable calendar and failed document import require different recovery steps.
Keep access and changes controlled
Define the roles allowed to view, create, approve, export and administer records. Sensitive actions can require another approval. Staff and accountant access follow explicit owner authorization.
The maintenance scope includes session handling, supported dependencies and the review of external API changes. Secret keys remain outside the public interface.
Test the restored system
Agree backup frequency, retention, location and the required recovery position. A restoration test checks that the application opens and its documents, balances and attachments agree with the saved state.
Records created after the latest backup and work still on offline devices need a reconciliation plan. The operating guide identifies how the business resumes and who approves recovery.
Release updates with a recorded result
A release is checked against normal workflows and the interruptions that can create duplicates or missing records. Rule changes retain their version and effective date.
The support record should identify the affected function, confirmed outcome and any action the operator needs to take. Additional work and changes to scope follow the agreed approval process.
Start with the business problem
Tell us what needs to change.
Bring the current process, the software you use and the result you need. We will work through the scope, connections and delivery requirements.
