Services | Page 11 of 17 | Locus Technologies

Top 10 cool features in EIM (that you probably didn’t know about)

1. “Show locations on map” from a grid

In many locations in EIM, you can make a map directly from your query results. Click on the “folded map” icon on a results grid anywhere in EIM to open the GIS application, where you can then view and save your results as a map query layer.

So if you’re looking at TCE in specific locations, you can quickly map them and see what other parameters are present.

2. Save custom grid configurations

When you see a pushpin icon below a grid, that means you can name and save your current configuration in the grid, including column visibility, column order, sorting, and column width.

So if you use certain grids all the time, and prefer to view the data in a specific way, just click the pushpin and save your configuration for future use.

3. Save and share maps and reports on the dashboard

You can share saved maps and formatted reports with your colleagues and team members on the Project Manager Console dashboard. Saved maps and quick reports will show up under the sections “Quick Reports” and “Quick Maps”.

See Tip #4 to learn how to make this dashboard your default homepage.

4. Set your homepage and your preferred default grid row count

EIM user options includes some very cool features. You can access your user options from the EIM menu: just click [your username] > Manage Profile.

Here, you can set your preferred homepage, enable filter options for easier login, and— our favorite— the option to adjust the default number of records to display in all EIM grids (20 is just never enough!)

5. Lab Invoice Tracking

Full invoice tracking down to the parameter delivered level, to help you confirm that the lab gave you what you ordered, and that they’re charging you for exactly what they gave you.

You can find these forms at Input > Analytical > Lab Invoices.

6. Simple or complex query building in a drag-and-drop interface

For users wanting to go beyond the standard “out-of-the-box” queries, EIM has an advanced query builder that lets SQL lovers go wild and share their results with other. You can even query data across multiple EIM sites to which you have access.

7. Easy data preparation for annual Consumer Confidence Reports (CCRs)

If you have the Locus EIM Water configuration, you will be able to prepare data tables for the CCR reports that all water providers are required to prepare annually. This is a huge timesaver compared to manually preparing these data summaries that are required by the Safe Drinking Water Act.

8. Send your sampling plan directly to your mobile device

With EIM’s integration with mobile, you can create a sampling plan in EIM and send that plan to one or more people to perform field sampling. This saves mountains of time and ensures your field teams have the correct information they need to collect their field data.

The sampling team can sync anytime to have team members back in the office review the interim data.

9. Create NetDMR submittals directly from EIM

If you have to submit EPA NPDES DMRs, EIM can create the electronic NetDMR output, saving you time and effort and banishing (hopefully) those old, complex, and overly difficult paper forms.

10. Support menu alerts you when new user guides, cheat sheets, training videos, or FAQs are posted

Locus is always busy creating new guide documents and help materials for our users, but it was hard to know when we added some new content. Now, our Support menu itself will flag you as soon as something new is posted so you can check it out!

Locus Technologies performs a record number of GHG verifications in California

Locus takes the lead in GHG verification services for California Air Resources Board AB32 Program

MOUNTAIN VIEW, Calif., 8 February 2017 — Locus Technologies (Locus), the industry leader in multi-tenant SaaS environmental compliance and information management software, performed 74 verifications for the reporting year 2015 for the California Air Resources Board AB32 Program — more than any other accredited verification body. With six full-time accredited verifiers, Locus has been providing verification services since 2010 for reporting entities across California. Even more notably, after completing hundreds of these verifications and complying with several routine audits by ARB, Locus has never had a single verification statement overturned. This means that facility operators using Locus’ verification services have high confidence that their participation in the cap and trade program will not be affected by potential delays related to questions on their verification statement.

The GHG verification services cover facilities in California that are regulated by the California Air Resources Board (CARB) under the Mandatory Reporting Rule (AB32). Locus is accredited as a verification body through CARB and has Lead Verifiers certified in all reporting sectors, including process emissions, oil and gas, and transactions. Over the past eight years, Locus staff have completed verifications for several industries and have become experts on reporting for most covered product types which translate into emission allowances under the cap and trade program.

GHG emission reports are coming under increased scrutiny from regulators, stakeholders, and financial auditors. Choosing the right verifier plays a critical part in remaining compliant with these rapidly evolving requirements and regulations. Locus verifiers have noticed that many companies struggle with complex GHG calculations. Some ‘black box’ calculation tools in the market have not been sufficiently stress-tested and are generating errors that cause enterprises to fail their GHG verifications. Locus’ calculation engine addresses these deficiencies and capitalizes on the architecture of the highly scalable Locus platform. All calculations performed by Locus SaaS are viewable and traceable through the tool to the original data inputs.

“We are very pleased to lead the California verification program and that so many Fortune 500 firms selected Locus for verification services. Locus continues to expand its carbon practice at a rapid pace. Coupled with our software services and domain expertise in all three key AB32 reporting sectors, Locus is becoming a partner of choice for all companies wishing to be credible in their carbon reporting needs,” said J. Wesley Hawthorne, President of Locus. “Our growth in this market has been largely fueled by referrals from existing customers, and it speaks volumes about the quality of our service that so many of our customers speak highly of Locus to their colleagues.”

EHS SaaS explained: Multi-tenancy is a difference that makes a difference

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 announcement¹ 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

¹Gartner Inc., “SaaS will have significant impact on IT services and outsourcing providers,” Tekrati, 7 March 2007

Configurable software solutions—Change is good, right?

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.

You need to know what you want.

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.

Just because you can make easy and fast changes, doesn’t mean you should.

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.

You are not in this alone.

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:

The software vendor can be your configuration partner and do the work at your direction. You get real-time updates to ensure the configuration keeps heading in the right direction toward fulfilling your needs— and you can spend your time focusing on your business, rather than configuring the software.
Your consultants can configure for you. It’s very likely that you have great, trusted relationships with the consulting community, who already know you and have developed some understanding of your business needs. These resources can help to ensure you get the perfect solution.
Your staff likely has people that would love to configure and would jump at the chance to develop an effective solution that benefits the department and the organization as a whole. They are easy to spot— they spend time in Excel and write macros for fun.

Bottom line: Plan, prioritize, partner.

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.

—

Still looking for the right EHS software to revolutionize your environmental and compliance initiatives? Book a demo with us today!

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.

Why SaaS multitenancy is key to successful and sustainable EHS management

A recently published survey by a research analyst firm indicates that 90 percent of EHS software applications installed today are single-tenant on customer premises or single-tenant, vendor hosted. Only 10 percent are multitenant, vendor-hosted. In other words, most of the vendors in the EH&S space do not run a single version of their software maintained at one location. Instead, they run multiple copies at a single or multiple locations, with the high likelihood that these multiple copies are not alike, but instead represent multiple versions or contain specific customizations for individual customers. This model is crushing their growth and scalability potential.

Locus delivers EHS+S SaaS solutions as highly scalable, Software as a Service (SaaS) application and platform services on a multitenant technology architecture. Multitenancy is an architectural approach that allows Locus to operate a single application instance for multiple organizations, treating all customers as separate tenants who run in virtual isolation from each other. Customers can use and customize an application as though they each have a separate instance, yet their data and customizations remain secure and insulated from the activities of all other tenants. Locus multitenant services run on a single stack of hardware and software, which is comprised of commercially available hardware and a combination of proprietary and commercially available software. As a result, Locus can spread the cost of delivering EHS SaaS services across user base, which lowers the cost for each customer. Also, because Locus does not have to manage thousands of distinct applications with their business logic and database schemas, we believe that we can scale our business faster than traditional software vendors. Moreover, we can focus our resources on building new functionality to deliver to customer base as a whole rather than on maintaining an infrastructure to support each of their distinct applications.

Multitenancy also allows for faster bug and security fixes, automatic software updates and the ability to deploy major releases and frequent, incremental improvements to Locus’ services, benefiting the entire user community. Our services are optimized to run on specific databases and operating systems using the tools and platforms best suited to serve customers rather than on-premise software that must be written to the different hardware, operating systems and database platforms existing within a customer’s unique systems environment. Locus developers build and support solutions and features on a single code base on our chosen technology platform. Locus efforts are focused on improving and enhancing the features, functionality, performance, availability and security of existing service offerings as well as developing new features, functionality, and services.

Locus customers and third-party developers can create apps rapidly because of the ease of use of Locus Platform and the benefits of a multitenant platform. Locus provides the capability for business users to configure applications easily to suit their specific needs.

Also, Locus multitenant cloud platform makes it possible to use a remarkably small number of servers as efficiently as possible. When organizations move business applications to Locus, they can significantly reduce their energy use and carbon footprints compared to traditional on-premises or single-tenant or ASP solutions

Locus built and maintains a multitenant application architecture that has been designed to enable service to scale securely, reliably and cost effectively. Locus’ multitenant application architecture maintains the integrity and separation of customer data while still permitting all customers to use the same application functionality simultaneously.

Both Locus and its data centers providers hold independent AICPA SOC1 (SSAE16) and SOC2 certification.

Locus Technologies introduces indoor air management application

The Locus indoor air management application is fully integrated with the dynamic Locus Platform and will automate indoor air management for small and large enterprises.

MOUNTAIN VIEW, Calif., 6 June 2016 — Locus Technologies (Locus), the leader in cloud-based environmental compliance and sustainability management software, introduces an all-new vapor intrusion and indoor air management application to its newest platform to redefine how companies organize, manage, and report their indoor air and vapor intrusion data. The Locus platform— a true, multi-tenant SaaS— offers a highly configurable, user-friendly interface to meet individual organizations’ environmental management needs.

Indoor air quality is becoming an important environmental and chemical exposure challenge for many companies whose properties may be impacted by contaminated groundwater or soil that release vapors or fumes. Once the indoor air quality problem is identified, it follows a lengthy investigation that can involve several phases of sampling (including soil-gas, subslab, pathway, and ambient indoor air samples) using either active or passive sampling techniques. Samples are typically composited over time periods that can range from hours to weeks. A substantial amount of additional metadata is collected surrounding each sampling event, including information on the building construction, layout, occupancy, chemical use, and heating and ventilation systems.

All these activities generate large quantities of data, which until now were managed primarily by spreadsheet scattered on laptops or desktops. Locus’ new application brings an organized approach and workflow process to schedule, sample, and manage analytical results stemming from investigation and ongoing monitoring programs. Tools are also included to track the status and effectiveness of mitigation efforts related to indoor air quality. The data are easily summarized for review through reporting and built-in mapping tools, which can identify adjacent properties at potential risk for indoor air quality issues. Plus, if a customer is already a subscriber to Locus EIM, Incidents, or other Locus Platform applications, they can correlate data among various applications and facilitate finding the cause of degradation of the indoor air quality.

“Indoor air quality and vapor intrusion are gaining more and more attention from regulators, property owners, and managers of environmental sites. These projects generate a large volume of structured and unstructured data as part of the investigation and mitigation processes. To successfully compile and review this information, companies need a software that can manage these various data types and allow quick review and decision making. The right software can reduce the stress, time, and potential inaccuracies associated with these projects.” said Wes Hawthorne, Senior Vice President of Locus.

The new TSCA law not REACH (in data requirements)

After a bipartisan accord, the US Congress overhauled the 40-year-old Toxic Substances Control Act (TSCA), with legislation to give the EPA greater powers to regulate about 100 hazardous chemicals. This is the first major statutory update to US environmental law that’s been passed in over 25 years. On a 403-12 vote, the U.S. House of Representatives on 24 May 2016 approved bipartisan legislation to amend the key provisions of the TSCA.

Under existing law, the Environmental Protection Agency (EPA) has succeeded in regulating only five toxic chemicals since 1976, prompting public health advocates to decry TSCA as broken. Part of the problem is that the law grants EPA only 90 days to decide whether a new chemical poses “unreasonable risk” before it can enter the market, and agency officials say they rarely get the toxicity data they need to make that call in time.

The compromise legislation will remove those procedural hurdles, require EPA to focus on “high priority” chemicals such as arsenic and asbestos, and give the agency new tools to collect data from companies. It also grandfathers in some existing state chemical safety laws, such as those enacted under California’s Proposition 65, but limits states’ authority to create their own restrictions on chemicals in the future. State pre-emption was a key point of contention between Democrats and Republicans during negotiations.

So how does the new TSCA law compare to the EU REACH program? REACH (Registration, Evaluation, Authorization and Restriction of Chemical substances) is a regulation of the European Union, adopted to improve the protection of human health and the environment from the risks that can be posed by chemicals. REACH also promotes alternative methods for the hazard assessment of substances to reduce the number of tests on animals. Under the REACH Regulation, companies are responsible for providing information on the hazards, risks and safe use of chemical substances that they manufacture or import.

One notable difference between REACH and TOSCA is how they support downstream users in implementing their chemicals management programs. Regarding knowing chemicals in products, REACH provides clear direction that downstream users must communicate uses up to suppliers and know and publicly disclose (if requested) if their product contains substances of very high concern (SVHC). The TSCA does essentially nothing to support downstream users in knowing chemicals in products and disclosing them to the public, and its requirements for upstream communication to suppliers on uses are uncertain.

Significantly, REACH requires companies to provide minimum data sets on the inherent hazards of chemicals. This data enables downstream users to evaluate and compare chemicals on their hazard characteristics. TSCA, while expanding the ability of the US EPA to require testing of chemicals, explicitly prohibits the agency from requiring minimum data sets.

While it is important to avoid the unnecessary testing of chemicals, it is also vital to have a data set on chemicals that enable their comparison on a common set of endpoints. The EPA needs the authority to establish a minimum data set on chemicals, although this may differ depending on the specific chemical.

On assessing the hazards of chemicals, the new US law falls short of REACH and impedes harmonizing European and US requirements for chemical testing. Given that most US chemical companies sell into the European market, and therefore are already meeting those requirements, it is inefficient and wasteful to establish a totally separate testing regime in the US.

To support the use of inherently safer chemicals, REACH provides a clear and more streamlined process for identifying and restricting SVHCs. Over the course of seven years, the Regulation has identified 161 Candidate SVHCs, while over five years, the US bill only requires the designation of 25 high priority chemicals and with new law extending that number to about 100 chemicals. Harmonization, consistency, and predictability are critical for downstream users, and these elements are all lacking in the new TSCA law.

Stanford Board of Trustees issues a statement on climate change

In a statement, the Board of Trustees underlines Stanford’s commitment to battling climate change, highlights university initiatives to address it and responds to Fossil Free Stanford’s request to divest from the fossil fuel industry.

The trustees have concluded that Stanford’s endowment will not divest, based on a review of criteria in the university’s Statement on Investment Responsibility and input from the Advisory Panel on Investment Responsibility and Licensing. The trustees also announce a new climate task force that will solicit new ideas from across the Stanford community for addressing climate change.

Find out more about Stanford University’s new climate change policy.

Locus Technologies introduces new calculation engine for GHG emissions inventories

The Locus GHG calculation engine is fully integrated with the dynamic Locus Platform and will automate emissions calculations for large enterprises.

MOUNTAIN VIEW, Calif., 20 November 2015 — Locus Technologies (Locus), the leader in cloud-based environmental compliance and sustainability management software, introduces an all-new calculation engine to its newest platform to redefine how companies organize, manage, and calculate their greenhouse gas (GHG) inventories. The Locus Platform offers a highly configurable, user-friendly interface to fully meet individual organizations’ environmental management needs.

With an increased focus on the role that GHG emissions play in climate change, ensuring that companies’ emissions are reported accurately is more important than ever. GHG emissions reports are coming under increased scrutiny from regulators, stakeholders, verifiers, and financial auditors. Choosing the right calculation engine plays a critical part in remaining compliant with these rapidly evolving requirements and regulations.

Locus GHG calculation engine eases compliance burdens for GHG tracking

GHG inventories may be the result of mandatory state, regional, or national reporting programs, such as California Air Resource Board (AB32), U.S. EPA Mandatory Reporting Rule, or European Union Emissions Trading Scheme (EU ETS). Organizations need a GHG calculation engine that can calculate GHGs automatically and accurately from all emission-producing activities at all of their facilities anywhere in the world. The new Locus calculation engine supports simultaneous calculations using multiple methods so that users can input data once and report to federal, state, and voluntary reporting programs according to each proper protocol.

“The requirements and procedures for GHG reporting are varied, complex, and rapidly evolving. To ensure compliance, companies need a calculation engine that can handle complex equations using appropriate emission factors, conversion factors, and calculation methodologies for each reporting program. The right calculation engine can reduce the stress, time, and potential inaccuracies found in home-grown accounting methods,” said Neno Duplan, President and CEO of Locus.

New GHG calculation engine removes reporting inaccuracies

As a leading accredited GHG verification company in California, Locus observed challenges that many companies experience with GHG inventory calculation, coupled with the gross inadequacy of tools previously available in the market. Informed by the verification of hundreds of inventories, Locus developed the new calculation engine.

“Besides spreadsheets, many calculation engines are proprietary to software vendors and are not transparent. For GHG calculations to pass audits and meet cap & trade requirements, transparency is absolutely required. Some of these ’black box‘ calculation tools have not been sufficiently stress-tested in the market and are generating errors that cause enterprises to fail their GHG verifications. Locus’ calculation engine addresses these deficiencies and capitalizes on the architecture of the highly scalable Locus platform. All calculations are viewable and traceable through the tool to the original data inputs,” said J. Wesley Hawthorne, Locus’ Senior Vice President of Operations and an accredited GHG verifier.

When evaluating carbon management software with built-in calculation engines, companies must ensure that users are able to define both the calculation rules and display of calculated data for the purpose of reporting to various regulators. By giving end users the power to view, analyze, and make changes to analytic model data, Locus helps companies emphasize the transparency of the process and ensure that calculations are correct and that the company meets all verification requirements.

“We listened to industry users and created a configurable calculation engine that is easy to use, dynamically driven, transparent, provides reproducible calculations, and is easy to verify. This calculation engine, along with the Locus Platform, will improve companies’ data collection, analysis, and most importantly, reporting capabilities,” added Duplan.

Locus will conduct live demonstrations of the Locus Platform and calculation engine at the Locus booth at the National Association for Environmental Management (NAEM) 2016 Sustainability Software and Data Management Conference from March 15-16, 2016 in Tampa, FL.