Document ID: EPA-HQ-OPP-2004-0005-0016
Agency: epa
Document Type: Supporting & Related Material
Title: 
Posted Date: 2004-03-08T05:00Z

Appendix
L,
Page
1
of
3
Appendix
L.
QA/
QC
Guidance
for
Models
Model
Name
Version
Number
QA
Summary
Summary
Developer:
Person
or
Team
Name
and
Team
Member
Names
Date:
dd/
mmm/
yyyy
Model
Developer:
Person
or
Team
Name
and
Member
Names
Phone,
Address
(
e­
mail
and
postal)
Model
Contact:
Primary
Contact
Name
and
Alternate
Contact
Name
Phone,
Address
(
e­
mail
and
postal)

Model
Type:
Empirical,
deterministic,
stochastic(?),
Aquatic,
Ecological,
Health
Effects,
etc.

Historical
Insight:

Method
of
Version
Control
and
Notification:
process
and
names
involved
in
version
control
List
of
All
Prior
Model
Versions
and
Dates
of
their
QA
Summaries:
Version
Number,
QA
Summary
Date:
dd/
mmm/
yyyy
Version
Number,
QA
Summary
Date:
dd/
mmm/
yyyy
Model
Calibration
Reports:
Include
a
reference
to
where
this
information
is
available.

Model
Evaluation
Reports:
Include
a
reference
to
where
this
information
is
available.
Summerize
model
evaluation.
Refer
to:
Guidance
for
QA
Project
Plans
for
Modeling
(
QA/
G­
5M)
EPA/
600/
R­
02/
007
http://
www.
epa.
gov/
quality/
qa_
docs.
html
Peer
Review
Report
Summary
­
Dated:
dd/
mmm/
yyyy
Include
a
reference
to
where
this
information
is
available.

Model
Access
Mechanism
or
Model
Site:
Web
Site
or
Access
Location
User
Manual
Access
Mechanism
or
Site:
Web
Site
or
Access
Location
Intended
Use
of
Output
(
risk
characterization,
support
decision,
answer
question,
etc.):

Intended
Use
of
Output
justification
goes
here.

Regulatory
Context,
if
any:

Regulatory
Context
justifying
existence
of
the
model
goes
here.

Process
for
archiving
and
documentation:
Appendix
L,
Page
2
of
3
Model
Name
Version
Number
QA
Summary
Summary
Developer:
Person
or
Team
Name
and
Team
Member
Names
Date:
dd/
mmm/
yyyy
Model
Output
Description:
Include
output
description(
s)
including
the
format(
s).
And/
Or
include
a
reference
to
where
this
information
is
available.

Examples
of
How
Model
Output
is
Used:
Include
examples
of
model
output.
And/
Or
include
a
reference
to
where
this
information
is
available.
An
appendix
in
the
User's
Manual
might
be
appropriate.

Limitations
on
Model
Use:
Describe
any
limitations
on
using
the
model.
And/
Or
include
a
reference
to
where
this
information
is
available.
An
appendix
in
the
User's
Manual
might
be
appropriate.

Description
of
Model
Input
including
Input
Sources:
List
the
Model
Input
and
Input
Sources.
Describe
details
as
necessary
and/
or
include
a
reference
to
where
this
information
is
available.
This
should
refer
to
a
particular
portion
of
the
User's
Manual.
Appendix
L,
Page
3
of
3
Suggested
QA/
QC
Steps
for
Documenting
Changes
to
a
Model:

1.
Objective:
Why
were
changes
necessary?

2.
Process:
What
was
changed
and
how?

3.
Results:
Were
changes
made
in
a
satisfactory
manner?
Was
"
revised"
model
tested
to
make
sure
that
changes
met
objectives?
This
step
must
be
performed
by
someone
who
was
not
involved
in
the
"
Process"
step.

4.
What's
Next:
If
changes
were
found
to
met
set
objectives:

!
Document
all
above
steps.
It
is
recommended
that
a
"
readme.
txt"
file
containing
all
relevant
information
about
the
changes
be
created
for
the
"
new"
version.

!
Replace
"
old"
version
with
"
new"
version
(
Make
sure
to
have
a
version
control
number
to
differentiate
new
vs
old).

!
Notify
users
of
changes
and
of
the
"
new"
version
!
Archive
"
old"
version
!
Send
a
copy
of
the
documentation
to
the
QA
officer.

TLN
01/
24/
2003