Locus is mentioned in ENR’s article about data mining, discussing how Locus software helps our long-time customer, Los Alamos National Laboratory, manage their environmental compliance and monitoring.
There is a considerable degree of (intended) confusion in the EHS software space when it comes to multi-tenancy. Companies that are considering Software-as-a-Service (SaaS) hear all sorts of things from EHS software vendors hoping to tap into the momentum of cloud computing. Among the most common is that multi-tenancy is a “techie” thing that doesn’t need to be part of the conversation. Many go as far as saying “sure, we can do multi-tenant, single-tenant, whatever you need!”— anything to win the job.
Unfortunately, those vendors simply do not understand what they are talking about. Multi-tenancy is a major shift in computing and requires all new approach to software architecture and delivery model. It is transformational, and customers who intend to buy the next generation of EHS software should spend the time to understand differences.
Multi-tenancy is the core foundation of modern SaaS and shouldn’t be taken lightly, generalized, or massaged into something that suits a vendor’s self-serving interpretation of SaaS. Having experienced first-hand the true benefits of multi-tenant SaaS, I can’t conceptualize how SaaS would have delivered those benefits if it wasn’t multi-tenant. Can anyone imagine companies like Salesforce, NetSuite, Google, or Amazon offering a “single-tenant” solution side by side to their multi-tenant clouds? I will go as far as say that any company offering a single-tenant solution cannot be a serious contender in offering multi-tenant SaaS.
I would also add that single-tenant (hybrid) cloud applications are worse than on-premise installment. Why? Because they are fake clouds. In these instances, a customer is, in fact, outsourcing maintenance of their application to a vendor that is not equipped for that maintenance. No single vendor in the EHS software industry is large enough to undertake maintenance of the single-tenant infrastructure on behalf of their customers, regardless how inexpensive hardware may be.
There are many ways to take the functions of on-premise installed software model of the 1980s and package them as services. Some of these service delivery modes– such as ASP, single-tenant hosting, and hybrid clouds– merely relocate and reassign long-standing problems and potentially make them worse. In a single-tenant model, user customizations may infiltrate throughout the stack, in a way that makes it difficult to upgrade the performance of the stack. The true SaaS models confront and mitigate– or even eliminate– some of the most vexing elements of software installation and maintenance: configurability on the fly, software maintenance, and upgrades. It is “a tyranny of software upgrades” that kills the single-tenant model.
Let me offer a simple analogy to drive home the point as to why multi-tenancy matters: Tesla vs. Edison– War of Currents.
The War of Currents was a series of events surrounding the introduction of competing electric power transmission systems in the late 1880s and early 1890s that pitted companies against one another and involved a debate over cost and convenience of electricity generation and distribution systems, electrical safety, and a media/propaganda campaign, with the main players being the direct current (DC) based on the Thomas Edison Electric Light Company and the supporters of alternating current (AC) based on Nikola Tesla’s inventions backed by Westinghouse.
With electricity supplies in their infancy, much depended on choosing the right technology to power homes and businesses across the country. The Edison-led group argued for DC current that required a power generating station every few city blocks (single-tenant model), whereas the AC group advocated for a centralized generation with transmission lines that could move electricity great distances with minimal loss (multi-tenant model).
The lower cost of AC power distribution and fewer generating stations eventually prevailed. Multi-tenancy is equivalent of AC when it comes to cost, convenience, and network effect. You can read more about how this analogy relates to SaaS in the book by Nicholas Carr, “Big Switch,” a Wall Street Journal bestseller. It’s “the best read so far about the significance of the shift to cloud computing,” said Financial Times. The EHS software industry has been a laggard in adopting multi-tenancy.
Given these fundamental differences between different modes of delivering software as a service, it is clear that the future lies with the multi-tenant model.
Whether all customer data is put onto one database or onto multiple databases is of no consequence to the customer. For those arguing against it, it is like an assertion that companies “do not want to put all their money into the same bank account as their competitors,” when what those companies are doing is putting their money into different accounts at the same bank.
When customers of a financial institution share what does not need to be partitioned—for example, the transactional logic and the database maintenance tools, security, and physical infrastructure and insurance offered by a major financial institution—then they enjoy advantages of security, capacity, consistency, and reliability that would not be affordably deliverable in isolated parallel systems.
In enterprise cloud applications and cloud application platforms, multi-tenancy yields a compelling the combination of efficiency and capability without sacrificing flexibility or governance.
When a software provider seeks to blur the distinctions between one technology and another, there’s usually just one reason: because they are unable to offer the superior technology to their customers, and hope to persuade their customers that real differences are not relevant to their needs. Multi-tenant platforms for enterprise on-demand applications represent genuine opportunities for customer advantage. The reality of multi-tenant differentiation is acknowledged by authoritative industry analysts such as Gartner, whose March 2007 announcement1 of its Outsourcing Summit that month included this definition of Software as a Service:
“Hosted software based on a single set of common code and data definitions that are consumed in a one-to-many model.”
In other words, hosting models that do not offer the leverage of multi-tenancy don’t belong in the same discussion as the value proposition implied by the term, “SaaS”. Multi-tenancy is a difference that makes a difference.
—
References
1Gartner Inc., “SaaS will have significant impact on IT services and outsourcing providers,” Tekrati, 7 March 2007
Finding a differentiator for your organization is the key to success in a competitive marketplace.
Anyone in the tech industry will tell you that building software can be a costly endeavor.
On top of the overhead expenses, selling enterprise software means long sales cycles and competing in a crowded field of vendors.
To succeed in this cutthroat environment, you need a differentiator—somewhere your company excels compared to the other players in the field. This differentiator will be your main focus in every aspect of the business. It allows you to effectively prioritize and execute your tasks, maintaining an edge on the competition.
Working at Locus, a question I often hear is, “How do you hire and retain top engineering talent, when you’re competing with the big tech titans in Silicon Valley?”
My answer is simple and straightforward: our environmental focus. Ever since Locus started as a company, our vision has been to deliver technologies that optimize the management of environmental data for our customers. Our goal is to be the best technology partner for helping our customers manage their environmental footprint.
At Locus, environmental engineers with high domain expertise work closely with software engineers to build solutions that very effectively fulfill our customers’ needs.
To work on Locus’ product development team, you must either be exceptional in cloud/SaaS technologies or in environmental engineering. Our ability to integrate these two specialties is our differentiator. Other vendors may have capability in one area, but very few can claim both.
At Locus, these two types of engineers work side by side, collaborating to deliver new software. This dynamic creates incredible opportunities for engineers to learn new things and experience the satisfaction of being challenged at work. At the same time, it creates an ideal team to deliver the best products to address the environmental health & safety market.
Recently, our engineering team was working on our vapor intrusion and indoor air management application, built for our customers for compliance and regulatory reporting. Environmental engineers were best suited for this project because they thoroughly understand the regulatory compliance process. Having environmental engineers collaborating directly with software designers on the team, rather than relying on consultants, allowed us to quickly design a reliable system for automating GHG tracking. This is just one example of how we integrate a unique set of skills and expertise in our company.
Projects such as this one help reaffirm my belief that finding a unique differentiator is the key to success. Find what makes you stand out in the market, and pride yourself on that quality.
—
About guest blogger— Sandeep Khabiya, Locus Technologies
Sandeep Khabiya is responsible for driving software development at Locus Technologies in alignment with the company objectives. In his role, he directs the work of a broad range of technical personnel and is a coach and mentor for team members across multiple and diverse projects.
Before joining Locus as the Director of Software Engineering, he spent over 14 year with HP Software leading development of products like IT Governance, Project Management and Cloud Service Automation while working with teams across the globe in US, Czech Republic, India, and China.
A configurable application-building platform lets you easily build and reconfigure apps that perfectly fit your business needs.
In the EHS&S industry, companies and organizations demand a unique set of needs from their software applications.
There are many software tools and applications available out there aimed to assist with any aspect of your company. Many buyers get stuck on the question of how to find the perfect app solution for their business needs, especially considering that these needs grow and evolve over time. They spend money and time researching the perfect app that fits their unique situation.
An unexpected solution to this dilemma lies in a configurable software platform— designed specifically to allow you to easily build and reconfigure apps that perfectly fit your business needs.
Developing custom applications on a cloud-based application development platform has a number of advantages that you should consider before deciding to buy an off-the-shelf application that happens to tick all the boxes on your features list. This solution delivers easily configurable, scalable, and well-integrated applications that will help you drive your productivity and success in the future.
Lower long-term costsCustom app development on a platform means you can create a custom application that is specifically tailored to your company’s needs, as well as being focused on scalability and efficiency.
Off-the-shelf software may initially seem like the faster and cheaper option, but the lack of customization for day-to-day operations is ultimately inefficient (and often leads users to invent their own manual processes outside the software to compensate for the software’s inefficiencies). As the application is used more often, even the smallest issues can grow exponentially, leading to costs that will far outweigh your initial savings on the off-the-shelf software.
Better productivity = higher ROIConfigurable custom applications that are specifically designed with your needs in mind will help your team work faster and smarter. Well-integrated apps on a unified platform can yield major efficiency gains, since all the data is in one place and users do not have to switch between different applications or websites as part of their workflow.
Another added benefit comes from the interoperability of apps coexisting on the same platform, which can drastically reduce input requirements, as well as the need for multiple QA/QC processes. Input once, use many times.
Save time, adapt fasterThe ability of an organization to quickly shift technology strategies can mean the difference between dominance and obsolescence in many industries. A configurable platform enables you to rapidly customize and deploy your application, with a fraction of the time and resources that would be required for an off-the-shelf application.
Common UI, data and security modelPlatform applications share the same user interface, security, and configuration-data model amongst all apps. There is no need to manage data integration or sync issues.
Additionally, new software upgrades are easily deployed to a large number of users, so users will remain in a familiar interface across all apps. These benefits support faster and easier deployment, as well as rapid user adoption— both of which are critical to success and a high ROI for any solution.
Built-in support for integration with other platformsAdvanced APIs (to support integration of third-party, enterprise, Internet of Things, or legacy applications not on the platform) are interoperable and will help maximize your team’s productivity.
Off-the-shelf software may not be compatible with other programs. You may need one software product to read IoT data from sensors, another to launch an incident management workflow, and yet another to file a new SAP purchase order. If the programs do not communicate effectively, they will hinder your work process.
A custom platform app can integrate with a wider set of APIs from different software and data partners, providing a seamless flow of information.
Mobile capabilityMobile applications have become a significant extension of any web-based application. A configurable app platform inherently supports an easy transition from a web app to a mobile app, without any extra development efforts. This saves time, money, and resources needed to maintain the mobile app. It also resolves any data integration or usability issues that integrating a third-party, custom mobile app could cause with your application.
—
About guest blogger— Rehan Shah, Locus Technologies
An avid programmer, Rehan Shah is passionate about programming and making the world a better place. At Locus, Rehan gets the opportunity to combine both his passions, making his job much more fun and intriguing.
After graduating from Purdue with a degree in computer engineering, he spent the next 10 years working for industry leaders including HP, Oracle, and ServiceNow. Now at Locus, he’s a senior software engineer in the Locus Platform dev team, an agile dev team lead and a self-proclaimed Chief Hackathon Officer.
In today’s Internet-driven age, consumers are overwhelmed by an abundance of choices and information on every conceivable product on the marketplace. The same is true for businesses looking to buy software solutions. Selecting an enterprise-wide EHS&S software solution can be a feat for any organization.
Whether you have been tasked to research vendors from the EHS shop window, or you are driving the data evolution in your business to move from spreadsheets (or worse – paper) to a 21st century-ready alternative— the task at hand can seem daunting and fraught with challenge.
Establishing a timeline and setting milestones along the way will help you break down your mission into manageable, bite-size chunks. Here are some helpful tips to find the right EHS vendor for you — and remember, it’s a marathon, not a sprint!
Different departments and stakeholders will have different goals– don’t forget to consider how the EHS software solution will help them, too.
As the individual spearheading this project, you are not the only one with skin in the game, nor is this likely confined to your team. Multiple business units, divisions, and departments are not only going to have to use a new EHS software solution – they need to like doing so.
The different stakeholders also come with their own individual business goals, and they will be looking to the new EHS software solution to assist them. Can you carefully engage different areas of your business to find the key drivers?
Even better – assign project leaders within business units to join your selection process, attending demos and providing critical feedback along the way. After all, more heads are better than one.
Many of us in the EHS&S industry share similar passions, such as the desire to help reduce climate change and help businesses move to more environmentally-friendly ways of operating.
Sadly, this isn’t at the top of every company’s list of priorities. But we can all agree that the most important and critical areas are compliance-driven.
Think about which local, state, and federal regulations you are bound by and must adhere to at all costs. It’s all well and good, having a software that can calculate CO2 emissions saved from a new “green” initiative. But shouldn’t it also be smart enough to alert you when a permit is up for renewal?
Take time to compile a list of all areas you need to keep on top of. The right software should be able to keep you one step ahead, not left scrambling around, collecting data from all of your sites to meet a certain deadline.
Conferences such as those hosted by NAEM are a great place to network with other EHS professionals and ask your peers about their experience with specific software vendors.
Trying to select a shortlist of vendors to demo with is no easy feat, especially when an Internet search throws up 20 pages of results. Fortunately, there are plenty of independent sources and conferences that exist specifically to help you in this endeavor. The National Association of Environmental Managers (NAEM) is one example. Networking with other EHS professionals can lead to recommendations and “been there, done that” advice on who the key players are.
It’s also important to remember that EHS vendors are not necessarily built for every terrain, and some specialize in different areas (i.e., health and safety, air emissions, waste management, etc.). I have yet to come across two businesses with the exact same EHS needs and requirements, so remember to regard your own company as the unique entity that it is.
Once you have a feel for the vendors that are most suitable for your needs, you should start engaging sales professionals in initial 20-30 minute conversations on what you are trying to achieve, as well as finding out more from vendors on their potential suitability for your project.
Before a demo, give the vendor as much detail about your unique requirements, business processes, and ultimate goals as you’re willing to share– this will help the vendor focus on the most relevant functionality for your needs.
Once you have a shortlist of worthy candidates, the next logical step is to schedule some demos. I recommend a 60-90 minute demo to begin with – anything shorter is not worthwhile to get a full grasp on the software capabilities.
There seems to be two schools of thought regarding demos and how much information to provide to the vendor, prior to the big day. Some companies like to keep their cards close to their chest and ask to see the “out-of-the-box” functionality. Others choose to provide the vendor upfront with their detailed requirements, existing reports, and sample data, in order for the demo to focus specifically on what the customer is looking to solve.
I favor the latter approach, as it gives the vendor the opportunity to tailor the demo to the needs that are of most importance to the customer. This helps both sides to focus the conversation on exactly how the software functionality will make the customer’s job easier. Tell them what you want to achieve or what you’re struggling with, and let them do the work of showing you how their product will solve all your problems. And quite frankly, if you are looking to catch out a vendor who doesn’t have everything you need, then the relationship is already off to a pretty bad start!
Longer sessions and “focus groups” can be arranged as a follow-up. Second and third demos are par for the course in most selection processes. These additional demos will give you a chance to whittle down the competition, plus give you the opportunity to reflect and to go back to the vendors with any additional questions, requirements, and clarifications.
As you continue through the purchasing process, you will find yourself building bonds with the best vendors. This working relationship is key to a lasting experience that assists your business in getting the “mission-critical” EHS work done.
As your relationship with a vendor grows, you should start to see evidence of a cross-departmental team that is committed to your satisfaction and your business’s compliance success.
The best EHS vendors will have a healthy mix of subject matter experts, project managers, developers, and sales professionals – all dedicated to keeping your business compliant and happy enough to renew your subscription, year after year.
Pricing is obviously a concern for any customer, and it’s important that you fully understand what the vendor is going to charge you. The last thing you want is to agree on a project and implementation process, only to be hit with a hefty bill once the software has been deployed – for what you felt was a minor change.
Useful questions to ask:
Once you have settled on a vendor and are ready to embark on the implementation, the real fun begins. Now you can start to reap the benefits of your carefully planned and executed selection process.
Good luck out there!
—
About guest blogger— Remy Leaf, Locus Technologies
Remy Leaf has worked in the EHS industry for 6 years, since graduating from the University of the West of England with a BSc in Environmental Management & Sustainability. His current role with Locus is Sales Engineer, working with new and prospective customers to identify their EHS targets.
The new visual rule configuration leverages the latest web technologies. We designed it to efficiently perform tasks in the software configuration process – without any programming. This helps Locus Platform customers meet rapidly changing EHS&S software requirements at lower cost.
SAN FRANCISCO, Calif., 18 October 2016 —
Locus Technologies (Locus), the leader in cloud-based environmental, sustainability, energy, and compliance management software, has once again expanded on the configurability of its cloud-based Locus Platform. Locus Platform is introducing new visual rule configuration, which allows users to conditionally change the behavior of fields within any form using a simple interface that requires no additional software code.
The system can be easily configured to make certain fields conditionally visible, editable, and required based on other information entered by the user. This makes data-dependent forms easy to construct for any application. This feature is available for all existing Locus Platform applications, as well as for customers building their own applications using the Platform’s configuration tools.
This new feature is pertinent to all EHS applications. System administrators are able to follow a simple setup wizard to create many kinds of dynamic input forms, such as collecting additional information if a user responds ‘no’ to an audit question, or displaying waste code options if a waste profile is categorized as hazardous. With visual rules, the these applications can now be reconfigured for any user without the need for any expensive software development.
With this functionality, Locus Platform emerges as a market leader in EHS&S rule management systems. The intuitive, graphical approach will make it popular with domain experts, as well as managers. EHS&S departments will be able to create and maintain business rules and to automate a wide variety of operational decisions specific to their organization, without needing any programming knowledge. Visual rule configuration reduces the time it takes to develop, implement, and update their applications, compared to traditional software.
“One of the great benefits of the Locus Platform has always been its configurability. Businesses don’t need to modify their practices and policies to fit an off-the-shelf EHS&S solution with predefined forms, features, and rules. Rather, the solution can be configured to their existing practices – without the need to ask a vendor to do it for them. And with the new visual rules feature, that configuration is easier than ever,” said Wes Hawthorne, President of Locus.
“Keeping the end users’ perspective in mind, we’ve packed the same 20-plus years of domain expertise that Locus has been offering into a highly configurable and scalable new software platform, built from the ground up using the latest web technologies,” remarked Neno Duplan, CEO of Locus.
Follow the new President of Locus, Wes Hawthorne, through his typical week to see the big picture of running a successful environmental cloud software company
Wes Hawthorne is the newly appointed President of Locus Technologies, having been promoted to this position after 17 years of working at Locus. Wes comes from a background of environmental engineering and geology, and he previously worked as VP of Operations, overseeing Locus’ operations and product management teams.
In his new role as President, Wes is quickly learning about all the aspects of the company, and what roles come together to keep it operating smoothly and successfully. As part of this, he has been getting a crash course in departments that were previously outside his scope of job responsibilities (such as sales and marketing).
Let’s follow Wes through some highlights of his typical week as the new President of Locus to see what kind of things he works on day to day.
10 a.m. – Met with our marketing team to discuss some upcoming conferences. It’s looking like it will be a busy conference season, and each conference takes months of careful planning— from booth design, to presentations, to setting up demos of our mobile app for conference attendees— but our marketing team works hard to make sure we have everything mapped out well in advance of the events.
Getting organized and ready for a busy week at Locus…
11 a.m. – Reviewed emissions and environmental data acquisition equipment for a cement manufacturing facility. One of the things I really love about working at Locus is the opportunity to work with so many industries, each with their own specific needs and requirements for managing their environmental data.
2 p.m. – Met with sales team to talk about some ongoing sales opportunities. We also talked about the kinds of company values our sales team members are communicating to our clients. Everyone agreed that one of Locus’ core strategies is having all the stakeholders involved initially, before the kickoff of the project. We have a strong cross-disciplinary team involved in making sure that every new customer has their data migrated and their personnel trained, and that they are totally satisfied with how the system is configured.
4:30 p.m. – Discussed new configurable reporting options with product management and development teams for Locus Platform. There is some really innovative work coming out of our Platform team, and no shortage of exciting ideas in the pipeline!
9 a.m. – Met with USEPA to discuss data management and reporting requirements for bioremediation projects. These projects have special data collection and analysis needs, which our EIM system handles in a very simple way. I just took a tablet into the field and was able to redesign a monitoring program on the spot with the regulator. As a result, the project is taking another step towards closure, bypassing a process that used to take months.
11:30 a.m. – Prepared an evaluation of potential uncertainty associated with cap and trade emissions credits for a winery. With cap and trade programs, the metadata related to the reported emissions and product data are just as important as the reported totals themselves. Using a transparent data set and calculation engine, I can not only review reported data, but also quantify uncertainty and sensitivity of the inputs.
Meeting with the Locus Platform dev team
3 p.m. – Met with product development team for Locus Platform to preview upcoming features, including new tools for managing Internet of Things (IoT) data feeds. The dev team showed some really interesting new features related to using IoT data, such as showing live data connection and viewing real-time dashboards. We also have some new tools that are developed to configure those features— not just to view them, but also for setting them up in Locus Platform, using its existing integration tools to pull that data in, drive actions for meeting compliance goals, and process it.
The product and development of Locus Platform is something that I’ve been involved with for several years now, but it’s still so gratifying to see the product continually evolve, and to have a hand in saying how it should grow.
8:30 a.m. – Spoke with California Air Resources Board about GHG verification requirements for cogeneration plants. I frequently interact with many regulatory agencies. Because most of our products and services are driven by regulations, I use these conversations to keep our work aligned with the current and upcoming requirements.
12 p.m. – Joined welcome lunch at Doppio Zero in downtown Mountain View for new employee Venk Madabhushi. We’re always growing and finding new recruits, and we welcome new employees and support their growth.
The company culture at Locus is a very friendly, workable atmosphere; people just get along. We have people in a lot of different multi-disciplines— you have people from the environmental engineering background, the software developers, marketing and sales personnel, field technicians, and others. It’s just a huge variety of people to learn from.
Reviewing and brainstorming about a new mobile tool for managing compliance for drinking water utilities
And culturally, I think Locus is great. Well, I’ve been here for 17 years, so I obviously think it’s a great place to work. When our customers interact with an implementation team or our products team, they can tell that we’re constantly communicating and working together, talking daily about their projects and how to keep moving forward. Keeping a positive atmosphere around how we work helps ensure that we’re all aiming towards the same goal of delivering the best product possible.
3 p.m. – Met with account management and product management to start work on a new mobile tool for managing compliance information for drinking water entities. An exciting part of our work at Locus is identifying new needs for our current customers and then finding new ways to use our technologies to meet those needs.
4 p.m. – Reviewed cap and trade applicability for a supplier of petroleum products with operations in California. Fuel marketers have very different needs for their data management when it comes to cap and trade, because the reporting is organized around regulatory boundaries rather than facilities. We used integration with the transaction database to quickly assemble the data and avoid potential transcription errors.
9 a.m. – Prepared a monitoring program for a theme park to address surface water runoff issues for permit compliance. This is a project where regulatory compliance tools are integrated with software for compiling and analyzing analytical data, in order to optimize a monitoring program that meets the specific sampling requirements of the permit. It also meets the objective of identifying the source to target future mitigation efforts.
A sample map with graduated symbols and custom layers, from our forthcoming GIS+ platform
10 a.m. – Reviewed the latest build of our GIS+ functionality with development team. As all of our customers know, Locus has provided cutting-edge mapping and visualization tools with our software for many years, and we continue to invest in those features.
But I’m really excited about GIS+, a new platform that we’re rolling out, which has amazing new tools for data analysis using Esri technology. We’ve seen our mapping and other visual analysis tools become more and more popular every year, thanks to the increasing volume of data being collected for environmental projects.
The new GIS+ is more powerful than anything we’ve offered before. It’s an all-in-one tool to give you quick visual analysis of contours or other geographic distribution of data, to give you a visual display of where things are located, make quick interpretations, and then generate report-ready deliverables. I can’t wait until our customers get a chance to try it out!
1 p.m. – Completed GHG verifications for an oil and gas producer, a distribution company for natural gas, and nine cogeneration facilities. Locus is one of the largest accredited verification bodies for GHG emissions in California. This gives us a unique perspective when it comes to this type of data, which is why we put a lot of emphasis on the quality and transparency of data in our software development.
4:30 p.m. – Reviewed applicability of data management requirements for air emissions from a power generation facility under 40 CFR Part 75. For this facility, we reviewed the system configuration to make sure that data substitution procedures were correctly applied. I’ve worked with many continuous emissions monitoring systems over the years. For the most part, I’ve found that they collect a huge volume of data, but the tools for extracting useful findings out of that data are usually limited. Fortunately, we’ve learned some quick methods for reviewing this data that help to immediately identify potential issues.
Hashing out ideas on the whiteboard
8 a.m. – Updated a compliance monitoring program for a school site that is managing arsenic issues with a surface cap. For compliance programs, you really need to look at the variety of regulations that apply to specific sites, which can be difficult and challenging. You have to not only identify them initially, but then you have to help them manage all the associated requirements. This specific project had a lot of issues with making sure they stay on top of these requirements.
At the heart of a lot of environmental remediation sites is risk management. And school sites have a particular sensitivity regarding risk. While you’re in the process of cleaning up these problem areas, there’s a real risk exposure, and minimizing the potential impact to those risk receptors is extremely important. Eventually, you need to have all of the risk receptors addressed before you can close the project.
Our team helped this particular school district to consolidate their EHS compliance requirements and develop a calendar with notifications, in order to ensure all their obligations are met.
10 a.m. – Worked on a management system for handling community outreach documentation associated with large environmental projects. Occasionally, Locus gets involved in projects that go somewhat beyond the traditional scope of “environmental data”. This could be financial data associated with environmental projects, or in this case, the public outreach documentation.
Previously, this “tangential” environmental data had to be managed in separate spreadsheets, but Locus now has the tools for building applications that are tailor-made for handling this information, and allows it to be directly integrated with the tools for managing compliance tasks or analytical data. It’s a huge time-saver to be able to maintain information on all these affiliated activities in one system.
3 p.m. – Modified a corporate compliance reporting tool for health and safety incidents for a railroad operator. A lot of times, our customers are able to teach us about how they manage and analyze their EHS data. For this project, our customer gave us some great ideas which we merged into a master template for incident reporting. Even after so many years, I’m still learning quite a bit with every new project.
5:30 p.m. – Made it through the Bay Area traffic and got my daughter to soccer practice on time. After a full and exhausting week, it was quite rewarding to relax and just watch her run around for an hour. In two more days, I’ll be re-energized to start up a few new projects and finish work on a few others. Though, if the past 17 years are any indication, on Sunday evening I’ll already be lining up my activities for the week and figuring out what new challenges Locus will tackle in the next five days.
About guest blogger— Wes Hawthorne, Locus Technologies
Wes Hawthorne has been with Locus Technologies since 1999, working on development and implementation of services and solutions in the areas of environmental compliance, remediation, and sustainability. As President, he currently leads the overall product development and operations of the company.
The first deal limiting greenhouse gasses from international aviation has been sealed after years of negotiations. Carbon emissions from international aviation will be capped under a global agreement to limit the impact of commercial flights on the climate. The deal launches a voluntary compliance system from 2021 that would become mandatory in 2027. Airlines spent about $181 billion on fuel last year, and this deal would add between $5 and $24 billion in additional costs, depending on the price of carbon at the time. The aviation carbon cuts were agreed in Montreal by national representatives at the International Civil Aviation Organization, ICAO.
The deal comes in a critical week for climate policy when the Paris agreement to stabilize climate change passed a key threshold for becoming law. International aviation is responsible for putting more carbon dioxide into the atmosphere every year than the whole of the Germany or the UK. And until now, there has been no global consensus on how to address aviation emissions.
CO2 will be allowed to grow to 2020, but after that, emissions will need to be offset. The deal will be voluntary to 2026, but most major nations are expected to take part. Airlines that pollute more than the prescribed level after 2020 would have to purchase carbon-offsetting credits.
The offsetting proposal is especially controversial. Airlines are striving to make planes more efficient, but the industry can’t innovate fast enough to contain its dynamic growth.
That led to the proposal for offsetting – but sometimes offsetting by planting trees is not enough and is prone to double-counting.
One way to offset emissions, besides planting trees, is using trees’ and other plants spoils to make sustainable fuels. The effort to use sustainable fuels has already started, and manufacturers and airlines support of alternative fuels is high.
To that end, the US biofuels leader, Amyris, Inc is developing an alternative aviation jet fuel made with a sustainably-sourced hydrocarbon using Amyris’s proprietary synthetic biology platform. It is one of the most promising developments in aviation fuels in decades.
Amyris’ jet fuel can reduce greenhouse gas emissions by up to 80 percent compared with petroleum fuels, when compared unmixed to petroleum fuels on a one-to-one basis, according to Amyris.
Attempts have been made for nearly two decades to include aviation and shipping in the UN’s climate agreements, but both sectors have managed to avoid firm targets.
US EPA earlier this year issued a final scientific assessment that concluded that carbon emissions from aircraft endanger public health and welfare, a legal prerequisite the agency must take before regulating those emissions in the US. It is widely expected that EPA will introduce its set of rules for regulating domestic aircraft emissions in the US. Domestic aviation represents about 40% of total carbon-dioxide output from commercial flights.
Environmental groups said they hope the action to curb airline emissions will spur a similar cap on maritime CO2 production. Maritime emissions aren’t covered by the Paris climate deal even though the industry is considered a major carbon emitter.
All these emissions trackings must be managed and verified and will require companies to install scalable and intelligent database systems like Locus SaaS-based EIM and Locus Platform that already help many companies comply with various emission laws and regulations around the world.
Modern software technology and design has enabled an unprecedented amount of creation and innovation by managers, subject matter experts, and technical staff.
Before, if you wanted a new custom facility environmental audit form, you had to create a set of specifications, outline all functionality, and engage software developers to create the application (or just do it all on paper). This approach could take months to develop, test, debug, and rework. With the tools we have now, this kind of custom job can be done within a day, complete with mobile-enabled forms. It’s amazing how modern technology is such a huge time and cost saver. But it also introduces a new list of challenges that have to be considered when taking ownership of a configurable software solution.
While we now have easy-to-use tools for creating applications, you still need to define what you want to get out of the application you’re making. When you buy pre-configured software, you adapt your process to fit the constraints of the system you just bought. When you buy configurable software, you’re able to create the exact workflow that you need, but you have to first develop a complete understanding of what your needs actually are. With flexible tools, it’s easy to try out different configurations with your team members. However, it’s a challenge to have your team on the same page about what configuration will benefit the entire range of users or departments.
Typically, you have to wait until a vendor updates the software and hope they address any changes you were hoping for. With configurable software, you or the vendor can make those changes anytime.
However, if you’re making these kinds of changes on your own, without proper management and communication, there is a very good chance you will create usability issues for other users in your community. Even the simplest management system for changes will make everyone’s life easier. For example, you can categorize potential changes by their urgency. The urgent changes can be notified to users immediately (as soon as they are made), and the non-urgent changes can be scheduled for later. Establishing any kind of management and communication system can help you keep your team up to date with software changes.
Configurable software, with its endless possibilities, may seem daunting. But you don’t have to be overwhelmed with options— there are plenty of people who would love to help you:
Configurable software can open up a world of options and often prove to be a great choice for many customers. But it’s important that you understand the process— including all the advantages and challenges that come with it. Decide how you want to manage the configuration and reach out to trusted people. With some preparation and an invested team, you will have no problem navigating the exciting waters that technology has made possible.
—
About guest blogger— Marian Carr, Locus Technologies
Ms. Carr is responsible for managing overall customer solution deployments and customer relationships with Locus’ government accounts. Her career at Locus includes heading the product development team of the award-winning cloud-based environmental ePortal solution as well as maintaining and growing key customer accounts with Locus’ Fortune 100 enterprise deployments. In addition, Ms. Carr was instrumental in driving the growth and adoption of the Locus EIM platform with key federal and water organizations.
SAN FRANCISCO, Calif., 24 August 2016 — Locus Technologies (Locus), the industry leader in cloud computing enterprise software for environmental, energy, air, water, and compliance management, is pleased to announce that the company has undergone a Service Organization Control 1SM and 2SM examination. A CPA report has been issued stating that Locus Technologies has maintained effective management over financial reporting, as well as the security, availability, processing integrity, confidentiality and privacy of its Software as a Service (SaaS) system. The assessment was performed by A-Lign. Locus is proud to have held these reports for the past four years.
The SOC 1SM report provides assurance to current or potential customers about the effectiveness of financial reporting systems at Locus. This report was prepared in accordance with Statement on Standards for Attestation Engagements (SSAE) No. 16, Reporting on Controls at a Service Organization. It is specifically intended to meet the needs of the entities that use Locus’ SaaS products and the CPAs that audit Locus’ financial statements, in evaluating the effect of the controls at Locus on the company’s financial statements.
Locus’ SOC 1SM report is a Type 2–report stating that the presentation and description of Locus’ system is fair, and that its design and operating effectiveness of controls achieve the related objectives included in the description throughout a specified period of time.
The SOC 2SM report is designed for customers who inquire about the effectiveness of controls at Locus that are relevant to the security, availability, or processing integrity of the system Locus uses to process customers’ information, or the confidentiality or privacy of that information.
The SOC 2SM report places Locus in a rare category among environmental data management providers to have attained this rigorous classification. In today’s corporate social responsibility (CSR) and risk-management environment, it is essential that service providers like Locus demonstrate that they have adequate controls and safeguards in place, so customers can be confident that their data are safe. Unlike most other environmental data management providers, Locus does not limit the SOC 2SM review to their data centers for hosting, but rather the entirety of the software development and management process, including the data centers.
“We are pleased that our SOC 1SM report has shown that we have the appropriate financial controls in place. This is in addition to a SOC 2SM report we received that is focused on mitigating risks related to security, availability, processing integrity, confidentiality and privacy of customers’ environmental, energy, sustainability, and compliance data stored in Locus’ cloud,” said Dr. Neno Duplan, CEO of Locus Technologies.
“The culture here at Locus is to put our customers first at all times, and it is essential that they feel secure with our financial information management and in trusting us with their data.”