How to Configure Service Manager Plus for Your OrganizationImplementing Service Manager Plus effectively requires planning, understanding your organization’s processes, and careful configuration. This guide walks you through preparing, installing, configuring, and optimizing Service Manager Plus so it fits your business needs and scales as you grow.
1. Plan before you configure
Before touching the product, map out the services, teams, and processes you want to support.
- Identify stakeholders: IT operations, service desk agents, change managers, security, HR, and business-unit owners.
- Define scope: Support services (hardware, software, network), locations, and which departments will use the system initially (pilot vs full rollout).
- Document processes: Incident, problem, change, request fulfillment, asset lifecycle, and SLAs. Use RACI to define roles and responsibilities.
- Define KPIs: Mean time to resolution (MTTR), SLA compliance, ticket backlog, first-contact resolution, change success rate, asset utilization.
- Data and integrations: Inventory existing CMDB data sources, Active Directory, monitoring tools, email system, single sign-on (SSO), and backup procedures.
- Security and compliance: Access controls, data retention, audit logging, and any regulatory requirements (GDPR, HIPAA, etc.).
2. Installation and initial setup
Choose hosting: on-premises or cloud. Each has trade-offs in maintenance, control, and scalability.
- System requirements: Verify OS, database, CPU, memory, and storage needs per vendor recommendations.
- Install Service Manager Plus: Follow vendor installer for your platform. For on-premises, install database (if required) and application server. For cloud, provision the service and tenant.
- Create admin account and secure it: Use a strong password and, if available, enable two-factor authentication.
- Set up email server: Configure SMTP for outgoing notifications and POP/IMAP (or API) for incoming emails to create tickets from mail.
3. Configure users, roles, and access controls
Proper access controls reduce risk and ensure users see only relevant information.
- Integrate with Active Directory/LDAP/SSO: Synchronize users and groups to avoid manual account creation.
- Define roles: Service Desk Agent, Technician, Change Manager, Asset Manager, Site Admin, and End User. Keep permission sets aligned with job functions.
- Role-based access control (RBAC): Limit access to modules and actions. For example, only Change Managers can approve changes; technicians can update tickets for their assigned groups.
- Multi-tenancy (if applicable): Partition data and access by department or business unit.
4. Configure core modules
Tailor each module to match your documented processes.
Incidents and Service Requests
- Create request templates and categorization: Service category → Subcategory → Item.
- SLAs: Define priorities, SLA targets, escalation paths, and notifications.
- Assignment rules: Automate assignment based on category, site, or availability.
- Templates and canned responses: Save time with prebuilt resolution notes and responses.
Problem Management
- Link problems to incidents: Configure workflows to escalate recurring incidents to problem cases.
- Root-cause fields: Capture RCA analysis, workarounds, and permanent fixes.
Change Management
- Change types: Standard, Emergency, Normal.
- Approval processes: Single- or multi-level approvals; define approval policies based on change risk and impact.
- Change calendar and blackout windows: Integrate with CMDB and asset calendar to avoid conflicts.
Asset & CMDB
- Import assets: Bulk import from spreadsheets, discovery tools, or integration with procurement.
- CI relationships: Map dependencies between hardware, software, and services.
- Asset lifecycle states: Ordered → Received → Deployed → Retired.
- Warranty and contract fields: Track vendor support and renewal dates.
Knowledge Base
- Structure articles by service and process.
- Approval and review workflows: Ensure content accuracy with periodic reviews.
- Link KB articles to incidents and requests for self-service resolution.
Service Catalog & Self-Service Portal
- Design the portal for non-technical users: Simple wording, clear categories, and approval steps.
- Request fulfillment workflows: Automate approvals, fulfillment tasks, and notifications.
- Mobile access: Ensure forms and workflows work on mobile devices.
5. Automations and workflows
Automation reduces manual work and speeds resolution.
- Workflow builder: Model approvals, validations, escalations, and post-resolution actions.
- Business rules: Auto-assign, auto-close resolved tickets after validation, trigger surveys after closure.
- Scripts and webhooks: Integrate with monitoring tools or external systems for event-based ticket creation.
- Scheduled tasks: Regular health checks, cleanup of stale records, and reporting jobs.
6. Integrations
Connect Service Manager Plus to other systems to improve data accuracy and reduce duplicate entry.
- Active Directory / SSO: Streamlines login and user provisioning.
- Monitoring tools (Nagios, Zabbix, SolarWinds): Auto-create incidents on alerts.
- CMDB/discovery tools: Import discovered CIs to keep your inventory current.
- IT automation/orchestration (Ansible, PowerShell scripts): Execute remediation steps from tickets.
- Financial/procurement systems: Sync purchase orders and costs for assets.
- ChatOps/Slack/Microsoft Teams: Allow agents and users to create and update tickets from chat.
7. Notifications and SLA management
Well-configured notifications keep stakeholders informed.
- Notification templates: Use clear, concise messaging with context and links to tickets.
- Escalation policies: Notify team leads when SLAs are breached or tickets age beyond thresholds.
- SLA reporting: Build dashboards showing compliance trends and breach reasons.
8. Reporting and dashboards
Measure adoption and performance with relevant reports.
- Out-of-the-box reports: Incident trends, SLA compliance, agent performance, change success rates.
- Custom reports: Combine datasets (assets vs incidents, cost per ticket, MTTR by service).
- Dashboards: Executive summary, service desk operational, change calendar, asset health.
- Scheduled distribution: Email weekly/monthly performance reports to stakeholders.
9. Testing and pilot rollout
Validate configurations before full production use.
- Sandbox environment: Test workflows, automations, and integrations safely.
- Pilot group: Start with a single team or location to gather feedback and refine processes.
- UAT checklist: Forms, approvals, notifications, mobile access, SLA behavior, integrations.
10. Training and documentation
Adoption depends on people, not just tools.
- Role-based training: Agents, approvers, asset managers, and end users.
- Quick reference guides: Common tasks, ticket lifecycle, how to request services.
- Train-the-trainer: Create internal champions who can onboard new users.
- Knowledge base articles: How-tos for both agents and end users.
11. Go-live and post-live support
A structured go-live minimizes disruption.
- Go-live checklist: Backups, rollback plan, communication plan, support rota.
- Hypercare period: Provide extra support for the first 2–4 weeks to handle issues quickly.
- Feedback loop: Collect user feedback and iterate on workflows and UI.
12. Continuous improvement
ITSM is iterative; keep optimizing.
- Regular reviews: Monthly SLA review, quarterly process audits, and annual platform assessments.
- Adopt metrics-driven changes: Use KPIs to prioritize improvements.
- Keep integrations and plugins up to date: Reduce security risks and leverage new features.
Example configuration checklist (concise)
- Stakeholders identified and processes mapped
- Hosting chosen and system installed
- AD/SSO integrated and roles defined
- Request catalog and templates created
- SLA and escalation rules configured
- CMDB populated and CI relationships mapped
- Workflows, automations, and integrations tested
- Pilot completed and end-user training delivered
- Dashboards and reports scheduled
- Go-live with hypercare and continuous improvement plan
This configuration approach balances technical setup with process alignment and user adoption to ensure Service Manager Plus delivers measurable value to your organization.
Leave a Reply