Returns, Repair and Depot
RMA Creation and Return Authorisation
Authorising a customer to send something back. In FSM 6 an RMA is a request with request units, and the RMA line is a request line, so return authorisation reuses the whole request machinery rather than having a separate document.
Repair Centre Determination and Routing
Deciding where a returned item should go and how long it should take. FSM 6 delivers a family of repair centre rules that select the place, the shipping route, the turnaround time and the eligible repair locations for each unit.
Return Receipt, Inspection and Disposition
Receiving the item, working out what state it is in, and deciding what happens to it. Receipt establishes condition, which in FSM 6 is a code that governs whether the item can satisfy demand and how it is valued.
Repair Task Creation and Assignment
Creating the shop work for a returned unit and giving it to a technician. FSM 6 uses a dedicated Request Unit Task Creation rule so that depot work is generated per unit rather than per request.
Repair Scheduling and Shop Capacity
Sequencing depot work against bench capacity and turnaround commitments. FSM 6 handles this on the repair board, which is the depot equivalent of the schedule board.
Repair Debrief, Completion and Return to Customer
Recording what the repair consumed, valuing it, and sending the unit back. Repair debrief runs through the same repricing rules as field debrief, then the unit ships and the customer is billed or credited.
Component Repair and Exchange
Repairing a serialised part that came out of a bigger machine, and managing the exchange pool that keeps the machine working while its component is away. This is where installed base, stock and repair meet.
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