Setting Up PeopleSoft Maintenance Management System Parameters

This chapter provides an overview and prerequisites of Oracle's PeopleSoft Enterprise PeopleSoft Maintenance Management's product integration and system parameters setup requirements and discusses how to:

• Define a service request business unit.

• Set up a work order business unit.

• Set up resource assignment approval options in PeopleSoft Maintenance Management.

• Set up PeopleSoft Maintenance Management work order parameters.

• Set up rules and data related to Project Costing.

• Set up ChartField distributions for PeopleSoft Maintenance Management.

Understanding Overall System Setup Parameters for PeopleSoft Maintenance Management

This section discusses:

• PeopleSoft Maintenance Management setup considerations.

• PeopleSoft Maintenance Management installation options.

• SetID considerations in PeopleSoft Maintenance Management.

• Permission lists, roles, and user profiles.

• PeopleSoft Maintenance Management user preferences.

PeopleSoft Maintenance Management Setup Considerations

In addition to the integrated product setup, setting up PeopleSoft Maintenance Management includes:

• Installation options.

• SetID.

• Security.

• User preferences.

• Service request business unit.

• Work order business unit.

• Work order types.

• Service groups.

• Work order priority codes.

• Maintenance types.

• Asset downtime reasons.

• Problem, cause, and resolution data and problem trees.

• Service request statuses.

• Work order statuses.

• Labor and tool resources.

• Work order templates.

• Preventive maintenance loops and schedules.

• Work order workflow approval.

SetID Considerations in PeopleSoft Maintenance Management

PeopleSoft Maintenance Management uses system data, which is set up in PeopleSoft Asset Management, Project Costing, PeopleSoft Purchasing, PeopleSoft Expenses, PeopleSoft Inventory, PeopleSoft Resource Management, and other subsystems to create and process work orders. Much of the data that is set up in these subsystems is organized by setID.

It is important to understand the difference between business units, setIDs, and records:

SetID mapping is used to coordinate the various set control record groups. For example in PeopleSoft Maintenance Management, work order task and work order job templates reference setIDs from various subsystems. You must set these templates to copy labor, PeopleSoft Inventory, purchase/on hand materials, and tool task requirement values, which are derived from various subsystems, to a work order task. These requirements must be compatible with the various work order business units used for each work order. To accomplish this, you set up the setIDs as set control values using setID mapping:

The following table lists some of the record groups used in PeopleSoft Maintenance Management:

You must follow one rule and guideline to perform setID mapping for work order job and work order task templates.

See Understanding Work Order Templates.

PeopleSoft Maintenance Management Installation Options

Select the PeopleSoft Maintenance Management check box on the Installation Options - Products page to enable you to install PeopleSoft Maintenance Management. You must install PeopleSoft Asset Management, Project Costing, and PeopleSoft Purchasing prior to installing PeopleSoft Maintenance Management.

If your organization intends to obtain items from PeopleSoft Inventory to use in the repair and maintenance of assets via PeopleSoft Maintenance Management, you must. install PeopleSoft Inventory.

If you want to create requisitions in eProcurement to purchase noninventory and open description labor, materials, and tools for a work order task, you must install PeopleSoft eProcurement. You may want to also install PeopleSoft Payables to continue processing the purchase orders and requisitions.

If you want technicians to enter personal time on the Technician Workbench and process that time through PeopleSoft Time and Labor and PeopleSoft Payroll, you must install those products.

Finally, to process and post accounting data that is generated based on work order transactions in the general ledger, you normally install PeopleSoft General Ledger.

See Setting Up Application-Specific Installation Options.

Permission Lists, Roles and User Profiles

You must set up permission lists using PeopleTools Security. You then define roles and select permission lists to apply to these roles. Once the roles are set up, you select the roles that apply to specific user profile.

For example, the sample data contains the following permission lists:

• EPPC2100 – Project/Activity Team

• EPPG4000 – Detailed Project Planning

• Work Order Management

The PeopleSoft Maintenance Management sample also has these roles defined:

• Project Manager

• Maintenance Technician

• Maintenance Planner

• Maintenance Supervisor

• Warehouse Clerk

• System Administrator

• Self-Service User

Examples of user profiles are:

• SRVP - Senior Vice Presidents

• SRMGR - Senior Managers

See Enterprise PeopleTools PeopleBooks: Security Administration

PeopleSoft Maintenance Management User Preferences

Your organization may enable specific users to perform selected service request and work order functionality by accessing the User Preferences, Maintenance Management page.

You can read about each option on the User Preferences, Maintenance Management page in the PeopleSoft Enterprise Application Fundamentals PeopleBook by clicking on the link below.

Important! User Preferences is where you determine the time reporting method (Punch Time or Elapsed Time) that applies to the work order labor hours that apply to this user or for the labor hours entered by this user for other users.

See Defining PeopleSoft Maintenance Management User Preferences.

Prerequisites

Set up the following products prior to setting up PeopleSoft Maintenance Management:

• PeopleSoft Asset Management

• Project Costing

• PeopleSoft Purchasing

• (Optional) PeopleSoft Inventory

• (Optional) PeopleSoft eProcurement

• (Optional) PeopleSoft Time and Labor

• (Optional) PeopleSoft Payroll

Defining a Service Request Business Unit

To set up a service request business unit, use the Service Request (BUS_UNIT_TBL_WR) component.

This section provides an overview of service request business units and discusses how to:

• Set up the service request business unit Definition page.

• Select service request fields for audit control.

Understanding Service Request Business Units

The primary purpose of the service request business unit is to separate service requests by request center. The service request business unit consists of two separate pages:

• Definition page.

  Service Request Options, which enable you to set up a default service center and service request priority value of critical, urgent, standard, or low. You also indicate the number of days between completion of a service request and the actual automatic closing of a service request. A requester is notified when a service request is complete and can respond within the number of days entered here if the work was not performed satisfactorily or something more needs to be done. The system also tracks the number of the last service request issued for this service request business unit.

• Audit Control page.

  This page enables you to select the service request fields to audit for changes.

There is no direct correlation between service request business units and work order business units. If an agent creates a work order from a service request, the work order business unit is derived from the problem definition and the service center (location) on the service request. For example, if you create a service request indicating that there is a malfunctioning desktop computer in Pleasanton for the HQ-IT agent, the agent can create a work order using work order business unit US001, which is the business unit for which this problem and service center were defined.

Note. The system does not use the service request business unit to process any accounting transactions.

Pages Used to Set Up a Service Request Business Unit

Setting Up the Service Request Business Unit Definition Page

Access the Service Request Definition page. (Select Set Up Financials/Supply Chain, Business Unit Related, Maintenance Management, Service Request Definition.)

When you set up a new service request business unit, you enter the new business unit number in the Add a New Value page, and when you access the Definition page, you describe this new business unit, select a default setID, and create the business unit using:

Service Request Options

Selecting Service Request Fields for Audit Control

Access the Audit Control page. (Select the Audit Control tab.)

Service Request Audit Fields

Select the service request fields in which you want to audit changes. The fields include: Asset Identification. Assigned By. Assigned To. Location Code. Service Request Center. Service Request Priority. Service Request Status.

Setting Up a Work Order Business Unit

To set up a work order business unit use the Work Order Definition (BUS_UNIT_TBL_WM) component.

This section provides an overview of work order business unit setup and discusses how to:

• Define the work order business unit.

• Set up integration parameters for a work order business unit.

• Enter preventive maintenance parameters for a work order business unit.

Understanding Work Order Business Unit Setup

Work order business units are synonymous with work centers. You can set up as many work order business units as necessary to support your business requirements. The business unit represents the highest level of the default hierarchy within PeopleSoft Maintenance Management, which means that the values specified in a work order business unit are used as default values and controls throughout PeopleSoft Maintenance Management.

The work order business unit consists of three parts, which include:

• The Definition page in which you define information unique to this business unit, set up work order workflow approval and work order access security, select specific set up options and warranty claim information, define default values and default hierarchies, specify work order numbering characteristics, and track last Warranty Claim and Failure Tracking IDs.

  The required fields on this page are Location, GL Business Unit, Base Currency, Rate Type, Service Group, and Accounting Default Order.

• The Integration page in which you identify specific options that enable a business unit to integrate with Project Costing, PeopleSoft Inventory, PeopleSoft Purchasing, and PeopleSoft eProcurement, define default labor rates for resources, and enable mobile integration.

  The Project Costing Business Unit is a required field.

  Note. The Inventory business unit and commit rule are only required if you plan to integrate and use PeopleSoft Inventory with PeopleSoft Maintenance Management.

• The PM Options page defines specific options that enable you to use this business unit to enter and process preventive maintenance work orders.

  The required fields on this page are Priority Code, Work Order Type, and Task Status.

See Understanding Integrated and Shared Products Setup Considerations.

GL Business Unit

You must identify a GL business unit for each work order business unit that you set up. This GL business unit serves as the default GL business unit in each of the distribution templates that you set up (Project Costing, PeopleSoft Expenses, PeopleSoft Inventory, and PeopleSoft Purchasing). However, the default GL business unit value only appears in the PeopleSoft Purchasing distribution template, because PeopleSoft Purchasing is the only product in which you can override this value.

To process labor costs, you must set up a GL business unit in PeopleSoft Expenses that matches the GL business unit that you specify in the work order business unit.

To process inventory costs, you must set up a GL business unit in PeopleSoft Inventory that matches the GL business unit that you specify in the work order business unit.

Currency Conversion

You must set up a base currency in each work order business unit, which establishes the base currency in the work order. You cannot override this value in the work order. When you create and schedule resources for a work order, the transactions generated in the subsystems based on the work order for PeopleSoft Inventory, PeopleSoft Purchasing, PeopleSoft eProcurement, PeopleSoft Payables, PeopleSoft Expenses, PeopleSoft Time and Labor, PeopleSoft Payroll, and PeopleSoft Asset Management (based on tool rates defined at the shop level) can undergo currency conversions if the base currency in the subsystem differs from the base currency in the work order business unit. When a user closes a work order task or runs the Cost Summarization process in PeopleSoft Maintenance Management to return the actual costs from Project Costing to PeopleSoft Maintenance Management, the costs are converted back to the base currency in the work order.

Note. Currency conversions do not apply to labor costs.

This section discusses:

• Currency conversion for labor costs.

• Currency conversion for inventory costs.

• Currency conversion for purchasing/on-hand costs.

• Currency conversion for tool costs.

Currency Conversion for Labor Costs

You enter time entries for employees based on labor rates set up in PeopleSoft Maintenance Management. These entries use the base currency in the work order. No currency conversion is performed for work order time recorded. Only the hours and labor rates are provided to Project Costing's cost collection process for the calculation of labor cost.

You enter time for personal time entries and you set up PeopleSoft Time and Labor and PeopleSoft Payroll, the system uses the currency code set up in PeopleSoft Time and Labor to calculate estimated payable time. PeopleSoft Payroll has currency codes set up to calculate the actual payable time and sends this actual payable time back to update PeopleSoft Time and Labor.

See PeopleSoft Time and Labor PeopleBook: "Publishing Estimated and Actual Payable Time"

Currency Conversion for Inventory Costs

When you enter or select an inventory item in the Inventory Requirements and/or Inventory Schedules grids of a work order, PeopleSoft Inventory returns the cost of the item using the base currency in the Inventory business unit. If the base currency for the work order differs from the Inventory base currency, PeopleSoft Maintenance Management converts the cost of the item to the base currency in the work order. When the transactions are sent to PeopleSoft Inventory for processing, they are converted back to the Inventory base currency, which sends them to Project Costing. After Project Costing processes the actual costs and chargebacks in the Inventory base currency, then it sends the actual costs back to the work order, where the PeopleSoft Maintenance Management Cost Summarization process converts the currency back to the base currency in the work order business unit.

For example:

• Work Order Business Unit base currency = EUR

• Inventory Business Unit base currency = USD

Currency Conversion for Purchasing/On-Hand Costs

There are several ways to capture purchase/on-hand costs in PeopleSoft Maintenance Management. The currency conversions are based on whether the work order task transaction uses a purchase order or a requisition in Purchasing, eProcurement, or whether the work order transaction came from PeopleSoft Payables.

An example of currency conversions based on Purchasing:

• Work Order Business Unit base currency = EUR

• Purchasing base currency = USD

An example of PeopleSoft Payables currency conversions:

• Work Order Business Unit base currency = EUR

• PeopleSoft Purchasing base currency = USD

• PeopleSoft Payables base currency = AUD

Currency Conversion for Tool Costs

Tools are set up as assets in PeopleSoft Asset Management's asset repository and normally have a cost rate assigned to them indirectly through the asset type/subtype association. A default currency is set up in the Asset Management business unit. However, you can also specify a default currency, as well as a cost and billing rate for an asset subtype. The default values for currency, cost rate, and billing rate that appear in the work order task schedule line, depend on your selection. When you schedule a tool for a work order task, the system converts the base currency for the asset to the base currency for the work order, which is established in the work order business unit. When a user enters tool usages in the technician workbench, PeopleSoft Maintenance Management calculates the cost of the tools and updates the total actual costs in the Costs page of the work order using the base currency in the work order. Because these costs do not update PeopleSoft Asset Management or Project Costing, they are not converted back to the base currency in PeopleSoft Asset Management.

Business Unit Setup Options

When you select the check box associated with each of the options listed in the work order business unit, you can:

• Use multiple assets when you create a work order with this business unit.

• Generate chargebacks when you set up the Task Accounting for a work order associated with this business unit.

• Edit ChartFields enables ChartField combination editing in the Inventory, PeopleSoft Purchasing/On-Hand, and Tools distribution rows for each work order task.

• Enter labor requirements, inventory requirements, and tool usage requirements on the Requirements page of a work order.

• Schedule labor, inventory, and tools for a work order.

• Record Actuals tool usage costs, which display in the Cost page of the work order.

• Update assigned tasks in an employee's resource calendar and assigned tools in the tools calendar to enable a scheduler to determine if either type of resource may be available for another assignment.

Work Order Approval

You determine whether a work order requires approval or is pre-approved in the work order business unit. You can override this selection for a specific shop or for a work order type. If you indicate that you want work orders set up with this business unit approved, then you must first perform the setup described in the Configuring Work Order Approval Workflow chapter. Once you have set up work order approval, refer to the Approving Work Orders chapter for details on how to approve each work order.

See Configuring Work Order Approval Workflow.

See Approving Work Orders.

Warranty Claim Information

You can generate warranty claims in PeopleSoft Maintenance Management based on assets that are selected for repair or maintenance in a work order. You can identify the contact information that will appear on warranty claims generated based on assets identified in work orders that are created with this business unit.

See Managing Warranty Claims.

Technician WO Security

Select one of these options to apply work order access security to any work orders created with this business unit. Work order access security restricts access for users with the Apply WO Access Security check box selected on the User Preferences – Maintenance Management page to a work order, work order tasks, and an express work order created with this business unit depending on which of these options you select.

• Full Access

  When you select the Full Access option in the work order business unit, any PeopleSoft Maintenance Management resource can access any work order and work order task on the Work Order, Technician Workbench, and the Express Work Order components created with this business unit, depending on the user's PeopleSoft Security setup for these components.

• Shop

  Selecting this option enables a user with the Allow Access to WO Security check box selected on the User Preferences – Maintenance Management page to click the Technician Work Order Access link on the Work Order component's Miscellaneous page of any work order created with this business unit and access the Work Order Access page.

  The Work Order Access page lists, at a minimum, the shop used to create the work order. If a resource is selected for a work order task and is assigned to a shop that is different from the shop used to create the work order (cross-shop), then this shop is automatically added to the list on the Work Order Access page. The authorized user can add or remove any shops to and from this list except for the shop that was used to create the work order.

  Resources, who have Apply WO Access Security selected on the User Preferences – Maintenance Management page and are assigned to one of the shops listed on the Work Order Access page can access the work order and work order tasks from the Work Order, Technician Workbench, and the Express Work Order components.

  Note. Shop security applies to work order-managed work orders and Project Costing-managed work orders.

• Resource Pool

  Resource pools are set up in PeopleSoft Resource Management for use in PeopleSoft Program Management and Project Costing. A resource pool consists of a specific group of resources that you can assign to a project from PeopleSoft Program Management. If you select this option and create a work order using this business unit and a project and activity that is associated with a resource pool, then only the members of that resource pool, who have the Apply WO Access Security check box selected in the User Preferences – Maintenance Management page, can access the work order and work order tasks created with this business unit and the project and activity associated with the resource pool on the Work Order, Technician Workbench, and Express Work Order components.

  For example, you set up a resource pool (Pool A with the resources John Jones, Earl Green, Regina Smith, and Eric Lasser) and assign the pool to a project (MM001) and activity (0001) in PeopleSoft Program Management. You select the Apply WO Access Security check box on the User Preferences – Maintenance Management page for each of the resources in the pool. You select the Resource Pool option for work order business unit US001. You create five work orders using work order business unit US001. Each work order has 3 tasks associated with Project MM001 and activity 0001. Only resources John Jones, Earl Green, Regina Smith, and Eric Lasser can access the five work orders and their associated tasks that were created with this work order business unit, project, and activity in the Work Order, Express Work Order, and Technician Workbench components.

  Note. You can assign generic resources to resource pools in PeopleSoft Resource Management. Generic resources are resources that do not have an employee ID associated with them. Generic resources serve as role-oriented placeholder descriptions for resources during the project planning phase. Typically, in the planning stage, project managers use generic resources instead of named resources. After the project is approved, project managers create resource requests and replace generic resources with the specific available resources.

  Important! The resource pools associated with projects and activities must be up to date in order to use resource pool security in PeopleSoft Maintenance Management. You typically set up projects and activities associated with Project Costing-managed work orders ahead of time, which remain stable over the life of the associated work orders. The pool cache table stores data at the project, activity, and resource level. However, since the activities for work orders associated with work order-managed projects are created when the work order task is created, the pool cache table will not reflect the latest valid combinations of resource, project, and activity unless you run the pool cache Refresh process using the Program Management, Program Tools, Enforce Team Pool Refresh process to enable resource pool security.

• Shop and Resource Pool

   

  Selecting this option enables only authorized users to access work orders and work order tasks in the Work Order, Express Work Order, and Technician Workbench components who are assigned to one of the shops listed on the Work Order Access page of a work order created with this business unit, or who are assigned to a resource pool set up for the project and activity that is associated with this work order and work order tasks created with this business unit.

See Establishing Resource Pool Security.

See Defining PeopleSoft Maintenance Management User Preferences.

See PeopleSoft Maintenance Management Integration with PeopleSoft Project Costing.

Work Order Business Unit Defaults and Default Hierarchies

You can set up specific values in the work order business unit that you want to display as default values in the work order. You can also set up different default hierarchies that use a weighting formula (algorithm) to determine which setup data to use as default data in the work order.

Work Order Business Unit Default Values

You can enter the default field values in the work order business unit that you want to display in fields in the work order. These fields include:

• Service Group

  When you create a work order using this business unit, the service group value that you enter in the work order business unit becomes the default value for the service group field in the work order header.

  You can override this value in the work order.

• Shop

  When you create a work order using this business unit, the shop value that you enter in the work order business unit becomes the default value for the shop field in the work order header.

  You can override this value in the work order.

  Important! When you add a new work order business unit you have not set up your shop(s) for that business unit. Therefore, you bypass this field when creating a new business unit and return to it after creating the shops that you want to associate with this business unit.

• Close Days

  When you complete a work order task in a work order that was created with this business unit, the system uses the default value that you enter here in the work order business unit to determine the number of days between the completion and the close of a work order task.

  You can override this value for a specific work order type.

• Asset Lookup Field

  When you create a work order with this business unit, the lookup field value (Asset ID, Serial ID, Tag Number, or Vehicle ID Number) that you select for this business unit displays as part of the asset specifications on the work order and work order tasks.

• Maintenance Type

  This value displays in the Maintenance Type field on the Miscellaneous page of the work order. You can override this value in the work order. If you use this business unit to create preventive maintenance work orders, you must specify a maintenance type in the work order in order to close the work order. Entering a default value in this field for the business unit helps prevent any problems at closing.

See Setting Up PeopleSoft Maintenance Management Work Order Parameters.

Work Order Business Unit Default Hierarchies

You can also set up default hierarchies in a work order business unit to determine the various types of data that you want to display in a work order. The default hierarchies include:

• Control Default Order

• Project Default Order

• Accounting Default Order

Control Default Order

Control Default Order is used to determine the default data that you want to use for work order control procedures such as work order close and work order approvals. You can choose from two different default hierarchies:

• Unit, WO Type, Shop.

  In this hierarchy, the system checks the default values for a work order created with this business unit based on the following order:

  1. Shop.

  2. Work order type.

  3. WO business unit.

• Unit, Shop, WO Type.

  In this hierarchy, the system checks the default values for a work order created with this business unit based on the following order:

  1. Work order type.

  2. Shop.

  3. WO business unit.

Important! There must be a specified value in a level for one level to override another level. For example, if you specified at the shop level that you want the work order approved, and you either do not specify a value or select default for the work order type, the system ignores the work order type and looks at the default value specified in the work order business unit. If the value specified in the work order business unit is Pre-Approved, since the shop's value takes precedence over the value in the business unit based on the default hierarchy, then the system applies the shop's value, which requires work order approval to any work order created with the specific business unit and shop.

Project Default Order

Project Default Order is used to determine the default project to use in a work order created with this business unit using values specified in the Associate Projects component, as well as values specified in the Project Costing ChartField distribution template. Both the Associate Projects component and the Default PC ChartFields component are set up based on the value specified for the business unit, service group, and work order type. In this case, a formula is applied to these values to determine the default level. You can choose from two different hierarchies:

• Unit, Service Group, Type.

• Unit, Type, Service Group.

You can set up the Default PC ChartFields component based on various combinations of service group and work order type. For example, you could set up the Default PC ChartFields component with these values:

• WO BU 01, Service Group %, Work Order Type %

• WO BU 01, Service Group MAINT, Work Order Type %

• WO BU 01, Service Group MAINT, Work Order Type CAPT

Since there can be numerous combinations, the system needs some method to determine which Project Costing ChartFields to use as default values in the work order. It determines the default values based on the following formula and based on the combination that you select in the work order business unit. This is also the way the default project is determined based on the setup of the Associate Projects component.

The formula to determine the default project ID in the work order is:

1x₁ + 2x₂ = Default Row Value

Where:

For: x₁ If value is % (wildcard) then x₁ = 0 Or: If value is not % (wildcard) then x₁ = 1

Where:

For 2x₂ If value is % (wildcard) then x₂ = 0 or If value is not % (wildcard) then x₂ = 1

For example, if you select the Project Default Order in the work order business unit as Unit, Service Group, Type, and the rows that you set up in Associate Projects contain the information in the following table. Based on your selection in the work order business unit, the Service Group value is 1x₁ and the Work Order Type value is 2x₂ in the formula. When the system applies the formula, the default Project ID in the work order would be PC002, because the sum of the values in Row #2 = 2, which is greater than the sum in Row #1 (0) or Row #3 (1).

If you select the Project Default Order as Unit, Type, Service Group, then the Service Group = 2x₂ and the Work Order Type = 1x₁ , then when you apply the formula to the same rows, then Row #1 = 0, Row #2 = 1, and Row #3 = 2.

Therefore, the default Project ID based on Unit, Type, Service Group in the work order is PC003 in Row #3, which is the row with the greatest value.

Once the default Project ID is selected, the system uses the Project Default Order that you select in the work order business unit and applies the formula again to the PC Default ChartFields component to determine which row containing default Project Costing ChartField values for the default project ID has the highest calculated value. This row contains the defaulting Project Costing ChartField values that display in the work order task when you click the Distribution link for a work order task.

See Understanding Project Defaulting and Capitalization Rules in PeopleSoft Maintenance Management.

See Associating Projects with a Work Order Business Unit, Work Order Type, and Service Group.

Accounting Default Order

Accounting Default Order is used to determine the default ChartField distribution template to use in the work order based on the values set up in the Distribution Template Rules component. There are seven values to which you can assign default attribute levels from 1 to 7, where 1 is the lowest and 7 is the highest. These default attributes include:

• Service Group.

• Work Order Type.

• Asset Type.

• Asset Subtype.

• Asset Location.

• Asset ID.

• Asset Unit.

Important! You must assign a numeric value to each of the seven attributes, with no duplicate values allowed. For example, you cannot assign a numerical value of 2 to Asset Type and Asset Location. The values must each be different. You cannot save the work order business unit unless you assign these values.

The formula to determine the default ChartField Distribution Template in a work order works basically the same way as the Project Order Default.

The formula to apply to the default values for the Accounting Default Order is:

1x₁ + 2x₂ + 3x₃ + 4x₄ + 5x₅ + 6x₆ + 7x₇ = Default Row Value

1x₁ + 2x₂ = Default Row Value

Where:

For x₁: If value is % (wildcard) then x₁ = 0 Or:If value is not % then x₁ = 1

Where:

For x₂: If value is % (wildcard) then x₂ = 0 Or: If value is not % then x₁ = 1

Where:

For x₃: If value is % (wildcard) then x₃ = 0 Or: If value is not % then x₁ = 1

Where:

For x₄: If value is % (wildcard) then x₄ = 0 Or: If value is not % then x₁ = 1

Where:

For x₅: If value is % (wildcard) then x₅ = 0 Or: If value is not % then x₁ = 1

Where:

For x₆: If value is % (wildcard) then x₆ = 0 Or: If value is not % then x₁ = 1

Where:

For x₇: If value is % (wildcard) then x₇ = 0 Or: If value is not % then x₁ = 1

For example, if you set up the values in the work order business unit and sequence them in the following order:

1. Service Group =

   x₁

2. Work Order Type =

   x₂

3. Asset ID =

   x₃

4. Asset Subtype =

   x₄

5. Asset Type =

   x₅

6. Asset Location.

   x₆

7. Asset Unit =

   x₇

The rows that you set up in the Distribution Template Rules contain the following values and the formula calculated for each value. In this example the default Distribution Template in the work order would be FLEET because the sum of the values = 13.

See Understanding ChartField Distribution Setup in PeopleSoft Maintenance Management.

Work Order Business Unit Integration Options

You set up specific options in the Integration page of the work order business unit for Project Costing, PeopleSoft Inventory, and PeopleSoft Purchasing.

You can also set up labor cost and bill rates that serve as default values in the labor requirements or labor schedule for a work order created with this business unit. You can override these labor rates in the shop.

Work Order Business Unit and Project Costing Integration Options

You must indicate the Project Costing business unit that will be used to create both work order managed and project costing projects in Project Costing. This business unit serves as the default value in the work order, the Associate Projects component, and the Work Order Task Accounting page.

You also indicate whether you plan to use a rate plan or rate sets for calculating chargebacks and other costs.

Rate sets enable you to create transaction rows for use in costing, billing, revenue recognition, or reporting, from incoming or existing transactions in the Project Transaction table. Rate sets have two parts: The source criteria that the Pricing process uses to compare against cost transactions coming in from feeder systems. The target definition of the cost, billing, or revenue recognition row that the Pricing process creates. When an incoming cost transaction matches the source criteria, the Pricing process creates a new transaction row for every target row on the rate set. You can assign the same rate set to multiple rate plans.

A rate plan is a collection of rate sets that the system executes in a specified order. Use rate plans to link rate sets so that priced rows from one rate set are used to create additional priced rows from the next rate set. For example, you can add additional expenses, such as administrative costs or overhead, to cost transactions before they are priced for billing or revenue. The Pricing process uses the rate plan to determine which rate sets to run and in what sequence to run them. When setting up the rate plan, you can assign rate sets in any combination of rate definition types—cost, billing, and revenue.

You select the analysis group from PeopleSoft Project Costing that is used by the Cost Collection process in PeopleSoft Maintenance Management to gather costs from PeopleSoft Project Costing into PeopleSoft Maintenance Management. The analysis group delivered for Maintenance Management in the Project Costing sample data is MMCST.

Work Order Business Unit and PeopleSoft Inventory Integration Options

You set up the Inventory business unit, the Inventory Commit rule, and the Work Order Reservation rule in the Integration page of the work order business unit.

The Inventory business unit serves as the default value when you select an item in the Inventory Requirements and Inventory Schedules grids. The setID associated with the Inventory business unit must match the setID associated with this work order business unit.

You specify a Commit rule to determine the point when you want to commit (recognize work order demand) the selected items to PeopleSoft Inventory, which means the point at which you want PeopleSoft Inventory to recognize the work order task demand for the item. Commit rules can be set up at the business unit level, the shop level, and the shop/work order type level within a shop. The rule you select applies to all work orders created with this business unit, shop, or shop/type. You can select one of the following Commitment rules, which include:

• Commit at Reserve

  Selecting this Commit rule enables you to defer committing the item(s) to PeopleSoft Inventory until the time you choose to reserve the item(s).

• Parts List

  The addition of an inventory item to the parts list, which means that Items are committed when they have been added to the Inventory Schedules grid and a save has been issued. Each subsequent part that is added and saved on the work order task will commit the item to PeopleSoft Inventory.

• Picking Plan

  Items are committed when a Picking Plan is created. A picking plan consists of the parts or inventory items that are added to a list, which direct inventory personnel to the storage locations for the items that they need to pick for the work order task. This option delays committing of the inventory items until you are ready to have them picked and available to begin working the work order.

• Work Order Status Change

  Items are committed when the work order task status is changed to an internal status of Awaiting Schedule, Scheduled, or Work in Progress.

You can also reserve inventory items, which are selected for a work order task, based upon your selection of a Work Order Reservation rule, which works in combination with the selected Commit rule. Work Order Reservation rules can be set up at the business unit level, the shop level, and the shop/work order type within the shop level. Inventory items must be committed before or at the same as they are reserved. The system will verify the valid combinations that can be set up for the commit and reservation rules that are chosen. The available values to select from for both commit and reservation rules will be filtered down to the applicable/acceptable valid values to ensure that you cannot establish invalid combinations of commit and reservation rules. The Work Order Reservation rules include:

• Batch Reserve Only

  When the batch process is run, the rows will be reserved.

• Parts List Creation

  When the parts (items) in the work order task are saved, the parts (items) are reserved.

• Pick Plan Creation

  When the picking plan is created, the part (item) is reserved.

• Work Order Status Change

  When the status of the work order task is changed to Awaiting Schedule, Scheduled, or Work in Progress, the parts (items) are reserved.

You also specify a priority number between 1 and 999 for work order reservations. PeopleSoft Inventory uses this number to sort demand and prioritize it accordingly, with 1 being the highest or most important priority and 999 being the lowest or least important priority. This number displays as a default value in the Inventory Schedules grid.

The selected Commit rule and the Work Order Reservation rule combination must be valid.

The values that display on the Reserve Rule/Status dropdown list depend on the value(s) that you selected for the Commit Rule/Status. If you change the Commit Rule/Status or change the default flag from Specify to Default on the shop header or shop/type pages and the current Reserve Rule/Status becomes invalid, the Reserve Rule/Status field is blanked out and a message is issued instructing you to specify a new Reserve Rule/Status from the updated list of valid choices.

Note. Depending on the changes you make, other restrictions may apply to limit work order business unit rule/status values from invalidating a lower-level shop header or shop/type definition that depend on the current work order business unit values.

Valid edit combinations are:

1. Commit rule = Parts List

   Reservation rule = Parts List.

2. Commit rule = Parts List

   • Reservation rule = Status Change = any 3 statuses

   • Reservation rule = Pick Plan

   • Reservation rule = Batch Only

3. Commit rule = Status Change = Awaiting Schedule

   • Reservation rule = Awaiting Schedule or Scheduled or Work in Progress

   • Reservation rule = Pick Plan

   • Reservation rule = Batch Only

4. Commit rule = Status Change = Scheduled

   • Reservation rule = Scheduled, Work in Progress

   • Reservation rule = Pick Plan

   • Reservation rule = Batch Only

5. Commit rule = Status Change = Work in Progress

   • Reservation rule = Work in Progress

   • Reservation rule = Pick Plan

   • Reservation rule = Batch Only

6. Commit rule = Pick Plan

   Reservation rule = Pick Plan

7. Commit rule = Commit at Reserve

   Reservation rule = All rules

then this indicates that there is at least one lower-level Shop or Shop/Type definition associated with (keyed by) this WO BU that depends on the current WO BU rule settings. The User may have to first reset the dependent Shop-level definition(s), before making the desired rule change to the WO BU.

Important! The edit ensures that the commit of items occurs prior to or at the same time as execution of the reservation rule. If the WO Status Change option is selected for both the commit and the reserve rule, then the reserve rule's internal status must be later than or the same as the commit rule's internal status.

If fewer values appear than usual on the commit rule dropdown list (less than 3 for commit rule, 4 for internal status), or the reserve rule dropdown list (fewer internal statuses based on Important rule above), then at least one shop or shop/type level setting depends on the current work order business unit setting. You may need to reset Inventory/Commit Rule Reservation at the shop or shop/type level before you can make changes to the rules at the work order business unit level.

Note. The batch reservation process will only reserve committed work order rows. If a reservation rule implies on-line reserve and the row(s) could not be reserved, a status TBD (to be determined) by Inventory will dictate if the batch reservation process will pick up the row(s).

Work Order Business Unit and Work Order Procurement Integration Options

You determine in the work order business unit whether you want to use purchase orders to purchase labor, non-inventory and open description materials, and tools for a work order, or whether you want to use Purchasing or eProcurement requisitions. When you set up requirements and scheduling for a work order created with this business unit, you can purchase items based only on the option you choose for this business unit.

If you do not want to use purchase orders or requisitions, you can select the blank space to leave the field blank or select None. Selecting this option hides the Load Purchase Order/Load Requisition button on Purchase/On-hand Schedules section of the Schedules page.

See PeopleSoft Maintenance Management Integration with PeopleSoft Purchasing and PeopleSoft Payables.

GIS Integration

If you indicate that you want to use ESRI GIS maps in the installation options for PeopleSoft Maintenance Management, a check box appears on the Integration page of the work order business unit. You select this check box if you want to enable the Map It buttons in the work order, Work Order Workbench, and Technician Workbench. Clicking one of these buttons enables you to view the asset associated with a work order task on an ESRI map. The check box is disabled if the GIS integration has not been setup and enabled by the system administrator.

Mobile Integration

If you are planning to integrate a mobile device supplied by a third party organization with PeopleSoft Maintenance Management Mobile Web Services, you must enable this Mobile Integration option for the Mobile Tasks Updated Pending links to appear on the Work Order, Express Work Order or Work Order Completion components, and the Mobile Public link to appear on the Task Search page associated with the Technician Workbench.

See Mobile Web Services Integration.

Pages Used to Set Up a Work Order Business Unit

Defining the Work Order Business Unit

Access the Work Order - Definition page. (Set Up Financials/Supply Chain, Business Unit Related, Maintenance Management, Work Order Definition, Definition.)

When you set up a new work order business unit, you enter the new business unit number in the Add a New Value page and, when you access the Definition page, you describe this new business unit, associate a setID, and create the business unit.

Business Unit

See Currency Conversion.

See Understanding Overall System Setup Parameters for PeopleSoft Maintenance Management.

Business Unit Setup Options

Select the options that you want to apply to your work order transactions.

Defaults

Define each of these fields to use as default fields on a work order associated with this business unit. You can override these values when you enter a work order.

See Work Order Business Unit Defaults and Default Hierarchies.

Numbering

Setting Up Integration Parameters for a Work Order Business Unit

Access the Work Order - Integration page. (Select Set Up Financials/Supply Chain, Business Unit Related, Maintenance Management, Work Order Definition, Definition.)

Project Costing

This section links any work order associated with this business unit to PeopleSoft Project Costing so that PeopleSoft Project Costing can serve as the cost repository for all work order costs, which includes the calculation and capitalization costs of assets. PeopleSoft Project Costing also calculates chargebacks and sends them to the appropriate GL business unit.

See Analysis Groups.

Inventory

These fields only display if Inventory is installed.

Purchasing

PeopleSoft Maintenance Management requires the installation of PeopleSoft Purchasing to enable users to obtain materials, tools, labor, and other goods and services by creating either a requisition or a purchase order directly from the work order or work order workbench. You can also create a requisition or purchase order in PeopleSoft Purchasing and link it to a work order. If you prefer to use PeopleSoft eProcurement, you can create a requisition directly in PeopleSoft eProcurement from the work order or you can load and stage scheduled rows and create requisitions, which can be accessed in PeopleSoft eProcurement.

Labor Rates

Note. You can override these rates for a specific shop at the shop level, as well as associate specific crafts and craft labor rates with a shop.

GIS Integration

Mobile Integration

See Mobile Web Services Integration.

Entering Preventive Maintenance Parameters for a Work Order Business Unit

Access the PM Options page (Select the PM Options tab in the work order business unit Definition component.)

Calendar	Select a business calendar to use in determining valid business days for preventive maintenance work orders that are generated for this business unit. Selecting this option enables you to avoid scheduling preventive maintenance work orders on holidays or weekends.
Priority Code	Select H (High), M (Medium), or L (Low) to appear as the default priority in any preventive maintenance work order that the application automatically creates for this business unit. This is a required field. Important! This default value appears for all work orders except for work orders that you create for a project for a Project Costing-managed project. See Setup and Processing of Preventive Maintenance Work Orders.
Work Order Type	Select the work order type that you want to use as the default value in any preventive maintenance work orders that the application generates for this business unit. This is a required field.
Task Status	Select the work order task status for a work order task that you want to appear as the default value for any preventive maintenance work orders created during Preventive Maintenance processing that are associated with this business unit. You can select any user-defined work order task status except for those that you defined for the internal statuses of complete, closed, and canceled. This is a required field. See Understanding Work Order Statuses.
Last PM Schedule ID	This identifies the last number used to create a preventive maintenance schedule and automatically increments each time a new preventive maintenance schedule is created. See Setup and Processing of Preventive Maintenance Work Orders.
Enable Workflow Approval	Click the Workflow Approval radio button to enable the workflow approval process.

Setting Up Resource Assignment Approval Options in PeopleSoft Maintenance Management

To set up resource assignment approval options use the Work Order Options (WM_BUS_UNIT_OPT) component.

This section provides an overview of labor resource assignment approval workflow and discusses how to define resource assignment approval options.

Understanding Labor Resource Assignment Approval Workflow

For a work order task, you have the option of approving the assignment of labor resources who are associated with a shop that is different from the shop associated with the work order. The employee data, regardless of the source, identifies the supervisor of each employee. You can also set up employee data and identify the supervisor of an employee using the Manage Employee Data component in PeopleSoft Maintenance Management. When you set up the Work Order Options component to indicate that assignment approval is required, this automatically activates the assignment approval workflow. Once this approval workflow is activated, then when you create a work order task and assign a labor resource who works for a shop other than the shop in the work order, the system sets the assignment to Pending Approval status and sends the assignment to the worklist of the supervisor of the resource for approval. The supervisor is identified in the resource's Employee Data. The supervisor can approve or reject the assignment. If the supervisor approves the assignment, the system sets the assignment approval status to Assigned. If the supervisor does not approve the assignment, the system sets the assignment approval status to Rejected. Only the supervisor of the resource can save an assignment with a status of Assigned.

In addition, you can set up E-mail notifications to the manager of a resource and to the resource being assigned. You can select one or more assignment statuses that trigger an E-mail notification to the manager of the resource and to the resource.

For example, Jim Dobson is identified in Jill Stanton's Employee Data as her supervisor and Jill is assigned to Shop A. Tyler Jones is identified as the manager of Jill Stanton. You set up the Work Order Options page to require assignment approval and you indicate that you want to notify Jill's manager, Tyler Jones, when Jill is Assigned to the task. You also indicate that you want to notify Jill when the assignment is either Pending Approval, Assigned, or Rejected.

When you create a work order with Shop B and assign Jill Stanton as the technician on a task, then the worklist for Jill's supervisor, Jim Dobson, is updated to indicate that the assignment of Jill Stanton is Pending Approval. Based on the notification setup, Jill also receives an E-mail notifying her that the assignment is Pending Approval. When Jim Dobson approves the assignment, a E-mail is sent to Jill notifying her that the assignment is Approved, and an E-mail is sent to Jill's supervisor, Jim Dobson, indicating that the assignment is Approved.

Sample Supervisor/Manager Notification

The following information is an example of the notification sent to the manager designated in the Options page:

Assignment # 0000000263 has been created for Ng, Edward

Work Order Business Unit: US001

Work Order ID: 0000000001

Requestor: Edward Ng

Assignment Description: Replace tires on dump-truck.

Required Start Date: 07–01–2005 Required End Date: 07–01–2005

Project: Truck Maint - QTR 3

Work Order Task Scheduler: Jon Renquist

Work Location: US001 – San Francisco

Assignment Detail:

Schedule Start Date: 07:01:2005 Time: 8 a.m., End Date: 07–01–2005 Time: 5 p.m. for 8 hours

Sample Resource Notification

The following information is an example of the notification sent to the resource designated in the Options page:

Your assignment # 0000000263 has been created for:

Work Order Business Unit: US001

Work Order ID: 0000000001

Requestor: Edward Ng

Assignment Description: Replace tires on dump-truck.

Required Start Date: 07–01–2005 Required End Date: 07–01–2005

Project: Truck Maint - QTR 3

Work Order Task Scheduler: Jon Renquist

Contact Name: George Jacobson

Telephone: 415 454–2315

Email ID: gjacobson@california.com

AM Business Unit: US001

Asset ID: TR114423

Asset Description: 1997 40 Ton Ford Dump Truck

Asset Location: US001 – San Francisco

Work Location: US001 – San Francisco

Assignment Detail:

Schedule Start Date: 07:01:2005 Time: 8 a.m., End Date: 07–01–2005 Time: 5 p.m. for 8 hours

Page Used to Set Up Resource Assignment Approvals

Defining Resource Assignment Approval Options

Access the Work Order Options page. (Select Set Up Financials/Supply Chain, Business Unit Related, Maintenance Management, Work Order Options. )

These options are set up by setID, which means that they can apply to all work orders regardless of their business unit or other required fields.

Assignment Approval Options

E-mail Notification Options

You can enable E-mail notifications to notify a resource's supervisor/manager and the resource about changes in the assignment status.

Setting Up PeopleSoft Maintenance Management Work Order Parameters

To set up:

• Work order types use the Work Order Type (WM_WO_TYPE) component.

• Service groups use the Service Group (WM_SRVC_GRP) component.

• Work order priorities use the Work Order Priority (WM_PRIORITY) component.

• Maintenance types use the Maintenance Type (WM_MAINT_TYPE) component.

• Downtime reasons use the Downtime Reason (WM_DWNTIME_RSN) component

• Failure impact codes use the Failure Impact (WM_FAILURE_IMPACT) component.

• Failure severity codes use the Failure Severity (WM_FAILURE_SEVRTY) component.

This section provides an overview of work order types, service groups, priorities, maintenance types, and downtime reasons and discusses how to:

• Create work order types.

• Create work order service groups.

• Establish work order priority codes.

• Set up asset maintenance types.

• Define asset downtime reasons.

• Define failure impact codes.

• Set up failure severity codes.

Understanding PeopleSoft Maintenance Management Work Order Parameters

Work order types and service groups are used to categorize work orders, work order data, and work order behavior. Maintenance types and downtime reasons are attributes describing the selected asset.

Work Order Types

Work order types are user-defined and specify in general terms the kind of work performed within the work order. Work order type is an element in each of the default hierarchies defined in the work order business unit. It is used to identify some of the basic functionality of the work order, which includes:

• The distribution accounting template that the work order uses.

• The distribution template rules setup.

• The associate projects setup.

• The grace period for closing a work order and work order task.

• The use or nonuse of chargebacks in a work order.

• The default commitment rule for inventoried materials.

• The display of project-related fields in the work order.

• The work order workflow approval options.

Service Groups

Service groups are used to group work orders by major categories such as Fleet, IT, and Facilities. A service group is required when you create a work order. While a work order business unit is not specifically associated with a service group, it may be used in conjunction with several service groups. A default service group may be set up in a work order business unit. Service groups help define certain work order behaviors, such as:

• Triggering the relevant data that displays in the work order at both the task level and the asset lookup level.

• Identifying the defaulting ChartField distribution templates in the work order for each of the resource types: labor, parts, materials, and tools.

  Note. You set up ChartField distributions to enable you to perform manual allocations to GL to generate accounting entries.

• Applying the ChartField distribution template rules to the work order.

• Enabling the Project ID default value in the work order based on the setup of the Associate Projects component.

Priorities

You set up priorities for work orders to identify each work order's level of urgency or importance to a scheduler or technician. Examples of priorities are high, medium, and low.

Note. Service request priorities are system-defined values (Critical, Urgent, Standard, and Low). Users cannot define them.

Maintenance Types

Maintenance types are defined in PeopleSoft Asset Management. They identify the type of maintenance and maintenance procedures that should be followed for a particular asset. For example, you might establish a Tune Up maintenance code that specifies routine maintenance for an automobile. In PeopleSoft Maintenance Management, you must associate one or more maintenance types with an asset type and subtype in order to define a preventive maintenance loop. You can set up a maintenance type as a default value in the work order business unit, which displays in the Maintenance Type field on the Miscellaneous page of the work order. This field must be entered before you can close preventive maintenance work orders.

Downtime Reasons

You can enter the downtime for an asset and select a reason for the asset downtime for each work order task. When a work order is closed, the Work Order Close process updates the total of downtime hours in the asset maintenance history using the data that you entered on the work order. Work order close does not, however, update the start and end downtimes in PeopleSoft Asset Management.

Note. There is a link to enter downtime on the Actual Task Dates tab of the Technician Workbench.

Failure Tracking Setup

You define failure severity and failure impact codes based on the requirements of your organization. When you perform a failure analysis, you can select failure severity and failure impact codes to search for specific failure events to analyze on the Failure Analysis page. PeopleSoft Maintenance Management delivers sample data that contains examples of these two types of failure codes. You can use this sample data to help you define your own failure codes.

You must set up failure severity codes for your organization before you can track failure events in PeopleSoft Maintenance Management. Each code describes the seriousness of the asset failure to your organization. For example, you could define failure severity codes as critical, high, medium, low, or none or with numerical values. You are required to select a failure severity code on the Work Order Failure Tracking page.

Failure impact codes are useful for identifying how the failure of an asset will affect specific organization circumstances or requirements such as hazardous conditions or materials, health issues, safety issues, and more. You can assign more than one failure impact code to a failure event on the Work Order Failure Tracking page. However, you are not required to set up failure impact codes to complete the Work Order Failure Tracking page.

Pages Used to Set Up Work Order Types, Service Groups, and Priorities

Creating Work Order Types

Access the Work Order Type page. (Select Set Up Financials/Supply Chain, Product Related, Maintenance Management, Setup, Work Order Type.)

Work Type	Enter and describe each type of work order that you use in your organization such as Ad Hoc, Preventive, Capital.
Chargeback	Select one of these values: Default Selecting this value means that the system applies the value specified in the work order business unit to any work order that you create with a specific business unit. Specify Selecting this value enables you to select the Generate Chargeback check box, which means that you can generate chargebacks for any work orders that you create using this work order type.
Close Days Task	Select one of these values: Default Selecting this value means that the value that you specify at the business unit level applies to any work order that you create with a specific business unit. Specify Selecting this value enables you to specify the number of days between the completion of a work order task and its closing. This value applies to every work order that you create using this work order type.
Enable Workflow Approval	Select one of these values: Default Selecting this value means that the system bypasses the work order type based on the default hierarchy that you selected in the business unit, and looks at the values at the shop and work order business unit levels. Specify Selecting this value enables you to click either the Pre-Approved option, which means that work orders that you create using this work order type are always pre-approved. Or click the Workflow Approval option if you want to require the approval of work orders that you create using this work order type based on the established workflow approval process. This specification is used depending on the default hierarchy selected in the work order business unit.

See Understanding the Work Order Approval Workflow Architecture.

Creating Work Order Service Groups

Access the Work Order Service Group page. (Select Set Up Financials/Supply Chain, Product Related, Maintenance Management, Setup, Service Group.)

Service Group

Enter and describe each type of service group, such as IT and Facilities, to use for defining specific work order behaviors. See Understanding Work Order Business Unit Setup.

Establishing Work Order Priority Codes

Access the Work Order Priority page. (Select Set Up Financials/Supply Chain, Product Related, Maintenance Management, Setup, Work Order Priority.)

Priority Code

Enter a level of priority such as High, Medium or Low or whatever values are meaningful to your organization. When you create a work order, you select its level of priority in relation to other work orders.

Setting Up Asset Maintenance Types

Access the Maintenance Type page. (Select Set Up Financials/Supply Chain, Product Related, Maintenance Management, Setup, Maintenance Type.)

SetID and Asset Type and Asset Subtype and Description and Short Description	Access the Maintenance Type component, enter the setID and select the Asset Type and Subtype.
Maintenance Type	Add one or more rows of maintenance types to associate with the selected Asset Type and Asset Subtype.

Defining Asset Downtime Reasons

Access the Downtime Reason page. (Select Set Up Financials/Supply Chain, Product Related, Maintenance Management, Setup, Downtime Reason.)

Downtime Reason	Enter the abbreviated reason that an asset is unavailable for use.
Description	Provide a longer description of the reason for the asset downtime.

Defining Failure Impact Codes

Access the Failure Impact page. (Set Up Financials/Supply Chain, Product Related, Maintenance Management, Setup, Failure Impact, Failure Impact)

SetID andFailure Impact	Select a SetID and enter an identifiable code to define a circumstance or requirement that can be impacted by a failure event on the Failure Impact Codes - Add a New Value page such as ASST to represent Asset Life Cycle.
Description andShort Description	Enter a long and a short meaningful description of the entered failure impact code such as Asset Life Cycle impact. If you choose to define a failure impact code, these are both required fields.

Setting Up Failure Severity Codes

Access the Failure Severity page. (Set Up Financials/Supply Chain, Product Related, Maintenance Management, Setup, Failure Severity, Failure Severity)

SetID and Failure Severity	Select a SetID and enter a code up to five characters that best represents a level of the severity on an asset failure to your organization on the Add a New Value page. For example 1, 2, 3.
Description and Short Description	Enter a meaningful long and short description of this failure severity code such as Critical, High, Medium or a definition of a numerical failure severity code, if you used numbers to define these codes. These are both required fields.

Setting Up Rules and Data Related to PeopleSoft Project Costing

To set up:

• Associate projects use the Associate Projects (WM_PC_DFLT_PRJ) component.

• PeopleSoft Project Costing ChartField mappings use the Default PC ChartFields (WM_PC_DFLT_CFS) component.

• Capitalization rules use the Capitalization Rules (WM_PC_CAP_INTGRTN) component.

This section provides an overview of PeopleSoft Project Costing related rules and data in PeopleSoft Maintenance Management and discusses how to:

• Associate projects with a work order business unit, work order type, and service group.

• Set up default PeopleSoft Project Costing ChartFields.

• Define work order capitalization limits.

• Associate capitalization filters with an asset.

Understanding Project Defaulting and Capitalization Rules in PeopleSoft Maintenance Management

This section discusses:

• Project defaulting in work orders.

• Capitalization rules for work order-managed projects.

Project Defaulting in Work Orders

A project ID displays in the work order header and an activity ID displays in the work order task for work orders that are created from PeopleSoft Project Costing. To display this information in the work order and work order task, you must map the project IDs with the Project Costing business unit that is specified in Integrations page of the work order business unit, as well as map these values to a work order business unit, work order type, and service group.

Default Project Costing ChartField Template

PeopleSoft Project Costing has its own set of ChartFields that are used to sort costs for Projects. These ChartFields are different from ChartFields used for accounting entries in PeopleSoft General Ledger and do not impact the flow of costs into PeopleSoft General Ledger. You can edit everything except the Project Costing business unit, project ID, and activity ID.

This template is used to load defaulting Project ChartField values to each work order distribution row and applies to both work orders associated with work order managed projects and Project Costing managed projects. Users can override these ChartField values for each resource row, if desired. These ChartFields are carried over to PeopleSoft Purchasing, PeopleSoft Payables, the time entry infrastructure shared with PeopleSoft Expenses, and PeopleSoft Inventory along with the accounting ChartFields. Tools integrates directly with PeopleSoft Project Costing and uses this template. You can map a specific project to an integration module, resource type, source type, category and subcategory for a work order business unit, work order type and service group. You can enter wildcards for the work order type and service group values.

Capitalization Limits for Work Order-Managed Projects

You set up the capitalization limits to establish a minimum amount that it costs to repair or maintain an asset in a work order before PeopleSoft Project Costing capitalizes the costs. For example, if facility repairs have a capitalization limit of $500, this means that you must spend a minimum of $500 on a facility repair work order task before the costs of that repair are capitalized in PeopleSoft Project Costing and sent to PeopleSoft Asset Management. You must specify the Asset Business Unit and the asset currency code for which the capitalization of costs is calculated. This feature only applies to work orders associated with work order-managed projects and not work orders associated with Project Costing-managed projects.

The following table is an example of capitalization limit setup:

Capitalization Filters for Work Order-Managed Projects

PeopleSoft Project Costing uses capitalization filters to capitalize costs for work orders that are associated with Project Costing-managed projects. However, to enable PeopleSoft Project Costing to capitalize costs used in work orders associated with work order-managed projects, you must select an adjustment filter and a retirement filter, which are defined in Express Asset Criteria in PeopleSoft Project Costing, for an asset type and subtype in the WO Capitalization page in PeopleSoft Maintenance Management. You associate these filters with the Project Costing business unit that is specified in the work order business unit. The adjustment filter is user-defined, and you can set one up in PeopleSoft Project Costing, for example, so that PeopleSoft Project Costing only capitalizes the material costs to the asset. The retirement filter is used for PeopleSoft Project Costing to calculate the cost of removal for an asset.

Note. You must run the Cost Summarization process after the PeopleSoft Project Costing runs the Capitalization process to view the Capitalized Amount on the Capitalization inquiry in PeopleSoft Maintenance Management.

Pages Used to Set Up Rules and Data Related to Project Defaulting

Associating Projects with a Work Order Business Unit, Work Order Type, and Service Group

Access the Work Order - Projects Association page. (Select Set Up Financials/Supply Chain, Product Related, Maintenance Management, Accounting Defaults, Associate Projects.)

Business Unit	Enter the work order business unit that you want to associate with these projects.
Work Order Type and Service Group	Enter a specific work order type and service group to associate with these projects or you can use a wildcard (%) for all work order types. The system weights these fields with the wildcard taking precedence over a specified value. See Work Order Business Unit Defaults and Default Hierarchies.
Effective Date	Enter the date that this setup became effective. This date is checked against the start date in the work order to assure that you can apply these rules to the work order.
PC Business Unit (Project Costing business unit)	This value defaults from the value entered in the work order business unit's Integrations page.
Project	Select the option next to the project ID that you want to be the default value in the work order.

Setting Up Default Project Costing ChartFields

Access the Work Order Project ChartField Mapping page. (Select Set Up Financials/Supply Chain, Product Related, Maintenance Management, Accounting Defaults, Default PC ChartFields.)

Project	Select the project with which to associate these ChartFields.
Integration Module	Select either: Project Costing. Inventory. PO/AP. Expenses.
Resource Type	Select: Labor for PeopleSoft Expenses and PO/AP. Tools for PeopleSoft Project Costing. Material for PO/AP and PeopleSoft Inventory.
Source Type	Select the PeopleSoft Project Costing source type ChartField value. See Source Types.
Category and Subcategory	Select the category and subcategory to associate with this source type. See Categories and Subcategories.

Defining Work Order Capitalization Limits

Access the Capitalize Limit page. (Select Set Up Financials/Supply Chain, Product Related, Maintenance Management, Accounting Defaults, Capitalization Rules.)

Effective Date	Enter the date that the information in this page becomes effective. The system checks this date against the work order start date.
AM Business Unit (Asset Management business unit)	Select the Asset Management business unit to which this cost capitalization limit amount applies. A default book and currency code that are set up set up for this business unit in PeopleSoft Asset Management display.
Default Book	The default book associated with the Asset Management business unit displays for reference purposes. See Defining Business Unit/Book Feature Options.
Currency Code	Displays the currency code based on the currency code specified in the default book of the Asset Management business unit, which PeopleSoft Project Costing uses when capitalizing the asset This can be a different code from the code set up in the work order business unit.
Capitalization Minimum	Enter the minimum cost of repairing this asset in a work order task before the task become eligible for Capitalization. PeopleSoft Project Costing capitalizes the costs.

Associating Capitalization Filters with an Asset

Access the Capitalize Filter page. (Select the Capitalize Filter tab.)

PC Business Unit (Project Costing business unit)	Select the PC business unit to which you want to associate specific PeopleSoft Project Costing filters that the system uses to determine which costs to capitalize or count as costs of removal for a work order.
Adjustment Filter	Select a user-defined filter. This filter determines which of the asset repair or maintenance costs to capitalize. Note. Filters are defined in the Express Asset Filter component in PeopleSoft Project Costing setup.
Retirement Filter	This filter identifies the cost of removal of an asset that is being disposed using a work order task. The system uses this filter for asset gain and loss calculations.

Setting Up ChartField Distributions for PeopleSoft Maintenance Management

To set up PeopleSoft Maintenance Management ChartField distributions, use the Distribution Template (WM_DIST_TMPL) component.

This section provides an overview of ChartField distribution setup and discusses how to:

• Set up a distribution template.

• Set up distribution template rules.

Understanding ChartField Distribution Setup in PeopleSoft Maintenance Management

PeopleSoft delivers financial identifiers referred to as ChartFields to group PeopleSoft Maintenance Management activities by their accounting treatments. Organizations must define ChartFields to account for and classify work order-related costs. Although work order ChartField distribution default values are set up prior to the creation of a work order, users can override them, if necessary, in the work order before the system passes them to the feeder systems, such as PeopleSoft Inventory, PeopleSoft Purchasing, and PeopleSoft Expenses with other work order data. Once the system passes these ChartFields to the feeder systems, it inserts them into the transaction documents of the feeder system, and they are then sent to PeopleSoft Project Costing for financial cost tracking, cost capitalization, and cost recovery, including markup and discount, if appropriate. The need to pass along ChartField values to distribution lines in different feeder systems requires slightly different data element requirements for each specific product. For example, PeopleSoft Purchasing and Accounts Payable require the same active ChartFields, while PeopleSoft Inventory requires a transaction group and distribution type codes along with the active ChartFields.

Work in process (WIP) accounting is handled in PeopleSoft Project Costing only for work orders associated with PeopleSoft Project Costing managed projects and not for work orders associated with work order managed projects.

PeopleSoft Inventory only supports one ChartField distribution row for materials. The cost element in PeopleSoft Maintenance Management is not part of this distribution row. For PeopleSoft Inventory stock items, there is always an Inventory distribution row even if the requested item is fully procured through PeopleSoft Purchasing. In this situation, distribution rows exist for both Inventory and PeopleSoft Purchasing in the Materials and Procurement distribution records, because all stock items eventually must have an issue transaction associated with them in order to decrease the PeopleSoft Inventory balance.

The accounting rules in PeopleSoft Project Costing handle the chargeback ChartField distribution setup for a work order business unit. To mark up or discount costs, the system books the costs to the work order organization then charges them to the recipient at the close of a WO task. Alternatively, you can override default ChartField values and charge the as-incurred costs (without discount or markup) directly to other organizations without having to process them via the accounting rules.

If PeopleSoft Maintenance Management integrates with PeopleSoft Expenses for the purpose of labor time entry, the system only allows one distribution row because the labor distribution data in PeopleSoft Expenses is embedded in the time entry structure. The distribution line is generated once you assign a resource to the work order task.

Important! You must set up the integrated modules that you know that you will be using to default distributions properly to the work order. If you do not use tools for a work order, then you do not need to define a value for PeopleSoft Project Costing. You also do not need to all the resource types in PeopleSoft Purchasing if you do not intend to associate or create purchase orders and vouchers with work orders.

Users create a distribution template in PeopleSoft Maintenance Management for a work order business unit, which contains the ChartField distributions and default values for integration with PeopleSoft Inventory, PeopleSoft Purchasing/PeopleSoft Payables, PeopleSoft Expenses, and PeopleSoft Project Costing (for tools) using the Distribution Template component. Tool transactions are sent directly to PeopleSoft Project Costing based on the ChartField combinations that you determine at the task row level.

ChartField Distribution Template Rules

After setting up a distribution template, users can define distribution template rules based on the work order business unit, service group, work order type, asset type, asset subtype, asset business unit, asset ID, and asset location combinations. Users can use wildcards (%) to apply the same template across more than one work order type, service group, and asset location. The accounting default order is set up in the work order business unit, where you can sequence the service group, work order type, asset type, asset subtype, asset location, asset ID, and asset business unit to determine the weighting of each option listed. Defaulting can also occur at the shop level. Users can specify default ChartFields at the shop level that override ChartField defaults brought over from the distribution template. Only the fields that are populated at the shop level override the default values specified in the template. The system does not change any other default template field values.

Users can override the ChartField defaults up to the point that an inventory issue or requisition/purchase order is created and labor and tools usage actuals are entered. In other words, the ChartFields are established from the PeopleSoft Maintenance Management side from the moment that a transaction containing the distributions is generated in any of the feeder systems. However, the feeder systems can override these ChartField values. If the values are overridden in the feeder system, these changes will be sent back to the work order.

ChartField template selection is based on the work order business unit, shop, work order type, service group, asset type, asset subtype, asset business unit, asset id and asset location. The first three are identified on the work order header, the remaining four are identified on the different work order tasks. Generally the system triggers default ChartField distributions at the point of scheduling. If requirements or assignments are not required, then the default distribution occurs when the actuals are recorded.

If assignments are not used, the ChartField distribution line defaulting occurs when you add actual hours or units of measure for labor and tools usage. Entry or update of labor hours in the Technician Workbench populates actuals on the work order. PeopleSoft Maintenance Management looks up the correct default ChartField templates and populates the time record for data integration into PeopleSoft Project Costing. However, if only actuals are recorded, the default values of the distribution lines are directed into the feeder system transaction.

See Work Order Business Unit Defaults and Default Hierarchies.

ChartField Combination Editing

Because other PeopleSoft products use and interface with ChartFields, PeopleSoft Maintenance Management supports combination editing based on transactions that originate from the work order. The groups that are attached to the GL business unit and the ledger group associated with the work order business unit are the combination groups that are used for PeopleSoft Maintenance Management. You can turn off combination editing at the work order business unit level. As long as you turn on combination editing at the work order business unit level, the system validates each row in the work order.

Important! Combination editing is not performed on the ChartField distributions for labor resources, because these ChartFields do not contain an account or alternate account.

Pages Used to Set Up ChartField Distributions for PeopleSoft Maintenance Management

Setting Up a Distribution Template

Access the Distribution Template page. (Select Set Up Financials/Supply Chain, Product Related, Maintenance Management, Accounting Defaults, Distribution Template.)

Integration Module

Set up a template for each product (PeopleSoft Inventory, Payables/PeopleSoft Purchasing, and PeopleSoft Expenses), as well as a template for tools using the PeopleSoft Project Costing Integration Module.

Distribution Lines

Configure the distribution lines for each integration module based on these rules:

• For PeopleSoft Inventory:

  • Users can configure only one distribution line.

  • The PeopleSoft Inventory transaction group associated with the ChartField distribution is not shown on the page because PeopleSoft Enterprise Inventory uses transaction group 231 exclusively for Maintenance Management. This is the default value for all PeopleSoft Inventory transactions related to PeopleSoft Maintenance Management.

  • Users cannot blank out the default fields that were set up in the PeopleSoft Inventory Accounting Rules Template.

• For Payables/Purchasing:

  Users can enter multiple distribution lines and specify the percentage of costs or quantity to allocate to each row. Your choice of Quantity or Amount determines the default values that appear in the PeopleSoft Purchasing schedule row of the work order task. You can modify these values prior to staging the purchase order or requisition schedule row.

Setting Up Distribution Template Rules

Access the Distribution Templates Defaulting Rules page. (Select Set Up Financials/Supply Chain, Product Related, Maintenance Management, Accounting Defaults, Distribution Template Rules.)

You can add multiple rows containing different values.