is decimal degrees (e.g., -
                                    77.029289) and the WGS84
                                    standard coordinate system.
                                    The Permitted Feature
                                    Identifier (Compliance
                                    Monitoring Activity) data
                                    element is used to identify
                                    the location of each sewer
                                    overflow at a permitted
                                    feature. If the sewer
                                    overflow is associated with
                                    a private residence the
                                    latitude of the nearest
                                    collection system structure
                                    (e.g., manhole) can be used
                                    for this data element to the
                                    extent that reporting is
                                    required. The POTW can leave
                                    this data element blank on
                                    the Sewer Overflow/Bypass
                                    Event Report if the sewer
                                    overflows are caused by an
                                    extreme weather event (e.g.,
                                    hurricane) that floods the
                                    entire sewer system and are
                                    too numerous to count. This
                                    data element can also be
                                    system generated if the
                                    Sewer Overflow/Bypass Event
                                    Report collects the street
                                    location of the sewer
                                    overflow and the street
                                    location can be used to
                                    generate an accurate
                                    longitude value. (Note:
                                    ``Post Office Box''
                                    addresses and ``Rural
                                    Route'' addresses are
                                    generally not geocodable).
Type of Sewer Overflow/Bypass      A unique code/description      122.41(l)(4), (6),   3, 9.
 (Sewer Overflow/Bypass Event       that identifies the type of    and (7) and
 Report).                           sewer overflow or bypass       122.41(m)(3).
                                    (e.g., CSO or SSO from the
                                    POTW's collection system,
                                    anticipated bypass from the
                                    treatment works,
                                    unanticipated bypass from
                                    the treatment works) for
                                    each Sewer Overflow/Bypass
                                    Identifier. For bypass
                                    events the permittee will
                                    also use this data element
                                    to identify if any NPDES
                                    effluent limitations were
                                    violated as a result of the
                                    bypass.
Type of Sewer Overflow/Bypass      A unique code/description      122.41(l)(4), (6),   3, 9.
 Structure.                         that identifies the type of    and (7) and
                                    sewer overflow or bypass       122.41(m)(3).
                                    structure (e.g., manhole,
                                    CSO outfall) for each Sewer
                                    Overflow/Bypass Identifier.
                                    The POTW can leave this data
                                    element blank on the Sewer
                                    Overflow/Bypass Event Report
                                    if the sewer overflows are
                                    caused by an extreme weather
                                    event (e.g., hurricane) that
                                    floods the entire sewer
                                    system and are too numerous
                                    to count.
Sewer Overflow/Bypass Cause......  The one or more unique codes/  122.41(l)(4), (6),   3, 9
                                    descriptions that best         and (7) and
                                    represent the likely cause     122.41(m)(3).
                                    of the sewer overflow or
                                    bypass (e.g., broken pipe,
                                    fats/oil/grease, mechanical
                                    failure, pump station
                                    electrical failure, wet
                                    weather, vandalism) for each
                                    Sewer Overflow/Bypass
                                    Identifier..
Duration of Sewer Overflow/Bypass  Estimated duration of the      122.41(l)(4), (6),   3, 9.
 (hours) (Sewer Overflow/Bypass     sewer overflow or bypass (in   and (7) and
 Event Report).                     hours) for each Sewer          122.41(m)(3).
                                    Overflow/Bypass Identifier.
                                    If the discharge has not
                                    been corrected, this is the
                                    best professional judgment
                                    from the sewer owner or in
                                    the case of a bypass, the
                                    treatment plant owner, of
                                    the time the sewer overflow
                                    or bypass is expected to
                                    continue. The POTW can leave
                                    this data element blank on
                                    the Sewer Overflow/Bypass
                                    Event Report if the sewer
                                    overflows are caused by an
                                    extreme weather event (e.g.,
                                    hurricane) that floods the
                                    entire sewer system and are
                                    too numerous to count.

Sewer Overflow/Bypass Discharge    Best professional judgment     122.41(l)(4), (6),   3, 9.
 Volume (gallons) (Sewer Overflow/  from the sewer owner on the    and (7) and
 Bypass Event Report).              estimated number of gallons    122.41(m)(3).
                                    of sewer overflow or bypass
                                    for each Sewer Overflow/
                                    Bypass Identifier. If the
                                    discharge has not been
                                    corrected, this is the best
                                    professional judgment from
                                    the sewer owner or in the
                                    case of a bypass, the
                                    treatment plant owner, of
                                    the volume of overflow or
                                    bypass prior to cessation.
                                    The POTW can leave this data
                                    element blank on the Sewer
                                    Overflow/Bypass Event Report
                                    if the sewer overflows are
                                    caused by an extreme weather
                                    event (e.g., hurricane) that
                                    floods the entire sewer
                                    system and are too numerous
                                    to count.
Receiving Waterbody Name for       This data element identifies   122.41(l)(4), (6),   3, 9.
 Unpermitted Feature (Sewer         the receiving waterbody name   and (7).
 Overflow/Bypass Event Report).     for each Sewer Overflow/
                                    Bypass Identifier that does
                                    not have a corresponding
                                    value in the `Permitted
                                    Feature Identifier (Permit)'
                                    data element. This data
                                    element will use the best
                                    professional judgment of the
                                    sewer owner to identify the
                                    name of the waterbody that
                                    is or will likely receive
                                    the discharge from each
                                    Sewer Overflow/Bypass
                                    Identifier. The POTW can
                                    leave this data element
                                    blank on the Sewer Overflow/
                                    Bypass Event Report if the
                                    sewer overflows are caused
                                    by an extreme weather event
                                    (e.g., hurricane) that
                                    floods the entire sewer
                                    system and are too numerous
                                    to count.
Wet Weather Occurrence for Sewer   The unique code (e.g.,         122.41(l)(4), (6),   3, 9.
 Overflow/Bypass Status.            ``Yes'', ``No'') that          and (7) and
                                    represents the best            122.41(m)(3).
                                    professional judgment of the
                                    sewer owner, or in the case
                                    of a bypass, the treatment
                                    plant owner, regarding
                                    whether the sewer overflow
                                    or bypass, by Sewer Overflow/
                                    Bypass Identifier, occurred
                                    during wet weather.
Corrective Actions Taken or        The unique code/description    122.41(l)(4), (6),   3, 9.
 Planned for Sewer Overflow/        that describes the steps       and (7) and
 Bypass (Sewer Overflow/Bypass      taken or planned to reduce,    122.41(m)(3).
 Event Report).                     eliminate, and prevent
                                    reoccurrence of future sewer
                                    overflows or bypasses for
                                    each Sewer Overflow/Bypass
                                    Identifier and the related
                                    impacts to health and the
                                    environment. This data
                                    element can be used to
                                    identify the portion of the
                                    sewer overflow or bypass
                                    that was contained and
                                    recovered prior to any
                                    discharge to waters of the
                                    U.S. This data element will
                                    also identify if any
                                    monitoring of the receiving
                                    waterbody was done during
                                    and/or after the sewer
                                    overflow or bypass to gauge
                                    the potential impact to
                                    health and the environment.
                                    The POTW can leave this data
                                    element blank on the Sewer
                                    Overflow/Bypass Event Report
                                    if the sewer overflows are
                                    caused by an extreme weather
                                    event (e.g., hurricane) that
                                    floods the entire sewer
                                    system and are too numerous
                                    to count.
Type of Potential Impact of Sewer  The unique code/description    122.41(l)(4), (6),   3, 9.
 Overflow/Bypass (Sewer Overflow/   that describes the type of     and (7) and
 Bypass Event Report).              potential health or            122.41(m)(3).
                                    environmental impact(s)
                                    (e.g., beach closure) for
                                    each Sewer Overflow/Bypass
                                    Identifier. Under 40 CFR
                                    122.41(l)(6), ``the
                                    permittee shall report any
                                    noncompliance which may
                                    endanger health or the
                                    environment.'' This data
                                    element provides information
                                    regarding the nature of such
                                    potential endangerment. The
                                    POTW can leave this data
                                    element blank on the Sewer
                                    Overflow/Bypass Event Report
                                    if the sewer overflows are
                                    caused by an extreme weather
                                    event (e.g., hurricane) that
                                    floods the entire sewer
                                    system and are too numerous
                                    to count.
----------------------------------------------------------------------------------------------------------------

    Compliance Monitoring Activity Information (Data Elements Specific to CWA section 316(b) Annual Reports)

[Note: Where the Director requires additional measures to protect Federally-listed threatened or endangered
 species or critical habitat pursuant to 40 CFR 125.94(g), the Director shall require reporting associated with
 those measures [see 40 CFR 125.97(g)]. The following data elements correspond to this reporting requirement.
 These data elements are only required for facilities that are required to report on their additional measures
 to protect Federally-listed threatened or endangered species or critical habitat.]
----------------------------------------------------------------------------------------------------------------
CWA Section 316(b) Biological      For existing facilities, a     125.96, 125.97(g),   10.
 Monitoring--Species Name           listing of each Federally-     125.98,
 (Program Report).                  listed threatened or           125.138(b), 401.14
                                    endangered species (or         and CWA section
                                    relevant taxa) for all life    316(b).
                                    stages that might be
                                    susceptible to impingement
                                    and entrainment at the
                                    facility's cooling water
                                    intake structure(s).
                                    Specific monitoring
                                    protocols and frequency of
                                    monitoring will be
                                    determined by the Director.
CWA Section 316(b) Biological      For existing facilities, the   125.96, 125.97(g),   10.
 Monitoring--Species Number         number of each Federally-      125.98,
 (Program Report).                  listed threatened or           125.138(b), 401.14
                                    endangered species (or         and CWA section
                                    relevant taxa) that might be   316(b).
                                    susceptible to impingement
                                    and entrainment at the
                                    facility's cooling water
                                    intake structure(s).
                                    Specific monitoring
                                    protocols and frequency of
                                    monitoring will be
                                    determined by the Director.
CWA Section 316(b) Biological      For existing facilities, a     125.96, 125.97(g),   10.
 Monitoring--Threatened or          unique code/description that   125.98,
 Endangered Status (Program         identifies for each            125.138(b), 401.14
 Report).                           Federally-listed threatened    and CWA section
                                    or endangered species (or      316(b).
                                    relevant taxa) whether the
                                    species is threatened,
                                    endangered, or is an
                                    otherwise protected species
                                    that might be susceptible to
                                    impingement and entrainment
                                    at the facility's cooling
                                    water intake structure(s).
                                    Specific monitoring
                                    protocols and frequency of
                                    monitoring will be
                                    determined by the Director.
CWA Section 316(b) Biological      For existing facilities, the   125.96, 125.97(g),   10.
 Monitoring--Species Impinged and   number of each Federally-      125.98,
 Entrained (Program Report).        listed threatened or           125.138(b), 401.14
                                    endangered species (or         and CWA section
                                    relevant taxa) impinged and    316(b).
                                    entrained per year by the
                                    facility's cooling water
                                    intake structure(s).
                                    Specific monitoring
                                    protocols and frequency of
                                    monitoring will be
                                    determined by the Director.
CWA Section 316(b) Biological      For existing facilities, a     125.96, 125.97(g),   10.
 Monitoring--Applicable Measures    text summary of the measures   125.98,
 to Protect Designated Critical     taken by the permittee to      125.138(b), 401.14
 Habitat (Program Report).          protect designated critical    and CWA section
                                    habitat in the vicinity of     316(b).
                                    impingement and entrainment
                                    at the facility's cooling
                                    water intake structure(s).
----------------------------------------------------------------------------------------------------------------
                     Information Common to Violations, Enforcement Actions, and Final Orders

[Note: Single Event Violation (SEV) data elements are mandatory for construction stormwater inspections that
 identify CWA violations that result in a regulatory authority taking a formal enforcement action. SEV data
 elements are optional for other construction stormwater inspections.]
----------------------------------------------------------------------------------------------------------------
Violation Code...................  The unique code/description    123.45 and CWA       1.
                                    that identifies each type of   section 309.
                                    violation that has occurred
                                    at the facility (e.g., D80 =
                                    Required Monitoring DMR
                                    Value Non-Receipt, E90 =
                                    Effluent Violation, C20 =
                                    Schedule Event Achieved
                                    Late). This includes single
                                    event violations (SEVs) and
                                    violations that are system
                                    generated based upon DMRs,
                                    schedules, etc.
Violation Date...................  This is the date of the        123.45 and CWA       1.
                                    violation, which varies        section 309.
                                    depending on the type of
                                    violation. The date must be
                                    provided in YYYY-MM-DD
                                    format where YYYY is the
                                    year, MM is the month, and
                                    DD is the day. This data
                                    element may be system
                                    generated and does not apply
                                    to single event violation
                                    dates.
----------------------------------------------------------------------------------------------------------------
                                              Violation Information
----------------------------------------------------------------------------------------------------------------
Agency Identifying the Single      The unique code/description    123.26, 123.41(a),   1.
 Event Violation (SEV).             that identifies the agency     123.45.
                                    that identified the single
                                    event violation (SEV).

Single Event Violation Start Date  The date the single event      123.26, 123.41(a),   1.
                                    violation (SEV) began. If      123.45.
                                    the SEV occurred on one
                                    date, this data element is
                                    optional as this date can be
                                    system generated to equal
                                    ``Single Event Violation End
                                    Date'' when left blank. The
                                    date must be provided in
                                    YYYY-MM-DD format where YYYY
                                    is the year, MM is the
                                    month, and DD is the day.
Single Event Violation End Date..  The date the single event      123.26, 123.41(a),   1.
                                    violation (SEV) ended. This    123.45.
                                    field will be left blank to
                                    denote an ongoing or
                                    unresolved SEV. The date
                                    must be provided in YYYY-MM-
                                    DD format where YYYY is the
                                    year, MM is the month, and
                                    DD is the day.
RNC Detection Code...............  The unique code/description    123.26, 123.41(a),   1.
                                    that identifies the type of    123.45.
                                    reportable noncompliance
                                    (RNC) detected by the
                                    regulatory authority.
RNC Detection Date...............  The date that reportable       123.26, 123.41(a),   1.
                                    noncompliance (RNC) was        123.45.
                                    detected. This date may vary
                                    according to the type of
                                    violation detected. The date
                                    must be provided in YYYY-MM-
                                    DD format where YYYY is the
                                    year, MM is the month, and
                                    DD is the day.
RNC Resolution Code..............  The unique code/description    123.26, 123.41(a),   1.
                                    that identifies the            123.45.
                                    reportable noncompliance
                                    (RNC) status (e.g.,
                                    noncompliant, resolved
                                    pending, waiting resolution,
                                    resolved) for each
                                    violation. This data element
                                    can be entered manually or
                                    system generated.
RNC Resolution Date..............  The date reportable            123.26, 123.41(a),   1.
                                    noncompliance (RNC) was        123.45.
                                    marked to its current
                                    resolution status. This data
                                    element is entered manually.
                                    The date must be provided in
                                    YYYY-MM-DD format where YYYY
                                    is the year, MM is the
                                    month, and DD is the day.
----------------------------------------------------------------------------------------------------------------
                                         Enforcement Action Information

[Note: NPDES authorized programs will only need to share criminal action information with EPA when the criminal
 case is concluded.]
----------------------------------------------------------------------------------------------------------------
Enforcement Action Identifier....  The unique identifier for      123.27, 123.41(a),   1.
                                    each enforcement action. For   and CWA section
                                    EPA enforcement actions,       309.
                                    this field will be have
                                    three components, each
                                    separated by a hyphen (e.g.,
                                    04-2014-4509). These three
                                    components are: (1) the EPA
                                    Region responsible for the
                                    enforcement action as
                                    identified by the EPA Region
                                    code (e.g., 04); (2) the
                                    four-digit fiscal year
                                    during which the enforcement
                                    action is initiated (e.g.,
                                    2014); and (3) a four-digit,
                                    user-assigned sequence
                                    number between 0001 and 9999
                                    (e.g., 4509). States will be
                                    able to use this same
                                    structure, or they will be
                                    able to use a different
                                    structure of their choosing
                                    provided that the first two
                                    characters of the identifier
                                    constitute the state code
                                    (e.g., Alabama = ``AL'').
Enforcement Action Forum.........  This identifies the forum of   123.27, 123.41(a),   1.
                                    the formal enforcement         and CWA section
                                    action (e.g., administrative   309.
                                    formal, judicial). This can
                                    be system generated.
Enforcement Action Type..........  The unique code/description    123.27, 123.41(a),   1.
                                    that identifies the type for   and CWA section
                                    each formal or informal        309.
                                    enforcement action. This
                                    code/description identifies,
                                    for example, whether the
                                    enforcement action is a
                                    civil judicial referral, a
                                    notice of violation, an
                                    administrative penalty
                                    order, administrative order,
                                    or criminal prosecution.
Programs Violated (Enforcement     The unique code/description    123.27, 123.41(a),   1.
 Action).                           that identifies each program   and CWA section
                                    (e.g., pretreatment,           309.
                                    biosolids/sewage sludge,
                                    MS4s, Core NPDES program)
                                    associated with each
                                    enforcement activity.

Enforcement Action Sub-activity    A unique code/description      123.27, 123.41(a),   1.
 Type.                              that identifies the type for   and CWA section
                                    each sub-activity associated   309.
                                    with each enforcement
                                    activity (e.g., COMPS =
                                    compliance achieved, MECDJ =
                                    motion to enforce consent
                                    agreement, AHRG =
                                    administrative hearing,
                                    AMNCA = amended complaint).
                                    Some of these sub-activities
                                    are system required and some
                                    can be system generated.
                                    Data on sub-activities that
                                    are not milestones are
                                    optional.
Enforcement Action Sub-activity    The date on which the sub-     123.27, 123.41(a),   1.
 Completion Date.                   activity was completed. This   and CWA section
                                    data element is required for   309.
                                    each sub-activity provided.
                                    The date must be provided in
                                    YYYY-MM-DD format where YYYY
                                    is the year, MM is the
                                    month, and DD is the day.
                                    Some of these dates can be
                                    system generated.
----------------------------------------------------------------------------------------------------------------
                                             Final Order Information

 [Note: These data elements are linked to the ``Enforcement Action Identifier''. NPDES authorized programs will
          only need to share criminal action information with EPA when the criminal case is concluded.]
----------------------------------------------------------------------------------------------------------------
Final Order Identifier...........  The unique identifier for      123.27, 123.41(a),   1.
                                    each final order. This data    and CWA section
                                    element can be system          309.
                                    generated.
Final Order Type.................  A unique code that identifies  123.27, 123.41(a),   1.
                                    the legal process used by      and CWA section
                                    the authorized NPDES program   309.
                                    to settle the enforcement
                                    action (e.g., administrative
                                    compliance order, an
                                    administrative penalty
                                    order, consent decree,
                                    Federal facility agreement,
                                    criminal conviction or plea
                                    agreement).
Final Order Issued/Entered Date..  For a judicial enforcement     123.27, 123.41(a),   1.
                                    action this is the date the    and CWA section
                                    Clerk of the Court stamps      309.
                                    the document after it is
                                    signed by the presiding
                                    Judge. For an administrative
                                    formal enforcement action
                                    this is the date the Final
                                    Order was issued. For a
                                    criminal enforcement action,
                                    this is the date the
                                    sentence was imposed. The
                                    date must be provided in
                                    YYYY-MM-DD format where YYYY
                                    is the year, MM is the
                                    month, and DD is the day.
NPDES Closed Date................  The date of closure for each   123.27, 123.41(a),   1.
                                    NPDES final order. The date    and CWA section
                                    must be provided in YYYY-MM-   309.
                                    DD format where YYYY is the
                                    year, MM is the month, and
                                    DD is the day.
----------------------------------------------------------------------------------------------------------------
                                               Penalty Information

[Note: These data elements are linked to the ``Enforcement Action Identifier''. NPDES authorized programs will
 only need to share criminal action information with EPA when the criminal case is concluded.]
----------------------------------------------------------------------------------------------------------------
Penalty Amount Assessed..........  For civil judicial             123.27, 123.41(a),   1.
                                    enforcement actions, the       and CWA section
                                    dollar amount of the penalty   309.
                                    assessed against the
                                    defendant(s) as specified in
                                    the final entered Consent
                                    Decree or Court Order. For
                                    administrative enforcement
                                    actions, it is the dollar
                                    amount of the penalty
                                    assessed in the Consent
                                    Decree or Final Order. For
                                    criminal enforcement
                                    actions, it is the dollar
                                    amount of the fine agreed to
                                    by the defendant or
                                    sentenced by the Court and
                                    should include fields for
                                    prison time, probation, home
                                    confinement or monitoring
                                    periods, restitution, and
                                    special assessments.
Penalty Amount Collected.........  For civil judicial             123.27, 123.41(a),   1.
                                    enforcement actions, the       and CWA section
                                    dollar amount of the penalty   309.
                                    collected from the
                                    defendant(s). For
                                    administrative enforcement
                                    actions, it is the dollar
                                    amount collected of the
                                    penalty assessed in the
                                    Consent Decree or Final
                                    Order. For criminal
                                    enforcement actions, it is
                                    the dollar amount of the
                                    fine paid by the defendant
                                    as well as restitution and
                                    special assessments.
Supplemental Environmental         The unique identifier for      123.27, 123.41(a),   1.
 Project Identifier.                each supplemental              and CWA section
                                    environmental project. This    309.
                                    data element can be system
                                    generated.

Supplemental Environmental         The assessed cost, in          123.27, 123.41(a),   1.
 Project Amount.                    dollars, of the one or more    and CWA section
                                    of the defendant's             309.
                                    Supplemental Environmental
                                    Projects (SEPs). This is the
                                    dollar amount that is
                                    assessed either in addition
                                    to civil penalties or in
                                    lieu of civil penalties.
                                    This data element is only
                                    required if there is a SEP
                                    and may be entered at a
                                    later date when the data is
                                    available.
Supplemental Environmental         This text field summarizes     123.27, 123.41(a),   1.
 Project Description.               the Supplemental               and CWA section
                                    Environmental Projects         309.
                                    (SEPs) that the respondent
                                    has completed in response to
                                    an enforcement action. This
                                    data element is only
                                    required if there is a SEP
                                    and may be entered at a
                                    later date when the data is
                                    available.
----------------------------------------------------------------------------------------------------------------
                                         Compliance Schedule Information

[Note: These data elements are linked to the ``Enforcement Action Identifier''.]
----------------------------------------------------------------------------------------------------------------
Compliance Schedule Number.......  This number that in            123.27, 123.41(a),   1.
                                    combination with the           and CWA section
                                    Compliance Schedule Type and   309.
                                    NPDES ID uniquely identifies
                                    a compliance schedule.
Compliance Schedule Type.........  The unique code/description    123.27, 123.41(a),   1.
                                    that identifies the type of    and CWA section
                                    compliance schedule (e.g.,     309.
                                    an administrative formal
                                    action = ``A'', a judicial
                                    action = ``J'').
Compliance Schedule Description..  The unique code/description    123.27, 123.41(a),   1.
                                    that identifies each type of   and CWA section
                                    condition or requirement       309.
                                    (e.g., best management
                                    practices plan development)
                                    for the compliance schedule.
Compliance Schedule Event Code...  The unique code/description    123.27, 123.41(a),   1.
                                    that identifies each event     and CWA section
                                    that is added within a         309.
                                    compliance schedule.
Compliance Schedule Due Date.....  The date the compliance        123.27, 123.41(a),   1.
                                    schedule event is scheduled    and CWA section
                                    to be completed (i.e., the     309.
                                    due date). The date must be
                                    provided in YYYY-MM-DD
                                    format where YYYY is the
                                    year, MM is the month, and
                                    DD is the day.
Compliance Schedule Actual Date..  The actual date on which the   123.27, 123.41(a),   1.
                                    compliance schedule event      and CWA section
                                    was completed or achieved.     309.
                                    The date must be provided in
                                    YYYY-MM-DD format where YYYY
                                    is the year, MM is the
                                    month, and DD is the day.
Compliance Schedule Report         The date the regulatory        123.27, 123.41(a),   1.
 Received Date.                     agency received the report     and CWA section
                                    required by the compliance     309.
                                    schedule report. The date
                                    must be provided in YYYY-MM-
                                    DD format where YYYY is the
                                    year, MM is the month, and
                                    DD is the day.
----------------------------------------------------------------------------------------------------------------

    Notes:
    (1) The NPDES program authority may pre-populate these data
elements and other data elements (e.g., Federal Registry System ID)
in the NPDES electronic reporting systems in order to create
efficiencies and standardization. For example, the NPDES program
authority may configure their electronic reporting system to
automatically generate NPDES IDs for control mechanisms for new
facilities reported on a Pretreatment Program Report [40 CFR
403.12(i)]. Additionally, the NPDES program authority can decide
whether to allow NPDES regulated entities to override these pre-
populated data.
    (2) The data elements in this table conform to EPA's policy
regarding the application requirements for renewal or reissuance of
NPDES permits for discharges from municipal separate storm sewer
systems (see 61 FR 41698; 6 August 1996).
    (3) The data elements in this table are also supported by the
Office Management and Budget approved permit applications and forms
for the NPDES program.
    (4) These data will allow EPA and the NPDES program authority to
link facilities, compliance monitoring activities, compliance
determinations, and enforcement actions. For example, these data
will provide several ways to make the following linkages: linking
violations to enforcement actions and final orders; linking single
event violations and compliance monitoring activities; linking
program reports to DMRs; linking program reports to compliance
monitoring activities; and linking enforcement activities and
compliance monitoring activities.

PART 403--GENERAL PRETREATMENT REGULATIONS FOR EXISTING AND NEW
SOURCES OF POLLUTION

0
24. The authority citation for part 403 continues to read as follows:

    Authority:  33 U.S.C. 1251 et seq.

0
25. Amend Sec.  403.10 by adding paragraph (f)(2)(viii) to read as
follows:

Sec.  403.10  Development and submission of NPDES State pretreatment
programs.

* * * * *
    (f) * * *
    (2) * * *

    (viii) Regularly notify all Control Authorities of electronic
submission requirements of 40 CFR part 127.
* * * * *

0
26. Amend Sec.  403.12 by revising paragraphs (e)(1), (h), and (i)
introductory text to read as follows:

Sec.  403.12  Reporting requirements for POTW's and industrial users.

* * * * *
    (e) * * *
    (1) Any Industrial User subject to a categorical Pretreatment
Standard (except a Non-Significant Categorical User as defined in Sec.
403.3(v)(2)), after the compliance date of such Pretreatment Standard,
or, in the case of a New Source, after commencement of the discharge
into the POTW, shall submit to the Control Authority during the months
of June and December, unless required more frequently in the
Pretreatment Standard or by the Control Authority or the Approval
Authority, a report indicating the nature and concentration of
pollutants in the effluent which are limited by such categorical
Pretreatment Standards. In addition, this report shall include a record
of measured or estimated average and maximum daily flows for the
reporting period for the Discharge reported in paragraph (b)(4) of this
section except that the Control Authority may require more detailed
reporting of flows. In cases where the Pretreatment Standard requires
compliance with a Best Management Practice (or pollution prevention
alternative), the User shall submit documentation required by the
Control Authority or the Pretreatment Standard necessary to determine
the compliance status of the User. At the discretion of the Control
Authority and in consideration of such factors as local high or low
flow rates, holidays, budget cycles, etc., the Control Authority may
modify the months during which the above reports are to be submitted.
For Industrial Users for which EPA or the authorized state, tribe, or
territory is the Control Authority, as of December 21, 2020 all reports
submitted in compliance with this section must be submitted
electronically by the industrial user to the Control Authority or
initial recipient, as defined in 40 CFR 127.2(b), in compliance with
this section and 40 CFR part 3 (including, in all cases, subpart D to
part 3), 40 CFR 122.22, and 40 CFR part 127. Part 127 is not intended
to undo existing requirements for electronic reporting. Prior to this
date, and independent of part 127, the Industrial Users for which EPA
or the authorized state, tribe, or territory is the Control Authority
may be required to report electronically if specified by a particular
control mechanism or if required to do so by state law.
* * * * *
    (h) Reporting requirements for Industrial Users not subject to
categorical Pretreatment Standards. The Control Authority must require
appropriate reporting from those Industrial Users with Discharges that
are not subject to categorical Pretreatment Standards. Significant Non-
categorical Industrial Users must submit to the Control Authority at
least once every six months (on dates specified by the Control
Authority) a description of the nature, concentration, and flow of the
pollutants required to be reported by the Control Authority. In cases
where a local limit requires compliance with a Best Management Practice
or pollution prevention alternative, the User must submit documentation
required by the Control Authority to determine the compliance status of
the User. These reports must be based on sampling and analysis
performed in the period covered by the report, and in accordance with
the techniques described in part 136 of this chapter and amendments
thereto. This sampling and analysis may be performed by the Control
Authority in lieu of the significant non-categorical Industrial User.
For Industrial Users for which EPA or the authorized state, tribe, or
territory is the Control Authority, as of December 21, 2020 all reports
submitted in compliance with this section must be submitted
electronically by the industrial user to the Control Authority or
initial recipient, as defined in 40 CFR 127.2(b), in compliance with
this section and 40 CFR part 3 (including, in all cases, subpart D to
part 3), 40 CFR 122.22, and 40 CFR part 127. Part 127 is not intended
to undo existing requirements for electronic reporting. Prior to this
date, and independent of part 127, the Industrial Users for which EPA
or the authorized state, tribe, or territory is the Control Authority
may be required to report electronically if specified by a particular
control mechanism or if required to do so by state law.
    (i) Annual POTW reports. POTWs with approved Pretreatment Programs
shall provide the Approval Authority with a report that briefly
describes the POTW's program activities, including activities of all
participating agencies, if more than one jurisdiction is involved in
the local program. The report required by this section shall be
submitted no later than one year after approval of the POTW's
Pretreatment Program, and at least annually thereafter, and must
include, at a minimum, the applicable required data in appendix A to 40
CFR part 127. The report required by this section must also include a
summary of changes to the POTW's pretreatment program that have not
been previously reported to the Approval Authority and any other
relevant information requested by the Approval Authority. As of
December 21, 2020 all annual reports submitted in compliance with this
section must be submitted electronically by the POTW Pretreatment
Program to the Approval Authority or initial recipient, as defined in
40 CFR 127.2(b), in compliance with this section and 40 CFR part 3
(including, in all cases, subpart D to part 3), 40 CFR 122.22, and 40
CFR part 127. Part 127 is not intended to undo existing requirements
for electronic reporting. Prior to this date, and independent of part
127, the Approval Authority may also require POTW Pretreatment Programs
to electronically submit annual reports under this section if specified
by a particular permit or if required to do so by state law.
* * * * *

PART 501--STATE SLUDGE MANAGEMENT PROGRAM REGULATIONS

0
27. The authority citation for part 501 continues to read as follows:

    Authority:  33 U.S.C. 1251 et seq.

0
28. Revise Sec.  501.21 to read as follows:

Sec.  501.21  Program reporting to EPA.

    As of December 21, 2020, state sludge management programs must
comply with 40 CFR part 3 and 40 CFR part 127 (including the applicable
required data elements in appendix A to part 127).

PART 503--STANDARDS FOR THE USE OR DISPOSAL OF SEWAGE SLUDGE

0
29. The authority citation for part 503 continues to read as follows:

    Authority:  Sections 405 (d) and (e) of the Clean Water Act, as
amended by Pub. L. 95-217, sec. 54(d), 91 Stat. 1591 (33 U.S.C. 1345
(d) and (e)); and Pub. L. 100-4, title IV, sec. 406(a), (b), 101
Stat., 71, 72 (33 U.S.C. 1251 et seq.).

0
30. Amend Sec.  503.18 by revising paragraph (a) introductory text to
read as follows:

Sec.  503.18  Reporting.

    (a) Class I sludge management facilities, POTWs (as defined in
Sec.  501.2 of this chapter) with a design flow rate equal to or
greater than one million

gallons per day, and POTWs that serve 10,000 people or more shall
submit a report on February 19 of each year. As of December 21, 2016
all reports submitted in compliance with this section must be submitted
electronically by the operator to EPA when the Regional Administrator
is the Director in compliance with this section and 40 CFR part 3
(including, in all cases, subpart D to part 3), 40 CFR 122.22, and 40
CFR part 127. As of December 21, 2020 all reports submitted in
compliance with this section must be submitted electronically in
compliance with this section and 40 CFR part 3 (including, in all
cases, subpart D to part 3), 40 CFR 122.22, and 40 CFR part 127. Part
127 is not intended to undo existing requirements for electronic
reporting. Prior to the start dates for electronic reporting (see Table
1 in 40 CFR 127.16), the Director may also require operators to
electronically submit annual reports under this section if required to
do so by state law.
* * * * *

0
31. Revise Sec.  503.28 to read as follows:

Sec.  503.28  Reporting.

    Class I sludge management facilities, POTWs (as defined in 40 CFR
501.2) with a design flow rate equal to or greater than one million
gallons per day, and POTWs that serve 10,000 people or more shall
submit a report on February 19 of each year. As of December 21, 2016
all reports submitted in compliance with this section must be submitted
electronically by the operator to EPA when the Regional Administrator
is the Director in compliance with this section and 40 CFR part 3
(including, in all cases, subpart D to part 3), 40 CFR 122.22, and 40
CFR part 127. As of December 21, 2020 all reports submitted in
compliance with this section must be submitted electronically in
compliance with this section and 40 CFR part 3 (including, in all
cases, subpart D to part 3), 40 CFR 122.22, and 40 CFR part 127. Part
127 is not intended to undo existing requirements for electronic
reporting. Prior to the start dates for electronic reporting (see Table
1 in 40 CFR 127.16), the Director may also require operators to
electronically submit annual reports under this section if required to
do so by state law.

0
32. Revise Sec.  503.48 to read as follows:

Sec.  503.48  Reporting.

    Class I sludge management facilities, POTWs (as defined in Sec.
501.2 of this chapter) with a design flow rate equal to or greater than
one million gallons per day, and POTWs that serve a population of
10,000 people or greater shall submit a report on February 19 of each
year. As of December 21, 2016 all reports submitted in compliance with
this section must be submitted electronically by the operator to EPA
when the Regional Administrator is the Director in compliance with this
section and 40 CFR part 3 (including, in all cases, subpart D to part
3), 40 CFR 122.22, and 40 CFR part 127. As of December 21, 2020 all
reports submitted in compliance with this section must be submitted
electronically in compliance with this section and 40 CFR part 3
(including, in all cases, subpart D to part 3), 40 CFR 122.22, and 40
CFR part 127. Part 127 is not intended to undo existing requirements
for electronic reporting. Prior to the start dates for electronic
reporting (see Table 1 in 40 CFR 127.16), the Director may also require
operators to electronically submit annual reports under this section if
required to do so by state law.

[FR Doc. 2015-24954 Filed 10-21-15; 8:45 am]
BILLING CODE 6560-50-P


[Federal Register: October 24, 2007 (Volume 72, Number 205)]
[Notices]
[Page 60360-60361]
[DOCID:fr24oc07-87]

-----------------------------------------------------------------------

ENVIRONMENTAL PROTECTION AGENCY

[EPA-HQ-OECA-2007-0046; FRL-8486-8]

Agency Information Collection Activities; Submission to OMB for
Review and Approval; Comment Request; NSPS for Small Industrial-
Commercial-Institutional Steam Generating Units (Renewal); EPA ICR
Number 1564.07, OMB Control Number 2060-0202

AGENCY: Environmental Protection Agency (EPA).

ACTION: Notice.

-----------------------------------------------------------------------

SUMMARY: In compliance with the Paperwork Reduction Act (44 U.S.C. 3501
et seq.), this document announces that an Information Collection
Request (ICR) has been forwarded to the Office of Management and Budget
(OMB) for review and approval. This is a request to renew an existing
approved collection. The ICR which is abstracted below describes the
nature of the collection and the estimated burden and cost.

DATES: Additional comments may be submitted on or before November 23,
2007.

ADDRESSES: Submit your comments, referencing docket ID number EPA-HQ-
OECA-2007-0046, to (1) EPA online using http://www.regulations.gov (our preferred method), or by e-mail to<EMAIL_ADDRESS>or by mail to:

EPA Docket Center (EPA/DC), Environmental Protection Agency,
Enforcement and Compliance Docket and Information Center, mail code
2201T, 1200 Pennsylvania Avenue, NW., Washington, DC 20460, and (2) OMB
at: Office of Information and Regulatory Affairs, Office of Management
and Budget (OMB), Attention: Desk Officer for EPA, 725 17th Street,
NW., Washington, DC 20503.

FOR FURTHER INFORMATION CONTACT: Learia Williams, Compliance Assessment
and Media Programs Division, Office of Compliance, Mail Code 2223A,
Environmental Protection Agency, 1200 Pennsylvania Avenue, NW.,
Washington, DC 20460; telephone number:<PHONE_NUMBER>; fax number:
(202) 564-0050; email address<EMAIL_ADDRESS>
SUPPLEMENTARY INFORMATION: EPA has submitted the following ICR to OMB
for review and approval according to the procedures prescribed in 5 CFR
1320.12. On March 9, 2007 (72 FR 10735), EPA sought comments on this
ICR pursuant to 5 CFR 1320.8(d). EPA received no comments. Any
additional comments on this ICR should be submitted to EPA and OMB
within 30 days of this notice.
    EPA has established a public docket for this ICR under docket ID
number EPA-HQ-OECA-2007-0046, which is available for public viewing
online at http://www.regulations.gov, or in person viewing at the

Enforcement and Compliance Docket and Information Center in the EPA
Docket Center (EPA/DC), EPA West, Room 3334, 1301 Constitution Avenue,
NW., Washington, DC. The EPA Docket Center Public Reading Room is open
from 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding legal
holidays. The telephone number for the Reading Room is<PHONE_NUMBER>,
and the telephone number for the Enforcement and Compliance Docket is
(202) 566-1752.
    Use EPA's electronic docket and comment system at http://www.regulations.gov
 to submit or view public comments, access the index

listing of the contents of the docket, and to access those documents in
the docket that are available electronically. Once in the system,
select ``docket search,'' then key in the docket ID number identified
above. Please note that EPA's policy is that public comments, whether
submitted electronically or in paper, will be made available for public
viewing at http://www.regulations.gov, as EPA receives them and without

change, unless the comment contains copyrighted material, Confidential
Business Information (CBI), or other information whose public
disclosure is restricted by statute. For further information about the
electronic docket, go to http://www.regulations.gov.

    Title: NSPS for Small Industrial-Commercial-Institutional Steam
Generating Units (Renewal).
    ICR Numbers: EPA ICR Number 1564.07, OMB Control Number 2060-0202.
    ICR Status: This ICR is scheduled to expire on November 30, 2007.
Under OMB regulations, the Agency may continue to conduct or sponsor
the collection of information while this submission is pending at OMB.
An Agency may not conduct or sponsor, and a person is not required to
respond to, a collection of information unless it displays a currently
valid OMB control number. The OMB control numbers for EPA's regulations
in title 40 of the CFR, after appearing in the Federal Register when
approved, are listed in 40 CFR part 9, and displayed either by
publication in the Federal Register or by other appropriate means, such
as on the related collection instrument or form, if applicable. The
display of OMB control numbers in certain EPA regulations is
consolidated in 40 CFR part 9.
    Abstract: The New Source Performance Standards (NSPS) for small
industrial-commercial-institutional steam generating units, published
at 40 CFR part 60, subpart Dc, were proposed on June 9, 1989, and
promulgated on September 12, 1990. These standards apply to industrial-
commercial-institutional steam generating units with maximum design
heat input capacity of 29 megawatts (MW) (100 million Btu/hr) or less,
but greater than or equal to 2.9 MW (10 million Btu/hr), commencing
construction, modification, or reconstruction after June 9, 1989. The
standards limit the emissions of sulfur dioxide (SO2) and
particulate matter (PM). For the purposes of this document, new units
are those affected units that have had construction, modification, or
reconstruction within the last three years. This information is being
collected to assure compliance with 40 CFR part 60, subpart Dc.
    In general, all NSPS standards require initial notifications,
performance tests, and periodic reports. Owners or operators are also
required to maintain records of the occurrence and duration of any
startup, shutdown, or malfunction in the operation of an affected
facility, or any period during which the monitoring system is
inoperative. These notifications, reports, and records are essential in
determining compliance and are required of all sources subject to NSPS.
    Any owner or operator subject to the provisions of this part shall
maintain a file of these measurements, and retain the file for at least
two years following the date of such measurements, maintenance reports,
and records. All reports are sent to the delegated state or local
authority. In the event that there is no such delegated authority, the
reports are sent directly to the EPA regional office. This information
is being collected to assure compliance with 40 CFR part 60, subpart
Dc, as authorized in section 112 and 114(a) of the Clean Air Act. The
required information consists of emissions data and other information
that have been determined to be private.
    An Agency may not conduct or sponsor, and a person is not required
to respond to, a collection of information unless it displays a
currently valid OMB Control Number. The OMB Control Number for EPA's
regulations are listed in 40 CFR part 9 and 48 CFR chapter 15, and are
identified on the form and/or instrument, if applicable.
    Burden Statement: The annual public reporting and recordkeeping
burden for this collection of information is

estimated to average 293 hours per response. Burden means the total
time, effort, or financial resources expended by persons to generate,
maintain, retain, or disclose or provide information to or for a
Federal agency. This includes the time needed to review instructions;
develop, acquire, install, and utilize technology and systems for the
purposes of collecting, validating, and verifying information,
processing and maintaining information, and disclosing and providing
information; adjust the existing ways to comply with any previously
applicable instructions and requirements which have subsequently
changed; train personnel to be able to respond to a collection of
information; search data sources; complete and review the collection of
information; and transmit or otherwise disclose the information.
    Respondents/Affected Entities: Small industrial-commercial-
institutional steam generating units.
    Estimated Number of Respondents: 235.
    Frequency of Response: Initially, on occasion, and semiannually.
    Estimated Total Annual Hour Burden: 159,972.
    Estimated Total Annual Cost: $19,653,054 which includes $1,491,005
annualized Capital Startup cost, $7,955,140 annualized Operating and
Maintenance (O&M) cost and $10,206,909 annual Labor Costs.
    Changes in the Estimates: There is no significant change in this
ICR compared to the previous ICR. This is due to two considerations.
First, the regulations have not changed over the past three years and
are not anticipated to change over the next three years. Secondly, the
growth rate for the industry is very low, negative or non-existent.
    There is, however, an adjustment in the labor hour estimate. The
previous ICR shows a total of 156,610 annual hours. This renewal ICR
shows a total of 159,972 annual hours. The small labor hour increase of
3,362 was caused by a mathematical error in the previous ICR.
    There is also a small change in the cost estimate. The previous ICR
used a cost figure that was rounded-up ($9,446,000). This ICR uses the
exact cost figure of ($9,446,145) resulting in a small cost increase of
$145.

    Dated: October 18, 2007.
Sara Hisel-McCoy,
Acting Director, Collection Strategies Division.
[FR Doc. E7-20938 Filed 10-23-07; 8:45 am]

BILLING CODE 6560-50-P