15 Operations ring
← Technical Guide

Chapter 15

Operations ring

The purchasing, logistics, installed base, problem record, spare parts and service modules, and the ring screen that connects them: what each screen shows, how the links are counted and who sees it.

Overview

The Operations ring brings together the operations after the sale in six modules: Purchasing, Logistics, Installed Base, Problem & Solution, Spare Parts, and Service and Field. Each module has its own license and permissions; one module being disabled does not disable the others. The Operations ring screen combines all six on a single page.

ModuleLicenseView permissionManage permission
Purchasingpurchasing_modulepurchasing.viewpurchasing.manage
Logisticslogistics_modulelogistics.viewlogistics.manage
Installed baseinstalledbase_moduleinstalledbase.viewinstalledbase.manage
Problem & solutionsolution_modulesolution.viewsolution.manage
Spare partsspares_modulespares.viewspares.manage
Service and fieldservice_moduleservice.viewservice.manage

Each module's gate sits in its own page layout (layout): the license is checked first; without a license you are redirected to the features page with an upgrade link. Then the view permission is checked; without it the page opens as not found. In the Purchasing, Logistics and Problem & Solution modules, the organization owner and admin get in even without the view permission; in the Installed Base, Spare Parts, and Service and Field modules only the view permission is checked. If a screen shows data of another module (for example the part or problem in a service record), that data is read with that module's own permission; without the permission, the relevant field states which permission is required.

Operations ring

The page opens if you have the license and the view permission for at least one of the six modules. The ring drawing at the top shows the six nodes in this order: Purchasing, Spare Parts, Service, Solution, Installed Base and Logistics. Each node shows the count of what it counts (open purchase item, registered part, open service record, open problem, installed machine and shipment) and links to the module's page; if the module has no license it says «disabled», if you have no permission it says «no permission», and it does not show zero. The data of a disabled or unauthorized module is never read.

JointLinkCountedDenominator
Purchasing → Spare Partsmaterial codethe open purchase item belongs to a registered part codeopen purchase item
Spare Parts → Servicepart useda part was entered on the service recordservice records
Service → Solutionthe record’s problemthe service record is linked to a problemservice records
Solution → Installed Basethe problem’s machinethe problem is linked to a machineproblem records
Installed Base → Logisticsthe machine’s shipmentthe machine is linked to the shipment that brought itinstalled machine
Logistics → Purchasingsame material codethere is a material code in the shipment’s order that also appears in a purchase itemshipment

The Joints section writes each link as «number / denominator» and as a percentage. If the denominator is empty, the link has not been established, or one of the two modules is disabled or unauthorized, it writes this instead of a number («Not measurable»). Note for the Logistics → Purchasing joint: Not origin: these are items that carry the same material code — it does not say that the goods received went out with that shipment. «Today’s decisions» below it shows the first five records in each list, and clicking a record opens it on its own page; each list is read with the license and permission of its own module, and a list that relies on two modules requires both. The lists and their sorting criteria:

  • Open service records: first by priority, then oldest first; there is no target time, the age is shown.
  • Late purchase items: open items past their date, the most overdue first; the criterion is the date the supplier confirmed, or the requested date if there is no confirmation.
  • Machines in the quote window: machines whose warranty ends within 90 days and that have no contract, earliest end first.
  • Open problems: problems that are open or have a proposed solution; first by priority, then oldest first.
  • Delivered, not linked to a machine: shipments more than 14 days past delivery that are not linked to any machine; those whose customer has no machine record first, then oldest first.
  • Critical part: no stock, no open purchase — parts classified as critical, with a net stock quantity of zero or below and no open purchase item with a remaining quantity under this code.

Purchasing: Open Orders

Shows the items of open purchase orders as of a reference day (at most 1000 rows are read; if the limit is reached, the screen says so). Draft and cancelled orders are not included. The cards give the number of open items, late items, items awaiting confirmation and planned items, and the average promise slip. «Late» is measured against the date confirmed by the supplier, or against the requested date if there is no confirmation; items with neither date are counted separately. The filter chips can overlap; you can also filter by supplier.

  • Supply Promise Ledger: number of open items per supplier, promise slip (confirmed − requested) and its median, items where the promise was kept, broken or unknown, keeping and postponement. Tapping a supplier name opens all its items and the promise outcome of each.
  • Tapping an item opens focus panels: the confirmation date and promise history (at most 500 records), the goods receipt ledger (at most 200 records) and «Delay wave» — which part, which machines that use that part, and which open service records are waiting if this item is late. Each link in the wave is read with the permission of its own module.
  • With the purchasing.manage permission you enter orders, add suppliers, write the confirmation date and record goods receipt («Receive»). For items imported from the ERP, the confirmation date and goods receipt are done in the source system; each import overwrites them.

Logistics: Shipments

Shows shipments and the sales orders they are linked to as of a reference day (at most 1000 shipments are read). Order information comes from the sales orders in CRM; a shipment is entered on this screen or created through Connect, and the source column says which. The table has the columns order, customer, dispatch, delivery, status, order amount and source. The cards show the number of shipments, the delivered ones, those without delivery information, those late against the promise, and the average days in transit; the «Shipment flow» strip and the «Distribution of days in transit» are built from the same records.

  • With the logistics.manage permission you enter shipments and mark deliveries; the order options list the first 500 orders in descending order by number.
  • Machine link: the machine brought by the shipment is linked to an Installed Base record. Unlinked deliveries more than 14 days past delivery are collected in a separate chip, and those whose customer has candidate machines are separated from those with no machine record. The link chips are visible if you have the Installed Base license and the installedbase.view permission.
  • Link suggestions: for an unlinked machine, the suggestion is the shipment, among the same customer's shipments (matched by name equality), that was delivered at most 30 days before the machine was commissioned (or dispatched, if there is no delivery date); if there are several candidates, the closest is suggested and the number of remaining candidates is shown. At most 100 suggestions appear on the screen. A suggestion is not a link; you establish the link one by one or for the selected ones in bulk, and this requires installedbase.manage.
  • Tapping a shipment opens the «Machines of this shipment» and «Purchase items for these materials» panels.

Installed Base: What the Customer Has

Groups the installed machines at customers by customer. Records are entered manually on this screen. The cards show the number of installations and customers, and the installations whose warranty is running and those with no warranty information; «no warranty information» means the warranty end date has not been entered, not that there is no warranty. You can filter by status (Active, Out of service and Dismantled) and by warranty. The table has the columns serial no., product, province, commissioning, warranty, contract, status and source.

With the installedbase.manage permission you enter a record with «Add installation». Tapping the serial number opens the machine passport: life line, failure frequency, linked problems, commercial status and the shipment link; each neighboring piece of information in the passport is read with its own module's permission. The screen states separately that there are no installation records at all and that the filter lets no record through.

Installed Base: Aging

Sorts the installed machines by commissioning date, oldest at the top, and divides them into age bands: 0–1 years, 1–3 years, 3–5 years, 5–10 years, 10+ years, Future-dated and Commissioning not entered. The cards show the number of installations, those whose age can be measured, those over ten years old, and those with no commissioning date entered; you filter with the band chips. The table has the columns age, serial no., product, customer, province, commissioning and status. A machine with no commissioning date entered is not counted as «0 years old», its age is not calculated and it stays in a separate band; a future date is also shown in a separate band.

Problem & Solution: Problem Ledger

Keeps the problems (problem records) that come from customers. The cards show the number of recorded problems, the open ones, those with no diagnosis entered, and the recurring ones; the recurrence criterion is the number of distinct customers: the same class must have been seen at at least two distinct customers. The table has the columns customer, problem, class, diagnosis, machine, opportunity, priority, status, seen and resolved. Statuses: Open, Solution proposed, Resolved and Closed — not resolved.

  • Problem classes: Recurring failure, Unplanned downtime, Quality problem, High energy / maintenance cost, End of product life, Spare part unavailability, Supplier dissatisfaction, Delivery issue, Occupational safety, Competitor product failure and Other.

The «Problem class × machine age» radar distributes problems by machine age; showing the next candidate machine requires installedbase.view, and from there you can go on to open a preventive service record. With the solution.manage permission you open a new problem record and change the record's status.

Spare parts

Spare part record and its stock counterpart. This screen has no stock counter of its own: quantities are read from the Stock module (described in Section 11). A part with no counterpart in the stock slice is not counted as «zero stock»; it is counted separately as «no counterpart in stock». The cards show registered parts, critical parts, unclassified ones, those with no counterpart in stock, those with zero stock, and those that are both critical and zero stock. The table has the columns material code, criticality, stock status, quantity, warehouse and open purchase; the open purchase column requires purchasing.view.

The «Part assurance» matrix distributes parts as criticality × stock and lists the order status of parts that are critical but not in stock; «no stock» in the matrix means a net quantity of zero or below, while the «Zero stock» card counts only exact zero. An open purchase is a purchasing item that has a remaining quantity and whose material code matches exactly. With the spares.manage permission you classify a part as Critical or Normal and add and remove compatibility in the «Which machines does it fit?» panel. There is no form on this screen that creates a new part.

Service and field

Keeps failure, maintenance and complaint records; this screen has no target time (SLA) and no billing, priority only sorts, and age is an observation, not a verdict of lateness. The cards show the number of open records, total records, the oldest open record and closed records. The record types are Failure, Maintenance and Complaint; the statuses are Open, In progress, Closed and Cancelled; the priorities are Urgent, High and Normal. You filter by status, type and the open / unassigned / oldest open chips. The list shows the newest 200 records, the total is counted separately; the columns are no., record, type, status, priority, installation, problem, technician and age.

  • The Service Desk shows records in four columns: Unassigned, Open, In progress and Closed in the last 7 days.
  • The new service record form requires installedbase.view together with service.manage, because the record is linked to an installation.
  • Tapping the record number opens a panel: warranty badge, status and priority, technician (hr.view), linked problem (solution.view) and parts used (spares.view; parts compatible with the product come to the top of the list marked with ★). Changes in the panel require service.manage.