Skip to Content
Click on "Edit" in the right panel to replace this with your own HTML code
Support Knowledge Base

Support should help manufacturers regain control faster.

TSRB support is organized around practical manufacturing questions: what happened, what is blocked, who owns the response, what evidence is needed, and how the issue becomes easier to prevent next time.

Support for real manufacturing environments

The TSRB support knowledge base should help users understand how to use Production Intelligence, MERIT 2.0, dashboards, machine connections, ERP data, governance workflows, and support tickets to resolve issues with clarity.

Production Intelligence support

Help with machine status, utilization, downtime, part counts, dashboards, operator views, and data interpretation.

Governance support

Help with exceptions, ownership, SLA clocks, gates, escalation, proof-of-execution, and learning-loop questions.

Connectivity support

Help with ERP data, machine data, network readiness, DNC workflows, hardware signals, API/SQL questions, and integration prerequisites.

Recommended knowledge-base structure

Group support articles by how customers actually experience the system.

Getting started

Login, roles, navigation, dashboard basics, operator portal basics, and what each view is designed to answer.

Machine visibility

Machine states, uptime/downtime, counts, utilization, timelines, fault events, and status troubleshooting.

Jobs and ERP context

Work orders, operations, routings, part numbers, labor tickets, completion, and status synchronization.

Governance workflows

Acknowledging exceptions, assigning ownership, closing with proof, escalation, gates, and learning-loop updates.

Pilots and deployment

One-machine pilot setup, validation steps, success measures, machine readiness, and expansion planning.

Troubleshooting

Common symptoms, data gaps, connectivity issues, missing context, user permissions, and when to open a ticket.

How to request support

1. Describe the issueInclude the machine, job, operation, page, event time, user role, and what result you expected.
2. Attach evidenceScreenshots, part numbers, work orders, controller messages, dashboard examples, or error text help accelerate diagnosis.
3. Define urgencyTell TSRB whether the issue is informational, blocking production, affecting reporting, or preventing governed action.
Suggested button link: Update the primary CTA to your actual Odoo help-ticket URL after pasting this page.

Need help with a production issue?

Open a help ticket with the machine, job, time, screenshot, and impact so TSRB can focus the response quickly.

Open a Help Ticket