Exibir origem

Adding SO Schedule

Confirm schedule data and system displays screen to add SO schedule divided in areas to better organize information:

Area 1: Parameters

Parameters for the selection of service orders to be schedule. It enables the filtering per Asset, Maintenance Team, Cost Center and Estimated Start Date, Status, Work Center, Asset Family, Maintenance Type, Maintenance Area, Service, Service Order, Maintenance Plan. It also enables to choose whether it considers Lubrication SO and per Location.

Area 2: Orders available for schedule

Service Orders selected from the parameters established by user, that is, they are the SO available to be scheduled.

This list has the following columns: Selected (Yes or No), Situation (Caption), Status (Caption), Order, Asset, Asset Description, Code and Service Description, Schedule Date, Estimated Date, Priority and Status Code.

Subtitle (Status):

Linha Microsiga Protheus - Inglês > Adding SO Schedule-mnta990_inclusao_os.htm > br_azul.png SO Released in Current Schedule

SO change status after selected for next grid and selected Release.

Linha Microsiga Protheus - Inglês > Adding SO Schedule-mnta990_inclusao_os.htm > br_cinza.png SO Released with Inputs Accomplished

SO has this status when it is released and inputs are reported in SO Return and it is not finished.

Linha Microsiga Protheus - Inglês > Adding SO Schedule-mnta990_inclusao_os.htm > br_verde.png SO Released without Inputs Accomplished

SO has this status when it is released and inputs are not reported in SO Return and it is not finished.

Linha Microsiga Protheus - Inglês > Adding SO Schedule-mnta990_inclusao_os.htm > br_laranja.png Pending SO

SO has this status when it is pending.

Options:

•	Change Date: changes foreseen date to start SO. Changes are only saved when register of SO Schedule is confirmed.

•	View SO: displays register of SO selected.

Area 3: Orders selected to be performed

SO selected for schedule that were transferred from list of Area 2. After transfer for this screen they must be released inRelease.

Options:

•	Release: used to release SO to be performed. You can release one or all SO in Area 3. SO released in schedule contains .

•	Print SO: prints SO report.

•	View SO: displays register of SO selected.

•	Generate WR: generates warehouse request of products foreseen for SO selected for Schedule (Area 3).

•	Print Schedule: allows Schedule report with SO scheduled and uses of labor force resources.

•	Labor: displays specialties required to perform SO with quantity of resources to perform task and quantity of hours foreseen. Displays possibility to partially program SO and changes fields Hours Scheduled.

Area 4: Maintenance Calendar

Calendar of month selected is displayed and indicates each day if labor force is enough to perform service orders or if there is service order foreseen for day.

Example:

On May 2 and 5, 2008 have SO in which labor force is enough to accomplish maintenances. On 1 and 30, labor force available is not enough and in other days they do not have SO scheduled.

Actions:

•	Change Day: Select day in calendar and system displays question Do you want to filter Service Orders of _/_/_ only?

•	Change Month: click < or > to update calendar with month selected and check if labor force is enough or not or does not have SO for each day.

•	Change Year: click << or >> in navigation bar and system updates calendar with month/year selected and checks if labor force is enough or not or does not have SO for each day.

Area 5: Resources to Schedule SO.

Specialty: Specialists needed to perform the service orders

All the specialties available are displayed in the schedule period.

Indicates for each specialty: quantity of technicians, time scheduled (total of hours in SO scheduled), time available, % used of each specialty in schedule in addition to columns Technicians/Additional Days and Technicians/Absent Days.

Example:

Forty hours of Tire Fitter specialty. Add 1 technician in 1 day and my specialty of Tire Fitter increases to 56 hours (40 + 16 additional hours).

Filling out field Technicians/Absent Days is inverse operation, it means if you enter 1 technician and 2 absent days, my availability decreases to 24 hours (40 – 16 hours).

Product: Products required to perform service orders.

Products are organized according to field Order (code of Service Order) which contains information below: Product Code and Description, Quantity required in SO, Quantity of product in stock, Number of Purchase Request, Date Foreseen of purchase and Number of Warehouse Request.

Tool: Tools required to perform service orders.

Tools are organized according to field Order (code of Service Order) which contains information below: Tool code and description and Quantity of tool required in service order.

Labor: Labor needed to perform the service orders.

Labor is organized by field Registration (Employee Registration) that also has the following information: Employee name, Specialty, Scheduled Time, Available Time and % Used.

•	Scheduled Time is the sum of the selected employee hours that are necessary to perform the scheduled service orders.

•	Available Time is the time the employee is working, according to calendar in the schedule total period.

•	% Used represents the percentage used in labor according to time available.

Options:

•	Print Inputs: report with information in Labor force, Product and Tool screen.

•	View PR: opens window to view Purchase Request when product selected has PR related.

•	Print WR: displays report with products to perform service orders as far as it has WR related.

•

Detail Labor force: displays all service orders scheduled that need specialty selected and enables you to change fields Technicians/Additional Days and Technicians/Absent Days. The editing of the columns Technicians/Additional Days and Technicians/Absent Days automatically reflects in the Available Time of the specialty, but this editing is a simulation to help the planner to analyse how many specialists are necessary to be hired to answer the maintenance area needs and for how long as well. This simulation is not saved.

Area 6: Moving Service Orders

Add all SO in schedule

Linha Microsiga Protheus - Inglês > Adding SO Schedule-mnta990_inclusao_os.htm > avancar.png - Transfers all service orders available (area 2) to list of service orders selected to perform it in (area 3).

Add only SO selected in schedule

Linha Microsiga Protheus - Inglês > Adding SO Schedule-mnta990_inclusao_os.htm > avancar.png - Transfers only service orders selected (area 2) to list of service orders selected to perform it in (area 3).

Delete only SO selected in schedule

Linha Microsiga Protheus - Inglês > Adding SO Schedule-mnta990_inclusao_os.htm > voltar2.png - Transfers only service orders selected (area 3) to list of service orders selected (area 2).

Delete all SO in schedule

Linha Microsiga Protheus - Inglês > Adding SO Schedule-mnta990_inclusao_os.htm > vernota.png - Transfers all service orders selected to perform (area 3) to list of service orders available (area 2).

Area 7: Options

Linha Microsiga Protheus - Inglês > Adding SO Schedule-mnta990_inclusao_os.htm > s4wb059n.png - Allows you to view and change header information of Service Order Schedule (schedule data).

Linha Microsiga Protheus - Inglês > Adding SO Schedule-mnta990_inclusao_os.htm > bmppost.png - Displays subtitles.

Area 8: Locate and Organize Service Orders

Contains fields Organize SO by and Locate SO.

Warning Workflow in the Service Order Release

This functionality aims at warning the person in charge about the release of a Service Order. The workflow is sent for the people in charge of the Workshop (TSK_PROCES = 1 or 6) process according to what is defined in the Branch routine (MNTA855).

Linha Microsiga Protheus - Inglês > Adding SO Schedule-mnta990_inclusao_os.htm > help_button.zoom40.gif Note:

The file MNTW215.HTM must be added in the folder according to parameter MV_WFDIR.