Skip to content
Service-King

Digital Twin - Service-King

Your company's digital twin. Connect data and operations.

What do you have, where is it saved, who uses it, and what was done recently? Connect equipment, places, people and operations into a clear image of the company.

Service-King provides the basis for records and service. RFID readings and exchange of selected data with ERP We adapt to a specific process.

Conceptual illustration of a plant with warehouse, machinery and office
Business concept illustration. The actual views of individual modules are shown below. Enlarge ↗

The information you need meets at the same thing.

The asset list, issues and repair plan describe the different aspects of daily work. Linked records allow you to check them in a common context.

01

Assets and assortment

You can distinguish between the items of tools, devices, containers and clothing. You combine name, group, photo and IDs.

02

Seat structure

Warehouses, halls, rooms, racks and shelves create a division that is understandable to the team.

03

People and responsibility

Person assignment helps determine who uses the equipment. Your own panel shows the data available to this person.

04

Machines and parts

The device file combines parts, documentation, history and service.

05

Reports and reviews

The need for action meets the deadline, procedure, contractor and recorded work result.

06

Traffic and documents

Receipts, issues, returns, and movements explain what happened to specific items.

In inter-company transactions, the client may receive a panel of his own organization. Relationships and permissions determine the available scope. The map helps you see the structure, and the records and reports help you answer specific questions.

Seat structure

From the company plan to a specific place.

Zone-King Map presents halls, areas and storage areas. Layers help separate different parts of an object.

You go inside the zone, the shelf and its contents. The location results from the assignment of items and saved operations.

Discover maps, racks and shelves in Zone-King →

Sample data in the applicationEnlarge preview
Zone-King location map in Service-King
Actual view of zone map on sample data.

People and responsibility

It is known who uses the equipment.

Linking items to an employee helps you prepare the check-out, check the allocation and clarify the shortage.

The employee uses his own equipment view and available T&A history. The client can work in the data panel of his organization - according to the role and the running workflow.

See separate customer and employee views →

Tool case, drill, clothing and employee ID
Sample equipment and person ID. Illustrative image. Enlarge ↗
Sample data in the applicationEnlarge preview
Employee portal with assigned equipment and T&A history
The employee checks the equipment assigned to his record.
Sample data in the applicationEnlarge preview
Record of the machine and related parts on fictitious data
The device card connects a machine with information about its components.

Machinery management

The machine with its parts and documentation.

Device card collects machine data, installed parts, log and technical files.

You return to replacing a specific element and the arrangements saved on the device. This is the context needed for further service and work planning.

See the machine and parts replacement card →

Submissions, plan and execution

From the description of the problem to the result of the work performed.

Report indicates equipment and location. The staff verifies the need and arranges the order contractor, procedure and deadline.

The technician records activities, results, comments and necessary documentation. The history of a thing also includes its servicing.

Learn about maintenance and service →

Motor, bearing, drive belt and service kit
Examples of elements related to device operation. Illustrative image. Enlarge ↗
Sample data in the applicationEnlarge preview
List of orders in the Service-King Service Center
Actual view of service requests on sample data.

One drill. Several related steps.

The example shows why you want to combine modules around the ID of the same thing.

  1. Check-out. The drill has a name, photo, UHF, additional QR and saved rack. The warehouseman issues a specific item to an employee.
  2. Report. Employee describes the damage. The staff checks the problem against the appropriate file and plans work.
  3. Service. The technician uses the checklist and records the result and documentation.
  4. Continued circulation. Once service is completed, the actual update is performed and the required return to the warehouse is performed.

When things are missing, you check the last place and history. UHF search on a compatible handheld terminal with the appropriate application can help in the field. It's still the same file and its history.

Connection to the master system

ERP and Service-King can complement each other with data.

ERP often leads indexes, business partners, orders and commercial documents. Service-King can add the physical movements of individual items, load carriers and people, linked to locations.

We set the connection scope for the client's system. On the Service-King side, we use the available interfaces of records, locations and controlled operations. On the ERP side, we check API, exchange formats or the need to prepare an adapter.

First, we establish the meaning of the data and responsibility for changes. Then both systems can describe the same things to their appropriate extent.

Conceptual illustration of exchanging company data with a business system
Agreed data exchange concept. The scope of integration depends on the project. Enlarge ↗

What can we associate with ERP?

The breakdown below is the starting point for the project. For each group we set fields, common identifiers and the direction of exchange.

Indexes and products
ERP can pass index, name and unit. Service-King associates them with item. The product index and unique equipment number have different functions.
Contractors and places
We connect companies and branches with circulation locations. We establish common identifiers for warehouses, positions and responsibility for names.
Employees
An ERP or HR system may provide person ID, department and agreed information. We limit the scope of data to the needs of allocation and operations.
Bounties and tasks
A number from a parent system can be the context for a batch, load carriers, or activity. We check the connection and available fields for the client's order model.
Traffic and confirmations
We agree on the transfer of selected receipts, check-outs or transfers. We determine whether the data is information, a document proposal or a confirmation requiring acceptance.

Which system determines the change?

For each type of data, we choose the host system and the rules for updating them.

Scheme of exemplary data exchange between ERP, Service-King and event sources
Conceptual diagram. We determine the scope of data and the connection method for a specific implementation. Enlarge diagram ↗
01

Source and responsibility

For example, ERP maintains indexes and orders, and Service-King maintains the assignment of specific pieces and operations from the shop floor. We agree on common identifiers.

02

Direction and moment

We choose to exchange in one or both directions: after an event, periodically or on demand. When both sides change the same data, we define a rule to resolve the differences.

03

Confirmations and retries

We are designing a way to confirm, control repetitions and resume after a break. We identify the person responsible for unexplained differences.

In the project we decide how to show the source of information, the time of the last save and the operation that changed it. We are also preparing exception handling: unknown tag, no reading, incorrect assignment, connection interruption and data change in ERP. We determine how to show confirmed operations and data awaiting clarification. We design the connector, synchronization and handling of pending events for a specific system.

ERP Scenario → Hall → ERP

From order data to confirmation from the floor.

Sample integration scenario for tagged load carriers related to a production order:

  1. Data from ERP. The agreed indexes and order context are sent to the prepared workflow.
  2. Linking things. Service-King links pieces or load carriers to IDs and places.
  3. Receipt at the hall. A scan or event from a prepared RFID point confirms the corresponding movement.
  4. Next steps. Operations record the path through machining and quality control.
  5. Confirmation required. The operator or device transmits the determined data. The result of the inspection is recorded separately from the presence in the zone.
  6. Information for ERP. The selected confirmation returns in the agreed format. The user can review the history of item.

This is an example of a connection to be agreed. The screen shows the actual Service-King report with sample parts and locations.

Sample data in the applicationEnlarge preview
Report of selected parts with IDs and locations
List of selected items and their places in the sample circulation.

RFID delivers events. The process gives them meaning.

An employee's scan or a prepared stationary point helps recognize an item and use its identifier.

01

Recognizing things

UHF indicates a marked item. An additional QR allows you to recognize the same record with a camera.

02

Movement confirmation

We associate the reading with the point and circulation rules. The worker or integration performs the actual operation.

03

Result of the action

Attendance and termination have different meanings. The inspection result requires your own confirmation.

The container tag identifies the load carriers; We determine the method of confirming its content separately. The last reading point describes the recorded event. Get to know the zone RFID points and the principles of their operation →

Industry Summaries and Context

The report answers a question arising from the data.

Manager checks quantities in zones, recorded operations, cycles and stay times. We select the range of indicators based on the information that the company actually records.

Example shown applies Garment circulation and cycle limits. Helps identify textiles for further inspection; does not measure the operation of the machine controller.

When analyzing time, we determine the meaning of the beginning and end of the measurement. Learn about the rankings and circulation history →

Sample data in the applicationEnlarge preview
Report of clothing cycles and time spent in the zone in Service-King
Industry example: textile cycles and zone time, as recorded.

The right view for each role

  • Warehouse and logisticsWhat was received, spent and where were things recorded? Moving from groups of names to specific identifiers.
  • EmployeeWhat equipment am I assigned? Own scope of information available to a person.
  • Service and maintenanceWhat does it take to work on the machine? Context of the part, location, notification and previous arrangements.
  • ManagerWhat is happening in selected zones and what needs to be explained? Summaries, monitors and reports.
  • Customer and service companyCustomer panel and service access to selected sub-organizations, in accordance with relationships and authorizations.

Implementation starts with one workflow.

The next stages allow you to check the suitability of the model and expand it on common principles.

01

We choose questions

We determine whether the most important thing is the allocation of equipment, the location of the load carriers, control or service.

02

We are organizing the data

We prepare files, identifiers, locations, people and connections with ERP. We explain duplicates and names.

03

We map the circulation

We launch the selected hall, warehouse or equipment group along with operations and history.

04

We include sources

We configure the necessary scanning, RFID points and agreed data exchange. We check ordinary and unusual situations.

05

We choose views

The employee, warehouseman, manager and customer receive the necessary information and actions.

06

We are extending the model

We add additional places, types of equipment and processes after checking the first scope.

Questions before implementation

Do we need a new ERP?
We are checking the possibility of connecting the necessary data with the current system. The scope results from its interfaces and the way the company works.
Does a digital twin have to be a 3D model?
The basis of Service-King are records, relations, operations and clear views. Zone maps help visualize them. Additional 3D models or visualizations are a separate scope.
Is everything updated without employee involvement?
Selected automatic points can deliver events. Other information requires user confirmation or ERP data. We determine this for a specific activity.
Can we measure machine downtime and efficiency?
History and service help you understand the equipment flow. OEE, measurement from controllers, prediction and simulations require additional sources and a separate project.
How to start a conversation about integration?
Prepare the name and version of the ERP, contact details for its maintainer, sample data and a description of one workflow you want to improve.

Free consultation

Show us one workflow in your company.

Let's go the way of a tool, container or device. We'll figure it out what you already have in ERP, what should come from the readings and what view will help the team.

  • Process: thing and its subsequent places.
  • System: ERP name and version and available maintainer.
  • Purpose: a question that is difficult to answer today.

On this basis, we will propose the scope of piloting and further expansion.

Let's talk about the digital twin

Describe one workflow and the systems you use.

Website language

Choose a language.