The Quarterly EDGEBIC Admin Health Check

A quarterly EDGEBIC admin health check is six short reviews: accounts and roles, custom roles against new permissions, a backup that has actually been restored, import masks against their current files, the site scheduling policy, and the housekeeping that quietly accumulates. In EDGEBIC by User Solutions none of these takes long, and none of them announces itself when it goes wrong. That is exactly why they belong on a calendar rather than in someone's memory.

Go-live has its own gate list, covered in what an admin checks before go-live. This post is the routine that follows it: what to look at every three months so the system in month 18 still behaves like the system you commissioned. Every control it names lives on a Settings tab you open in the application.

Check 1: The Access Review

Open Settings and the Security tab, then read the Users list top to bottom. You are looking for four things.

Leavers still active. Deactivating rather than deleting is the right move when someone leaves, because it bars sign-in while keeping their history attributable, but it only helps if someone actually does it. Walk the list against your current headcount.

Accounts locked and forgotten. Five consecutive wrong passwords lock an account for 15 minutes by default, and the Users grid shows a locked column. A person who gave up in April and has been borrowing a colleague's login since is the problem this column exists to expose. Clear it with Unlock, covered in how to unlock a locked-out user.

Shared logins. One account per person, always. The security audit trail records sign-ins, password resets, role changes, and permission denials permanently, and every one of those records is worthless if two people use one name.

Roles that no longer match the job. People change roles inside a plant more often than anyone updates the software. Because a user's rights are the union of their roles, a promotion that added a role never removed anything.

Check 2: Custom Roles Against New Permissions

This is the check almost nobody thinks of, and it has a distinctive symptom: an administrator can see a new feature and nobody else can.

When a product update introduces new permissions, only the built-in Administrator role receives them automatically. Custom roles must be granted new capabilities explicitly. That is deliberate, because the alternative is a release quietly widening what your planners can do, but it means every upgrade leaves a small gap between what the software offers and what your roles allow.

So after any upgrade, and at least quarterly, open each custom role and read its permission tree. The tree is grouped by area (Sales, Production, Master Data, Insights, Data, Settings, Security), so a new capability sits visibly under its group. Grant what the role genuinely needs. The mechanics are in how to create a role, and the failure mode is one of the classics collected in user and permission mistakes.

Check 3: A Backup That Has Actually Been Restored

Most plants can answer "do you have a backup?" Far fewer can answer "when did a backup last become a working system?"

The quarterly version is small. Take a current backup: on the local single-file database, the Export button on the DataSource tab makes a timestamped copy in one click, and it is safe to click while the application is running. On SQL Server, confirm the scheduling database is genuinely inside IT's rotation rather than assumed to be.

Then prove one restores. Restoring into a separate training database rather than over production is the whole trick, and it is worth doing as a timed exercise once a quarter. That drill has its own post: running a restore drill. The wider backup rhythm sits in keeping the database healthy over time.

Check 4: Import Masks Against Their Current Files

An import mask maps columns in your file to fields in the database. It keeps working until the file changes, and files change without telling anyone: a column gets renamed, a report adds a field, someone rebuilds the export.

Quarterly, dry-run each mask you rely on against the file it actually reads today, on a small slice. Read the result counts. Every run reports rows as created, updated, reused, or failed with a reason, and a mask whose source drifted usually shows up as an unexpected pile of one of those four. Confirm too that routing files are still whole, since a routing import wipes and recreates a product's steps each run and a split file leaves an incomplete routing behind. The ownership discipline around this is in the data import governance workflow.

Check 5: Re-Read the Scheduling Policy

Site scheduling policy lives on the Schedule tab in Settings and shapes every run: the default direction stamped on new jobs and quotes, what happens when a backward job does not fit, which optimizer engine runs, how a short confirm is treated, how far ahead the engine may search for capacity, whether parallel hours roll into job totals, and whether sub-assemblies are scheduled with their parent.

None of it needs a restart, since policy is read fresh on every scheduler run. That convenience is also the risk: a setting changed in a hurry six months ago is still in force and nobody remembers deciding it. Read the tab, confirm each choice is still the one you would make today, and write down anything you change. See how to configure scheduling policy for what each group does.

Check 6: The Housekeeping That Accumulates

Three things pile up quietly.

Import run logs. One file per run, and deleting a mask does not delete its logs. Prune them periodically.

One-off capacity overrides. A daily override replaces the shift formula for that work center, shift, and date until someone removes it, so a day set to zero for a shutdown stays closed forever. Review the override list and reset what has passed.

Drifted screen layouts. Grid and panel layouts save per user automatically, which is a feature until someone hides a column and forgets. Any view's configuration dialog has a Reset to Defaults button; see administering grid layouts.

The Quarterly Checklist

Thirty years of deployments at User Solutions (founded 1991, with systems at the US Navy, GE, and Cummins) say the same thing: systems rarely fail at commissioning, they drift afterward. A quarterly hour spent reading six screens is what keeps the schedule the plant trusts on day 400 the same one it trusted on day 1. For the full administrator reference behind every check here, read the EDGEBIC admin guide, and for the discipline underneath all of it, what production scheduling is meant to deliver.