# Jessica Balukas, ICF, September 2021
# Script to process ORM data (2010-2019), calculate section 404 impacts with mitigation requirements and single-water permit counts for Rapanos, NWPR, and the change
# NOTE: TO ADJUST FOR DIFFERENT EMPLOYEE ID/FOLDER SYNCING, UPDATE CODE SIGNIFIED WITH #*# (search for combo to get all occurrences)
# NOTE: File paths assume syncing of entire WOTUS Reconsideration general folder

# Revised 07/28/2022 after realizing that the ORM dataset included 2020 and 2021 permits, added filter to remove
# Revised 08/19/2022 to output permit counts by HUC2 and Cowardin Code

# Install Packages
#install.packages("tidyverse")
#install.packages("stringr")

# Load Packages
library(tidyverse)
library(stringr)

# Folder locations
var <- "40179" #*#
IN_DIR <- (paste0("C:/Users/",var,"/ICF/WOTUS Reconsideration (ICF Internal Site) - General/ORM Data Processing/Inputs")) #*#
OUT_DIR <- (paste0("C:/Users/",var,"/ICF/WOTUS Reconsideration (ICF Internal Site) - General/ORM Data Processing/Outputs")) #*#
QA_DIR <- (paste0("C:/Users/",var,"/ICF/WOTUS Reconsideration (ICF Internal Site) - General/ORM Data Processing/Outputs/QA")) #*#

# Read input files
ORM_Dataset <- read.csv(file.path(IN_DIR,"ORM_Data_2010-2019_ReducedFields.csv"))
CWR_Filter <- read.csv(file.path(IN_DIR,"filter_for_CWR_ICF_Edits.csv"))
Perc_Permitted_Waters <- read.csv(file.path(IN_DIR,"Perc_Permitted_Waters.csv"))
HUC12 <- read.delim(file.path(IN_DIR,"ORMPermit_Georef_0907.txt"))
HUC12_AK <- read.delim(file.path(IN_DIR,"ORMPermit_AK_Georef_0907.txt"))
Prop_10YrPeriod_NonCWR <- read.csv(file.path(IN_DIR,"Proportion10YrPeriod_NonCWR.csv"))

# QA - HUC12 obs. lower than ORM_Dataset obs.
HUC12_ID <- HUC12[c("PERMIT_ID")]
HUC12_ID$HUC12_Flag <- 1
ID_test <- merge(x=ORM_Dataset,y=HUC12_ID,by="PERMIT_ID",all.x=TRUE)
ID_test_QA <- ID_test[is.na(ID_test$HUC12_Flag), ]
write.csv(ID_test_QA,paste(QA_DIR,"HUC12_MissingIDs.csv",sep="/"),row.names=FALSE)
rm(list = c('HUC12_ID','ID_test','ID_test_QA'))

# Ensure that HUC12 values are always 12 digits (add leading zeros when necessary), add HUC4 variable
names(HUC12)[names(HUC12) == "WBD_HUC12"] <- "HUC12_Main"
HUC12$HUC12 <- str_pad(HUC12$HUC12_Main,12, pad = "0")
HUC12$HUC4 <- substr(HUC12$HUC12,start=1,stop=4)

# Convert HUC12 and HUC4 variables to character
HUC12$HUC12 <- as.character(HUC12$HUC12)
HUC12$HUC4 <- as.character(HUC12$HUC4)

# Merge HUC12 to ORM_Dataset
HUC12 <- HUC12[c("PERMIT_ID", "HUC12", "HUC4", "STUSPS")]
ORM_Dataset_Final <- merge(x=ORM_Dataset,y=HUC12,by="PERMIT_ID",all.x=TRUE)

# Create combined STATE variable (prioritize spatial state, then STATE_AR, then STATE)
ORM_Dataset_Final$STATE_FINAL <- ifelse(ORM_Dataset_Final$STUSPS=='' | is.na(ORM_Dataset_Final$STUSPS),ORM_Dataset_Final$STATE_AR,ORM_Dataset_Final$STUSPS)
ORM_Dataset_Final$STATE_FINAL <- ifelse(ORM_Dataset_Final$STATE_FINAL=='' | is.na(ORM_Dataset_Final$STATE_FINAL),ORM_Dataset_Final$STATE,ORM_Dataset_Final$STATE_FINAL)

# Check for remaining missing values in STATE_FINAL variable
STATE_QA  <- ORM_Dataset_Final[ which(ORM_Dataset_Final$STATE_FINAL ==''), ]
write.csv(STATE_QA,paste(QA_DIR,"STATE_MISSING_2022.07.28.csv",sep="/"),row.names=FALSE)

# Merge HUC12_AK to ORM_Dataset_Final, replace HUC12 with AK value if STATE_FINAL=AK (Alaska HUC12 merge processed separately)
names(HUC12_AK)[names(HUC12_AK) == "WBD_HUC12"] <- "HUC12_AK"
HUC12_AK$HUC12_AK <- str_pad(HUC12_AK$HUC12_AK,12, pad = "0")
HUC12_AK$HUC4_AK <- substr(HUC12_AK$HUC12_AK,start=1,stop=4)
HUC12_AK$HUC12_AK <- as.character(HUC12_AK$HUC12_AK)
HUC12_AK$HUC4_AK <- as.character(HUC12_AK$HUC4_AK)
HUC12_AK <- HUC12_AK[c("PERMIT_ID", "HUC12_AK","HUC4_AK")]
ORM_Dataset_Final <- merge(x=ORM_Dataset_Final,y=HUC12_AK,by="PERMIT_ID",all.x=TRUE)
ORM_Dataset_Final$HUC12 <- ifelse(ORM_Dataset_Final$STATE_FINAL=='AK',ORM_Dataset_Final$HUC12_AK,ORM_Dataset_Final$HUC12)
ORM_Dataset_Final$HUC4 <- ifelse(ORM_Dataset_Final$STATE_FINAL=='AK',ORM_Dataset_Final$HUC4_AK,ORM_Dataset_Final$HUC4)

# QA - obs. with missing HUC12
HUC12_QA <- ORM_Dataset_Final[is.na(ORM_Dataset_Final$HUC12), ]
write.csv(HUC12_QA,paste(QA_DIR,"HUC12_MissingValue.csv",sep="/"),row.names=FALSE)
ORM_Dataset_Final[ ,c('HUC12_AK', 'HUC4_AK')] <- list(NULL)

### Merge remaining datasets to ORM_Dataset
# CWR Filter (to remove permits issued under Clean Water Rule Guidance)
CWR_Filter$State_Date <- paste(CWR_Filter$state,"_",CWR_Filter$END_DATE)
CWR_Filter <- CWR_Filter[c("State_Date","CWR")]
ORM_Dataset_Final$State_Date <- paste(ORM_Dataset_Final$STATE_FINAL,"_",ORM_Dataset_Final$END_DATE)
ORM_Dataset_Final <- merge(x=ORM_Dataset_Final,y=CWR_Filter,by="State_Date",all.x=TRUE)

# Check CWR Filter Merge
#write.csv(ORM_Dataset_Final,paste(QA_DIR,"CWR_Filter_Merge.csv",sep="/"),row.names=FALSE)
ORM_Dataset_Final$State_Date <- NULL

# Perc_Permitted_Waters (jurisdictional determination corrections)
ORM_Dataset_Final <- merge(x=ORM_Dataset_Final,y=Perc_Permitted_Waters,by="COWARDIN_FINAL",all.x=TRUE)
#write.csv(ORM_Dataset_Final,paste(QA_DIR,"Perc_Permitted_Waters_Merge.csv",sep="/"),row.names=FALSE)

# Prop_10YrPeriod_NonCWR
ORM_Dataset_Final <- merge(x=ORM_Dataset_Final,y=Prop_10YrPeriod_NonCWR,by="STATE_FINAL",all.x=TRUE)
#write.csv(ORM_Dataset_Final,paste(QA_DIR,"Prop_10YrPeriod_NonCWR_Merge.csv",sep="/"),row.names=FALSE)

# Drop intermediate datasets
rm(list = c('ORM_Dataset','CWR_Filter','Perc_Permitted_Waters','HUC12','HUC12_AK','HUC12_QA','Prop_10YrPeriod_NonCWR','STATE_QA'))

# Remove CWR permits and projects with a primarily mitigation-based purpose from analysis
ORM_Dataset_Final_NoCWR  <- ORM_Dataset_Final[ which(ORM_Dataset_Final$CWR==0), ]
ORM_Dataset_Final_NoCWRNoMit  <- ORM_Dataset_Final_NoCWR[ which(ORM_Dataset_Final_NoCWR$NonMitigation_Work_Type==1), ]

# Remove permits issued after 12/31/2019
RIGHT = function(x,n){
  substring(x,nchar(x)-n+1)
}
ORM_Dataset_Final_NoCWRNoMit$YEAR <- RIGHT(ORM_Dataset_Final_NoCWRNoMit$END_DATE, 4)
ORM_Dataset_Final_NoCWRNoMit$YEAR <- as.numeric(ORM_Dataset_Final_NoCWRNoMit$YEAR)
ORM_Dataset_Final_NoCWRNoMit  <- ORM_Dataset_Final_NoCWRNoMit[ which(ORM_Dataset_Final_NoCWRNoMit$YEAR<2020), ]
unique(ORM_Dataset_Final_NoCWRNoMit$YEAR)

# Drop intermediate ORM datasets
rm(list = c('ORM_Dataset_Final','ORM_Dataset_Final_NoCWR'))

# Create binary variable to indicate permit type (1=individual permt, 0=general permit)
ORM_Dataset_Final_NoCWRNoMit %>% count(ACTION_TYPE)
ORM_Dataset_Final_NoCWRNoMit$Ind_Permit <- ifelse(ORM_Dataset_Final_NoCWRNoMit$ACTION_TYPE=='LOP',1,
                                           ifelse(ORM_Dataset_Final_NoCWRNoMit$ACTION_TYPE=='SP',1,0))

# Create binary variables to indicate single water permits (1=single water affected, 0=multiple waters affected)
PermitID_Count <- ORM_Dataset_Final_NoCWRNoMit %>% count(PERMIT_ID2)
ORM_Dataset_Final_NoCWRNoMit <- merge(x=ORM_Dataset_Final_NoCWRNoMit,y=PermitID_Count,by="PERMIT_ID2",all.x=TRUE)
rm(list = c('ORM_Dataset_Final','ORM_Dataset_Final_NoCWR','PermitID_Count'))
ORM_Dataset_Final_NoCWRNoMit$SingleWater <- ifelse(ORM_Dataset_Final_NoCWRNoMit$n>1,0,1)
ORM_Dataset_Final_NoCWRNoMit$n <- NULL

# Create SI, SG, MI, MG binary variables (described on EPA's technical direction)
ORM_Dataset_Final_NoCWRNoMit$SI <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Ind_Permit==1 & ORM_Dataset_Final_NoCWRNoMit$SingleWater==1,1,0)
ORM_Dataset_Final_NoCWRNoMit$SG <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Ind_Permit==0 & ORM_Dataset_Final_NoCWRNoMit$SingleWater==1,1,0)
ORM_Dataset_Final_NoCWRNoMit$MI <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Ind_Permit==1 & ORM_Dataset_Final_NoCWRNoMit$SingleWater==0,1,0)
ORM_Dataset_Final_NoCWRNoMit$MG <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Ind_Permit==0 & ORM_Dataset_Final_NoCWRNoMit$SingleWater==0,1,0)

# Calculate SI, SG, MI, MG percentages by HUC4/COWARDIN_FINAL (divide by # affected waters)
# Determine unique number of permits by HUC4/COWARDIN_FINAL for later permit analysis
count_SI_SG_MI_MG <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(HUC4,COWARDIN_FINAL) %>%
  summarise(Permit_Count = n_distinct(PERMIT_ID2),
            Waters_Count = n(),
            SI_Count = sum(SI),
            SG_Count = sum(SG),
            MI_Count = sum(MI),
            MG_Count = sum(MG)) %>%
  mutate(SI_Perc = SI_Count/Waters_Count,
         SG_Perc = SG_Count/Waters_Count,
         MI_Perc = MI_Count/Waters_Count,
         MG_Perc = MG_Count/Waters_Count)
count_SI_SG_MI_MG$HUC4_COWARDIN <- paste(count_SI_SG_MI_MG$HUC4,"_",count_SI_SG_MI_MG$COWARDIN_FINAL)

count_SI_SG_MI_MG_2 <- count_SI_SG_MI_MG[c("HUC4_COWARDIN","Permit_Count","SI_Perc","SG_Perc","MI_Perc","MG_Perc")]

# Merge SI, SG, MI, MG percentages with ORM_Dataset_Final_NoCWRNoMit dataset
ORM_Dataset_Final_NoCWRNoMit$HUC4_COWARDIN <- paste(ORM_Dataset_Final_NoCWRNoMit$HUC4,"_",ORM_Dataset_Final_NoCWRNoMit$COWARDIN_FINAL)
ORM_Dataset_Final_NoCWRNoMit <- merge(x=ORM_Dataset_Final_NoCWRNoMit,y=count_SI_SG_MI_MG_2,by="HUC4_COWARDIN",all.x=TRUE)
rm(list = c('count_SI_SG_MI_MG','count_SI_SG_MI_MG_2'))

# Create dummy variable for mitigation (1=mitigation required, 0=mitigation NOT required)
ORM_Dataset_Final_NoCWRNoMit$MitReq <- ifelse(ORM_Dataset_Final_NoCWRNoMit$MITIGATION_TYPES!='',1,0)

# Create dummy variables for permanent and temporary impacts (1=has impacts, 0=no impacts)
ORM_Dataset_Final_NoCWRNoMit$Perm_Impact <- ifelse(ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_PERM>0 | ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_PERM>0,1,0)
ORM_Dataset_Final_NoCWRNoMit$Temp_Impact <- ifelse(ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_TEMP>0 | ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_TEMP>0,1,0)
ORM_Dataset_Final_NoCWRNoMit$PermTemp_Impact <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Perm_Impact==1 | ORM_Dataset_Final_NoCWRNoMit$Temp_Impact==1,1,0)
ORM_Dataset_Final_NoCWRNoMit$Perm_Impact <- ifelse(is.na(ORM_Dataset_Final_NoCWRNoMit$Perm_Impact),0,ORM_Dataset_Final_NoCWRNoMit$Perm_Impact)
ORM_Dataset_Final_NoCWRNoMit$Temp_Impact <- ifelse(is.na(ORM_Dataset_Final_NoCWRNoMit$Temp_Impact),0,ORM_Dataset_Final_NoCWRNoMit$Temp_Impact)
ORM_Dataset_Final_NoCWRNoMit$PermTemp_Impact <- ifelse(is.na(ORM_Dataset_Final_NoCWRNoMit$PermTemp_Impact),0,ORM_Dataset_Final_NoCWRNoMit$PermTemp_Impact)
write.csv(ORM_Dataset_Final_NoCWRNoMit,paste(QA_DIR,"PermTempImpactDummies.csv",sep="/"),row.names=FALSE)

# Create PM, TM, PN, TN binary variables (described on EPA's technical direction)
ORM_Dataset_Final_NoCWRNoMit$PM <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Perm_Impact==1 & ORM_Dataset_Final_NoCWRNoMit$MitReq==1,1,0)
ORM_Dataset_Final_NoCWRNoMit$TM <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Temp_Impact==1 & ORM_Dataset_Final_NoCWRNoMit$MitReq==1,1,0)
ORM_Dataset_Final_NoCWRNoMit$PN <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Perm_Impact==1 & ORM_Dataset_Final_NoCWRNoMit$MitReq==0,1,0)
ORM_Dataset_Final_NoCWRNoMit$TN <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Temp_Impact==1 & ORM_Dataset_Final_NoCWRNoMit$MitReq==0,1,0)
write.csv(ORM_Dataset_Final_NoCWRNoMit,paste(QA_DIR,"PM_TM_PN_TN.csv",sep="/"),row.names=FALSE)

# Calculate PM, TM, PN, TN percentages by HUC4/COWARDIN_FINAL (divide by # affected waters)
count_PM_TM_PN_TN <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(HUC4,COWARDIN_FINAL) %>%
  summarise(Waters_Count = n(),
            PM_Count = sum(PM),
            TM_Count = sum(TM),
            PN_Count = sum(PN),
            TN_Count = sum(TN)) %>%
  mutate(PM_Perc = PM_Count/Waters_Count,
         TM_Perc = TM_Count/Waters_Count,
         PN_Perc = PN_Count/Waters_Count,
         TN_Perc = TN_Count/Waters_Count)
count_PM_TM_PN_TN$HUC4_COWARDIN <- paste(count_PM_TM_PN_TN$HUC4,"_",count_PM_TM_PN_TN$COWARDIN_FINAL)

count_PM_TM_PN_TN_2 <- count_PM_TM_PN_TN[c("HUC4_COWARDIN","Waters_Count","PM_Perc","TM_Perc","PN_Perc","TN_Perc")]

# Merge PM, TM, PN, TN percentages with ORM_Dataset_Final_NoCWRNoMit dataset
ORM_Dataset_Final_NoCWRNoMit <- merge(x=ORM_Dataset_Final_NoCWRNoMit,y=count_PM_TM_PN_TN_2,by="HUC4_COWARDIN",all.x=TRUE)
rm(list = c('count_PM_TM_PN_TN','count_PM_TM_PN_TN_2'))

# Convert LF (permanent & temporary) to acres, using average buffer width of 50 ft. (25 ft. on each side of the stream)
ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_PERM_ACRE_CONV <- ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_PERM*50*0.0000229568
ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_TEMP_ACRE_CONV <- ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_TEMP*50*0.0000229568

# Calculate total permanent and temporary impacts (acres + LF converted to acres)
ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_PERM <- ifelse(is.na(ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_PERM),0,ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_PERM)
ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_PERM_ACRE_CONV <- ifelse(is.na(ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_PERM_ACRE_CONV),0,ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_PERM_ACRE_CONV)
ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_PERM_TOTAL <- ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_PERM+ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_PERM_ACRE_CONV

ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_TEMP <- ifelse(is.na(ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_TEMP),0,ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_TEMP)
ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_TEMP_ACRE_CONV <- ifelse(is.na(ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_TEMP_ACRE_CONV),0,ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_TEMP_ACRE_CONV)
ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_TEMP_TOTAL <- ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_TEMP+ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_TEMP_ACRE_CONV

################################################################
#Calculate impacts not covered by a permit under Rapanos & NWPR
################################################################

# Remove observations with HIST1, missing COWARDIN_FINAL, or missing HUC12
ORM_Dataset_Final_NoCWRNoMit  <- ORM_Dataset_Final_NoCWRNoMit[ which(ORM_Dataset_Final_NoCWRNoMit$COWARDIN_FINAL != "HIST1"), ]
ORM_Dataset_Final_NoCWRNoMit  <- ORM_Dataset_Final_NoCWRNoMit[ which(ORM_Dataset_Final_NoCWRNoMit$COWARDIN_FINAL != ''), ]
ORM_Dataset_Final_NoCWRNoMit <- ORM_Dataset_Final_NoCWRNoMit[!(is.na(ORM_Dataset_Final_NoCWRNoMit$HUC12)), ]

# Multiply impacts by Cowardin Code-level Rapanos and NWPR adjustments (to account for impacts not covered under Rapanos vs. NWPR)
# Multiply Rapanos/NWPR-corrected impacts by HUC4/Cowardin Code mitigation percentages (PM_Perc & TM_Perc)
# Divide Rapanos/NWPR- & PM/TM-corrected impacts by proportion of 10-year period that state followed Rapanos to get annual average
# Use the same methodology to count impacted waters not covered under Rapanos vs. NWPR
ORM_Dataset_Final_NoCWRNoMit <- ORM_Dataset_Final_NoCWRNoMit %>%
  mutate(IMPACT_AUTH_ACRES_PERM_PM_Rapanos_10Yr = (((IMPACT_AUTH_ACRES_PERM/Rapanos_Perc_Permitted)-IMPACT_AUTH_ACRES_PERM)*PM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_Rapanos_10Yr = (((IMPACT_AUTH_LF_PERM_ACRE_CONV/Rapanos_Perc_Permitted)-IMPACT_AUTH_LF_PERM_ACRE_CONV)*PM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_PERM_TOTAL_PM_Rapanos_10Yr = (((IMPACT_AUTH_PERM_TOTAL/Rapanos_Perc_Permitted)-IMPACT_AUTH_PERM_TOTAL)*PM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_ACRES_TEMP_TM_Rapanos_10Yr = (((IMPACT_AUTH_ACRES_TEMP/Rapanos_Perc_Permitted)-IMPACT_AUTH_ACRES_TEMP)*TM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_Rapanos_10Yr = (((IMPACT_AUTH_LF_TEMP_ACRE_CONV/Rapanos_Perc_Permitted)-IMPACT_AUTH_LF_TEMP_ACRE_CONV)*TM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_TEMP_TOTAL_TM_Rapanos_10Yr = (((IMPACT_AUTH_TEMP_TOTAL/Rapanos_Perc_Permitted)-IMPACT_AUTH_TEMP_TOTAL)*TM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_ACRES_PERM_PM_NWPR_10Yr = (((IMPACT_AUTH_ACRES_PERM/Rapanos_Perc_Permitted)-(IMPACT_AUTH_ACRES_PERM/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)*PM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_NWPR_10Yr = (((IMPACT_AUTH_LF_PERM_ACRE_CONV/Rapanos_Perc_Permitted)-(IMPACT_AUTH_LF_PERM_ACRE_CONV/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)*PM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_PERM_TOTAL_PM_NWPR_10Yr = (((IMPACT_AUTH_PERM_TOTAL/Rapanos_Perc_Permitted)-(IMPACT_AUTH_PERM_TOTAL/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)*PM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_ACRES_TEMP_TM_NWPR_10Yr = (((IMPACT_AUTH_ACRES_TEMP/Rapanos_Perc_Permitted)-(IMPACT_AUTH_ACRES_TEMP/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)*TM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_NWPR_10Yr = (((IMPACT_AUTH_LF_TEMP_ACRE_CONV/Rapanos_Perc_Permitted)-(IMPACT_AUTH_LF_TEMP_ACRE_CONV/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)*TM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_TEMP_TOTAL_TM_NWPR_10Yr = (((IMPACT_AUTH_TEMP_TOTAL/Rapanos_Perc_Permitted)-(IMPACT_AUTH_TEMP_TOTAL/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)*TM_Perc)/Prop_10YrPeriod_NonCWR,
         PERM_Count_Rapanos_10Yr = ((Perm_Impact/Rapanos_Perc_Permitted)-Perm_Impact)/Prop_10YrPeriod_NonCWR,
         PERM_Count_NWPR_10Yr = ((Perm_Impact/Rapanos_Perc_Permitted)-(Perm_Impact/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)/Prop_10YrPeriod_NonCWR,
         PERM_Count_Change_10Yr = (Perm_Impact-(Perm_Impact*(NWPR_Perc_Permitted/Rapanos_Perc_Permitted)))/Prop_10YrPeriod_NonCWR,
         TEMP_Count_Rapanos_10Yr = ((Temp_Impact/Rapanos_Perc_Permitted)-Temp_Impact)/Prop_10YrPeriod_NonCWR,
         TEMP_Count_NWPR_10Yr = ((Temp_Impact/Rapanos_Perc_Permitted)-(Temp_Impact/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)/Prop_10YrPeriod_NonCWR,
         TEMP_Count_Change_10Yr = (Temp_Impact-(Temp_Impact*(NWPR_Perc_Permitted/Rapanos_Perc_Permitted)))/Prop_10YrPeriod_NonCWR,
         ImpactedWater_Count_Rapanos_10Yr = ((PermTemp_Impact/Rapanos_Perc_Permitted)-PermTemp_Impact)/Prop_10YrPeriod_NonCWR,
         ImpactedWater_Count_NWPR_10Yr = ((PermTemp_Impact/Rapanos_Perc_Permitted)-(PermTemp_Impact/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)/Prop_10YrPeriod_NonCWR,
         ImpactedWater_Count_Change_10Yr = (PermTemp_Impact-(PermTemp_Impact*(NWPR_Perc_Permitted/Rapanos_Perc_Permitted)))/Prop_10YrPeriod_NonCWR)

# Aggregate permanent & temporary impacts at the HUC12 level
Impacts_HUC12 <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(HUC12) %>%
  summarise(PERM_ACRES_Rapanos = sum(IMPACT_AUTH_ACRES_PERM_PM_Rapanos_10Yr),
            PERM_LF_ACRE_CONV_Rapanos = sum(IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_Rapanos_10Yr),
            PERM_TOTAL_Rapanos = sum(IMPACT_AUTH_PERM_TOTAL_PM_Rapanos_10Yr),
            TEMP_ACRES_Rapanos = sum(IMPACT_AUTH_ACRES_TEMP_TM_Rapanos_10Yr),
            TEMP_LF_ACRE_CONV_Rapanos = sum(IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_Rapanos_10Yr),
            TEMP_TOTAL_Rapanos = sum(IMPACT_AUTH_TEMP_TOTAL_TM_Rapanos_10Yr),
            PERM_ACRES_NWPR = sum(IMPACT_AUTH_ACRES_PERM_PM_NWPR_10Yr),
            PERM_LF_ACRE_CONV_NWPR = sum(IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_NWPR_10Yr),
            PERM_TOTAL_NWPR = sum(IMPACT_AUTH_PERM_TOTAL_PM_NWPR_10Yr),
            TEMP_ACRES_NWPR = sum(IMPACT_AUTH_ACRES_TEMP_TM_NWPR_10Yr),
            TEMP_LF_ACRE_CONV_NWPR = sum(IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_NWPR_10Yr),
            TEMP_TOTAL_NWPR = sum(IMPACT_AUTH_TEMP_TOTAL_TM_NWPR_10Yr)) %>%
  mutate(PERM_ACRES_CHANGE = PERM_ACRES_Rapanos - PERM_ACRES_NWPR,
         PERM_LF_ACRE_CONV_CHANGE = PERM_LF_ACRE_CONV_Rapanos - PERM_LF_ACRE_CONV_NWPR,
         PERM_TOTAL_CHANGE = PERM_TOTAL_Rapanos - PERM_TOTAL_NWPR,
         TEMP_ACRES_CHANGE = TEMP_ACRES_Rapanos - TEMP_ACRES_NWPR,
         TEMP_LF_ACRE_CONV_CHANGE = TEMP_LF_ACRE_CONV_Rapanos - TEMP_LF_ACRE_CONV_NWPR,
         TEMP_TOTAL_CHANGE = TEMP_TOTAL_Rapanos - TEMP_TOTAL_NWPR)
write.csv(Impacts_HUC12,paste(OUT_DIR,"Impacts_By_HUC12_2022.07.28.csv",sep="/"),row.names=FALSE)

# Aggregate permanent & temporary impacts at the HUC4 level
Impacts_HUC4 <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(HUC4) %>%
  summarise(PERM_ACRES_Rapanos = sum(IMPACT_AUTH_ACRES_PERM_PM_Rapanos_10Yr),
            PERM_LF_ACRE_CONV_Rapanos = sum(IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_Rapanos_10Yr),
            PERM_TOTAL_Rapanos = sum(IMPACT_AUTH_PERM_TOTAL_PM_Rapanos_10Yr),
            TEMP_ACRES_Rapanos = sum(IMPACT_AUTH_ACRES_TEMP_TM_Rapanos_10Yr),
            TEMP_LF_ACRE_CONV_Rapanos = sum(IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_Rapanos_10Yr),
            TEMP_TOTAL_Rapanos = sum(IMPACT_AUTH_TEMP_TOTAL_TM_Rapanos_10Yr),
            PERM_ACRES_NWPR = sum(IMPACT_AUTH_ACRES_PERM_PM_NWPR_10Yr),
            PERM_LF_ACRE_CONV_NWPR = sum(IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_NWPR_10Yr),
            PERM_TOTAL_NWPR = sum(IMPACT_AUTH_PERM_TOTAL_PM_NWPR_10Yr),
            TEMP_ACRES_NWPR = sum(IMPACT_AUTH_ACRES_TEMP_TM_NWPR_10Yr),
            TEMP_LF_ACRE_CONV_NWPR = sum(IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_NWPR_10Yr),
            TEMP_TOTAL_NWPR = sum(IMPACT_AUTH_TEMP_TOTAL_TM_NWPR_10Yr)) %>%
  mutate(PERM_ACRES_CHANGE = PERM_ACRES_Rapanos - PERM_ACRES_NWPR,
         PERM_LF_ACRE_CONV_CHANGE = PERM_LF_ACRE_CONV_Rapanos - PERM_LF_ACRE_CONV_NWPR,
         PERM_TOTAL_CHANGE = PERM_TOTAL_Rapanos - PERM_TOTAL_NWPR,
         TEMP_ACRES_CHANGE = TEMP_ACRES_Rapanos - TEMP_ACRES_NWPR,
         TEMP_LF_ACRE_CONV_CHANGE = TEMP_LF_ACRE_CONV_Rapanos - TEMP_LF_ACRE_CONV_NWPR,
         TEMP_TOTAL_CHANGE = TEMP_TOTAL_Rapanos - TEMP_TOTAL_NWPR)
write.csv(Impacts_HUC4,paste(OUT_DIR,"Impacts_By_HUC4_2022.07.28.csv",sep="/"),row.names=FALSE)

# Aggregate permanent & temporary impacts at the STATE_FINAL level
Impacts_STATE <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(STATE_FINAL) %>%
  summarise(PERM_ACRES_Rapanos = sum(IMPACT_AUTH_ACRES_PERM_PM_Rapanos_10Yr),
            PERM_LF_ACRE_CONV_Rapanos = sum(IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_Rapanos_10Yr),
            PERM_TOTAL_Rapanos = sum(IMPACT_AUTH_PERM_TOTAL_PM_Rapanos_10Yr),
            TEMP_ACRES_Rapanos = sum(IMPACT_AUTH_ACRES_TEMP_TM_Rapanos_10Yr),
            TEMP_LF_ACRE_CONV_Rapanos = sum(IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_Rapanos_10Yr),
            TEMP_TOTAL_Rapanos = sum(IMPACT_AUTH_TEMP_TOTAL_TM_Rapanos_10Yr),
            PERM_ACRES_NWPR = sum(IMPACT_AUTH_ACRES_PERM_PM_NWPR_10Yr),
            PERM_LF_ACRE_CONV_NWPR = sum(IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_NWPR_10Yr),
            PERM_TOTAL_NWPR = sum(IMPACT_AUTH_PERM_TOTAL_PM_NWPR_10Yr),
            TEMP_ACRES_NWPR = sum(IMPACT_AUTH_ACRES_TEMP_TM_NWPR_10Yr),
            TEMP_LF_ACRE_CONV_NWPR = sum(IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_NWPR_10Yr),
            TEMP_TOTAL_NWPR = sum(IMPACT_AUTH_TEMP_TOTAL_TM_NWPR_10Yr)) %>%
  mutate(PERM_ACRES_CHANGE = PERM_ACRES_Rapanos - PERM_ACRES_NWPR,
         PERM_LF_ACRE_CONV_CHANGE = PERM_LF_ACRE_CONV_Rapanos - PERM_LF_ACRE_CONV_NWPR,
         PERM_TOTAL_CHANGE = PERM_TOTAL_Rapanos - PERM_TOTAL_NWPR,
         TEMP_ACRES_CHANGE = TEMP_ACRES_Rapanos - TEMP_ACRES_NWPR,
         TEMP_LF_ACRE_CONV_CHANGE = TEMP_LF_ACRE_CONV_Rapanos - TEMP_LF_ACRE_CONV_NWPR,
         TEMP_TOTAL_CHANGE = TEMP_TOTAL_Rapanos - TEMP_TOTAL_NWPR)
write.csv(Impacts_STATE,paste(OUT_DIR,"Impacts_By_STATE_2022.07.28.csv",sep="/"),row.names=FALSE)

# Aggregate permanent & temporary impacts at the Cowardin Code level
Impacts_Cowardin <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(COWARDIN_FINAL) %>%
  summarise(PERM_ACRES_Rapanos = sum(IMPACT_AUTH_ACRES_PERM_PM_Rapanos_10Yr),
            PERM_LF_ACRE_CONV_Rapanos = sum(IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_Rapanos_10Yr),
            PERM_TOTAL_Rapanos = sum(IMPACT_AUTH_PERM_TOTAL_PM_Rapanos_10Yr),
            TEMP_ACRES_Rapanos = sum(IMPACT_AUTH_ACRES_TEMP_TM_Rapanos_10Yr),
            TEMP_LF_ACRE_CONV_Rapanos = sum(IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_Rapanos_10Yr),
            TEMP_TOTAL_Rapanos = sum(IMPACT_AUTH_TEMP_TOTAL_TM_Rapanos_10Yr),
            PERM_ACRES_NWPR = sum(IMPACT_AUTH_ACRES_PERM_PM_NWPR_10Yr),
            PERM_LF_ACRE_CONV_NWPR = sum(IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_NWPR_10Yr),
            PERM_TOTAL_NWPR = sum(IMPACT_AUTH_PERM_TOTAL_PM_NWPR_10Yr),
            TEMP_ACRES_NWPR = sum(IMPACT_AUTH_ACRES_TEMP_TM_NWPR_10Yr),
            TEMP_LF_ACRE_CONV_NWPR = sum(IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_NWPR_10Yr),
            TEMP_TOTAL_NWPR = sum(IMPACT_AUTH_TEMP_TOTAL_TM_NWPR_10Yr)) %>%
  mutate(PERM_ACRES_CHANGE = PERM_ACRES_Rapanos - PERM_ACRES_NWPR,
         PERM_LF_ACRE_CONV_CHANGE = PERM_LF_ACRE_CONV_Rapanos - PERM_LF_ACRE_CONV_NWPR,
         PERM_TOTAL_CHANGE = PERM_TOTAL_Rapanos - PERM_TOTAL_NWPR,
         TEMP_ACRES_CHANGE = TEMP_ACRES_Rapanos - TEMP_ACRES_NWPR,
         TEMP_LF_ACRE_CONV_CHANGE = TEMP_LF_ACRE_CONV_Rapanos - TEMP_LF_ACRE_CONV_NWPR,
         TEMP_TOTAL_CHANGE = TEMP_TOTAL_Rapanos - TEMP_TOTAL_NWPR)
write.csv(Impacts_Cowardin,paste(OUT_DIR,"Impacts_By_Cowardin_2022.07.28.csv",sep="/"),row.names=FALSE)

#################################################################################
#Calculate count of impacted waters not covered by a permit under Rapanos & NWPR
#################################################################################

# Aggregate permanent & temporary impacts at the HUC12 level
ImpactedWaters_HUC12 <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(HUC12) %>%
  summarise(Waters_Count_PERM_Rapanos = sum(PERM_Count_Rapanos_10Yr),
            Waters_Count_PERM_NWPR = sum(PERM_Count_NWPR_10Yr),
            Waters_Count_PERM_Change = sum(PERM_Count_Change_10Yr),
            Waters_Count_TEMP_Rapanos = sum(TEMP_Count_Rapanos_10Yr),
            Waters_Count_TEMP_NWPR = sum(TEMP_Count_NWPR_10Yr),
            Waters_Count_TEMP_Change = sum(TEMP_Count_Change_10Yr),
            Waters_Count_Rapanos = sum(ImpactedWater_Count_Rapanos_10Yr),
            Waters_Count_NWPR = sum(ImpactedWater_Count_NWPR_10Yr),
            Waters_Count_Change = sum(ImpactedWater_Count_Change_10Yr))
write.csv(ImpactedWaters_HUC12,paste(OUT_DIR,"ImpactedWaters_By_HUC12_2022.07.28.csv",sep="/"),row.names=FALSE)

# Aggregate permanent & temporary impacts at the HUC4 level
ImpactedWaters_HUC4 <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(HUC4) %>%
  summarise(Waters_Count_PERM_Rapanos = sum(PERM_Count_Rapanos_10Yr),
            Waters_Count_PERM_NWPR = sum(PERM_Count_NWPR_10Yr),
            Waters_Count_PERM_Change = sum(PERM_Count_Change_10Yr),
            Waters_Count_TEMP_Rapanos = sum(TEMP_Count_Rapanos_10Yr),
            Waters_Count_TEMP_NWPR = sum(TEMP_Count_NWPR_10Yr),
            Waters_Count_TEMP_Change = sum(TEMP_Count_Change_10Yr),
            Waters_Count_Rapanos = sum(ImpactedWater_Count_Rapanos_10Yr),
            Waters_Count_NWPR = sum(ImpactedWater_Count_NWPR_10Yr),
            Waters_Count_Change = sum(ImpactedWater_Count_Change_10Yr))
write.csv(ImpactedWaters_HUC4,paste(OUT_DIR,"ImpactedWaters_By_HUC4_2022.07.28.csv",sep="/"),row.names=FALSE)

# Aggregate permanent & temporary impacts at the STATE_FINAL level
ImpactedWaters_STATE <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(STATE_FINAL) %>%
  summarise(Waters_Count_PERM_Rapanos = sum(PERM_Count_Rapanos_10Yr),
            Waters_Count_PERM_NWPR = sum(PERM_Count_NWPR_10Yr),
            Waters_Count_PERM_Change = sum(PERM_Count_Change_10Yr),
            Waters_Count_TEMP_Rapanos = sum(TEMP_Count_Rapanos_10Yr),
            Waters_Count_TEMP_NWPR = sum(TEMP_Count_NWPR_10Yr),
            Waters_Count_TEMP_Change = sum(TEMP_Count_Change_10Yr),
            Waters_Count_Rapanos = sum(ImpactedWater_Count_Rapanos_10Yr),
            Waters_Count_NWPR = sum(ImpactedWater_Count_NWPR_10Yr),
            Waters_Count_Change = sum(ImpactedWater_Count_Change_10Yr))
write.csv(ImpactedWaters_STATE,paste(OUT_DIR,"ImpactedWaters_By_STATE_2022.07.28.csv",sep="/"),row.names=FALSE)

# Aggregate permanent & temporary impacts at the Cowardin Code level
ImpactedWaters_Cowardin <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(COWARDIN_FINAL) %>%
  summarise(Waters_Count_PERM_Rapanos = sum(PERM_Count_Rapanos_10Yr),
            Waters_Count_PERM_NWPR = sum(PERM_Count_NWPR_10Yr),
            Waters_Count_PERM_Change = sum(PERM_Count_Change_10Yr),
            Waters_Count_TEMP_Rapanos = sum(TEMP_Count_Rapanos_10Yr),
            Waters_Count_TEMP_NWPR = sum(TEMP_Count_NWPR_10Yr),
            Waters_Count_TEMP_Change = sum(TEMP_Count_Change_10Yr),
            Waters_Count_Rapanos = sum(ImpactedWater_Count_Rapanos_10Yr),
            Waters_Count_NWPR = sum(ImpactedWater_Count_NWPR_10Yr),
            Waters_Count_Change = sum(ImpactedWater_Count_Change_10Yr))
write.csv(ImpactedWaters_Cowardin,paste(OUT_DIR,"ImpactedWaters_By_Cowardin_2022.07.28.csv",sep="/"),row.names=FALSE)

####################################
#Calculate changes in permit counts
####################################

# Multiply Permit_Count by Cowardin Code-level (Rapanos_Perc - NWPR_Perc) adjustment (to calculate change in number of permits issued between the two scenarios)
# Multiply Permit_Count by SI_Perc and SG_Perc (calculate average number of Ind/Gen permits affecting one water at the HUC4/Cowardin Code level)
# Divide SI/SG- & Rapanos/NWPR-corrected Permit_Count by proportion of 10-year period that state followed Rapanos to get annual average
ORM_Dataset_Final_NoCWRNoMit <- ORM_Dataset_Final_NoCWRNoMit %>%
  mutate(Avg_SI_Count = (Permit_Count*SI_Perc*(Rapanos_Perc_Permitted-NWPR_Perc_Permitted))/Prop_10YrPeriod_NonCWR,
         Avg_SG_Count = (Permit_Count*SG_Perc*(Rapanos_Perc_Permitted-NWPR_Perc_Permitted))/Prop_10YrPeriod_NonCWR)

write.csv(ORM_Dataset_Final_NoCWRNoMit,paste(QA_DIR,"ORM_Dataset_Final_2022.07.28.csv",sep="/"),row.names=FALSE)

# Subset dataset to retain permits affecting single waters only (permits affecting multiple waters will still need to be permitted)
Permit_Counts  <- ORM_Dataset_Final_NoCWRNoMit[ which(ORM_Dataset_Final_NoCWRNoMit$SingleWater==1), ]

# Subset dataset, count number of permits per HUC4/COWARDIN and HUC4/COWARDIN/STATE combo, merge with permit counts
Permit_Counts <- Permit_Counts[c("HUC4_COWARDIN","HUC4","STATE_FINAL","Avg_SI_Count","Avg_SG_Count")]
Permit_Counts$HUC4_COWARDIN_STATE <- paste(Permit_Counts$HUC4_COWARDIN,"_",Permit_Counts$STATE_FINAL)

Permit_Counts_HUC4_COWARDIN <- Permit_Counts %>%
  group_by(HUC4_COWARDIN) %>%
  summarise(Permit_Count_HUC4_COWARDIN = n())

Permit_Counts_HUC4_COWARDIN_STATE <- Permit_Counts %>%
  group_by(HUC4_COWARDIN_STATE) %>%
  summarise(Permit_Count_HUC4_COWARDIN_STATE = n())

Permit_Counts <- merge(x=Permit_Counts,y=Permit_Counts_HUC4_COWARDIN,by="HUC4_COWARDIN",all.x=TRUE)
Permit_Counts <- merge(x=Permit_Counts,y=Permit_Counts_HUC4_COWARDIN_STATE,by="HUC4_COWARDIN_STATE",all.x=TRUE)

# Weight adjust permit counts based on HUC4/COWARDIN/STATE divided by HUC4/COWARDIN
Permit_Counts <- Permit_Counts %>%
  mutate(Avg_SI_Count_Adj = Avg_SI_Count * (Permit_Count_HUC4_COWARDIN_STATE/Permit_Count_HUC4_COWARDIN),
         Avg_SG_Count_Adj = Avg_SG_Count * (Permit_Count_HUC4_COWARDIN_STATE/Permit_Count_HUC4_COWARDIN))

# Subset by unique HUC4/COWARDIN/STATE
Permit_Counts2 <- Permit_Counts[!duplicated(Permit_Counts[,c("HUC4_COWARDIN_STATE")]),]
write.csv(Permit_Counts2,paste(QA_DIR,"PermitCounts_QA_2022.07.28.csv",sep="/"),row.names=FALSE)
rm(list = c('Permit_Counts','Permit_Counts_HUC4_COWARDIN','Permit_Counts_HUC4_COWARDIN_STATE'))

# Calculate change in average number of permits at the HUC4 level
Permits_HUC4 <- Permit_Counts2 %>%
  group_by(HUC4) %>%
  summarise(Avg_SI_Count = sum(Avg_SI_Count_Adj),
            Avg_SG_Count = sum(Avg_SG_Count_Adj))
write.csv(Permits_HUC4,paste(OUT_DIR,"PermitCounts_By_HUC4_2022.07.28.csv",sep="/"),row.names=FALSE)

# Calculate change in average number of permits at the HUC2/Cowardin Code level
Permit_Counts2$HUC2 <- substr(Permit_Counts2$HUC4,start=1,stop=2)
Permit_Counts2$COWARDIN <- substring(Permit_Counts2$HUC4_COWARDIN, 8)
Permits_HUC2_Cowardin <- Permit_Counts2 %>%
  group_by(HUC2,COWARDIN) %>%
  summarise(Avg_SI_Count = sum(Avg_SI_Count_Adj),
            Avg_SG_Count = sum(Avg_SG_Count_Adj))
write.csv(Permits_HUC2_Cowardin,paste(OUT_DIR,"PermitCounts_By_HUC2_Cowardin_2022.08.18.csv",sep="/"),row.names=FALSE)

# Calculate change in average number of permits at the state level
Permits_State <- Permit_Counts2 %>%
  group_by(STATE_FINAL) %>%
  summarise(Avg_SI_Count = sum(Avg_SI_Count_Adj),
            Avg_SG_Count = sum(Avg_SG_Count_Adj))
write.csv(Permits_State,paste(OUT_DIR,"PermitCounts_By_State_2022.07.28.csv",sep="/"),row.names=FALSE)


[Federal Register Volume 84, Number 79 (Wednesday, April 24, 2019)]
[Notices]
[Pages 17234-17239]
[FR Doc No: 2019-08171]

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

DEPARTMENT OF TRANSPORTATION

National Highway Traffic Safety Administration

[Docket No. DOT-OST-2019-0057]

Privacy Act of 1974; Department of Transportation, National
Highway Traffic Safety Administration; DOT/NHTSA-415; Vehicle Owner
Questionnaire (VOQ) System

AGENCY: National Highway Traffic Safety Administration, Department of
Transportation.

ACTION: Notice of a modified system of records.

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

SUMMARY: In accordance with the Privacy Act of 1974, the National
Highway Traffic Safety Administration (NHTSA) proposes to update,
reissue, and rename a previously published Department of Transportation
(DOT) system of records titled, ``Department of Transportation--DOT/
NHTSA 415 Artemis/Vehicle Owner Complaint Information.'' This system of
records allows NHTSA to collect and retain complaints, letters
communicating vehicle or equipment concerns, and supporting
documentation which may include photos, videos, police accident
reports, repair invoices or medical information (collectively,
``vehicle owner questionnaires'' or ``VOQs'') submitted by or on behalf
of vehicle or equipment owners and lessees (consumers). NHTSA updated
the notice with regards to: System Name to Vehicle Owner Questionnaire
(VOQ) System to appropriately identify the specific records maintained
in the Artemis system covered by the Privacy Act; System Location to
include NHTSA's current address and the location of the

Federal disaster recovery facility in Stennis, MS; System Managers to
update the name and contact information for the system's current points
of contact; Authority for Maintenance of the System to reflect the
system's underlying authority; Purposes to provide clarity and
facilitate understanding of NHTSA investigation and recall processes;
Categories of Records to provide greater clarity of the type of records
and information included in the system; Record Source Categories to
provide additional information about the mechanisms used by NHTSA for
collecting records in the system; and Routine Uses to modify an
existing routine use to permit sharing of records with manufacturers
named in VOQs earlier in NHTSA's investigation and recall processes
than permitted under the previously published system of records notice
(SORN), unless a consumer ``opts-out'' at the time of collection, and
to provide additional details and clarification about NTHSA referrals
of complaints to other agencies; and Policies and Practices for
Storage, Retrieval, Retention and Disposal of Records, respectively, to
provide additional information about the location of the system,
methods of retrieval, individuals permitted to retrieve records, and to
specify the applicable NARA record retention schedule; Administration,
Technical and Physical Safeguards to detail the privacy-risk mitigating
controls applicable to the system. Additionally, this notice includes
non-substantive changes to simplify and clarify the language,
formatting, and text of the previously published notice to align with
the requirements of Office of Management and Budget Memoranda A-108.
This updated system, Vehicle Owner Questionnaire (VOQ) System, will be
included in the Department of Transportation's inventory of record
systems.

DATES: Written comments must be submitted on or before May 24, 2019.
The modified system will be effective immediately with the exception of
the modified routine use which will be effective May 24, 2019.

ADDRESSES: You may submit comments, identified by docket number DOT-
OST-2019-0057 by one of the following methods:
     Federal e-Rulemaking Portal: http://www.regulations.gov.
Follow the instructions for submitting comments.
     Fax:<PHONE_NUMBER>.
     Mail: Department of Transportation Docket Management, Room
W12-140, 1200 New Jersey Ave. SE, Washington, DC 20590.
    Instructions: You must include the agency name and docket number,
DOT-OST-2019-0057. All comments received will be posted without change
to http://www.regulations.gov, including any personal information
provided.
    Privacy Act: In accordance with 5 U.S.C. 553(c), DOT solicits
comments from the public to better inform its rulemaking process. DOT
posts these comments, without edit, to www.regulations.gov. In order to
facilitate comment tracking and response, we encourage commenters to
provide their name, or the name of their organization; however,
submission of names is completely optional. Whether or not commenters
identify themselves, all timely comments will be fully considered. If
you wish to provide comments containing proprietary or confidential
information, please contact the agency for alternate submission
instructions.
    Docket: For access to the docket to read background documents or
comments received, go to https://www.regulations.gov or to the street
address listed above. Follow the online instructions for accessing.

FOR FURTHER INFORMATION CONTACT: For system-related questions please
contact Jeff Giuseppe<PHONE_NUMBER>), [email protected], Associate
Administrator, Enforcement, NHTSA, 1200 New Jersey Ave. SE, Washington,
DC 20590. For privacy questions, please contact: Claire W. Barrett
(202-366-8135), [email protected]. Departmental Chief Privacy Officer,
Department of Transportation, 1200 New Jersey Ave. SE, Washington, DC
20590.

SUPPLEMENTARY INFORMATION:

I. Background

    In accordance with the Privacy Act of 1974, NHTSA proposes to
update, reissue, and rename a previously published DOT system of
records titled, ``Department of Transportation--DOT/NHTSA 415 Artemis/
Vehicle Owner Complaint Information.'' The updated system of records
consists of VOQs submitted by or on behalf of consumers.
    Under 49 U.S.C. Chapter 301, NHTSA Office of Defects Investigation
(ODI), is responsible for identifying, investigating and ensuring the
remedy, through safety recalls conducted by manufacturers, of safety-
related defects and non-compliance issues in motor vehicles and items
of motor vehicle equipment. To accomplish this, ODI collects and
evaluates information from several different sources: Consumers, motor
vehicle and equipment manufacturers, State and local law enforcement,
insurance companies, automobile dealers, advocacy groups, and other
entities. Among the types of information collected by ODI are VOQs that
can be submitted through NHTSA's website https://www.NHTSA.gov, through
a telephone hotline where an operator inputs the consumer's information
into an electronic form, or a hard copy form sent to NHSTA by mail. ODI
also receives letters from consumers and their Congressional
representatives communicating vehicle and equipment concerns that the
Agency, in addition to or in place of the questionnaire form. This
system enables NHTSA to facilitate the defect investigation and recall
processes, which may include contacting consumers regarding their
complaints or recalls affecting their vehicle. ODI relies on the
Advanced Retrieval (Tire, Equipment, Motor Vehicles) Information System
(ARTEMIS) to provide centralized storage, document management and data
analysis tools for all information collected in support of the defect
investigation process, including VOQs. NHTSA uses the information in
this system to help the Agency identify, investigate and ensure that
manufactures remedy, through recall, replacement or repair, (1)
potential safety defects and failures to comply with Federal Motor
Vehicle Safety Standards (FMVSS) in motor vehicles and items of motor
vehicle equipment, and (2) problems with the scope, administration,
notification or remedy of a recall. NHTSA also may use the email
addresses and Vehicle Identification Numbers (VINs) collected, to
contact consumers whose vehicles are the subject of VOQs, and to notify
consumers via email of open recalls applicable to the vehicles or
equipment referenced in their VOQs.
    Changes to the System Name, System Location, System Managers,
Authority, Purpose, Categories of Individuals Covered by the System,
Categories of Records in the System, Record Source Categories, Policies
and Practices for Storage, Retrieval, Retention and Disposal of
Records, and Safeguards improve transparency, but do not reflect
substantive changes to the Notice. In particular, NHTSA's change to the
System Name is intended to clarify for members of the public that only
VOQs (as defined above) and not all documents stored in ARTEMIS, are
part of the VOQ Privacy Act system of records that is the subject of
this notice.
    Changes to the SORN include:
    1. System Name to Vehicle Owner Questionnaire (VOQ) System to
appropriately identify the specific records maintained in the Artemis
system covered by the Privacy Act;

    2. System Location to include NHTSA's current address and the
location of the Federal disaster recovery facility in Stennis, MS;
    3. System Managers to update the name and contact information for
the system's current points of contact;
    4. Authority for Maintenance of the System to reflect the system's
underlying authority;
    5. Purposes to provide clarity and facilitate understanding of
NHTSA investigation and recall processes;
    6. Categories of Records to provide greater clarity of the type of
records and information included in the system;
    7. Record Source Categories to provide additional information about
the mechanisms used by NHTSA for collecting records in the system;
    8. Routine Uses to modify an existing routine use to permit sharing
of records with manufacturers named in VOQs earlier in NHTSA's
investigation and recall processes than permitted under the previously
published SORN, unless a consumer ``opts-out'' at the time of
collection;
    9. Routine uses to replace a general routine use permitting NHTSA
to refer complaints to other state or federal agencies with three
separate routines uses specifying that NHTSA may share consumer
complaints with the National Transportation Safety Board (NTSB) in
connect with NTSB investigations of surface transportation incidents,
and highway accidents and incidents including those at railway grade
crossings; to the Consumer Product Safety Commission to support
enforcement of consumer product safety laws; to the Federal Trade
Commission in matters involving potential unfair or deceptive
practices;
    10. Routine uses to add a routine use permitting NHTSA to share
with the Department of Homeland Security consumer complaints indicative
of a cybersecurity vulnerability impacting critical infrastructure;
    11. Routine Uses to remove internal uses of the information in the
VOQ by ODI which are more appropriately addressed in the system's
Purpose.
    12. Policies and Practices for Storage, Retrieval, Retention and
Disposal of Records, respectively, to provide additional information
about the location of the system, methods of retrieval, individuals
permitted to retrieve records, and to specify the applicable NARA
record retention schedule;
    13. Administration, Technical and Physical Safeguards to detail the
privacy-risk mitigating controls applicable to the system.
    14. Additionally, this notice includes non-substantive changes to
simplify and clarify the language, formatting, and text of the
previously published notice to align with the requirements of Office of
Management and Budget Memoranda A-108. This updated system, Vehicle
Owner Questionnaire (VOQ) System, will be included in the Department of
Transportation's inventory of record systems.
    NHTSA routinely publishes VOQs without personally identifiable
information (PII) on its public facing website. A critical piece of
information included in a VOQ is the VIN. A VIN is coded information
that a vehicle manufacturer assigns to each vehicle it produces. This
code contains seventeen alphanumeric characters that provide
information about the vehicle. The first eleven characters identify the
manufacturer and various generic attributes of the vehicle, such as the
make, model, model year, body style, engine type, wheel base,
supplemental restraint system and production plant, etc. The last six
characters are the number sequentially assigned by the manufacturer in
the production process. This sequential number is the part of the VIN
that identifies a specific vehicle such as build history, standard or
optional equipment packages and service history (and makes it possible
through a search of public records to determine the identity of the
owner). Because the VIN provides significant data, a VIN is critical to
NHTSA's and a manufacturer's assessment and evaluation of potential
safety issues in motor vehicles. NHTSA publishes the first eleven
characters of the seventeen characters of VIN because, without the last
six characters, the VIN cannot be linked to an individual. The public,
including vehicle equipment manufacturers, can view these complaints
with the truncated VIN and access the general make, model, model year
attributes of the vehicle. Without the full seventeen character VIN, a
manufacturer is unable to identify the precise vehicle that has
experienced a potential safety related defect. Without such
information, a manufacturer is unable to learn of vehicle specific
information and focus on or identify potential safety issues.
    The previously published SORN permitted NHTSA to share PII,
including the full VIN, in VOQs with the manufacturer of the vehicle or
equipment identified in a VOQ only after the agency has opened a formal
investigation or a manufacturer has commenced a recall. In NHTSA's
view, providing manufacturers and other stakeholders earlier access to
PII in VOQs is critical to improving highway safety because earlier
access will help manufacturers to identify the specific vehicle and its
attributes that is subject to the complaint and remedy safety defects
and noncompliance issues in a more timely manner than under the
previously published SORN. Modifying this routine use will permit NHTSA
to share VOQs with manufacturers on a routine basis as soon as is
practicable after receipt by the Agency. Sharing these records at an
earlier stage than permitted under the previously published SORN is
compatible with the original vehicle safety purposes of the system
because it allows NHTSA to provide manufacturers with information
necessary to definitively identify the build history, equipment
options, and repair history of a vehicles identified in a VOQ, and to
identify, investigate and work with NHTSA to remedy a potential safety
defect, failure to comply with an FMVSS or recall administration, scope
or remedy issue.
    To limit the potential privacy risks of sharing consumer contact
information with manufacturer of the vehicles or equipment identified
in the VOQ, NHTSA updated its collection instrument (see 2127-0008) to
include explicit opt-out. Consumers who choose to opt-out will not have
their information shared with the manufacturer of the vehicles or
equipment identified in the VOQs unless the Agency opens an
investigation or a recall is initiated. The Agency takes consumer
privacy seriously and has included this new ``opt out'' feature in the
VOQ form in order to provide consumers with additional control over
their personal information. To enhance transparency, the ``opt-out''
appears in a prominent place in the electronic form maintained on the
Department's public website, and will be communicated to consumers by
hotline operators at the end of each hotline call. If consumers, at the
point and time of collection, either check an ``opt out'' box on the
VOQ form or direct the hotline operator collecting their information
over the telephone to do so, NHTSA will not share with manufacturers
the personal information provided in response to VOQ questions unless
the Agency opens up a defect investigation or a recall takes place. At
that point, an existing routine use permits the Agency to share their
VOQs with the manufacturer of the vehicles or equipment identified in
the VOQs. In addition to the approximately 70,000 VOQs filed annually
directly with NHTSA, the Agency also receives approximately 1500
letters per year

from consumers or consumers' Congressional representatives
communicating vehicle and equipment concerns that the Agency may
convert into VOQs. It is not practicable for NHTSA to provide this
small subset of consumers with the opportunity to ``opt out'' of
sharing their personal information with the manufacturer of the
vehicles or equipment identified in their letters. For this reason,
NHTSA will pursue a privacy-positive course of action and assign ``opt-
out'' status to the VOQs generated from these letters. NHTSA will not
share their personal information with the manufacturer of the vehicles
or equipment identified in these letters unless the Agency opens a
defect investigation or a recall is commenced.
    To further enhance transparency, NHTSA is adding a routine use
concerning comments received in the free form narrative section of the
web based VOQ form and VOQs received through the hotline. The publicly
available VOQs are on NHTSA's website, accessed through NHTSA.gov. As
part of the online VOQ form, NHTSA has a free text narrative section
that requests that the consumer ``In your own words, tell us what
happened.'' NHTSA provides notice to the consumer that any text
submitted will be made public without edits. Once the individual
submits the online form, NHTSA publishes these comments without edit
and other non-personal identifying information in the VOQ to NHTSA's
public website. In order to advise the public how NHTSA uses the
narrative comments in a VOQ, NTHSA is establish a routine use this
system of records. This routine use is compatible with the purpose of
collection, which is to provide the public with information concerning
potential safety related defects and noncompliance with a federal motor
vehicle safety standard.
    Finally, NHTSA is replacing pre-existing, generally-worded, routine
use that permits NTHSA to share consumer complaints with ``appropriate
State or Federal agenc[ies] for actions involving matters of law or
regulation beyond the responsibility'' of NHSTA with three separate
routine uses that specify the agencies with and purposes for which
NHTSA shares information. This does not reflect a change in the types
of disclosures NTSHA has or will make under the routine use, but is
merely intended to provide clarity and transparency into how NHTSA
shares information with other agencies. NHTSA also is updating its
routine uses to permit disclosure to DHS when the consumer complaint
evidences a potential cybersecurity vulnerability impacting
transportation critical infrastructure. These routine uses are
compatible with the purpose of the collection as a ``necessary and
proper'' use of the information, as discussed more below. Individuals
who provide VOQ information to NHTSA do so because they are seeking
Federal agency intervention to address a potential issue with their
vehicle. When the potential issue relates to a matter outside of
NHTSA's jurisdiction, individuals may expect that NHTSA will share the
information with the Federal agencies having jurisdiction for the
matter. Thus, this routine use with compatible with the purpose of the
collection, which is to identify, investigate and remedy potential
safety defects.
    NHTSA is updating this Notice to include Departmental general
routine uses previously incorporated by reference, to the extent that
they are compatible with the purposes of this System. As recognized by
the Office of Management and Budget (OMB) in its Privacy Act
Implementation Guidance and Responsibilities (65 FR 19746, July 9,
1975), the routine uses include all proper and necessary uses of
information in the system, even if such uses occur infrequently. NHTSA
has included in this Notice general routine uses for disclosures to law
enforcement when the record, on its face, indicates a violation of law,
to DOJ for litigation purposes, or when necessary in investigating or
responding to a breach of this system or other agencies' systems. NHTSA
must work with DOT to take appropriate action to address any apparent
violations of the law, and to share information with legal counsel in
the Department of Justice when necessary for litigation. OMB has long
recognized that these types of routine uses are ``proper and
necessary'' uses of information and qualify as compatible with agency
systems. 65 FR 19476. In addition, by OMB Memorandum M-17-12, OMB
directed agencies to include routine uses that will permit sharing of
information when needed to investigate, respond to, and mitigate a
breach of a Federal information system. NHTSA also has included routine
uses that permit sharing with the National Archives and Records
Administration when necessary for an inspection, to any Federal
government agency engaged in audit or oversight related to this system,
or when DOT determines that the disclosure will detect, prevent, or
mitigate terrorism activity. These types of disclosures are necessary
and proper uses of information in this system because they further
DOT's obligation to fulfil its records management and program
management responsibilities by facilitating accountability to agencies
charged with oversight in these areas, and the Department's obligation
under Intelligence Reform and Terrorism Prevention Act of 2004, Public
Law 108-456, and Executive Order 13388 (Oct. 25, 2005) to share
information necessary and relevant to detect, prevent, disrupt,
preempt, or mitigate the effects of terrorist activities against the
territory, people, and interests of the United States.
    Finally, this system includes a routine use to permit sharing with
our contractors, consultants, experts, grantees, and others when
necessary to fulfill a NHTSA function related to this System. Agencies
routinely engage assistance of these types of individuals in the
fulfillment of their duties, such as contract support necessary to
maintain the database in which these records are housed. NHTSA relies
on contract support to maintain this system, and disclosures for this
purpose are compatible with the purpose of the collection.

System Name and Number:
    Vehicle Owner Questionnaire System DOT/NHTSA 415.

Security Classification:
    Unclassified, Sensitive.

System Location:
    Records are maintained at the Department of Transportation
Headquarters, 1200 New Jersey Ave., Washington, DC 20590, and at the
Federal disaster recovery facility in Stennis, MS.

System Manager(s):
    Stephen A. Ridella, Ph.D., Director, Office of Defects
Investigation, National Highway Traffic Safety Administration, U.S.
Department of Transportation, 1200 New Jersey Avenue SE, Washington, DC
20590,<PHONE_NUMBER>, [email protected].

Authority for Maintenance of the System:
    49 U.S.C. 30116, 30118-22, 30166.

Purpose of the System:
    To assist NHTSA to identify, investigate and ensure that
manufactures remedy, through recall, replacement or repair, potential
safety defects and failures to comply with FMVSS in motor vehicles and
items of motor vehicle equipment. To assist NHTSA to identify,
investigate and ensure that manufactures remedy problems with the
scope, administration, notification or remedy of a recall. For these
purposes, NHTSA routinely retrieves VOQs by name or

assigned identifier to contact motor vehicle drivers or owners
experiencing safety problems or witnesses and other individuals with
information relevant to the agency's investigative or remedial efforts.

Categories of Individuals Covered by the System:
    Owners of motor vehicles and motor vehicle equipment, as well as
users of leased motor vehicles and motor vehicle equipment, who have
filed, or on whose behalf have been filed VOQs, or who send letters to
the agency directly or through their representatives (e.g., advocates,
attorneys or Congressmen) concerning motor vehicle safety.

Categories of Records in the System:
    The standard questionnaire format collects information that assists
NHTSA to identify and identify potential defects, recall issues, and
instances of noncompliance. The information submitted by or on behalf
of an individual includes the following:
     Vehicle identification number (VIN).
     Make, model and year of relevant vehicle.
     Part affected.
     A narrative field that permits the individual to describe
in his or her own words what happened.
     Photographs/supporting documentation.
     Date of incident.
     Was there a crash.
     Was there a fire.
     Was there an injury or fatality.
     Speed at time.
     Number of miles on the vehicle.
     First and last name.
     Email address.
     Street address.
     Telephone/alt telephone number.
    Individuals may also submit supporting documentation with a
questionnaire or letter. NHTSA does not control the data submitted in
these records and it may include personal information. Supporting
documentation includes:
     Repair invoices.
     Insurance claims.
     Vehicle crash information.
     Police accident reports.
     Photographs and video image recordings of vehicles, parts,
bodies or body parts.

Record Source Categories:
    Consumers, to include; vehicle owners, drivers of leased vehicles,
and individuals or organizations submitting VOQs to NHTSA on their
behalf.

Routine Uses of Records Maintained in the System, Including Categories
of Users and the Purposes of Such Uses:
    In addition to those disclosures generally permitted under 5 U.S.C.
552a(b) of the Privacy Act, all or a portion of the information
contained in this system may be disclosed outside of DOT as a routine
use pursuant to 5 U.S.C. 552a(b)(3) as follows:

System Specific Routine Uses:
    1. To manufacturers prior to the initiation of a formal
investigation by the Department, an entire VOQ information to respond
to consumer complaints and research the cause of the complaint, except
when consumers ``opt out'' of such sharing at the point and time of
collection. Information from individuals who submit VOQs by means other
than the NHTSA website will be treated as if the individual has opt-
out;
    2. To manufacturers, after the Agency opens an investigation, to
allow them to investigate owner complaints and researching the root
cause of the alleged problem;
    3. To the National Transportation Safety Board (NTSB) an entire VOQ
to support NTSB investigations of surface transportation incidents,
highway accidents and incidents, including incidents at railway grade
crossings;
    4. To the Consumer Product Safety Commission (CPSC) an entire VOQ
to support identification of violations and enforcement of consumer
product safety laws;
    5. To the Federal Trade Commission an entire VOQ in matters
involving potential unfair or deceptive trade practices;
    6. To the Department of Homeland Security (DHS) if the VOQ is
indicative of a cybersecurity vulnerability impacting critical
infrastructure; and
    7. To members of the public through NHTSA.gov website, information
included in the narrative portion of the form questionnaire.
Individuals are notified at the time of the VOQ submission that all
information provided in the narrative will be made publicly available
without edit.

Department General Routine Uses:
    The U.S. Department of Transportation has established general
routine uses applicable to all systems maintained by DOT. The following
DOT general routine uses apply to this system of records:
    1. In the event that a system of records maintained by DOT to carry
out its functions indicates a violation or potential violation of law,
whether civil, criminal or regulatory in nature, and whether arising by
general statute or particular program pursuant thereto, the relevant
records in the system of records may be referred, as a routine use, to
the appropriate agency, whether Federal, State, local or foreign,
charged with the responsibility of investigating or prosecuting such
violation or charged with enforcing or implementing the statute, or
rule, regulation, or order issued pursuant thereto.
    2a. Routine Use for Disclosure for Use in Litigation. It shall be a
routine use of the records in this system of records to disclose them
to the Department of Justice or other Federal agency conducting
litigation when--
    (a) DOT, or any agency thereof, or
    (b) Any employee of DOT or any agency thereof (including a member
of the Coast Guard), in his/her official capacity, or
    (c) Any employee of DOT or any agency thereof (including a member
of the Coast Guard), in his/her individual capacity where the
Department of Justice has agreed to represent the employee, or
    (d) The United States or any agency thereof, where DOT determines
that litigation is likely to affect the United States, is a party to
litigation or has an interest in such litigation, and the use of such
records by the Department of Justice or other Federal agency conducting
the litigation is deemed by DOT to be relevant and necessary in the
litigation, provided, however, that in each case, DOT determines that
disclosure of the records in the litigation is a use of the information
contained in the records that is compatible with the purpose for which
the records were collected.
    2b. Routine Use for Agency Disclosure in Other Proceedings. It
shall be a routine use of records in this system to disclose them in
proceedings before any court or adjudicative or administrative body
before which DOT or any agency thereof, appears, when--
    (a) DOT, or any agency thereof, or
    (b) Any employee of DOT or any agency thereof (including a member
of the Coast Guard) in his/her official capacity, or
    (c) Any employee of DOT or any agency thereof (including a member
of the Coast Guard) in his/her individual capacity where DOT has agreed
to represent the employee, or
    (d) The United States or any agency thereof, where DOT determines
that the proceeding is likely to affect the United States, is a party
to the proceeding or has an interest in such proceeding, and DOT
determines that use of such records is relevant and necessary in the
proceeding, provided, however, that in each case, DOT determines that

disclosure of the records in the proceeding is a use of the information
contained in the records that is compatible with the purpose for which
the records were collected.
    3. One or more records from a system of records may be disclosed
routinely to the National Archives and Records Administration in
records management inspections being conducted under the authority of
44 U.S.C. 2904 and 2906.
    4. DOT may disclose records from this system, as a routine use, to
appropriate agencies, entities, and persons when (1) DOT suspects or
has confirmed that the security or confidentiality of information in
the system of records has been compromised; (2) DOT has determined that
as a result of the suspected or confirmed compromise there is a risk of
harm to economic or property interests, identity theft or fraud, or
harm to the security or integrity of this system or other systems or
programs (whether maintained by DOT or another agency or entity) that
rely upon the compromised information; and (3) the disclosure made to
such agencies, entities, and persons is reasonably necessary to assist
in connection with DOT's efforts to respond to the suspected or
confirmed compromise and prevent, minimize, or remedy such harm.
    5. DOT may disclose records from this system, as a routine use, to
the Office of Government Information Services for the purpose of (a)
resolving disputes between FOIA requesters and Federal agencies and (b)
reviewing agencies' policies, procedures, and compliance in order to
recommend policy changes to Congress and the President.
    6. DOT may disclose records from this system, as a routine use, to
contractors and their agents, experts, consultants, and others
performing or working on a contract, service, cooperative agreement, or
other assignment for DOT, when necessary to accomplish an agency
function related to this system of records.
    7. DOT may disclose records from this system, as a routine use, to
an agency, organization, or individual for the purpose of performing
audit or oversight operations related to this system of records, but
only such records as are necessary and relevant to the audit or
oversight activity. This routine use does not apply to intra-agency
sharing authorized under Section (b)(1) of the Privacy Act.
    8. DOT may disclose from this system, as a routine use, records
consisting of, or relating to, terrorism information (6 U.S.C.
485(a)(5)), homeland security information (6 U.S.C. 482(f)(1)), or Law
enforcement information (Guideline 2 Report attached to White House
Memorandum, ``Information Sharing Environment, November 22, 2006) to a
Federal, State, local, tribal, territorial, foreign government and/or
multinational agency, either in response to its request or upon the
initiative of the Component, for purposes of sharing such information
as is necessary and relevant for the agencies to detect, prevent,
disrupt, preempt, and mitigate the effects of terrorist activities
against the territory, people, and interests of the United States of
America, as contemplated by the Intelligence Reform and Terrorism
Prevention Act of 2004 (Pub. L. 108-458) and Executive Order 13388
(October 25, 2005).

Policies and Practices for Storage of Records:
    Records are maintained in electronic systems and hard copy at DOT
Headquarters, 1200 New Jersey Ave. SE, Washington, DC 20590 and at the
Federal disaster recovery facility in Stennis, MS.

Policies and Practices for Retrieval of Records:
    NHTSA staff and agents routinely retrieve VOQs by consumer name or
personal identifier.

Policies and Practices for Retention and Disposal of Records:
    Pursuant to approved NARA Schedule N1-416-05-003 (Office of Defect
Investigation Files), NHTSA: (1) Destroys VOQ information provided by
consumers 15 years after receipt; (2) destroys investigation files,
including any VOQs in the files, 15 years after the date of the
resolution of an investigation when the investigation did not lead to a
court decision; and (3) retains on a permanent basis investigation
files, including any VOQs in the files, when an investigation leads to
a court decision, but transfers legal custody of the files to NARA
after 15 years. Original hard copy records collected from consumers and
others are scanned into ARTEMIS and then destroyed.

Administrative, Technical and Physical Safeguards:
    The VOQ system is protected by a multi-layer security approach to
prevent unauthorized access to personally identifiable information
through appropriate administrative, physical, and technical safeguards.
Protective strategies include: Implementing physical access controls at
DOT facilities; ensuring confidentiality of communications using tools
such as encryption, authentication of sending parties, and
compartmentalizing databases; and employing auditing software and
personnel screening to ensure that all personnel with access to data
are screened through background investigations commensurate with the
level of access required to perform their duties. Records maintained in
hard copy are stored in locked file cabinets until they can be scanned
and uploaded to ARTEMIS and subsequently destroyed.

Record Access Procedures:
    An individual wishing to gain access to any record pertaining to
him or her in the system should send his or her name, address,
telephone number, and a description of the record(s) sought to the U.S.
Department of Transportation, Privacy Act Officer, Office of the Chief
Information Officer, 1200 New Jersey Avenue SE, Washington, DC 20590.

Contesting Record Procedures:
    An individual seeking to contest information contained in a record
pertaining to him or her in this system should address written
inquiries to the U.S. Department of Transportation, Privacy Act
Officer, Office of the Chief Information Officer, 1200 New Jersey
Avenue SE, Washington, DC 20590. Inquiries should include name,
address, telephone number, and a description of the record and
information being contested.

Notification Procedures:
    An individual seeking to determine whether a record pertaining to
him or her is contained in this system should address written inquiries
to the U.S. Department of Transportation, Privacy Act Officer, Office
of the Chief Information Officer, 1200 New Jersey Avenue SE,
Washington, DC 20590. Inquiries should include name, address, telephone
number, and identify the system that is the subject of the inquiry.

Exemptions Promulgated for the System:
    None.

History:
    The last full Federal Register Notice pertaining to this system
that contained all SORN elements was published on September 3, 2004 (69
FR 53971-53972).

    Issued in Washington, DC on April 18, 2019.
Claire W. Barrett,
Departmental Chief Privacy Officer, Department of Transportation.
[FR Doc. 2019-08171 Filed 4-23-19; 8:45 am]
 BILLING CODE 4910-9X-P


[Federal Register Volume 88, Number 218 (Tuesday, November 14, 2023)]
[Notices]
[Pages 78064-78065]
[FR Doc No: 2023-25071]

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

DEPARTMENT OF LABOR

Occupational Safety and Health Administration

[Docket No. OSHA-2023-0003]

National Advisory Committee on Occupational Safety and Health
(NACOSH): Notice of Meeting

AGENCY: Occupational Safety and Health Administration (OSHA), Labor.

ACTION: Notice of NACOSH meeting.

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

SUMMARY: The National Advisory Committee on Occupational Safety and
Health (NACOSH) will meet December 12, 2023, in a hybrid format.
Committee members will meet in person, while the public is invited to
participate either in person or virtually via WebEx.

DATES: The NACOSH will meet from 10:00 a.m. to 4:00 p.m., ET, December
12, 2023.

ADDRESSES:
    Submission of comments and requests to speak: Comments and requests
to speak at the NACOSH meeting, including attachments, must be
submitted electronically at www.regulations.gov, the Federal
eRulemaking Portal by November 27, 2023. Comments must identify the
docket number for this Federal Register notice (Docket No. OSHA-2023-
0003). Follow the online instructions for submitting comments.
    Registration: All persons wishing to attend the meeting, either in
person or virtually, must register via the registration link on the
NACOSH web page at https://www.osha.gov/advisorycommittee/nacosh. Upon
registration, in-person attendees will receive directions for
participation and virtual attendees will receive a WebEx link for
remote access to the meeting. At this time, OSHA will be limiting in-
person attendance to 25 members of the public.
    Requests for special accommodations: Submit requests for special
accommodations, including translation services, for this NACOSH meeting
by November 27, 2023, to Ms. Christie Garner, Directorate of Standards
and Guidance, OSHA, U.S. Department of Labor; telephone: (202) 693-
2246; email: [email protected].

    Instructions: All submissions must include the agency name and the
OSHA docket number for this Federal Register notice (Docket No. OSHA-
2023-0003). OSHA will place comments and requests to speak, including
personal information, in the public docket, which may be available
online. Therefore, OSHA cautions interested parties about submitting
personal information such as Social Security numbers and birthdates.
    Docket: To read or download documents in the public docket for this
NACOSH meeting, go to www.regulations.gov. All documents in the public
docket are listed in the index; however, some documents (e.g.,
copyrighted material) are not publicly available to read or download
through www.regulations.gov. All submissions, including copyrighted
material, are available for inspection through the OSHA Docket Office.
Contact the OSHA Docket Office at<PHONE_NUMBER> (TTY<PHONE_NUMBER>)
for assistance in locating docket submissions.

FOR FURTHER INFORMATION CONTACT:
    For press inquiries: Mr. Frank Meilinger, Director, OSHA Office of
Communications, U.S. Department of Labor; telephone:<PHONE_NUMBER>;
email: [email protected].
    For general information about NACOSH: Ms. Lisa Long, Deputy
Director, Directorate of Standards and Guidance, OSHA, U.S. Department
of Labor; telephone:<PHONE_NUMBER>; email: [email protected].
    Telecommunication requirements: For additional information about
the telecommunication requirements for the meeting, please contact Ms.
Christie Garner, Directorate of Standards and Guidance, OSHA, U.S.
Department of Labor; telephone:<PHONE_NUMBER>; email:
[email protected].
    For copies of this Federal Register Notice: Electronic copies of
this Federal Register notice are available at www.regulations.gov. This
notice, as well as news releases and other relevant information, are
also available at OSHA's web page at https://www.osha.gov/advisorycommittee/nacosh.

SUPPLEMENTARY INFORMATION:

I. Background

    NACOSH was established by section 7(a) of the Occupational Safety
and Health Act of 1970 (OSH Act) (29 U.S.C. 651, 656) to advise,
consult with, and make recommendations to the Secretary of Labor and
the Secretary of Health and Human Services on matters relating to the
administration of the OSH Act. NACOSH is a continuing advisory
committee of indefinite duration.
    NACOSH operates in accordance with the Federal Advisory Committee
Act (FACA) (5 U.S.C. App.2), its implementing regulations (41 CFR part
102-3), and OSHA's regulations on NACOSH (29 CFR 1912.5 and 29 CFR part
1912a).

II. Meeting Information

    Public attendance will be in a hybrid format, either in person or
virtually via WebEx. Meeting information will be posted in the docket
(Docket No. OSHA-2023-0003) and on the NACOSH web page, https://www.osha.gov/advisorycommittee/nacosh, prior to the meeting.
    NACOSH will meet from 10:00 a.m. to 4:00 p.m., ET on December 12,
2023.
    Meeting agenda: The tentative agenda for this meeting includes:
     Introduction of new members;
     OSHA Updates;
     NIOSH Update;
     NIOSH Mental Health for Healthcare Workers Campaign;
     Safety as a Core Value; and
     Whistleblower Discussion.

Authority and Signature

    James S. Frederick, Deputy Assistant Secretary of Labor for
Occupational Safety and Health, authorized the preparation of this
notice under the authority granted by 29 U.S.C. 655(b)(1) and 656(b), 5
U.S.C. app. 2, 29 CFR parts 1912 and 1912a, and Secretary of Labor's
Order No. 8-2020 (85 FR 58393).

    Signed at Washington, DC.
James S. Frederick,
Deputy Assistant Secretary for Occupational Safety and Health.
[FR Doc. 2023-25071 Filed 11-13-23; 8:45 am]
BILLING CODE 4510-26-P


[Federal Register: January 15, 2010 (Volume 75, Number 10)]
[Notices]
[Page 2532-2535]
[DOCID:fr15ja10-50]

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

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

Combined Notice of Filings 1

January 6, 2010.
    Take notice that the Commission received the following electric
rate filings:
    Docket Numbers: ER02-537-027; ER03-983-024; ER07-758-020; ER06-739-
024; ER06-738-024; ER07-501-023; ER08-649-016.
    Applicants: Cogen Technologies Linden Venture, L.P., Fox Energy
Company LLC, Birchwood Power Partners, L.P., Shady Hills Power Company,
LLC, East Coast Power Linden Holding, LLC, EFS Parlin Holdings, LLC,
Inland Empire Energy Center, LLC.
    Description: Notice of Non-Material Changes in Status of East Coast
Power Linden Holding, LLC, et al.
    Filed Dated: 01/04/2010.
    Accession Number: 20100104-5074.
    Comment Date: 5 p.m. Eastern Time on Monday, January 25, 2010.

    Docket Numbers: ER06-278-005; ER08-654-004.

    Applicants: Nevada Hydro Company, Inc.; California Independent
System Operator Corporation.
    Description: Response of the Nevada Hydro Company, Inc. Request for
Clarification.
    Filed Dated: 01/05/2010.
    Accession Number: 20100105-5022.
    Comment Date: 5 p.m. Eastern Time on Tuesday, January 26, 2010.

    Docket Numbers: ER06-739-023; ER06-738-023; ER07-501-022; ER08-649-
015.
    Applicants: Cogen Technologies Linden Venture, L.P., East Coast
Power Linden Holding, LLC, Birchwood Power Partners, L.P., EFS Parlin
Holdings, LLC.
    Description: Notice of Non-Material Change in Status of East Coast
Power Linden Holding, LLC, et al.
    Filed Dated: 01/04/2010.
    Accession Number: 20100104-5072.
    Comment Date: 5 p.m. Eastern Time on Monday, January 25, 2010.

    Docket Numbers: ER09-408-003.
    Applicants: PacifiCorp.
    Description: Compliance Filing of PacifiCorp.
    Filed Dated: 01/04/2010.
    Accession Number: 20100104-5078.
    Comment Date: 5 p.m. Eastern Time on Monday, January 25, 2010.

    Docket Numbers: ER09-412-010.
    Applicants: PJM Interconnection, LLC.
    Description: PJM Interconnection, LLC submits Fifth Revised Sheet
572 et al to FERC Electric Tariff, Sixth Revised Volume 1.
    Filed Dated: 12/29/2009.
    Accession Number: 20091231-0044.
    Comment Date: 5 p.m. Eastern Time on Tuesday, January 19, 2010.

    Docket Numbers: ER09-1114-002; ER09-1115-002.
    Applicants: RRI Energy Services, Inc.; RRI Energy Solutions East,
LLC.
    Description: Supplement to the December 14, 2009 Category One
Request Filing of RRI Energy Services, Inc. and RRI Energy Solutions
East, LLC.
    Filed Dated: 01/06/2010.
    Accession Number: 20100106-5017.
    Comment Date: 5 p.m. Eastern Time on Wednesday, January 27, 2010.

    Docket Numbers: ER09-1542-001.
    Applicants: California Independent System Operator Corporation.
    Description: The California Independent System Operator Corporation
submits the Second Revised Sheet134 et al to FERC Electric Tariff,
Fourth Replacement Volume 11542.
    Filed Dated: 12/31/2009.
    Accession Number: 20100104-0067.
    Comment Date: 5 p.m. Eastern Time on Thursday, January 21, 2010.

    Docket Numbers: ER10-517-000.
    Applicants: New England Power Pool.
    Description: The New England Power Pool Participants Committee
submits transmittal letter, counterpart signature pages etc.
    Filed Dated: 12/30/2009.
    Accession Number: 20091231-0042.
    Comment Date: 5 p.m. Eastern Time on Wednesday, January 20, 2010.

    Docket Numbers: ER10-519-000.
    Applicants: MidAmerican Energy Company.
    Description: MidAmerican Energy Company submits Service Agreement
for Transmission Operator Services including but not limited to
performance of Certain Activities etc.
    Filed Dated: 12/30/2009.
    Accession Number: 20091231-0041.
    Comment Date: 5 p.m. Eastern Time on Wednesday, January 20, 2010.

    Docket Numbers: ER10-520-000.
    Applicants: PJM Interconnection, LLC.
    Description: PJM Interconnection, LLC submits executed version of
the revised Wholesale Market Participation Agreement with WM Renewable
Energy, LLC et al.
    Filed Dated: 12/30/2009.
    Accession Number: 20091231-0040.
    Comment Date: 5 p.m. Eastern Time on Wednesday, January 20, 2010.

    Docket Numbers: ER10-521-000.
    Applicants: Southern California Edison Company.
    Description: Southern California Edison Company submits revised
rate sheet to a letter agreement.
    Filed Dated: 12/30/2009.
    Accession Number: 20091231-0039.
    Comment Date: 5 p.m. Eastern Time on Wednesday, January 20, 2010.

    Docket Numbers: ER10-528-001.
    Applicants: Portland General Electric Company.
    Description: Portland General Electric Company submits the errata
and the revised pages for Attachments 9 and 10 to the 12/29/09 filing.
    Filed Dated: 12/31/2009.
    Accession Number: 20100104-0061.
    Comment Date: 5 p.m. Eastern Time on Thursday, January 21, 2010.

    Docket Numbers: ER10-534-000.
    Applicants: Southwest Power Pool, Inc.
    Description: Southwest Power Pool, Inc. submits an executed Large
Generator Interconnection Agreement with Shooting Star Power Partners,
LLC et al.
    Filed Dated: 12/31/2009.
    Accession Number: 20100104-0072.
    Comment Date: 5 p.m. Eastern Time on Thursday, January 21, 2010.

    Docket Numbers: ER10-535-000.
    Applicants: Puget Sound Energy, Inc.
    Description: Puget Sound Energy Inc. submits an Interconnection and
Operating Agreement effective 1/1/2010.
    Filed Dated: 12/31/2009.
    Accession Number: 20100104-0071.
    Comment Date: 5 p.m. Eastern Time on Thursday, January 21, 2010.

    Docket Numbers: ER10-537-000.
    Applicants: Palmco Power MD, LLC.
    Description: Palmco Power MD, LLC submits an amendment for the
Petition for Acceptance of Initial Tariff, Waivers and Blanket
Authority, FERC Electric Tariff, Original Volume 1.
    Filed Dated: 01/05/2010.
    Accession Number: 20100105-0205.
    Comment Date: 5 p.m. Eastern Time on Tuesday, January 26, 2010.

    Docket Numbers: ER10-539-000.
    Applicants: Palmco Power OH, LLC.
    Description: Palmco Power OH, LLC submits an amendment for the
Petition for Acceptance of Initial Rate Schedule, Waivers and Blanket
Authority.
    Filed Dated: 01/05/2010.
    Accession Number: 20100105-0206.
    Comment Date: 5 p.m. Eastern Time on Tuesday, January 26, 2010.

    Docket Numbers: ER10-540-000.
    Applicants: Wabash Valley Power Association, Inc.
    Description: Wabash Valley Power Association, Inc submits Original
Sheet 1 et al. to FERC First Revised Rate Schedule 5 to be effective 3/
11/10.
    Filed Dated: 12/31/2009.
    Accession Number: 20100104-0110.
    Comment Date: 5 p.m. Eastern Time on Thursday, January 21, 2010.

    Docket Numbers: ER10-541-000.
    Applicants: Midwest Independent Transmission System, Xcel Energy
Services Inc.
    Description: Northern States Power Company et al. submits the
Second Revised Sheet No. 2751 to FERC Electric Tariff, Fourth Revised
Volume 1 to be effective 1/1/10.
    Filed Dated: 12/31/2009.
    Accession Number: 20100104-0069.
    Comment Date: 5 p.m. Eastern Time on Thursday, January 21, 2010.

    Docket Numbers: ER10-542-000.
    Applicants: Southern California Edison Company.
    Description: Southern California Edison Company submits the Service
Agreement No. 31 et al. to FERC Electric Tariff, Second Revised Volume
6 et al.
    Filed Dated: 12/31/2009.
    Accession Number: 20100104-0066.
    Comment Date: 5 p.m. Eastern Time on Thursday, January 21, 2010.

    Docket Numbers: ER10-543-000.
    Applicants: West Georgia Generating Company, LLC.

    Description: Southern Power Company submits Notice of Cancellation
of West Georgia's market based rate tariff, FERC Electric Tariff, First
Revised Volume 1.
    Filed Dated: 12/31/2009.
    Accession Number: 20100104-0063.
    Comment Date: 5 p.m. Eastern Time on Thursday, January 21, 2010.

    Docket Numbers: ER10-544-000.
    Applicants: Southern California Edison Company.
    Description: Southern California Edison Company submits the amended
Service Agreement for Wholesale Distribution Service No. 20 etc.
    Filed Dated: 12/31/2009.
    Accession Number: 20100104-0064.
    Comment Date: 5 p.m. Eastern Time on Thursday, January 21, 2010.

    Docket Numbers: ER10-545-000.
    Applicants: Idaho Power Company.
    Description: Idaho Power Company submits the Fourth Revised Service
Agreement No. 159 to FERC Electric Tariff, First Revised Volume 6 to be
effective 1/1/10.
    Filed Dated: 12/31/2009.
    Accession Number: 20100104-0065.
    Comment Date: 5 p.m. Eastern Time on Thursday, January 21, 2010.

    Docket Numbers: ER10-546-000.
    Applicants: Southern California Edison Company.
    Description: Southern California Edison Company submits the amended
Project System Facilities Agreement with Blythe Energy LLC, Service
Agreement No. 13 etc.
    Filed Dated: 12/31/2009.
    Accession Number: 20100104-0062.
    Comment Date: 5 p.m. Eastern Time on Thursday, January 21, 2010.

    Docket Numbers: ER10-551-000.
    Applicants: Hartwell Energy Limited Partnership.
    Description: Hartwell Energy Limited Partnership submits Notice of
Cancellation of Rate Schedule FERC No. 1.
    Filed Dated: 01/04/2010.
    Accession Number: 20100104-0211.
    Comment Date: 5 p.m. Eastern Time on Monday, January 25, 2010.

    Docket Numbers: ER10-552-000.
    Applicants: Heard County Power, LLC.
    Description: Heard County Power, LLC submits Notice of Cancellation
of Electric Tariff.
    Filed Dated: 01/04/2010.
    Accession Number: 20100104-0212.
    Comment Date: 5 p.m. Eastern Time on Monday, January 25, 2010.

    Docket Numbers: ER10-554-000.
    Applicants: New York Independent System Operator, Inc.
    Description: New York Independent System Operator, Inc. et al.
submits an executed Small Generator Interconnection Agreement with
National Grid, and Innovative Energy Systems, Inc.
    Filed Dated: 01/05/2010.
    Accession Number: 20100105-0210.
    Comment Date: 5 p.m. Eastern Time on Tuesday, January 26, 2010.

    Docket Numbers: ER10-555-000.
    Applicants: New York Independent System Operator, Inc.
    Description: New York Independent System Operator, Inc. et al.
submits an executed Small Generator Interconnection Agreement with
National Grid, and Chautauqua County.
    Filed Dated: 01/05/2010.
    Accession Number: 20100105-0211.
    Comment Date: 5 p.m. Eastern Time on Tuesday, January 26, 2010.

    Docket Numbers: ER10-556-000.
    Applicants: Kansas City Power & Light Company.
    Description: Kansas City Power & Light Company submits revised
pages to the Facilities Use Agreement with enXco Develop.m.ent Corp.
    Filed Dated: 01/05/2010.
    Accession Number: 20100105-0208.
    Comment Date: 5 p.m. Eastern Time on Tuesday, January 26, 2010.

    Docket Numbers: ER10-557-000.
    Applicants: Virginia Electric and Power Company.
    Description: Virginia Electric and Power Company submits Third
Revised Sheet 314F et al. to FERC Electric Tariff, Sixth Revised Volume
1 to PJM Interconnection, LLC's open-access transmission tariff etc.
    Filed Dated: 01/05/2010.
    Accession Number: 20100105-0209.
    Comment Date: 5 p.m. Eastern Time on Tuesday, January 26, 2010.

    Take notice that the Commission received the following electric
securities filings:

    Docket Numbers: ES10-22-000.
    Applicants: Rochester Gas and Electric Corporation.
    Description: Application of Rochester Gas and Electric Corporation
for Authorization to Issue Short-Term Debt Under Section 204 of the
Federal Power Act.
    Filed Dated: 01/05/2010.
    Accession Number: 20100105-5075.
    Comment Date: 5 p.m. Eastern Time on Tuesday, January 26, 2010.

    Docket Numbers: ES10-23-000.
    Applicants: New York State Electric & Gas Corp.
    Description: Application of New York State Electric & Gas
Corporation for Authorization to Issue Short-Term Debt Under Section
204 of the Federal Power Act.
    Filed Dated: 01/05/2010.
    Accession Number: 20100105-5076.
    Comment Date: 5 p.m. Eastern Time on Tuesday, January 26, 2010.

    Docket Numbers: ES10-24-000.
    Applicants: Central Maine Power Company.
    Description: Application of Central Maine Power Company for
Authorization to Issue Short-Term Debt Under Section 204 of the Federal
Power Act.
    Filed Dated: 01/06/2010.
    Accession Number: 20100106-5041.
    Comment Date: 5 p.m. Eastern Time on Wednesday, January 27, 2010.

    Take notice that the Commission received the following open access
transmission tariff filings:

    Docket Numbers: OA08-61-003.
    Applicants: Southwest Power Pool, Inc.
    Description: Southwest Power Pool, Inc. submits an errata to its
11/2/09 filing proposing revisions to their transmission planning
process etc.
    Filed Dated: 12/30/2009.
    Accession Number: 20091231-0043.
    Comment Date: 5 p.m. Eastern Time on Wednesday, January 20, 2010.

    Any person desiring to intervene or to protest in any of the above
proceedings must file in accordance with Rules 211 and 214 of the
Commission's Rules of Practice and Procedure (18 CFR 385.211 and
385.214) on or before 5 p.m. Eastern Time on the specified comment
date. It is not necessary to separately intervene again in a subdocket
related to a compliance filing if you have previously intervened in the
same docket. Protests will be considered by the Commission in
determining the appropriate action to be taken, but will not serve to
make protestants parties to the proceeding. Anyone filing a motion to
intervene or protest must serve a copy of that document on the
Applicant. In reference to filings initiating a new proceeding,
interventions or protests submitted on or before the comment deadline
need not be served on persons other than the Applicant.
    The Commission encourages electronic submission of protests and
interventions in lieu of paper, using the FERC Online links at http://
www.ferc.gov. To facilitate electronic service, persons with Internet
access who will eFile a document and/or be listed as a contact for an
intervenor must create and validate an eRegistration account using the
eRegistration link. Select the eFiling link to log on and submit the
intervention or protests.

    Persons unable to file electronically should submit an original and
14 copies of the intervention or protest to the Federal Energy
Regulatory Commission, 888 First St., NE., Washington, DC 20426.
    The filings in the above proceedings are accessible in the
Commission's eLibrary system by clicking on the appropriate link in the
above list. They are also available for review in the Commission's
Public Reference Room in Washington, DC. There is an eSubscription link
on the Web site that enables subscribers to receive e-mail notification
when a document is added to a subscribed docket(s). For assistance with
any FERC Online service, please e-mail<EMAIL_ADDRESS>or
call<PHONE_NUMBER> (toll free). For TTY, call<PHONE_NUMBER>.

Nathaniel J. Davis, Sr.,
Deputy Secretary.
[FR Doc. 2010-635 Filed 1-14-10; 8:45 am]
BILLING CODE 6717-01-P