Templates provide the ability to define rules and assign attributes (data to capture) for various parts of the system. Templates need to be set up to support the setup of other records in the system. Templates are required for:
- Items. Item templates are setup and then Item Masters created. Every item unit in the system is tracked by an item master.
- Containers. Movable container setup is the merge of a template and master. Define different types of movable containers, the rules, and the data to capture.
- Locations. This includes internal facilities, areas, customer, and vendor addresses.
- Shipments. If using the shipping functionality, shipment templates will be defined.
- Maintenance. If completing maintenance transactions in the system, maintenance templates will be defined.
- Projects. When using the projects/jobs infrastructure, project templates will be setup.
- Transport. Shipping functions will assign a carrier and the transport container (i.e., shipping method). Transport templates will be defined.
Item Templates
The first step of setting up item masters and being able to add and receive item units into the system requires the setup of the item templates. Templates can also be used to define categories of items. For an example of tool tracking, a template can be setup for different types of tools, such as ladders, drills, saws, etc. Templates define the rules of how the item is tracked and also the attributes that are captured for the unit.
Setup item templates under the settings (icon on the top menu bar) under Item Setup.
Item templates identify if the unit is tracked by a unique ID (serialized) or if the units will be tracked by a quantity. Rules available to assign will be based on what option is selected.
Enter the Template ID.
Enter a Description for the template (optional)
Select the Type: Serial or Quantity
Item Template Rule Overview
Under the Rule Assignment Tab, define the rules for this item template.
Items can be setup with these combinations:
- SERIAL TRACKED: ASSET RETURNABLE
- SERIAL TRACKED: INVENTORY
- QUANTITY TRACKED: ASSET RETURNABLE
- QUANTITY TRACKED: INVENTORY
- LOT TRACKED: INVENTORY
- NON-INVENTORY CONSUMABLE (is available to select as a consumable for Unit Maintenance only)
Based on the item configuration above, the following rules can be applied:
SERIAL TRACKED ITEM – RETURNABLE ASSET
| Track Place-In-Service | When enabled, units received will be set to a status of ‘Received’. Received status can be moved and transferred, but cannot be checked out or deployed unit placed-in-service which updates the status to ‘Available’. |
| Capture Unit Cost | For Receive New Unit and Create, the unit cost can be captured. The unit cost is stored against the serialized item unit. |
| Can be Assigned to a Group | The grouping features is used to support reporting a group of asset to a single ERP/Accounting Asset record. The Group ID represents the financial record ID. The individual assets are tracked in Panatracker. |
| Can be Checked Out | When enabled, items will the status of available can be checked out to assignees or customers. If the item is already checked out, it can be transferred or it can be checked in and then re-checked out as part of the check out step. Sub rules include the ability to track an expected return date. |
| Can be Deployed | Similar to check out, deployed units maintain a facility or customer address location. Typically stationary assets are deployed verus checked out as the physical location is obvious. |
| Track Ownership by Team | When enabled, ownership is tracked for the assets. Owners can be an internal team or can be a customer. Visibility to the assets is based on both custody and ownership. If not checked, there is no team ownership assigned and visibility will be available to all users based on custody. |
| Track Maintenance Activities | When checked, the unit can be selected to setup for scheduled maintenance or can be selected to record unplanned maintenance activities. Reporting is available to view all maintenance details for items setup to track maintenance. |
| Track as a Master Item for Build Unit | When enabled, the asset is treated as a parent unit and components can be assigned to the asset. Components may be returnable or can be consumables. There is the ability for unlimited nesting; therefore, a parent (master) unit can also be a component (child) unit. |
| Enable as a Component Item for Master Item | When enabled, the asset can be selected as part of a unit build. Assets that are part of a build retain the status of ‘In Build’ until removed. |
| Track Retirement Date and Disposal | When enabled, assets can be assigned a retirement date (often relating to financial reporting). When the asset is disposed, it is no longer actively tracked in the system. There is a grid view to access all disposed assets. |
| Enable Status Change on Update Unit transaction | The Update Unit transaction tends to be a generic transaction to support changes to status or capturing or changing unit attribute data. When enabled, the status is enabled to support status changes. For example, a unit may be updated from available to out-of-service if it is being sent to maintenance. |
| Track as Rental TO Customers | When enabled, the item master can be assigned a billing schedule. Billing is then calculated against assets checked out to a project associated with a customer. |
| Track as a Rental FROM Vendors | When enabled, the item master can be assigned a billing schedule. Billing is then calculated against assets from a vendor. |
Serial-Tracked: Inventory
| Capture Unit Cost | For Receive New Unit and Create, the unit cost can be captured. The unit cost is stored against the serialized item unit. |
| Can be Checked Out | When enabled, items will the status of available can be checked out to assignees or customers. The unit checked out will be marked as consumed and no longer tracked in the system. Use the Unit Return transaction to record returns to stock. |
| Track Ownership by Team | When enabled, ownership is tracked for the assets. Owners can be an internal team or can be a customer. Visibility to the assets is based on both custody and ownership. If not checked, there is no team ownership assigned and visibility will be available to all users based on custody. |
| Track as a Master Item for Build Unit | When enabled, the asset is treated as a parent unit and components can be assigned to the asset. Components may be returnable or can be consumables. There is the ability for unlimited nesting; therefore, a parent (master) unit can also be a component (child) unit. |
| Enable as a Component Item for Master Item | When enabled, the asset can be selected as part of a unit build. The unit will be marked as consumed when added to a master (parent) item, but can be reviewed in the logs or reports. |
| Enable Status Change on Update Unit transaction | The Update Unit transaction tends to be a generic transaction to support changes to status or capturing or changing unit attribute data. When enabled, the status is enabled to support status changes. For example, a unit may be updated from available to out-of-service if it is being sent to maintenance. |
| Track as parts of Maintenance | When enabled, units can be selected as a component to issue on unit maintenance. |
Quantity Tracked: Asset Returnable
| Capture Unit Cost | For Receive New Unit and Create, the unit cost can be captured. The unit cost is stored against the serialized item unit. |
| Can be Checked Out | When enabled, items will the status of available can be checked out to assignees or customers. If the item is already checked out, it can be transferred or it can be checked in and then re-checked out as part of the check out step. Sub rules include the ability to track an expected return date. |
| Can be Deployed | Similar to check out, deployed units maintain a facility or customer address location. Typically stationary assets are deployed verus checked out as the physical location is obvious. |
| Track Ownership by Team | When enabled, ownership is tracked for the assets. Owners can be an internal team or can be a customer. Visibility to the assets is based on both custody and ownership. If not checked, there is no team ownership assigned and visibility will be available to all users based on custody. |
| Enable as a Component Item for Master Item | When enabled, the asset can be selected as part of a unit build. Assets that are part of a build retain the status of ‘In Build’ until removed. |
| Track as Rental TO Customers | When enabled, the item master can be assigned a billing schedule. Billing is then calculated against assets checked out to a project associated with a customer. |
Quantity Tracked: Inventory
| Capture Unit Cost | For Receive New Unit and Create, the unit cost can be captured. The unit cost is stored against the serialized item unit. |
| Can be Checked Out | When enabled, items will the status of available can be checked out to assignees or customers. When checked out, it recorded as consumed. To record returns back to stock, use the Return transaction |
| Track Ownership by Team | When enabled, ownership is tracked for the assets. Owners can be an internal team or can be a customer. Visibility to the assets is based on both custody and ownership. If not checked, there is no team ownership assigned and visibility will be available to all users based on custody. |
| Enable as a Component Item for Master Item | When enabled, the asset can be selected as part of a unit build. Item is marked as consumed but can be reviewed in the logs or reports. |
| Track as parts for Maintenance | When enabled, available to select as a consumable to issue for maintenance. Item is updated to consumed. View issued items in the logs or reports. |
Lot Tracked Inventory
| Capture Unit Cost | For Receive New Unit and Create, the unit cost can be captured. |
| Track Ownership by Team | When enabled, ownership is tracked for the assets. Owners can be an internal team or can be a customer. Visibility to the assets is based on both custody and ownership. If not checked, there is no team ownership assigned and visibility will be available to all users based on custody. |
| Enable Capture of Expire Date | When enabled, the expire date field will be enabled to capture. Note that if there is existing quantities for the SAME item + lot, the expire date will inherit from the originally entered lot. |
| Enable Capture of Manufacture Date | When enabled, the manufacture date field will be enabled to capture. Note that if there is existing quantities for the SAME item + lot, the manufacturer date will inherit from the originally entered lot. |
| Enable as a Component Item for Master Item | When enabled, the asset can be selected as part of a unit build. Item is marked as consumed but can be reviewed in the logs or reports. |
Item Template Weight & Dimension Setup
Under the Weights & Dimensions tab, define the default UOM and weight and dimension rules.
Under the weight and dimension setup tab, define a default item UOM for this template. When creating item master records, the UOM will default for the items based on this setup. The UOM can be changed for item masters if needed or leave blank to assign when creating an item master record.
Enable Weights. If tracking weights for items, set the weight unit of measure.
Enable Dimensions. If tracking dimensions for items, set the dimensional unit of measure.
Item Template Attribute Assignment
Under the Attributes tab, assign the attributes. Be sure to have attributes you plan to assign created before setting up this portion of the item templates. Attributes can be set as optional or required.
Attributes for items can be assigned to:
Master. These attributes are captured when a new item master is created or imported (if importing your item master records). Item Master attributes are those that are standard and directly related to the Item Master (or item code). For example, if your item master represents an item with a specified manufacturer and model; then those attributes can be assigned on the master level. This eliminates the need to capture those details for every unit being entered. All units with this item master inherit the item master data. Attributes can be set to be optional or required. Edit to the item master records support the ability to change the data later if needed.
Unit. Assigned data specific to the individual unit. Typically, these attributes will be presented when adding or receiving a new unit into the system; however, the attribute can be set up to be assigned on an alternate transaction.
Unit attributes can also be setup to default for Receiving transactions. For example, a serial number would always be unique to each individual unit; however, a manufacturer being tracked on the unit level would be the same if receiving 20 units of the same item at the same time.
Unit attributes can also be enabled to capture on the following transactions:
- Build Unit
- Update Unit
- Check In
- Maintenance
- Allocate to Project
- Transfer Site Location
- Transfer Ownership
Transaction. Attributes defined under transaction will be presented to capture based on the transaction(s) selected. This data is directly ASSOCIATED with the unit; however, it is not a unit attribute. Transaction attributes are those that capture historical information for a unit. For example, a condition of a unit being checked in. The condition can be recorded at different times the unit is checked in and a historical report can be created to review the condition captured over the course of the item’s life.
Container Templates-Masters
Define movable containers under Container Setup. Movable container examples are pallets, cartons, or boxes. Containers are tracked by a unique ID to support the ability to move a group of items or to group items and other containers for shipping.
Container Setup Rules
Rules can be defined for the movable container units being tracked in the system.
Can Hold Hazardous Material.
If you have any item setup as hazardous, consider if the movable container is able to hold that item. If yes, then be sure to check this rule. This rule allows the ability to define different containers that can hold hazardous material for storage and shipping.
Can combine items with different attributes.
When checked, restricts the items that can be added to those for the same item master and the same attributes. Be sure to check this rule to allow a mix of items to be added to the container. The rule is designed to support grouping same items to a single container. Example: Grouping of an item tracking a lot number so the same lot and lot details can be tracked on a container level.
Can combine items with multiple owners.
When items tracked in the system have multiple owners (either internal or customer), this rule supports the ability to keep the contents of the container segregated by ownership. This is typically used for organizations that manage customer-owned inventory to keep the items segregated.
Restrict contents to a single item master.
Similar to the rule Can combine items with different attributes but removes the attribute level restriction. This allows the ability to track an item on a container level. Example: Create a container holding 100 of WIDGET-A. The container of 100 can then easily be picked for an order by the container.
Can hold other movable containers. This rule manages the ability to nest containers. For smaller containers (such as boxes or cartons), it may not be practical to allow other containers to be added. By not checking this rule, the container would only become available for adding item units and not nesting other containers. This rule is typically checked for large containers that will be used for shipping (such as a pallet or crate) to allow adding other smaller containers.
Available as a pick to container for Pick Order.
This container template will be available to create for pick order when the order pick also includes a pack function. Containers that do not have this rule will not be available to pack items into during a pick activity.
For internally owned units, track ownership by team versus organization.
When checked, the container will support the ability to identify the owner. Ideal if tracking customer-owned items. If not checked, container ownership is not tracked.
Can be directly shipped.
When checked, the container can be directly shipped outside of a shipment build.
Allow for Update Unit Transaction.
Most often checked if tracking weight and dimensions for the container or if other attributes need to be assigned to the container at a later time outside of when it is created. Example: Capture the packaging date for a container. Weight and dimension fields behaviors are setup under the weight and dimension section.
Enable Project Allocation.
If tracking items for projects/jobs, this rule allows the ability to enable assigning a project to the container. Only items allocated to the project or that have no project allocation can then be added to the container. This rule allows the ability to group items in a container for a specific project/job. The project assignment is enabled on create with this rule checked.
Container Weights & Dimensions
If tracking weights and dimensions on the container, define the unit of measure for the container. Identify when the weight and/or dimensions are captured for the container.
- When created.
- For Build Container (as the container being built)
- As the container being added to the container being built.
- When added to a shipment build.
- When directly shipped.
- On Update Transaction.
Container Attributes
The same as items, attributes can also be assigned to containers.
Template-Master Attributes. Container setup combines the template and master setup that items have. When defining an attribute at this level, the entry of the data will be entered at the same time.
Unit Attributes. Identify additional data to capture on a container unit. Once added, define which transaction to capture or update the data.
- Create
- Build Container
- Shipping
- Receive Transfer
- Build Shipment
- Update Unit
Transaction. Capture data associated with the container on a transaction. This would typically be data that may change over the life of the container at different points and times.
Transport Setup
Transport setup is basically setting up container types or shipping methods directly related to Carriers. Different types of templates can be defined to capture different attributes. Example: For carriers such as Fed Ex, UPS, etc., an attribute to capture an account number or present a field to capture a third-party account number at shipping could be set up.
Access Transport Setup under the setting icon on the top menu bar.
Template ID. Enter a template ID. Note that at least one template must be defined if using the shipping functionality of the system.
Description. Add a description.
Assign Unit or Transaction Attributes.
Shipment Template Setup
If using the shipping portion of the system, set up at least one shipment template. Templates identify the data that would be captured for the shipment. For example, a template can be defined for shipments that require a Bill of Lading. System attributes such as the BOL Number, Freight Charge Terms, Freight Bill To; would then assign. Attributes can be marked as required for shipping. A different template would then be defined for shipments such as for Fed Ex or UPS. Planned Carrier and Expected Ship Date are inherited attributes for all shipment templates.
Access the Shipment Setup under the settings icon on the top menu bar.
Template ID. Enter a template ID.
Description. Add a description for this template.
Assign Attributes. If the attribute is required for shipping documentation; then check the Required for Shipping checkbox.
Maintenance Template Setup
If completing maintenance activities and setting up maintenance plans, define the maintenance templates.
Template ID. Identify the name of the maintenance activity.
Default Frequency. Option to define the default frequency for maintenance plan setup. Options include days, weeks, and months. This can be changed on the actual unit maintenance plan setup.
Description/Notes. Add a description or instructions for this maintenance activity.
Assign Attributes. Assign the attributes to capture for this maintenance activity. Note: Even if there is no specific data to capture, it is recommended to at least have a note field attribute added.
Project Template Setup
When setting up project or jobs in the system, at least one project template needs to be defined. Project templates provide the ability to define additional data (attributes) to track for the project. Standard project data (that won’t require adding attributes) include:
- Customer association
- Project Location (can be assigned any facility or customer address setup in the system)
Other examples of attributes could be contract number or project end date.
If using projects, at least one project template must be setup.
Access the Project Setup under the settings icon on the top menu bar.
Name. Enter the project template name.
Description. Option to add a description for this template.
Assign Attributes. Assign attributes to track for the projects created with this project template is selected. Attributes can be set as optional or required.
Package Template Setup
If using the Package Tracking functionality in PanatrackerST, setup the package tracking template.
Template ID. Enter a template ID.
Display name. Enter a display name for the template. If left empty, the template ID will be used by default.
Description. Enter a description for the template.
Weights and Dimensions Tab. Supports the ability to enable capture of weight and dimensions for the package when received.
Attribute Assignments. Assign the attributes to capture for the package unit.
Location Template Setup
Templates are defined for locations
- Facility
- Areas
- External (Addresses) for Customers and Vendors
Facility Template Setup
Facilities represent internal site locations such as a warehouse, plant location, tool crib, or stockroom. Facilities will typically have a mailing address associated.
Access setup from the system settings icon from the top menu bar under Location Setup. The Location setup has three tabs: Facility – Area – External (for customer and vendor address setup).
Template ID. Enter a Template ID for the template
Description. Enter a description for the template.
Receipt Confirmation Expected. If the destination facility will receive transfers shipped from another internal facility, check this rule option. If not checked, transfers shipped will be marked as shipped and no further tracking of the units under that shipment is expected.
Attributes. Identify attributes to define for any locations created using this template.
Area Template Setup
Areas are the locations within a facility. Typically, areas represent an aisle, shelf, row, bin, or floor area. It is required that every facility has at least one area setup. Area templates support different rules. For example, setup stock areas and staging areas with different rules to better manage items.
Access setup under the system settings icon from the top menu bar. Under Location Setup, select the Area tab.
Template ID. Enter a template ID.
Description. Enter a description for the template.
Area Template Rules:
Can Contain Hazardous Material. If tracking items marked as hazardous, at least one area should have this rule enabled. Hazardous items cannot be assigned to any areas that do not have this rule enabled.
Mark units as consumed when received from an in-transit transfer. If a shipment is from another internal facility, the receipt can be recorded to an area that will mark all in-transit units received to the area as automatically consumed. This allows the ability to record the receipt and mark the items consumed at an end-point destination.
Set as a stock area for units to be picked from. Only areas with this flag will be areas available for an order pick. Allows the segregation of items staged to ship and items actually available to pick.
Set as a staging area. When enabled, these areas will be available to select to move items to when picking and reserving.
Assign Area Attributes
Define any additional data to track for the areas being setup with this template.