NeCCS stores data in a database (SQL Server) and therefore one of the main differences in using NeCCS compared with using the CHARM Calculator is that the basic data need only be entered once. For example, if many chemical scenarios need to be reported for one installation then the data pertinent to the installation need only be entered once. Then for each scenario (Application) the required installation data is called up .
Similarly substance data with its related toxicity test information can be entered and saved, and products can be defined based on the substances entered.
To create a report for a particular scenario, an Application is created by selecting an Application Type, e.g. Production, then the pre-defined installation and product information are used. The concentration and flow parameters for this scenario are added, and the calculations run. The report can be displayed and the Application saved so that it can be revisited on another occasion.
The use of the database has many advantages for managing data.
|
Feature |
Included in NeCCS |
Included In CHARM |
|
Data entry and calculations |
|
|
|
Storing platform / installation parameters in database |
Ö |
|
|
Storing toxicity test data in database |
Ö |
|
|
Storing substance definition in database |
Ö |
|
|
Define both minimum and full dataset products |
Ö |
Ö |
|
Define products based on pre-defined substances |
Ö |
|
|
Define chemical use scenarios for all the application types identified in CHARM |
Ö |
|
|
Save Application scenarios in database |
Ö |
|
|
Run calculations to produce HQ or RQ report |
Ö |
Ö |
|
Save report to PDF format |
Ö |
|
|
Data import and export |
|
|
|
Allow export of installation, substance, product or application data |
Ö |
Ö |
|
Allow import of data from other NeCCS users |
Ö |
|
|
Allow import of data from CHARM Calculator |
Ö |
Ö |
|
Allow export of data to CSV format and import to Word |
Ö |
|
|
Manage software, licences and users |
|
|
|
Install independently of other software on destination computer |
Ö |
|
|
Allow multi-user access to one database |
Ö |
|
|
Provide for management of user-licences |
Ö |
|
|
Provide for creation and management of user ids |
Ö |
|
|
Tailor the functions available according to the type of user |
Ö |
|
|
Allow setting of user preferences in software |
Ö |
|
|
Allow password controlled access and password management |
Ö |
|