C1000-141 Process Automation

Process Automation Detailed Explanation

1. Workflow Design and Management

Workflows in Maximo are predefined sequences of actions that automate processes like approvals and assignments. Maximo’s workflow editor lets you design workflows to fit your organization’s needs.

• Creating Workflows: With the workflow editor, you can map out the steps a process needs to follow. For instance, a work order might require multiple approvals before being assigned. You can set up each step in the workflow, from creation to final approval, ensuring that each user involved knows what to do next.

• Setting Approval Nodes and Conditional Branches: Workflows can include approval nodes (steps where someone reviews and approves the task) and conditional branches (where the workflow follows different paths based on certain conditions). For example, if a work order is high-priority, it might require a manager’s approval, while lower-priority work orders skip this step.

• Adding Notification Rules: Notifications can alert users when they need to take action. For example, a notification might be triggered when a new work order is assigned to a technician or when a manager’s approval is required. These notifications keep everyone informed and prevent delays.

• Ensuring Business Logic Alignment: When designing workflows, ensure that they match your organization’s actual processes. A workflow that mirrors real-life operations helps employees understand and use the system more effectively.

Key Takeaways:

• Use workflows to automate complex, multi-step processes.
• Set up approvals and notifications to keep everyone informed.
• Customize workflows to fit the business’s specific needs and logic.

2. Automation Scripts

Maximo supports scripting languages like Jython and JavaScript, allowing you to create scripts that automate repetitive tasks, saving time and reducing errors.

• Field Validation: Scripts can check if entered data meets specific criteria. For example, if a technician enters a completion date that is before the start date, a script can alert them to correct it. Field validation ensures data accuracy.

• Auto-Calculating Field Values: Automation scripts can automatically calculate values for specific fields. For instance, if you have fields for “Quantity” and “Unit Price,” a script can automatically calculate the “Total Cost” whenever those fields are updated. This reduces the need for manual calculations.

• Triggering Notifications: Scripts can trigger notifications based on certain actions or conditions. For example, if a high-priority work order is created, a script can send an immediate notification to the responsible team. This helps ensure urgent tasks are addressed promptly.

• Reducing Manual Tasks: Automation scripts are great for handling small, repetitive tasks, like setting default values for certain fields or updating the status of a work order once a task is complete.

Key Takeaways:

• Use scripts to validate data and perform calculations.
• Trigger notifications automatically to keep the team informed.
• Automate repetitive tasks, freeing up users for more complex work.

3. Conditional Expressions and Automated Actions

Conditional expressions are statements that evaluate to either true or false. In Maximo, you can use these expressions to trigger specific actions only under certain conditions.

• Defining Conditions: For example, a conditional expression might check if a work order’s priority is “High.” If it is, the expression triggers an automatic action, like assigning the work order to a senior technician or sending a notification to a manager.

• Automated Actions: Once a condition is met, Maximo can perform actions without user input. Examples include:

  • Auto-assigning Work Orders: Based on specific conditions (e.g., work order type or priority), Maximo can automatically assign tasks to appropriate team members.
  • Updating Status: Conditional expressions can change the status of records, like updating a work order’s status from “Open” to “In Progress” when it’s assigned to a technician.

• Ensuring Accurate Triggers: When writing conditional expressions, be specific to avoid triggering actions at the wrong times. For example, a poorly written condition could accidentally assign every work order to the same person, regardless of priority.

Key Takeaways:

• Use conditions to trigger actions automatically based on specific data.
• Automate assignments, status updates, and other routine changes.
• Carefully define conditions to avoid unwanted actions.

4. Notifications and Alerts

Notifications and alerts keep relevant users informed about important events in Maximo, reducing delays and improving response times.

• Configuring Notifications: Notifications can be triggered by many events, such as when a new work order is created, an approval is required, or a task is overdue. You can set up Maximo to send notifications via email, SMS, or in-system alerts.

• Alerts for Key Events: For example, if an asset requires urgent maintenance, Maximo can send an alert to the maintenance team. Similarly, if inventory for an essential part falls below a threshold, Maximo can alert the purchasing department to order more.

• Setting Notification Rules: Define rules to determine who receives notifications and under what conditions. For example, notifications about high-priority tasks might go directly to managers, while routine updates only go to team members.

• Using Notification Templates: Maximo allows you to create templates for common notifications. Templates save time and ensure consistent messaging, so each notification has the necessary details, like the task description, due date, and assigned person.

Key Takeaways:

• Set up notifications to inform users about critical events.
• Use rules to target notifications to the right people.
• Create notification templates for efficiency and consistency.

5. Business Rules and Triggers

Business rules and triggers in Maximo ensure that certain actions happen automatically when specific conditions are met, without requiring user input.

• Defining Business Rules: Business rules are pre-defined conditions that automate routine tasks. For instance, if inventory for a part falls below a certain level, Maximo can automatically create a purchase order to replenish stock.

• Event Triggers: Triggers are events that activate a specific action. Examples include:

  • Auto-assigning Tasks: When a work order is created, a trigger can automatically assign it to an available technician, based on workload or skill set.
  • Auto-generating Purchase Orders: If stock levels drop, a trigger can automatically create a purchase order to restock inventory.
  • Changing Status Based on Triggers: For example, when a technician marks a task as completed, a trigger could automatically change the work order’s status to “Closed.”

• Ensuring Efficiency with Automation: Business rules and triggers remove the need for manual intervention, which speeds up processes and reduces human error.

Key Takeaways:

• Define business rules to automate routine tasks, like reordering inventory.
• Use triggers to activate actions based on specific events.
• Automate common workflows to improve efficiency and consistency.

Summary

Process automation in Maximo transforms complex workflows into efficient, automated processes. Here’s a recap:

1. Workflow Design and Management: Create workflows to automate multi-step operations with approval nodes and notifications.
2. Automation Scripts: Use Jython or JavaScript to automate validations, calculations, and notifications.
3. Conditional Expressions and Automated Actions: Define conditions to trigger automated actions, like assigning tasks or updating statuses.
4. Notifications and Alerts: Set up alerts for key events to keep relevant users informed.
5. Business Rules and Triggers: Create rules and triggers to automate responses to specific conditions, like reordering stock or assigning tasks.

By automating processes, Maximo reduces manual tasks, increases efficiency, and ensures that workflows run smoothly from start to finish.

Process Automation (Additional Content)

1. Maximo Cron Tasks (Scheduled Jobs)

Cron Tasks are automated scheduled jobs that execute background tasks in Maximo, reducing manual intervention and ensuring consistent system processes.

1.1 Purpose of Cron Tasks

Cron tasks automate tasks such as:

• Sending notifications (e.g., email daily pending approvals at 8 AM).
• Auto-closing inactive work orders (e.g., close work orders not updated in 30 days).
• Data synchronization with external systems (e.g., syncing ERP financial data every night).

1.2 Examples of Common Cron Tasks

• Report Cron Task:
  • Generates reports on a scheduled basis and sends them via email.
• Escalation Cron Task:
  • Checks overdue work orders and notifies responsible users.
• Reorder Cron Task:
  • Triggers purchase requisitions when stock falls below threshold.

1.3 Configuring a Cron Task

1. Navigate to: System Configuration → Cron Task Setup
2. Select a predefined cron task or create a new one.
3. Define the schedule (e.g., run every day at midnight).
4. Assign relevant parameters (e.g., specify report type for email notifications).
5. Activate the cron task.

2. Escalations (Automated Event Checking & Actions)

Escalations automate business process checks by periodically evaluating conditions and executing predefined actions.

2.1 Purpose of Escalations

• Automatically detect conditions requiring action.
• Trigger notifications, status updates, or approvals when conditions are met.

2.2 Common Use Cases

• Overdue High-Priority Work Orders
  • If a work order remains unassigned for over 24 hours, escalate to a manager.
• Purchase Order Approval Delays
  • If a purchase request remains unapproved for 3 days, notify senior management.
• Asset Retirement
  • If an asset is inactive for over 30 days, automatically set its status to "Retired".

2.3 How to Configure an Escalation

1. Go to: System Configuration → Platform Configuration → Escalations.
2. Define an Escalation Condition (e.g., work order status = 'Waiting' AND last updated > 24 hours).
3. Set Actions (e.g., send an email notification, change work order priority).
4. Assign Escalation Schedule (e.g., run every hour).

3. Maximo Actions (Automated System Tasks)

Maximo Actions define preconfigured operations that can be triggered by workflows, escalations, or events.

3.1 Purpose of Actions

• Modify record status automatically.
• Update field values dynamically.
• Invoke automation scripts to perform complex operations.

3.2 Common Use Cases

• Auto-Change Asset Status
  • If an asset passes an inspection, change its status from “Pending” to “Active”.
• Auto-Fill Date Fields
  • When a purchase order is approved, automatically set the approval date.
• Trigger Custom Scripts
  • When inventory stock falls below 10, trigger a script that generates a purchase request.

3.3 Configuring Actions

1. Navigate to: Process Automation → Actions
2. Create a new action (Choose type: Status Change, Value Update, Custom Script Execution).
3. Define the conditions for triggering the action.
4. Link the action to workflows, escalations, or event-based triggers.

4. Maximo Integration Framework (MIF) for Automated Data Exchange

Maximo Integration Framework (MIF) enables automated data exchange with external systems.

4.1 Purpose of MIF

• Automates integration with external platforms such as:
  • ERP Systems (e.g., SAP, Oracle) – Auto-import purchase orders.
  • SCADA Systems – Sync asset status updates in real-time.
  • HR Systems – Sync employee data for Maximo user access.

4.2 How MIF Works

1. Data Extraction – Extract Maximo data for external processing.
2. Data Transformation – Convert data to an API-ready format (XML, JSON, CSV).
3. Data Import – Load external system data into Maximo.

4.3 Setting Up MIF

1. Define an Integration Object Structure (e.g., Work Orders, Inventory Records).
2. Create a Publish Channel or Enterprise Service:

• Publish Channel → Sends Maximo data to external systems.
• Enterprise Service → Imports external data into Maximo.

3. Configure Data Exchange Rules:

• Example: Allow only active purchase orders to sync with ERP.

5. Automation Scripts & Event-Based Processing

Maximo Automation Scripts allow custom business logic execution when specific events occur.

5.1 Purpose of Automation Scripts

• Automatically populate fields based on conditions.
• Trigger notifications when specific data changes.
• Perform calculations dynamically.

5.2 Types of Events That Trigger Automation Scripts

• Before Save (Before Save Event):
  • Auto-fill fields before data is committed.
  • Example: Assign the work order owner automatically before saving.
• After Save (After Save Event):
  • Perform actions after a record is saved.
  • Example: After a purchase request is approved, create a linked purchase order.
• Before Delete (Before Delete Event):
  • Prevent deletion of records under certain conditions.
  • Example: Prevent deleting assets that still have active work orders.

5.3 Creating an Automation Script

1. Go to: Automation Scripts → Create New Script

2. Select Event Type (Before Save, After Save, Before Delete).

3. Write a script using Jython or JavaScript.

• Example: Auto-assign a work order owner:

  from psdi.mbo import MboConstants
  if mbo.getString("WOPRIORITY") == "HIGH":
     mbo.setValue("OWNER", "JohnDoe", MboConstants.NOACCESSCHECK)
  

4. Activate the script and test it.

Summary

To fully leverage Maximo Process Automation, administrators should master:

1. Cron Tasks (Scheduled Jobs)

• Automate background tasks such as report generation, stock reordering, and escalations.
• Common cron jobs:
  • Report Cron Task
  • Escalation Cron Task
  • Reorder Cron Task

2. Escalations (Automated Event Checking)

• Periodically check business conditions.
• Trigger alerts and updates based on defined criteria.

3. Maximo Actions (Automated System Tasks)

• Modify statuses, update fields, and trigger scripts automatically.

4. Integration Framework (MIF)

• Automate data exchange between Maximo and external systems (ERP, SCADA, HR).
• Use Publish Channels and Enterprise Services.

5. Automation Scripts & Event-Based Processing

• Trigger scripts dynamically based on system events.
• Enhance workflow automation through custom scripts.