IFS FSM 6 (Field Service Management) · FSM11

Security, Administration and Background Processing

5
Processes
166
Details worked out
35
Execution steps
5
Diagrams
FSM11.01

Role and Access Restriction Design

Deciding who can do what. FSM 6 roles are restriction lists rather than grants: a role names what a person cannot use, or can use read only, and the role table and view maps are generated from those settings.

IFS FSM 6 Security
37 details
diagram
FSM11.02

Person, User and Access Group Administration

Managing who exists in the system and which records they can see. FSM 6 separates functional access, carried by roles, from record visibility, carried by access groups, and ships eighteen delivered rules that assign access groups automatically.

IFS FSM 6 Security
31 details
diagram
FSM11.03

Code Table and Application Parameter Governance

Maintaining the vocabulary and the switches. FSM 6 holds hundreds of code tables and nearly six hundred application parameters, and they carry a large part of the behaviour of the system.

IFS FSM 6 Core Concepts, Code Tables and Application Parameters
33 details
diagram
FSM11.04

Scheduled Process and Background Queue Administration

Running the work that nobody triggers. FSM 6 executes billing generation, preventive maintenance generation, rota transmission, escalation evaluation and much else as scheduled processes, monitored through the run log.

IFS FSM 6 Scheduled Processes and Background Processing
33 details
diagram
FSM11.05

Audit and Personal Data Protection

Recording who changed what, and honouring the rights people have over data held about them. FSM 6 ships column level audit and a personal data protection capability for erasure and export.

IFS FSM 6 Audit and Personal Data Protection
32 details
diagram
What a license opens

Everything you can see here is real and current, the names, the structure and the counts come straight out of the ModelIFS library and change as it grows. What sits behind the license is the worked-out content itself: the execution steps, the data each one needs, the configuration decisions, the KPIs, the integration points, the workshop questions and the diagrams. That is the part you would otherwise spend a program building from nothing.

Sign in to open it