SLA & Service Commitments

What We Commit To

Structured, Severity-Based Response

TRIOTECH SYSTEMS provides structured technical support and operational response based on the severity and business impact of an issue.

For services covered by an applicable service agreement, incidents are classified by severity and handled according to the response targets below.

Severity Levels

Response Targets by Priority
P1

Critical

Response: 15 minutes

Critical incidents with significant or complete loss of service.

Examples:
  • Production outage
  • Critical security incident
  • Major infrastructure failure
  • Issue causing significant loss of service
P2

High

Response: 1 hour

High-impact incidents causing substantial degradation or affecting important production functionality.

Examples:
  • Major service degradation
  • Important production failure
  • Significant infrastructure issue
  • Issue with substantial business impact
P3

Normal

Response: 4 business hours

Non-critical issues that affect functionality but do not cause a major service interruption.

Examples:
  • Non-critical service issue
  • Configuration problem
  • Limited production issue
  • Issue with limited business impact
P4

Low

Response: 1 business day

Routine requests and issues with limited or no immediate operational impact.

Examples:
  • General support request
  • Minor issue
  • Documentation request
  • Routine assistance

Response Time vs. Resolution Time

Service Level Definitions

Response time means the time taken to acknowledge the incident and begin handling it.

Response time does not represent a guaranteed resolution time. Resolution depends on the severity and complexity of the incident, the affected environment, third-party dependencies, required client actions, and other technical factors.

Response Time

The time taken to acknowledge an incident and begin handling it.

Resolution Time

The time required to resolve an incident may vary based on its complexity, dependencies, and technical conditions.

Uptime Commitment

Defined Per Agreement

Uptime commitments are defined according to the applicable service agreement and client contract.

Specific uptime targets, planned maintenance windows, exclusions, measurement methods, and any applicable service credits are confirmed in the applicable agreement before service begins.

Uptime targets are service-specific and are established in the applicable client agreement rather than published as a universal commitment.

Support & Incident Handling

24/7 Monitoring & Escalation

Depending on the service and agreement, TRIOTECH SYSTEMS may provide monitoring, alerting, incident response, escalation, remediation, and ongoing infrastructure support.

Our 24/7 monitoring services are designed to detect and respond to infrastructure issues continuously, with defined response procedures and escalation paths.

Key Highlights of Support:

Monitoring

Continuous infrastructure monitoring and alerting.

Incident Response

Structured handling and escalation of operational incidents.

Remediation

Technical investigation and corrective action where included.

Ongoing Support

Infrastructure and operational support based on the applicable agreement.

Scope of Service Commitments

Covered Under Your SLA

These response targets apply only to services and support arrangements covered by the applicable client agreement or SLA.

The applicable agreement defines:
  • Covered services and systems
  • Support channels
  • Service hours and coverage
  • Severity classification
  • Response targets
  • Uptime measurement
  • Planned maintenance
  • Exclusions and dependencies
  • Escalation procedures
  • Any applicable service credits

Need Guaranteed Response Times?

For engagements requiring defined response times and service commitments, contact TRIOTECH SYSTEMS to discuss the appropriate support and SLA structure.

Update cookies preferences