BMC Remedy: The Unsung Hero of IT Operations (and Your Career)

If you’ve spent any time in the IT world, especially on the operations or service delivery side, you’ve almost certainly bumped into a term like “ITSM” or a tool like “Remedy.” For some, it’s the daily command center; for others, it’s a mysterious system that generates tickets. But what exactly is BMC Remedy, and why has it been such a cornerstone of IT service management for decades?

Let’s cut through the jargon and get to the practical understanding.

So, What Exactly is BMC Remedy?

At its core, BMC Remedy isn’t just one thing; it’s a comprehensive suite of applications built on a powerful underlying platform, designed to manage IT services and support business processes. Think of it as the ultimate organizer and taskmaster for an IT department. Its main goal? To help organizations deliver IT services efficiently, consistently, and reliably.

Historically, when we say “BMC Remedy,” people often mean the BMC Remedy ITSM Suite. This suite includes applications like Incident Management, Problem Management, Change Management, Asset Management (CMDB), and Service Request Management. These modules work together, often seamlessly, to cover the entire lifecycle of an IT service request or issue.

The “Remedy” part itself comes from the BMC Remedy AR System (Action Request System). This is the low-code development platform that the ITSM applications are built upon. It’s the engine underneath the hood, responsible for managing forms, workflows, database interactions, and integrations. Understanding the AR System is crucial for anyone who wants to customize, administer, or really understand how Remedy works at a deeper level.

Over the years, BMC has evolved Remedy. While the classic “Remedy ITSM Suite” running on-premises is still in use by many large enterprises, BMC’s modern offering has moved towards a cloud-native platform called BMC Helix ITSM. Helix builds on the robust foundation of Remedy but adds AI capabilities, cognitive automation, and a much more modern user experience, often delivered as a SaaS solution. So, when you hear “Remedy,” it could refer to the traditional suite, the AR System platform, or the modern Helix iteration. For the purposes of this article, we’ll mostly focus on the classic ITSM suite and its underlying principles, which remain highly relevant even with Helix.

Why Does Remedy Matter in the IT World?

Imagine an IT department without any structured way to handle user requests, track equipment, or plan system changes. Chaos, right? Emails flying everywhere, forgotten tasks, miscommunications, and a general sense of things falling through the cracks. This is precisely what tools like Remedy aim to prevent.

Here’s why Remedy (and ITSM tools in general) are indispensable:

• Centralized Operations: It provides a single source of truth for all IT-related activities. Incidents, problems, changes, and assets are all managed in one system, making it easier to track, report, and audit.
• Standardization and Process Enforcement: Remedy embeds ITIL (Information Technology Infrastructure Library) best practices into its modules. This means it helps enforce standardized processes for how incidents are handled, how changes are approved, and how services are requested. This standardization leads to consistency and predictability.
• Improved Service Delivery: By streamlining processes, automating tasks, and providing agents with the right information (through a knowledge base or CMDB), Remedy helps IT teams resolve issues faster and deliver services more efficiently. This translates directly to better service for end-users.
• Reduced Risk: Especially in Change Management, Remedy helps manage and mitigate risks associated with system changes. By requiring proper approvals, impact assessments, and scheduled rollout windows, it prevents unexpected outages and service disruptions.
• Enhanced Decision Making: With all data flowing into one system, Remedy provides rich reporting capabilities. You can analyze incident trends, problem root causes, change success rates, and asset utilization. This data empowers IT leaders to make informed decisions about resource allocation, infrastructure investments, and process improvements.
• Compliance and Auditing: For regulated industries, having a robust system to track all IT activities is critical for demonstrating compliance with various regulations (e.g., SOX, HIPAA, GDPR). Remedy provides a detailed audit trail for every action taken.
• User Satisfaction: A well-implemented Remedy system, especially with a user-friendly self-service portal (Service Request Management), empowers users to find answers themselves or quickly submit requests, leading to a much better experience than sending a vague email into the abyss.

Core Concepts: The Building Blocks of Remedy

To truly understand Remedy, you need to grasp its fundamental components.

AR System (Action Request System): The Engine Under the Hood

The AR System is the core platform upon which all BMC Remedy applications are built. It’s a powerful and flexible workflow engine that allows organizations to automate and manage complex business processes without extensive coding.

• Forms: These are the user interfaces where data is entered and displayed. Think of them as the web pages or windows you interact with in Remedy. Every incident, change, or asset record sits on a form.
• Fields: These are the individual data entry points on a form (e.g., Incident ID, Summary, Status, Assigned To). Fields have properties like data type (text, integer, date), maximum length, and whether they are required.
• Workflow: This is where the magic happens. AR System workflow consists of various components that automate processes:
  • Filters: Server-side automations that execute when data is created, modified, or deleted on a form. They perform actions like setting field values, pushing data to other forms, or validating user input. For example, a filter might automatically assign an incident to a specific support group based on the service selected.
  • Active Links: Client-side automations that respond to user actions in the browser (e.g., clicking a button, changing a field value). An active link might hide or show certain fields based on user input or open a new window.
  • Escalations: Time-based automations that run at scheduled intervals. They’re often used for reminding agents about overdue tickets, escalating incidents that haven’t been touched in a while, or generating reports.
• Database Interaction: The AR System abstracts the database layer, meaning developers and administrators interact with forms and fields rather than directly with database tables. The AR System handles all the underlying SQL queries, making it easier to build applications without deep database expertise.
• APIs and Integrations: The AR System provides robust APIs (Application Programming Interfaces) that allow Remedy to integrate with other systems, such as monitoring tools, HR systems, or other ITSM platforms. This ensures that Remedy doesn’t operate in a silo.

Understanding the AR System is vital because it explains how Remedy behaves. When an incident gets routed to the right team or a status changes automatically, it’s the AR System’s filters and active links doing the heavy lifting.

The ITSM Modules: Daily Operations

These are the applications that IT teams and end-users interact with daily.

• Incident Management

  This module focuses on restoring normal service operation as quickly as possible and minimizing the adverse impact on business operations. An incident is an unplanned interruption to an IT service or a reduction in the quality of an IT service.

  • Practical Example: A user calls the help desk saying, “My email isn’t working.” The help desk creates an incident ticket, classifies it (e.g., “Email – Outlook”), assigns it to the appropriate team (e.g., “Messaging Support”), and tracks its progress until resolution.

• Problem Management

  This module aims to reduce the likelihood and impact of incidents by identifying the root causes of problems and preventing recurrence. A problem is the cause of one or more incidents.

  • Practical Example: If the help desk receives 50 incidents in a week about email not working, Problem Management might investigate if there’s an underlying issue, like a faulty email server or a misconfigured firewall rule, rather than just fixing individual email clients.

• Change Management

  This module ensures that standardized methods and procedures are used for efficient and prompt handling of all changes, minimizing the impact of change-related incidents upon service quality. A change is the addition, modification, or removal of anything that could affect IT services.

  • Practical Example: The networking team needs to upgrade a core router. A Change Request is created, detailing the plan, risks, back-out procedures, and required approvals from various stakeholders (e.g., management, security, application owners) before the change can be scheduled and implemented.

• Asset Management (and CMDB – Configuration Management Database)

  This module tracks the lifecycle of IT assets (hardware, software, network devices) and manages their relationships. The CMDB is a critical repository that contains information about all Configuration Items (CIs) that make up an IT service and their interdependencies.

  • Practical Example: The CMDB would contain records for every server, laptop, printer, and software license. If a server goes down, an incident ticket can be linked to that specific server’s CI in the CMDB, immediately providing support staff with details like its location, associated applications, and last maintenance date.

• Service Request Management (SRM)

  This module provides a single point of entry for users to request standard IT services (e.g., “I need a new monitor,” “I need access to a specific application,” “Reset my password”). It often involves a self-service portal and a service catalog.

  • Practical Example: A new employee joins the company. Their manager submits a service request for a new laptop, standard software, and network access via the Remedy Self-Service Portal. This triggers automated workflows to provision these items.

• Knowledge Management

  This module creates, stores, and manages a knowledge base of solutions, workarounds, known errors, and how-to guides. It supports both end-users (through self-service) and IT staff (for quick problem resolution).

  • Practical Example: Before contacting the help desk, a user might search the knowledge base for “How to connect to the VPN” and find an article with step-by-step instructions. An IT agent might find a workaround for a known email issue.

Real-World Examples: Seeing Remedy in Action

Let’s walk through a few scenarios to bring Remedy to life.

The Busy Help Desk and a Puzzling Printer Problem

Sarah, a marketing manager, logs an incident in the Remedy Self-Service Portal: “My office printer isn’t working.”

1. Incident Creation: The system automatically creates an Incident ticket. It captures details like Sarah’s name, department, affected service (“Printing”), and a description.
2. Automated Routing: Based on the service selected (“Printing”) and Sarah’s location, a Remedy filter automatically assigns the incident to the “Office IT Support – Floor 3” team.
3. Agent Action: John, an IT support engineer, picks up the ticket. He sees that Sarah’s printer, “PRN-MKTG-FLOOR3,” is linked as a Configuration Item (CI) from the CMDB. He checks the CMDB to see its model, IP address, and recent maintenance history.
4. Knowledge Base Search: John quickly searches the Remedy knowledge base for common issues with that printer model. He finds an article: “PRN-MKTG Series: Paper Jam Error Code F01.”
5. Resolution: John guides Sarah through clearing a paper jam, and the printer starts working. He updates the incident with the resolution steps, links the knowledge article, and resolves the ticket.
6. User Confirmation & Closure: Sarah confirms the fix, and the incident is automatically closed after a set period.

The Critical Server Upgrade

The server team needs to upgrade the operating system on a critical production database server.

1. Change Request Submission: The server team submits a Change Request in Remedy. They detail the purpose, affected server (linked from CMDB), planned start/end times, back-out plan, and potential impact.
2. Impact Assessment & Approvals: Remedy workflows route the change for approval. The database team reviews it for potential conflicts. The security team checks for compliance. The application owners verify that their applications will function post-upgrade. Management approves the maintenance window.
3. Scheduled Change: Once approved, the change is scheduled. Remedy automatically creates a “blackout window” in its calendar to prevent other conflicting changes. Notifications are sent to affected users and teams.
4. Implementation: During the approved window, the upgrade is performed.
5. Post-Implementation Review: After the change, the team updates the change request with success/failure status and any lessons learned. If an issue occurred, an incident and potentially a problem ticket might be linked back to this change. The CMDB is updated with the new OS version for the server CI.

Onboarding a New Employee: A Streamlined Process

HR hires a new employee, Alex.

1. Service Request Initiation: HR submits a “New Employee Onboarding” service request through the Remedy Self-Service Portal. They provide Alex’s details, department, and required role-specific software.
2. Automated Fulfillment: Remedy kicks off a series of automated workflows:
   • An incident is created for IT to provision a laptop.
   • Another task is created for the network team to set up network access.
   • Software installation requests are generated for the specific applications Alex needs.
   • A task is created for facilities to prepare Alex’s desk.
3. Status Tracking: Alex’s manager can track the progress of the service request directly in the portal.
4. Completion: As each task is completed by different teams, the service request progresses, and upon completion of all tasks, Alex is ready to start on day one with all necessary tools and access.

Practical Scenarios: Day-to-Day with Remedy

Let’s look at how different IT roles interact with Remedy.

As an IT Support Engineer

You’re at the front lines. Your day revolves around:

• Receiving and Updating Incidents: New tickets constantly flow into your queue. You’ll update statuses (e.g., “Assigned,” “In Progress,” “Pending User”), add work notes detailing troubleshooting steps, and link related CIs.
• Escalating Tickets: If you can’t resolve an issue, you’ll escalate it to a higher-tier support group within Remedy, ensuring proper documentation and ownership transfer.
• Using the Knowledge Base: Before starting complex troubleshooting, you’ll search for existing solutions in Remedy’s knowledge base. If you discover a new solution, you might contribute to the knowledge base.
• Creating Change Requests: If a solution requires a system change (e.g., a software patch), you might initiate a change request or link your incident to an existing one.
• CMDB Consultation: You’ll constantly use the CMDB to understand the infrastructure components related to an incident. “Which applications run on this server? Who owns that switch?”

As a Change Manager

Your role is to ensure stability and minimize risk:

• Reviewing Change Requests: You’ll meticulously review change requests submitted by various teams, checking for completeness, impact analysis, and adherence to change policies.
• Approving/Rejecting Changes: Based on risk, impact, and compliance, you’ll approve or reject changes, often after coordinating with Change Advisory Board (CAB) meetings.
• Scheduling Changes: You’ll ensure changes are scheduled during appropriate maintenance windows and don’t conflict with other critical activities.
• Reporting: You’ll generate reports on change success rates, back-outs, and emergency changes to identify areas for process improvement.

As a Remedy Administrator/Developer

You’re responsible for the health and customization of the Remedy platform itself:

• User and Group Management: Creating new users, managing permissions, and configuring support groups.
• Customization and Configuration: Building new forms, fields, and workflows (filters, active links, escalations) to meet specific business requirements. This might involve adapting out-of-the-box functionality or developing entirely new applications on the AR System.
• Integration Development: Building integrations with other IT systems using Remedy APIs or custom connectors.
• Performance Monitoring and Tuning: Ensuring the Remedy system performs optimally, troubleshooting performance bottlenecks, and maintaining database health.
• Upgrades and Patches: Planning and executing upgrades to new versions of Remedy or applying patches.
• Data Management: Importing and exporting data, ensuring data integrity, especially within the CMDB.

Common Mistakes and How to Avoid Them

Even with a powerful tool like Remedy, things can go wrong.

• Ignoring Process for Tool Functionality: Trying to make Remedy fit a broken or non-existent process. The tool should support a good process, not define it.

  Avoid: Define clear ITIL-aligned processes first, then configure Remedy to enforce them.

• Poor CMDB Data Quality: A CMDB full of outdated or inaccurate information is worse than no CMDB at all. It leads to bad decisions and frustration.

  Avoid: Implement strict data governance, automate data population where possible, and conduct regular audits and cleanup of CMDB data.

• Over-Customization: Heavily customizing Remedy (especially the core ITSM modules) can make future upgrades incredibly difficult and expensive.

  Avoid: Always strive to use out-of-the-box functionality first. Only customize when absolutely necessary and document every modification thoroughly.

• Lack of User Training: If IT staff and end-users aren’t properly trained, they won’t use the system effectively, leading to incorrect data entry, bypassed processes, and underutilization.

  Avoid: Invest in comprehensive training for all user types, provide ongoing support, and create easily accessible user guides.

• Not Using Knowledge Management: Many organizations implement incident and change but neglect the knowledge base, forcing agents to “reinvent the wheel.”

  Avoid: Make knowledge contribution and consumption a mandatory part of the incident resolution process. Reward knowledge sharing.

• Confusing Incidents and Problems: Treating every recurring incident as a new incident rather than investigating the root cause as a problem.

  Avoid: Establish clear criteria for when to escalate an incident to a problem and dedicate resources to problem management.

• Siloed Implementations: Using Remedy effectively but failing to integrate it with other critical IT systems (monitoring, identity management).

  Avoid: Plan for strategic integrations to automate data flow and create a more holistic view of IT operations.

Interview Questions Relevance

Understanding Remedy is a huge plus in many IT roles. Here are some questions you might encounter:

• “What is the primary purpose of Incident Management, and how does Remedy support it?”

  Answer: Explain that it’s about restoring service quickly. Remedy supports this by providing a structured way to log, categorize, prioritize, assign, escalate, and resolve incidents, along with a knowledge base for quick solutions.

• “Explain the difference between Incident and Problem Management.”

  Answer: Incident is about immediate service restoration; Problem is about finding and removing the root cause to prevent future incidents. Link them back to Remedy’s distinct modules for each.

• “What is a CMDB, and why is accuracy critical?”

  Answer: Define CMDB as a repository of CIs and their relationships. Explain accuracy is critical for impact analysis (knowing what’s affected by a change/outage), efficient troubleshooting, and effective asset management.

• “Describe a change process you’ve been involved in, highlighting the role of an ITSM tool like Remedy.”

  Answer: Walk through the lifecycle: request, assessment, approval, scheduling, implementation, review. Emphasize how Remedy streamlines approvals, tracks progress, and provides an audit trail.

• “As an IT support engineer, how would you use Remedy to troubleshoot a recurring user issue?”

  Answer: Start by searching past incidents and the knowledge base. Check the CMDB for related CIs. If it’s truly recurring and widespread, propose creating a problem ticket.

• “What is the AR System, and why is it significant for Remedy customization?”

  Answer: Explain it’s the underlying platform/workflow engine. Its significance lies in allowing low-code customization (forms, fields, filters, active links) without needing to write extensive code, making it adaptable to specific business needs.

Career Opportunities in the Remedy Ecosystem

A strong grasp of Remedy opens doors to various roles:

• Remedy Administrator: The backbone of any Remedy implementation. You’ll manage users, permissions, configurations, basic customizations, and system health.
• Remedy Developer/Customizer: Someone who builds and modifies applications on the AR System platform, creates complex workflows, and integrates Remedy with other systems. This often requires deep AR System knowledge.
• ITSM Business Analyst: Acts as a bridge between the business/IT process owners and the Remedy technical team. They gather requirements and translate them into Remedy configurations.
• Solution Architect: Designs complex Remedy solutions, often involving integrations with multiple systems and aligning the solution with organizational ITSM strategy.
• IT Support Analyst/Engineer: Your daily job will involve working within Remedy’s ITSM modules to resolve incidents, fulfill service requests, and manage changes.
• ITSM Consultant: Advises organizations on Remedy best practices, implementations, migrations, and process improvements.
• Project Manager: Oversees the implementation or upgrade projects of Remedy solutions.

The skills gained working with Remedy are highly transferable, even if you eventually move to other ITSM platforms like ServiceNow or Jira Service Management, as the core ITIL processes remain the same.

Best Practices for Remedy Success

To get the most out of your Remedy investment:

1. Prioritize Process Over Tool: Define your ITIL processes clearly before configuring Remedy. The tool should enable the process, not dictate it.
2. Embrace Out-of-the-Box: Leverage standard Remedy functionalities as much as possible. Customization adds complexity and cost, especially during upgrades.
3. Invest in Training: Don’t just train users once. Provide ongoing training for all roles – end-users, support staff, administrators, and developers – to ensure effective utilization.
4. Maintain a Clean CMDB: Treat your CMDB as a living, breathing entity. Implement processes for continuous data discovery, updates, and audits to ensure its accuracy.
5. Foster a Culture of Knowledge Sharing: Encourage and reward the creation and utilization of knowledge articles. A robust knowledge base significantly improves resolution times and empowers self-service.
6. Integrate Smartly: Identify key systems that Remedy should integrate with (monitoring, identity, HR) to automate workflows, reduce manual effort, and improve data consistency.
7. Regular Review and Improvement: ITSM is not a one-time project. Regularly review your Remedy usage, identify bottlenecks, gather feedback, and implement iterative improvements to processes and configurations.
8. Automate Where Possible: Use the AR System’s powerful workflow capabilities to automate routing, approvals, notifications, and simple tasks, freeing up your IT staff for more complex work.

Summary

BMC Remedy, whether you’re talking about the classic ITSM Suite or the modern Helix platform, has been a central pillar of IT service management for a long time. It provides the structured framework and powerful engine needed to bring order to the inherent complexity of IT operations.

By understanding its core components like the AR System and the various ITSM modules, you gain insight into how IT teams efficiently handle incidents, prevent problems, manage changes, and deliver services. Mastering Remedy isn’t just about learning a tool; it’s about understanding the practical application of ITSM principles that are relevant across the entire IT industry. Whether you’re a fresher starting your career in IT support or an experienced professional looking to streamline operations, a solid grasp of Remedy and its capabilities will make you an invaluable asset in any organization. It’s truly a system that keeps the digital world humming along, often behind the scenes, but always making an impact.