Please visit our new TrackAbout Knowledge Base at https://supportkb.trackabout.com for the most-up-to-date documentation on TrackAbout and TrackAbout Mobile.
Difference between revisions of "Work Orders"
(→Sort) |
|||
| Line 124: | Line 124: | ||
There is a 'Priority' button displayed in scan assets screen. | There is a 'Priority' button displayed in scan assets screen. | ||
==Logging Time for Sorting== | ==Logging Time for Sorting== | ||
| + | |||
| + | Trackabout provides support to track the start and end times that a user is spending in the Sort for Filling action. Since Sort Assets is a single user action, the record start date and save date, combined with asset scan times will be enough for our reporting needs. However, since the Sort Container action can be paused any number of times and multiple users can sort at the same time, the record start date and save date alone are not necessarily an accurate representation of the amount of time it takes to sort the assets. | ||
| + | Instead, we track the user and start time when the user starts the sort action. When they either click the Pause or Close button, we would track the end time. We also store a "temporary" end time for the user of whatever they last did (scan asset, scan new container, etc.) in case they never click either of those buttons (battery dies, software crashes, etc). | ||
| + | This information is stored on the web server both for the Sort* tables and pushed into the record when a record is saved. It is cleared out if a container is restarted. | ||
| + | |||
| + | A new Start Time is recorded when Sort Container action is restarted after pausing. When the user scans an asset, the End Time is added in the ScanTimes DB table. That “End Time” gets updated every time the user scans an assets. This entry is updated even when an invalid asset is scanned. | ||
| + | |||
| + | |||
| + | '''NOTE:''' This modified Start Time is not logged for 'Sort Container-Maintenance' and 'Sort Container-Interbranch Transfer' actions | ||
=Fill= | =Fill= | ||
==Routing Steps== | ==Routing Steps== | ||
Revision as of 13:07, 24 October 2014
Summary
Work Orders
TrackAbout supports the following kind of information for Work Orders:
- New Order Type for Work Order
- Priority
- Parts Lists
- Product Code
- Unit of Measure
- Quantity
- Routing Steps
- Step
Here is a sample of the Work Orders webservice xml:
<pct:WorkOrders xmlns:pct="http://www.praxair.com/PCT/WorkOrderRequest"> <WorkOrder> <OrderNumber>WO00001</OrderNumber> <BranchLocation>PITT</BranchLocation> <PlannedFulfillmentDate>2013-03-30</PlannedFulfillmentDate> <Priority>12</Priority> <OrderCommentsToDisplay>These are comments</OrderCommentsToDisplay> <PurchaseOrderNumber>900099876</PurchaseOrderNumber> <OrderedBy>NEW SMYRNA BEACH</OrderedBy> <EnteredBy>Vonheeder, Robin L</EnteredBy> <OrderedDate>2013-03-21</OrderedDate> <WorkOrderItems> <WorkOrderItem> <LineNumber>1</LineNumber> <ProductCode>OXINDLF</ProductCode> <ProductCodeDescription>OXYGEN MEDICAL 15 SCF/CYL</ProductCodeDescription> <ProductCodeUnitOfMeasure>CYL</ProductCodeUnitOfMeasure> <ProductCodeLotNumberRequired>true</ProductCodeLotNumberRequired> <OwnerFlag>PX</OwnerFlag> <OrderQuantity>1</OrderQuantity> <ProductCodeUNHazardIdentifier>2.2</ProductCodeUNHazardIdentifier> <ProductCodeUNNumber>UN1072</ProductCodeUNNumber> <Components> <Component> <SeqNum>1</SeqNum> <Description>Carbon Dioxide</Description> <ComponentCode>C02</ComponentCode> </Component> </Components> </WorkOrderItem> </WorkOrderItems> <RoutingSteps> <RoutingStep> <Sequence>1</Sequence> <Description>Inspection</Description> <Status>Completed</Status> </RoutingStep> <RoutingStep> <Sequence>2</Sequence> <Description>Filling</Description> <Status>Open</Status> </RoutingStep> </RoutingSteps> </WorkOrder> </pct:WorkOrders>
The addition of Work Order information should not affect the existing orders table, since it will still be used for Delivery Orders. Note: Work orders themselves cannot be edited from the TrackAbout website.
Sort
During the sort actions (Sort Container and Sort Assets), the user can see the current Work Orders for their location listed by priority. The operator will not be selecting and assigning containers/cylinders to work orders at this point, but will be able to see what should be prioritized.
TrackAbout can accept updates from client's accounting system as work orders are fulfilled and added, so the prioritization screen is accurate.
During sort, the user can click a button to see a list of work orders. These are filterable by Product Code, and display the following information:
- Priority
- Work Order
- Empty Cylinder Type (Product Code)
- Quantity
The user can also see this screen during sort container after they scan a pallet and select Filling as it's use. When the screen is shown, the data is be pulled dynamically from the web server, so we are always showing fresh data.
The user can select the Work Orders to work based on the product code. The grid is empty by default and once the product code is selected from the dropdown, the corresponding work orders are displayed.
NOTE: The Prioritization screen and Priority button are not displayed for a Location that do not have any Work Orders assigned to it. In this same scenario, the 'Sort Container-Filling' action also doesn’t display a 'Priority' button in the asset scan screen.
Parts List
On the Priority screen, once a product is selected, the available work orders will display. The display sequence of work orders will be by priority and then by start date. The operator will be able to tap on a work order and see the associated parts list.
The following information will be displayed:
- Product Code
- Product Code Description
- Unit of Measure
- Quantity
Handheld steps:
- Select the 'Sort Container' action
- Scan a container
- Select 'Filling' button
- Verify that user is taken to 'Prioritization' screen
- Verify that there are some work orders displayed
- Select a work order from the list
- User is taken to the 'Work Order Parts List' screen which displays various work order details
From the parts list screen, they can jump to the routing steps screen to review the routing steps.
NOTE: The parts list and routing screens are display only, no entry or update of information is allowed.
Routing Steps
There is a 'Routing Steps' button present on the Work Order Parts List screen. The screen should display the steps for the work order, indicating which is complete and which is not. This button will only appear when there are actual Routing Steps associated with the Work Order.
The user will see information such as:
- Sorting Completed
- Filling Open
Click on 'Done' button. The user will be taken back to the 'Work Order Parts List' screen. Click on 'Done' again on 'Work order Parts List' screen to be taken to the Prioritization screen.
Finish Sorting
Click 'Continue' in the 'Prioritization' screen to display the 'Scan assets' screen. There is a 'Priority' button displayed in scan assets screen.
Logging Time for Sorting
Trackabout provides support to track the start and end times that a user is spending in the Sort for Filling action. Since Sort Assets is a single user action, the record start date and save date, combined with asset scan times will be enough for our reporting needs. However, since the Sort Container action can be paused any number of times and multiple users can sort at the same time, the record start date and save date alone are not necessarily an accurate representation of the amount of time it takes to sort the assets. Instead, we track the user and start time when the user starts the sort action. When they either click the Pause or Close button, we would track the end time. We also store a "temporary" end time for the user of whatever they last did (scan asset, scan new container, etc.) in case they never click either of those buttons (battery dies, software crashes, etc). This information is stored on the web server both for the Sort* tables and pushed into the record when a record is saved. It is cleared out if a container is restarted.
A new Start Time is recorded when Sort Container action is restarted after pausing. When the user scans an asset, the End Time is added in the ScanTimes DB table. That “End Time” gets updated every time the user scans an assets. This entry is updated even when an invalid asset is scanned.
NOTE: This modified Start Time is not logged for 'Sort Container-Maintenance' and 'Sort Container-Interbranch Transfer' actions