Digicorp
Home Services Industries About Contact
Enterprise ↗ Get in touch
Legal & Compliance

Service Level Agreement Terms

PT. Digicorp Solusi Internasional  ·  Effective 01 January 2026  ·  Applies to all managed service contracts

Contents

  1. Scope and Application
  2. Service Hours
  3. Priority Levels
  4. Response and Resolution Targets
  5. Uptime Commitment
  6. Incident Management
  7. Service Credits
  8. Exclusions
  9. Client Responsibilities
  10. Reporting
  11. Review and Amendments

1. Scope and Application

These SLA Terms ("SLA") form part of the agreement between PT. Digicorp Solusi Internasional ("Digicorp") and the Client for the provision of managed IT services. They define service-level commitments, measurement methodology, and remedies for non-compliance.

The specific service tiers and commitments applicable to a Client are confirmed in the Service Order. Where the Service Order specifies different targets, those targets prevail over the defaults in this SLA.

2. Service Hours

Digicorp operates the following support tiers:

  • Business Hours (BH): Monday–Friday, 08:00–17:00 WIB (UTC+7), excluding Indonesian public holidays
  • Extended Hours (EH): Monday–Saturday, 07:00–22:00 WIB
  • 24/7 Coverage: All hours, including weekends and public holidays — available for Critical and High priority incidents under managed service contracts that include NOC coverage

The applicable support window for a Client is specified in the Service Order.

3. Priority Levels

Priority Definition Examples
P1 Critical Complete service outage or severe degradation affecting all or the majority of users; significant business impact with no workaround Core network down, server cluster failure, security breach, total VPN loss
P2 High Significant impact on a group of users or a business-critical function; workaround may be available but is inadequate Key application intermittent, backup failure, firewall policy error, partial connectivity loss
P3 Medium Limited impact affecting individual users or non-critical systems; acceptable workaround exists Single user unable to connect, printer offline, email delay, non-critical service degraded
P4 Low Minimal or no immediate impact; informational requests, how-to questions, and scheduled change requests New user setup, software installation, configuration change request, documentation query

4. Response and Resolution Targets

Response time — time from ticket submission to a Digicorp engineer acknowledging the incident.
Resolution target — target time to restore service or deliver a confirmed fix. Complex issues may require a workaround first, with a permanent fix scheduled separately.

Priority Response Time Resolution Target Applies During
P1 Critical 15 minutes 4 hours 24/7
P2 High 1 hour 8 business hours 24/7 (response) / BH (resolution)
P3 Medium 4 business hours 3 business days Business Hours
P4 Low 1 business day 5 business days Business Hours

Resolution targets assume Client provides timely cooperation and access. Time spent waiting for Client response is excluded from resolution-time calculations.

5. Uptime Commitment

For managed infrastructure services, Digicorp commits to the following monthly uptime targets, measured on a rolling calendar-month basis:

Service Tier Monthly Uptime Target Max Allowed Downtime / Month
Standard Managed 99.5% ~3 hours 39 minutes
Premium Managed 99.9% ~43 minutes
Mission Critical 99.95% ~21 minutes

Uptime is calculated as: ((Total Minutes in Month − Unplanned Downtime Minutes) / Total Minutes in Month) × 100. Scheduled maintenance windows (agreed in advance) are excluded from downtime calculations.

6. Incident Management

6.1 Reporting channels

Incidents may be reported via:

  • Helpdesk portal — ticketing system (URL provided at onboarding)
  • Email — helpdesk@digicorp.co.id
  • Phone — +62 811 294 7711 (P1/P2 critical line, 24/7)

6.2 Escalation

If a P1 incident is not acknowledged within 15 minutes or a P2 is not acknowledged within 1 hour, Client may escalate by calling the critical line. Unresolved P1 incidents exceeding 2 hours automatically escalate to Digicorp's senior engineering lead.

6.3 Communication

For P1 and P2 incidents, Digicorp will provide status updates at minimum every 60 minutes until resolution. A written incident report (root-cause analysis) will be delivered within 5 business days of P1 resolution.

7. Service Credits

Where Digicorp fails to meet the uptime commitment in Section 5 due to causes within Digicorp's reasonable control, Client may claim service credits as follows:

Monthly Uptime Achieved Credit (% of Monthly Fee for Affected Service)
99.0% – < SLA target10%
98.0% – < 99.0%20%
95.0% – < 98.0%30%
< 95.0%50%

Credits must be claimed in writing within 30 days of the month in which the failure occurred. Credits are applied as a deduction against the next invoice and represent the sole financial remedy for SLA misses. Maximum aggregate credits in any calendar month shall not exceed 50% of the monthly fee for the affected service.

8. Exclusions

SLA commitments do not apply to downtime or degradation caused by:

  • Scheduled maintenance windows agreed with Client in advance (minimum 48 hours' notice for standard maintenance; emergency maintenance as soon as practicable)
  • Actions or omissions of Client or third parties not under Digicorp's reasonable control
  • Failure or underperformance of Client-supplied hardware, software, or internet connectivity
  • Force majeure events as defined in the Terms of Service
  • Upstream cloud or carrier outages (e.g. AWS, Azure, Telkom, XL Axiata) beyond Digicorp's control
  • Security incidents caused by Client's failure to apply recommended patches or configurations within agreed timelines
  • Services explicitly listed as out-of-scope in the Service Order
  • Beta, preview, or trial services

9. Client Responsibilities

To enable Digicorp to meet its SLA commitments, Client agrees to:

  • Provide remote access credentials and access permissions as required
  • Respond to Digicorp's requests for information or approvals within the timeframes specified in the open ticket
  • Notify Digicorp at least 5 business days in advance of planned changes to the IT environment that may affect managed services
  • Apply security patches to Client-managed endpoints within the timelines recommended by Digicorp
  • Maintain valid licences for all software under management
  • Designate at least one authorised technical contact available during business hours

10. Reporting

Digicorp provides the following standard reports:

  • Monthly Service Report — uptime metrics, incident summary, SLA performance, and open action items; delivered within 5 business days of month-end
  • Quarterly Review — trend analysis, capacity observations, and roadmap discussion; scheduled jointly with Client
  • On-demand — ticket status and real-time monitoring data accessible via the helpdesk portal at any time

11. Review and Amendments

SLA targets are reviewed at each annual contract renewal or upon significant change in the managed environment. Digicorp may update these SLA Terms with at least 30 days' written notice. Where changes materially reduce protections, Client may terminate the affected Service Order with 30 days' notice without early-termination penalty.

Questions about your SLA? Contact your dedicated account engineer or email helpdesk@digicorp.co.id.

Digicorp

PT. Digicorp Solusi Internasional — enterprise IT built around how your business actually works. Trusted across SEA, monitored 24/7.

Company

Home Services Industries About Contact

Legal & Compliance

Privacy Policy Terms of Service SLA Terms

Reach us

info@digicorp.co.id +62 811 294 7711
© PT. Digicorp Solusi Internasional · Digital Transformation. Sustaining Enterprises. Enterprise IT · Cloud · Security · Managed Services