Artificial Intelligence and Environmental Compliance–Revisited–Part 3: Multi-Tenancy and AI

SaaS–Multi-Tenant Cloud Architecture

Multi-tenancy offers distinct benefits over traditional, single-tenant software hosting. A multi-tenant SaaS provider’s resources are focused on maintaining a single, current version of the application, rather than having its resources diluted in an attempt to support multiple software versions for its customers. If a provider is not using multi-tenancy, it may be hosting or supporting thousands of single-tenant customer implementations. By doing so, a provider cannot aggregate information across customers and extract knowledge from large data sets as every customer may be housed on a different server and possibly a different version of software. For these reasons, it is almost impossible and prohibitively expensive to deliver modern AI tools via single-tenancy.

Locus Multi-Tenant Software
View Infographic | Download White Paper

Multi-tenancy has other advantages as well. Because every customer is on the same version of the software and the same instance, machine-learning (a prerequisite for building an AI system) can happen more quickly as large datasets are constantly fed into a single system. A multi-tenant SaaS vendor can integrate and deploy new AI features more quickly, more frequently, and to all customers at once. Lastly, a single software version creates more of a sense of community among users and facilitates the customers’ ability to share their lessons learned with one another (if they chose to do that). Most of today’s vendors in the EH&S software space cannot offer AI, sustain their businesses, and grow unless they are a true multi-tenant SaaS provider. Very few vendors are.

AI

Almost 30 years after the publication of our paper on the hazardous data explosion, SaaS technologies combined with other advancements in big data processing are rising to the challenge of successful processing, analyzing, and interpreting large quantities of environmental and sustainability data. It is finally time to stop saying that AI is a promising technology of the future. A recent Gartner study indicates that about 20 percent of data will be created or gathered by computers by 2018. Six billion connected devices will acquire the ability to connect and share data with each other. This alone will fuel AI growth as we humans cannot interpret such massive amounts of data.

Gone are the days where EHS software was just a database. There are two factors that are fueling the adoption of AI technologies for water quality management and  EHS compliance. First, there is a vast increase that we have mentioned of data that needs sorting and understanding (big data). Second, there is the move to true multi-tenant SaaS solutions, which enables the intake and dissection of data from multiple digital sources (streaming data) from multiple customers, all in real-time.

AI has entered the mainstream with the backing and advocacy of companies like IBM, Google, and Salesforce, who are heavily investing in the technology and generating lots of buzzes (and we are seeing the consequent talent war happening industry-wide). It is remarkable to observe how quickly AI is proliferating in so many verticals, as CBS’s 60 Minutes segment showed us.

For our purposes, let’s look at where AI is likely to be applied in the EHS space. The mission-critical problem for EHS enterprise software companies is finding solutions that both enhance compliance and reduce manual labor and costs. This is where AI will play a major role. So far, companies have largely focused on aggregating their data in a record system(s); they have done little to interpret that data without human interaction. To address the ever-changing growth in environmental regulations, companies have been throwing people at the problem, but that is not sustainable.

Locus Artificial Intelligence

AI and natural language processing (NLP) systems have matured enough to read through the legalese of regulations, couple them with company’s monitoring and emissions data, and generate suggestions for actions based on relevant regulations and data. Take, for example; a CEMS installed at many plants to monitor air emissions in real-time. Alternatively, a drinking water supply system monitoring for water quality. In each of these systems, there are too many transactions taking place to monitor manually to ascertain which ones are compliant and which ones are not? I see no reason why similar algorithms that are used for computerized trading (as described in the recent best-seller “Flash Boys”) to trade stocks in fractions of a second cannot be used for monitoring exceedances and automatically shutting down discharges if there is an approaching possibility of emission exceedance. It is an onerous task to figure out every exceedance on a case-by-case basis. Intelligent databases with a built-in AI layer can interpret data on arrival and signal when emissions exceed prescribed limits or when other things go wrong. The main driver behind applying AI to EHS compliance is to lower costs and increase the quality of EHS compliance, data management, and interpretation, and ultimately, to avoid all fines for exceedances.

For example, a large water utility company has to wade through thousands of analytical results to look for outliers of a few dozen chemicals they are required to monitor to stay compliant. Some of these may be false-positives, but that still leaves some results to be investigated for outliers. Each of those investigations can take time. However, if a software algorithm has access to analytical results and can determine that the problem rests with a test in the lab, that problem can be solved quickly, almost without human interaction. That is powerful.

Combing through data and doing this by hand or via spreadsheet could take days and create a colossal waste of time and uncertainty. Hundreds of billable hours can be wasted with no guaranteed result. Using AI-driven SaaS software to determine what outliers need investigation allows compliance managers, engineers, and chemists to focus their expertise on just these cases and thus avoid wasting their time on the remaining ones that the AI engine indicates need no further examination.

Predictive analytics based on big data and AI will also make customer data (legacy and new) work harder for customers than any team(s) of consultants. A good analogy that came to me after watching 60 minutes is that the same way the clinical center in North Carolina used AI to improve cancer treatment for their patients, engineers and geologists can improve on selecting the site remedy that will be optimized for given site conditions and will lead to a faster and less expensive cleanup with minimum long-term monitoring requirements.

A final example where AI will be playing a role is in the area of enterprise carbon management. SaaS software is capable of integrating data from multiple sources, analyzing and aggregating it. This aggregated information can then be distributed to a company’s divisions or regulatory agencies for final reporting and validation/verification, all in real-time. This approach can save companies lots of time and resources. Companies will be able to access information from thousands of emission sources across the states, provinces, and even countries where their plants are located. Because each plant is likely to have its set of regulatory drivers and reporting requirements, these would have to be incorporated into the calculation and reporting engine. After data from each plant is uploaded to a central processing facility, the information would be translated into a “common language,” the correct calculation formulae and reporting requirements applied, and the results then returned to each division in a format suitable for reporting internally and externally.

Blockchain for EHS—Looking ahead

And finally, another emerging technology, blockchain, will further augment the power of AI for EHS monitoring and compliance. While blockchain is in its infancy, its decentralized approach coupled with AI will bring another revolution to EHS compliance and water monitoring.

Blockchain technology

Parts one, two, and four of this blog series complete the overview of Big Data, IoT, AI, and multi-tenancy. We look forward to feedback on our ideas and are interested in hearing where others see the future of AI in EHS software – contact us for more discussion or ideas!

Contact us to learn more about Locus uses IoT and AI

    Name

    Company Email

    Phone

    Tell us about your company's needs

    Locus is committed to preserving your privacy.

    Stories and conversations from this summer’s radiological workshop

    Locus recently joined the nuclear power plant community in Orlando, FL for this year’s Radiological Effluents and Environmental Workshop. It’s always a pleasure to join other professionals in a space that encourages discussion, education, and awareness of industry processes and compliance.

    Locus Technologies at the NEI Radiological Conference, Orlando, 2019

    Bill Donaldson and Danny Moore of Locus Technologies.

    Each conference we attend is an opportunity to learn. Whether talking with current or potential customers, it’s always fascinating to hear some of the success and horror stories experienced in their daily operations. We’ve summarized a few of those conversations below. And since REEW takes place in the summer, there’s a theme.


    Locus SaaS does not have version numbers.Version Island

    Imagine you’ve spent years utilizing a certain feature of your radiological software. You’ve gone through the training process, the growing pains, and you are finally enjoying the fruits of that labor. Now imagine learning that the latest and greatest version being released has removed the feature that you’ve grown to rely on. You are now stuck on a version island. At this point, a costly and time consuming upgrade will cause more problems. Locus SaaS has no version numbers, meaning you will never need to upgrade.


    Ditch Excel and go off the gridOff the Grid

    At one time, the simple columns and rows in Excel seemed to provide a sufficient solution to prepare your REMP sampling data for reports. However, when you need to transfer data between systems, or create more sophisticated reports, those grids begin to feel like prison bars. Maybe it’s time to go off the grid and deploy a more modern solution that can connect and work side by side with your existing tools.


    Locus helps with decommissioningSunsetting (Decommissioning)

    Closing a power plant is a long and involved process that many attendees were in the process of dealing with or will be in the near future. This operational change can be the motivation to rethink the way radiological data is sampled and managed. Some software packages can be too big for the job. Locus offers a modular approach where you only pay for what you need. Choosing which system tools are relevant to the type of data sampling and resources available can minimize implementation cost and increase productivity.


    Locus' cloud securitySerene Security

    Many people we spoke with at REEW had serious security concerns. Locus takes those concerns seriously. We are SOC 1 and SOC 2 certified and have migrated our software to Amazon Web Services. All customer data is stored with AWS, one of the most advanced and secure cloud-hosting providers on the planet. Locus provides the ability to control user permissions, customizing access based on job duties. This provides a more granular approach to data security.


    Locus sample planningMaking Plans

    Using a sample planning application organizes sample events and allows for scheduling weeks, months, or years in advance. Many were interested in this powerful tool that is flexible enough to adapt when a reactor changes modes, allowing for one-time, ad-hoc samples. Mobile applications that integrate with planned samples and events minimize setup, ease data collection, speed up loading field data, and can expedite samples to the lab more efficiently.


    Your feedback has helped Locus build a solution that makes it easy to manage all your facility’s data for RETS/REMP, helping you meet your NRC reporting requirements. We enjoyed speaking with everyone at REEW and we look forward to seeing you again next year!

    [sc_button link=”https://www.locustec.com/applications/industry/nuclear/” text=”Learn more about Locus for Nuclear” link_target=”_self” background_color=”#52a6ea” centered=”1″ separator_style=”double”]


    About the author—Danny Moore, Locus Technologies

    Danny Moore, Marketing Manager, Locus Technologies

    Mr. Moore has spent the last decade designing and marketing for enterprise SaaS systems. In his career at Locus, he leads a team of marketing professionals in branding, content creation, social media engagement, and email outreach. Mr. Moore enjoys attending conferences as a Locus brand ambassador and sharing any feedback gained to improve product development.


    About the author—Bill Donaldson, Locus Technologies

    Bill Donaldson, Locus Technologies

    Mr. Donaldson has 5 years experience in SaaS systems, performing Product Management and QA/QC of Locus Mobile iOS application and Locus’ Environmental Information Management system (EIM). While completing his B.S., Mr. Donaldson held several paid internships, where he configured a Relational GeoDatabase and a Database Management System (DBMS), for biological data entry.

    Does your EHS software have a version number?

    Freedom from product release tyranny

    I love the article by Geoffrey Moore on the power of software as a service (SaaS) business model published on LinkedIn. In SaaS’s Real Triumph he writes: “by far the greatest contribution of SaaS is to free the enterprise from the tyranny of the product release model.”

    He cites the operational burden, enterprise-wide distraction and associated cost to roll out an enterprise software and then the subsequent hesitation to repeat that when a new release of that software becomes available as that deployment model is not sustainable nor affordable. Companies spend big dollars buying and then deploying EHS software that they know will be outdated in just a few years. Only IT personnel benefits from that model as it may extend their employment for a few years before IT department goes out of business for good. Moore points out the painful truth, stating: “you have paid maintenance of 18 to 20% per year for anywhere from five to ten years for the express purpose of not availing yourself of the innovation created during that time period.”

    Probably the main benefit of SaaS multi-tenancy (that is frequently overlooked during the software selection process) is no software versioning. This is because multi-tenant software typically provides a rolling upgrade program: incremental and continuous improvements. It is an entirely new architectural approach to software delivery and maintenance model. Companies have to develop applications from the ground up for multi-tenancy. Legacy client-server or single-tenant software cannot qualify for multi-tenancy. Let’s take a look at definitions:

    No version number

    Single-Tenant – A single instance of the software and supporting infrastructure serves a single customer. With single-tenancy, each customer has his or her own independent database and instance of the software. Essentially, there is no sharing happening with this option.

    Multi-Tenant – Multi-tenancy means that a single instance of the software and its supporting infrastructure serves multiple customers. Each customer shares the software application and also shares a single database. Each tenant’s data is isolated and remains invisible to other tenants.

    Benefits of SaaS Multi-Tenant Architecture

    The multi-tenant architecture provides lower costs through economies of scale: With multi-tenancy, scaling has far fewer infrastructure implications than with a single-tenancy-hosted solution because new customers get access to the same software.

    Shared infrastructure leads to lower costs: SaaS allows companies of all sizes to share infrastructure costs. Not having to provision or manage any infrastructure or software above and beyond internal resources enables businesses to focus on everyday tasks.

    Ongoing maintenance and updates: Customers don’t need to pay costly upgrades to get new features or functionality. 

    Configuration can be done while leaving the underlying codebase unchanged: Single-tenant-hosted solutions are often customized, requiring changes to an application’s code. This customization can be costly and can make upgrades expensive and time-consuming because the upgrade might not be compatible with customers changes to the earlier software version.

    Multi-tenant solutions are designed to be highly configurable so that businesses can make the application perform the way they want. There is no changing the code or data structure, making the upgrade process easy.

    Multi-tenancy ensures that every customer is on the same version of the software. As a result, no customer is left behind when the software is updated to include new features and innovations. A single software version also creates a unique sense of community where customers and partners share knowledge, resources, and learning. Smart managers work with their peers and learn from them and what they are doing. A multi-tenant SaaS provider’s resources are focused on maintaining a single, current (and only) version of the application, rather than spread out in an attempt to support multiple software versions for customers. If a provider isn’t using multi-tenancy, it may be hosting thousands of single-tenant customer implementations. Trying to maintain that is too costly for the vendor, and those costs, sooner or later, become the customers’ costs.

    A vendor who is invested in on-premise, hosted, and hybrid models cannot commit to providing all the benefits of a true SaaS model due to conflicting revenue models. Their resources are going to be spread thin, supporting multiple versions rather than driving innovation. Additionally, if the vendor makes the majority of their revenue selling on-premise software, it is difficult for them to fully commit to a true SaaS solution since the majority of their resources are allocated to supporting the on-premise software.

    Before you engage future vendors for your enterprise EHS software, assuming you already decided to go with SaaS solution, ask these questions:

    1. Does your software have version numbers? 
    2. Do you charge for upgrades and how often do you upgrade?

    If the answer is yes to any of these two questions, you should not consider that vendor as they are not true multi-tenant SaaS. You should not select that vendor if they answer “we are in the process of switching to multi-tenancy.” Multi-tenancy train departed a long time ago, and no EHS vendor who is single-tenant is not going to make that switch in time to make it work.

    And if they suddenly introduce a “multi-tenant” model (after selling an on-premises version for 10+ years) who in the world would want to migrate to that experimental cloud without putting the contract out to bid to explore a switch to well established and market-tested true multi-tenant providers? The first-mover advantage when it comes to multi-tenancy is a huge advantage for any vendor.

    Multi-tenant architecture