There are many situations where e-Quip will display a warning or an alert. It is very difficult to document all of them because there are so many and most are self-explanatory. If you see a message that says “The work end date is before the call date” then you don’t really need us to explain what that means – it means that the work end date is before the call date!
However, when you open an equipment or job record it is useful to know what types of information can be displayed and what it means.
The Equipment Property Page
Whenever the equipment property page is opened the user can be alerted about important or useful information in three ways: Header Alerts, Alert Dialog Boxes & Events Alerts.
Asset Header Alerts
The most obvious alerts are the 5 coloured boxes on the page header. These are (from left-to-right):
1. The device is subject to an on-going medical device alert. Whenever this alert is displayed the Alerts tab will also be displayed.
2. User-Defined. In this example the alert is showing that the device is overdue for PPM. This alert is configured by editing the SQL-Server stored procedure qAssetAlert1_Local. Note that editing stored procedures is a technical configuration action and must be undertaken by appropriately qualified technical staff. Any stored procedure whose name ends in ‘_Local‘ will not be affected by subsequent upgrades.
3. The device holds patient data. This is controlled by a check-box on the Data tab.
4. User-Defined. In this example the alert is showing that the device is covered by a particular contract. This alert is configured by editing the SQL-Server stored procedure qAssetAlert2_Local.
5. There is an open non-PPM job for this device
Although not part of the header alerts there is some other useful information displayed. The window caption bar shows that the device is subject to an on-going medical device alert and also displays the date that the record was last modified. If the record is read-only this will also be shown in the caption bar.
Notice also that there is a coloured check-box on the Contracts tab. This indicates that the device is currently covered by a contract.
Asset Dialog Alerts
Before the equipment property page is displayed a number of warning messages may be displayed. These are:
A Maintenance Event is an action which is carried out at predefined intervals but which may not be associated with a particular PPM schedule. For example, a battery may be changed at 6-monthly intervals and this may coincide with a repair job, a 3-monthly, 6-monthly or annual PPM. If an event is due then this will be displayed when the record is opened.
The Job Property Page
The alerts on the job screen are similar to those on the equipment screen, although rather than using multiple individual alert dialog boxes, all of the messages are combined into a single message.
Job Header Alerts
The job property page has 3 header alerts. These are (from left-to-right):
1. The job is billable. This warning is controlled by the SQL-Server function JobIsBillable_Local. This is where you can define your site-specific logic which determines whether or not a job is billable.
2. User-Defined. In this example the alert is showing that the device has passed its predicted life. This alert is configured by editing the SQL-Server stored procedure qJobAlert1_Local.
3. User-Defined. In this example the alert is showing that the device is Beyond Economic Repair. This alert is configured by editing the SQL-Server stored procedure qJobAlert2_Local.
There are many more alerts for jobs than there are for equipment. To prevent a large number of individual warnings these are all combined into a single message.
The possible warnings are:
1. The device is under warranty
2. The device is on contract
3. There is an outstanding non-PPM job for this device
4. A PPM is due for this device
5. A PPM is overdue for this device
6. The device is subject to an on-going medical device alert
7. The device is covered by a customer contract
8. The device has passed its predicted life
9. The device holds patient data
The job screen displays maintenance events due in exactly the same way as the equipment screen. However, if an event is due it will be added to the job events tab.
Part 1 – An Introduction to Device Maintenance Events
This is the first of a 2-part article about the maintenance event feature of E-Quip. This article introduces the concept of events and shows a simple automated event mechanism. The 2nd article will go into this subject in much greater depth.
A maintenance event is any activity that must take place at some fixed interval on a device. Examples might be “Battery Change”, “Replace Filter” etc.
Suppose that the battery for a device must be changed every year, and the device is on 6-monthly, annual and 5-yearly PPM Schedules. If you understand how PPM Schedules work then you will know that there will always be 3 non-completed jobs for this device, one for each schedule. (If you didn’t know that, check out some of the articles on this blog on PPM management).
It is easy to envisage situations where the annual battery change might coincide with any of these jobs. Indeed, if the device develops a fault between scheduled maintenance the battery might be replaced as part of a repair job. How is the engineer to know (without searching through the service history) whether or not the job that he is currently doing should include the battery change or not?
E-Quip now includes a simple to use maintenance event mechanism. It works like this:
1. On the model screen define which events the device needs, and their interval.
2. If you choose to make these events automatic, that’s all you need to do! Every time you open a device, if any events are due (or overdue) then you will see a list of the events. If you want to you can complete the events directly from the equipment property page.
3. Similarly, whenever you create or open a job for a device which has one or more events due, then you will see a list of the events, and those events will snap to that job. If you complete the event it will be added to the device’s event history, but you won’t hear from it again until it is next due. If you complete the job but don’t complete the event(s), then they will just snap to the next job.
Step 1: Define an event for a model.
Note that in this example both events are defined with the Auto-Link option.
Step 2: Create a job for a device of that type:
As soon as you select the Equipment No. for the job you will be warned about due/overdue events.
Them when the job opens, the events will automatically snap to the job.
It is possible to manually specify events on the job property page, such as when you wish to carry out an event before it is actually due. Events which have snapped to a job automatically will be coloured light blue. They are only temporarily attached to the job. If they are completed (by entering the completion date) then they will be permanently linked to job and will appear in the device event history.
If an auto-snapped event is not completed and the job is closed, the event(s) will simply snap to the next appropriate job.
This is the simplest scenario but events can be used much more flexibly than this. The next article on this topic will explore this in more detail.