The Sigga alternative for SAP PM teams

Teams evaluating Sigga already have SAP PM as the central maintenance record. PM Run is the execution layer built by Grupo ITSS on top of that SAP PM: it takes the order to the field, online and offline, and builds the weekly plan in the Planning module, with Gantt, capacity, and the official schedule returned to SAP.

Field execution, online and offline
Planning with Gantt, capacity, and kanban
Implementation and support by the Grupo ITSS team
The Sigga alternative for SAP PM teams

The Sigga alternative for teams already running SAP PM

Teams comparing Sigga with PM Run already have SAP PM as their central record, so the decision comes down to the details of each process. PM Run is the Grupo ITSS execution layer on top of SAP PM: it takes the order that mirrors IW31 to the field, even offline, and builds the week on the Planning module's Gantt, with the official schedule returned to SAP.

When the weekly schedule holds back execution in SAP PM

These signs show up when the week is built outside SAP and time confirmations arrive late.

  • The week is built in a spreadsheet outside SAPThe planner schedules in a file, and nobody knows which version the crew is following.
  • Crew capacity is checked from memoryThe week closes with more hours than the crew has, and the backlog grows without warning.
  • An urgent order comes in and the schedule is redone on paperDisplaced orders do not return to SAP with their new dates, and the delay only shows up at month-end closing.
  • With no signal in the area, time logging is left for laterSomeone retypes the hours into SAP at the end of the shift, and the confirmation arrives from memory.

With PM Run, scheduling and the field work on the same SAP PM

The planner allocates orders in the Gantt against crew capacity, creates the official schedule integrated with SAP PM and reschedules dates when an urgent order comes in. The technician executes the order in the app, online or offline, and the confirmation goes to SAP.

What PM Run covers in the SAP PM process

Capabilities of the Mobility and Planning modules, linked to SAP PM objects.

Order mirroring IW31

The technician creates and runs the order on the phone with the fields of the IW31 screen, including operations and reservations that pull the equipment bill of materials.

Notification with failure catalogs

Failure recording in the field uses the object part, damage, and cause catalogs, calculates machine downtime, and feeds the history in SAP.

Measurement by QR Code

Measuring point readings are taken by QR Code, hierarchy, or list, and a value outside the limit forces a notification to be opened.

Checklist and safety forms

The long text of the order becomes a checklist in the app, and the team fills in safety forms and surveys alongside execution.

Online and offline execution

The technician opens, runs, and confirms the order with no network, using the local base that syncs once the connection is back.

Weekly planning on top of SAP PM

Backlog, Gantt scheduling, capacity by work center, skills, and a daily kanban, with the official schedule of the period returned to SAP PM.

The weekly schedule in Planning

This is how the PM Run Planning & Scheduling screen organizes the week's orders on top of SAP PM.

PM Run Planning & Scheduling screen with order counters, Gantt, resource utilization and skills matrix tabs, and the button to create the official schedule
  • Weekly countersUnallocated orders, operations, allocations, planned hours and capacity appear at the top.
  • Gantt and resourcesTabs for Gantt, resource utilization, materials, skills matrix and the 52-week map, among others.
  • Official scheduleThe screen has a button to create the official schedule.
  • Actions on ordersRelease, close and reopen orders and reschedule dates, with the integration log in view.

How to compare Sigga and PM Run with your own process in front of you

CriterionQuestion to ask any vendorWhat PM Run delivers today
Weekly planningDoes planning work on the same orders the technician executes on the phone and return the schedule to SAP?Backlog, Gantt scheduling, capacity by work center, skills, and a daily kanban, on the same orders as the app
Official scheduleDoes the schedule the team follows return to SAP as the official schedule of the period?Official schedule of the period's preventive orders, integrated with SAP PM
Operating with no signalCan the technician open, run, and confirm the order with no network and sync when the connection is back?Online and offline app, with a local base that syncs once the network returns
Adherence to the SAP objectDoes the order created in the field mirror the IW31 fields, with operations and reservations?Order creation mirroring IW31, with operations and reservations pulling the bill of materials
Failure historyDoes the field notification feed object part, damage, and cause, and calculate machine downtime?Notification with object part, damage, and cause catalogs, and downtime calculation
Field measurementAre measuring point readings taken by QR Code, opening a notification when the value leaves the range?Measurement document by QR Code, hierarchy, or list, with a limit that forces a notification
Implementation and supportDo the people who implement and support the tool know your SAP PM process?Grupo ITSS team, based in Brazil, running implementation and support
Integration audit trailCan you audit, submission by submission, what reached SAP and what failed?Integration Log validating every submission, over SOAMANAGER, PI, CPI, or RFC

Frequently asked questions

Does SAP PM remain the core system with PM Run?

Yes. SAP PM remains the central record of the asset, the order and the notification. PM Run is the execution and planning layer that runs on top of it, takes the work to the field and returns the data to SAP.

What is the difference between Sigga and PM Run?

Both serve teams with SAP PM as the central record and cover field and planning work. According to Sigga's website, the Sigga EAM Empower app takes SAP PM to technicians offline, and Sigga Planning & Scheduling handles scheduling. At PM Run, the Mobility and Planning modules play that role. The table on this page lists the questions to ask both vendors.

When can Sigga make sense?

When, in an item-by-item comparison, Sigga's process answers your operation's questions better. Since both work on top of SAP PM, the choice comes from a list of criteria you check in each vendor's demo, with your own process in front of you.

Does PM Run work with no signal inside the plant?

Yes. The app works online and offline. The technician opens, runs and confirms the order using the local base, and the app syncs with SAP once the connection is back.

Does PM Run do predictive maintenance?

No. The scope is execution and planning on top of SAP PM, and PM Run does not use sensors. In planning, Manu, PM Run's AI assistant, suggests order allocation by skill, capacity and availability. The preventive strategy stays defined in SAP PM.

Who implements and supports PM Run?

The Grupo ITSS team. PM Run is a Grupo ITSS product and has served more than 12,000 users.

Is there a free guide to check whether the maintenance week fits the crew?

Yes. The maintenance schedule guide covers annual, monthly and weekly horizons, the 52-week plan and balancing against real capacity. The backlog guide shows the formula with a full numerical example and why the healthy range sits between 2 and 4 weeks.

Book a demo of PM Run on top of your SAP PM

In the demo you follow the work order reaching the technician's phone, the confirmation going back into SAP PM and planning seeing what was executed in the field.