Implementation Planning
About 5% of the CIS-FSM exam — see all 4 domains.
The smallest domain. It is about the discipline around an implementation rather than the product features:
- Understanding the Now Create methodology and standard implementation phases.
- Gathering requirements for work order types, state flows, skills, territories, and integrations before build.
- Planning data: stockrooms, assets/install base, skills-to-agent mapping, group structures.
- Sequencing plugin activation (base FSM first, then feature plugins) and managing dependencies.
- Planning the CSM integration, mobile rollout, and SLA definitions as part of scoping.
Watch item: official Now Create artifacts and the exact CIS-FSM implementation methodology content were not fully extractable from primary sources; treat methodology specifics as supplementary and confirm via Now Create.
Sample questions from this domain
Three of the 15 in this domain, with the reasoning. The full set is in the question bank.
During FSM implementation planning, why is it important to gather the customer's existing foundation data early?
- A. Foundation data is only needed for reporting
- B. Foundation data is optional and can be skipped
- C. Foundation data such as locations, accounts, contacts, and assets underpins qualification and scheduling and must be loaded before processes can work ✓
- D. Foundation data prevents the platform from upgrading
Why: Foundation data is the basis for qualification and scheduling, so it must be planned and loaded early. It is not optional (B), not only for reporting (C), and does not block upgrades (D).
An implementer is scoping an FSM project. Which activity belongs to the requirements-gathering phase rather than build?
- A. Configuring auto-routing rules
- B. Loading production data
- C. Building work order templates
- D. Documenting the customer's field service processes and personas ✓
Why: Documenting processes and personas is requirements gathering. Configuring auto-routing (B), building templates (C), and loading data (D) are build/deployment activities.
Which two considerations are most important when planning an FSM scheduling approach? (Choose two)
- A. The number of knowledge categories
- B. The geographic distribution and territories of agents ✓
- C. Whether the customer needs manual dispatch, auto-routing, or optimization ✓
- D. The color theme of the Service Portal
- E. The instance hostname
Why: Scheduling planning hinges on the chosen dispatch model and on territory/geographic distribution. Portal theme (C), knowledge categories (D), and hostname (E) do not drive the scheduling approach.