CEMView is software and software is intellectual property (IP). At Nexus Solutions, we believe that CEMView must deliver the best value and our software enhances many analyzer hardware platforms to truly deliver value to the end user. The modular and scalable nature of the CEMView platform allows the CEMView software to be configured to best suit the site specific requirements, hence there is an impact on the price of the software. We do not believe in the 'one price fits all' models that many of our competitors employ and because we do not sell hardware, we cannot adjust the hardware prices to subsidize or hide the true cost of the software.
The CEMView software price is made up of several components. There is a basic license cost for each version of CEMView. This cost reflects the features and the target markets of the product. The Nexus Solutions pricing model is further built-up on a number of parameters that reflect on the specific application and regulatory requirements. Parameters that affect the cost include the number of sources or processes, the specific analyzers being used, the number of primary pollutants being monitored, and the calculations and corrections, including process parameters and connectivity requirements to the process control system, that affect what the reporting requirements are for the system.
The number of logically distinct processes affect the number of completely independent CEMView Server instances, each with its own SQL Server database instance, that run on a single computer. A source may or may not have a one-to-one relationship with the number of analyzers or processes. Multiple sources could exist on a single process. Multiple processes could share a single common stack, in which the measured pollutant by an analyzer is apportioned to each source. Analyzers could be dedicated to a single source or time-shared to monitor multiple sources. The number of pollutants being measured varies and some source measurements impact the complexity of the system differently than others.
For example, the measurement of stack flow rates or energy rates would result in the computation and need to report mass flow rates or energy rates for many monitored pollutants. The measurement of temperature or pressure would affect the number of computations required for standardized and normalized pollutant values, but the number of reported pollutants would not change. The regulatory requirements for the application also significantly affect the complexity of the system. Types of regulatory averages to be computed, with specific averaging rules and averaging procedures, as well as permanent record keeping, automatic or manual data backfill requirements, basic or specific custom reports and electronic data reporting requirements all affect the pricing model.