Products / TeleForge
2026 Product · Pre-pilot

TeleForge

Telegram simulation without a PLC. Edge cases on demand.

Generate synthetic SAP MFS telegrams without a PLC and without an emulation. Test scenarios, trigger edge cases, wire it into CI/CD. On-premise, annual licence.

The problem

Testing MFS code without a PLC is half-baked today.

The emulation takes an hour to boot, is usually occupied by someone else, and a clean edge case such as “five hundred handling units jammed at once” cannot be triggered there anyway. What is left: assembling telegrams by hand in SE16, hoping the format is right, and on failure not knowing whether the bug sits in the code or in the test.

That is the reality in almost every MFS project. Tests get avoided because they are laborious. Edge cases are discovered when they blow up in production. CI/CD barely happens because the setup is too complicated.

TeleForge lowers the friction. Telegram templates, scenarios, sequences, pass/fail, automatable. Testing becomes standard practice rather than an act of heroism.

How it helps

Three capabilities. One tool.

01

Generate telegrams

Compose routing, arrival, confirmation, status and error telegrams from parameterised templates. For stacker cranes, pick-up and drop-off as well.

Standard telegram types ship with the product. Site-specific CTT structures are maintained once and then available as building blocks.

TemplatesCTT structuresParameterisedBAdI-extensible
02

Orchestrate scenarios

Chain telegrams into sequences with delays, loops and deliberate faults. A whole day of operation or one targeted edge case.

Build a scenario in the Fiori editor, or import a TeleTrace recording and turn a real situation into a repeatable test.

SequencesDelaysLoopsFault injection
03

Automate

Trigger scenarios from CI/CD via REST and get a pass/fail report. Regression testing for material flow logic becomes a routine step.

A safeguard prevents accidental sending into clients flagged as productive. Bypassing it takes a deliberate, documented release.

REST triggerPass/failRegressionProduction lock
Getting started

From transport to test suite in three steps.

01

Import the transport

Runs in namespace /FROEH/TF, no modifications to the SAP standard. Guided IMG path. Effort: 30 minutes including a smoke test.

02

Configure templates

Standard telegram types are there out of the box. Site-specific CTT structures are maintained once and stay available as building blocks.

03

Build, send, compare

Assemble a scenario in the Fiori editor or import a trace recording. Run it against development or test. Pass/fail report in seconds instead of hours.

Licence

Annual licence, three tiers.

Scales with the number of systems. All prices exclude VAT, no setup fee.

Single project · 1 system

Bronze

from € 1,800 / year
  • 1 system / 1 warehouse
  • Standard telegram types
  • Fiori scenario editor
  • Updates within the major version
  • Email support (best effort)
Enquire about a licence
Recommended
Up to 5 systems · CTT support

Silver

from € 4,900 / year
  • Up to 5 systems / warehouses
  • Unlimited custom CTT structures
  • CI/CD trigger via REST
  • TeleTrace bridge (import)
  • Prioritised email support · 2 working days SLA
Enquire about a licence
Unlimited systems · multi-client

Enterprise

On request
  • Unlimited systems and clients
  • Custom telegram types and generators
  • On-site onboarding and training
  • Direct influence on the roadmap
  • Priority support · 1 working day SLA
Enquire about a licence
Questions

Before you ask: probably answered already.

How does TeleForge differ from TeleTrace?
TeleTrace records real production telegrams and plays them back. TeleForge generates synthetic telegrams from scratch, for test and edge-case scenarios that have never occurred in reality. The two complement each other: Trace for reproduction, Forge for development and regression. Trace recordings can be imported as Forge sequences.
Why not simply use the SAP emulation?
Emulations are close to reality, but slow to set up, often contended (only one instance in test) and poor for isolated edge cases. TeleForge complements the emulation rather than replacing it: for the first 80 % of tests a synthetic telegram in seconds beats spinning up an emulation environment for hours.
Which telegram types are included?
For conveyor systems: routing request, arrival, confirmation, status, error, heartbeat. For stacker cranes: pick-up and drop-off (dual cycle). Site-specific CTT structures are maintained once in customising and are then available as building blocks. Custom telegram types can be added via BAdI.
Does TeleForge touch the production system?
No. TeleForge is explicitly meant for development, test and sandbox systems. A lock prevents accidental sending into clients flagged as productive. Bypassing it requires a deliberate, documented release.
Pilot programme · Q1 2027

Looking for three pilot sites.

I am looking for three pilot sites. Joining early means permanently preferred pricing, direct influence on templates and the scenario editor, and personal support during onboarding. In return I ask for an honest account of your experience after three months of use.