Company Settings

What is Company Settings?

Company Settings contains system-wide defaults and preferences that apply to all users.

Access: Settings → Company

Who Can Edit: Managers, Executives, IT Admins

Start of Day and Timezone

Access: Settings → Company → Details

Start of day is the time your facility’s working day begins. This is one of the most impactful settings in MachineMetrics — it controls the First Active Time displayed throughout the application, including on machine cards, dashboards, and reports.

Important: The First Active Time shown on machine cards and dashboards is calculated from your Start of Day setting. If your Start of Day is set to 6:00 AM, the First Active Time for any given day will be the first moment a machine was active on or after 6:00 AM. Changing this setting will shift when “today” begins across the entire app.

MachineMetrics uses Start of Day as the boundary for all calendar-style periods — not midnight in your timezone.

Reports and historical metrics: Date ranges follow start of day → start of day. For example, if Start of day is 6:00 AM, a report for yesterday includes data from 6:00 AM yesterday through 6:00 AM today. Choosing last week or similar periods uses the same rule: each “day” in the range is your configured working day, not 12:00 AM–11:59 PM.

Live reporting: Views such as OEE and utilization for the current period also roll up from start of day forward, so intraday numbers match how your shop defines “today.”

Timezone: Set the timezone that matches your facility (e.g., America/New_York). Start-of-day boundaries and timestamps are interpreted in this timezone.

note

Start of Day and Timezone are configured by MachineMetrics — customers do not have access to change them. Although these values are visible under Settings → Company → Details, they are not customer-editable. To request a change to either setting, contact your Solution Delivery Manager (SDM).

Default Dashboard View

Purpose: Set which dashboard users see when logging in or navigating to dashboards.

Options:

• Utilization: Current Shift Dashboard with Utilization view
• Parts Goal: Current Shift Dashboard with Parts Goal view
• Downtime: Current Shift Dashboard with Downtime view
• OEE: Current Shift Dashboard with OEE view

Configuration: Select default view from dropdown and click Save.

Display Settings

Display "Waiting for Work":

• Enabled: Show "Waiting for Work" status when machine has no assigned operation
• Disabled: Hide this status

Display "Unknown Job":

• Enabled: Show "Unknown Job" when machine is running without assigned operation in MachineMetrics
• Disabled: Hide this status

Use Case: If you don't use Operations/APM, disable "Unknown Job" to reduce clutter.

Allow Operators to Override Job Start/End Times

Purpose: Let operators adjust job timestamps when starting/stopping operations on tablets.

Options:

• Enabled: Operators can backdate job start time (e.g., "I actually started 10 minutes ago")
• Disabled: Job timestamps always use current time

Configuration: Toggle on/off

Use Case: Enable if operators frequently forget to start operations on time. Disable to enforce strict timestamping.

Custom Job Name Display

Access: Settings → Company → System → Custom Job Name Display (Optional)

Purpose: Control how job and operation names are shown across MachineMetrics. You write a format using placeholders (tokens in curly braces), and MachineMetrics fills each one with the job's data. Any other text you type, such as Part:, OP, - or /, appears exactly as entered.

Where it applies:

• Machine list, machine timeline and production runs
• Production Schedule
• Production Analytics
• Scheduled time entries
• Notifications and webhooks (the operationName field in webhook payloads)

Available Tokens

Token	Aliases	Shows
{name}	{job}, {workorder}	The job/operation name
{part}		The part number
{operation}	{op}	The operation (sequence) number
{lot}		The lot
{description}		The job description
{wo}		The ERP work order ID for the run. If the run has no work order, it shows the part number instead, or the job name if there's no part.

Tokens are case-sensitive and must be lowercase ({part}, not {Part}).

note

{workorder} is an older alias for {name} and does not show the ERP work order ID. Use {wo} for the work order ID.

Unsupported tokens: Any token not in the table above (for example {sub}, {split} or a misspelling like {prt}) is removed from the name, along with one separator next to it (-, –, —, /, |, :, ;, , or .). For example, {name}-{sub} OP{op} displays as 12345 OP20.

note

{sub} and {split} are only filled in on the Operator View. Everywhere else they are removed as described above. When your format includes {sub} and a run is linked to an ERP work order operation that has a sub value, the work order ID in notifications and webhooks is sent as <work order>-<sub> (for example WO-1001-2).

Examples

Assume a job named 12345, part ABC-100, operation 20, lot L7 and ERP work order WO-1001:

Format	Displays as
{part} OP{operation}	ABC-100 OP20
{name} / {lot} : {part}	12345 / L7 : ABC-100
Name: {name}; Part: {part}; Op: {op}; Lot: {lot}	Name: 12345; Part: ABC-100; Op: 20; Lot: L7
{wo}-{op}	WO-1001-20 (or ABC-100-20 for a run with no work order)
{name}-{sub} OP{op}	12345 OP20 ({sub} is removed outside the Operator View)

When a Value Is Missing

How a token with no value is handled depends on where the name is shown:

• Most of the app (machine list, timeline, runs, notifications, webhooks): the token is left blank and the rest of the format is kept. For example, {part} Lot: {lot} on a job with no lot displays as ABC-100 Lot:.
• Production Schedule: if any token in your format has no value, the custom format is skipped and the schedule uses the first of these built-in formats that can be fully filled in: {part} Op {operation}, then {name} Op {operation}, then {part}, then {name}. On the Production Schedule, {name} is the ERP work order ID.
• Production Analytics: {lot} and {description} are not available and are removed like unsupported tokens. If none of the tokens has a value, the name falls back to {part} OP{operation}, or to the job name if there's no part.

tip

For the most consistent results, only use tokens your jobs always have values for. If some jobs don't have a lot, leave {lot} out of the format rather than ending up with a trailing Lot: label.

Leaving It Blank

The field is optional. If it's blank, or doesn't contain at least one supported token, MachineMetrics uses its default naming, which joins the name, part, operation and lot with | (for example 12345|ABC-100|20|L7). The Production Schedule uses its built-in formats listed above.

Configuration: Enter your format and click Save. The change takes effect immediately and also applies to existing jobs and runs, since names are generated when they're displayed rather than stored.

Cycle Time Entry

Purpose: Define how cycle time is entered in operation definitions.

Options:

• Single Part Duration: Enter time for one part (most common)
• Full Cycle Time Duration: Enter time for complete cycle (if multiple parts per cycle)
• Parts Per Hour: Enter production rate (e.g., 30 parts/hour)

Configuration: Select from dropdown

Impact: Affects how Expected Part Time is entered when creating operations.

Operator Tracking

Purpose: Enable/disable operator login functionality on tablets.

Options:

• Enabled: Operators can log in/out on tablets, operator performance tracked
• Disabled: No operator tracking

Configuration: Toggle on/off

See Also: Operators and ShopPulse Interface Guide

Ideal Cycle Time

Purpose: Define how ideal cycle time is handled for OEE Performance calculations.

Options:

• Automatic: MachineMetrics calculates ideal cycle time from historical data
• Manual: Enter ideal cycle time manually for each operation
• Disabled: No ideal cycle time used (Performance based on expected cycle time only)

Configuration: Select from dropdown

See Also: Understanding Your Data Guide

Ignore APM Archive Operations

Purpose: Control whether APM (Automatic Production Monitoring) auto-archives operations.

Options:

• Enabled: APM ignores archived operations (won't create new runs for archived ops)
• Disabled: APM can still create runs for archived operations

Configuration: Toggle on/off

Use Case: Enable to prevent APM from reactivating old operations when program numbers are reused.

Operator Verification

Purpose: Require operators to enter a 6-digit PIN when signing in on the tablet.

Access: Settings → Company Settings → Operator Verification

Default: Off

Configuration: Toggle on/off

Effect when enabled:

• Every operator sign-in on the tablet requires a PIN entry after choosing their name
• Operators without a PIN cannot sign in until an IT Admin generates one for them
• Applies to both MES and non-MES configurations — this is a plain Company Setting with no MES prerequisite

See also: Operator Dashboard — PIN Verification

ERP Job Tracking Settings

Job Tracking Method:

Purpose: Define who controls production run creation.

Options:

• Driven by MachineMetrics: Operators or APM create production runs in MachineMetrics
• Driven by ERP: External ERP system creates/manages production runs via API

Configuration: Select from dropdown

Use Case: If integrating with ERP (e.g., IQMS, E2, JobBOSS), set to "Driven by ERP".

Default Metric Goals

Purpose: Set company-wide performance thresholds for color-coded dashboards.

Configurable Goals:

1. Utilization Goals

• Goal (Green): % or above (e.g., 85%)
• Warning (Yellow): % threshold (e.g., 70%)
• Failure (Red): Below warning threshold

2. OEE Goals

• Goal (Green): % or above (e.g., 70%)
• Warning (Yellow): % threshold (e.g., 50%)
• Failure (Red): Below warning threshold

3. Parts Goal

• Goal (Green): % or above (e.g., 100% of expected)
• Warning (Yellow): % threshold (e.g., 85%)
• Failure (Red): Below warning threshold

Configuration:

1. Enter percentages for each threshold
2. Click Save

Impact: Determines Performance Wheel colors on ShopPulse Interface and dashboard tile colors.

Override: Machine-specific or operation-specific goals override company defaults.

Holidays

Purpose: Define company-wide non-production days where downtime is automatically categorized as planned downtime, so metrics like OEE and availability reflect only expected production time.

Access: Settings → Company → Holidays

Prerequisite: Enable Exclude Planned Downtime from Scheduled Time in Settings → Downtimes before configuring holidays. Without this setting, downtime will still be categorized with the selected reason, but Scheduled Time and related metrics will not be adjusted.

How holidays work:

• Apply to all machines across all machine schedules
• Span a full day based on your company's Start of Day setting
• Automatically categorize any idle time during the holiday with the selected downtime reason
• Recur annually on the configured date
• Apply from the date they are created forward — historical metrics are not affected

Note: Existing automatic downtime categorization rules covering the same time period are no longer required once a holiday is configured.

Impact on metrics:

Metric	Impact
Scheduled Time	Reduced by planned downtime during the holiday
Availability	Recalculated using reduced Scheduled Time
OEE	Recalculated (Availability component changes)
OOE	Recalculated
TEEP	Recalculated
Parts Goal	Recalculated using reduced Scheduled Time
Performance	No impact
Quality	No impact

Adding a Standard Holiday

1. Navigate to Settings → Company
2. Scroll to the Holidays section
3. Click Add
4. In the Holiday field, select from the list — defaults are based on your company's region; use the search bar to search all holidays. The date populates automatically.
5. Select a Downtime Category to classify idle time during this period
6. Click Save

Adding a Custom Holiday

1. Click Add, then in the Holiday search bar click + Custom holiday
2. Enter a unique Name
3. Select a Date — custom holidays recur on this date every year
4. Select a Downtime Category
5. Click Save

Editing or Removing a Holiday

Click the three-dot menu (⋮) next to a holiday and select Edit or Delete.

FAQ:

• Will holidays change historical metrics? No — holidays apply from the date they are created forward.
• What if a machine runs during a holiday? Production activity is recorded normally. Only downtime is automatically categorized.
• Can holidays differ by machine? No — holidays are company-wide.