EDGEBIC + Statii: The Complete Scheduling Integration Guide

Integrating Statii with EDGEBIC means exporting the parts, work centers, operations, and open jobs Statii already holds to CSV or Excel, mapping those columns once with a reusable import mask, and letting EDGEBIC schedule the work against finite capacity: real shift hours, real machine counts, and sequence-dependent setups. Executable dates then go back as Excel. There is no API project, nothing installed inside Statii, and no certified connector to version-match when either side updates.

EDGEBIC by User Solutions is the newest generation of a scheduling line that has integrated with ERPs this way since 1991. Across 35+ years the same file-based approach has fed schedules for the US Navy, GE, BAE Systems, and Cummins. This guide covers the Statii case, aimed at the small and mid-size manufacturers Statii serves.

Why a small-shop system still needs finite capacity scheduling

Statii runs the small-shop business record well: quotes, jobs, purchasing, and the operation tracking that follows work through the floor. What most Statii shops report is that the daily sequencing decision still happens in a spreadsheet, because the morning questions are finite capacity questions:

• Which of these open jobs actually fit on the two machines this week?
• If this rush job jumps the queue, which promise dates move and by how much?
• Is that one bottleneck machine loaded to 80 percent or 160 percent next Thursday?

Those require modeling shifts, machine instances, changeover sequences, and operator availability against every open job at once. It is a different computational problem from recording transactions, which is why a dedicated finite capacity layer beside the system is the standard pattern, and it is exactly the decision a small shop has the least spare time to get right by hand. The general case is in finite versus infinite capacity scheduling.

The integration in one table

The EDGEBIC ERP integration architecture is identical for every system, Statii included:

An import mask is a saved recipe that remembers the data type, the file format, whether the first row is headings, whether text values are quoted, and how each column maps onto an EDGEBIC field. You build it once by dragging column headings onto target fields, and every run after that is two clicks. Each row returns Created, Updated, Reused, or Failed, with a per-run log recording every one.

Step 1: the four exports

Any Statii list or report that saves to CSV is a valid source.

1. Parts. Identifier, description, unit of measure, and any cost or lead-time columns worth keeping visible. The identifier is the natural key, matched case-insensitively.
2. Work centers. Identifier, machine count, default setup hours, efficiency, and an hourly rate. A bottleneck flag rides along.
3. Operations. One row per operation: end part, work center, sequence number, hours per unit, setup time, queue time.
4. Open jobs. Part, quantity, job reference, and due dates.

Step 2: map the columns once

Name each mask after the routine, so Weekly Statii Jobs outlives jobs-week29.csv. Mandatory fields are flagged and the run refuses to start until they are mapped. Unit conversion applies a factor to a numeric column before storage, so minutes become hours with 0.016667. Blank-cell preservation keeps an existing value when a cell is blank on an update run, with a zero counting as a value rather than a blank.

Step 3: the operation import, and why it takes two passes

Operations reference each other, step 10 feeds step 20 feeds step 30, so a row-by-row import cannot wire the links because step 20 does not exist when step 10 is written. EDGEBIC's routing import runs in two passes: pass one validates and buffers every row and auto-creates any missing work center or part, and pass two groups the rows by end part, sorts by sequence, writes them, and wires the chain so the routing renders as one connected flow in the graphical routing designer. Number sequences in gaps of 10, and keep all of one part's operations in one file so re-imports stay idempotent.

Step 4: jobs in, then run the scheduler

The job import maps part, quantity, reference, and due date. Imports never schedule anything: imported jobs sit as unscheduled demand until you run the scheduler, which states how many jobs are new and how many are being rescheduled before it plans. Once the data is in, the full engine applies: finite capacity across multiple shifts and machine instances, work center groups, a sequence-dependent setup matrix, lot streaming, operator skills, and mathematical optimization with a proven optimality gap. The EDGEBIC product overview maps the engine.

Step 5: sending dates back

The return trip is Excel. The Job View grid exports the schedule as a workbook with colored cells and a legend, the work center schedule exports the same way, and every report exports to Excel or PDF using your saved layout. Revised dates go back into Statii through your normal job maintenance path. There is no automated write-back, which keeps your data under your control.

Test it with your own export

Export this week's open jobs and an operations file, then bring them to a demo. Mapping them live takes minutes. If you are comparing systems, the MRPeasy and Katana versions follow the same method, which is the point of a universal import layer.