Off the Labeled Path

Configurability has been a hallmark of Blue Mountain’s software over the years.  With the introduction of Calibration Manager 4 in 2002, we expanded the set of User Defined Fields available to users and introduced the ability to partition Equipment within a single database by Datasets.  Both of these enhancements allowed users to creatively utilize the system in order to maximize their ROI, improve efficiency, and ensure compliance.   In 2007, we released Blue Mountain Regulatory Asset Manager (a.k.a. Blue Mountain RAM), the successor to Calibration Manager 4, and expanded the configurability available with our software.

One example of this configurability and flexibility is a record type available in Blue Mountain RAM called the User Defined Asset Record (a.k.a. UDART).    The purpose of UDART records is to provide users with the flexibility to capture information electronically for records beyond just the base Equipment, Event and Work Histories.   This is sometimes referred to as “off label” use of software.

Some of the characteristics and benefits of UDARTs include:

  • Call it what you want – designate a custom record title
  • Configure it how you want – specify field/tab visibility and layout, labeling, and workflow
  • Report and Query on it how you want – build custom workspaces to include queries, reports and actions specific to the workflows associated with each UDART record type
  • Automatically Generate when you want – configure the system to automatically create UDART records based on conditions encountered such as when an Out of Tolerance is recorded on a Calibration Work History a by Technician

One example of how the UDART can be put to use might be to track Out Tolerance Investigations, or OOTs.  An OOT Investigation form is a typical artifact that is part of the follow-up investigation activities that must occur once an instrument is found to be out of calibration.   This follow-up is critical in GMP environments since faulty instrumentation may impact product safety and quality.

  • Figure 1 depicts a UDART record before it has been configured (six UDARTs are available).
  • Figure 2 depicts how users might configure a UDART as an OOT Investigation record.

Other examples of how UDARTs could be purposed include :

  • Change Controls
  • Deviations
  • Service contracts
  • etc.

The UDART is just one example of the type of configurability available with Blue Mountain software that provides users with the ability to utilize the software “off the labeled path” to maximize its value.

Figure 1 – UDART prior to configuration

bm blog 2.1

Figure 2 – UDART configured to be an OOT Investigation record

bm blog 2.2

Leave a Reply