Best Practices for Configuring SolarWinds FSM (formerly Athena FirePac)
1. Plan your deployment and topology
- Assess requirements: number of users, technicians, concurrent sessions, mobile usage, integration needs (ERP, PSA, maps).
- Scale appropriately: separate servers for application, database, and web services when load warrants it.
- Use high-availability options for critical installations (load balancers, redundant polling/web engines).
2. Secure the environment
- Use Windows Authentication or SAML for user access (avoid local accounts).
- Harden servers: latest OS patches, limit services/ports, restrict admin access.
- Network segmentation: place FSM servers on restricted VLANs and limit inbound access to only required IPs/ports.
- Rotate service and API credentials regularly and enforce least privilege.
3. Database configuration & maintenance
- Dedicated SQL instance for FSM database; keep database and app servers separate if possible.
- Set appropriate retention and pruning policies for historical/transactional data to control DB growth.
- Scheduled maintenance: regular backups, index maintenance, and integrity checks; avoid frequent auto-shrink.
- Monitor disk IO and queue length; ensure storage provides required IOPS.
4. Authentication, roles & permissions
- Define roles and least-privilege views for dispatchers, techs, managers, and admins.
- Use module-specific roles and restrict administrative privileges to few users.
- Audit and log configuration changes and user actions.
5. Mobile and offline usage
- Test mobile workflows (sync, offline mode, attachments) on representative devices and networks.
- Limit large attachments or use external storage integration to avoid performance issues.
- Optimize sync schedules and payload sizes to reduce bandwidth and latency.
6. Workflows, templates & data quality
- Standardize work order templates, forms, and checklists to ensure consistent field data.
- Use picklists and validation rules to reduce free-text errors.
- Import and clean master data (customers, sites, assets) before go-live.
7. Integrations & automation
- Plan integrations (ERP, inventory, billing, mapping/GIS) with clear data mappings and error handling.
- Use APIs and webhooks for real-time updates; queue/retry logic for transient failures.
- Automate routine tasks like assignment rules, SLA escalation, and notifications.
8. Alerts, notifications & SLAs
- Define priority-based SLAs and escalation paths.
- Restrict notifications to relevant recipients; use templated messages.
- Test alert routing and escalation end-to-end before production.
9. Monitoring, logging & capacity planning
- Monitor application health, API rates, sync performance, and DB metrics.
- Set thresholds and alerts for resource utilization and error spikes.
- Plan capacity reviews quarterly or when usage grows.
10. Testing, rollout & training
- Staged rollout: develop → test → pilot → production.
- Provide role-based training and quick reference guides for dispatchers and field techs.
- Run dry-runs for dispatch, mobile sync, and integrations before full cutover.
11. Backup, disaster recovery & upgrades
- Regular backups of database and configuration; test restores periodically.
- Document DR runbooks and RTO/RPO targets.
- Follow upgrade best practices: test upgrades in a sandbox, review release notes, and schedule maintenance windows.
12. Ongoing governance
- Establish ownership: designate FSM system administrators and stewards.
- Review configurations quarterly: roles, integrations, retention, templates, and SLAs.
- Collect feedback from field users and iterate on forms/workflows to improve adoption.
If you want, I can convert this into a checklist, a 30‑day rollout plan, or a configuration checklist tailored to small (≤50 users) or large (≥500 users) deployments.
Leave a Reply