T-NEX
Menu
For industrial mid-market companies

Use AI where your production benefits from it.

We connect software and AI with processes in planning, IT and production. Together, we select a specific task and test the solution with your data and users. The results show how the application can be developed further.

Scope an industrial AI pilotExplore the details
AI and software for industrial companies
  1. 01Start with an important production task
  2. 02What the MONTEE customer project demonstrates
  3. 03Connect ERP, production systems and the application

Aligned with your processes

In daily work

Start with an important production task

For management, production leaders, production planning, IT and project owners in manufacturing businesses.

Start with a recurring question: Which work instruction applies? Which document is missing? Which projects need the same resources? The answer determines the data, interface and integrations. A clearly defined task makes development and operating decisions easier to assess.

Three distinct starting points
AreaConcrete taskRelevant T-NEX service
Technical documentsFind approved information or prepare extracted details for reviewKnowledge management or document AI
Production planning and executionConnect work plans, instructions and shop-floor feedbackCustom development, illustrated by the MONTEE project
Project portfolioConsider priorities, ownership and resources across projectsProject portfolio management
Solutions and services

The right solutions for your team.

Overview

What the MONTEE customer project demonstrates

T-NEX contributed to the development of MONTEE manufacturing software. The application connects work plans maintained in administration with guided steps at an operator terminal. Feedback, quality checks and relevant documents remain associated with the job.

MONTEE is a customer project. The reference demonstrates development work on planning, interfaces and feedback. It is not a standard T-NEX MES and does not establish a general increase in throughput. System boundaries and rights to existing components are clarified separately for a new project.

Overview

Connect ERP, production systems and the application

Establish where items, bills of materials, orders and approved document versions are maintained. An application needs clear rules for reading data, writing updates and leaving decisions in the authoritative system. Existing interfaces and data quality are evaluated against real examples.

Acceptance should cover a corrected bill of materials, a duplicate order and an interrupted connection. If mobile or local buffering is required, later synchronisation belongs in the same test. Recovery after an error is part of the workflow.

Overview

Involve operations, IT and employee representatives early

Operations defines the task and evaluates results. IT assesses integration and operation. Data protection roles review processing. In Germany, section 87(1)(6) of the Works Constitution Act is particularly relevant to technical systems for monitoring employee behaviour or performance. The specific works council involvement is clarified before introduction.

Make the intended views concrete: Which individual records are captured, which analyses are possible and who can access them? A view for order coordination and an employee performance analysis are different decisions. Define purpose, access and deletion accordingly.

Overview

Evaluate the pilot against your current process

Agree comparison cases and quality criteria before development. Knowledge search needs correct answers and supporting sources. Document processing needs accurate output fields. A production interface needs clear guidance, correct job allocation and complete feedback.

Include the time users spend checking and correcting results. A successful model call alone does not establish operational benefit. The pilot ends with a reasoned decision to expand, adapt or take another approach.

Overview

Include ongoing operation in the decision

After introduction, an application needs owners for content, users, interfaces and changes. AI adds source maintenance and evaluation of changing answers. Include this work when deciding on scope.

Agree the operating environment, handover and routes for incidents and changes at the start. Another production hall, site or document type may require different access controls and tests. Expansion follows demonstrated requirements.

Overview

Prepare a concrete next step

A process map, the systems involved and a few approved example cases are enough for initial scoping. Identify a user representative, a technical contact and the decision to be made after the pilot.

We use this information to define development scope, integrations and acceptance criteria. Operations and IT can then evaluate the same proposed project.

  • A normal case and the main exceptions
  • Authoritative systems and available interfaces
  • Required roles and analyses
  • Expected improvement and current handling effort
Development references

From the task to the application.

FAQ

Questions about the solution

Do we need our own AI team?

Operations and IT need to support the use case and make decisions. T-NEX provides the agreed development work. A dedicated model development department is not automatically required for a limited application.

Can we begin with a production pilot?

Yes, when the task and environment can be sufficiently bounded. Changes to machine control or safety-relevant functions require additional technical and specialist assessment. An information assistant is a distinct use case.

Can we deploy MONTEE as a standard T-NEX product?

This page presents MONTEE as a customer project and development reference. A new project is planned around your requirements and components that may lawfully be used. The reference does not imply a general T-NEX MES package.

How is an economic improvement demonstrated?

Compare the same case types before and after the change, including review, rework and operating effort. A fixed saving is not assumed before that assessment.

Sources & further reading

  1. Section 87 BetrVG: Co-determination concerning technical systemsgesetze-im-internet.de
Related options

You may also be interested in these.

Scope an industrial AI pilot