11/20/2022 0 Comments Wmt scheduler faa![]() ![]() This is for any planned or unplanned WMT outage. ![]() * A printed OT (hard copy) list must available in the area after the latest assignment of OT. * All employees need to make sure their contact information is correct in WMT. * We've reset the hours based on the lowest number of opportunities in each area, and counted up to the most opportunities. Example: Day 6 of the workweek should be a day/mid and day 7 would be a swing shift. * When scheduling multiple overtime shifts, if possible, the integrity of descending shift assignments for the workweek should be maintained. #Wmt scheduler faa full#The rationale there is that generally when call ins are made, its usually within 24 hours of the shift and there are some people who would rather be here for the full 8 because of commute or whatnot. Call in OT for the non-volunteer list, employees will have to make their own request for their RDO, but will still get priority. Non-volunteers will have an "auto-request" for an RDO if scheduled prior to publishing. * Non-volunteers will have priority to be excused over all other pending requests. * Swapping OT shifts will not count as extra opportunities on the published schedule. including holdover OT and Saturday night mid briefing. Another benefit of using WMT is that it will make it more transparent to all BUE's on how OT is being used. By going to the WMT scheduler we will still have the same philosophy, except when it goes into effect, we will be tracking all OT by minutes and hours. We discussed this as a board and decided that it would be simpler to track overtime with WMT scheduler. Along the way we did have some inadvertent skips that were in result of how the spreadsheet was used. The spreadsheet that they are using can be convoluted and not all the FLM's were on the same page when using it. ![]() In addition, three panel sessions have been organizcd.Last month management approached NATCA to discuss looking at other options for tracking Overtime. All paper sessions ended with a 30 minute discussion period on the topics covered by the session. As a Working Conference, the program was designed to promote the exchange of ideas by extensive discussions. The selection process was greatly facilitated by the diligent work of the program committee members, for which we are most grateful. The resulting program represents a broad spectrum of interests, with papers from universities, corporations and government agencies in eight countries. The Program Committee selected 21 papers for presentation from a total of 95 submissions at a September meeting in Menlo Park, California. Because of its broad scope, a main goal was to contribute to a unified understanding and integration of these concepts. In keeping with the previous three conferences held in August 1989 at Santa Barbara (USA), in February 1991 at Tucson (USA), and in September 1992 at Mondello (Italy), the conference was concerned with an important basic question: can we rely on computer systems for critical applications? This conference, like its predecessors, addressed various aspects of dependability, a broad term defined as the degree of trust that may justifiably be placed in a system's reliability, availability, safety, security and performance. This volume contains the articles presented at the Fourth InternationallFIP Working Conference on Dependable Computing for Critical Applications held in San Diego, California, on January 4-6, 1994. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |