When discussing technological advancements, the conversation is not limited to Bluetooth/WiFi Application Programming Interfaces (APIs) and Open Communication Protocols for inspection equipment. Often, users discuss transformative tools that empower industry professionals to create workflow and data-logging apps that prevent mistakes and enhance data collection accuracy like never before. In an era where several industries have successfully transitioned to digital modes for banking, communications and just about everything else, why do industry professionals rely on paper for documenting inspections required by permit or law? Is it because it performs faster? Maybe, but only if users do not consider the time and efficiency gained from investing in process improvement and leveraging the right tools.
By Kevin Moses, Director of Operations, LDARtools
Communicating with Analyzers/Meters
The majority of manufacturers offer APIs or communication protocols free of charge. The technology is ripe for the taking to create custom applications for Windows 10+ and Android devices using Serial Port Profile (SPP). The challenge is not a lack of capability but a gap in understanding how to make the most of these capabilities.
Design Guidelines
A well-designed app should adhere to a set of fundamental guidelines. Start with the basics, such as utilizing conventional Operating System (OS) controls and icons. The application should not require a user manual for navigation. Often times, knowledge staff may want to include instructions for fundamental tasks like firmware updates, but if the app is well-designed, is paired with a logical layout and intuitive controls, the need for such instructions becomes redundant. When it comes to data collection, it is important to ensure the app scales well to a tablet format. In the modern work environment, the flexibility and mobility of tablets are prized, and the app that is being used should take full advantage of this medium.
GPS and Location Services
In today’s connected world, using timestamps and location data has become crucial in digital inspection processes. Having an accurate record of when and where an inspection took place provides an additional layer of transparency and accountability to operations.
Timestamps provide a precise record of when each inspection was carried out. This can be crucial in understanding the sequence of events, monitoring the time taken for each inspection, and even in verifying compliance with inspection schedules.
Incorporating location data, on the other hand, adds a geographic context to inspections. Utilizing GPS, Wi-Fi, or cellular data, the application can log the precise location where each inspection took place. This feature can be invaluable in industries like construction, oil & gas, and public utilities, where inspections often occur across a wide geographic area.
However, it is essential to log the accuracy and method used for the location, be it GPS, Wi-Fi, or cellular. This provides users or customers with the understanding of how much confidence to put in the location data. GPS data tends to be highly accurate but requires a clear view of the sky, while Wi-Fi and cellular data can be used indoors to determine location but may have a wider margin of error.
Additionally, a breadcrumbing feature could allow for the tracking of users’ routes during inspections. By leaving digital ‘breadcrumbs,’ the user can create a traceable path of the inspection, providing a detailed view of the inspector’s journey. This can be critical in confirming that the inspector has indeed visited all necessary areas and completed the required tasks.
The collection of GPS data not only allows for accurate tracking and verification of inspections but also has a strategic advantage. Once collected, this geographical data can be analyzed and utilized to optimize routing for future inspections.
Imagine a scenario where an inspector must conduct inspections across multiple locations in a large area. Without prior planning, the inspector may end up traversing unnecessary distances, leading to wasted time and resources. However, with the analysis of GPS data, the optimal route can be calculated to minimize travel and maximize efficiency.
For instance, the collected GPS data can provide insights into aspects like traffic patterns, distance between inspection sites, and average inspection times. Based on this data, an optimized route can be charted out for subsequent inspections. This route would aim to minimize travel time, distance and prioritize inspections based on factors such as urgency, resource availability, and location proximity.
User Interface
No matter how powerful an app may be, its success ultimately hinges on its usability. Especially in outdoor inspections, the app’s interface needs to be designed keeping the users’ environment and limitations in mind.
The outdoors often comes with their unique set of challenges. Users may have to contend with bright sunlight, varying weather conditions, and even the need to use protective equipment like gloves. All these factors should be considered when designing an app.
For instance, to counter the brightness of sunlight, the app should feature a high-contrast color scheme. This scheme will make it easier for users to discern text and graphics even in glaring conditions. A light text on a dark background or vice versa can provide the contrast needed for clear visibility.
Moreover, users in the field often wear protective gloves, which can make precise touch interactions difficult. Thus, designing larger buttons and menu items is advisable for easy interaction. Similarly, the text size should be sufficiently large to allow easy reading without straining the eyes.
Developers should consider adding a responsive design feature that adjusts the app layout based on the device being used and its screen size. This ensures that the app remains user-friendly whether it is being accessed on a smartphone, tablet, or other mobile device.
Data In/Data Out
Data input and output are crucial areas to address. The app should employ a lite database format if it syncs with a central database or opt for comma separated values (CSV). The trick here is to ensure the output format matches the input format. This enables the user to clear results and repeat the same inspections in the next scheduled interval without the hassle of dealing with incompatible formats.
Analyzer Logging
Drawing from the user experience, one feature that is highly recommend is comprehensive logging. The applications log barometric pressure, temperature, battery voltage, and even VOC (ppm) readings every two seconds might sound excessive, but when text storage is inexpensive, and computers are more than capable of handling the load, comprehensive logging is helpful.
Log files have proven to be one of the most valuable internal tools and often provides critical insights during troubleshooting. For those frustrating situations where a fault cannot be reproduced in the repair shop or when dealing with chronic intermittent issues, log files can be a lifesaver. They transform the often vague user reports of ‘an error message popped up’ into a concrete piece of evidence for resolution.
App Logging
Building on the theme of comprehensive logging, it is crucial to highlight the necessity of robust error logging within the custom application. As much as users strive for perfection, the truth is that at some point, something will go wrong. When these inevitable issues arise, having a detailed error log can make the difference between a quick resolution and prolonged downtime.
An efficient error log does not just record the error messages or crashes. It captures the sequence of user actions leading up to the error, creating a narrative that can help developers retrace the user’s steps and identify where things went wrong.
This chronological report can unearth patterns, highlight repetitive errors, and even provide insights into how users are interacting with the application.
Having a detailed and thorough error log is akin to having a black box in an aircraft. It will not prevent crashes, but it provides invaluable data that can help investigate what went wrong, understand the chain of events leading up to the crash, and, most importantly, prevent the same issues from recurring in the future.
Inform and Enforce Workflows
The power of custom applications extends far beyond inspections involving hardware readings. They can effectively serve as digital supervisors, guiding users through complex procedures and compliance requirements, enhancing safety, and ensuring consistency in operations.
For example, the process of acquiring a confined space permit is essential when a worker needs to inspect locations classified as confined spaces, which are not necessarily designed for continuous occupancy and have limited entries and exits. This can include tanks, vessels, silos, storage bins, hoppers, vaults, pits, manholes, tunnels, equipment housings, ductwork, pipelines, and so on. The acquisition of a confined space permit involves understanding specific safety regulations, verifying the completion of required procedures, and ensuring worker safety.
A well-designed app can facilitate this process by guiding users step-by-step through the requirements needed to acquire the permit. It can provide necessary warnings, reminders, and checks at each stage of the procedure. For instance, it could ensure that the atmosphere within the space has been tested for potential hazards, that rescue and emergency services are available, or that an entry supervisor has reviewed and signed the permit confirming all precautions have been taken. By implementing these checks, the app can prevent the user from moving to the next step without meeting the necessary safety conditions.
This type of intelligent guidance is akin to having an experienced supervisor micromanaging all day, ensuring that procedures are adhered to accurately, efficiently, and safely. It is not just about preventing mistakes or oversights but about embedding best practices into the operations, thus increasing productivity and quality while minimizing risks.
In this digital age, leveraging technology to automate and streamline complex procedures is no longer an option but a necessity. Custom apps are not just digital tools; they can be seen as the user’s safety advisors, compliance officers, and operation supervisors all rolled into one. They enhance efficiency, reduce errors, ensure compliance, and, most importantly, improve worker safety.
Mobile Hardware Selection
After creating a custom app, it is critical to choose the right hardware that aligns with the safety and operational requirements of the specific work environment. The hardware should not only be compatible with the software the user is developing but also comply with the safety standards of the work area. When it comes to potentially explosive environments, these safety standards include categories like Class 1 Division 1 (C1D1), Class 1 Division 2 (C1D2), and non-certified devices.
Class 1 Division 1 certification is for environments where an explosive atmosphere is present continuously, intermittently, or during normal operations. This could include areas where volatile flammable liquids or flammable gases are handled, processed, or used.
Class 1 Division 2 certification, on the other hand, is for environments where explosive conditions are not likely to exist under normal operations but may occur under abnormal conditions or in case of a specific fault.
Non-certified devices are for environments where there is no expectation of an explosive atmosphere. These could be regular office spaces, commercial kitchens, or general storage areas where the risk of a flammable or explosive environment is very low.
If the hardware is not certified for a specific area, a hot work permit may be required. This permit is a documented process that normally authorizes hazardous work operations such as welding, cutting, or other sparking activities in an explosive environment but also applies to non-certified electronics. The typical requirements for a hot workpermit include a clear description of the work, location, and time duration, a pre-work safety check to verify precautions taken, and continuous monitoring of the environment while the work is being performed.
Selecting a C1D1, C1D2, or non-certified device depends on the specific work environment, operational needs, and safety requirements. It is crucial to have a clear understanding of these categories to ensure safety and efficiency. Pairing the right hardware with a custom app tailored to the user’s processes ensures seamless integration, safety compliance, and effective performance.
Conclusion
Transitioning from paper to custom apps for inspection processes is not only about embracing technology—it is about increasing efficiency, reducing errors, and improving traceability. Now is the time to embrace APIs, utilize the freely available resources from hardware manufacturers, and step into a world of streamlined inspections. The benefits far outweigh the investment required, and the leap is not as daunting as it might initially seem. This is not the future. This is the present, and it is time to get on board.
