The LOLI Database
June 15, 2016
Table of Contents:
Table of Contents:
2
Executive Summary
3
LOLI Database
4
List Content
4
Substance Content
5
Entity Relationship Diagrams (ERD)
7
Content Storage via Extensible Markup Language (XML)
8
EXAMPLE 1: Toxicology Data - Selected LD50s and LC50s
EXAMPLE 2: Norway - Occupational Exposure Limits - STELs
8
10
Chemical Name Translations
12
Regulatory Data Translations
12
LOLI Datafeed
LOLI Datafeed System Requirements
LOLI Desktop
13
13
14
LOLI Desktop Features
14
Change Reporting
14
LOLI Desktop Versions
15
LOLI Desktop – Enterprise edition
15
LOLI Desktop – Personal edition
15
LOLI Desktop: Minimum System Requirements
15
LOLI Desktop, Enterprise Edition (Network Setup)
15
LOLI Desktop, Personal Edition (Standalone Setup)
16
LOLI in the Cloud
17
Minimum System Requirements
17
The LOLI-SAP EHS&T Compliance Suite
18
ChemADVISOR Online
18
Data Delivery Options
19
2
The LOLI Database
Executive Summary
ChemADVISOR is a leading provider of international chemical regulatory information. Our LOLI (List of
Lists) Database is the most extensive product of its type on the market, and it serves as a powerful tool
in support of our consulting services and the compliance efforts of organizations around the world.
The LOLI (List Of LIsts) Database contains over 5600 regulatory lists, including environmental, health,
safety and transportation regulations, international inventories, and reference material necessary for
Safety Data Sheet ((M)SDS or SDS) preparation.
ChemADVISOR provides several software interfaces for the database including:





LOLI Datafeed
LOLI Desktop
LOLI in the Cloud
ChemADVISOR Online
The LOLI-SAP EHS&T Compliance Suite
The information herein contained is proprietary and confidential.
3
The LOLI Database
LOLI Database
The LOLI (List Of LIsts) Database contains over 4700 regulatory lists, including environmental, health,
safety and transportation regulations, international inventories, and reference material necessary for
Safety Data Sheet ((M)SDS or SDS) preparation.
List Content
A LOLI List's content mainly utilizes the following four tables within a LOLI Datafeed:




ListNames
o This table is the parent table for a list
o Its primary key is a numeric ListID field and thus has one record per LOLI List
o Each record's values apply to an entire LOLI List as a whole
o The data in this table is what ChemADVISOR refers to as the "List Header" and is
comprised mainly of List Name, List Document, List Abstract, List Source, Date Updated
ListNames_Control
o This table is an extension of the ListNames table in that its primary key is also the ListID
field and thus has a 1:1 relationship with ListNames.
o The reason this is separate is because this table contains meta information about the list
as a whole and not what would be considered 'list content'
o The data in this table is designed to assist programmers in the consumption of LOLI List
data content by containing such meta-data as a given list's XML structure
ListData
o This table is the child of ListNames and its primary key is a compound key comprised of
the ListID field and the Cas field.
o This structure allows the storage of multiple unique numeric identifiers (Cas field) per
ListID
o Each record contains the content that applies to the given ListID and Cas identifier
combination stored as aggregate data (delimited text) within the Data field and as XML
within the XML field
CasSyns
o This table is comprised of chemical name synonyms for numeric identifiers (mainly CAS
numbers) found throughout the database
o This table is referenced within the ListData table in order to associate a specific chemical
name that a given LOLI List's source documentation uses for a given numeric identifier
(CAS number)
 Below is how this reference is organized:
ListData.Cas + ListData.SynID + ListData.LangID =>
CasSyns.Cas + CasSyns.SynID + CasSyns.LangID
The information herein contained is proprietary and confidential.
4
The LOLI Database
Substance Content
The LOLI Datafeed contains Chemical Substance related content to assist in the support of searching for
and better utilizing the LOLI List content. Substance content mainly utilizes the following four tables
within a LOLI Datafeed:



CasNames
o This table is the parent to all chemical substance based tables
o The primary key of this table is the Cas field
o The Name field within this table is considered to be the given substance identifier's (Cas
field) "Primary Name" (a.k.a. default name)
 ChemADVISOR software uses this name as a default when no name is given
 NOTE: This name corresponds to the CasSyns.IsPrimary flag
o Since this table contains all of the unique chemical substances within the LOLI Datafeed,
additional fields were added to take advantage of this
 The Formula field contains the molecular formula for each substance
 The InventoryStatus field contains a calculated value that can be used in
conjunction with the ListNames.InventoryFlag as a quick way of checking
whether or not a given substance is on a given government inventory list
CasSyns
o This table has two purposes, as explained in the LOLI Content section above, this table
can be used in conjunction with the ListData table in order to find the name on list
o Additionally, this table contains multiple chemical name synonyms per numeric
identifier for a given substance and language
CasLinks
o The primary key of this table is Cas and LinkCas, which are equivalent fields in that the
hold the same kinds of identifiers
o This table is used to link two related substance identifiers
o This table should be used when one wishes to see all of the related LOLI List content for
a specific chemical substance in order to have a more complete result
 This is because some regulatory bodies list substances in a way that
encompasses a category of substances rather than list every specific substance
within a category
o For example, if one were searching for all LOLI List content related to the chemical
substance "lead sulfate" without utilizing the CasLinks table, then the results would only
include those LOLI Lists where the CAS number for "lead sulfate" is specifically regulated
and miss all of the LOLI Lists were this substance is regulated because it is considered a
"lead compound"
o The Cas field of this table contains the primary chemical substance identifier and the
LinkCas field contains the chemical substance for which the Cas substance is linked
 In the above example, one would search CasLinks.Cas for lead sulfate's CAS
number and find the numeric identifier associated with "lead compounds" and
The information herein contained is proprietary and confidential.
5
The LOLI Database
include both of these substance identifiers when searching the ListData.Cas field
to find all associated LOLI Lists

CasKeys
o This table's primary key is comprised of Cas, DataKey, and DataKeyType
o Since the LOLI Database is primarily a "CAS number" based database, one must have the
CAS number (or equivalent RR number) to obtain the LOLI List content associated with
the given substance.
o If a user wishes to find all of the LOLI List data related to a chemical substance but only
has an alternative numeric identifier, such as EINECS number, then this table can be
used to find the CAS number association
o The DataKey field in this table contains the alternative numeric identifier associated
with the numeric identifier contained with the Cas field, which is typically a CAS number
o The DataKeyType field contains a descriptive key that categorizes the DataKey value as
being of a specific type, such as "EINECS number"
 The DataKeyType field is supported by the DataKeyTypes table which has a
primary key of DataKeyType and contains all of the unique DataKeyTypes
contained within the LOLI Datafeed along with a brief description of each
The information herein contained is proprietary and confidential.
6
The LOLI Database
Entity Relationship Diagrams (ERD)
Content Tables
NameTypes
Languages
ListNames
Regions
PK
PK,FK3,I1
Region
U1
Description
ListNames_RegBasis
PK
RegBase_ID
RegulatoryBasis
ListDataTypes
PK
ListDataType
Description
FK5,I4
FK2,I3
FK1,I2
FK4
PK
CasSyns
LangID
PK,FK1,I3,I1
PK
PK,FK2,I2
ListID
ParentLangID
Language
IsActive
IsUnicode
LOLISAP_LangID
SAP_LangID
ISO_LanguageName
ISO_LangCode_639_1
ISO_LangCode_639_2
ISO_LangCode_639_3
Admin_Notes
ListName
ListDocument
ListAbstract
ReviewDesc
SourceAbstract
ListSize
DateAdded
DateReviewed
DateUpdated
ListCategory1
ListCategory2
RegLink
SourceCitation
Region
ListDataType
LangID
SourceRevision
RegBase_ID
PK
Cas
SynID
LangID
TypeMask
Abbreviation
SAP_ID_Type
TypeName
CasSort
Name
Search
NameSort
IsPrimary
inListData
NameType
Name_MD5
I5
I4
Position
CasNames
PK
I1
CasKeys
Cas
PK,FK1
PK
PK,FK2,I1
CasSort
Name
NameSort
InventoryStatus
Formula
UnLinkable
Source_Count
ListData
PK,I2,I1
DataKeyTypes
ListID
CasLinks
ListNames_Translation
PK
PK,FK1
ListNames_Control
PK
Cas
DataKey
DataKeyType
I5
ListID
LangID
FK1,FK2,I3
FK1,I3
ListID
ListName
UPD_ID
InventoryFlag
LGI
XML_Schema
XML_Admin
XML_ParseGrammar
DataKeyVisible
DataKeyAlias
DataKeyType
DataKeySource
Code_Type
Translate
XML_XSD
CasSort
Data
DataKey
AdminChange
LangID
SynID
EnglishSynID
XML
UPD_ID
PK,FK1,I1
PK,I2
Cas
LinkCas
DataKeyType
Description
Condition
UPD_ID
ApprovedBy
Comments
ListData_Phrases
ListData_Translation
PK,FK1
PK
PK,FK1
PK
PK
PK,FK1
ListID
Cas
LangID
Code_Types
Code
Code_Type
PK
Data
Code_Type
Table_Name
Field_Name
Description
Phrase
STD_Text
STD_Comments
History Tables
ReleaseHistory_Structure
ReleaseHistory_Lists
PK
PK,FK1
ListID
UPD_ID
PK,FK1
ReleaseHistory
PK
UPD_ID
Version_Major
Version_Minor
Version_Build
Update_Scripts
EffectiveDate
Notes
UPD_ID
ReleaseQuarter
ReleaseDate
OfficialRelease_LOLI4
OfficialRelease_LOLISAP
OfficialRelease_OHS
ListNames_History
PK
PK,FK1
ListNames_RegBasis_History
PK
PK,FK1
RegBase_ID
UPD_ID
UpdateAction
RegulatoryBasis
ListID
UPD_ID
UpdateAction
ListName
ListDocument
ListAbstract
ReviewDesc
SourceAbstract
ListSize
DateAdded
DateReviewed
DateUpdated
ListCategory1
ListCategory2
RegLink
SourceCitation
Region
ListDataType
SourceLanguage
LangID
ShortListName
SourceRevision
RegulatoryBasis
LGI
Changes
RegBase_ID
ListNames_Control_History
PK
PK,FK1
ListID
UPD_ID
UpdateAction
InventoryFlag
LGI
XML_Schema
XML_Admin
XML_ParseGrammar
DataKeyVisible
DataKeyAlias
DataKeyType
DataKeySource
Code_Type
Translate
ListData_History
PK
PK
PK,FK1
ListID
Cas
UPD_ID
UpdateAction
Data
AdminChange
DataKey
Changes
LangID
SynID
XML
EnglishSynID
CasSyns_History
PK
PK
PK
PK,FK1
Cas
SynID
LangID
UPD_ID
UpdateAction
Name
Search
NameSort
IsPrimary
NameType
The information herein contained is proprietary and confidential.
7
The LOLI Database
Content Storage via Extensible Markup Language (XML)
All LOLI Lists are stored within a single table inside the LOLI Datafeed: ListData. ChemADVISOR achieves
the ability to store such a wide variety of content within a single table by taking advantage of eXtensible
Markup Language (XML). Each LOLI List has its own separate XML Schema definition which is available
within the ListNames_Control table and used to consume each given list's XML content from the
ListData table. This use of XML allows for a simpler database design making it much easier for
developers to consume the LOLI database for integration within third party or custom applications.
EXAMPLE 1: Toxicology Data - Selected LD50s and LC50s
TableName.FieldName
value
-----------------------------------------------------------------------------------------------ListNames.ListID:
571
ListNames.ListName:
Toxicology Data - Selected LD50s and LC50s
ListNames_Control.ListID:
571
ListNames_Control.XML_XSD: (simplified for this document)
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="root">
<xs:element name="row" maxOccurs="unbounded" minOccurs="1">
<xs:element name="type" maxOccurs="1" minOccurs="0">
<xs:extension base="xs:string"></xs:extension>
</xs:element>
<xs:element name="species" maxOccurs="1" minOccurs="0">
<xs:extension base="xs:string"></xs:extension>
</xs:element>
<xs:element name="value" maxOccurs="1" minOccurs="0">
<xs:extension base="xs:string"></xs:extension>
</xs:element>
<xs:element name="unit" maxOccurs="1" minOccurs="0">
<xs:extension base="xs:string"></xs:extension>
</xs:element>
<xs:element name="exposuretime" maxOccurs=1 minOccurs=0>
<xs:extension base="xs:string"></xs:extension>
</xs:element>
<xs:element name="exposuretimeunit" maxOccurs=1minOccurs=0>
<xs:extension base="xs:string"></xs:extension>
</xs:element>
<xs:element name="method" maxOccurs="1" minOccurs="0">
<xs:extension base="xs:string"></xs:extension>
</xs:element>
<xs:element name="remark" maxOccurs="1" minOccurs="0">
<xs:extension base="xs:string"></xs:extension>
</xs:element>
<xs:element name="source" maxOccurs="1" minOccurs="0">
<xs:extension base="xs:string"></xs:extension>
</xs:element>
</xs:element>
</xs:element>
</xs:schema>
The above simplified value from ListNames_Control.XML_XSD reveals the standard XML
Schema for ONLY this specific LOLI List and is used as a guide for what to expect when
accessing the ListData.XML field where ListData.ListID=571.
The information herein contained is proprietary and confidential.
8
The LOLI Database
TableName.FieldName
value
-----------------------------------------------------------------------------------------------ListData.ListID:
571
ListData.Cas:
50-00-0
ListData.Data:
Dermal LD50 Rabbit 270 mg/kg (Source: IUCLID); Inhalation LC50 Rat
0.578 mg/L 4 h (Source: NLM_CIP); Oral LD50 Rat 500 mg/kg (Source:
IUCLID)
ListData.XML:
<root>
<row>
<type id="003_0009850">Dermal LD50</type>
<species id="003_0009851">Rabbit</species>
<value>270</value>
<unit>mg/kg</unit>
<source>IUCLID</source>
</row>
<row>
<type id="003_0009852">Inhalation LC50</type>
<species id="003_0009848">Rat</species>
<value>0.578</value>
<unit>mg/L</unit>
<exposuretime>4</exposuretime>
<exposuretimeunit>h</exposuretimeunit>
<source>NLM_CIP</source>
</row>
<row>
<type id="003_0009847">Oral LD50</type>
<species id="003_0009848">Rat</species>
<value>500</value>
<unit>mg/kg</unit>
<source>IUCLID</source>
</row>
</root>
The above XML data for Formaldehyde reveals the XML data structured based on the XML
Schema for ListData.ListID=571. Notice that the ListData.Data field contains the aggregate
(delimited text) data. This is illustrative of how the XML data lends itself much better to
export, manipulation, and/or import into other systems than the aggregate. The aggregate,
on the other hand, is useful for presentation for printing on documentation and offering this
choice for the end user is the reason both formats are provided.
The information herein contained is proprietary and confidential.
9
The LOLI Database
EXAMPLE 2: Norway - Occupational Exposure Limits - STELs
TableName.FieldName
value
-----------------------------------------------------------------------------------------------ListNames.ListID:
2374
ListNames.ListName:
Norway - Occupational Exposure Limits - STELs
ListNames_Control.ListID:
2374
ListNames_Control.XML_XSD: (simplified for this document)
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="root">
<xs:element name="row" maxOccurs="unbounded" minOccurs="1">
<xs:element name="value" maxOccurs="1" minOccurs="0">
<xs:extension base="xs:string"/>
</xs:element>
<xs:element name="unit" maxOccurs="1" minOccurs="0">
<xs:extension base="xs:string"/>
</xs:element>
<xs:element name="type" maxOccurs="1" minOccurs="0">
<xs:extension base="xs:string"/>
</xs:element>
<xs:element name="remark" maxOccurs="1" minOccurs="0">
<xs:extension base="xs:string"/>
</xs:element>
<xs:element name="expressedas" maxOccurs="1" minOccurs="0">
<xs:extension base="xs:string"/>
</xs:element>
<xs:element name="formofexposure" maxOccurs=1 minOccurs=0>
<xs:extension base="xs:string"/>
</xs:element>
<xs:element name="listedunder" maxOccurs="1" minOccurs="0">
<xs:extension base="xs:string"/>
</xs:element>
</xs:element>
</xs:element>
</xs:schema>
This example is accessing the same database tables and fields to get this list's data,
however, the XML Schema above reveals that this list's structure is different than the first
example. This difference illustrates the power of using an XML Schema to dictate list content
structure instead of physical tables.
The information herein contained is proprietary and confidential.
10
The LOLI Database
TableName.FieldName
value
-----------------------------------------------------------------------------------------------ListData.ListID:
2374
ListData.Cas:
50-00-0
ListData.Data:
1.5 ppm STEL; 1.8 mg/m3 STEL
ListData.XML:
<root>
<row>
<value>1.5</value>
<unit id="003_0000370">ppm</unit>
<type id="003_0001412">STEL</type>
</row>
<row>
<value>1.8</value>
<unit id="003_0000377">mg/m3</unit>
<type id="003_0001412">STEL</type>
</row>
</root>
The ListData.XML value stores the data in an XML structure, defined by the list's XML
Schema, which allows users to access each data element's value individually.
NOTE: Both of the above examples contain carriage returns, tabs, and color/text
formatting. This has been added for easy readability within this document, the actual data
for both the XML Schema and XML data do not contain carriage returns or tabs.
Additionally, sections of the XML Schemas were removed in an effort to make this document
easier to read.
The information herein contained is proprietary and confidential.
11
The LOLI Database
Chemical Name Translations
The LOLI Database includes Chemical Name Translations at no additional cost. When our regulatory
experts compile the information in LOLI, they also capture the chemical name as it appears in the
original regulatory source. Chemical Name Translations taken from the original source materials are
available in 33 languages. This allows you to search the database using these chemical names, in
addition to the other available search methods. These names are also able to be integrated with your
software to reduce translation costs and improve accuracy.
Regulatory Data Translations
Translations of textual information found in the LOLI regulatory database has been captured from the
various non-English sources of LOLI data. LOLI Database contains two tables:


ListNames_Translation
ListData_Translation
Together these tables allow you to view the List Name, Chemical Name and aggregate LOLI List Data in
English and the source language of that list, when the source language of the list is not English.
The information herein contained is proprietary and confidential.
12
The LOLI Database
LOLI Datafeed
The LOLI Datafeed is the most basic version of the LOLI Database to be used in integration with other
software programs, including ChemADVISOR’s LOLI Desktop. For a list of our partner companies who
have developed integrations with the LOLI Datafeed, please visit:
http://www.chemadvisor.com/partners
LOLI Datafeed System Requirements

Microsoft SQL Server 2005 or higher
The information herein contained is proprietary and confidential.
13
The LOLI Database
LOLI Desktop
LOLI Desktop is ChemADVISOR’s tool to efficiently and effectively research and utilize global regulatory
environmental, health, safety, and transportation information available in the LOLI Regulatory Database.
LOLI Desktop Features
LOLI Desktop allows you to:
- Search the database using:
- CAS number
- Inventory identification number
- Chemical names (including foreign language synonyms)
- Partial chemical names
- Chemical formula or formula elements
Create customized lists to capture proprietary and company specific information:
- Private lists can be created for use by individual users. They are available only at a
particular installation of the software.
- Public lists can be created for use throughout an entire organization. They are
available to the entire organization covered by a LOLI Desktop License.
- Conduct integrated LOLI queries
- View expanded generic link information
- Simultaneously view the list header and the list content
- Generate change reports by CAS number or by list
- Filter search result and list data
- Easily identify deleted CAS numbers in FindCAS results
- Control access for multiple users
Change Reporting
LOLI Desktop can produce a document detailing every change made in a list or group of lists during a
specified time frame. Alternatively, you can determine for a specific chemical (CAS number) or group of
chemicals any changes that occurred during a specified time period. The tool provides a tabbed result
view based on the type of change:




Additions
Chemical Name Changes
Data Changes
Deletions.
The results can be exported and saved in one of four formats (comma-separated values, HTML, Rich text
or text) or printed.
The information herein contained is proprietary and confidential.
14
The LOLI Database
LOLI Desktop Versions
LOLI Desktop – Enterprise edition: Will use a client/server setup. This configuration allows multiple
users to access a centralized copy of the database and share public lists.
LOLI Desktop – Personal edition: Will run on a single workstation. This configuration accesses a local
copy of the database.
LOLI Desktop: Minimum System Requirements
LOLI Desktop, Enterprise Edition (Network Setup)
 Server
o Processor
 Minimum: 1 Virtual Core
o RAM
 Minimum: 1 GB
 Recommended: 2 GB or more
o Disk Space
 ~10 GB for Database files
o Operating System
 Minimum: Microsoft Windows Server 2003 SP1
 Recommended: Microsoft Windows Server 2008 or later
o Optical Drive
 DVD Drive
o Additional Software (not included)
 One of the following editions of Microsoft SQL Server:
 2005, 2008, 2008 R2, or 2012 Standard Edition
 2005, 2008, 2008 R2, or 2012 Enterprise Edition
 2005, 2008, 2008 R2, or 2012 Datacenter Edition
 Recommended: Verify Microsoft SQL Server minimum system
requirements
 Client
o Processor
 Minimum: 750 MHz or higher
 Recommended: 1 GHz or higher
o RAM
 Minimum: 512 MB
 Recommended: 1 GB or more
o Operating System (with Language Packs installed for non-Latin data viewing)
 Minimum: Microsoft Windows XP Professional with SP3
o Optical Drive for physical media delivery method
 DVD Drive
o Disk Space
 200 MB
o Additional Software (included on CD)
 Microsoft .NET Framework 4.0
 Microsoft Windows Installer 4.5
The information herein contained is proprietary and confidential.
15
The LOLI Database
LOLI Desktop, Personal Edition (Standalone Setup)
 Workstation
o Processor
 Minimum: Single Core 1.4 GHz or higher
 Recommended: Dual Core 2.0 GHz or higher
o RAM
 Minimum: 1 GB
 Recommended: 2 GB or more
o Operating System (with Language Packs installed for non-Latin data viewing)
 Minimum: Microsoft Windows XP Professional with SP3
o Optical Drive for physical media delivery method
 DVD Drive
o Disk Space
 ~10 GB
o Additional Software (included on CD)
 Microsoft .NET Framework 4.0
 Microsoft SQL Server 2008 R2 Express Edition
 Microsoft Windows Installer 4.5
The information herein contained is proprietary and confidential.
16
The LOLI Database
LOLI in the Cloud
ChemADVISOR can deliver LOLI Desktop in a SaaS environment. You can now access all of the LOLI
regulatory data required for your global chemical compliance needs through the cloud. ChemADVISOR
will provide you with a user name and password for you to log onto your hosted location. We will take
care of maintaining the software and providing your quarterly updates through cloud computing.
By taking advantage of ChemADVISOR’s hosted solution:





You won’t have to get your IT department involved every quarter to access the most
recent information
No more media delivery or electronic download required
You will get access to the updates as soon as they are released every week
ChemADVISOR’s experts will make sure your software is properly configured
You can free up storage resources, since you won’t need to keep the LOLI Database on
your system
Dedicated servers can be made available.
Minimum System Requirements
The connecting client requires one of the following operating systems and installed components as a
minimum requirement.



Windows 7
o No additional components necessary
Windows Vista
o Service Pack 1
o Remote Desktop Connection 7.0 client
 http://support.microsoft.com/kb/969084
Windows XP
o Service Pack 3
o Remote Desktop Connection 7.0 client
 http://support.microsoft.com/kb/969084
o Enable Credential Security Support Provider
 http://support.microsoft.com/kb/951608
The information herein contained is proprietary and confidential.
17
The LOLI Database
The LOLI-SAP EHS&T Compliance Suite
ChemADVISOR has developed a collection of products designed to support companies who work in the
SAP EH&S Module. Together, these products are referred to as the LOLI-SAP EHS&T Compliance Suite.
The Suite is composed of the following pieces:





Product Safety Dataset
Dangerous Goods Dataset
Physical-Chemical/Toxicity/Ecotoxicity Dataset
SAP EHS Expert Rules
GHS Expert Rules
For more information on the LOLI-SAP EHS&T Compliance Suite, contact ChemADVISOR.
ChemADVISOR Online
ChemADVISOR Online incorporates the LOLI Database and two of ChemADVISOR’s other products: the
transportation advisor database and the OHS Pure Substance Database. This application allows for payper-use or pre-paid searching of these databases.
For more information on ChemADVISOR Online, contact ChemADVISOR.
The information herein contained is proprietary and confidential.
18
The LOLI Database
Data Delivery Options
LOLI data updates are sent via FTP download or physical media (DVD), if desired, every quarter. Updates
are sent during the first week of January, April, July and October. The update will contain a “delta” file
of additions, changes and deletions. CDs will be shipped by carrier with tracking information.
The ChemADVISOR’s web based products are updated every week. These include LOLI in the Cloud and
ChemADVISOR Online.
The information herein contained is proprietary and confidential.
19