Service Catalogue

Service Catalogue

OVERVIEW

A Service Catalogue outlines all of DeployPartners Managed Services service requests available for clients to assist in keeping their services online or to improve their existing deployments. 

PURPOSE

The purpose of the Service Catalogue is to provide an agreed services that can be requested by clients. This document can be customised for each client or contract.

PREREQUISITES

Contract

The client must have an active contract with available hours with DeployPartners.

System

In order to deliver services DeployPartners personnel must be onboarded to the clients systems.  The following systems are typical, but not limited to, the standard enterprise customer environment:

  • Remote Access

  • Authentication and Authorisation services (LDAP, AD, SAML, CyberArk, etc)

  • Privileged Access Management - (CyberArk, Tokens, Cards, etc) 

  • Mail services - (Global Address Lists, Mail client, etc)

  • File repositories - documentation and processes relevant to role and related roles

  • IT Service Management - Change, Incident, Problem queues, tools, processes and templates

  • Verification and Validation - Tools and related systems

  • Policies - Security, Change, WHS&E, etc

  • Code/Configuration repositories

  • Deployment tools

Dependencies

The prerequisites will be managed through DeployPartners Project Management system known as CRUX. The Risks, Issues, Dependencies, Actions and Constraints of projects (RIDAC) will be updated and communicated during the weekly update with the customer until resolved.

Vendor Scopes 

Deploy have certification and experience in a large number of systems and vendors which we will support:

  1. Zenoss

  2. IBM Netcool

  3. Netscout

  4. Splunk

  5. Elastic

  6. CyberArk

  7. ScienceLogic

  8. Splunk

  9. InfoVista

  10. BMC (Remedy)

  11. HP (MicroFocus)

LIST OF SERVICES

Process

Each request will broadly take the following approach with exceptions generated and included as they become apparent:

  1. Review incoming request for completeness and accuracy;

  2. Develop code to specification;

  3. Test the code in the development environment (INT);

  4. Provide to stakeholders for testing;

  5. Create Change Request (if required);

  6. Engage or provide artefacts to the Support Provider to implement changes (if required);

  7. Implement change (unless relevant Support Provider chooses to do so); and

  8. Hand over to relevant support team. 

Generic Services

The following is a generic list of services. Additional services can be added upon request.


Id

Service

Type

Vendor

Description

Typical Duration

1

Enablement Service(s)

Adhoc Request

<all>

Provide onsite/remote services to help adoption of a system or capability. 

1+ Days - NEG

2

Training Service(s)

Adhoc Request

<all>

Provide onsite/remote services to train users.

1+ Days - NEG

3

Architecture Service(s)

Adhoc Request

<all>

Provide architecture roadmap or provide integration reviews.

1+ Days - NEG

4

Small Configuration Change

Standard

<all>

Data change to an established feature or capability 

2 - 3 Days 

5

Device Onboarding

Standard

<all>

Configuration change to support monitoring of the device type

3 - 5  Days per system based on devices

6

Dashboard or Reporting

Standard

<all>

Discovery of reporting requirements and delivery of a report to stakeholders. 

3 - 5  Days per report

Assumes: existing data integration

    • Related Articles

    • After Hours Support Contact Details

      If the issue occurs outside of normal business hours, please raise the ticket as normal, then contact DeployPartners Support on +61 2 99667859, you will be connected to a DP support messaging service. Or contact +61 2 8076 9444 you will be connected ...
    • Priority Description

      DeployPartners Technical Support Service Level Agreement is applicable to both the on-line ticketing and calls to the applicable telephone numbers. Critical - P1 Priority   If you encounter an incident where the system is severely degraded in terms ...