Skip to content
snflows

Catalog

Every module, family, and term — searchable by name, acronym (ITSM, CMDB, SPM…), or the problem in your own words. Prefer pictures? Use the map.

Audit Management

Runs the internal audit function: planning what to audit based on risk, executing engagements with workpapers and evidence, recording findings, and tracking remediation to closure — replacing document-and-spreadsheet audits with a managed workflow that reuses existing risk and control data.

Business Continuity Management (BCM)

Preparing the business to keep running through disruptions: analyzing which processes are critical and how quickly they must recover (business impact analysis), building and maintaining continuity plans, and coordinating response when something actually happens.

Policy & Compliance Management

Managing the organization's policies and the controls that enforce compliance with regulations and frameworks (ISO 27001, SOC 2, NIST, etc.). It maps requirements to controls, tests whether controls are working, and tracks remediation — so compliance is continuous rather than a scramble before each audit.

Risk Management

A live system for identifying, assessing, and monitoring the risks a business faces — operational, technology, financial — replacing periodic spreadsheet exercises with a continuously updated risk register that can pull real signals from across the platform.

Third-Party Risk Management (TPRM)

Assessing and monitoring the risk your vendors and partners introduce: sending due-diligence questionnaires, scoring responses, tracking issues to remediation, and re-assessing periodically — so third-party risk is managed continuously rather than at onboarding only.

Government1 module

Change Management

A controlled way to modify anything that could impact an IT service — updating a server, deploying an application, swapping network gear. Each change gets assessed for risk, approved by the right people, scheduled to avoid collisions, and reviewed afterward. The goal isn't bureaucracy; it's making beneficial changes with minimum disruption.

Incident Management

The system your IT team uses when something breaks: a user reports it (or a monitoring tool detects it), the right team gets it, works it, and restores service as fast as possible. An "incident" is simply an unplanned interruption or degradation of a service — from "my laptop won't start" to "email is down for everyone."

Major Incident Management

A dedicated response process for the incidents that hurt: highest impact, many users, crucial services down. It adds what a regular ticket can't — a coordinated response team, structured stakeholder communications ("here's what we know, next update at 3pm"), and a post-incident review so the organization actually learns from the event.

On-Call Scheduling

Schedules, rotations, and escalation rules that answer one question reliably: *who gets contacted right now when a critical system breaks?* When an incident lands, ServiceNow works out who is on shift, notifies them, and automatically escalates to the next person if nobody acknowledges.

Problem Management

Where Incident Management fixes the symptom, Problem Management finds and eliminates the cause. When the same thing keeps breaking, a "problem" record tracks the investigation into why, documents the temporary workaround so every technician knows it, and drives a permanent fix.

Mobile1 module
Now Platform4 modules
Retail1 module