IFSworld.

com

1
IFS Presentation July 19, 2020

IFS FSMTM BASIC

CONFIGURATION &
MOBILE OVERVIEW
IFS ESSENTIALS COURSE – IFS FSM 6

DHANUSHKI PAHATHKUMBURE
SENIOR BUSINESS SYSTEMS ANALYST
IFS ACADEMY

2
IFS Presentation July 19, 2020

01 02

AGENDA INTRODUCTION APPLICATION

SETUP

03 04
APPLICATION WRAP UP
INSTALL

11:30 – 12:00
3

3
IFS Presentation July 19, 2020

OUR TRAINING APPROACH

HOW WE LIKE TO DELIVER TRAINING

Learning Activities

Facilitator-led instruction
System Demos
Take home Exercises
Knowledge Tests

LEARNING ACTIVITIES
Facilitator-led Instruction
We try not to do too much of this, but it’s inevitable that some of that we do during the course will involve me taking you through some slides
and providing some information about how the system is structured, is designed to work and to show you how to configure the solution.
System Demos
Then, of course, we’ll show you what this looks like in the system so that you can fully appreciate what we’ve been talking about
Hands-On
The most important part of what you’ll do while you’re here is get the opportunity to do some hands-on work in the training environment. This
will always be a bit artificial compared to what you’ll do back in the real world, but it’s really important to have a go
Activities
These will be designed to give you a break from the screen and add a bit of fun!
Review sessions
This is where we’ll aim to consolidate the learning that we’ve covered and make sure everyone has the basis they need to move on to the next
steps
Knowledge Tests
Nothing heavy, just a little self-assessment so that you can check your learning progress and understand where your knowledge gaps are
LEARNING APPROACHES
Outcomes-based
For each lesson we’ll set out, at the beginning, what we anticipate you’ll be able to do by the end of the course – this means we’re focused on
what you’ll be able to do with the training, not just on the training itself
Field service context-based
Field service is quite a distinctive business area and if you understand a bit about that context, it will really help you to appreciate what IFS
customers are looking for when they implement this solution
Practically, functionally-based
We want to teach you things that are useful; whilst the code behind the scenes might be interesting to some, this course is about a practical,
functional knowledge base that will allow you to implement the solution
Peer learning
There are people here from different backgrounds, with different experiences; if you get the opportunity to hear and share some of that, you’ll
find it makes the course more useful and more interesting

4
IFS Presentation July 19, 2020

INTRODUCTION TO FSM MOBILE

5
IFS Presentation July 19, 2020

MOBILE
LEARNING OUTCOMES
By the end of this lesson, you will:
▪ Understand the features of the FSM Mobile Client
▪ Created a person (user) record and authorized it for mobile use
▪ Understood significant fields and functions of the Person
Mobile record
▪ Appreciate the basic requirements for set up of the Mobile Client
▪ Downloaded and installed the mobile client

6
IFS Presentation July 19, 2020

MOBILE
HARDWARE PLATFORMS

Scanner Phone Tablet Notebook

Ruggedized
Devices

The FSM Mobile offerings can be run on scanners, phones, tablets and notebooks. The FSM Mobile can run on
Android, iOS or Windows devices. FSM Mobile can stand alone or be integrated. Mobile can have online/off-line
Connectivity via SQLITE Database

The Mobile offerings will be discussed in more detail in IFS FMS Mobile course.

7
IFS Presentation July 19, 2020

MOBILE
FEATURES – DEVICE

Wireless
Access to Travel,
Printing,
Tasks, Time,
Multi- Barcode
Assets, Expense
Language Scanning,
Maps and and
Supported Sketches
Driving Signature
and
Directions Capture
Attachments

Once the data is downloaded onto the device, the technician can see the jobs, find directions, add parts, labor
and expenses and even get the signature of the customer when the work in completed. One feature about Mobile
is the ease of configurations. The FSM Mobile Designer enables you to configure FSM Mobile applications to
match your organization’s brand identity, terminology, and business practices. You can configure screens, menus,
workflows, logos and icons. Designs and revisions are created on the client. A design is a collection of configured
options that constitutes the entire user experience. You can create multiple designs and use the FSM Designs
screen to assign designs to the appropriate users. If the user has the ability, via an application parameter, to
“Designer” on the device, he can make changes to the design.

8
MOBILE
OTHER FEATURES
Attachments

Tasks

Quoting

Shipping

Purchase Orders
9

As a field service technician, I want to be able to upload an attachment within a

shorter time as attachment uploading time can be very long due to the size of
pictures taken by cameras which results in a delay in the task completion. I want to
be able to have the system pre-define photo sizes for the mobile so that it can
leverage the photo quality and attachment submission time.
Therefore, define picture size limits in FSM smart client to shorten upload times. This
is configured by the parameter, camera_photo_size, where it identifies the largest
picture size that can be uploaded.

As a field service engineer, I want to be able to download attachments only if they are
relevant for my task so that it will help to reduce the sync time in the mobile and the
data expenditures.
Attachments can be marked as "On Demand" attachments. When a task is assigned
to a mobile user, "On Demand" attachments will not be automatically downloaded to
the mobile. Technicians can download these attachments only when they make a
request.

As a field service technician, I want to be able to re visit the customer and perform
necessary services to completely fix the current problem so that it would be much

9
convenient if I can create an additional task for the same service request and assign it
to myself. Therefore, schedule a follow-up task for a task the tech is completing. They
can access the follow-up task screen from the debrief context menu and create a new
task assigned under their name.
the tasks that are assigned to my team and a map showing the pooled task locations
so that I would be able to accept the task assigned to my team in order to serve my
customer in a timely manner by achieving SLAs. Field service technicians can easily
view tasks assigned to their team, and allow them to accept one of the tasks as
something they're working on, which will result in them being assigned that task.

As a service manager, I want to be able to have the task times to be updated

automatically when a technician selects a task status from their mobile in the field so
that it allows our organization to effectively manage resources and achieve service
excellence. Tracking and monitoring the
As a field service technician, I want to be able to see task times based on status
changes of the mobile technicians is done on the “STATUS BASED TIMES” business
rule where columns on the task table can be configured to update automatically
when a task status is selected.

As a Field Service Engineer, I want to be able to select service parts on my task so that
part needs for those parts are created automatically. As a Call Taker, I want to be able
to include all the serviceable part information when I’m creating a service request so
that my mobile team members would be able to see them on their tasks. I want to be
able to see all the part ids associated with the product on the request which are
marked ‘Serviceable’ so that I would be able to select a serviceable part for a part
need or a usage. The service BOM (Bill of Material) allows the mobile technician to
select and retrieve BOMs if there are service parts associated to the request unit.

As a Field Service Engineer, I want to be able to easily create a quote from my mobile
and let my customers know what it could cost to have other work done for them so
that at the end of the quoting process I should be able to present them with a price.
As a Customer, I want to be able to know from the field service personal working on
my site about the cost to perform a specific work or to create a contract at the
specified price so that this will assist me in deciding whether to accept this quotation
for my future work. Use workflows to create new quotes or converted from other
records.

As a field service technician, I want to be able to ship a de-installed part or to return

unused inventory back to a warehouse so that it will give me more flexibility to
manage my own stock by tracing the parts in the system. Technicians can ship items
to other places within the system from the Shipping screen on the Home page. Also
they can specify a shipment from the stock list screen.

9
As a field service technician, I want to be able to source part needs from the supplier
so that it will help me to control the cost of the request/task and also to ensure the
task completion on time. Technicians have the ability to create purchase orders and
receive them.

9
IFS Presentation July 19, 2020

MOBILE
FEATURES – MOBILE DASHBOARD

Mobile
Syncing

Unsynced
Devices by
Carrier

Mobile
Errors
10

A feature within the client to monitor mobile users and their devices is the Mobile Dashboard. It can also be used
for troubleshooting issues. Besides seeing what techs are logged in and when they last initialized, there is also a
map displaying the location of your technicians. You can initialize devices from the dashboard so you can take the
burden off your technicians from initializing when you have installed new software or changes.
The charts on the dashboard gives you a different representation of the data.
Mobile Syncing chart shows the number of devices synced and not synced.
Unsynced Devices by Carrier chart shows the number of devices not synced by carrier.
Mobile Errors chart shows the number of mobile errors in the specified time that occur as a result of transactions
submitted by a device.

▪ used to monitor the devices in the field.

▪ The analytic charts display the sync status of the devices and display the number of errors in the
Mobile Error Log.
▪ Each device in the device list can be selected and administrators can contact the technician via a
text messages (SMS) or an email.
▪ Administrators can also initialize a device remotely or view the Mobile Error Logs for the user. Each
device will appear on a map displaying its last known location.

10
MOBILE
FEATURES – MOBILE DASHBOARD
If you right-click on a device in the list, these options appear:

Initialize Device—reinitializes the tables on the device. This creates a new database at the server and then
streams the database to the device.

Refresh Table—executes a batch replication for a specific table on the device. A dialog appears with
checkboxes for each table you want to refresh on the device. Select the tables and then click Refresh
Selected Tables. 11

Do practical.

11
IFS Presentation July 19, 2020

APPLICATION SETUP

© 2015 IFS 12
PLATFORMS SUPPORTED
OPTION OF ANY Native
Performance
& Usability
Android Windows iOS
Supports: 4+ Supports: 10+ Supports: 7+
Platform: Java Platform: .NET (C#) Platform: Objective-C
UX: Configurable
UX: Configurable UX: Configurable
Database: SQLite
Database: SQLite Database: SQLite

Phone,
Store and Tablet
Forward and Laptop
13

13
IFS Presentation July 19, 2020

PERSON
OVERVIEW
• Who is logged in - Employee
Identity/License • Status of Person

• Name and Address

Personal Information • Telephone Numbers
• Language

• Mobile and Portal Access

Relationships • Work Calendars

• Roles
Security • Access Groups
• Approvals
14

The Person record can be broken into several areas.

Under the Identity/License category would be fields such as: FMS License Type,
Employee and Person Status. If an employee leaves your company, set Employee =
"N" and Person Status = "Inactive". The former employee can no longer log in but you
will still have visibility of any work that had been done. The only time you should
delete a person record is if you created it in error.
Under the Personal Information category would be fields such as: Name, Address,
Home/Mobile/Work Phone, Fax, Job Title, Email, Alt Email, Language, and
Currency. The value in the “Language” field determines the language displayed in
FSM when the user logs in. You could use Messsage Translations or import from a
translator to modify the language. If you use multi-currency, the “Currency” field
defaults your technician"s currency when he creates his usage records.
Under the Relationships category would be fields such as: Mobile User and Calendar.
The “Calendar” field is the work calendar for the person. Calendar exceptions are for
vacation, jury duty, and training courses. We will discuss calendar exceptions later in
this lesson.
Under the Security category would be fields such as Access Group and
Approver/Approval. Access groups determinates who can see or access certain records.
Approver/Approval fields define approval of monetary limits for a person.

14
IFS Presentation July 19, 2020

PERSON
SECURITY TAB

Password

Hierarchical Groups

Images

Single Sign On
15

Of all the tabs on the Person record, the Security tab carries the most weight. Here
are the password resides. If the user has failed to log in after a certain number
attempts, the Administrator can unlock the person record by the “Unlock” button on
the Person record.

The hierarchical groups, Physical Service Groups and Organizational Service Groups,
are used to group employees. For example, what is my geographic location (Physical
Service Group) in relationship to my organization, i.e., Northeast, Midwest, Asia-
Pacific and what is my organizational role (Organizational Service Groups) in
relationship to my organization, i.e., Service, Tech Support, Warehouse. Note, Physical
Service Groups are also used with Mobile.
Images can be taken from the Studio Image Library.

You can choose to enable single sign on using Windows authentication; once a person is authenticated that
person can log in to FSM with no additional authentication required. FSM supports LDAP and Active Directory
Windows authentication when using single sign on.

15
PERSON
SECURITY TAB (CONT…)

Field Name Description

Detail Tab – Mobile User Select to allow this user to activate a mobile device.

Security Tab – Phy Svc Grp A Set this the same as the places you want downloaded to the device. Each place record
also has a physical service group. The person and place physical service groups must
match for the baseline sync rule to populate the Customer List in mobile. This also
determines which products will be populated on the device. This is a way of regionalizing
the data to reduce the amount of data that must be replicated to the device.
Security Tab – Labor Rate Used on the Mobile’s Labor screen for Simple Pricing. When a labor record is created the
value in the Labor Rate Global Code is used to set the bill price on the non-part usage.
Simple pricing can be enabled/disabled using app parameters in.

16

16
IFS Presentation July 19, 2020

PERSON
OTHER PERSON TABS
Skills
Roles
Positions
Mobile
Social Media
Printers
Communication History 17

The person record has tabs that are specific to the person record and there are tabs
that are generic, such as Notes, Events and Attachments, and used across multiple
core entities. We will discuss those in later lessons.
Skills includes skills and certifications associated with the person. These skills are used during work
assignment to compare with the skills specified on the Product record and the Place record. For example, a
product might require a certain type of certifications where a place might require proficiency in a certain
language.
Roles includes roles assigned to a person, which determines access rights. Roles will be discusses in a later
lesson.
Positions corresponds to a person’s job for approvals and escalations. A person ID is specified for the position.
A position can have only one person, although a person can be assigned to multiple positions. The escalation
hierarchy determines which positions, and consequently persons, are notified that an approval is required.
This will be discussed further in a later lesson.
Mobile includes information about the device assigned this person using FSM mobile applications.
Social Media includes social media and other accounts for this person. Types include Twitter, Facebook,
Tumblr, and eBay.
Printers includes default printers associated with this person. These printers are used for specific reports such
as pick lists. There are application parameters that are significant for Printers on the Person record:
DEFAULT_PRINTER_FOR_PICKLIST, DEFAULT_PRINTER_FOR_RECEIVING_DOC,
DEFAULT_PRINTER_FOR_SHIPPING_DOC.
Communication History includes email communications by this person using the Outlook connector.
Attachments also appear.

© 2015 IFS 17
PERSON
ENABLING THE MOBILE CLIENT

Mobile User FSM License

(Details Tab) Type

Must be selected.
Identifies that a
STUDIO, NAMED,
person can be
or MOBILE
associated to a
mobile device.

18

To Do Design work, You should Have STUDIO license

A user can have multiple devices

Mobile User (Details Tab) – Must be selected. Identifies that a person can be
associated to a mobile device
FSM License Type – STUDIO, NAMED, or MOBILE

18
IFS Presentation July 19, 2020

PERSON MOBILE
OVERVIEW
• Device ID
Device • Brand
• Model

Carrier • Carrier Name

• Type
Operating System • Version

• Activation
Dates • Initialization
• Synchronization

19

Mobile TAB
The Person Mobile record can be broken into several areas.
Under the Device category would be fields such as: Device ID, Brand and Model. The
Device ID is assigned by the manufacturer, and isn’t guarenteed to be unique. The
Brand tells you the name of the Manufacturer (Apple, Samsung, etc.) while the Model
tells you the Manufacturer’s Model ID.
The Carrier tells you the name of the mobile carrier that the device is using for voice
and data.
Under the Operating Systems category would be fields such as: Type and Version.
Type tells you if the device is running Android, iOS, or Windows. Version tells you the
version number of the operating system currently installed on the device.
Under the Dates category would be fields such as Activation Date, Last Initialization
Date, and Last Synchronization Date. Activation Date shows you when the
application on this particular device was activated. Last initialization date shows you
the most recent time the user initialized the application. Last Synchronization Date
shows you when the device last synced, attempting to get or send transactions or

© 2015 IFS 19
reference data.

19
IFS Presentation July 19, 2020

PERSON
PLACE RELATIONSHIPS

Works Starts Place

from work for
place from stock

20

The Places tab defines how the person is related to the specified place.
Works from place Used to identify default places for a person. This is important in Repair Center for the
receiver and the shipper as well as the person who creates the RMA.
Starts work from Used to identify the place where the person begins work; used when calculating and
optimizing routes for scheduling.
Place for stock Used for the default location of stock for field service representatives or repair personnel. This
is also used with the Mobile user to determinutese where they get their stock from. Mobile must also indicate
the location.
Default place for portal access If a person accesses portals, used to define the place whose information the
person can access.
Place for portal access If a person accesses portals, used to define any other place whose information the
person can access.

© 2015 IFS 20
IFS Presentation July 19, 2020

PERSON
TEAM DEFINITION

Identify one or more people

comprised of a group

Person must belong to a team

before can work on a task

Team Team members can temporarily be

deactivated from a team without
being removed

Sub-teams can be created

21

Person records must exist before they can belong to a team. Team records are used to
identify one or more people who compose a group. Because tasks are assigned to
teams or team members, a person must be a member of a team before that person
can work on a task. The team leader must also be specified as a team member if the
team leader can also work on tasks.
Persons assigned to a team can have their team memberships temporarily inactivated
without removing them from the team.
For example, you might inactivate a person who is temporarily reassigned to another
job function. You can create sub‐teams that are subordinate to the specified team.
When you create sub‐teams, you can choose whether to use either the team or sub‐
team name when performinutesg work assignment or use the Schedule Board.
A team can have both members and sub‐teams.

© 2015 IFS 21
IFS Presentation July 19, 2020

PERSON
WORK CALENDAR

Assignment

Specify
Exceptions
hours

Work calendars are used to specify working hours and exceptions for persons or places. They are used on
Schedule Board to assign requests and tasks, in Repair Center to determinutese turn around times and in MWFM
to optimally assigning requests and task. You can create multiple calendars and then assign the appropriate
calendar to individual places or individual employees. Work calendars specify hours to accommodate part‐time
and split shifts as well as holidays. Work calendars are assigned to each Person record and used for scheduling on
the Schedule Board and Repair Board. We will discuss work calendars again when we talk about Places.
Exceptions include when the person is not available to work, such as vacations or training classes. It can
specify as working or non‐working and can appear on the Schedule Board in a unique color which must be set up
using Color Settings under the Adminutes menu. The "Non working" option determinuteses whether work
assignment can be performed in the exception period. When not selected, the exception appears on the Schedule
Board, but work can still be assigned. When selected, work cannot be assigned.
Work calendars consist of day codes and time blocks. Day codes are an FSM code table. Time blocks are defined
on the time_block code table. You can create any time blocks you need but when you specify time blocks on this
tab, they cannot overlap.

© 2015 IFS 22
IFS Presentation July 19, 2020

APPLICATION INSTALL

© 2015 IFS 23
INSTALL
STEPS

Download Install Activate

24

24
IFS Presentation July 19, 2020

INSTALL

Side Loading

• Downloading and installing an application without an

App Store
• Requires OS permission from the user

Mobile Service

• Contains hyperlinks to the application

25

Used for list with 2 items to explain in with sentences (long).

25
INSTALL
STEPS TO INSTALL

Open the default browser on the device

Navigate to the Mobile Service

Click on the appropriate link for the device

The application will download and install on the device.

Follow the instructions on the device to launch the installed app.
26

26
INSTALL
ACTIVATING Provide valid
credentials for a
Launch the mobile mobile user:
application.
• Person ID
• Password

Enter the URL of the

Hit activate.
Mobile Service.

The application will active and initialize itself.

This may take up to a minute. Once it’s completed, it
will take you to the home screen.
27

27
IFS Presentation July 19, 2020

INSTALL
DEVICES

Person Screen

• Shows all of the devices activated for a user.

• Includes: Carrier, Brand, Model, OS type and version, and key
dates.

Mobile Dashboard

• Shows all of the devices.

• Visualizes location, charts metrics, and allows for device
management.

28

Used for list with 2 items to explain in with sentences (long).

28
INSTALL
VIEWING DEVICES IN THE SMART CLIENT

Launch the smart client.

Navigate to the Admin\Person screen.

Select the Person you activated the device against.

Click on the Mobile tab.

Navigate to the Mobile\Mobile Dashboard screen.

29

29
WRAP-UP

30

30
IFS Presentation July 19, 2020

IFS FSMTM BASIC

CONFIGURATION &
MOBILE OVERVIEW
IFS ESSENTIALS COURSE – IFS FSM 6

DHANUSHKI PAHATHKUMBURE
SENIOR BUSINESS SYSTEMS ANALYST
IFS ACADEMY

31

31
IFS Presentation July 19, 2020

01 02

AGENDA FSM
INTRODUCTION
FSM CORE
FSM ESSENTIALS COURSE & SOLUTION
ENTITIES
OVERVIEW

03 04
FSM CORE BASIC
PROCESSES CONFIGURATION
AND MOBILE
OVERVIEW

32

This is the agenda for the week’s course.

This morning is highlighted in the green box

32
IFS Presentation July 19, 2020

01 02

AGENDA OVERVIEW TO
SYNC RULES
TYPES OF
SYNC RULES

03 04
KEY FIELDS DEMO

05
WRAP UP

11:30 – 12:00
33

33
IFS Presentation July 19, 2020

OVERVIEW TO SYNC RULES

© 2015 IFS 34
IFS Presentation July 19, 2020

SYNC RULES
LESSON OBJECTIVES
By the end of this lesson, students should have:
▪ Understood the purpose of Sync Rules and how they’re used to
implement FSM Mobile.
▪ Learn about the impact Sync Rules have on the mobile device’s
database schema.
▪ Understood best practices for building Sync Rules.

35

© 2015 IFS 35
 SYNC RULES

Metadata which define what tables and data should be on the

device and how that data is filtered and synced.

36
SYNC RULE
PERFORM THE FOLLOWING FUNCTIONS
▪ Identify which tables have their data synchronized to the device.

▪ Generates the database on the device (tables and indexes). A table is created for each sync rule
regardless of whether the sync rule is for a table or a view. Note that the table’s metadata is used to
create the key resolution triggers in the database.

▪ Determine how data is filtered before going to device.

▪ Set how often a table’s data is synchronized.

▪ Gather and send related data for a transaction being sent to a device.

▪ Identify Metrix Perform Messages (MPM) to be invoked when a table update is received from mobile.

37

Data sync according to this sync rules. It says that those are real time synching, what
to be sync, whom to be sync etc.

37
SYNC RULES
CONT…

▪ Each sync rule manages a single table or view

▪ can be configured to push updates to that table for the interval
▪ You can add, edit, or delete sync rules in your environment using the Smart Client

Changes made to sync rules are

immediately applied to the environment.

38

38
IFS Presentation July 19, 2020

TYPES OF SYNC RULES

© 2015 IFS 39
SYNC RULES
SYNCHRONIZATION TYPES

Real Time Batch

As transactions occur in Transactions are sent to
FSM, they sent to the the mobile device in
mobile device. batches based on a
defined frequency. Only
changed data is sent.

40

40
SYNC RULES
SYNCHRONIZATION TYPES

Real Time Batch-All Batch-Delta

when information is changed over a specific interval, the over a specific interval,
in the FSM database, it is entire table is sent to the changes to the table since the
immediately delivered to the device on a specified interval. last sync are sent to the
device This delivery method is rarely device. This delivery method
used. is used for information that
changes little such as places
or addresses.

41

41
SYNC RULES
REAL TIME
▪ Intended for time sensitive data (tasks, requests, notes, attachments).
▪ Processed on a transaction by transaction basis.
▪ Generally sent to a specific user who is assigned the data (e.g. the PERSON_ID on a TASK
record).

For data that is not changing often and whose

updates a
user in the field needs to be aware of quickly.

42

42
SYNC RULES
BATCH-ALL AND BATCH-DELTA
▪ Intended for large data sets of non-time critical data (places, products, models,
parts).
▪ Runs on a frequency (number of hours).
▪ Only sends down updated data.
▪ Generally sends data to many or all devices.
▪ Batch-Delta is advised to use than Batch all

For data in tables with a lot of records that need

to go to the device but do not need to be updated
immediately
43

43
IFS Presentation July 19, 2020

KEY FIELDS

© 2015 IFS 44
SYNC RULES
KEY FIELDS – HEADER FIELDS
Field Description
Table Name The table this rule manages. Each table can have at most one
Rule.
Delivery Method Determines how messages are sent.
Frequency Determines how often messages are sent. Only for Batch.
Active If not selected, this rule will not be used.
Owner If selected, a field on this table identifies the person who should
receive an updated transaction.
Broadcast If selected, all devices will receive updates to this table.
Last Run Displays when this table was last synced. Only for Batch. 45

45
SYNC RULES
TYPES OF SYNC RULE QUERIES
▪ Ownership Query—If a table is not an Owner, for example there is no field on
the table that tells us who to send the update to, this query is issued to
determine who gets the update. Only for real-time sync.

▪ Initial Query—This query is used when initializing a device. It is used in the

population of the data after the database is created at the server.

▪ Related Query—This query is used to gather information related to a

transaction to send with the transaction. For example, when a task is assigned
to a user, we also want to get it attachments, notes etc.

46

46
DEMO

47

47
WRAP-UP

48

48
IFS Presentation July 19, 2020

IFS FSMTM BASIC

CONFIGURATION &
MOBILE OVERVIEW
IFS ESSENTIALS COURSE – IFS FSM 6

DHANUSHKI PAHATHKUMBURE
SENIOR BUSINESS SYSTEMS ANALYST
IFS ACADEMY

49

49
IFS Presentation July 19, 2020

01 02

AGENDA FSM
INTRODUCTION
FSM CORE
FSM ESSENTIALS COURSE & SOLUTION
ENTITIES
OVERVIEW

03 04
FSM CORE BASIC
PROCESSES CONFIGURATION
AND MOBILE
OVERVIEW

50

This is the agenda for the week’s course.

This morning is highlighted in the green box

50
IFS Presentation July 19, 2020

01 02

AGENDA INTRODUCTION
TO UI DESIGN
CONFIGURATION
SCOPE

03 04
KEY CONCEPTS WRAP UP

11:30 – 12:00
51

51
IFS Presentation July 19, 2020

INTRODUCTION TO UI DESIGNER

© 2015 IFS 52
IFS Presentation July 19, 2020

UI DESIGNER
LESSON OBJECTIVES
By the end of this lesson, students should:
▪ Understand the purpose of the UI Designer.
▪ Know how to configure the user experience of the mobile
apps through the UI Designer.
▪ Understand that the UI Designer is a cross-platform
development tool.

53

© 2015 IFS 53
MOBILE OVERVIEW
NAVIGATION List Screens
Screens Standard Screens
Themes

Global Menus
Home Menus Menus
Can be Modified in UI Designer Quick Jump Menus

Debrief
Workflows Quote
Custom

54
 UI DESIGNER

Built into the mobile apps themselves, this is the tool to

configure the user experience of the mobile applications.

55
UI DESIGNER
DYNAMIC USER EXPERIENCE

Localize
Meta- Build
Data Add fields,
screen
Store menu,
images

56

56
MANAGING SCREEN DESIGNS
▪ FSM Mobile allows you to configure our mobile applications.
▪ Your design match your organization’s brand identity, terminology, and business processes. hyperlinks and
control their You can configure
▪ workflows
▪ screens
▪ menus
▪ colors
▪ logos
▪ buttons, and icons.

It is possible to assign
Design/Revision to
User/Team/Role

57

57
IFS Presentation July 19, 2020

CONFIGURATION SCOPE

© 2015 IFS 58
UI DESIGNER
WHAT CAN BE CONFIGURED?

Screens ▪ Branding Workflows

Title, help, ▪ Colors, logos, Screens, order,
events, labels, images, terms, conditions,
fields, etc. etc. input and output

Interactions Fields Menus

Validations, Binding, validation, Contents,
verifications, interaction, defaults, order,
flows, etc. events, state, etc. actions, etc.

59

59
UI DESIGNER
ACCESSING
Available on any of the FSM mobile apps
Only users with STUDIO licenses can access
Access granted through global menu
Option Description

Designer Will take you to the UI Designer’s home screen.

Designer – Screen Will take you to the metadata for the screen you’re currently on.

Designer – Fields Will take you to the metadata for the fields on the screen you’re currently on.

Designer – Field Order Will take you to the metadata for the field order on the screen you’re currently
on.

60

60
IFS Presentation July 19, 2020

KEY CONCEPTS

© 2015 IFS 61
UI DESIGNER
KEY CONCEPTS – DESIGNS, REVISIONS

Designs Revisions States

• A design is a collection • Versions of a design • States of a revision
of the entire user • Control when • PENDING –
experience values you changes are Changes are still
build or configure for introduced being made
your users • Show changes by • PUBLISHED – No
• Made up of 1 or version further changes are
more revisions allowed
• INACTIVE – No
longer being used

62

Design Have more revisions

Either PENDING or PUBLISHED revisions can be assigned to users in the field.
Revision states give you a control mechanism for how changes are introduced to your
field force.

62
UI DESIGNER
KEY CONCEPTS – LAYOUT ELEMENTS

Menus Screens Workflows Themes

• Can add new, re-order • Screens within the • Can add new, re-order • Define the look of the
or remove options. apps. or remove screens app.
• Global Menu • Add, remove, position from workflows. • Colors
• Context Menu controls and labels. • Debrief Workflow. • Logos
• Home Screen • Define events. • Schedule Workflow. • Icons
• Bind data.

63

63
UI DESIGNER
EXPORT AND IMPORT DESIGN
▪ Open the Smart Client.
▪ Navigate to the Designs screen by selecting Designs on the Mobile menu.
▪ Click Import/Export.

The screen design export does not

export the sync rules. Those must be
exported separately.

64

64
WRAP-UP
65
IFS Presentation July 19, 2020

IFS FSMTM BASIC

CONFIGURATION &
MOBILE OVERVIEW
IFS ESSENTIALS COURSE – IFS FSM 6

DHANUSHKI PAHATHKUMBURE
SENIOR BUSINESS SYSTEMS ANALYST
IFS ACADEMY

66

66
IFS Presentation July 19, 2020

01 02

AGENDA FSM
INTRODUCTION
FSM CORE
FSM ESSENTIALS COURSE & SOLUTION
ENTITIES
OVERVIEW

03 04
FSM CORE BASIC
PROCESSES CONFIGURATION
AND MOBILE
OVERVIEW

67

This is the agenda for the week’s course.

This morning is highlighted in the green box

67
IFS Presentation July 19, 2020

01 02

AGENDA APPLICATION
NAVIGATION
FUNCTIONAL
WALKTHROUGH

03 04
DEBRIEF APPLICATION
WORKFLOW PARAMETERS

05
WRAP UP

11:30 – 12:00
68

68
IFS Presentation July 19, 2020

APPLICATION PARAMETERS
LESSON OBJECTIVES

By the end of this lesson, students should:

▪ Understand the basic functional flows of the application
▪ Understand the debrief workflow
▪ Understand the purpose, behaviour and impact of Application Parameters.
▪ Know the Application Parameters available to configure the behavior
of the mobile applications.

69

© 2015 IFS 69
IFS Presentation July 19, 2020

APPLICATION NAVIGATION

© 2015 IFS 70
 MOBILE OVERVIEW
FEATURE SET
hoose your colour

Job Creation Job Debrief Sales in Service

Scheduling and dispatch, Job completion, signatures, Opportunities,
parts ordering, surveys, notes, parts, replace and renewals,
file attachments, labor, expenses, service contracts,
notes, etc. PCR codes, etc. etc.

Inventory Customer Relations Miscellaneous

Parts ordering, searching, Accounts, installed products, Time & Attendance,
adjustments, contracts, warranties, LBS and ETA,
receiving, swapping, service history, actions,
etc. location, etc. collaboration, etc.

71

71
MOBILE OVERVIEW
REQUEST AND TASK CREATION
▪ Request

▪ Contact

▪ Product

▪ Part Needs

▪ Notes

▪ Task

72

72
IFS Presentation July 19, 2020

FUNCTIONAL WALKTHROUGH

73

73
MOBILE INTERFACE
HOME SCREEN

▪ Home screen contains 8 tiles

▪ The maximum number of tiles is 8
▪ Although different tiles can be configured
▪ The bottom of each tile shows the item count
▪ Alerts are shown at the bottom of the home
screen

74
MOBILE INTERFACE
CUSTOMERS
▪ Customers Screen shows all the
customers this Technician
(Person) is assigned to

▪ Clicking on a customer from the

list shows the customer details
Including:
▪ Products
▪ Contacts
▪ History
▪ Attributes

75
MOBILE INTERFACE
STOCK

▪ Stock displays a list of the current

Van Stock of the technician

▪ By selecting a part from the list the

details are displayed

▪ Including serial numbers and Lots if

relevant

76
MOBILE INTERFACE
TEAM

▪ Team displays other team members

▪ Clicking on a team member entry

displays their contact details

77
MOBILE INTERFACE
RECEIVING
▪ Receiving is where the technician would record
van stock replenishments

78
MOBILE INTERFACE
JOBS/TASKS
▪ Tasks assigned to a field resource
or technician appear in the Jobs
section

79
MOBILE INTERFACE
JOBS/TASKS
▪ Once a job is selected the details
are displayed

▪ From here the task can be started

80
IFS Presentation July 19, 2020

DEBRIEF WORKFLOW

81

81
MOBILE INTERFACE
JOBS/TASKS
▪ In the top right are notification icons

▪ Attachments
Documents
Images
Videos

▪ Notes

▪ Job/Task Status

82
MOBILE INTERFACE
JOBS/TASKS

▪ The hand Wrench icon allows

control of Job status

83
MOBILE INTERFACE
JOBS/TASKS
▪ Jump to Icon presents a Menu of
links to different tables/areas in the
request

▪ The More Icon drives the navigation

forward through the Job/Task

84
MOBILE INTERFACE
JOBS/TASKS COMPLETION
▪ Parts

85
MOBILE INTERFACE
JOBS/TASKS COMPLETION
▪ Labour and expenses

86
MOBILE INTERFACE
JOBS/TASKS COMPLETION
▪ Attachments
▪ Photos
▪ Videos
▪ Documents
▪ Files

87
MOBILE INTERFACE
JOBS/TASKS COMPLETION

▪ Completion Questionnaire

88
MOBILE INTERFACE
JOBS/TASKS COMPLETION
▪ Customer Review

▪ Summary

89
IFS Presentation July 19, 2020

APPLICATION PARAMETERS

© 2015 IFS 90
APPLICATION PARAMETERS
ACCESS

▪ App Params are accessible in the

Smart Client
▪ Admin\System\App Params
▪ To see App Params for Mobile, apply
Param Category = MOBILE filter
▪ Each param has a Description which
identifies it’s purpose
▪ Changes to App Params are broadcast
to devices (see METRIX_APP_PARAMS
Sync Rule).

91

We will see what are the Sync Rule Next

91
MOBILE APP PARAMETERS

ACCEPTING OR REJECTING TASKS

Allows you to specify whether technicians have the option to accept or reject
an assigned task.
ALLOW_ACCEPT_OR_REJECT_TASKS
If you want to enable the accepting or rejecting of
tasks using notifications or the Work List screen,
set this value to Y (yes).
ACCEPTED_TASK_STATUS
The status the task is assigned if the user
accepts it.
REJECTED_TASK_STATUS
The status the task is assigned if the user rejects
it.
92

Show by enabling and disabling

92
SIMPLE PRICING
Allows you to specify whether you want to use simple pricing for part usage and non-part usage records.
Taxation and adjustments are not applied.
ENABLE_MOBILE_SIMPLE_EXPENSE_PRICING
Sets the expense price to the amount entered by the user.
ENABLE_MOBILE_SIMPLE_LABOR_PRICING
If enabled (Y) the bill price and unadjusted list price will be set to the person’s
labor rate (person.labor_rate_code) which will be a dollar value (per hour).
The labor rate codes are set up in Global Codes
ENABLE_MOBILE_SIMPLE_MILEAGE_PRICING
Sets the mileage price to the amount entered by the user multiplied by the
value of the SIMPLE_MILEAGE_PRICING_RATE app param.

ENABLE_MOBILE_SIMPLE_PART_PRICING
Sets the part price to the most recent active list price for the part.
SIMPLE_MILEAGE_PRICING_RATE
The rate at which mileage is reimbursed.

93

93
LOCATION
GPS_LOCATION_COMPARISON_TOLERANCE
Identifies the tolerance to use when determining whether two GPS reads are the same.

GPS_LOCATION_COMPARISON_TOLERANCE_UOM
Identifies the unit of measure to use in the tolerance check.
GPS_LOCATION_INTERVAL_MIN
Identifies the frequency of GPS reads in minutes. When zero, no GPS reads will be
taken.
GPS_LOCATION_INTERVAL_WORK_STATUS
Allows you to specify the work status of the user for capturing GPS reads. For example,
only capture the user’s position when on shift. When off shift, do not capture the position.

GPS_LOCATION_PERSON_STATUS_UPDATE
Whether to capture the user’s GPS position when they update their work status.

GPS_LOCATION_TASK_STATUS_UPDATE
Whether to capture the user’s GPS position when they update a task status.

94

94
IMPORTANT INFORMATION—OVERVIEW
These parameters control the conditions in which the important information is displayed to the user based on
the work assigned to them. These are displayed on the Overview screen in the Debrief Workflow. This feature
is only available for Android.

NOTIFY_DAYS_IF_CONTRACT_EXPIRES
Displays a message when the service contract covering this task is due to expire in less days than this
value.
NOTIFY_DAYS_IF_ECOS_EXIST
Displays a message when there are ECO’s scheduled within this window of time.
NOTIFY_DAYS_IF_OTHER_TASKS_EXIST
Displays a message when other tasks are scheduled within this window of time.

NOTIFY_DAYS_IF_PMS_EXIST
Displays a message when there are PMs scheduled within this window of time.

NOTIFY_DAYS_IF_WARRANTY_EXPIRES
Displays a message when the warranty covering this task is due to expire in less days than this value.

95

95
WORK LIST

ADDITIONAL_JOB_LIST_CONSTRAINTS
Allows you to further constrain which tasks are displayed.

96

96
 ADMIN

ALLOW_ADMIN_EDITS_IN_MOBILE
If this value is set to Y (yes), the user can modify values on the Admin
screen.

97

Show by enabling and disabling

97
 RECEIVING

AUTO_INITIALIZE_MOBILE_RECEIPTS
Determines whether a receiving record is initialized automatically when an in-transit shipment is posted to
a technician’s service vehicle.

SUMMARY

CONFIRM_TASK_COMPLETION_IN_MOBILE
Determines whether the user must confirm that they want to complete a task in mobile.

ENABLE_TECHNICIAN_SIGNATURE
Asks the user to sign when completing a task.

ENABLE_MOBILE_PLAY_SOUND
Makes the mobile device play a sound when the task is completed.

98

ENABLE_TECHNICIAN_SIGNATURE
Show by enabling and disabling

98
PRODUCT REMOVAL

DEFAULT_DISP_CODE_PRODUCT_REMOVAL
Identifies the disposition code used by default when a disposition is
created to remove a product from a customer site.

JOB SCHEDULING
SCHEDULE_JOB_TASK_STATUS
Identifies the default task status for tasks created on the mobile device.

99

99
ATTACHMENTS

CAMERA_PHOTO
Defines photo size for pictures submitted by a mobile client. (Extra
Large – default picture size from camera; Large – 1024X768; Medium –
640X480; Small – 320x240) Default is Extra Large.

Attachments are also available for immediate download on the Task or

Request screens. A placeholder is placed in the image carousel of
Attachments screen of the mobile client.

Some attachments can also be used to configure the login screen

background using the Smart Client.

100

100
SYSTEM SETTINGS

DEBRIEF_ALLOWED_STATUSES
Identifies task statuses that a task must have before a technician can debrief that task.

ENABLE_BARCODE_SCANNING
Identifies whether the user can scan barcodes on the device.
ENCRYPT_MOBILE_DATABASE
DO NOT CHANGE, THIS MUST ALWAYS BE N
MAX_ROWS
Identifies the maximum number of rows of data to be displayed on any mobile screen. This protects the
user experience and ensures good performance.
MOBILE_DATABASE_DIRECTORY
DO NOT CHANGE, THIS IS SET DURING THE INSTALLATION
MOBILE_ENABLE_TIME_ZONE
DO NOT CHANGE, THIS MUST ALWAYS BE Y

101

101
MOBILE_ENCODE_URL_PARAM
DO NOT CHANGE, THIS MUST ALWAYS BE N
MOBILE_SYNC_BATCH_SIZE
Identifies the maximum number of rows to include in each message sent to FSM Mobile for batch
synchronization rules. Value is any positive integer.
MOBILE_SYNC_BYTE_LIMIT
Indicates the byte size limit of read messages from MM_MESSAGE_OUT. Once the total size limit
= > app param value, send to device. 1 mb = 1048576 bytes.
DEVICE_LAST_SYNC_LIMIT
Determines whether the person_mobile.last_sync_dttm is less than the current date minus the
value of the
DEVICE_LAST_SYNC_LIMIT param. If it is, mm_message_out records are deleted and a new
init_request is sent. When this value changes, the init_request allows initialization to begin again.

TRANSLATE_DESCRIPTIONS
Determines whether translated description values are sent to mobile devices. For tables with
description and desc_message_id columns, if desc_message_id is specified and a message
translation exists for the user's language, then the translated description value is sent to the user's
mobile device in place of the default description value.

102

102
WRAP-UP
103
 IFSworld.com
© COPYRIGHT© 2020 BY INDUSTRIAL AND FINANCIAL SYSTEMS, IFS AB (PUBL). ALL RIGHTS RESERVED. THIS MATERIAL AND ITS CONTENT IS
PRODUCED BY THE IFS ACADEMY FOR AUTHORIZED TRAINING PURPOSES ONLY AND REMAINS THE INTELLECTUAL PROPERTY OF IFS.
NEITHER THE MATERIAL OR ITS CONTENT MAY BE COPIED, REPRODUCED, OR DISTRIBUTED WITHOUT IFS’ EXPRESS WRITTEN PERMISSION.

IFS DOES NOT WARRANT, EITHER EXPRESSLY OR IMPLIED, THE ACCURACY, TIMELINESS, OR APPROPRIATENESS OF THE INFORMATION
CONTAINED IN THIS TRAINING MATERIAL AND DISCLAIMS ANY RESPONSIBILITY FOR CONTENT ERRORS, OMISSIONS, OR INFRINGING
MATERIAL. IFS ALSO DISCLAIMS ANY RESPONSIBILITY ASSOCIATED WITH RELYING ON THE INFORMATION PROVIDED IN THIS DOCUMENT
AND ANY AND ALL LIABILITY FOR ANY MATERIAL CONTAINED ON OTHER CHANNELS THAT MAY BE LINKED TO THE IFS TRAINING MATERIAL.

104
#forthechallengers

105