Performance Standards

Performance standards tell Eclipse Pro how fast each machine is expected to run. They live under Settings → Performance Standards, with one row per machine and, underneath it, one row per tooling set up on that machine.

Each run speed (feet per minute) comes in two flavors:

Speed	What it is used for
Planning	The speed the schedule uses to estimate how long orders will take.
Target	The speed the plant is measured against. Target speeds are also saved back to Eclipse Classic.

The Historical column shows how fast the machine or tooling has actually run over the selected date range, so you can compare your standards against reality.

Machine defaults and tooling speeds

Every machine has a default plan and target speed. A tooling uses the machine default unless its Override box is checked, in which case it uses its own speeds.

Speeds can vary by part length. A speed list such as 60 ft/min at 0 in, 80 ft/min at 480 in means short parts run at 60, parts 480 in and longer run at 80, and parts in between get a speed proportionally between the two. The machine default target is the exception: Eclipse Classic stores a single target speed per machine, so it can't vary by length. Length-based targets are set on toolings.

---

Editing run speeds in a spreadsheet

When you have many toolings to update, or you calculate speeds elsewhere, you can edit run speeds in Excel (or any spreadsheet) and import them back. Always start from an export — it gives you every machine and tooling with the correct numbers and codes, so there is nothing to type from scratch.

1. On the Performance Standards page, choose Import/Export → Export run speeds. This downloads performance-standards-speeds.csv with the current plan and target speeds.
2. Open the file in Excel and make your changes. You can delete rows you don't want to touch and add your own calculation columns — anything the import doesn't recognize is ignored.
3. Save the file, keeping it in CSV format.
4. Choose Import/Export → Import run speeds and select the file.
5. Review the preview. Every machine and tooling that will change is listed with its current and new speeds. If the file has problems, they are listed by line number and nothing can be imported until they are fixed.
6. Click Import. The page refreshes with the new speeds.

The file format

Column	Required	Meaning
MachineNumber	Yes	The machine the row applies to.
ToolingCode	No	The tooling. Leave blank for the machine default.
LengthIn	No	Part length in inches where this speed starts. Blank means 0.
PlanFpm	One of these	Planning speed in feet per minute.
TargetFpm	One of these	Target speed in feet per minute.
Description	No	Machine or tooling description, for reference only. Ignored on import.

Column names aren't case-sensitive and spaces are ignored, so Machine Number and Plan FPM also work. Speeds are always feet per minute and lengths are always inches, regardless of the units selected in Eclipse Pro.

One speed per tooling — one row per tooling, leaving LengthIn blank:

MachineNumber,ToolingCode,LengthIn,PlanFpm,TargetFpm
1,PURLIN8,,90,110
1,PANEL,,120,140

Speeds that vary by length — one row per length for the same tooling:

MachineNumber,ToolingCode,LengthIn,PlanFpm,TargetFpm
1,PURLIN8,0,60,70
1,PURLIN8,240,80,95
1,PURLIN8,480,100,120

Machine default — leave ToolingCode blank. Plan speed can vary by length; give only one target speed:

MachineNumber,ToolingCode,LengthIn,PlanFpm,TargetFpm
2,,0,100,120
2,,300,110,

What the import changes

• Each machine or tooling in the file has its speeds replaced by the rows in the file. If a tooling had speeds at three lengths and the file gives one, it ends up with one.
• Machines and toolings not in the file are left alone. A file with a single tooling in it only changes that tooling.
• A column left blank on all of a tooling's rows is left alone. A file with only PlanFpm filled in updates plan speeds and keeps the existing target speeds.
• Importing speeds for a tooling turns on its Override, since otherwise the tooling would keep using the machine default. The preview marks these toolings with Turns on tooling speeds. Note that the tooling's other speed, the one the file left blank, also starts being used.
• Toolings that use the machine default are exported with blank speeds. Leave them blank to keep them on the machine default, or fill them in to give them their own speeds.
• An unedited export imports with no changes, so it is safe to re-import a file you only partly edited.

Before you import

• The Eclipse Agent must be running. Target speeds are saved to Eclipse Classic through the Agent. If it can't be reached, rows that change a target speed are reported as failed and left unchanged; rows that only change plan speeds are still imported.
• Numbers must use a period for decimals (92.5, not 92,5) and commas between columns. If Excel's regional settings use a comma for decimals, check the saved file before importing.
• Tooling must already be set up on the machine. The import updates speeds; it doesn't add toolings to machines.

Common problems

Message	What to do
Machine N was not found.	Check the machine number, and that the machine is licensed in Eclipse Pro.
Tooling X is not set up on machine N.	Check the code, or set the tooling up on that machine in Eclipse Classic first.
PlanFpm is given more than once for length L.	Each tooling can have only one row per length. Remove or merge the duplicate.
Machine N's default target speed can't vary by length.	Give the machine default a single TargetFpm, or set length-based targets on its toolings.
… must be a number greater than zero.	Speeds must be positive numbers. Leave the cell blank instead of entering 0.