EDGEBIC Localization Explained: Renaming the Software to Your Plant's Words

EDGEBIC by User Solutions includes a Localization tab that lets an administrator rename on-screen text, tab captions, button labels, and column headers, to the vocabulary your plant already uses. It is a label-override layer, not a change to how anything works. A shop that has said machine group for thirty years can make the software say machine group too, and nothing about the schedule changes.

That sounds like a small feature. In practice, terminology is one of the quieter reasons scheduling software fails to take root on a shop floor, and it is one of the cheapest to fix.

Where It Lives

Localization is one of the tabs on the Settings screen, alongside the data source, the site-wide scheduling policy, data management, import, and security. Opening it shows a list of rows, each one a piece of text the application displays.

An empty Alternative means the default is used, so you never have to fill in the whole list. You override the handful of terms that matter to you and leave the rest alone.

Above the list sits a single toggle, Use alternate strings. Off, the application reads the shipped defaults. On, it reads your alternatives wherever you supplied one and falls back to the default everywhere else. Edits are live, so you can see the effect as you make it, and a save persists the set.

What It Is Good For

The obvious use is vocabulary alignment. Manufacturing terminology is genuinely regional and genuinely industry-specific. What one plant calls a work center another calls a machine group, a cell, a station, or a resource. What one calls a bill of routing another calls a router, a traveler, a process sheet, or simply the routing. None of these are wrong, and none of them are worth arguing about.

The argument you want to avoid is the one where an experienced supervisor decides the new system is academic because it uses words the plant does not. That reaction is not really about words, but words are where it surfaces, and words are the part you can fix in ten minutes.

The second use is quieter and more valuable: reducing the reading load on the people who use the software least. A planner sits in EDGEBIC all day and will absorb any vocabulary within a week. A supervisor who opens it twice a shift, and an operator who touches only the shop floor kiosk, will not. Every unfamiliar term is a small pause. Removing the three or four terms those people read most often is worth more than renaming forty terms a planner reads once.

What It Deliberately Does Not Touch

Localization is presentation. It does not change:

• the scheduling engine or any capacity arithmetic
• the data stored in your database, including product names, work center names, and job numbers
• what a report computes, only what its column headers say
• permissions, roles, or what any user can do

That last separation matters more than it looks. Because renaming can never change a plan, it is a safe thing to adjust at any time, including in the middle of a live implementation. Contrast that with the site-wide scheduling policy on the neighboring Settings tab, where changing a setting genuinely changes what the next run produces and deserves a deliberate moment and a note to the team.

There is also a distinction worth drawing against the column glossary system. Localization changes what a column is called. The glossary explains what a column means, with its formula, unit, and examples, on demand from the report itself. Renaming a column does not rewrite its definition, so if you rename aggressively, expect the glossary text to keep speaking in the shipped vocabulary.

Moving a Label Set Between Machines

EDGEBIC runs as an application on each user's PC, and Localization includes export and import controls precisely so a custom vocabulary does not have to be retyped on every workstation. The intended pattern for a multi-user site is straightforward.

1. One administrator builds the override set once, on one machine.
2. Export the set.
3. Import it on each other workstation, or as part of setting up a new one.

A reset control clears every alternative at once and returns the whole application to the shipped defaults, which is the fastest way back if an override experiment went too far.

How Much to Rename

The honest answer is: less than you first want to.

A small, high-traffic override set is almost always better than a comprehensive one, for three reasons.

Support and documentation speak defaults. Guides, training material, and any support conversation use the shipped names. Every term you rename is a term someone has to translate in the other direction when they read a guide or describe a problem. A short list is easy to hold in your head. A long one is a private dialect.

Consistency is the whole benefit. A rename that reaches some screens and not others is worse than no rename. Overriding a handful of terms thoroughly beats overriding many terms partially.

Renaming does not fix a modeling problem. If your plant uses two different things and calls them both cells, renaming work center to cell will not make that ambiguity go away. It may hide it. That is a case for getting the work center model right first and the vocabulary right second.

A reasonable starting set for most shops is three to six terms: the one for a machine, the one for a routing, the one for a job, and whatever your plant calls the finished item.

Where It Fits in a Rollout

Localization belongs late in an implementation, not early. Get the master data, calendars, routings, and a first working schedule in place using the default vocabulary, because that is the vocabulary every guide and every support answer will use while you are learning. Then, once the system is producing plans people trust, do a vocabulary pass with the supervisors who actually read the screens, and export the result to every workstation.

Done in that order, renaming is a finishing touch that makes the software feel like it belongs to your plant. Done first, it is one more variable in the middle of a period when you want fewer.

For the step-by-step version of making an override, see how to rename on-screen labels. The complete EDGEBIC guide maps where Settings sits relative to the rest of the system, and /edgebic covers the platform as a whole.

The Point of Speaking the Plant's Language

Scheduling software earns its place by being used, and being used depends on being read. A supervisor who has to translate four terms on every screen reads the screen less carefully, and eventually reads it less often. Matching the words to the shop is not decoration. It is one of the few adjustments that costs almost nothing, risks nothing in the plan, and makes the difference between a system your people navigate and a system they tolerate.