Perform Pre-Scoping

Data Fields

Identified Existing Data

Check to verify effective maps, data have been identified

Contacted Communities

Check to verify the communities in proposed project have been contacted

Organization that Contacted Communities

The organization that contacted the communities

Initiated Population of Scoping Tool with Effective Data

Check to verify the effective data has been entered into the scoping tool

Actual or Final Cost $

Cost of just the pre-scoping task

Pre-Scoping Result

Choose to hold the project or to progress on to the scoping phase

Have Potential Obstacles?

If there are potential obstacles (i.e., funding), identify them here

Print this activity | Back to top

Hold Pre-Scoping Project

Data Fields

Do Not Hold, Continue Study

Check this to cancel the hold, move on to creating a case number, and the scoping process

Hold Expires On

The date you wish the task to reappear on your workbench to reevaluate whether a project can be created

Reason For Hold

The reason a hold is being placed on the project.

Print this activity | Back to top

Initiate Study Project

Data Fields

Project Name

County Name, Basin Project Name, etc. that will live for the entire project

Scoping Task Information

Start Date - Baseline Start Date for Scoping task only

End Date - Baseline End Date for Scoping task only

Organization Type - MODHQ, FEMA HQ, Mapping Partner, etc.

Organization Name - Specific name of organization responsible for scoping task

Scoping Negotiated Cost

Amount $ - Cost amount in dollars

Federal Funding Year - The fiscal year the dollars were contributed

Cost Type - Study Contract, Cooperative Agreement, etc.

Contract/Agreement Number - Number of contract this cost is documented in

Task Order Number - Task order number this contract falls under.

Select Area to Study

State - State that your project area is in

County - County that your project area is in

Community - Specific Communities that your project is in. If your project is a county-wide study, select the county-wide option in this drop-down

CID - Community ID number specific to each community in the MIP.

Contact List

FEMA HQ Lead
FEMA HQ Lead
FEMA Regional Engineer
FEMA Regional Floodplain Manager
Mapping Partner Project Lead
RSC Manager

Work Steps

The "Create Project" tab under the MIP workbench is used to create a new study project. At the beginning of the process, you must choose to either begin the study project or enter the pre-scoping process. The pre-scoping process workflow within the MIP is used to delay the scoping activity for a project. After this stage, a project name must be entered. Contract information (organization, baseline cost and schedule, etc.) is entered for the scoping task. After this, the communities affected by the study are entered. Lastly, points of contact for the study are entered. Upon completion of the activity, the MIP will display the newly created project case number.

Tips and Tricks

Use a clear naming convention for project name (i.e., County name, State)

When entering Scoping task contract and schedule information, remember this is ONLY for the scoping task. NOT for the entire project.

When entering scoping costs, remember to click "Add Cost".

When entering affected areas, you can enter single communities at a time, clicking "add area" after each one, you can enter all communities within a county for a countywide study. In either case, verify all community names and CIDs in the affected areas list.

Remember to note the project number after completing the activity.

Print this activity | Back to top

Prepare for Scoping

Data Fields

Scoping Checklist

Check each box to verify the appropriate steps have been followed

Schedule Meetings

Meeting Date - Date of scoping meeting

Meeting Time - Time of scoping meeting

Meeting Location - Location of scoping meeting

Comments - Any comments pertaining to the scoping meeting

Print this activity | Back to top

Conduct Scoping Meeting

Data Fields

Meeting Information

Meeting Date - Date of scoping meeting

Meeting Time - Time of scoping meeting

Meeting Location - Location of scoping meeting

Communities in Attendance - List all communities present at meeting

Ordinances Collected? - Yes or No

Meeting Minutes Collected - Check to verify

Comments - Any comments pertaining to the scoping meeting

Print this activity | Back to top

Finalize Project Scope

Data Fields

Scoping Cost

Scoping Project Completed using Scoping Tool - Check to verify

Federal Fiscal Year - Fiscal year the funds were spent on scoping

FEMA Funds Spent - Amount in dollars spent on scoping for that fiscal year

Project Leverage

Is leverage associated with this task? - Yes or no, leverage contributed to scoping task

Quantity - Amount of leverage

Type - Type of leverage

Contributed By - Organization contributing the leverage

Federal Fiscal Year - Fiscal year the leverage was contributed in

Comments - Any comments associated with that instance of leverage

Select Map Panels Affected by Study

Panel Number(s) - All currently effective map panels will be listed here for the project area. Choose which ones will be affected (superseded)

Select Scoped Tasks

Check off all Data Development tasks that are within scope of the project

Select Areas for Study

Area - Choose each area from the list of communities

Basin Boundary Area - Check to indicate yes

Print this activity | Back to top

Obligate Project Funds

Data Fields

Task Information

Task Name - Choose a task from the drop-down of tasks entered during the scoping process

Task Description - The user can enter a description of the task here, if desired

Affected Areas

Task Area - Choose all areas from the drop-down list for which the task applies to. To add all areas in the list, click the "Add All Areas" button

Contract Information

Planned Task - Indicate whether each task is beyond the planning stage or not

Organization Type - Type of organization that is responsible for completing the task

Organization Name - The name of organization that is responsible for completing the task

Baseline Task Start Date - Current planned start date for task

Baseline Task End Date - Current planned completion date for task

Cost

Cost Type - The category or type of cost for this specific task

Current Negotiated Cost ($) - The negotiated cost for this specific task

Federal Fiscal Year - The fiscal year associated with this specific cost

Contract or Agreement Number - Contract number for this task

Task Order Number - Task Order number this contract falls under

Independent QA

Independent QA Required? - Indicate whether an Independent QA will be required for the task or not.

Organization Type - Type of organization responsible for the QA

Organization Name - Name of organization responsible for the QA

Baseline QA Start Date - Current planned start date for QA

Baseline QA End Date - Current planned completion date for QA

Cost

Cost Type - The category or type of cost for this specific QA task

Current Negotiated Cost ($) - The negotiated cost for this specific QA task

Federal Fiscal Year - The fiscal year associated with this specific cost

Contract or Agreement Number - Contract number for this task

Task Order Number - Task Order number this contract falls under

Work Steps

The Obligate Project Funds activity is where the Study Project Administrator (FEMA/RSC) enters the contract information for the Data Development and Mapping tasks. The user chooses a specific scoped task, enters the area affected, organization/contractor, schedule and cost baselines, and any Independent QA information. If the study calls for a specific task to be performed in the study, but the contract information is not available at this time, the "planned task" button can be checked, and the task will appear under the "Authorize Planned Data Development Activity" where the contract information can be entered at a later date.

Tips and Tricks

"Add Area", "Add Cost", and "Add Task" are all buttons which can be used to enter multiple instances of data. For instance, multiple areas may be added to one task. Multiple cost entries may be added to one task. And, multiple tasks may be added to the screen.

Don't forget to click "Add Area", "Add Cost", and "Add Task" at the appropriate times in order to save the entered data.

When entering large amounts of contract information, and multiple task entries, you may want to periodically click "Save and Close" to save the entered data to the MIP. Then reopen the activity from your workbench to continue adding tasks. Don't use the back button on your browser. Utilize the blue back button in tool.

Print this activity | Back to top

Manage Data Development

Project Information Data Fields

Project Information

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc)

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Current SPI - Schedule Performance Index (pulled from Project Dashboard)

Estimated SPI - Schedule Performance Index (This figure will reflect immediately changes made in the Cost and Schedule Information section below)

Current CPI - Cost Performance Index (pulled from Project Dashboard)

Estimated CPI - Cost Performance Index (This figure will reflect immediately changes made in the Cost and Schedule Information section below)

Develop DFIRM Database (SAMPLE DATA DEVELOPMENT TASK) Data Fields

Task Information

Task Description - Description of the specific Data Development task

Current Negotiated Cost - Current cost estimate for this task

Baseline Task Start Date - Current planned start date for the task

Baseline Task End Date - Current planned end date for the task

Cost and Schedule Information

Actual Start Date - Actual date entered once the task has been started

Actual End Date - Actual end date (this will be disabled until all QA for this activity has been completed)

Actual Cost to Date or Final Cost - This should be updated periodically to reflect the most up to date cost for the task

As of - The date that the cost estimate above applies to

Percent Complete - The current percent complete for this specific task

Production Status

Task Area - Displays each of the areas within the project for which this specific task has been planned/initiated

Workflow Status - Displays the current workflow step pertaining to this specific task within each of the task areas in the table

Projected Preliminary Date - The date the preliminary maps will be distributed. This field is editable until the Distribute Preliminary task is complete

Area Complete - This check box is disabled for each area until the QA for that specific task in that area has been completed

Production Status Icons - Clicking these icons will open a separate window

QA Comments - Appears as a "c" icon in the table

Metadata Validation Results - Appears as a "m" icon in the table

DFIRM DB QA Results - Appears as a "d" icon in the table

Workflow History - Appears as an "i" icon in the table

Comments

Any comments concerning this task

Other Data Development Tasks in This Project

Task Name - Acquire Base Map, Develop Topography, etc

Organization Name - Organization responsible for each task

Baseline Task End Date - Planned completion date for each task

Percent Complete - Completion status for each task

As of - Date upon which the completion status above is based on

QA Task (SAMPLE QA TASK) Data Fields

Task Information

Task Description - Description assigned to each QA task

Current Negotiated Cost - Current estimated cost for the task

Baseline Task Start Date - Planned start date for the task

Baseline Task End Date - Planned end date for the task

Cost and Schedule Information

Actual Start Date - Actual date entered once the task has been started

Actual End Date - Actual end date (this will be disabled until all QA for this activity has been completed)

Actual Cost to Date or Final Cost - - This should be updated periodically to reflect the most up to date cost for the task

As of - The date that the cost estimate above applies to

Percent Complete - The current percent complete for this specific QA task

Production Status

Task Area - Displays each of the areas within the project for which this specific task has been planned/initiated

Workflow Status - Displays the current workflow step pertaining to this specific task within each of the task areas in the table

Projected Preliminary Date - The date the preliminary maps will be distributed. This field is editable until the Distribute Preliminary task is complete

Production Status Icons - Clicking these icons will open a separate window

QA Comments - Appears as a "c" icon in the table

Metadata Validation Results - Appears as a "m" icon in the table

DFIRM DB QA Results - Appears as a "d" icon in the table

Workflow History - Appears as an "i" icon in the table

Comments

Any comments concerning this task

Print this activity | Back to top

Authorize Planned Data Development Task

Data Fields

Task Information

Task Name - Choose a task from the drop-down of tasks entered during the scoping process

Task Description - The user can enter a description of the task here, if desired

Affected Areas

Task Area - Choose all areas from the drop-down list for which the task applies to. To add all areas in the list, click the "Add All Areas" button

Contract Information

Planned Task - Indicate whether each task is beyond the planning stage or not

Organization Type - Type of organization that is responsible for completing the task

Organization Name - The name of organization that is responsible for completing the task

Baseline Task Start Date - Current planned start date for task

Baseline Task End Date - Current planned completion date for task

Cost

Cost Type - The category or type of cost for this specific task

Current Negotiated Cost ($) - The negotiated cost for this specific task

Federal Fiscal Year - The fiscal year associated with this specific cost

Contract or Agreement Number - Contract number for this task

Task Order Number - Task Order number this contract falls under

Independent QA

Independent QA Required? - Indicate whether an Independent QA will be required for the task or not.

Organization Type - Type of organization responsible for the QA

Organization Name - Name of organization responsible for the QA

Baseline QA Start Date - Current planned start date for QA

Baseline QA End Date - Current planned completion date for QA

Cost

Cost Type - The category or type of cost for this specific QA task

Current Negotiated Cost ($) - The negotiated cost for this specific QA task

Federal Fiscal Year - The fiscal year associated with this specific cost

Contract or Agreement Number - Contract number for this task

Task Order Number - Task Order number this contract falls under

Print this activity | Back to top

Acquire Base Map

Data Fields

Project and Task Information:

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc.)

Task Description - Description of the specific task underway in the MIP

Baseline Task End Date - The projected date of completion for this specific task

Projected Preliminary Date - The current proposed date for the release of preliminary maps

Comments from Workflow QA - Comments from Workflow QA field is visible only if QA has failed. The "QA Report" link is visible if the report is present

Submission Status:

Metadata Profile Validation - Displays whether the metadata profile meets the requirements or not

Submit Data:

Submission Contents - This is where the data is uploaded into the portlet

Print this activity | Back to top

Develop DFIRM Database

Data Fields

Project and Task Information:

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc.)

Task Description - Description of the specific task underway in the MIP

Baseline Task End Date - The projected date of completion for this specific task

Projected Preliminary Date - The current proposed date for the release of preliminary maps

Comments from Workflow QA - Comments from Workflow QA field is visible only if QA has failed. The "QA Report" link is visible if the report is present

Submission Status:

Metadata Profile Validation - Displays whether the metadata profile meets the requirements or not

DFIRM DB QA Validation - Displays the status of the DFIRM Database submitted for automated validation.

Submit Data:

Submission Contents - This is where the data is uploaded into the portlet

Print this activity | Back to top

Develop Hydraulic Data

Data Fields

Project and Task Information:

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc.)

Task Description - Description of the specific task underway in the MIP

Baseline Task End Date - The projected date of completion for this specific task

Projected Preliminary Date - The current proposed date for the release of preliminary maps

Comments from Workflow QA - Comments from Workflow QA field is visible only if QA has failed. The "QA Report" link is visible if the report is present

Submission Status:

Metadata Profile Validation - Displays whether the metadata profile meets the requirements or not

Submit Data:

Submission Contents - This is where the data is uploaded into the portlet

Task Information

Actual Linear Miles of Detailed Study

Actual Linear Miles of Limited Detailed Study

Actual Linear Miles of Approximate Study

Hydraulic Models or Methods Used

Select the model or method from the drop-down list, or choose "Other" in order to manually enter the model/method into the "Other" data field.

A separate entry will be generated for each model/method. In the upper-right hand corner of each entry will be buttons for modifying or deleting the model/method entry. The "tablet" icon is used to modify the entry. The "X" button will delete that entry.

Print this activity | Back to top

Develop Hydrologic Data

Data Fields

Project and Task Information:

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc.)

Task Description - Description of the specific task underway in the MIP

Baseline Task End Date - The projected date of completion for this specific task

Projected Preliminary Date - The current proposed date for the release of preliminary maps

Comments from Workflow QA - Comments from Workflow QA field is visible only if QA has failed. The "QA Report" link is visible if the report is present

Submission Status:

Metadata Profile Validation - Displays whether the metadata profile meets the requirements or not

Submit Data:

Submission Contents - This is where the data is uploaded into the portlet

Task Information

Square Miles of Drainage Area Studied

Hydrologic Models or Methods Used

Select the model or method from the drop-down list, or choose "Other" in order to manually enter the model/method into the "Other" data field.

A separate entry will be generated for each model/method. In the upper-right hand corner of each entry will be buttons for modifying or deleting the model/method entry. The "tablet" icon is used to modify the entry. The "X" button will delete that entry.

Print this activity | Back to top

Develop Topographic Data

Data Fields

Project and Task Information:

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc.)

Task Description - Description of the specific task underway in the MIP

Baseline Task End Date - The projected date of completion for this specific task

Projected Preliminary Date - The current proposed date for the release of preliminary maps

Comments from Workflow QA - Comments from Workflow QA field is visible only if QA has failed. The "QA Report" link is visible if the report is present

Submission Status:

Metadata Profile Validation - Displays whether the metadata profile meets the requirements or not

Submit Data:

Submission Contents - This is where the data is uploaded into the portlet

Print this activity | Back to top

Perform Alluvial Fan Analysis

Data Fields

Project and Task Information:

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc.)

Task Description - Description of the specific task underway in the MIP

Baseline Task End Date - The projected date of completion for this specific task

Projected Preliminary Date - The current proposed date for the release of preliminary maps

Comments from Workflow QA - Comments from Workflow QA field is visible only if QA has failed. The "QA Report" link is visible if the report is present

Submission Status:

Metadata Profile Validation - Displays whether the metadata profile meets the requirements or not

Submit Data:

Submission Contents - This is where the data is uploaded into the portlet

Task Information

Alluvial Fan Landforms Exist?

Active Alluvial Fan?

Inactive Alluvial Fan?

Are There Structures Associated With The Alluvial Fan?

Alluvial Fan Models or Methods Used

Select the model or method from the drop-down list, or choose "Other" in order to manually enter the model/method into the "Other" data field.

Enter a description of the model or method into the "Description" field, then click on "Add Model or Method" to add it to the list. Repeat for each model or method used

A separate entry will be generated for each model/method. In the upper-right hand corner of each entry will be buttons for modifying or deleting the model/method entry. The "tablet" icon is used to modify the entry. The "X" button will delete that entry.

Print this activity | Back to top

Perform Coastal Analysis

Data Fields

Project and Task Information:

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc.)

Task Description - Description of the specific task underway in the MIP

Baseline Task End Date - The projected date of completion for this specific task

Projected Preliminary Date - The current proposed date for the release of preliminary maps

Comments from Workflow QA - Comments from Workflow QA field is visible only if QA has failed. The "QA Report" link is visible if the report is present

Submission Status:

Metadata Profile Validation - Displays whether the metadata profile meets the requirements or not

Submit Data:

Submission Contents - This is where the data is uploaded into the portlet

Task Information

If there are CBRS Zones, you will be prompted to answer the number of panels with CBRS zones

If there are costal structures, you will be prompted to enter information about the structure's stability

Coastal Models or Methods Used

Select the model or method from the drop-down list, or choose "Other" in order to manually enter the model/method into the "Other" data field.

Enter a description of the model or method into the "Description" field, then click on "Add Model or Method" to add it to the list. Repeat for each model or method used.

Enter the horizontal and vertical datum used for each model/method

A separate entry will be generated for each model/method. In the upper-right hand corner of each entry will be buttons for modifying or deleting the model/method entry. The "tablet" icon is used to modify the entry, the "X" button will delete that entry

Print this activity | Back to top

Perform Field Survey

Data Fields

Project and Task Information:

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc.)

Task Description - Description of the specific task underway in the MIP

Baseline Task End Date - The projected date of completion for this specific task

Projected Preliminary Date - The current proposed date for the release of preliminary maps

Comments from Workflow QA - Comments from Workflow QA field is visible only if QA has failed. The "QA Report" link is visible if the report is present

Submission Status:

Metadata Profile Validation - Displays whether the metadata profile meets the requirements or not

Submit Data:

Submission Contents - This is where the data is uploaded into the portlet

Print this activity | Back to top

Perform Floodplain Mapping

Data Fields

Project and Task Information:

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc.)

Task Description - Description of the specific task underway in the MIP

Baseline Task End Date - The projected date of completion for this specific task

Projected Preliminary Date - The current proposed date for the release of preliminary maps

Comments from Workflow QA - Comments from Workflow QA field is visible only if QA has failed. The "QA Report" link is visible if the report is present

Submission Status:

Metadata Profile Validation - Displays whether the metadata profile meets the requirements or not

Submit Data:

Submission Contents - This is where the data is uploaded into the portlet

Task Information

Vertical Datum Conversion Performed?

Total Linear Miles of Detailed Study

Total Linear Miles of Limited Detailed Study

Total Linear Miles of Approximate Study

Total Linear Miles of Redelineation

Print this activity | Back to top

Setup Map Production

Data Fields

Mapping Tasks

Organization Type - Type of organization that is responsible for completing the task

Organization Name - The name of organization that is responsible for completing the task

Baseline Task Start Date - Current planned start date for task

Baseline Task End Date - Current planned completion date for task

Cost

Cost Type - The category or type of cost for this specific task

Current Negotiated Cost ($) - The negotiated cost for this specific task

Federal Fiscal Year - The fiscal year associated with this specific cost

Contract or Agreement Number - Contract number for this task

Task Order Number - Task Order number this contract falls under

Print this activity | Back to top

Manage Preliminary Map Production

Data Fields

Task Information

Task Description - Description of the Produce Preliminary Map Products Task

Current Negotiated Cost - Current cost estimate for this task

Baseline Task Start Date - Current planned start date for the task

Baseline Task End Date - Current planned end date for the task

Projected Preliminary Date - Planned date for distribution of preliminary map products

Cost and Schedule Information

Actual Start Date - Actual date entered once the task has been started

Actual End Date - Actual end date (this will be disabled until all QA for this activity has been completed)

Actual Cost to Date or Final Cost - This should be updated periodically to reflect the most up to date cost for the task

As of - The date that the cost estimate above applies to

Percent Complete - The current percent complete for this specific task

Production Status

Workflow Status - Displays the current workflow step pertaining to the Produce Preliminary Map Products task

QA Comments - Comments from the QA of Preliminary Map Products will appear here, if they have been entered

Production Status Icons - Clicking these icons will open a separate window

Metadata Validation Results - Appears as a "m" icon in the table

DFIRM DB QA Results - Appears as a "d" icon in the table

Workflow History - Appears as an "i" icon in the table

Print this activity | Back to top

Produce Preliminary Map Products

Data Fields

Project and Task Information

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc.)

Task Description - Description of the specific task underway in the MIP

Baseline Task End Date - The projected date of completion for this specific task

Projected Preliminary Date - The current proposed date for the release of preliminary maps

Comments from Workflow QA - Comments from Workflow QA field is visible only if QA has failed. The "QA Report" link is visible if the report is present

Submission Status

Metadata Profile Validation - Displays whether the metadata profile meets the requirements or not

DFIRM DB QA Validation - Displays the status of the DFIRM Database submitted for automated validation.

Submit Data

Submission Contents - This is where the data is uploaded into the portlet

Analysis

Number of Printed Panels - Number of preliminary panels, including the index panel

Print this activity | Back to top

Distribute Preliminary Map Products

Data Fields

Project and Task Information:

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc.)

Task Description - Description of the specific task undergoing QA

Baseline Task End Date - The projected date of completion for this specific task

Projected Preliminary Date - The current proposed date for the release of preliminary maps

Community Information

Date Preliminary Mailed - The actual date the maps were mailed out. Can be entered manually or by clicking on the calendar function

Community Name - The name of the community the maps were sent to

BFE Changes - Yes or No

Advanced Copies Sent - Yes or No

Preliminary Maps Distributed to - The person the maps were sent to

Print this activity | Back to top

Setup Post Preliminary Processing

Data Fields

Post Preliminary Processing

Organization Type - Type of organization that is responsible for completing the task

Organization Name - The name of organization that is responsible for completing the task

Baseline Task Start Date - Current planned start date for task

Baseline Task End Date - Current planned completion date for task

Cost

Cost Type - The category or type of cost for this specific task

Current Negotiated Cost ($) - The negotiated cost for this specific task

Federal Fiscal Year - The fiscal year associated with this specific cost

Contract or Agreement Number - Contract number for this task

Task Order Number - Task Order number this contract falls under

Print this activity | Back to top

Manage Post Preliminary Map Products

Data Fields

Project Information

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc.)

Current SPI - Schedule Performance Index (pulled from Project Dashboard.)

Estimated SPI - Schedule Performance Index this figure will reflect immediately changes made in the Cost and Schedule Information section below

Current CPI - Cost Performance Index, pulled from Project Dashboard

Estimated CPI - Cost Performance Index, this figure will reflect immediately changes made in the Cost and Schedule Information section below

Print this activity | Back to top

Determine Community Meeting Schedule

Data Fields

Meeting Schedule

Will You Be Holding Community Meetings - Answer Yes or No for each community

Meeting Date - If yes, enter the meeting date for each community

Intermediate Meetings are required in this study - Check the box to indicate meetings are required. If checked, the "Prepare and Hold Intermediate Meetings" activity will appear on your workbench upon completion of this activity

Print this activity | Back to top

Prepare and Hold Intermediate Meetings

Data Fields

Meeting List

Community - Choose the community that you are assigning meeting data for

Meeting Date - Date of the meeting

Meeting Time - Time of the meeting

Meeting Location - Meeting Location (Town Hall, Library, etc)

Meeting Attended - Yes or No. Was the meeting attended by anyone? If not, why was the meeting not attended

Meeting Minutes Collected - Check to verify, meeting minutes are required

Minutes Submitted to

Name - Name of the person the minutes were submitted to

Organization - Organization the person belongs to that held the minutes (Mapping Partner, CTP, etc)

Meeting Summary - Enter a brief summary of what was accomplished/discussed during the meeting

Print this activity | Back to top

Confirm Community Meeting List

Data Fields

Meeting List

Approve Meeting List - Click to Approve or Reject the Meeting List

Comments - Enter any comments concerning the community meeting list

Print this activity | Back to top

Prepare Community Meetings

Data Fields

Prepare Community Meetings

Notified Participants - Check to verify this has been done

Contacted the community - Check to verify this has been done

Contacted FEMA/assigned post-prelim organization to determine level of community outreach support required - Check to verify this has been done

Print this activity | Back to top

Hold Community Meetings

Data Fields

Hold Community Meetings

Community - Choose the community that you are assigning meeting data for

Meeting Date - Date of the meeting

Meeting Time - Time of the meeting

Meeting Location - Meeting Location (Town Hall, Library, etc)

Meeting Attended - Yes or No. Was the meeting attended by anyone

Meeting Minutes Collected - Check to verify, meeting minutes are required

Minutes Submitted to

Name - Name of the person the minutes were submitted to

Organization - Organization the person belongs to that held the minutes (Mapping Partner, CTP, etc)

Meeting Summary - Enter a brief summary of what was accomplished/discussed during the meeting

Print this activity | Back to top

Determine If Appeal Period is Required

Data Fields

Appeal Determination

Appeal Period Required - For each community displayed to be within the study, indicate whether an appeal period is required by checking the box or not

Print this activity | Back to top

Produce Final Map Products

Data Fields

Data Submission

Baseline Task End Date - The projected date of completion for this specific task

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc)

Comments from Workflow QA - Comments from Workflow QA field is visible only if QA has failed. The "QA Report" link is visible if the report is present

DFIRM DB QA Validation - Displays the status of the DFIRM Database submitted for automated validation.

Metadata Profile Validation - Displays whether the metadata profile meets the requirements or not

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Projected Preliminary Date - The current proposed date for the release of preliminary maps

Submission Contents - This is where the data is uploaded into the portlet

Task Description - Description of the specific task underway in the MIP

Analysis

Number of Printed Panels - Number of map panels in final submission

Print this activity | Back to top

Submit MSC Deliverable

Data Fields

Data Submission

Baseline Task End Date - The projected date of completion for this specific task

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc)

Checklist of MSC Deliverable GPO Package - Read through checklist to ensure entire submittal package is present

Comments from Workflow QA - Comments from Workflow QA field is visible only if QA has failed. The "QA Report" link is visible if the report is present

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Projected Preliminary Date - The current proposed date for the release of preliminary maps

Submission Contents - This is where the data is uploaded into the portlet

Task Description - Description of the specific task underway in the MIP

Print this activity | Back to top

Prepare LFD Docket

Data Fields

Task Information

Baseline Task End Date - The projected date of completion for this specific task

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc)

CID - Community ID number specific to each community in the MIP

Comments - Comments may be sent along to the reviewer here, if desired

Comments from Docket Review - Comments are only visible if LFD Docket has previously failed review

Community Name - Any State or area or political subdivision thereof, or any Indian tribe or authorized tribal organization, or Alaska Native village or authorized native organization, which has the authority to adopt and enforce floodplain management regulations for the areas within its jurisdiction

Final SOMA - Clicking on the SOMA links for each of the communities will open in a separate browser window

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Projected Effective Date - This date dynamically changes as the projected LFD date is chosen above. This date is 6 months after the projected LFD date

Projected LFD Date - Choose the projected date from the drop-down list

Task Description - Description of the specific task underway in the MIP

New 60.3 Code - This drop-down list requires the user to identify the level of ordinance a community will have to adopt before the new maps become effective. The specific requirements are in Section 60.3 of the NFIP regulations, and apply to communities as follows:

60.3 (a) - FEMA has not provided any maps or data

60.3 (b) - FEMA has provided a map with approximate A Zones

60.3 (c) - FEMA has provided a FIRM with BFEs

60.3 (d) - FEMA has provided a FIRM with BFEs and a map that shows a floodway

60.3 (e) - FEMA has provided a FIRM that shows coastal high hazard areas (V Zones)

Print this activity | Back to top

Review LFD Docket

Data Fields

Task Information

Approve or Reject LFD Docket - Choose to approve or reject the LFD docket

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc)

Task Description - Description of the specific task underway in the MIP

Baseline Task End Date - The projected date of completion for this specific task

CID - Community ID number specific to each community in the MIP

Comments - Comments may be sent along to the preparer of the docket here, if desired. If the docket was rejected, comments are required

Comments from Docket Review - Comments are only visible if LFD Docket has previously failed review

Comments from FEMA Approver - Any comments left by the previous FEMA Approver will be displayed here

Comments from LFD Preparation - Any comments left by the user that prepared the LFD Docket will be displayed here

Community Name - Any State or area or political subdivision thereof, or any Indian tribe or authorized tribal organization, or Alaska Native village or authorized native organization, which has the authority to adopt and enforce floodplain management regulations for the areas within its jurisdiction

DFIRM Status - The current status of the DFIRM database QA. If completed, a link will be available to review the results

Final SOMA - Clicking on the SOMA links for each of the communities will open in a separate browser window

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Projected Effective Date - This date dynamically changes as the projected LFD date is chosen above. This date is 6 months after the projected LFD date

Projected LFD Date - The current proposed date chosen by the preparer of the LFD docket

Reviewer Name - The user completing this review

Print this activity | Back to top

Approve LFD Docket

Data Fields

Task Information

Approve or Reject LFD Docket - Choose to approve or reject the LFD Docket.

Baseline Task End Date - The projected date of completion for this specific task.

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc).

CID - The Community Identification (CID) number is a unique 6 digit number assigned to each community that has been identified under the National Flood Insurance Program. The CID number is shown on each FIRM panel and is the first 6 digits of all non-countywide format FIRM panel numbers.

Comments - Comments may be sent along to the preparer of the docket here, if desired. If the docket was rejected, comments are required.

Comments from Docket Review - Any comments left by the previous docket reviewer will be displayed here.

Community Name - Any State or area or political subdivision thereof, or any Indian tribe or authorized tribal organization, or Alaska Native village or authorized native organization, which has the authority to adopt and enforce floodplain management regulations for the areas within its jurisdiction.

DFIRM Status - The current status of the DFIRM database QA. If completed, a link will be available to review the results.

Final SOMA - Clicking on the SOMA links for each of the communities will open in a separate browser window.

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project.

Projected Effective Date - This date dynamically changes as the projected LFD date is chosen above. This date is 6 months after the projected LFD date.

Projected LFD Date - The current proposed date chosen by the preparer of the LFD docket.

Reviewer Name - The user completing this review.

Task Description - Description of the specific task underway in the MIP.

Print this activity | Back to top

Distribute LFD Letter

Data Fields

Task Information

Baseline Task End Date - The projected date of completion for this specific task.

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc).

CID - The Community Identification (CID) number is a unique 6 digit number assigned to each community that has been identified under the National Flood Insurance Program. The CID number is shown on each FIRM panel and is the first 6 digits of all non-countywide format FIRM panel numbers.

Comments from Docket Review - Comments are only visible if LFD Docket has previously failed review.

Community Name - Any State or area or political subdivision thereof, or any Indian tribe or authorized tribal organization, or Alaska Native village or authorized native organization, which has the authority to adopt and enforce floodplain management regulations for the areas within its jurisdiction.

Effective Date - The date on which the new maps and FIS will become effective. This date is 6 months after the LFD date.

Final SOMA - Clicking on the SOMA links for each of the communities will open in a separate browser window.

LFD Date - The current date chosen by the preparer of the LFD docket. This date is now finalized.

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project.

Task Description - Description of the specific task underway in the MIP.

Print this activity | Back to top

Create Final Rule for Federal Register

Data Fields

Create Rule

Date Sent to FEMA for Review - Date the final register publication was sent to FEMA for review.

Federal Register Publication Date - Date the rule was published in the federal register.

Print this activity | Back to top

Validate Content Submission

Data Fields

Project and Task Information:

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Task Under QA - The specific task that is undergoing QA

Task Description - Description of the specific task undergoing QA

Task Completed By - User that completed the task undergoing QA

Comments From Task - Any comments sent by the user above will be displayed here.

QA Status

Approve or Reject QA? - Choose approve or reject

Reviewers Name: This is the MIP Username for whoever is approving/rejecting

Comments: Any comments concerning the approval/rejection

Print this activity | Back to top

Perform Independent QA

Data Fields

Project and Task Information:

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Task Under QA - The specific task that is undergoing QA

Task Description - Description of the specific task undergoing QA

Task Completed By - User that completed the task undergoing QA

Schedule Information

Baseline QA Start Date - The projected date when QA of this specific task will start

Baseline QA End Date - The projected date when QA of the specific task will be completed

Reviewer Name - Name of the user that is performing this specific QA

QA Status

Projected Preliminary Date - The projected date that the preliminary maps will be completed

Comments From Task - Any comments sent by the user that performed the data development task will be displayed here

Approve or Reject QA?

Comments: Any comments the reviewer has concerning the QA can be entered here

File Submission

File Uploaded: Displays a link to the most recent file uploaded

Choose a file to Upload: The user can upload any file that is relevant to the QA

Print this activity | Back to top

Perform National DFIRM QA

Data Fields

Project and Task Information:

Project Name - A descriptive name given by the requestor or Process Administrator to distinguish the project

Task Description - Description of the specific task undergoing QA

Task Completed By - User that completed the task undergoing QA

Projected Effective Date - The projected date the maps will go effective. This is entered by the user that submitted the MSC deliverables

QA Status

Reviewer Name - The name of the user doing this particular QA

Review Start Date - Enter the date the QA review was started on

Review End Date - Enter the date the QA review was completed on

Approve or Reject QA?

Comments: Any comments the reviewer has concerning the QA can be entered here

File Submission

File Uploaded: Displays a link to the most recent file uploaded.

Choose a file to Upload: The user can upload any file that is relevant to the QA

Print this activity | Back to top

Create BFE Notice

Data Fields

BFE Notice

Second Publication Date - This is the date the BFE Notice will appear in the newspaper for the second time

Newspaper - Name of the newspaper it appears in

Prepared By - Enter the MIP username of the person who prepared the BFE notice

BFEs on the Web Notification - Indicate whether a notice was placed on the BFEs on the Web address

Print this activity | Back to top

Approve BFE Notice

Data Fields

Approve or Reject

Approve BFE Notice - Indicate whether the BFE Notice is being approved or rejected

Comments - Enter any comments regarding the BFE notice approval/denial

Print this activity | Back to top

Review BFE Docket

Data Fields

Approve or Reject

Approve Docket - Indicate whether the docket is approved or rejected

Reviewer Name - Enter the MIP username of the reviewer. The current username is pre-populated

Comments - Enter any comments regarding the review of the BFE docket

Print this activity | Back to top

Distribute BFE Notice

Data Fields

BFE Notice

Date Notice Sent to Communities - Enter the date the notice was mailed directly to communities

Print this activity | Back to top

Receive BFE Publication Affidavit

Data Fields

Receive Affidavit

Newspaper - Name of the newspaper the BFE Notice was published in

Affidavit Date - The date that appeared on the affidavit

1st Actual Publication Date - Date on which the affidavit first appeared in the newspaper

2nd Actual Publication Date - Date on which the affidavit was published twice. (This officially starts the 90-day appeal period)

BFEs on the Web Posting Date - Enter the date the notice was posted on BFEs on the Web

Print this activity | Back to top

Prepare Federal Register Proposed Rule

Data Fields

Prepare Rule

Date Sent to FEMA for Review - Date the federal registry entry was sent to FEMA for review

Federal Register Publication Date - The official date the entry was published in the register

Print this activity | Back to top

Record Appeal or Protest

Data Fields

Record Appeals or Protests

Community - Choose the community from which the appeal was received

Type - Appeal or protest

Date Received - Date the appeal was received

Acknowledgment Date - Date of the letter to the appellant acknowledging the appeal

Date Community Contacted - Date the community was contacted by the organization responsible for handling the appeals

Appellant Name - Name of the person filing the appeal

Appellant Type - Community (official), individual property owner, etc

Comments - Enter any comments pertaining to each appeal

Print this activity | Back to top

Review Appeal or Protest

Data Fields

Appeal or Protest Resolution

Recommendation Summary - For each appeal entry, enter the recommendation summary

Appeal or Protest Review

Reviewed with FEMA Contact - Check to verify this was done

Date of Review - Date the appeal recommendation was reviewed with the FEMA contract

Are any appeals or protests valid - Indicate whether any appeals are valid

Print this activity | Back to top

Prepare Appeal Package

Data Fields

Package Contents

Resolution Letter - Check to verify a resolution letter was prepared for the package

Revised Preliminary FIRM - Check here to indicate the appeal resulted in a revised preliminary FIRM

Revised Preliminary FIS Report - Check here to indicate the appeal resulted in revised preliminary FIRM

Backup Material - Check here to indicate the appeals resulted in revised backup material

Other - Enter any comments concerning the results of the appeals

Date Package Sent to FEMA - Date the appeal package was sent to FEMA

Comments - Any other comments the user would like to enter on the Appeals Package

Print this activity | Back to top

Review Appeal Resolution

Data Fields

Approve or Reject

Reviewer Name - Name of the reviewer of the appeal package (FEMA)

Date Returned - Date after the review the package was returned

Approve/Reject - Choose to approve or reject the appeals package

Comments - Enter any comments regarding the approval/rejection of the package

Print this activity | Back to top

Distribute Appeal Resolution

Data Fields

Distribute Resolution

Distribution Date - Date the appeals package was distributed

Print this activity | Back to top

Check Adoption Status

Data Fields

Check Adoption Status

Ordinance Adopted - For each community, the user will check in FEMA's CIS to see whether the community has adopted the new regulations that come along with the new effective maps

Ordinance Adoption Date - The date from CIS that the ordinance was adopted by the community (if applicable).

Automatic Adoption - Check here to indicate the community participates in the Automatic Adoption program.

Comments - Enter any comments concerning the adoption status here.

Print this activity | Back to top

Prepare 90 Day Suspension Notification

Data Fields

Prepare Notification

Communities Not Yet Adopted - This list displays all communities in the project which have not yet adopted the new regulations. These communities will receive a 90-day suspension notification

Prepared By - This is the MIP username of the person preparing the 90-day notifications.

Date Sent to FEMA for Review - Date the notifications were sent to FEMA for review before distributing to the communities.

Internal Review Performed - Check this box to verify that an internal review was performed on the notifications before they were sent to FEMA for the final review.

Print this activity | Back to top

Review 90 Day Suspension Notification

Data Fields

Review Notification

Communities to be Notified - This list displays all communities which will receive the notification.

Approve Notification - Click Yes or No to indicate approval of notification.

Date Sent to FEMA for Review - This is the date entered by the preparer that they sent the notification to FEMA for review.

Reviewer Name - This is the MIP username of the person performing the review of the notification.

Date Returned - Enter the date that the reviewer sent the notification back to the preparer for distribution to the communities.

Comments - Enter any comments concerning the review of the notification.

Print this activity | Back to top

Distribute 90 Day Suspension Notification

Data Fields

Distribute Notification

Distribute Date - Enter the date the notifications were mailed out to the communities.

Letter Date - Enter the actual date that appears on the notifications.

Print this activity | Back to top

Recheck Adoption Status

Data Fields

Recheck Adoption Status

Ordinance Adopted - For each community, the user will check in FEMA's CIS to see whether the community has adopted the new regulations that come along with the new effective maps.

Ordinance Adoption Date - The date from CIS that the ordinance was adopted by the community (if applicable).

Comments - Enter any comments concerning the adoption status here.

Print this activity | Back to top

Prepare 30 Day Suspension Notification

Data Fields

Prepare Notification

Communities Not Yet Adopted - This list displays all communities in the project which have not yet adopted the new regulations. These communities will receive a 30-day suspension notification.

Prepared By - This is the MIP username of the person preparing the 30-day notifications.

Date Sent to FEMA for Review - Date the notifications were sent to FEMA for review before distributing to the communities.

Internal Review Performed - Check this box to verify that an internal review was performed on the notifications before they were sent to FEMA for the final review.

Print this activity | Back to top

Review 30 Day Suspension Notification

Data Fields

Review Notification

Communities to be Notified - This list displays all communities which will receive the notification.

Approve Notification - Click Yes or No to indicate approval of notification.

Date Sent to FEMA for Review - This is the date entered by the preparer that they sent the notification to FEMA for review.

Reviewer Name - This is the MIP username of the person performing the review of the notification.

Date Returned - Enter the date that the reviewer sent the notification back to the preparer for distribution to the communities.

Comments - Enter any comments concerning the review of the notification.

Print this activity | Back to top

Distribute 30 Day Suspension Notification

Data Fields

Distribute Notification

Distribute Date - Enter the date the notifications were mailed out to the communities.

Letter Date - Enter the actual date that appears on the notifications.

Print this activity | Back to top

Confirm Adoption Status

Data Fields

Confirm Adoption Status

Ordinance Adopted - For each community, the user will check in FEMA's CIS to see whether the community has adopted the new regulations that come along with the new effective maps.

Ordinance Adoption Date - The date from CIS that the ordinance was adopted by the community (if applicable).

Comments - Enter any comments concerning the adoption status here.

Print this activity | Back to top

Prepare Revalidation Letter

Data Fields

Task Information

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc.).

CID - The Community Identification (CID) number is a unique 6 digit number assigned to each community that has been identified under the National Flood Insurance Program. The CID number is shown on each FIRM panel and is the first 6 digits of all non-countywide format FIRM panel numbers.

Comments - Comments can be left here by the preparer. The comments will be displayed for the next user that approves or reviews the revalidation docket.

Comments from Docket Review - Any comments left from a previous review of the revalidation docket will be displayed here.

Community Name - Any State or area or political subdivision thereof, or any Indian tribe or authorized tribal organization, or Alaska Native village or authorized native organization, which has the authority to adopt and enforce floodplain management regulations for the areas within its jurisdiction.

County - A division within a State, usually encompassing one or more cities or towns. Selecting a State populates the County field.

LOMC Information - This field will appear separate for each community in the project. Review the number of LOMC's on each community's revalidation letter.

Number of LOMC Revalidation Categorized - Number of LOMC's within the community that are categorized on the revalidation letter.

Number of LOMC Uncategorized - Number of LOMC's within the community that appeared on the SOMA list but are uncategorized according to the revalidation letter.

Revalidation Letter Date - The date that the Revalidation letter becomes effective. This date is usually 1 day after the new FIRM Effective date.

State - Any state, the District of Columbia, the territories and possessions of the United States, the Commonwealth of Puerto Rico, and the Trust Territory of the Pacific Islands.

View Revalidation Letter - View the revalidation letter for each of the communities within the project.

Print this activity | Back to top

Review Revalidation Docket

Data Fields

Task Information

Approve or Reject Docket - Choose to approve or reject the revalidation docket.

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc.).

CID - The Community Identification (CID) number is a unique 6 digit number assigned to each community that has been identified under the National Flood Insurance Program. The CID number is shown on each FIRM panel and is the first 6 digits of all non-countywide format FIRM panel numbers.

Comments - Comments can be left here by the reviewer. If the docket is rejected, then Comments is required field.

Comments from FEMA Approver - Any previous comments made by the FEMA approver will appear here.

Comments from Revalidation Preparation - Any comments from the user that prepared the revalidation letter will appear here.

Community Name - Any State or area or political subdivision thereof, or any Indian tribe or authorized tribal organization, or Alaska Native village or authorized native organization, which has the authority to adopt and enforce floodplain management regulations for the areas within its jurisdiction.

County - A division within a State, usually encompassing one or more cities or towns. Selecting a State populates the County field.

LOMC Information - This field will appear separate for each community in the project. Review the number of LOMC's on each community's revalidation letter.

Number of LOMC Revalidation Categorized - Number of LOMC's within the community that are categorized on the revalidation letter.

Number of LOMC Uncategorized - Number of LOMC's within the community that appeared on the SOMA list but are uncategorized according to the revalidation letter.

Revalidation Letter Date - The date that the Revalidation letter becomes effective. This date is always 1 day after the new FIRM Effective date.

Reviewer Name - The user completing this review.

State - Any state, the District of Columbia, the territories and possessions of the United States, the Commonwealth of Puerto Rico, and the Trust Territory of the Pacific Islands.

View Revalidation Letter - View the revalidation letter for each of the communities within the project.

Print this activity | Back to top

Approve Revalidation Docket

Data Fields

Task Information

Approve or Reject Docket - Choose to approve or reject the revalidation docket.

Case Number - The case number assigned to a project. Typically consists of Year, Region, a sequential number, and a letter indicating the type of project (P for LOMR, A for LOMA, etc.).

CID - The Community Identification (CID) number is a unique 6 digit number assigned to each community that has been identified under the National Flood Insurance Program. The CID number is shown on each FIRM panel and is the first 6 digits of all non-countywide format FIRM panel numbers.

Comments - Comments can be left here by the reviewer. If the docket is rejected, then Comments is required field.

Comments from Docket Review - Any comments left from a previous review of the revalidation docket will be displayed here.

Community Name - Any State or area or political subdivision thereof, or any Indian tribe or authorized tribal organization, or Alaska Native village or authorized native organization, which has the authority to adopt and enforce floodplain management regulations for the areas within its jurisdiction.

County - A division within a State, usually encompassing one or more cities or towns. Selecting a State populates the County field.

LOMC Information - This field will appear separate for each community in the project. Review the number of LOMC's on each community's revalidation letter.

Number of LOMC Revalidation Categorized - Number of LOMC's within the community that are categorized on the revalidation letter.

Revalidation Letter Date - The date that the Revalidation letter becomes effective. This date is usually 1 day after the new FIRM Effective date.

Reviewer Name - The user completing this review.

State - Any state, the District of Columbia, the territories and possessions of the United States, the Commonwealth of Puerto Rico, and the Trust Territory of the Pacific Islands.

View Revalidation Letter - View the revalidation letter for each of the communities within the project.

Print this activity | Back to top

Distribute Revalidation Letter

Data Fields

Distribute Revalidation Letter

Distribute Revalidation Letter By - The date by which the letter should be mailed to the communities

Date Letter Sent to Communities - The actual date the letters were sent out to the communities

Print this activity | Back to top