Document ID: EPA-HQ-OEI-2005-0010-0003
Agency: epa
Document Type: Supporting & Related Material
Title: 
Posted Date: 2005-08-26T04:00Z

INSTITUTIONAL
CONTROL
DATA
STANDARD
Standard
No.:
1­
XXX
Version
1
 
FINAL
DRAFT
July
26,
2005
This
data
standard
is
produced
by
the
Environmental
Data
Standards
Council
(
EDSC)

The
Environmental
Data
Standards
Council
(
EDSC)
is
a
partnership
among
EPA,
States
and
Tribal
partners
to
develop
and
agree
upon
data
standards
for
environmental
information
collection
and
exchange.
More
information
about
the
EDSC
is
available
at
http://
www.
envdatastandards.
net.
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
2
Foreword
The
Environmental
Data
Standards
Council
(
EDSC)
identifies,
prioritizes
and
pursues
the
creation
of
data
standards
for
those
areas
where
information
exchange
standards
will
provide
the
most
value
in
achieving
environmental
results.
The
Council
involves
Tribes
and
Tribal
Nations,
state
and
federal
agencies
in
the
development
of
the
standards
and
then
provides
the
draft
materials
for
general
review.
Business
groups,
non­
governmental
organizations,
and
other
interested
parties
may
then
provide
input
and
comment
for
Council
consideration
and
standard
finalization.
Draft
and
final
standards
are
available
at
http://
www.
envdatastandards.
net.

1.0
INTRODUCTION
Environmental
Protection
Agency
defines
institutional
controls
(
IC)
as
non­
engineering
measures,
such
as
administrative
and/
or
legal
controls,
that
help
to
minimize
the
potential
for
human
exposure
to
contamination
and/
or
to
protect
the
integrity
of
a
remedy
by
limiting
land
or
resource
use.
Institutional
controls
are
used
when
contamination
is
first
discovered,
when
remedies
are
ongoing,
and
when
residual
contamination
remains
onsite
at
a
level
that
does
not
allow
for
unrestricted
use
and
unlimited
exposure
after
cleanup.

This
document
is
organized
such
that
the
four
core
components
of
an
IC
(
IC
Instrument,
IC
Objective,
Location,
and
Engineering
Control)
and
all
auxiliary
components
that
accompany
this
information
(
IC
Affiliation,
IC
Resource,
and
IC
Event)
are
regarded
as
modules.
Within
these
modules
are
the
data
groupings
and
data
elements.

The
concept
of
most
importance
to
the
IC
Data
Standard
is
that
there
is
no
single
central
entity
that
defines
an
IC.
A
complete
IC
must
contain
an
IC
instrument,
an
IC
objective,
and
a
location
at
a
minimum.
(
Please
note
that
the
engineering
control,
though
an
integral
aspect
of
an
IC
when
applicable,
is
not
required
to
define
an
IC.)

I
t
is
important
to
note
that
IC
objectives
and
use
restrictions
are
not
the
same.
Although
an
IC
objective
may
be
met
by
the
use
restrictions
of
an
IC
instrument,
the
IC
objective
is
not
a
property
of
the
IC
instrument
and
must
be
captured
separately.
For
example,
the
objective
at
a
location
called
IC
Site
could
be
to
protect
the
integrity
of
a
landfill
cap.
The
use
restriction
(
generally
found
within
the
language
of
the
IC
instrument)
could
be
to
prohibit
entry
into
IC
Site.
This
use
restriction
prevents
the
disturbance
of
the
landfill
cap
by
restricting
access
to
it,
thereby
meeting
the
objective
at
IC
Site.
The
IC
objective
describes
the
desired
outcome
of
implementing
an
IC
at
a
location,
while
the
use
restriction
describes
what
is
actually
being
done
to
reach
that
outcome
once
the
IC
is
implemented.
To
summarize,
an
IC
instrument
has
use
restrictions
that
serve
to
meet
IC
objectives
at
specific
locations.

I
t
should
be
noted
that
all
permits
transmitted
within
the
scope
of
ICs
are
IC
instruments
or
IC
resources;
however,
not
all
IC
instruments
and
IC
resources
are
permits.
For
this
reason,
information
about
permits
must
be
captured
using
the
IC
instrument
or
IC
resource
data
elements
of
this
data
standard.
Although
these
data
elements
are
being
transmitted
via
XML
tags
that
are
not
part
of
the
Permitting
Information
[
1­
89246­
2]
Data
Standard,
this
data
standard
mandates
that
they
still
be
bound
by
the
rules
set
forth
by
the
Permitting
Standard.

1.1
Scope
This
EDSC
standard
defines
the
elements
required
for
describing
IC
information.
It
provides
information
about
the
implementation,
monitoring,
enforcement,
and
termination
of
instruments
(
via
the
IC
Event)
as
well
as
the
objectives
they
meet,
associated
locations,
affiliates
and
their
roles/
responsibilities
relevant
to
the
IC,
cleanup
actions
(
via
the
IC
Event),
technologies,
and
the
documentation
related
to
each
of
the
aforementioned
subsets
of
data.
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
3
1.2
References
to
Other
Data
Standards
This
data
standard
relies
on
other
data
standards
to
make
it
complete
and
to
provide
the
necessary
support.
As
such,
users
should
reference
the
normative
standards,
listed
below,
and
consider
them
integral
to
the
IC
Data
Standard.
These
include:

 
Bibliographic
Reference
[
Final
Draft
Version
1.0]
Data
Standard
 
Biological
Taxonomy
[
1­
19937­
2]
Data
Standard
 
Chemical
Identification
[
1­
19938­
1]
Data
Standard
 
Contact
Information
[
1­
88433­
2]
Data
Standard
 
Representation
of
Date
and
Time
[
Final
Draft
Version
2.0]
Data
Standard
 
Facility
Identification
[
1­
19936­
2]
Data
Standard
 
Latitude/
Longitude
[
Final
Draft
Version
2.0]
Data
Standard
 
Permitting
Information
[
Final
Draft
Version
2.0]
Data
Standard
1.3
Terms
and
Definitions
For
the
purposes
of
this
document,
the
following
terms
and
definitions
apply.

Term
Definition
Institutional
Control
A
non­
engineered
instrument,
such
as
an
administrative
and/
or
legal
control,
that
helps
to
minimize
the
potential
for
human
exposure
to
contamination
and/
or
protects
the
integrity
of
a
remedy
by
limiting
land
or
resource
use.

IC
Instrument
An
administrative
measure
and/
or
legal
mechanism
that
establishes
a
specific
set
of
land
or
resource
use
restrictions.

IC
Objective
The
intended
goal
of
an
IC
in
minimizing
the
potential
for
human
exposure
to
remaining
contamination
and/
or
protecting
the
integrity
of
an
engineering
control
by
limiting
land
or
resource
use
in
a
particular
media.

Location
A
physical
location
or
area
defined
by
a
set
of
geographic
area
descriptions,
facility
site
descriptions,
and/
or
set
of
geographic
coordinates.
An
example
of
two
separate
facility
site
descriptions
for
a
single
site
is
the
Superfund
National
Priorities
List
(
NPL)
Assessment
Program
(
SNAP)
Site
ID
and
the
Comprehensive
Environmental
Response,
Compensation,
and
Liability
Information
System
(
CERCLIS)
Site
ID
for
a
single
site.

Engineering
Control
A
physical
technology
implemented
to
minimize
the
potential
for
human
exposure
to
contamination
by
means
of
control
or
remediation.

IC
Affiliation
Any
person
or
organization
associated
with
an
IC
either
directly
or
indirectly.
An
example
of
an
affiliation
with
a
direct
IC
relation
is
a
party
responsible
for
monitoring
the
IC.
An
example
of
an
affiliation
with
an
indirect
IC
relation
is
an
owner
of
a
site
at
which
ICs
are
implemented.

IC
Resource
Any
document
or
source
of
information
associated
with
an
IC
either
directly
or
indirectly.
An
example
of
a
resource
with
a
direct
IC
relation
is
a
document
mandating
an
IC
enforcement
action.
An
example
of
a
resource
with
an
indirect
IC
relation
is
a
map
of
a
site
at
which
ICs
are
implemented.
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
4
Term
Definition
IC
Event
Any
occurrence
or
action,
taking
place
on
a
specific
date
or
over
a
period
of
time,
for
which
data
may
be
collected,
processed,
distributed,
or
used
for
the
purpose
of
ICs.

1.4
Implementation
Users
are
encouraged
to
use
the
XML
registry
housed
on
the
Exchange
Network
Web
site
to
download
schema
components
for
the
construction
of
XML
schema
flows
(
http://
www.
exchangenetwork.
net).

1.5
Document
Structure
The
structure
of
this
document
is
briefly
described
below:
a.
Section
2.0
Institutional
Control
Diagram,
illustrates
the
principal
data
groupings
contained
within
this
standard.
b.
Section
3.0
Institutional
Control
Data
Standard
Table,
provides
information
on
the
high
level,
intermediate
and
elemental
Institutional
Control
data
groupings.
Where
applicable,
for
each
level
of
this
data
standard,
a
definition,
XML
tag,
note(
s),
example
list
of
values
and
format
are
provided.
The
format
column
may
list
the
required
number
of
characters
for
the
associated
data
element,
where
"
A"
specifies
alphanumeric,
"
N"
designates
numeric,
and
date
and
time
that
reference
the
Representation
of
Date
and
Time
Data
Standard.
c.
Data
Standard
Numbering:
For
purposes
of
clarity
and
to
enhance
understanding
of
data
standard
hierarchy
and
relationships,
each
data
group
is
numerically
classified
from
the
primary
to
the
elemental
level.

d.
Code
and
Identifier
metadata:
Based
on
the
business
need,
additional
metadata
may
be
required
to
sufficiently
describe
an
identifier
or
a
code.
A
note
regarding
this
additional
metadata
is
included
in
the
notes
column
for
identifier
and
code
elements.
Additional
metadata
for
identifiers
may
include:

 
Identifier
Context,
which
identifies
the
source
or
data
system
that
created
or
defined
the
identifier
Additional
metadata
for
codes
may
include:

 
Code
List
Identifier,
which
is
a
standardized
reference
to
the
context
or
source
of
the
set
of
codes
 
Code
List
Version
Identifier,
which
identifies
the
particular
version
of
the
set
of
codes
 
Code
List
Version
Agency
Identifier,
which
identifies
the
agency
responsible
for
maintaining
the
set
of
codes
 
Code
List
Name,
which
describes
the
corresponding
name
for
which
the
code
represents
e.
Appendix
A,
Institutional
Control
Data
Structure
Diagram
illustrates
the
hierarchical
classification
of
the
Institutional
Control
data
standard.
This
diagram
enables
business
and
technical
users
of
his
standard
to
quickly
understand
its
general
content
and
complexity.

f.
Appendix
B,
Example
Lists
of
Values,
provides
the
long
lists
of
example
values
for
data
elements
that
would
hinder
readability
of
the
data
standard.
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
5
2.0
INSTITUTIONAL
CONTROL
DIAGRAM
This
diagram
specifies
the
major
data
groups
that
may
be
used
to
identify
the
characteristics
and/
or
catalog
IC
information.

Institutional
Control
Data
Standard
4.0
Engineering
Control
3.0
Location
2.0
IC
Objective
1.0
IC
Instrument
7.0
IC
Event
5.0
IC
Affiliation
6.0
IC
Resource
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
6
3.0
INSTITUTIONAL
CONTROL
DATA
STANDARD
TABLE
1.0
IC
Instrument
Definition:
Basic
identification
information
for
an
IC
instrument
including
its
use
restrictions
and
lifespan.

Relationships:
 
Each
IC
instrument
must
meet,
or
intend
to
meet,
one
or
more
IC
objective(
s).

 
Each
IC
instrument
must
cover,
or
intend
to
cover,
one
or
more
location(
s).

 
Each
IC
instrument
may
protect
zero,
one,
or
more
engineering
controls.

 
Each
IC
instrument
may
have
zero,
one,
or
more
affiliations.

 
Each
IC
instrument
may
be
associated
with
zero,
one,
or
more
resources.

 
Each
IC
instrument
must
be
associated
with
one
or
more
event(
s).

Notes:
None.

XML
Tag:
ICInstrument
Name
Definition
Notes
Format
XML
Tag
1.1
IC
Instrument
Identifier
A
unique
identifier
assigned
to
an
administrative
measure
and/
or
legal
mechanism.
This
data
element
may
be
used
to
provide
a
permit
number/
identifier.
Refer
to
the
Permit
Number/
Identifier
data
element
in
the
Permitting
Information
[
1­
89246­
2]
Data
Standard
for
definition
and
format
information.

Note:
Based
on
the
business
need,

additional
metadata
may
be
required
to
sufficiently
describe
an
identifier.
This
additional
metadata
is
described
in
the
Introduction
section
1.5.
d.
A
ICInstrumentId
entifier
1.2
IC
Instrument
Name
The
name
assigned
to
an
administrative
measure
and/
or
legal
mechanism.
This
data
element
may
be
used
to
provide
a
permit
name.
Refer
to
the
Permit
Name
data
element
in
the
Permitting
Information
[
1­

89246­
2]
Data
Standard
for
definition
and
format
information.
A
ICInstrumentN
ame
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
7
Name
Definition
Notes
Format
XML
Tag
1.3
IC
Instrument
Category
The
major
IC
classification
to
which
an
administrative
measure
and/
or
legal
mechanism
belongs.
This
data
element
serves
to
qualify
the
"
IC
Instrument
Type,"
data
element
1.4.

List
of
Example
Values:

 
Government
 
Propriety
 
Enforcement
 
Informational
A
ICInstrumentC
ategoryName
1.4
IC
Instrument
Type
The
type
of
administrative
measure
and/
or
legal
mechanism.
Note
1:
This
data
element
may
be
used
to
provide
a
permit
type.
Refer
to
the
Permit
Type
Code
data
element
in
the
Permitting
Information
[
1­
89246­
2]
Data
Standard
for
definition
and
format
information.

Note
2:
The
types
of
IC
Instruments
are
dependent
on
the
categories
involved.

Example
lists
of
values
are
provided
in
Appendix
B
for
Government,
Proprietary,

Enforcement,
and
Informational
categories.
A
ICInstrumentT
ypeText
1.5
IC
Instrument
Lifespan
Indicator
The
lifespan
of
the
IC
instrument
indicated
as
permanent
or
temporary.
List
of
Example
Values:

 
Permanent
 
Temporary
A
ICInstrumentLi
fespanIndicato
r
1.6
IC
Instrument
Lifespan
Conditions
Text
A
text
description
of
the
conditions
upon
which
the
lifespan
of
the
IC
instrument
is
contingent.
Example:

"
Protection
shall
continue
until
all
remedial
actions
have
been
completed."
A
ICInstrumentLi
fespanConditio
nsText
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
8
1.7
IC
Instrument
Use
Restriction
Definition:
Elements
or
attributes
that
describe
a
use
restriction.

Relationship:
None.

Notes:
Each
IC
instrument
must
have
one
or
more
use
restrictions.

XML
Tag:
ICInstrumentUseRestriction
Name
Definition
Notes
Format
XML
Tag
1.7.1
Use
Restriction
Type
The
type
of
land
or
resource
use
specifically
prohibited
or
restricted
by
the
language
of
the
IC
instrument.
List
of
Example
Values:

 
Establish
Ground
Water
Management
Zone
 
Limit
Future
Land
Use
 
Limit
Ground
Water
Use
Activities
 
Prohibit
Any
Activity
That
May
Disturb
the
Integrity
of
An
Engineering
Control
 
Prohibit
Disturbance
of
Soil
 
Prohibit
Excavation
 
Prohibit
Ground
Water
Well
Installation/
Construction
A
UseRestriction
TypeText
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
9
Name
Definition
Notes
Format
XML
Tag
1.7.2
Use
Restriction
Media
Name
The
name
of
the
major
environmental
component
contaminated
and
addressed
by
the
language
of
the
IC
instrument.
List
of
Example
values:

 
Air
 
Debris
 
Ground
Water
 
Leachate
 
Liquid
Waste
 
Residuals
 
Sediment
 
Sludge
 
Soil
 
Solid
Waste
 
Subsurface
Soil
 
Surface
Soil
 
Surface
Water
A
UseRestriction
MediaName
1.7.3
Use
Restriction
Text
The
text
extracted
from
the
IC
instrument
describing
the
land
or
resource
use
specifically
prohibited
or
restricted.
List
of
Example
Values:

 
Land
shall
not
be
used
for
residential
purposes
A
UseRestriction
Text
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
10
2.0
IC
Objective
Definition:
Basic
identification
information
for
an
IC
objective.

Relationships:
 
Each
IC
objective
must
be
met
by,
or
be
planned
to
be
met
by,
one
or
more
IC
instrument(
s).

 
Each
IC
objective
must
be
associated
with
one
or
more
location(
s).

 
Each
IC
objective
may
convey
the
need
to
protect
of
zero,
one,
or
more
engineering
controls.

 
Each
IC
objective
may
be
referenced
by
zero,
one,
or
more
resources.

 
Each
IC
objective
may
be
associated
with
zero,
one,
or
more
event(
s).

Notes:
None.

XML
Tag:
ICObjective
Name
Definition
Notes
Format
XML
Tag
2.1
IC
Objective
Identifier
A
unique
identifier
assigned
to
the
intended
goal
of
an
IC.
Note:
Based
on
the
business
need,

additional
metadata
may
be
required
to
sufficiently
describe
an
identifier.
This
additional
metadata
is
described
in
the
Introduction
section
1.5.
d.
A
ICObjectiveIde
ntifier
2.2
IC
Objective
Name
The
name
assigned
to
the
intended
goal
of
an
IC.
A
ICObjectiveNa
me
2.3
IC
Objective
Media
Name
The
name
of
the
major
environmental
component
contaminated
and
in
which
land
or
resource
use
needs
to
be
limited.
List
of
Example
Values:

 
Air
 
Debris
 
Ground
Water
 
Leachate
 
Liquid
Waste
 
Residuals
 
Sediment
 
Sludge
A
ICObjectiveMe
diaName
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
11
Name
Definition
Notes
Format
XML
Tag
2.3
IC
Objective
Media
Name
(
continued)
 
Soil
 
Solid
Waste
 
Subsurface
Soil
 
Surface
Soil
 
Surface
Water
2.4
IC
Objective
Text
The
text
describing
the
intended
goal
of
an
IC.
The
types
of
IC
Objectives
are
dependent
on
the
media
involved.
Example
lists
of
values
are
provided
in
Appendix
B
for
Air,

Debris,
Ground
Water,
Leachate,
Liquid
Waste,
Residuals,
Sediment,
Sludge,
Soil,

Solid
Waste,
Subsurface
Soil,
Surface
Soil,

and
Surface
Water.
A
ICObjectiveTe
xt
3.0
Location
Definition:
Basic
identification
information
for
a
location
including
the
geographic
area
description,
facility
site
description,
coordinate
information,
and
information
about
remaining
contamination.

Relationships:
 
Each
location
may
be
covered
by
zero,
one,
or
more
IC
instruments.

 
Each
location
may
have
zero,
one,
or
more
IC
objectives.

 
Each
location
may
have
zero,
one,
or
more
engineering
controls
in
place.

 
Each
location
may
have
zero,
one,
or
more
affiliations.

 
Each
location
may
be
associated
with
zero,
one,
or
more
resources.

 
Each
location
may
be
associated
with
zero,
one,
or
more
event(
s).

Notes:
Locations
may
be
related
to
other
locations
as
sub­
locations.
This
allows
a
hierarchy
of
locations
to
be
created
(
e.
g.,
a
county
with
its
own
location
identifier
would
be
a
sub­
location
of
a
state
with
its
own
location
identifier).

XML
Tag:
Location
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
12
Name
Definition
Notes
Format
XML
Tag
3.1
Location
Identifier
A
unique
identifier
for
a
physical
location.
Note:
Based
on
the
business
need,

additional
metadata
may
be
required
to
sufficiently
describe
a
name.
This
additional
metadata
is
described
in
the
Introduction
section1.5.
d.
A
LocationIdentif
ier
3.2
Location
Association
Type
The
text
that
describes
the
relationship
between
the
location
and
an
associated
data
element.
List
of
Example
Values:

 
Coverage
Area
 
Jurisdiction
 
Map
 
Physical
Location
 
Reference
 
Sub­
Location
A
LocationAssoc
iationTypeText
3.3
Geographic
Area
Description
The
address,
description,
and/
or
tribal
information
used
to
describe
a
physical
location.
Note
1:
Refer
to
the
Address
data
grouping
in
the
Contact
Information
[
1­
88433­
2]

Data
Standard.
The
following
items
are
expected
to
define
the
geographic
address
information
needed
for
section
3.3.1:

 
Location
Address
Text
Supplemental
Location
Text
 
Locality
Name
 
Location
Address
State
Code
 
Location
Address
Postal
Code
 
Location
Address
County
Code
 
Location
Description
Text
 
Tribal
Land
Name
 
Tribal
Land
Indicator
Note
2:
A
location
may
have
only
one
geographic
area
description.
A
GeographicAr
eaDescription
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
13
Name
Definition
Notes
Format
XML
Tag
3.3.1
Locality
Type
The
type
of
locality.
This
data
element
serves
to
qualify
the
"
Locality
Name"
in
data
group
3.3:

List
of
Example
Values:

 
Area
of
Contamination
 
Area
Name
 
Borough
 
City
 
Containment
Cell
 
Corrective
Action
Management
Unit
 
Ground
Water
 
Landfill
 
Municipality
 
Operable
Unit
 
Parcel
Number
 
Solid
Waste
Management
Unit
 
Ward
A
LocalityTypeN
ame
3.4
Facility
Site
Description
Basic
identification
information
for
a
facility
site.
Note
1:
Refer
to
the
Facility
Site
Identity
data
grouping
in
the
Facility
Identification
[
1­
19936­
2]
Data
Standard.
The
following
items
are
expected
to
define
the
facility
site
information
needed
for
data
group
3.4:

Facility
Site
Identifier
Facility
Site
Identifier
Context
Facility
Site
Name
Note
2:
A
location
may
have
more
than
one
facility
site
description;
however,
each
of
these
descriptions
must
pertain
to
the
same
facility
site.
A
FacilitySiteDes
criptionText
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
14
Name
Definition
Notes
Format
XML
Tag
3.4.1
Facility
Site
Name
Type
The
type
of
facility
site
name.
This
data
element
serves
to
qualify
the
"
Facility
Site
Name"
in
data
group
3.4.

List
of
Example
Values:

 
CERCLIS
Site
Name
 
CERCLIS
Site
Alias
 
RCRA
Facility
Name
 
SNAP
Site
Name
 
SNAP
Site
Alias
A
FacilitySiteNa
meNameType
3.5
Geographic
Coordinate
Elements
or
attributes
that
describe
a
geographic
coordinate
including
its
metadata.
Note
1:
Refer
to
the
Latitude/
Longitude
[
Final
Draft
Version
2.0]
Data
Standard.

The
following
items
are
expected
to
define
the
geographic
coordinate
information
needed
for
group
3.5:

Latitude
Measure
Longitude
Measure
Horizontal
Accuracy
Measure
Geometric
Type
Code
Geometric
Type
Name
Horizontal
Collection
Method
Code
Horizontal
Collection
Method
Text
Horizontal
Reference
Datum
Code
Horizontal
Reference
Datum
Name
Reference
Point
Code
Reference
Point
Text
Source
Map
Scale
Number
Vertical
Measure
Note
2:
Each
location
may
contain
more
than
one
geographic
coordinate
and
each
instance
of
a
geographic
coordinate
may
be
associated
with
more
than
one
location.
A
GeographicCo
ordinateText
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
15
3.6
Contaminant
Remaining
Definition:
A
hazardous
substance
remaining
in
a
particular
media
of
concern
at
a
specific
location.

Relationship:
None.

Notes:
A
location
may
have
more
than
one
contaminant
remaining.
A
valid
contaminant
consists
of
either
a
Chemical
or
Biological
Taxonomy,
but
not
both.

XML
Tag:
ContaminantRemainingType
Name
Definition
Notes
Format
XML
Tag
3.6.1
Contaminant
Identifier
A
unique
identifier
for
a
chemical
or
biological
taxonomy.
Note:
Based
on
the
business
need,

additional
metadata
may
be
required
to
sufficiently
describe
a
name.
This
additional
metadata
is
described
in
the
Introduction
section
1.5.
d.
A
ContaminantId
entifier
3.6.2
Chemical
Elements
or
attributes
that
describe
a
hazardous
substance.
Refer
to
the
Mandatory
Chemical
Identification
data
grouping
in
the
Chemical
Identification
[
1­
19938­
1]
Data
Standard.

The
following
items
are
expected
to
define
the
chemical
information
needed
for
data
group
3.6.1:

EPA
Chemical
Internal
Tracking
Number
Chemical
Abstracts
Service
Registry
Number
Chemical
Substance
Systematic
Name
EPA
Chemical
Registry
Name
EPA
Chemical
Identifier
Chemical
Substance
Type
Name
Chemical
Substance
Synonym
Chemical
Synonym
Source
Name
A
ICChemicalNa
me
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
16
Name
Definition
Notes
Format
XML
Tag
3.6.3
Biological
Taxonomy
Elements
or
attributes
that
describe,

identify,
name,
and
classify
biological
organisms
based
on
degrees
of
similarity
purportedly
representing
evolutionary
(
phylogenetic)

relatedness.
Refer
to
the
Mandatory
Biological
Taxonomy
data
grouping
in
the
Biological
Taxonomy
[
1­
19937­
2]
Data
Standard.

The
following
items
are
expected
to
define
the
biological
taxonomy
information
needed
for
data
group
3.6.2:

ITIS
Taxonomic
Serial
Number
ICTVdB
Taxon
Identifier
EPA
Biological
Identification
Number
Biological
Systematic
Name
Biological
Systematic
Context
Name
Biological
Vernacular
Name
Biological
Vernacular
Context
Name
Biological
Group
Name
Biological
Group
Context
Name
A
BiologicalTaxo
nomyName
3.6.4
Contaminated
Media
Name
The
name
of
the
major
environmental
component
contaminated
List
of
Example
Values:

 
Air
 
Debris
 
Ground
Water
 
Leachate
 
Liquid
Waste
 
Residuals
 
Sediment
 
Sludge
 
Soil
 
Solid
Waste
 
Subsurface
Soil
 
Surface
Soil
 
Surface
Water
A
Contaminated
MediaName
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
17
4.0
Engineering
Control
Definition:
Basic
identification
information
for
an
engineering
control.

Relationships:
 
Each
engineering
control
may
be
protected
by
zero,
one,
or
more
IC
instruments.

 
Each
engineering
control
may
need
protection
as
conveyed
by
zero,
one,
or
more
IC
objectives.

 
Each
engineering
control
may
be
associated
with
zero,
one,
or
more
location(
s).

 
Each
engineering
control
may
have
zero,
one,
or
more
affiliations.

 
Each
engineering
control
may
be
associated
with
zero,
one,
or
more
resources.

 
Each
engineering
control
may
be
associated
with
zero,
one,
or
more
event(
s).

Notes:
None.

XML
Tag:
EngineeringControl
Name
Definition
Notes
Format
XML
Tag
4.1
Engineering
Control
Identifier
A
unique
identifier
assigned
to
a
process
and/
or
tool
designed
or
used
to
manage
storage,
disposal,

treatment,
and
other
handling
protocols
(
e.
g.,
the
physical
technology
used
to
cleanup
a
site).
Note:
Based
on
the
business
need,

additional
metadata
may
be
required
to
sufficiently
describe
a
name.
This
additional
metadata
is
described
in
the
Introduction
section
1.5.
d.
A
EngineeringCo
ntrolIdentifier
4.2
Engineering
Control
Name
The
name
assigned
to
a
process
and/
or
tool
designed
or
used
to
manage
storage,
disposal,
treatment,

and
other
handling
protocols
(
e.
g.,
the
physical
technology
used
to
cleanup
a
site).
An
example
list
of
values
is
provided
in
Appendix
B.
A
EngineeringCo
ntrolName
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
18
Name
Definition
Notes
Format
XML
Tag
4.3
Engineering
Control
Media
Name
The
name
of
the
major
environmental
component
contaminated
and
associated
with
a
process
and/
or
tool
designed
or
used
to
manage
storage,

disposal,
treatment,
and
other
handling
protocols
(
e.
g.,
the
physical
technology
used
to
cleanup
a
site).
List
of
Example
Values:

 
Air
 
Debris
 
Ground
Water
 
Leachate
 
Liquid
Waste
 
Residuals
 
Sediment
 
Sludge
 
Soil
 
Solid
Waste
 
Subsurface
Soil
 
Surface
Soil
 
Surface
Water
A
EngineeringCo
ntrolMediaNa
me
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
19
5.0
IC
Affiliation
Definition:
Basic
identification
for
an
organization
and/
or
individual
person
and
their
association
with
an
IC
or
IC­
related
entity.

Relationships:
 
Each
affiliation
may
be
associated
with
zero,
one,
or
more
IC
instruments.

 
Each
affiliation
may
be
associated
with
zero,
one,
or
more
locations.

 
Each
affiliation
may
be
associated
with
zero,
one,
or
more
engineering
controls.

 
Each
affiliation
may
be
associated
with
zero,
one,
or
more
resources.

 
Each
affiliation
may
be
associated
with
zero,
one,
or
more
events.

Notes:
Note
1:
A
valid
affiliation
consists
of
either
an
organization
or
an
individual,
but
not
both.

Note
2:
The
physical
location
of
an
organization
or
individual
must
be
captured
through
the
location
module
(
data
group
3.0
of
this
section).

Note
3:
Each
organization
or
individual
may
have
more
than
one
type
of
affiliation
with
an
IC
or
IC­
related
entity
(
e.
g.,
the
owner
of
a
facility
site
may
also
be
the
operator
of
that
facility
site).

XML
Tag:
ICAfffiliation
Name
Definition
Notes
Format
XML
Tag
5.1
Affiliation
Identifier
A
unique
identifier
assigned
to
an
organization
or
individual.
Note:
Based
on
the
business
need,

additional
metadata
may
be
required
to
sufficiently
describe
a
name.
This
additional
metadata
is
described
in
Section
1.5,

Document
Structure.
A
AffiliationIdenti
fier
5.2
Affiliation
Entity/
Person
Identification
of
an
organization
and/
or
individual
person,
their
contact
information,
and
the
nature
of
their
affiliation
with
some
entity.
Note:
Refer
to
Point
of
Contact
data
grouping
in
the
Contact
Information
[
1­

88433­
2]
Data
Standard.

The
following
items
are
expected
to
define
the
affiliation
entity/
person
information
needed
for
data
group
5.2:

Organization
Organization
Identifier
Organization
Identifier
Context
Organization
Formal
Name
A
Affiliation
EntityPerson
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
20
Name
Definition
Notes
Format
XML
Tag
Individual
Individual
Identifier
Individual
Identifier
Context
Individual
Title
Text
Name
Prefix
Text
First
Name
Middle
Name
Last
Name
Name
Suffix
Text
Affiliation
Affiliation
Type
Note
2:
Refer
to
the
Address
data
grouping
in
the
Contact
Information
[
1­
88433­
2]

Data
Standard.

The
following
items
are
expected
to
define
the
affiliation
entity/
person
information
needed
for
data
group
5.2:

Mailing
Address
Text
Supplemental
Address
Text
Mailing
Address
City
Name
Mailing
Address
State
Code
Mailing
Address
Postal
Code
Mailing
Address
Country
Code
Note
3:
Refer
to
the
Communication
data
grouping
in
the
Contact
Information
[
1­

88433­
2]
Data
Standard.

The
following
items
are
expected
to
define
the
affiliation
entity/
person
information
needed
for
data
group
5.2:

Telephonic
Telephone
Number
Telephone
Number
Type
Name
Telephone
Extension
Number
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
21
Name
Definition
Notes
Format
XML
Tag
Electronic
Address
Electronic
Address
Text
Electronic
Address
Type
Name
Note
4:
The
Organization
Formal
Name
and
Affiliation
Type
data
elements
are
required
to
be
provided
with
the
IC
Instrument
if
the
IC
Instrument
is
a
permit
and
with
the
IC
Resource
if
the
IC
Resource
is
a
permit.
This
requirement
is
enforceable
by
the
Permitting
Information
[
1­
89246­
2]

Data
Standard.

5.2.1
Organization
Type
The
text
that
identifies
the
type
of
an
organization.
This
data
element
serves
to
qualify
the
"
Organization
Formal
Name"
from
data
group
5.1.

Example
List
of
Values:

 
City
Government
 
Community
Group
 
County
Government
 
Federal
Government
 
Industry
Group
 
Parish
Government
 
State
Government
 
Town
Government
 
Township/
Village
Government
 
Tribal
Alphan
umeric
OrganizationT
ypeName
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
22
6.0
IC
Resource
Definition:
Basic
identification
information
for
any
document
or
source
of
information
associated
with
an
IC
or
IC­
related
entity
either
directly
or
indirectly.

Relationship:
 
Each
resource
may
serve
as
an
associated
document,
reference,
or
source
of
information
for
zero,
one,
or
more
IC
objectives.

 
Each
resource
may
serve
as
an
associated
document,
reference,
or
source
of
information
for
zero,
one,
or
more
locations.

 
Each
resource
may
serve
as
an
associated
document,
reference,
or
source
of
information
for
zero,
one,
or
more
engineering
control.

 
Each
resource
may
serve
as
an
associated
document,
reference,
or
source
of
information
for
zero,
one,
or
more
affiliations.

 
Each
resource
may
serve
as
an
associated
document,
reference,
or
source
of
information
for
zero,
one,
or
more
other
resources.

 
Each
resource
may
serve
as
an
associated
document,
reference,
or
source
of
information
for
zero,
one,
or
more
events.

Notes:
Note
1:
A
resource
may
have
more
than
one
description,
each
of
which
must
be
qualified
by
a
description
qualifier.

Note
2:
A
resource
may
have
more
than
one
purpose.

XML
Tags:
ICResource
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
23
Name
Definition
Notes
Format
XML
Tag
6.1
Resource
Bibliographic
Descriptors
Identification
of
reference
documents,

information
sources,
images,
maps,

photos,
and
other
objects.
Note
1:
Refer
to
the
Bibliographic
Reference
Descriptors
data
grouping
in
the
Bibliographic
Reference
[
Final
Draft
Version
1.0]
Data
Standard.

The
following
items
are
expected
to
define
the
resource
bibliographic
information
needed
for
section
6.1:

Resource
Identifier
Resource
Title
Resource
Subject
Resource
Description
Resource
Type
Resource
Content
Format
Resource
Language
Resource
Rights
Note
2:
The
Resource
Identifier,
Resource
Title,
and
Resource
Type
data
elements
may
be
used
to
provide
a
permit
number/
identifier,
permit
name,
and
permit
type,
respectively.
Refer
to
the
Permit
Number/
Identifier,
Permit
Name,
and
Permit
Type
Code
data
elements
in
the
Permitting
Information
[
1­
89246­
2]
Data
Standard
for
definition
and
format
information.
A
ResourceBibli
ographicDescri
ptors
6.2
Resource
Description
Qualifier
Text
The
qualifier
that
specifies
the
meaning
of
the
description
associated
with
a
resource.
Note
1:
This
data
element
serves
to
qualify
the
Resource
Description
element
from
data
group
6.1.

Note
2:
A
single
resource
may
have
multiple
descriptions.
A
ResourceDesc
riptionQualifier
Text
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
24
Name
Definition
Notes
Format
XML
Tag
6.3
Resource
Category
The
major
classification
to
which
a
resource
belongs.
This
data
element
serves
to
qualify
the
"
Resource
Type"
element
from
data
group
6.1.
Example
List
of
Values:

 
Local
 
State
 
Tribal
 
USEPA
A
ResourceCate
goryName
6.4
Resource
Presentation
Type
The
means
by
which
a
resource
is
physically
presented.
Example
List
of
Values:

 
Application
 
Cassette
Audio
 
Compact
Disc
(
CD)
Audio
 
Database
 
Document
 
Video
Home
System
(
VHS)
Tape
 
Digital
Versatile
Disc
(
DVD)
Video
A
ResourcePres
entationTypeT
ext
6.5
Resource
Purpose
The
purpose
that
a
resource
serves.
List
of
Example
Values:

 
Mandate
IC
Enforcement
Action
 
Mandate
IC
Monitoring
Action
 
Reference
 
Source
of
Information
A
ResourcePurp
oseText
7.0
IC
Event
Definition:
Basic
identification
information
for
any
occurrence
or
action,
taking
place
on
a
specific
date
or
over
a
period
of
time,
for
which
data
may
be
collected,
processed,
distributed,
or
used
for
the
purpose
of
ICs.

Relationships:
 
Each
event
may
be
associated
with
zero,
one,
or
more
IC
instruments.

 
Each
event
may
be
associated
with
zero,
one,
or
more
IC
objectives.
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
25
 
Each
event
may
be
associated
with
zero,
one,
or
more
locations.

 
Each
event
may
be
associated
with
zero,
one,
or
more
engineering
control.

 
Each
event
may
be
associated
with
zero,
one,
or
more
affiliations.

 
Each
event
may
be
associated
with
zero,
one,
or
more
other
events.

Notes:
Events
may
be
related
to
other
events
as
sub­
events.
This
allows
dependencies
between
events
to
be
modeled
and
allows
single
events
to
be
referenced
by
different
names
with
different
uses
without
compromising
its
original
(
official)

name.
For
example,
there
may
be
an
IC
monitoring
event
with
a
frequency
of
five
years
that
describes
the
overall
monitoring
requirements.
Each
individual
monitoring
event
(
e.
g.,
Five
Year
Review)
that
is
planned
to
occur
every
five
years
is
its
own
separate
event,
but
each
is
related
to
the
IC
monitoring
event
as
a
sub­
event.
As
these
Five
Year
Reviews
occur,
an
actual
date
of
completion
may
be
added.
The
completion
of
these
sub­
events
determines
the
status
of
the
overall
IC
monitoring
event.

XML
Tag:
ICEvent
Name
Definition
Notes
Format
XML
Tag
7.1
Event
Identifier
A
unique
identifier
assigned
to
an
occurrence
or
action
taking
place
on
a
specific
date
or
over
a
period
of
time.
Note:
Based
on
the
business
need,

additional
metadata
may
be
required
to
sufficiently
describe
a
name.
This
additional
metadata
is
described
in
the
Introduction
section
1.5.
d.
A
EventIdentifier
7.2
Event
Name
The
name
given
to
an
occurrence
or
action
taking
place
on
a
specific
date
or
over
a
period
of
time.
The
Event
Name
may
be
used
to
differentiate
between
several
events
having
the
same
value
for
the
"
Event
Type,"
data
element
7.3.
A
EventName
7.3
Event
Type
The
type
of
occurrence
or
action
taking
place
on
a
specific
date
or
over
a
period
of
time.
An
example
list
of
values
is
provided
in
Appendix
B.
A
EventTypeTex
t
7.4
Event
Frequency
Definition:
Elements
or
attributes
that
describe
an
event
frequency.

Relationship:
None.

Notes:
An
event
must
have
only
one
frequency
specified.

XML
Tags:
EventFrequency
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
26
Name
Definition
Notes
Format
XML
Tag
7.4.1
Event
Frequency
Value
The
number
denoting
the
time
interval
between
a
series
of
occurrences
allotted
to
take
place.
Example
List
of
Values:

 
1
 
4
A
EventFrequen
cyValueNumer
ic
7.4.2
Event
Frequency
Unit
Text
The
unit
of
measure
associated
with
a
time
interval
between
a
series
of
occurrences
allotted
to
take
place.
This
data
element
serves
to
qualify
the
"
Frequency
Value,"
data
element
7.4.1.

Example
List
of
Values:

 
Hours
 
Days
 
Weeks
 
Months
 
Years
A
EventFrequen
cyUnitText
7.5
Event
Date
and
Time
Definition:
Elements
or
attributes
that
define
an
event
date.

Relationship:
None.

Notes:
An
event
may
have
more
than
one
date/
time.

XML
Tags:
EventDateTime
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
27
Name
Definition
Notes
Format
XML
Tag
7.5.1
Event
Date
The
date
that
the
event
takes
place.
Refer
to
the
Representation
of
Date
and
Time
[
Draft]
Data
Standard.
YYYY
MMDD
EventDate
7.5.2
Event
Date
Qualifier
Text
The
qualifier
that
specifies
the
meaning
of
the
date
that
the
event
takes
place.
This
data
element
serves
to
qualify
the
"
Event
Date,"
data
element
7.5.1.

Example
List
of
Values:

 
Actual
Completion
Date
 
Actual
Date
 
Actual
Start
Date
 
Planned
Completion
Date
 
Planned
Date
 
Planned
Start
Date
A
EventDateQua
lifierText
7.5.3
Event
Time
The
time
that
the
event
takes
place.
Refer
to
the
Representation
of
Date
and
Time
[
Draft]
Data
Standard.
hh:
mm:

ss
±
hh:

mm
EventTime
7.5.4
Event
Time
Qualifier
Text
The
qualifier
that
specifies
the
meaning
of
the
time
that
the
event
takes
place.
This
data
element
serves
to
qualify
the
"
Event
Time,"
data
element
7.5.3.

Example
List
of
Values:

 
Actual
Completion
Time
 
Actual
Time
 
Actual
Start
Time
 
Planned
Completion
Time
 
Planned
Time
 
Planned
Start
Time
A
EventTimeQua
lifierText
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
28
7.6
Event
Description
Definition:
Elements
or
attributes
that
describe
the
details
of
the
event.

Relationship:
None.

Notes:
An
event
may
have
more
than
one
description.

XML
Tags:
EvenDescription
Name
Definition
Notes
Format
XML
Tag
7.6.1
Event
Description
Text
Any
description
associated
with
the
event.
Alphan
umeric
EventDescripti
onText
7.6.2
Event
Description
Qualifier
Text
The
qualifier
that
specifies
the
meaning
of
the
description
provided
about
the
event.
This
data
element
serves
to
qualify
the
"
Event
Description
Text"
element
from
section
7.6.1.

Example
List
of
Values:

 
Purpose
 
Objectives
 
Procedures/
Methodologies
 
Findings
 
Results/
Conclusions
Alphan
umeric
EventDescripti
onQualifierTex
t
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
29
Appendix
A
Institutional
Control
Data
Structure
Diagram
Institutional
Control
Data
Standard
2.0
IC
Objective
2.1
IC
Objective
Identifier
2.2
IC
Objective
Name
2.3
IC
Objective
Media
Name
2.4
IC
Objective
Text
1.0
IC
Instrument
1.1
IC
Instrument
Identifier
1.2
IC
Instrument
Name
1.3
IC
Instrument
Category
1.4
IC
Instrument
Type
1.5
IC
Instrument
Lifespan
Indicator
1.6
IC
Instrument
Conditions
Text
1.7
IC
Instrument
Use
Restriction
1.7.1
Use
Restriction
Type
1.7.2
Use
Restriction
Media
Name
1.7.3
Use
Restriction
Media
Text
4.0
Engineering
Control
4.1
Engineering
Control
Identifier
4.2
Engineering
Control
Name
4.3
Engineering
Control
Media
Name
5.0
IC
Affiliation
5.1
Affiliation
Identifier
5.2
Affiliation
Entity/
Person
5.2.1
Organization
Type
3.0
Location
3.1
Location
Identifier
3.2
Location
Association
Type
3.3
Geographic
Area
Description
3.3.1
Locality
Type
3.4
Facility
Site
Description
3.4.1
Facility
Site
Name
type
3.5
Contaminant
Remaining
3.6.1
Contaminant
Identifier
3.6.2
Chemical
3.6.3
Biological
Taxonomy
3.6.4
Contaminated
Media
Name
6.0
IC
Resource
6.1
Resource
Bibliographic
Descriptors
6.2
Resource
Description
Qualifier
Text
6.3
Resource
Category
6.4
Resource
Presentation
Type
6.5
Resource
Purpose
7.0
IC
Event
7.1
Event
Identifier
7.2
Event
Name
7.3
Event
Type
7.4
Event
Frequency
7.4.1
Event
Frequency
Value
7.4.2
Event
Frequency
Unit
Text
7.5
Event
Date/
Time
7.5.1
Event
Date
7.5.2
Event
Date
Qualifier
Text
7.5.3
Event
Time
7.5.4
Event
Time
Qualifier
Text
7.6
Event
Description
7.6.1
Event
Description
Text
7.6.2
Event
Description
Qualifier
Text
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
30
Appendix
B
 
Lists
of
Example
Values
Name/
XML
Tag
Definition
Notes
1.4
IC
Instrument
Type
XML
Tag:
ICInstrumentTypeText
The
type
of
administrative
measure
and/
or
legal
mechanism
Note
1:
This
data
element
may
be
used
to
provide
a
permit
type.
Refer
to
the
Permit
Type
Code
data
element
in
the
Permitting
Information
[
1­
89246­
2]
Data
Standard
for
definition
and
format
information.

Example
List
of
Values:
IC
Instrument
Type
may
be
one
of
the
following
if
the
IC
Instrument
Category
is
Government:
Base
Use
Plan
Grant
of
Environmental
Resource
(
GER)
Ground
Water
Protection
Zone
Ground
Water
Use
Regulation
Local
Ordinance
Local
Permit
­
Alteration
Local
Permit
­
Building
Local
Permit
­
Demolition
Local
Permit
­
Development
Local
Permit
­
Excavation
Local
Permit
­
Ground
Water
Management
Local
Permit
­
Unspecified
Type
Local
Permit
­
Well
Drilling
Overlay
Zoning
State
Legislation
Subdivision
Regulation
Well
Drilling
Regulation
Zoning
Amendment
Zoning
Ordinance
Zoning
Variance
IC
Instrument
Type
may
be
one
of
the
following
if
the
IC
Instrument
Category
is
Proprietary:
Deed
Restriction
of
Unspecified
Type
Easement
­
Affirmative
Easement
­
Appurtenant
Easement
­
Conservation
Easement
­
In
Gross
Easement
­
Negative
Easement
­
Unspecified
Type
Equitable
Servitude
Restrictive
Covenant
Reservation
of
Interest
IC
Instrument
Type
may
be
one
of
the
following
if
the
IC
Instrument
Category
is
Enforcement:
Administrative
Order
on
Consent
(
AOC)
Consent
Decree
(
CD)
Contract
Federal
Interagency
Agreement
RCRA
3008(
h)
Compliance
Order
RCRA
Closure
Permit
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
31
Name/
XML
Tag
Definition
Notes
RCRA
Compliance
Schedule
RCRA
Corrective
Action
Order
RCRA
Exposure
Information
Report
RCRA
Inspection
Report
RCRA
Operating
Permit
­
Part
A
RCRA
Operating
Permit
­
Part
B
RCRA
Permit
Modification
­
Part
A
RCRA
Permit
Modification
­
Part
B
RCRA
Post­
Closure
Permit
Report
of
Spill
or
Release
Unilateral
Administrative
Order
(
UAO)

IC
Instrument
Type
may
be
one
of
the
following
if
the
IC
Instrument
Category
is
Informational:
Advisory
­
Agricultural
Advisory
­
Drinking
Water
Advisory
­
Fishing
Advisory
­
Food
Advisory
­
Health
Advisory
­
Swimming
Advisory
­
Unspecified
Type
Announcement
­
Radio
Announcement
­
Television
Announcement
­
Unspecified
Type
Listing
­
Local
Hazardous
Waste
Registry
Listing
­
Military
Hazardous
Waste
Registry
Listing
­
State
Hazardous
Waste
Registry
Listing
­
Unspecified
Type
Notice
­
Deed
Notice
Notice
­
Notice
to
State
Regulators
Before
Changes
in
Land
Ownership
Notice
­
Notice
to
State
Regulators
Before
Changes
in
Land
Use
Notice
­
Unspecified
Type
One
Call
System
­
Local
One
Call
System
­
State
One
Call
System
­
Unspecified
Type
Public
Education
­
Brochure
Public
Education
­
Direct
Mailing
Public
Education
­
Door
Hanger
Public
Education
­
Fact
Sheet
Public
Education
­
Unspecified
Type
Publication
­
Federal
Register
Publication
­
Internet
Announcement
Publication
­
Newspaper/
Press
Release
Publication
­
State
Register
Publication
­
Unspecified
Type
2.4
IC
Objective
Text
XML
Tag:
ICObjectiveText
The
text
describing
the
intended
goal
of
an
IC
Example
List
of
Values:
IC
Objective
Text
may
be
one
of
the
following
if
the
IC
Objective
Media
is
Air:
Prohibit
Inhalation
Exposure
Protect
Integrity
of
an
Engineered
Remedy
Provide
Information
to
Educate
Provide
Information
to
Modify
Behavior
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
32
Name/
XML
Tag
Definition
Notes
IC
Objective
Text
may
be
one
of
the
following
if
the
IC
Objective
Media
is
Debris:
Prohibit
Dermal
Contact
Prohibit
Ingestion
Exposure
Prohibit
Inhalation
Exposure
Prohibit
Recreational
Exposure
Scenario
Prohibit
Residential
Exposure
Scenario
Prohibit
School/
Daycare
Exposure
Scenario
Prohibit
Utility
Worker/
Excavation
Exposure
Scenario
Protect
Integrity
of
an
Engineered
Remedy
Provide
Information
to
Educate
Provide
Information
to
Modify
Behavior
IC
Objective
Text
may
be
one
of
the
following
if
the
IC
Objective
Media
is
Ground
Water:
Prohibit
Dermal
Contact
Prohibit
Drinking
Prohibit
Ingestion
Exposure
Prohibit
Inhalation
Exposure
Prohibit
Other
Use
(
Industrial,
Food
Preparation,
Gardening,
Agricultural,
etc.)
Prohibit
Pumping
(
Plume
Movement)
Protect
Integrity
of
an
Engineered
Remedy
Provide
Information
to
Educate
Provide
Information
to
Modify
Behavior
IC
Objective
Text
may
be
one
of
the
following
if
the
IC
Objective
Media
is
Leachate:
Prohibit
Dermal
Contact
Prohibit
Ingestion
Exposure
Prohibit
Inhalation
Exposure
Protect
Integrity
of
an
Engineered
Remedy
Provide
Information
to
Educate
Provide
Information
to
Modify
Behavior
IC
Objective
Text
may
be
one
of
the
following
if
the
IC
Objective
Media
is
Liquid
Waste:
Prohibit
Dermal
Contact
Prohibit
Ingestion
Exposure
Prohibit
Inhalation
Exposure
Prohibit
Recreational
Exposure
Scenario
Prohibit
Residential
Exposure
Scenario
Prohibit
School/
Daycare
Exposure
Scenario
Prohibit
Utility
Worker/
Excavation
Exposure
Scenario
Protect
Integrity
of
an
Engineered
Remedy
Provide
Information
to
Educate
Provide
Information
to
Modify
Behavior
IC
Objective
Text
may
be
one
of
the
following
if
the
IC
Objective
Media
is
Residuals:
Prohibit
Dermal
Contact
Prohibit
Ingestion
Exposure
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
33
Name/
XML
Tag
Definition
Notes
Prohibit
Inhalation
Exposure
Prohibit
Recreational
Exposure
Scenario
Prohibit
Residential
Exposure
Scenario
Prohibit
School/
Daycare
Exposure
Scenario
Prohibit
Utility
Worker/
Excavation
Exposure
Scenario
Protect
Integrity
of
an
Engineered
Remedy
Provide
Information
to
Educate
Provide
Information
to
Modify
Behavior
IC
Objective
Text
may
be
one
of
the
following
if
the
IC
Objective
Media
is
Sediment:
Prohibit
Ingestion
Exposure
Prohibit
Inhalation
Exposure
Prohibit
Residential
Exposure
Scenario
Protect
Integrity
of
an
Engineered
Remedy
Provide
Information
to
Educate
Provide
Information
to
Modify
Behavior
IC
Objective
Text
may
be
one
of
the
following
if
the
IC
Objective
Media
is
Sludge:
Prohibit
Dermal
Contact
Prohibit
Ingestion
Exposure
Prohibit
Inhalation
Exposure
Prohibit
Recreational
Exposure
Scenario
Prohibit
Residential
Exposure
Scenario
Prohibit
School/
Daycare
Exposure
Scenario
Prohibit
Utility
Worker/
Excavation
Exposure
Scenario
Protect
Integrity
of
an
Engineered
Remedy
Provide
Information
to
Educate
Provide
Information
to
Modify
Behavior
IC
Objective
Text
may
be
one
of
the
following
if
the
IC
Objective
Media
is
Soil:
Prohibit
Ingestion
Exposure
Prohibit
Inhalation
Exposure
Prohibit
Recreational
Exposure
Scenario
Prohibit
Residential
Exposure
Scenario
Prohibit
School/
Daycare
Exposure
Scenario
Prohibit
Utility
Worker/
Excavation
Exposure
Scenario
Protect
Integrity
of
an
Engineered
Remedy
Provide
Information
to
Educate
Provide
Information
to
Modify
Behavior
IC
Objective
Text
may
be
one
of
the
following
if
the
IC
Objective
Media
is
Solid
Waste:
Prohibit
Dermal
Contact
Prohibit
Ingestion
Exposure
Prohibit
Inhalation
Exposure
Prohibit
Recreational
Exposure
Scenario
Prohibit
Residential
Exposure
Scenario
Prohibit
School/
Daycare
Exposure
Scenario
Prohibit
Utility
Worker/
Excavation
Exposure
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
34
Name/
XML
Tag
Definition
Notes
Scenario
Protect
Integrity
of
an
Engineered
Remedy
Provide
Information
to
Educate
Provide
Information
to
Modify
Behavior
IC
Objective
Text
may
be
one
of
the
following
if
the
IC
Objective
Media
is
Subsurface
Soil:
Prohibit
Dermal
Contact
Prohibit
Ingestion
Exposure
Prohibit
Inhalation
Exposure
Prohibit
Recreational
Exposure
Scenario
Prohibit
Residential
Exposure
Scenario
Prohibit
Utility
Worker/
Excavation
Exposure
Scenario
Protect
Integrity
of
an
Engineered
Remedy
Provide
Information
to
Educate
Provide
Information
to
Modify
Behavior
IC
Objective
Text
may
be
one
of
the
following
if
the
IC
Objective
Media
is
Surface
Soil:
Prohibit
Dermal
Contact
Prohibit
Ingestion
Exposure
Prohibit
Inhalation
Exposure
Prohibit
Recreational
Exposure
Scenario
Prohibit
Residential
Exposure
Scenario
Prohibit
School/
Daycare
Exposure
Scenario
Prohibit
Utility
Worker/
Excavation
Exposure
Scenario
Protect
Integrity
of
an
Engineered
Remedy
Provide
Information
to
Educate
Provide
Information
to
Modify
Behavior
IC
Objective
Text
may
be
one
of
the
following
if
the
IC
Objective
Media
is
Surface
Water:
Prohibit
Aquatic
Food
Consumption
Prohibit
Dermal
Contact
Prohibit
Drinking
Prohibit
Ingestion
Exposure
Prohibit
Inhalation
Exposure
Prohibit
Other
Use
(
Industrial,
Food
Preparation,
Gardening,
Agricultural,
etc.)
Protect
Integrity
of
an
Engineered
Remedy
Provide
Information
to
Educate
Provide
Information
to
Modify
Behavior
4.2
Engineering
Control
Name
XML
Tag:
EngineeringControlName
The
name
assigned
to
a
process
and/
or
tool
designed
or
used
to
manage
storage,
disposal,
treatment,
and
other
handling
protocols
(
e.
g.,
the
physical
technology
used
to
cleanup
a
site)
Example
List
of
Values:
Aeration
Air
Emissions/
Off­
Gas
Treatment,
(
N.
O.
S.)
Air
Monitoring
Air
Sparging
Air
Stripping
(
Assuming
Pumping)
Air
Stripping
(
Assuming
Excavation)
Alternate
Drinking
Water,
(
N.
O.
S.)
Alternate
Drinking
Water,
Permanent
Replacement
Alternate
Drinking
Water,
Supply
Reinstated
Alternate
Drinking
Water,
Temporary
Replacement
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
35
Name/
XML
Tag
Definition
Notes
Biofiltration
Biological
Treatment
(
In­
Situ),
(
N.
O.
S.)
Biological
Treatment,
(
Ex­
Situ)
Biological
Treatment,
(
N.
O.
S.)
Bioreactors
Bioremediation
(
Ex­
Situ)
Bioremediation
(
In­
Situ)
Bioremediation
Treatment,
(
N.
O.
S.)
Bioslurping
(
Biological
Treatment)
Bioslurping
(
Physical/
Chemical
Treatment)
Biosparging
(
Biological
Treatment)
Biosparging
(
Physical/
Chemical
Treatment)
Bioventing
Cap
Carbon
Adsorption
Carbon
At
Tap
Chemical
Reactive
Wall
Chemical
Reduction/
Oxidation
(
Assuming
Pumping)
Chemical
Reduction/
Oxidation
(
Assuming
Excavation)
Clarification
Co­
Metabolic
Treatment
Coagulation
Component
Separation
Component
Separation,
(
N.
O.
S.)
Composting
Consolidate
Containment,
(
N.
O.
S.)
Controlled
Solid
Phase
Bioremediation
Decontamination
Dehalogenation
(
BCD)
Dehalogenation
(
Glycolate)
Dewatering
Dike/
Berm
Directional
Wells
(
Enhancement)
Discharge
Disposal
Drainage
Ditch
Dual
Phase
Dual
Phase
Extraction
Dust
Suppression
Electrokinetics
Encapsulation
Encapsulation
or
Overpacking
Engineering
Control,
(
N.
O.
S.)
Equalization
Evaporation
Excavation
Explosive/
Unexplosive
Ordnance
Extraction
Filtration
Fixed
Film
Flocculation
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
36
Name/
XML
Tag
Definition
Notes
Free
Product
Recovery
Fuming
Gasification
Gas
Collection/
Treatment
Grout
Curtain
Grouting
High
Energy
Corona
High
Temperature
Thermal
Desorption
Hot
Air
Injection
Hot
Gas
Decontamination
Hot
Water
or
Steam
Flushing/
Stripping
Hydraulic
Control
Hydrofracturing
(
Enhancement)
Impermeable
Barrier
In
Situ
Well
Aeration
Incineration
(
Assuming
Pumping)
Incineration
(
Assuming
Excavation)
Ion
Exchange
Landfarming
Leachate
Control
Levee
Limited
Response
Liner
Liquid
Phase
Carbon
Adsorption
(
Assuming
Pumping)
Liquid
Phase
Carbon
Adsorption
(
Assuming
Excavation)
Low
Temperature
Thermal
Desorption
Membrane
Separation
Monitoring
(
Air
Emissions/
Off­
Gas
Treatment)
Monitoring
(
Other)
Natural
Attenuation
Neutralization
(
Assuming
Pumping)
Neutralization
Nitrate
Enhancement
No
Action
No
Further
Action
Nutrient
Injection
Oil
Water
Separation
Open
Burn/
Open
Detonation
(
Assuming
Excavation)
Open
Burn/
Open
Detonation
Operations
(
O)
Operations
&
Maintenance
(
O&
M)
Other,
(
N.
O.
S.)
Oxidation
(
Air
Emissions/
Off­
Gas
Treatment)
Oxidation
(
Assuming
Pumping)
Oxidation
(
Assuming
Excavation)
Oxygen
Enhancement
With
Air
Sparging
Oxygen
Enhancement
With
H2O2
Passive
Treatment
Walls
Permeable
Treatment
Bed
(
Sludge)
Peroxidation
Physical
Separation
Physical/
Chemical
Treatment,
(
Ex­
Situ)
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
37
Name/
XML
Tag
Definition
Notes
Physical/
Chemical
Treatment,
(
In­
Situ.)
Physical/
Chemical
Treatment,
(
N.
O.
S.)
(
Air
Emissions/
Off­
Gas
Treatment)
Physical/
Chemical
Treatment,
(
N.
O.
S.)
(
Ex­
Situ)
Physical/
Chemical
Treatment,
(
N.
O.
S.)
(
In­
Situ)
Phytoremediation
(
Biological
Treatment)
Phytoremediation
(
Physical/
Chemical
Treatment)
Pneumatic
Fracturing
(
Enhancement)
Population
Relocation,
(
N.
O.
S.)
Population
Relocation,
Permanent
Population
Relocation,
Returned
Population
Relocation,
Temporary
Precipitation
Publicly
Owned
Treatment
Works
(
POTW)
Pump
And
Treat
Pyrolysis
Reactive
Wall
Recovery
Wells
Recycling
(
Assuming
Pumping)
Recycling
(
Assuming
Excavation)
Reduction
(
Assuming
Pumping)
Reduction
(
Assuming
Excavation)
Reinjection
Residuals
Discharge
Residuals
Disposal
Residuals
Storage
(
Temporary)
Revegetation
Reverse
Osmosis
Sedimentation
Sheet
Piling
Slope
Stabilization
Slurry
Phase
Bioremediation
Slurry
Wall
Soil
Flushing
Soil
Vapor
Extraction
(
Ex­
Situ)
Soil
Vapor
Extraction
(
SVE)
Soil
Washing
Solidification/
Stabilization
(
Ex­
situ)
Solidification/
Stabilization
(
In­
situ)
Solvent
Extraction
(
Chemical)
Storage
­
Permanent
Storage
­
Temporary
Subsurface
Drain
Surface
Drainage
Control
Surface
Water
Control
Surfactant
Flushing
Temporary
Well
Head
Treatment
Thermal
Treatment,
(
N.
O.
S.)
(
Assuming
Excavation)
Thermal
Treatment,
(
N.
O.
S.)
(
Ex­
situ)
Thermal
Treatment,
(
N.
O.
S.)
(
In­
situ)
Thermally
Enhanced
Soil
Vapor
Extraction
Tilling
Treatment,
(
N.
O.
S.)
(
Air
Emissions/
Off­
Gas
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
38
Name/
XML
Tag
Definition
Notes
Treatment)
Treatment,
(
N.
O.
S.)
(
Other)
UV
Oxidation
Vapor
Extraction
Vapor
Phase
Carbon
Adsorption
Vitrification
(
Ex­
situ)
Vitrification
(
In­
situ)
Water
Table
Adjustment
Waterline
Replacement
Well
Head
Treatment
Wetlands
Replacement
White
Rot
Fungus
7.3
Event
Type
XML
Tag:
EventTypeText
The
type
of
occurrence
or
action
taking
place
on
a
specific
date
or
over
a
period
of
time
Administrative
Order
on
Consent
(
AOC)
Alternative
Dispute
Resolution
Combined
Remedial
Investigation/
Feasibility
Study
(
RI/
FS)
Compliance
Inspection
 
Case
Development
Inspection
Compliance
Inspection
 
Compliance
Evaluation
Compliance
Inspection
 
Compliance
Sampling
Compliance
Inspection
 
Reconnaissance
or
Screening
Inspection
Compliance
Monitoring
 
Compliance
Inspection
Compliance
Monitoring
 
Compliance
Investigation
Compliance
Monitoring
 
Information
Request
Compliance
Monitoring
 
Offsite
Record
Review
Consent
Decree
(
CD)
Enforcement
Decision
Document
Enforcement
 
Complaint/
Proposed
Order
Enforcement
 
Demand
for
Stipulated
Penalties
Enforcement
 
Field
Citation
Enforcement
 
Final
Order
Enforcement
 
Judicial
Referral
Enforcement
 
Letter
to
Regulated
Entity
Enforcement
 
Letter
to
State/
Tribe
Enforcement
 
Oral
Notification
of
Violation
Enforcement
 
Voluntary
Compliance
Enforcement
 
Written
Notice
of
Violation
Explanation
of
Significant
Differences
(
ESD)
Federal
Facility
(
FF)
Feasibility
Study
(
FS)
FF
Long
Term
Response
Action
(
LR)
FF
Remedial
Action
(
RA)
FF
Remedial
Design
(
RD)
FF
Remedial
Investigation
(
RI)
FF
RI/
FS
FF
Removal
Feasibility
Study
Federal
Interagency
Agreement
Five
Year
Remedy
Assessment
IC
Enforcement
IC
Implementation
IC
Monitoring
IC
Termination
Long
Term
Response
Action
Institutional
Control
Data
Standard
Std
No.:
1­
XXX
Version
1
 
Final
Draft
July
26,
2005
Page
39
Name/
XML
Tag
Definition
Notes
Memorandum
of
Understanding
Multi­
Site
Cooperative
Agreement
No
Action
ROD
Operations
and
Maintenance
Potentially
Responsible
Party
(
PRP)
Emergency
Removal
PRP
FS
PRP
LR
PRP
RA
PRP
RD
PRP
RI
PRP
RI/
FS
PRP
Removal
RD
Contingency
Re­
Use
Plan
Record
of
Decision
(
ROD)
ROD
Amendment
Remedial
Action
Remedial
Design
Remedial
Investigation
Removal
Removal
Contingency
Resource
Archival
Resource
Creation
Resource
Modification
Resource
Presentation
Resource
Publication
Site
Access
Site
Security
And
Maintenance
State
Consent
Decree
State
Order
Unilateral
Administrative
Order
(
UAO)