EDGEBIC Configuration Options Explained: What You Can Tune, and Where

Production scheduling software settings get a bad reputation because most products mix two very different things in one screen: knobs that change the plan, and knobs that change the picture. EDGEBIC by User Solutions separates them deliberately. The Settings tab holds site-wide policy that affects everyone and, on its Schedule tab, the scheduling engine's own rulebook. A separate Configuration tab inside the scheduling area holds presentation: colors, labels, overlays, and what a drag is allowed to do. Nothing in the second group changes the math in the first.

This post is the map: what lives where, what each group decides, and what needs a restart. The step-by-step for the engine policy is in how to configure scheduling policy in EDGEBIC, and the boundary itself gets a deep dive in the settings that change how your schedule looks.

Two Homes, One Rule

The rule to carry: policy changes what the scheduler computes, display changes what you see.

That scope difference explains a support question that arrives at every plant eventually: two planners see different-looking Gantt charts and one of them assumes the schedule differs. It does not. They are reading identical rows through different presentation settings.

The Settings Tab, Sub-Tab by Sub-Tab

DataSource is covered in how to install and connect EDGEBIC. Security is covered in EDGEBIC users and roles explained. Import is covered in EDGEBIC import masks explained. This post concentrates on Schedule and Localization, plus the display side.

The Scheduling Policy: Seven Decisions

Settings, then Schedule, holds seven groups. Each is one decision about how the engine behaves for the whole site. You pick, you save, and the next scheduler run uses the new policy. No restart.

Three of these are worth flagging as genuinely consequential rather than cosmetic.

Default Scheduling Direction stamps a direction on every newly created job and quote. Existing orders keep the direction they were created with, and each order can still be overridden individually. That is why flipping the site default does not retroactively change anything; see forward vs backward scheduling for what the two directions actually do to a plan.

Partial-Confirm Behaviour decides where the next reschedule puts downstream work after a short confirm. Trusting the operator's finish stamp pulls work earlier and writes off the missing hours. Forward-shifting keeps the unfinished hours visible in the plan and queues downstream steps behind them. The default matches mainstream APS behavior.

Optimizer Engine selects the brain, not the goal. Both engines are propose-only: nothing changes until you accept, and neither can make the schedule worse than what you had. The goal preset and the time budget are chosen per run on the Optimizer tab instead, which is covered in the EDGEBIC optimizer guide.

The Display Configuration: Five Tabs

Open the Schedule tab, then Schedule View, then the Configuration sub-tab. It is organized into General, Views, Appearance, Time and Schedule, and Manufacturing. After changing anything, click Save and Apply Now Configuration.

The cards planners actually reach for:

• Host Scheduler decides how Gantt edits are committed. The default batches your edits so they persist together when you click Save Changes, which is the safety net that lets you review before committing.
• Operations controls how bars read: a visual minimum duration so short operations stay clickable, start and end times printed on bars, where the status color strip sits.
• Resource Display holds the operation label pattern, built from a field picker, per work center or applied to all of them at once.
• Timeline Limits bounds how far the timeline scrolls, with buffer weeks either side.
• Appointment Permissions enables or disables Gantt interactions: create, edit, delete, copy, drag, resize, and dragging a bar onto another work center row.
• Actual Date Tracking draws actual start and end markers against the planned bar, flags variance beyond a threshold, and highlights in-progress work.
• Setup and Queue Time renders setup, queue, teardown, and move time as their own segments on the bar.

Three buttons at the bottom matter as much as the settings above them: Reset to Defaults always brings factory settings back, and Import and Export move a whole configuration between machines as a file. Tune once, export, and every other planner imports instead of clicking through forty options.

The color and label layer specifically is covered in making the Gantt speak: colors, labels, and layouts.

Localization: Rename the Software to Match the Plant

The Localization tab lets an administrator rename on-screen text: tab captions, button labels, column headers. Each row shows the key, the default text, and an alternative. A single toggle switches the whole application between defaults and your alternatives, and edits are live.

This is more useful than it sounds. If your plant says "cell" and the software says "work center", renaming the label is cheaper than retraining vocabulary, and the concepts still map one to one. Label sets export and import as files, so a second machine inherits them.

What Is Not in Settings, and Where It Actually Lives

Half the time spent hunting through a settings screen is spent looking for something that is not there by design.

The pattern is consistent: anything that describes your plant is master data, and anything that describes how the application behaves for everyone is a setting. Getting that distinction right the first week saves a lot of searching later.

Who Should Be Allowed to Change What

Configuration is permission-controlled, and the split maps neatly onto the two homes.

The whole Settings tab is gated: a user whose roles do not include it does not see the tab at all. That is the correct default for planners and supervisors, because Settings holds the database connection, the Clear Data Tables utility, and the site-wide scheduling policy. One person changing scheduling direction for everyone should be a deliberate act by someone accountable for it.

Display configuration is the opposite case. It is per machine and per user, it changes nothing anyone else sees, and it is fully reversible with Reset to Defaults. Let planners tune their own screens freely.

The one grey area is worth naming: the display layer includes checkboxes that enable or disable Gantt interactions such as drag and delete. Those look like access control and are not, because they are per-machine settings rather than account rights. If you need someone genuinely prevented from dragging operations, do it with their role, not with a checkbox on their own screen that they can untick. See EDGEBIC users and roles explained.

A Configuration Review Cadence

Most settings are decided once and never revisited, which is fine. Three are worth a scheduled look:

The export habit is the highest-value one on that list and the least practiced. A display configuration takes an afternoon to get right and five seconds to save as a file.

What Needs a Restart

Only the database connection. Scheduling policy is read fresh at the start of every run, so the sequence is save, then run. Display configuration applies when you click Save and Apply Now Configuration.

That means every configuration change except the database connection can be made during a working day. Whether it should be is a different question: policy changes alter what the next run produces, so make them at a quiet moment and tell the team.

Where to Go Next

Read how to configure scheduling policy in EDGEBIC for the seven groups in detail with the fields and defaults, the settings that change how your schedule looks for the display-versus-engine boundary and the three traps inside it, and configuration mistakes in EDGEBIC for the symptoms that send people to support. EDGEBIC localization explained covers the Localization tab, where an administrator renames on-screen text to the plant's own vocabulary without changing how anything works. The whole product sits in the EDGEBIC complete guide.

Bring one setting you have argued about internally to a demo of EDGEBIC, and we will show you which side of the line it falls on.