Customer, Place and Installed Base
Place and Customer Master Maintenance
Maintaining the place record, which in FSM 6 is simultaneously the customer, the site and the billing party. Almost every other record resolves back to a place, so place structure decides what can be reported, priced and scheduled.
Contact and Role Management
Maintaining the people at a place and what each is for. Contact records carry roles, skills and social details, and contact quality decides whether notification and appointment confirmation reach anyone.
Product Registration and Installed Base Tracking
Registering the serialised equipment that is serviced and keeping track of where it is. In FSM 6 the product is the installed base record: it carries location, warranty, contract coverage and meter history.
Product Structure and Configuration Management
Holding the parent and child relationships between serialised items so that a machine, its assemblies and its components are serviced as one thing. Product structure drives component exchange, warranty inheritance and where used analysis.
Meter Definition and Reading Capture
Measuring how much a product has been used, and acting on it. Meters drive usage based preventive maintenance and usage based billing, and readings arrive from technicians, customers or devices.
Engineering Change Order Execution
Applying a modification, recall or upgrade across a population of installed products. FSM 6 uses an engineering change order with detail lines identifying affected products, and surfaces alerts and actions when one of those products appears on a request.
Place Merge and Master Data Quality
Finding and resolving duplicate places, and keeping the master data fit to schedule and bill against. FSM 6 ships a merge places function that consolidates a duplicate into a survivor together with its history.
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