Offstandard Functionality: Detailed Explanation of Changes (Updated)

This document outlines the changes implemented to manage and account for "offstandard" work within the system, ensuring that portions of work time and Standard Allowed Minutes (SAM) can be accurately attributed to "on-standard" activities. This is primarily achieved through the introduction of new percentage fields and corresponding logic adjustments across various system components.

1. Table Changes and Configuration

New fields have been introduced to define how offstandard work contributes to on-standard metrics, with configurable defaults:

Offstandards Table (% Fields):

New % field for Work Time: A percentage field on offstandards will determine the portion of work time that should be considered "on-standard." If this field is left null, it will default to 0%.

New % field for SAM: A separate percentage field on offstandards will specify the percentage of SAM that should be attributed to "on-standard" work. If null, this will also default to 0%.

Transactions in Offstandard (% Fields):

New % field for Work Time (on-std): A new percentage field on individual transactions in offstandard will specify how much of the work time for that specific transaction is "on-standard." This field will default to 0% if null.

New % field for SAM (on-std): Another new percentage field on transactions in offstandard will indicate how much of the SAM for that specific transaction is "on-standard." This field will also default to 0% if null.

Manage - Offstandards Configuration:

Configuration options for these new percentage fields will be added under the "Manage - Offstandards" section, allowing administrators to define default values and manage their application.

2. Real-Time Operations and Modifications

The system's real-time processing and modification capabilities will be updated to correctly apply and manage these new percentages, including a specific mechanism for SAM transfer:

SAM Transfer Mechanism:

Current State: For the type of manufacturing being performed, all earned SAMs from offstandard activities are currently transferred to "on-standard."

Transaction Split for Transfer: To facilitate this transfer, two distinct transactions are required for each offstandard record that includes an on-standard SAM component:

Transaction 1 (SAM-focused): This transaction will contain the earned SAMs that are transferred to on-standard, but it will have no corresponding cycle time.

Transaction 2 (Cycle Time-focused): This transaction will contain the cycle time associated with the offstandard activity and its corresponding cycle time, with the SAMs either remaining off-standard or being set to zero if already transferred by Transaction 1.

Transaction Creation: When new transactions are created in an "offstandard" status, the configured percentages for on-standard work time and SAM (from the offstandard definition) should be automatically applied, factoring in the SAM transfer mechanism described above.

Aggregates Update: Aggregated data for users and locations must be updated to respect and reflect these new percentages and the SAM transfer, accurately distinguishing between on-standard and off-standard contributions.

Modifying to On-standard: If an offstandard transaction is modified or moved back to an "on-standard" status, the newly introduced percentage fields (for work time and SAM) for that transaction should be automatically reset to 0% or removed, indicating full on-standard attribution.

Temporary Offstandard Approvals/Unapprovals: The approval and unapproval processes for temporary offstandard states will need to correctly trigger updates to related calculations and aggregations based on the applied percentages and SAM transfer.

3. Job Changes

Key background jobs responsible for data processing and payroll preparation will be modified to handle the new on-standard/off-standard distinctions:

PayDaily Job: This job will be updated to ensure that any on-standard portion of hours, SAM, and piece rate originating from offstandard activities is correctly transferred to a dedicated "on-standard pay record" for accurate compensation calculation. This will specifically account for the SAM transfer via the two-transaction mechanism.

UserDaily Job: For user-level daily aggregates, the on-standard portion of hours and SAM from offstandard work must be separated. This means HoursOff and SAMOff will reflect only the pure offstandard portion, while new fields (HoursOn, SAMOn) will capture the on-standard portion derived from offstandard activities, correctly reflecting the SAM transfer.

ProductDaily Job: Similarly, at the product level, the on-standard portion of hours and SAM from offstandard work must be separated. CycleTimeOff and SAMOff will hold the pure offstandard values, while new fields (CycleTimeOn, SAMOn) will record the on-standard contribution, accounting for the SAM transfer.

4. Back-End Services and Screens

All screens and back-end services that perform efficiency or work time calculations based on transactions must be updated:

Live Production and KPIs: Any calculations displayed under "Live Production" and "KPIs" that currently use transaction data will need to respect the percentage of time and SAM transferred from offstandard activities to on-standard, including the specific SAM transfer mechanism. This will impact several data points in these areas.

5. Reports

Reporting functionalities will be updated to accurately reflect the new on-standard/off-standard attribution:

Efficiency and Work Time Reports: Any report that calculates efficiency or work time based on transactions must be modified to respect the percentages of work time and SAM that are transferred from offstandard to on-standard, correctly integrating the SAM transfer via the two-transaction method. This change will affect multiple data points within these reports, ensuring consistent and accurate reporting across the system.

Created with the Personal Edition of HelpNDoc: Full-featured Help generator