1. Help Center
  2. DC Project Suite
  3. Support Plan and Product Licensing

Problem Resolution

Resolution Process

All problems and queries raised under our support plan are handled as tickets by our Help Desk. Each ticket describes the problem or question that needs to be resolved and is used by our team to ensure they can resolve the problem as quickly as possible. The resolution process works like this:

  1. Customer reviews support knowledge base.
  2. Ticket opened through our portal or by e-mail.
  3. Automatic Help Desk acknowledgement.
  4. Assign support engineer.
  5. Initial response by assigned engineer.
  6. Engineer confirms/reproduces the problem and issues immediate workaround if available.
  7. If additional work required for resolution, engineer provides periodic status updates.
  8. Ticket resolved according to severity. Unresolved tickets escalated according to severity.

Ticket Severity

Ticket severity is used to help us match our resources to demand and prioritize tickets so that problems get solved according to each customer's need. Our team will work with these definitions to determine how tickets should be solved:

  • Severity 1. Bugs that prevent some function or process from substantially meeting Specifications and which seriously affect the overall performance of the function or process and for which no known work-around exists.
  • Severity 2. Bugs that prevent some function or process from substantially meeting Specifications, but have a reasonable work-around.
  • Severity 3. Bugs that prevent some portion of a function from substantially meeting functional specification but do not seriously affect the overall performance of the function.

Resolution Targets

 Severity 1 2 3

Acknowledgement

Immediate Immediate Immediate

 

Initial response by engineer

 

8 hours (or next day for after hours) 8 hours (or next day for after hours) 24 hours

 

Escalation

 

3 business days 7 business days 7 business days

 

Resolution

 

Issue fix in code as soon as available Issue immediate workaround. Where viable, issue fix in code in next software release Fix in code considered for inclusion in future software release