CanMUG Calgary Puts Maximo's Operating Handoffs on the Agenda

CanMUG Calgary's published program connects scheduling, inspections, materials, mobile work, and adoption. Read it as a set of operating handoffs to examine, not as proof that a product demonstration has solved the work between teams.

Share
CanMUG Calgary Puts Maximo's Operating Handoffs on the Agenda

CanMUG Calgary Puts Maximo's Operating Handoffs on the Agenda

A maintenance job does not stay inside the application where it starts. Someone requests material, a planner checks readiness, a scheduler commits capacity, a technician works in the field, and another person accepts the result. Each screen can function correctly while the transfer between people remains ambiguous. That is a useful lens for reading a Maximo user-group program: not simply which features appear, but which operating handoffs the community chooses to discuss.

The published CanMUG Calgary events page lists a two-day in-person conference on October 28 and 29, 2026, at Hudson Downtown Calgary Loft. The organizers describe the format as a pilot based on user feedback, with one ticket covering both days of presentations. The program brings end-user experiences alongside consulting, product, and sponsor-led sessions. This article is a preview based on that published agenda, not a review of presentations that have already happened.

The interesting pattern is the proximity of subjects that organizations often govern separately. Scheduler adoption appears beside inspection forms and material requests. Mobile transformation sits alongside integrated asset operations and turnaround planning. The next day's topics include mapping, the people side of upgrades, an asset copilot pattern, contract management, API automation, and outcome-driven Maximo work. Those titles do not establish implementation details or business results. They do provide a practical structure for discussing where ownership changes during maintenance execution.

The analysis below uses the agenda as its source for session names and contributors. Its operating questions and suggested workshop exercises are recommendations, not claims about what speakers will demonstrate. Sessions can change. The aim is to help practitioners carry a more precise problem into the community conversation: what information, authority, and acknowledgement must cross a boundary before the next team can safely act?

1. Scheduling and materials share a readiness decision

The published first-day program includes YEG's Maximo Scheduler Journey: From GWW Challenges to User Adoption, presented by Di Rushfeldt of Edmonton International Airport with Gurleen Chandi of IBM Consulting. It also includes The Importance of Getting the Material Request Right for DP World, presented by Himanshu Sharma of DP World Canada with Mike Popovic of P2Insight. Later, Dan Robb of Teck Resources is listed for Scheduler Extension for Turn Around and Outage Planning. These are separate agenda entries, not evidence of one common implementation.

Read together, they suggest a question worth taking to a maintenance planning discussion: when does a job become ready enough to schedule? That question crosses both application and organizational boundaries. A requested item is not necessarily an item available at the required place and time. A planned job is not necessarily one whose prerequisites have been accepted. The workshop opportunity is to make those meanings explicit in the organization's own process, rather than infer them from an attractive schedule display.

A proposed exercise is to select a representative job and trace its material assumptions before discussing optimization. Identify who requests the item, who confirms the requirement, who establishes availability, and who authorizes a substitution or accepts a delay. Then identify which of those decisions the scheduler is permitted to rely upon. Use actual process owners to describe the boundary, but use fictional records if the resulting exercise will circulate outside the company. The output should be a clear handoff definition, not a list of favored application screens.

Keep the scheduler's promise separate from the inventory team's promise. One may concern when work is assigned; the other may concern whether the right material can be supplied under the required conditions. If the local process collapses those statements into one readiness status, ask how disagreement is detected and who resolves it. This is a proposed governance question, not an assertion that Maximo lacks an applicable control or that any listed presenter encountered this problem.

For an outage or turnaround discussion, extend the same exercise to a changed assumption. Ask what should happen when a material commitment changes after work has entered the schedule. Which owner is notified, which decision must be reconsidered, and what acknowledgement makes the change complete? The session titles justify examining readiness, adoption, and planning together. They do not justify predicting a presenter's answer. A useful community exchange compares the definitions different teams use and the consequences they manage, while leaving product-specific implementation claims to evidence supplied in the actual session.

2. Inspections and mobile work need an acceptance boundary

The agenda lists The Next Era of Maximo Inspections: Streamlining the Maximo Inspection Process and Implementing Smarter Form Functionality, with Ron Escamilla of Plains All American Pipeline and Thomas Pham of Nxt Era Solutions. It separately lists From Desktop to Field: YEG's Maximo Mobile Transformation, with Justin Moser of Edmonton International Airport and Dean Kees of Cohesive. Neither title establishes a particular form design, deployment topology, offline behavior, or measured productivity improvement. Treat those details as questions for the presenters rather than facts to fill in.

The operating connection is the boundary between captured information and accepted maintenance evidence. A technician can submit a completed form while a supervisor still needs to decide whether a defect requires follow-up, whether a reading is credible, or whether additional work is authorized. A mobile rollout can improve access to the workflow without answering who owns those decisions. The useful workshop problem is therefore not just whether the form reaches the system, but what makes its contents actionable.

Prepare a hypothetical inspection with an expected result, an unexpected result, and an incomplete observation. For each branch, define the next owner and the acknowledgement required before the original task is considered resolved. Keep physical task completion distinct from data submission and from supervisory acceptance. These distinctions are proposed process categories, not a claim about mandatory Maximo statuses. A local implementation may express them through different records, transitions, or operating procedures, and the point is to make that expression visible.

Then test the handoff from the field user's perspective. What information is needed before work starts? What should happen if the task changes while the worker is away from the desk? Which decision can the worker make, and which requires another person's authority? Do not assume a connectivity model from the word mobile. Ask speakers to explain the conditions under which their described process operates, and compare those conditions with the environment in which your own technicians work.

This framing also improves questions about adoption. Instead of asking whether users liked an application, ask which previously ambiguous action became clearer and which exception still requires human coordination. That invites a practical answer without demanding disclosure of sensitive site details. After the event, any internal proposal should preserve the distinction between a demonstrated capability and a locally accepted operating method. A presentation can supply an idea or example; the organization still owns the decision about who reviews a submitted observation, who authorizes the response, and what evidence makes the handoff complete.

3. Maps, copilot patterns, and APIs meet at the action boundary

The second-day program lists Maximo Spatial 101: Unlocking Map Functionality in Maximo Application Suite, with Ken Rodas of Cohesive. It also lists From Dashboards to Daily Actions: A Practical Asset Copilot Pattern for IBM Maximo Users, with Avinash Kumar of TechnoVITY, and Automating the Boring Stuff: Using Maximo APIs to Streamline Daily Workflows, with Graham Wells of Cohesive. These titles describe planned subjects. They do not establish an autonomous agent architecture, a specific API contract, or a particular Spatial configuration.

Their common operating question is what happens between finding a situation and changing work. A map can provide location context, a dashboard or copilot can help present information, and an API can support an interaction between systems. None of those descriptions, by itself, tells a reviewer who is authorized to create a commitment or change a record. Keep observation, recommendation, authorization, and execution separate when discussing an idea drawn from these sessions. That separation is a design recommendation, not a summary of undisclosed presentation content.

A useful hypothetical workshop starts with a person identifying an asset requiring attention. Write down the identifier used to refer to the asset, the site or organizational context needed to interpret it, and the proposed next action. Then ask who confirms that the observed asset and the intended target record are the same. The objective is not to design a map or an AI tool in advance of the talk. It is to identify the information that must survive the transfer from context to action without changing meaning.

For an automation discussion, ask what constitutes an acknowledged outcome. A request being sent is not the same claim as a business record reflecting the intended change. If a request is repeated, delayed, or rejected, which party owns the next step? Those are general integration design questions suitable for a technical conversation. They should not be attributed to a listed speaker as a known failure mode, nor turned into an invented assertion about the APIs that the speaker intends to show.

For the copilot session, preserve the distinction between a pattern and an announced product capability. The agenda's wording supports asking how a recommendation becomes daily action; it does not support claiming that a specific IBM feature has been released or approved for autonomous operation. Invite a concrete explanation of the actor, permission boundary, review point, and acknowledgement. The resulting discussion can connect spatial context, AI-assisted interpretation, and ordinary API reliability without pretending that all three solve the same problem or use the same technical implementation.

4. Upgrade adoption is a transfer of responsibility

CanMUG's published second-day program includes Beyond The Upgrade: Taking Your People on The Journey, Not Just Delivering a System, presented by Allison Quinn and Dhugal Watson of Electra Learning. It also includes Beyond the Expensive Spreadsheet: A Framework for Outcome-Driven Maximo Work, presented by Bassem Bassiouny of Qemyt Consulting. These titles make the people and outcome dimensions explicit in the agenda. They do not supply adoption metrics, training methods, or the content of the proposed framework.

A practical connection between them is the transfer from a project team delivering a configured system to an operating team accountable for daily decisions. That transfer can be described more precisely than a general statement that training is important. Ask which roles become responsible for recognizing exceptions, interpreting readiness, accepting inspection evidence, and escalating failures after the project team leaves. A person who can navigate the interface may still lack authority or a shared definition of what the next action means.

Use a role-based exercise rather than a feature inventory. Choose a maintenance scenario and have the planner, storekeeper, technician, supervisor, and application support owner describe their next action and the evidence they expect from the previous role. Adapt those role labels to the actual organization rather than treating them as a prescribed staffing model. Differences between answers are useful findings. They reveal where the operating method remains unwritten or where the configured workflow is understood differently across teams.

For each disagreement, assign ownership before proposing new automation. Some gaps may need a clarified decision rule; others may need configuration, reference data, or a technical change. The exercise should not assume that education can compensate for an unsuitable process, or that another field on a screen can settle an unresolved authority boundary. Keep the diagnosis attached to the specific transfer that failed in the exercise. That makes a follow-up question to a community contributor much more useful than a broad request for best practices.

Outcome-driven discussion also benefits from clear claim boundaries. Ask what operational decision a proposed change should improve and how the team would recognize the improvement in its own context. Do not attach an invented reduction in downtime, processing effort, or training time to an agenda title. Before the event, record the intended result as a hypothesis. After the event, separate the speaker's demonstrated evidence from the local experiment the team chooses to run. This preserves the value of peer learning without importing another organization's conditions, authority model, or reported experience as though they were already validated at home.

5. Co-presented sessions offer a better implementation conversation

Several first-day entries pair an operating organization with a consulting or solution contributor. The published examples include Edmonton International Airport with IBM Consulting for the Scheduler session, Plains All American Pipeline with Nxt Era Solutions for inspections, DP World Canada with P2Insight for material requests, and PETRONAS Energy Canada with Revisionz for integrated asset operations. The agenda also pairs the airport with Cohesive for the Mobile session. These are named presentation pairings, not evidence about contract scope, project ownership, or commercial arrangements.

For attendees, that structure creates an opportunity to ask two different kinds of question without confusing the answers. The operating practitioner can explain the problem definition and the decisions that mattered in daily work. The technical contributor can explain the configuration or implementation considerations that supported the approach, subject to what the speakers choose to share. Do not assume either person will disclose architecture or performance data merely because both names appear on a program.

A focused question starts with the boundary rather than a request for a success story. Ask how the teams decided that a job was ready, an inspection response was complete, or a field change had been accepted. Follow with a question about how that meaning was represented in the system and how exceptions were handled. This invites a concrete operating discussion while allowing contributors to answer at a level appropriate to a public event. It also reduces pressure to generalize one implementation into a universal recommendation.

Carry the same discipline into follow-up notes. Label whether a point came from the published agenda, an actual presentation, a speaker's answer, or the attendee's own interpretation. If information is shared informally, ask whether it may be quoted or circulated before using it in a wider report. Avoid collecting unnecessary personal details. A community relationship is more valuable when the other participant can trust that an exploratory conversation will not become an attributed technical claim without consent.

Finally, make contributions reciprocal. Bring a clearly described problem, explain the relevant boundary conditions without exposing private operational data, and offer to share the result of a small local experiment when appropriate. The program describes a community of Maximo users and professionals helping one another solve problems and achieve business goals. A useful attendee contribution is therefore not merely another request for free implementation work. It is a well-framed question, an honest statement of what remains unknown, and a willingness to return with evidence that might help the next practitioner facing a similar handoff.

Practical Implications

Before the conference, choose an operating handoff rather than trying to learn every subject on the program. A planning team might choose the transfer from material readiness to scheduled work. A field team might choose the transfer from inspection submission to accepted follow-up. An integration or AI team might choose the transfer from observed information to an authorized action. These are suggested preparation choices, not claims that any specific session will cover every part of the chosen problem.

Write a short scenario showing the sending role, receiving role, information required, decision authority, and acknowledgement. Include an exception so that the conversation is not limited to the successful path. Keep the scenario free of confidential asset, employee, and security information. Use the published agenda to locate relevant conversations, then check the organizer's page again before relying on a particular session or contributor being available.

During the event, distinguish what is actually demonstrated from what the audience infers. Afterward, turn a useful idea into a bounded local trial with a named owner and an explicit acceptance condition. Do not describe an agenda title as evidence that a feature works in your environment.

The goal is not a larger conference notebook. It is a clearer operating agreement that the team can explain, configure where needed, and test without depending on the original presenter to interpret every exception.

Bottom Line

CanMUG Calgary's published program offers a coherent reason to discuss scheduling, materials, inspections, mobile work, maps, AI-assisted patterns, and API automation together: maintenance depends on the transfers between those areas. The agenda establishes the planned subjects and named contributors. It does not establish implementation results, announce new product capabilities, or prove that a particular method will fit another organization.

The strongest use of the event is to bring a precise handoff problem into a peer conversation. Ask what must be true before work changes hands, who has authority to make the next decision, and what acknowledgement closes the transfer. Those questions are technical enough to expose a real design issue and operational enough to keep the discussion connected to maintenance work.

Treat any resulting idea as a candidate for local validation, not a shortcut around it. A community presentation can make a better operating method imaginable. The receiving organization still has to define its boundaries, test its assumptions, and own the decisions that turn the idea into daily practice.