The Personnel Rules feature supports the establishment of rules that govern the scheduling of labor resources. These practices range from informal procedures to legally binding collective bargaining agreements (e.g., union rules) or governmentally prescribed working directives.
Specific "rules" are defined as Windows Workflow Activities and are then linked to rule CATEGORIES. (At this time no standard rules have been defined, but ones can be custom programmed to defined rules parameters that cater to your scheduling needs.) RULES SETS are associated with labor scheduling resource records, and the rule categories linked to each rule set defines the personnel rules for resources.
The PERSONNEL RULES VIOLATIONS SEARCH LIST WINDOW allows you to see which resources are in violation of their assigned rules. You can check for rule violations from multiple applications and search list windows via the Check Personnel Rules Actions Button commands. If a violation is found, the system will open the Personnel Rules Violations Search List Window with the relevant details displaying.
Order and quick hold bookings may have rule violations checked automatically when bookings are added with or changed to particular transaction phases based on whether the Auto Check Personnel Rules Field has been checked on the PHASES SETUP WINDOW; and violations may also be checked automatically when adding a roster transaction to a resource based on whether the Auto Check Personnel Rules on Roster Add Field has been checked on the PREFERENCES – SCHEDULING WINDOW.
REQUIREMENTS / PREREQUISITES
} MediaPulse v5.1+, MediaPulse API, and MediaPulse Service Engine (MPSE) have been installed and licenses have been issued (as appropriate).
} The MPSE is already correctly configured to connect to the MediaPulse API.
} Microsoft Message Queuing is installed and configured on the server.
} Windows Workflow Activities have been created customized to create the personnel rules you need and you have familiarity with the custom personnel rules being checked by the workflow.
} Understanding of what the MPSE is and how it works.
} Understanding of what the MediaPulse EVENT TRIGGERS feature is and how it works.
} The MediaPulse configuration file must be updated for use with Microsoft Message Queuing.
} The MediaPulse Message Queue must be established.
} The MPSE must be configured for routing and handling personnel rules.
} Roster transactions should be configured for all scheduling resources to whom the Personnel Rules feature applies. Additionally, the Personnel Rules Area on the IDENTIFICATION TAB PAGE of the Scheduling Resource Maintenance Application should also be completed for such resources.
MEDIAPULSE SET UP
1. Links to the Windows Workflow Activities that define each personnel rule must be established in the PERSONNEL RULES CATEGORY WINDOW.
Each category can link to a Windows Workflow Activity by entering the proper tag in the Activity Field.
2. Collections of rules must be set up in the PERSONNEL RULES SETS WINDOW as well as establishing the timeframe the rules are in effect for each collection.
Establish the name of the collection and the timeframe the collection’s rules are in effect on the RULES SETS TAB PAGE, and then add one or more personnel rules categories to the CATEGORIES TAB PAGE to define the specific rules that scheduling resources that have been assigned to the collection will be governed by.
3. A personnel rule set must be assigned to each labor-type SCHEDULING RESOURCE (i.e., the Labor Field is checked) that you want to be included in the Check Personnel Rules functionality.
In addition to assigning a personnel rule set, you can establish values that support the rules set with regards to minimum and maximum times allowed to be worked on a daily, weekly, monthly, and/or yearly basis, and any entitlements that the resource is due.
4. Custom EVENT TRIGGERS can be set up as needed by your Personnel Rules workflows.
5. Activate the Auto Check Personnel Rules Field on the PHASES SETUP WINDOW for select phases as needed.
Use of the Auto Check Personnel Rules feature should be limited to only those phases where it is essential to the business workflow to receive automatic warning messages. Otherwise, the manual, user-initiated check should be utilized for most scenarios. (Refer to the Auto Check Personnel Rules Field definition on the DETAIL TAB PAGE topic of the Phases Window for details.)
6. Activate the Auto Check Personnel Rules on Roster Add Field on the PREFERENCES – SCHEDULING WINDOW if desired.
CHECK PERSONNEL RULES FUNCTIONALITY
The underlying application logic that checks for the presence of personnel rules violations runs asynchronously – meaning once the Check Personnel Rules function has been initiated (manually or automatically) – the system will run the appropriate workflows and activities in the background. The specific rules to be checked are determined based on the personnel rules set and categories associated with each scheduling resource in the selected records. The results of each check are stored in the MediaPulse database and can be viewed in the PERSONNEL RULES VIOLATIONS SEARCH LIST WINDOW. As this data is stored, subsequent queries and reports can be run for analysis purposes.
When a check is initiated for personnel rules violations, the following applies:
} If the Check Personnel Rules function is manually initiated (via one of the Check Personnel Rules Actions Button commands) and violations are found, the system will open the PERSONNEL RULES VIOLATIONS SEARCH LIST WINDOW; the window will be prefiltered by the request context (e.g., a particular resource / date range, a particular order, a particular quick hold).
} If the Check Personnel Rules function is automatically initiated and one or more violations are identified, the context of the request will cause an ALERT message to be presented with the relevant details and links so that you may review or edit any relevant records. If you elect to open the PERSONNEL RULES VIOLATIONS SEARCH LIST WINDOW from the alert, the window will be prefiltered by the request context (e.g., a particular resource / date range, a particular order, a particular quick hold).
} If the Check Personnel Rules function is automatically / manually initiated, and no violations are identified, the system will not issue an alert message / open the Personnel Rules Violations Search List Window.
} If you alter the criteria in the PERSONNEL RULES VIOLATIONS SEARCH LIST WINDOW and a new search is initiated, the window will update to match the latest request.
MEDIAPULSE BUSINESS LOGIC GOVERNING PERSONNEL RULES
} In order to establish a reliable baseline for all the calculation of personnel rules violations, it is strongly recommended that roster transactions are created to define all scheduled time on and off for each scheduling resource for each calendar day. If roster on and off time does not exist for a particular span of time, these days will not be considered in the calculation of days off or days worked. For example, weekend days are normally not worked; however, if “SDO” (scheduled day off) roster transactions have not been established for a resource’s weekends, these days are effectively invisible to the Personnel Rules business logic.
} For the purpose of rule execution, a “day” is considered to start at 12:00 a.m. (00:00) and end at 11:59 p.m. (23:59).
} When checking any personnel rule, only the start date and time of a roster, quick hold, or order transaction is considered.
} The creation or modification of an order record (Work Order, Media Order, or Transmission Order) from another module (e.g., from the Purchase Order Maintenance Application) will call the same personnel rule application logic and return the same results as when creating or modifying such orders from their primary maintenance applications.
} The personnel rule application logic does not apply when cancelling or voiding an order record (Work Order, Media Order, or Transmission Order) or when deleting a roster, quick hold, or order transaction.
} A scheduling resource has “on” time when at least one roster transaction that has been assigned an OFF TYPE with a Purpose Field value of Roster Day On or Other Time On has been assigned to the resource for a given day. Additionally, “on” hours are calculated when a resource has been assigned to an order transaction or quick hold booking.
} A scheduling resource has “SDO” (scheduled day off) time when at least one roster transaction that has been assigned an OFF TYPE with a Purpose Field value of Roster Day Off, Other Time Off, or Vacation has been assigned to the resource for a given day.