Project Studies Workbench

The Project Studies Workbench is the launching point for all Project Level Access Users. This Workbench will allow Project Level Access users to create, edit, assign, and track any assigned MIP Studies Projects or Tasks. Project Access Level Users can populate the Project Studies Workbench by searching individual case number or by selecting the View All Projects link. Once the table is populated sort by selecting the table headers or filter by utilizing the search bar.

Task Workbench

The Task Studies Workbench is the launching point for all MIP Users assigned to a Task. The Task Studies Workbench allows users to edit, assign, and track any assigned MIP Studies Tasks. For Task +EV and Task Access Level users only, the Tasks assigned to the user and have a status of In Progress or New will be visible on the Task Studies Workbench. The Filtered option is selected by default, which displays an empty table. Users can view individual Tasks by entering a Case Number or multiple Tasks by selecting Active or Completed. Only Project Access Level users can view completed Tasks on this workbench. Sort by selecting the table headers or filter by utilizing the search bar.

The Studies Task Workbench can be customized based on user preferences. Users can select the Customize Display button and then choose any or all of the following Task Details: Task Type, Task Status, Assigned To, Task Organization, Task Last Modified Date, and Task Created Date. Once saved, the customized display settings will be retained until any further changes are made. Users can view Details for individual Tasks by selecting the icon to the left of each Case Number.

Task+EV Workbench

The Task+EV Studies Workbench, labeled as the Track Progress Workbench, is accessible only for those that have Task+EV access. The Track Progress Workbench is the launching point for all MIP Users who have been tasked to track cost related information. The Track Progress Workbench allows users to edit the Actual Start & End Date, Percentage Complete, Dollars Spent, and As of Date for each selected Task. Sort by selecting the table headers or filter by utilizing the search bar.

Tasks appear on a user's Track Progress Workbench as soon as they are assigned and remain on that user's Track Progress Workbench until 90 days after the completion and 90 days after 100% progress complete.

The Track Task Progress Workbench can be customized based on user preferences. The Filtered option is selected by default, which displays an empty table. Users can view individual Tasks by entering a Case Number or multiple Tasks by selected Active, Recently Completed, or All. Sort by selecting the table headers or filter by utilizing the search bar. Users can select the Customize Display button and then choose any or all of the following Task Details: Project Name, Purchase Name, Task Type, Type Name, Task Description, Geography, Percent Complete, Dollars Spent, As of Date, Baseline Start Date, Baseline End Date, Negotiated Cost, Actual Start Date, Actual End Date, and Projected Date (LFD, Preliminary). Once saved, the customized display settings will be retained until any further changes are made. Users can view Details for individual Tasks by selecting the icon to the left of each Case Number.

Task+EV users can view and update percent complete and dollars spent for Tasks within their Organization that have been assigned to them.

The standard editable fields within the Track Progress Pop-Up Window include:

• Actual Start Date
• Actual End Date
• Percent Complete
• Dollars Spent
• As of Date
• Comment

Create a Project

To create a new Study Project, a User with Project Access level would click on the Create New Project button which is located on the Project Studies Workbench screen.

The only editable sections on Create a Project are Project Title, Project Status, Lead Region, P4 Project ID, other Regions, and the Comments Fields.

After the Project is created the user can then enter any contacts associated with the Studies Project, any Contract Information, and any Change Request Information. Note: The first two digits of a case number represent the fiscal year that the Project was created, which is not always the same as the fiscal year in which the funds were obligated.

Steps include:

1. A user can add Project Contacts by selecting the Add button within the Contacts Table
   1. The user will then be required to enter the Contact Type, Name, and Email Address. Additional information, including a Task Order number, can also be stored in this screen
   2. Once those fields are completed the user must select the Add button

      

2. A user can add Contract Information by selecting the Add button within the Contract Information Table
   1. The user will then be required to enter the Funding Region, Federal Fiscal Year, Organization Type, Organization Name, Cost Type, Contract/Agreement Number, and Task Order Number. Additional information can also be stored in this screen
   2. Once those fields are completed the user must select the Add button

      

Project Contract Information

Contract Information must be added in order to create a Task. Additional contract information can be added after the Project is created as new work is purchased for the Project. When a Contract is added to a Project, Task + EV users with that same Organization and assigned to the Task will have the ability to update the Earned Value information for those Tasks within that Studies Project.

3. A user can add Change Request Information at any time by selecting the Add button within the Change Request Table
   1. The user will then be required to enter the Change Request Number. Additional information can also be stored in this screen
   2. Once those fields are completed the user must select the Add button

      

Once all the associated Contacts and Contracts have been added to the Project, the user can then move onto Create a Purchase

To reach the Create a Purchase the user can either click on the Purchases button on the bottom of the screen or click on the Purchases tab on the tool bar

Create a Purchase

The Purchases Tab provides an overview of all the Purchases and connected Tasks associated with the specific Project. From this screen, a Project Access level user can create, edit, or delete a Purchase as well as create, edit, or delete a Task. Please note: that only certain fields are editable once a Purchase has been created, Purchase Description and Purchase Contacts. In addition, if a Purchase is deleted all the associated Tasks will be automatically deleted.

To create a new Purchase a user with Project Access level would follow these steps:

1. Select the Create Purchase button
2. Once on the Create Purchase page the user is required to complete the Purchase Group and the Purchase before entering a Purchase Name. The user may also select the Purchase Type Indicator and enter a Purchase Description before completing the Geography section (a full List of Purchase Groups and Purchases can be found in the Getting Started Section).
   • Purchase Type Indicators include:
   • Revised Prelim
   • Physical Map Revision (PMR)
   • Large Scale Automatic Engineering (LSAE)
   • Base Level Engineering (BLE)
   • Advisory BFE
   
   

   

Within the Create Purchase screen the Project Access level user will also be able to associate one or more Geography(ies) to the Purchase to define the area that has been scoped to perform FEMA funded work. Geographies are categorized into three types: a HUC Level and Watershed, a State and County, or a Community CID. Filtering by Geography type allows the user to select one or more desired Geographies to add to the purchase. Keep in mind that Tasks within the same purchase will have the same Geography. Once a Geography is defined and a purchase created, this Geography cannot be updated so it is critical that the correct Geography is selected when the purchase is created.

To add Geography a Project Level Access user would follow these steps:

1. To add the desired Available Geography, the user needs to select the row and then select the Add Geography button
   1. When searching for the desired Geography, Users can search by HUC Level and Watershed Name, OR State and County, OR Community CID. Each search option will populate the Available Geography Table below. Users can also import Geographies from other Purchases within that Project by selecting the Purchase Drop down and then the desired Purchase. This will populate the Available Geography Table with geographies from that Purchase.

   

2. A user can also remove any already added Geography by simply highlighting the desired row and then selecting the Remove button

Removing a Geography

Once a Purchase is completed, the Geography added to the Purchase cannot be removed without submitting a Risk MAP IT Help Ticket. When making a request to Risk MAP IT Help requesting geography/geographies be edited or removed, users should send only the list of geographies to be edited or removed. The list of geographies that need to remain within the Purchase should not be included. If there are no Tasks included in a Purchase with geography to be edited or removed, CDS recommends that users reach out to the Project Owner and request the Purchase be deleted and recreated with the proper geographies, rather than contacting Risk MAP IT Help.

Also, on the Create a Purchase page, the Project Level Access user will be able to add contacts to the Purchase. Steps include:

1. A user can add Purchase Contacts by selecting the Add button within the Contacts Table.
   1. The user will then be required to enter the Contact Type, Name, and email Address. Additional information can also be stored in this screen
   2. Once those fields are completed the user must select the Save button. Please Note: anyone identified as a Purchase Contact will not receive any system notifications
   3. .

      

Once the Purchase is complete it will appear on the list of Purchases under the Purchase Tab within the Studies Project. A Project Level Access user will only then be able to create any associated Tasks. Please note, these Tasks will have the same Geography as the Purchase.

Create a Task

To Create a Task, a Project Level Access User must first select which Purchase they would like to create the Task within. Once a Purchase is selected the Task Table will auto populate to display any already created Tasks. Once the Purchase is selected a user can choose to either create, edit, or delete a Task. Please note: While the system does not require Tasks be created in a certain order, some Tasks are dependent on others. Please refer to the Purchase Group Overviews for more information regarding the order in which Tasks should be created/completed.

NOTE: During the creation of certain tasks, other tasks can be auto-generated to ensure name and data consistency at the choice of the user. The tasks that trigger auto-generation and the resulting auto-generated tasks depend on the Purchase type and are listed in Purchase-specific instructions below.

For auto-generated taks that require the Represented Geography, the County FIPS should be input. The County FIPS used for appending will be pulled from the "Community to Validate Against" field if the selected value ends in a County FIPS 'C' designation. The 'C' will be removed from the ID that is appended to the task name. If the selected value does not end in the 'C' designation, the selected CID will be used.

Assignment of the auto-generated tasks is to the user who creates the triggering task, and re-assignment of auto-generated tasks to other useres must be done manually.

To create a new Task, the user can click on the Create Task button on the bottom of Task Table

Once on the Create a Task page, the user will be able select the desired Task. Steps include:

1. A user should start by selecting a Task from the Task drop down. Each Task drop down is predetermined based on which Purchase the Task is being created for
2. A user can then enter a Task Name. Examples of Task names are provided in the Task specific sections below
3. A user can select whether to track progress (most tasks will be required to track progress). The options are:
   • "Yes" (default selection) - the user can then enter a Baseline Task Start and End Date
   • "No" - the Baseline Task Start and End Date fields disappear
4. A user can also choose to enter a Task Description. A Task description can add more detailed information specific to the Task. This information is visible on the Task Workbench.
5. A user may have the option to indicate if the Task should track Earned Value (EV) or not. EV is required for some Tasks, thus this option will already be selected in those situations. For a list of Tasks that require EV information please review the Purchase & Tasks Overview section.
6. Users have the option of indicating if metadata is required or not for tasks which have associated metadata. This option is defaulted to "yes".

If the Task tracks Earned Value(EV) either because it is required or if chosen, a user will be able to add Contract Information. Steps include:

1. A user is required to enter Contract information
   1. A user should start by selecting which Task Order Number they would like to associate with the Task. The Organization Type and Name will auto generate based on the information prepopulated in the Create Project Steps
   2. A user can then enter the Current Negotiated Cost if the Task requires that field.
   3. Once all required fields are completed the user must select the Add/Edit Cost button to add the Contract Information to the Task.

Also, on the Create a Task page, a user will be able to Assign the Task. To filter choose either Name, Organization Name, Access-Level, OR a Region. Once the available users list is produced the user will then have to select the desired user(s). Steps include:

1. To Assign the Task, the user needs to select the row and then select the Add User(s) button
2. A user can also remove any already added user(s) by simply highlighting the desired row and then selecting the Remove User(s) button
3. Once the Task is submitted users cannot remove assigned users. Users must submit a Risk MAP IT Help Ticket to remove assigned users

Once all the required fields are completed a user must select the Submit button.

Once the Task is complete it will appear on the list of Tasks under the Task Tab within the Studies Project once the associated Purchase is highlighted.

Full details on the Tasks that can be created for each Purchase is included in the following guidance and organized by Purchase Group.

Alluvial Fan Purchase

This purchase will allow a user to Capture, Validate, and complete an Independent QA/QC of Alluvial Fan Data, and complete KDP Zero and One.

Purpose: This Task will be used when new Alluvial Fan Analysis is performed or provided as leveraged data. The purpose of this Task is for the Mapping Partner (PTS, CTP) to collect required data for the proposed alluvial fan analysis, and to capture Alluvial Fan Submittal information, per the Data Capture Standards.

Tasks:

• Alluvial Fan Data Capture (with option to auto-generate Alluvial Fan Data Validation Task)
• Alluvial Fan Data Validation
• Alluvial Data Independent QA/QC
• KDP Zero
• KDP One

Data Upload:

• For reference to the data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, Data Capture - General, and Data Capture - Workflow Details guidance documents

Validation:

• All Project data uploaded to the MIP through a Project Workflow needs to be reviewed and validated for completeness against the current Data Capture standards by a MIP super-user, typically a MIP Black Belt

Create Alluvial Fan Purchase & Tasks

While in the purchase creation process a Project Level Access user would locate the Alluvial Fan purchase by selecting the Data Development Purchase Group. Once that option is selected the Purchase dropdown will auto-populate and the option for the Alluvial Fan will be made available. During the purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list.

Once a Project Level Access user has created the purchase, the user would then be able to create the relevant Tasks associated with the specific Purchase as listed in the Purchases and Tasks Overview section of this document.

FEMA Official MIP Studies Guidance Highlights:

• Purchase Geography: Purchase geography can be county, watershed, multiple CIDs, dependent on the scope of work
• Purchase Contacts: Regional FEMA Contact, TO manager, PM for PTS or CTP. This could also include State and Federal Agency contacts
• Purchase Field Description: Provide a short narrative of study type (new, re-studied, leveraged), the area studied and unique identifiers of the stakeholders, geography, and communities.
• Purchase Type Indicator: PMR or Revised Preliminary as applicable
• Tasks Required to Support Purchase:
  • KDP 0 and 1 if not already completed
  • Validation
• Task Name: Should include a descriptor of the associated Geography(ies) and/or data creator, such as:
1. For example: Flood Watershed (County, Jurisdiction) Alluvial Fan Data Capture
2. For example: Flood Watershed (County, Jurisdiction) 'Mapping Partner' Alluvial Fan Data Capture
• Task Description: Consider including whether the Task associated with new, restudied, or leveraged analysis. Consider including a list of stakeholders, the study extent, a description of the associated Geography, and Mapping Partner (PTS/CTP) information. Include any other relevant information the Project Access Level user deems useful.
• EV Information: Will be tracked at the Task Level for the Alluvial Fan Data Capture Task and the Alluvial Fan Independent QA/QC Task
• Task Assignments:
  • KDP Zero: FEMA Region or their designee
  • KDP One: FEMA Region or their designee
  • Alluvial Fan Data Capture: Mapping Partner (funded to perform work)
  • Alluvial Fan Validation: FEMA Region or their designee (MIP BB or Regional POC)
  • Alluvial Fan Independent QA/QC: Mapping Partner (funded to review work)

Capture Alluvial Fan Task

Task Start: Data capture of alluvial fan starts once confirmation is received that both KDP 0 and KDP 1 have been completed.

The Alluvial Fan Data Capture Task includes the following sections, as shown in the example below

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Alluvial Fan Data and perform the automated Metadata Validation
• Analysis Section allows the user to indicate details specific to the Task and Leverage information
• Auto-Generate Tasks Section allows the user to auto-generate the Alluvial Fan Data Validation Task
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Alluvial Fan Validation and Alluvial Fan Independent QA/QC Tasks

The only editable sections of this Task are the Submit Data, Analysis, add Leverage, Auto-generate Tasks, and Comments sections. To edit these sections, steps include:

1. Upload Alluvial Fan data
   1. After selecting the file to upload, a user must select the Upload File button to have the file saved to the Task
   2. After submitting the file, a user must select the either the Direct Upload button, which uploads the file directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. After uploading the file, select Run Validation button to trigger metadata validation.
   4. To view uploaded files in File Explorer, select the View in File Explorer link.
   5. Select the View Details link for more information on the results of the auto validation. If the status displays Failed, the View Details link provides specific information on what part of the metadata failed the review.
2. Indicate which type of Analysis is present.
   1. A user can select from the following options, please select any that apply to the entire Alluvial Fan Submitted:
      1. Alluvial Fan Landforms Exist
      2. Active Alluvial Fan
      3. Inactive Alluvial Fan
      4. Structures are associated with the Alluvial Fan
3. Add Model or Method information
   1. Under the Model or Method Table, select the Add button.
   2. The user will then be required to choose the Model and enter the Description of Methods and Outputs
   3. Once those fields are completed the user must select the Save button

      

4. Add Leverage to the Task
   1. Under the Leverage section, select the Add button
   2. Enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments (all required fields).
   3. Consider including relevant contact information in the Leverage Comments, if possible.
   4. Once those fields are completed the user must select the Save button.

      

5. Auto-Generate Tasks: The user can choose to auto-generate the Alluvial Fan Data Validation Task when creating the Alluvial Fan Data Capture Task. To do so, the steps are:
1. Check the "Auto-Generate Tasks" box
2. Enter a descriptive suffix in the "Generated Task Suffix" field
6. Add Comments relevant to the Task
   1. The user may add information relating to special disaster events. Describe any foreseeable special requirements, difficulties, limitations or potential risks associated with the Alluvial Fan Data Capture Task.
7. A user can select the Save button at any point during this process. Once all the mandatory fields are completed the user can select the Submit button

Alluvial Fan Validation Task

The Alluvial Fan Validation Task is initiated when the Alluvial Fan Data Capture Task is completed, and the data is ready for Independent QA/QC.

The Alluvial Fan Validation Task includes the following sections, as shown in the example below

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validation Status fields. To edit these sections, steps include:

1. Approve or Reject Validation (user must select one)
2. Upload a Validation document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task.
3. The Validator can also enter any comments regarding the validation Task.
4. The user can select the Save button at any point during this process. Once all the mandatory fields are completed the user can select the Submit button

Alluvial Fan Independent QA/QC Task

The Independent QA/QC Task is initiated when the Data Capture Task is completed, and the Validation Task is completed/approved. The Independent QA/QC checks the technical correctness of the mapping and submittal files for completeness and quality excellence. This Task may be completed by a Mapping Partner; the Independent QA/QC is conducted by either the same Mapping Partner who completed the Data Capture Task (but by a different and independent production group) or by an independent technical reviewer.

The Alluvial Fan Independent QA/QC Task includes the following sections, as shown in the example below

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• QA/QC Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary QA/QC checklists as well as provide general comments related to this independent review

The only editable sections of this Task are the Independent QA/QC Status fields. Steps include:

1. Approve or Reject QA/QC (user must select one).
• If comments must be addressed, the Data Capture Task would be reopened, revised, and resubmitted. The Validation Task would then be reopened for Approval or Rejection.
2. Upload a QA/QC document
   1. Materials uploaded may be QA/QC documents with comments and resolutions, including Word or Excel documents, screen shots, and/or spatial files.
   2. After selecting the file, a user must select the Upload File button to have the file saved to the Task.
3. The Independent Reviewer may also enter any comments regarding the QA/QC Task, indicating specific attachments relevant to the QA/QC process.
4. A user can select the Save button at any point during this process. Once all the mandatory fields are completed the user can select the Submit button to submit the Independent QA/QC results.

Base Map Purchase

This Purchase will allow a user to Capture Base Map Data, Validate the Base Map Data, and complete an Independent QA/QC and if necessary KDP Zero and One.

Purpose: As it applies to Flood Risk Projects, a base map is defined as the planimetric, or horizontal representation, of map features that show geo-referenced locations, and contain attribute information (i.e., names) about the items. A base map does not include topographic or elevation data. The Mapping Partner performs this activity to upload the base map data and associated metadata to the MIP for auto QA.

Tasks:

• Base Map Data Capture with option to auto-generate Base Map Data Validation Task)
• Base Map Data Validation
• Base Map Data Independent QA/QC
• KDP Zero
• KDP One

Data Upload:

• For reference to the data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, Data Capture - General, and Data Capture - Workflow Details guidance documents

Validation:

• All Project data uploaded to the MIP needs to be reviewed and validated for completeness against the current Data Capture standards by a MIP super-user, typically a MIP Black Belt.

Create Base Map Purchase & Tasks

While in the purchase creation process, a Project Level Access user would locate the Base Map purchase by selecting Purchase Group: Data Development, Sharing Risk Awareness, & Mitigation Outreach. Once that option is selected the Purchase dropdown will auto-populate and the option for the Base Map will be made available. During the purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list.

Typically, the base map for a Project is identified and gathered during Discovery, so usually all Discovery purchases should have a base map data capture purchase also to provide a location to upload the base map. A base map purchase may not have much cost associated with it since the coordination to identify the base map may be included in Discovery and the processing of the base map for the final products may be included in later production Tasks. If the Project begins gathering data before there is a discovery purchase or a base map is not identified during discovery, the Project creator should make sure a base map data capture purchase is available to upload the base map in those situations.

Once a Project Level Access user has created the purchase, the user would then be able to create the relevant Tasks associated with the specific Purchase as listed in the Purchases and Tasks Overview section of this document.

FEMA Official MIP Studies Guidance Highlights:

• Purchase Geography: When determining the geographies associated with the Base Map purchase, the user should include all communities that appear on the printed FIRMs being revised as per the scope of the subject map revision, unless a community is designated as an "Area Not Included" (ANI) on the FIRM
• Purchase Contacts: FEMA Regional PM, Mapping Contractor PM, Mapping Contractor GIS Production Lead
• Purchase Field Description: Provide a short narrative of study type (new, re-studied, leveraged), the area studied and unique identifiers of the stakeholders, geography, and communities.
• Purchase Type Indicator: PMR or Revised Preliminary as applicable
• Tasks Required to Support Purchase:
  • KDP 0 and 1 if not already completed.
  • Validation
• Task Name: Base Map Data Capture Task
• Task Description: This Task is used by the mapping contractor to submit the updated base data to be displayed on the revised FIRM panels
• EV Information: Will be tracked at the Task Level for the Base Map Capture Task and the Base Map Independent QA/QC Task
• Task Assignments:
  • KDP Zero: FEMA Region or their designee
  • KDP One: FEMA Region or their designee
  • Base Map Data Capture: Mapping Partner (funded to perform work)
  • Base Map Data Validation: FEMA Region or their designee (MIP BB or Regional POC)
  • Base Map Independent QA/QC: Mapping Partner (funded to review work)

Capture Base Map Task

Task Start: This data capture Tasks can start once confirmation is received that both KDP 0 and KDP 1 have been completed. This Task should be the first of the data development activities to begin once discovery is complete. This Task should be completed prior to the Topographic Data Development, Field Survey, Hydrology and Hydraulics phases. This will allow for correct coordination of base data between mapping products and engineering products.

Below is the Capture Base Map Task which includes the following sections:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History.
• Submit Data Section allows the user to upload Base Map Data and perform the automated Metadata Validation. In the leverage section you should enter the value of any contributed data used for the base map such as orthophotos, planimetric street data, etc. used on the FIRM.
• Auto-Generate Tasks allows the user to choose to auto-generate the Base Map Data Validation Task
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Base Map Data Validation and Base Map Data Independent QA/QC.

The only editable sections of this Task are the Submit Data, Analysis, add Leverage, Auto-Generate Tasks, and Comments sections. Steps include:

1. Within the Submit Data Section, A user must select a Data Location from the drop-down menu.
   1. Pre-populated options are listed, and a user can select:
   • MIP - Select this option if data is being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer
   • Risk MAP IT Help - Select this option if data is not being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer. Instead this data must be physically sent to CDS for uploading, please see MIP Guidance document for further details on this process.
2. Upload Base Map data
   1. After selecting the file to upload, a user must select the Upload File button to have the file saved to the Task
   2. After submitting the file, a user must select the either the Direct Upload button, which uploads the file directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. After uploading the file, select Run Validation button to trigger metadata validation.
   4. To view uploaded files in File Explorer, select the View in File Explorer link
   5. Select the View Details link for more information on the results of the auto validation. If the status displays Failed, the View Details link provides specific information on what part of the metadata failed the review.
3. A user can add Leverage to the Task by:
   1. Selecting the Add button under the Leverage Tab section
   2. Entering Quantity, Type, Unit, Contributed By, Federal Fiscal Year (all required fields, and Comments)
   3. Once those fields are completed the user must select the Save button

      

4. Auto-Generate Tasks: The user can choose to auto-generate the Base Map Data Validation Task when creating the Base Map Data Capture Task. To do so, the steps are:
   1. Check the "Auto-Generate Tasks" box
   2. Enter a descriptive suffix in the "Generated Task Suffix" field
5. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Base Map Validation Task

Below is the view of the Validate Base Map Data Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validation Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a Validation file
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the validation Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Base Map Independent QA/QC Task

The Independent QA/QC Task is initiated when the Data Capture Task is completed, and the Validation Task is completed/approved. The Independent QA/QC checks the technical correctness of the mapping and submittal files for completeness and quality excellence. This Task may be completed by a Mapping Partner; the Independent QA/QC is conducted by either the same Mapping Partner who completed the Data Capture Task (but by a different and independent production group) or by an independent technical reviewer.

Below is the view of the Independent QA/QC Base Map Data Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• QA/QC Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary QA/QC checklists as well as provide general comments related to this independent review

The only editable sections of this Task are the Independent QA/QC Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a QA/QC file
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the QA/QC Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Coastal Purchase

This purchase will allow a user to Capture Coastal Data, Validate Coastal Data, and complete an Independent QA/QC.

Purpose: Submittal of coastal deliverables. Multiple purchases are required based on the geography of the study. Larger watershed modeling studies may be performed covering multiple states and transect based analysis would need to be purchased at county levels or smaller.

Tasks:

• Coastal Data Capture (with the option to auto-generate the Coastal Data Validation Task)
• Coastal Data Validation
• Coastal Data Independent QA/QC
• KDP Zero
• KDP One

Data Upload:

• For reference to the data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, Data Capture - General and Data Capture - Workflow Details, Coastal Study Documentation and Intermediate Data Submittals, and Coastal Data Capture guidance documents

Validation:

• All Project data uploaded to the MIP through a Project workflow needs to be reviewed and validated for completeness against the current Data Capture standards by a MIP super-user, typically a MIP Black Belt

Create Coastal Purchase & Tasks

While in the purchase creation process, a Project Level Access user would locate the Coastal purchase by selecting Data Development Purchase Group. Once that option is selected the Purchase dropdown will auto-populate and the option for the Coastal purchase will be made available. During the purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list and determine if associated uploaded data should be made available via FRiSEL.

Once they have created the purchase, a Project Level Access user would then be able to create these Tasks:

FEMA Official MIP Studies Guidance Highlights:

• Purchase Geography: Geography can be Regional, lake-wide, or countywide dependent on the data being developed, the Intermediate Data Submittal (IDS) being purchased and the coastal body being studied
• Purchase Contacts: Regional Engineer
• Purchase Field Description: Provide a short narrative of study type (new, re-studied, leveraged), specific IDS deliverable, and the area studied and unique identifiers of the stakeholders, geography, and communities.
• Purchase Type Indicator: PMR or Revised Preliminary as applicable
• Tasks Required to Support Purchase:
  • KDP 0 and 1 if not already completed.
  • Validation
• Task Name: Task name should coincide with the flooding source, or geography, or specific IDS deliverable
• Task Description: Description should include geography as that is the driver of the coastal submittals. There are different submittals based on the coastal flooding source
• Task Assignments:
  • KDP Zero: FEMA Region or their designee
  • KDP One: FEMA Region or their designee
  • Coastal Data Capture: Mapping Partner (funded to perform work)
  • Coastal Data Validation: FEMA Region or their designee (MIP BB or Regional POC)
  • Coastal Data Independent QA/QC: Mapping Partner (funded to review work)
• EV Information: Will be tracked at the Task Level for the Coastal Data Capture Task and the Coastal Independent QA/QC Task

Capture Coastal Data Task

Task Start: This data capture Tasks can start once confirmation is received that both KDP 0 and KDP 1 have been completed. Coastal submittals consist of multiple IDSs and the content of each IDS is dependent on the Region and study methods. Coastal submittals can be split between Purchases due to multiple year funding and the fact that some modeling is done on a Regional scale and others on a local (county or community) scale.

Below is the view of the Capture Coastal Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Coastal Data and perform the automated Metadata Validation
• Analysis Section allows the user to indicate details specific to the Task and Leverage information
• Auto-Generate Tasks allows the user to choose to automatically generate the Coastal Data Validation Task
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Coastal Validation and Coastal Independent QA/QC Tasks

The only editable sections of this Task are the Submit Data, Analysis, add Leverage, and Comments sections. Steps include:

1. Within the Submit Data Section, a user must select a Data Location from the drop-down menu.
   1. Pre-populated options are listed, and a user can select:
   • MIP - Select this option if data is being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer
   • Risk MAP IT Help - Select this option if data is not being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer. Instead this data must be physically sent to CDS for uploading, please see MIP Guidance document for further details on this process.
2. Upload Coastal data
   1. After selecting the file to upload, a user must select the Upload File button to have the file saved to the Task
   2. After submitting the file, a user must select the either the Direct Upload button, which uploads the file directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. After uploading the file, select Run Validation button to trigger metadata validation
   4. To view uploaded files in File Explorer, select the View in File Explorer link
   5. Select the View Details link for more information on the results of the auto validation. If the status displays Failed, the View Details link provides specific information on what part of the metadata failed the review.
3. A user can add which Coastal Analysis Types apply by selecting the check box next to the Intermediate Data Submission (IDS) of their choosing
4. A user can also add Task Information by selecting either "There are CBRS Zones" or "Certified Coastal Structure"
5. A user can add Coastal Models or Methods Used by selecting the Add button under the Coastal Models or Methods Used section
   1. The user will then be required to enter Model, Horizontal Datum, Measuring Unit, Vertical Datum, Measuring Unit, and Description of Methods and Outputs
   2. Once those fields are completed the user must select the Save button

      

6. A user can add Leverage to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

7. Auto-Generate Tasks: The user can choose to auto-generate the Coastal Data Validation Task when creating the Coastal Data Capture Task. To do so, the steps are:
   1. Check the "Auto-Generate Tasks" box
   2. Enter a descriptive suffix in the "Generated Task Suffix" field
8. When submitting Nearshore Hydraulics or Floodplain Mapping deliverables, a comment should be provided as to the purchase for the larger modeling effort.
9. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Coastal Validation Task

Below is the view of the Coastal Validation Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validation Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a Validation document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the validation Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Coastal Independent QA/QC Task

The Independent QA/QC Task is initiated when the Data Capture Task is completed, and the Validation Task is completed/approved. The Independent QA/QC checks the technical correctness of the mapping and submittal files for completeness and quality excellence. This Task may be completed by a Mapping Partner; the Independent QA/QC is conducted by either the same Mapping Partner who completed the Data Capture Task (but by a different and independent production group) or by an independent technical reviewer.

Below is the view of the Independent QA/QC Flood Mapping Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• QA/QC Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary QA/QC checklists as well as provide general comments related to this independent review

The only editable sections of this Task are the Independent QA/QC Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a QA/QC file
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the QA/QC Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Draft FIRM Database Purchase

This purchase will allow a user to capture a Draft FIRM Database, Validate the Draft FIRM Database, and complete an Independent QA/QC, if applicable.

Purpose: The FEMA FIRM Database will store the digital GIS data used in the map production process, as well as tabular information inside the Flood Insurance Study (FIS) report. The database will provide a standard, systematic method for FEMA to distribute comprehensive details of flood hazard identification studies to the public and others in a digital format.

Tasks:

• Draft FIRM Database Capture (with option to auto-generate Draft FIRM Database Validation)
• Draft FIRM Database Validation
• Draft FIRM Database Independent QA/QC
• KDP Two

Data Upload:

• For reference to the data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, Data Capture - General, Data Capture - Workflow Details, FIRM Database Technical Reference, and related guidance documents

Validation:

• All Project data uploaded to the MIP through a Project workflow needs to be reviewed and validated for completeness against the current Data Capture standards by a MIP super-user, typically a MIP Black Belt.

Create Draft FIRM Database Purchase & Tasks

While in the purchase creation process, a Project Level Access user would locate the Draft FIRM Database purchase by selecting Purchase Group: Data Development, Sharing Risk Awareness, & Mitigation Outreach. Once that option is selected the Purchase dropdown will auto-populate and the option for the Draft FIRM Database will be made available. During the purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list and determine if associated uploaded data should be made available via FRiSEL.

Typically, one FIRM database must be created for each county that will have revised map panels based on the scope of the Project. So, the Project level access users should create a separate Draft FIRM Database purchase for each county.

Once a Project Level Access user has created the purchase, the user would then be able to create the relevant Tasks associated with the specific Purchase as listed in the Purchases and Tasks Overview section of this document.

FEMA Official MIP Studies Guidance Highlights:

• Purchase Geography: A Draft FIRM Database purchase should always have countywide geography or a county-community based geography for PMR Projects. For watershed Projects the Project creator will need to create a separate Draft FIRM Database purchase for each county within the watershed that is receiving draft data
• Purchase Contacts: Regional FEMA Contact, TO manager, PM for PTS or CTP.
• Purchase Field Description: Provide a short narrative of study type (new, re-studied, leveraged), the area studied and unique identifiers of the stakeholders, geography, and communities.
• Purchase Type Indicator: PMR or Revised Preliminary as applicable
• Tasks Required to Support Purchase:
  • KDP 0 and 1 if not already completed
  • KDP 2
  • Validation
• Task Name: Name should include county name
• Task Description: Specify if study is a full countywide, PMR, or Partial Countywide
• Task Assignments:
  • KDP Zero: FEMA Region or their designee
  • KDP One: FEMA Region or their designee
  • KDP Two: FEMA Region or their designee
  • Draft FIRM Data Capture: Mapping Partner (funded to perform work)
  • Draft FIRM Validation: FEMA Region or their designee (MIP BB or Regional POC
  • Draft FIRM Independent QA/QC: Mapping Partner (funded to review work)
• EV Information: Will be tracked at the Task Level for the Draft FIRM Database Capture Task and the Draft FIRM Database Independent QA/QC Task

Capture Draft FIRM Database Task

Task Start: This Task can be started after data development Tasks such as base map, hydrology, hydraulics, and floodplain mapping have been completed, as outputs from these activities are necessary for building the Draft DFIRM database. KDP2 should also be approved prior to starting the Draft FIRM Database Task.

Below is the view of the Capture Draft FIRM Database Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload the Draft FIRM Database, select the Database Schema and perform the automated Metadata and database Validation
• Analysis Section allows the user to indicate details specific to the Task and Leverage information. Enter leverage for contributed work or funds in the production of the FIRM database. Don't count base map, elevation data, or other contributed spatial data sets here.
• Auto-Generate Tasks allows the user to choose to auto-generate the Draft FIRM Database Validation Task
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Draft FIRM Validation and Draft FIRM Independent QA/QC Tasks

The only editable sections of this Task are the Submit Data, Analysis, add Leverage, Auto-Generate Tasks, and Comments sections. Steps include:

1. A user must select a Database Schema
2. Next a user can upload Draft FIRM database data
   1. After selecting the file to upload, a user must select the Upload File button to have the file saved to the Task
   2. After submitting the file, a user must select the either the Direct Upload button, which uploads the file directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. After uploading the file, select Run Validation button to trigger metadata validation. If the metadata validation passes, DVT is automatically started right after metadata validation. Please Note: Tasks that involve DVT Validation, the CID to validate selected during task creation should match the CID within the metadata file and the CID in the file naming convention
   4. To view uploaded files in File Explorer, select the View in File Explorer link
   5. Select the View Details link for more information on the results of the auto validation. If the status displays Failed, the View Details link provides specific information on what part of the metadata failed the review. In some instances, there may be a need to bypass a failing DVT validation. Common bypass needs are described in the DVT Guidance in G&S. If you feel that the DVT validation has failed your submission when it should not have, please contact Risk MAP IT Help and provide your case number, validation URL, and reasoning
3. A user can add Leverage to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

4. Auto-Generate Tasks: The user can choose to auto-generate the Draft FIRM Database Validation Task when creating the Capture Draft FIRM Database Task. To do so, the steps are:
   1. Check the "Auto-Generate Tasks" box
   2. Enter a descriptive suffix in the "Generated Task Suffix" field
   3. Enter the County FIPS in the "Relevant Geography" field
5. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Draft FIRM Database Validation Task

Below is the view of the Validate Draft FIRM Database Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validation Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a Validation document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the validation Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Draft FIRM Database Independent QA/QC Task

The Independent QA/QC Task is initiated when the Data Capture Task is completed, and the Validation Task is completed/approved. The Independent QA/QC checks the technical correctness of the mapping and submittal files for completeness and quality excellence. This Task may be completed by a Mapping Partner; the Independent QA/QC is conducted by either the same Mapping Partner who completed the Data Capture Task (but by a different and independent production group) or by an independent technical reviewer.

Below is the view of the Independent QA/QC Draft FIRM Data Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• QA/QC Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary QA/QC checklists as well as provide general comments related to this independent review

The only editable sections of this Task are the Independent QA/QC Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a QA/QC document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the QA/QC Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

KDP 2 Task

Below is the view of the KDP 2 Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, and Purchase Geography(ies)
• Analysis Section allows user to enter if KDP is needed and the approval date as well as a reason if KDP is not needed
• Comments Section allows the user to enter any relevant comments

The only editable sections of this Task KDP 2 fields. Steps include:

1. A user must indicate where KDP 2 is needed or not
2. Next a user must enter the KDP 2 Approval Date
3. If a KDP 2 is not needed, then a user must provide a reason why
4. A reviewer can also enter any comments regarding the KDP 2 Task
5. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

Floodplain Mapping Purchase

This purchase will allow a user to Capture, Validate, and complete an Independent QA/QC of Floodplain Mapping Data, and complete KDP Zero and One

This purchase will allow a user to capture Floodplain Mapping Data, Validate the Floodplain Mapping Data, and complete an Independent QA/QC.

Purpose: Tasks associated with this activity are performed when new floodplain mapping is performed or provided as leverage. Data associated with this Task are purely for purposes of digital conversion or re-delineation. The floodplain mapping for a new hydraulic study are included as part of the Hydraulic Data Capture Task.

Tasks:

• Floodplain Mapping Data Capture (with option to auto-generate Floodplain Mapping Data Validation Task
• Floodplain Mapping Data Validation
• Floodplain Mapping Data Independent QA/QC
• KDP Zero
• KDP One

Data Upload:

• For reference to the data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, Data Capture - General and Data Capture - Workflow Details guidance documents

Validation:

• All Project data uploaded to the MIP through a Project workflow needs to be reviewed and validated for completeness against the current Data Capture standards by a MIP super-user, typically a MIP Black Belt.

Create Floodplain Mapping Purchase & Tasks

While in the purchase creation process, a Project Level Access user would locate the Flood Mapping purchase by selecting Purchase Group: Data Development, Sharing Risk Awareness, & Mitigation Outreach. Once that option is selected the Purchase dropdown will auto-populate and the option for the Flood Mapping purchase will be made available. During the purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list and determine if associated uploaded data should be made available via FRiSEL.

Once a Project Level Access user has created the purchase, the user would then be able to create the relevant Tasks associated with the specific Purchase as listed in the Purchases and Tasks Overview section of this document.

FEMA Official MIP Studies Guidance Highlights:

• Purchase Geography: Purchase geography can be county, watershed, multiple CIDs, dependent on the scope of work
• Purchase Contacts: Regional FEMA Contact, TO manager, PM for PTS or CTP. This could also include State and Federal Agency contacts
• Purchase Field Description: Provide a short narrative including whether the Purchase is for Re-delineation or Digital Conversion. Consider including a list of stakeholders, a description of the associated Purchase Geography(ies), a description of relevant data sources such as whether the data is leveraged, created by a PTS and/or CTP Mapping Partner, and the type of floodplain mapping, such as riverine and/or coastal
• Purchase Type Indicator: PMR or Revised Preliminary as applicable
• Tasks Required to Support Purchase:
  • KDP 0 and 1 if not already completed
  • Validation
• Task Name: Should include a descriptor of the associated Geography(ies) and/or data creator, such as Flood Watershed (County, Jurisdiction) Floodplain Mapping Data Capture, or Flood Watershed (County, Jurisdiction) Floodplain Mapping Data Capture
• Task Description: Consider including whether the Task associated with a Re-delineation and/or Digital Conversion effort(s). Consider including a list of stakeholders, the study extent, a description of the associated Geography, and Mapping Partner (PTS/CTP) information. Furthermore, consider including relevant data sources (leveraged, created by a PTS and/or CTP Mapping Partner, and any previous Case numbers associated with the Task
• Task Assignments:
  • KDP Zero: FEMA Region or their designee
  • KDP One: FEMA Region or their designee
  • Floodplain Mapping Data Capture: Mapping Partner (funded to perform work)
  • Floodplain Mapping Validation: FEMA Region or their designee (MIP BB or Regional POC
  • Floodplain Mapping Independent QA/QC: Mapping Partner (funded to review work)
• EV Information: Will be tracked at the Task Level for the Floodplain Mapping Data Capture Task and the Floodplain Mapping Data Independent QA/QC Task

Capture Floodplain Mapping Data Task

Task Start: The Mapping Partner should start this Task if this is a continuation of a study KDP 1, or if this represents a new KDP 0 and KDP 1

Below is the view of the Capture Floodplain Mapping Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Floodplain Data and perform the automated Metadata Validation
• Analysis Section allows the user to indicate Leveraged datasets and details (including Vertical Datum Conversion, Stream Information, and Leverage data sets)
• Auto-Generate Tasks allows the user to choose to auto-generate the Floodplain Mapping Data Validation Task
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Floodplain Mapping Data Validation and Floodplain Mapping Data Independent QA/QC Task

The only editable sections of this Task are the Submit Data, Vertical Datum Conversion, Stream Information, Leverage, and Comments sections. Steps include:

1. A user can upload Floodplain Mapping data
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. After uploading the file, select Run Validation button to trigger metadata validation
   4. To view uploaded files in File Explorer, select the View in File Explorer link
   5. Select the View Details link for more information on the results of the auto validation. If the status displays Failed, the View Details link provides specific information on what part of the metadata failed the review.
2. A user can also indicate if a Vertical Datum Conversion has been performed by selecting the check box
3. A user can add Studies data by selecting the Add button under the Studies section
   1. The user will then be required to enter Stream Name, Type of Study, and Linear Miles
   2. Once those fields are completed the user must select the Save button

      

4. A user can add Leverage to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

5. Auto-Generate Tasks: The user can choose to auto-generate the Floodplain Mapping Data Validation Task when creating the Capture Floodplain Mapping Data Task. To do so, the steps are:
   1. Check the "Auto-Generate Tasks" box
   2. Enter a descriptive suffix in the "Generated Task Suffix" field
6. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Floodplain Mapping Validation Task

The Validation Task is initiated when the Data Capture Task is completed, and the data is ready for Independent QA/QC

Below is the view of the Validate Floodplain Mapping Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validation Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a Validation document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the validation Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Floodplain Mapping Independent QA/QC

The Independent QA/QC Task is initiated when the Data Capture Task is completed, and the Validation Task is completed/approved. The Independent QA/QC checks the technical correctness of the mapping and submittal files for completeness and quality excellence. This Task may be completed by a Mapping Partner; the Independent QA/QC is conducted by either the same Mapping Partner who completed the Data Capture Task (but by a different and independent production group) or by an independent technical reviewer.

Below is the view of the Independent QA/QC Floodplain Mapping Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• QA/QC Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary QA/QC checklists as well as provide general comments related to this independent review

The only editable sections of this Task are the Independent QA/QC Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a QA/QC document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the QA/QC Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Flood Risk Products (FRP) Purchase

This purchase will allow a user to Capture Draft Flood Risk Products (FRP) Data, Capture Final FRP Data, Validate the FRP Data, complete an Independent QA/QC of FRP Data, and complete KDP Zero and One.

Typically, each FRP is associated with a Regulatory Product Purchase under the Data Development Purchase Group; the FRP Purchase would occur at the beginning of the Project or after Discovery

Purpose: Tasks associated with this Purchase are completed to upload FRPs, including a Flood Risk Report (FRR), Flood Risk Map (FRM), Flood Risk Database (FRD), and/or other Flood Risk Datasets, to the MIP.

Tasks:

• FRP Data Capture (with option to auto-generate FRP Data Validation Task)
• FRP Data Validation
• FRP Data Independent QA/QC
• KDP Zero
• KDP One

Data Upload:

• For reference to the data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, MIP User Guide, Data Capture - General and Data Capture - Workflow Details, and Flood Risk Database Technical Reference and related Flood Risk Database guidance documents

Validation:

• All Project data uploaded to the MIP through a Project workflow needs to be reviewed and validated for completeness against the current Data Capture standards by a MIP super-user, typically a MIP Black Belt

Create Flood Risk Products (FRP) Purchase & Tasks

While in the purchase creation process, a Project Level Access user would locate the FRP purchase by selecting Purchase Data Development Group. Once that option is selected the Purchase dropdown will auto-populate and the option for the FRP purchase will be made available. During the purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list and determine if associated uploaded data should be made available via FRiSEL.

Once a Project Level Access user has created the purchase, the user would then be able to create the relevant Tasks associated with the specific Purchase as listed in the Purchases and Tasks Overview section of this document. Only one Task will be created to capture all of the individual FRPs.

FEMA Official MIP Studies Guidance Highlights:

• Purchase Geography: Purchase geography can be county, watershed, multiple CIDs, dependent on the scope of work
• Purchase Contacts: Project Manager, PTS, CTP, etc.
• Purchase Field Description: In the Purchase Description, state whether the FRPs represent basic or enhanced data, and list whether FRR, FRM, and/or FRD products are included.
• Purchase Type Indicator: Not applicable
• Tasks Required to Support Purchase:
  • KDP 0 and 1 if not already completed
  • Validation
• Task Name: Should include a descriptor of the associated Geography(ies) and/or data creator, such as Flood Watershed (County, Jurisdiction) Flood Risk Products Data Capture, or Flood Watershed (County, Jurisdiction) Flood Risk Products Data Capture. Also, indicate if the data is draft or final, if possible.
• Task Description: List the exact FRPs included (i.e., FRR, FRM, FRD, other Flood Risk Datasets).
• Task Assignments:
  • KDP Zero: FEMA Region or their designee
  • KDP One: FEMA Region or their designee
  • Flood Risk Products Data Capture: Mapping Partner (funded to perform work)
  • Flood Risk Products Validation: FEMA Region or their designee (MIP BB or Regional POC
  • Flood Risk Products Independent QA/QC: Mapping Partner (funded to review work)
• EV Information: Will be tracked at the Task Level for the FRP Data Capture Task and the FRP Independent QA/QC Task

Capture FRP Data Task

Mapping Partners may initiate the FRP Data Capture Task at varying times, depending on the Project and necessary FRPs. Some FRPs may be created prior to the development of regulatory products. The Capture FRP Data Task can be used for uploading draft (optional) and final (required) versions of FRPs. Within the Capture FRP Data Task, users will need to upload the correct file structure from FEMA's Data Capture Technical Reference for Draft and Final FRP submittals for multiple data uploads.

The Capture FRP Task includes the following sections, as shown in the example below

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload FRP Data and perform the automated Metadata Validation
• Analysis Section allows the user to indicate Leveraged datasets and details (including Flood Risk Products & Datasets and Leverage data sets)
• Auto-Generate Tasks Section allows the user to choose to auto-generate the FRP Data Validation Task
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the FRP Validation and FRP Independent QA/QC Tasks

The only editable sections of this Task are the Submit Data, Flood Risk Products & Datasets, Leverage, and Comments sections. Steps include:

1. Upload FRP data
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task.
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. To view uploaded files in File Explorer, select the View in File Explorer link
2. Add FRPs & Datasets:
   1. Under the FRPs & Datasets section, select the Add button
   2. The user will then be required to enter Product/Dataset and Data Type. A user can also indicate if Enhanced Dataset information applies. The user must ensure that each product and/or dataset is represented by a row of data. Therefore, there will be a number of products entered in the analysis section dependent on the scope.
   3. Once those fields are completed the user must select the Save button

      

3. Add Leverage to the Task:
   1. Under the Leverage section, select the Add button
   2. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   3. Once those fields are completed the user must select the Save button.

      

4. Auto-Generate Tasks: The user can choose to auto-generate the FRP Data Validation Task when creating the FRP Data Capture Task. To do so, the steps are:
   1. Check the "Auto-Generate Tasks" box
   2. Enter a descriptive suffix in the "Generated Task Suffix" field
5. Add Comments relevant to the Task.
   • Include the FRP narrative here
6. A user can select the Save button at any point during this process. Once all the mandatory fields are completed the user can select the Submit button

FRP Validation Task

The Validation Task is initiated when the Data Capture Task is completed, and the data is ready for Independent QA/QC. If more than one FRP Data Capture Task is created, then the user will need to create separate validation Tasks.

The Validate FRP Task includes the following sections, as shown in the example below:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validation Status fields. Steps include:

1. Approve or Reject Validation (user must select one).
2. Upload a Validation document.
   1. After selecting the file, a user must select the Upload File button in order to have the file saved to the Task.
3. 3. The Validator can also enter any comments regarding the validation Task.
4. A user can select the Save button at any point during this process. Once all the mandatory fields are completed the user can select the Submit button

FRP Independent QA/QC Task

The Independent QA/QC Task is initiated when the Data Capture Task is completed, and the Validation Task is completed/approved. The Independent QA/QC checks the technical correctness of the mapping and submittal files for completeness and quality excellence. This Task may be completed by a Mapping Partner; the Independent QA/QC is conducted by either the same Mapping Partner who completed the Data Capture Task (but by a different and independent production group) or by an independent technical reviewer.

The Independent QA/QC FRP Task includes the following sections, as shown in the example below

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• QA/QC Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary QA/QC checklists as well as provide general comments related to this independent review

The only editable sections of this Task are the Independent QA/QC Status fields. Steps include:

1. Approve or Reject Validation (user must select one)
1. If comments must be addressed, the Data Capture Task would be reopened, revised, and resubmitted. The Validation Task would then be reopened for Approval or Rejection.
2. Upload a QA/QC document.
   1. Submit the approved QC checklist with signatures here.
   2. After selecting the file, a user must select the Upload File button to have the file saved to the Task.
3. The Independent Reviewer may also enter any comments regarding the QA/QC Task.
4. A user can select the Save button at any point during this process. Once all the mandatory fields are completed the user can select the Submit button to submit the Independent QA/QC results.

Hydraulics Purchase

This purchase will allow a user to Capture Hydraulics, Validate the Hydraulics data, and complete an Independent QA/QC.

Purpose: Capture hydraulic modeling data, meeting FEMA data capture standards. Types of hydraulic analysis include large scale automated engineering, base level engineering and enhanced engineering including one and two-dimensional hydraulic modeling at the stream or watershed level, and hydraulic data collection on smaller scale Projects, such as levee accreditations.

Tasks:

• Hydraulics Data Capture (with option to auto-generate Hydraulics Data Validation Task)
• Hydraulics Data Validation
• Hydraulics Data Independent QA/QC
• KDP Zero
• KDP One

Data Upload:

• Hydraulic model information should be captured by stream within the Hydraulics Data Capture Task. For reference to the data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, Data Capture - General, Data Capture - Workflow Details, and related guidance documents

Validation:

• All Project data uploaded to the MIP through a Project workflow needs to be reviewed and validated for completeness against the current Data Capture standards by a MIP super-user, typically a MIP Black Belt

Create Hydraulics Purchase & Tasks

While in the purchase creation process, a Project Level Access user would locate the Hydraulics purchase by selecting Data Development Purchase Group. Once that option is selected the Purchase dropdown will auto-populate and the option for the hydraulics will be made available. During the purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list and determine if associated uploaded data should be made available via FRiSEL.

Once a Project Level Access user has created the purchase, the user would then be able to create the relevant Tasks associated with the specific Purchase as listed in the Purchases and Tasks Overview section of this document.

FEMA Official MIP Studies Guidance Highlights:

• Purchase Geography: The geography of a hydraulic purchase will vary depending on Project scope (e.g., state, watershed, countywide, or county-community)
• Purchase Contacts: Regional FEMA Contact, TO manager, PM for PTS or CTP. This could also include State and Federal Agency contacts
• Purchase Field Description: Identify if this is a traditional stream based hydraulic analysis, LSAE or LAMP analysis
• Purchase Type Indicator: PMR, Revised Preliminary, LSAE, or BLE as applicable. The purchase type indicator of LSAE should be selected to differentiate between this type of hydraulic analysis and traditional stream-based hydraulic modeling. If a Project scope of work includes both LSAE and traditional stream based hydraulic modeling, then the Project creator will need to create separate hydraulic purchases.
• Tasks Required to Support Purchase:
  • KDP 0 and 1 if not already completed.
  • Validation
• Task Name: Hydraulics Analysis for 'Watershed Number (County or Community)', OR 'Watershed Number' (County or Community) Mapping Partner name, OR Levee ID levee accreditation, 'LSAE' or Leverage
• Task Description: Identify if this is a traditional stream based hydraulic analysis, LSAE or LAMP analysis
• Task Assignments:
  • KDP Zero: FEMA Region or their designee
  • KDP One: FEMA Region or their designee
  • Hydraulics Data Capture: Mapping Partner (funded to perform work)
  • Hydraulics Validation: FEMA Region or their designee (MIP BB or Regional POC)
  • Hydraulics Independent QA/QC: Mapping Partner (funded to review work)
• EV Information: Will be tracked at the Task Level for the Hydraulics Data Capture Task and the Hydraulics Independent QA/QC Task

Capture Hydraulics Data Task

Task Start: This data capture Task can start once confirmation is received that both KDP 0 and KDP 1 have been completed.

Below is the view of the Capture Hydraulics Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Hydraulic Data and perform the automated Metadata Validation
• Analysis Section allows the user to indicate details specific to the Task such as flood frequency modeled that are applicable, model information by stream name and study type and Leverage information
• Auto-Generate Tasks allows the user to choose to autogenerate the Hydraulics Data Validation Task
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Hydraulics Validation and Hydraulics Independent QA/QC Tasks

The only editable sections of this Task are the Submit Data, Analysis, add Leverage, and Comments sections. Steps include:

1. Within the Submit Data Section, a user must select a Data Location from the drop-down menu.
   1. Pre-populated options are listed, and a user can select:
   • MIP - Select this option if data is being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer
   • Risk MAP IT Help - Select this option if data is not being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer. Instead this data must be physically sent to CDS for uploading, please see MIP Guidance document for further details on this process.
2. Upload Hydraulics data
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task.
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. After uploading the file, select Run Validation to trigger metadata validation
   4. To view uploaded files in File Explorer, select the View in File Explorer link
   5. Select the View Details link for more information on the results of the auto validation. If the status displays Failed, the View Details link provides specific information on what part of the metadata failed the review
3. A user can add Model Information by selecting the Add button under the Model Information section
   1. Model information must be entered by stream either manually entering the information or using the upload template. The user will then be required to enter Stream Name, Type of Study, Actual Linear Miles, and Model
   2. Once those fields are completed the user must select the Save button

      

4. A user can add Leverage to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments
   2. Once those fields are completed the user must select the Save button

      

5. Auto-Generate Tasks: The user can choose to auto-generate the Hydraulics Data Validation Task when creating the Hydraulics Data Capture Task. To do so, the steps are:
   1. Check the "Auto-Generate Tasks" box
   2. Enter a descriptive suffix in the "Generated Task Suffix" field
6. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Hydraulics Validation Task

Below is the view of the Validate Hydraulics Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validation Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a Validation document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the validation Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Hydraulics Independent QA/QC Task

The Independent QA/QC Task is initiated when the Data Capture Task is completed, and the Validation Task is completed/approved. The Independent QA/QC checks the technical correctness of the mapping and submittal files for completeness and quality excellence. This Task may be completed by a Mapping Partner; the Independent QA/QC is conducted by either the same Mapping Partner who completed the Data Capture Task (but by a different and independent production group) or by an independent technical reviewer.

Below is the view of the Independent QA/QC Hydraulics Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• QA/QC Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary QA/QC checklists as well as provide general comments related to this independent review

The only editable sections of this Task are the Independent QA/QC Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a QA/QC document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the QA/QC Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Hydrology Purchase

This Task will allow a user to Capture Hydrology Data, Validate the Hydrology Data, and complete an Independent QA/QC.

Purpose: Capture hydrology purchase documentation related to riverine flooding analyses, including the methodology, assumptions, and resultant data.

Tasks:

• Hydrology Data Capture (with option to auto-generate the Hydrology Data Validation Task)
• Hydrology Data Validation
• Hydrology Data Independent QA/QC
• KDP Zero
• KDP One

Data Upload:

• Hydrology information should be captured by stream within the Hydrology Data Capture Task. For reference to the data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, Data Capture - General, Data Capture - Workflow Details, and related guidance documents

Validation:

• All Project data uploaded to the MIP through a Project workflow needs to be reviewed and validated for completeness against the current Data Capture standards by a MIP super-user, typically a MIP Black Belt

Create Hydrology Purchase & Tasks

While in the purchase creation process, a Project Level Access user would locate the Hydrology purchase by selecting Data Development Purchase Group. Once that option is selected the Purchase dropdown will auto-populate and the option for the Hydrology will be made available. During the purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list and determine if associated uploaded data should be made available via FRiSEL.

Once a Project Level Access user has created the purchase, the user would then be able to create the relevant Tasks associated with the specific Purchase as listed in the Purchases and Tasks Overview section of this document.

FEMA Official MIP Studies Guidance Highlights:

• Purchase Geography: The geography of a hydraulic purchase will vary depending on Project scope (e.g., state, watershed, countywide, or county-community)
• Purchase Contacts: Regional FEMA Contact, TO manager, PM for PTS or CTP. This could also include State and Federal Agency contacts
• Purchase Field Description: Provide narrative identifying if this is a traditional stream-based hydrology analysis, LSAE or LAMP analysis
• Purchase Type Indicator: PMR, Revised Preliminary, LSAE, or BLE as applicable. The purchase type indicator of LSAE should be selected to differentiate between this type of hydrologic analysis and traditional hydrologic modeling. If a Project scope of work includes both LSAE and traditional modeling, then the Project creator will need to create separate hydrology purchases
• Tasks Required to Support Purchase:
  • KDP 0 and 1, if not already completed
  • Validation
• Task Name: Hydrologic Analysis for 'Watershed Number (County or Community)', 'Watershed Number (County or Community) Mapping Partner name', 'LSAE' or Leverage
• Task Description: Identify if this is a traditional stream-based hydrology analysis, LSAE or LAMP analysis
• Tasks Assignments:
  • KDP Zero: FEMA Region or their designee
  • KDP One: FEMA Region or their designee
  • Hydrology Data Capture: Mapping Partner (funded to perform work)
  • Hydrology Validation: FEMA Region or their designee (MIP BB or Regional POC)
  • Hydrology Independent QA/QC: Mapping Partner (funded to review work)
• EV Information: Will be tracked at the Task Level for the Hydrology Data Capture Task and the Hydrology Independent QA/QC Task

Capture Hydrology Data Task

Task Start: This data capture Task can start once confirmation is received that both KDP 0 and KDP 1 have been completed

Below is the view of the Capture Hydrology Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Hydrology Data and perform the automated Metadata Validation
• Analysis Section allows the user to indicate details specific to the Task and Leverage information (including Model Information and Leverage data sets)
• Auto-Generate Tasks allows the user to choose to auto-generate the Hydrology Data Validation Task
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Hydrology Validation and Hydrology Independent QA/QC Tasks

The only editable sections of this Task are the Submit Data, Analysis, add Leverage, Auto-Generate Tasks, and Comments sections. Steps include:

1. Within the Submit Data Section, a user must select a Data Location from the drop-down menu.
   1. Pre-populated options are listed, and a user can select:
   • MIP - Select this option if data is being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer
   • Risk MAP IT Help - Select this option if data is not being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer. Instead this data must be physically sent to CDS for uploading, please see MIP Guidance document for further details on this process.
2. Upload Hydraulics data
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task.
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. After uploading the file, select Run Validation to trigger metadata validation.
   4. To view uploaded files in File Explorer, select the View in File Explorer link
   5. Select the View Details link for more information on the results of the auto validation. If the status displays Failed, the View Details link provides specific information on what part of the metadata failed the review
3. A user can add Model Information by selecting the Add button under the Model Information section
   1. Model information must be entered by drainage area by manually entering the information such as, Type of Study, Model and Drainage Area Studied.
   2. The user will then be required to enter Stream Name, Type of Study, Actual Linear Miles, and Model
   3. Once those fields are completed the user must select the Save button

      

4. A user can add Leverage to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

5. Auto-Generate Tasks: The user can choose to auto-generate the Hydrology Data Validation Task when creating the Hydrology Data Capture Task. To do so, the steps are:
   1. Check the "Auto-Generate Tasks" box
   2. Enter a descriptive suffix in the "Generated Task Suffix" field
6. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Hydrology Validation Task

Below is the view of the Validate Hydrology Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validation Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a Validation document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the validation Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Hydrology Independent QA/QC Task

The Independent QA/QC Task is initiated when the Data Capture Task is completed, and the Validation Task is completed/approved. The Independent QA/QC checks the technical correctness of the mapping and submittal files for completeness and quality excellence. This Task may be completed by a Mapping Partner; the Independent QA/QC is conducted by either the same Mapping Partner who completed the Data Capture Task (but by a different and independent production group) or by an independent technical reviewer.

Below is the view of the Independent QA/QC Hydrology Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• QA/QC Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary QA/QC checklists as well as provide general comments related to this independent review

The only editable sections of this Task are the Independent QA/QC Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a QA/QC document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the QA/QC Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Levee Purchase

This Task will allow a user to Capture Levee/LAMP Data, Validate the Levee/LAMP Data, and complete an Independent QA/QC.

Purpose: Capture levee and LAMP data packages, correspondence, and supporting documentation

• Levee Data Capture: This Task is intended to capture levee certification packages, new PAL offers, or natural valley concurrence letters. However, modeling data should be captured in the appropriate hydraulic and hydrologic purchases.
• LAMP Data Capture: This Task is intended to LAMP Phase One (Identification) and Two (Plan & Preparation) documentation, including the final report. However, modeling data should be captured in the appropriate hydraulic and hydrologic purchases. In addition, this Task captures levee meeting (LLPT 1 and LLPT 2) data for pre-meeting, meeting, and post-meeting activities related to levee meetings.

Tasks:

• Levee Data Capture (with option to auto-generate Levee Data Validation Task)
• LAMP Data Capture (with option to auto-generate LAMP Data Validation Task)
• Levee Data Validation
• LAMP Data Validation
• Levee Data Independent QA/QC
• LAMP Data Independent QA/QC
• KDP Zero
• KDP One

Data Upload:

• For reference to levee data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, Data Capture - General, and Data Capture - Workflow Details guidance documents

Validation:

• All Project data uploaded to the MIP through a Project workflow needs to be reviewed and validated for completeness against the current Data Capture standards by a MIP super-user, typically a MIP Black Belt.

Create Levee Purchase & Tasks

While in the purchase creation process, a Project Level Access user would locate the Hydrology purchase by selecting Data Development Purchase Group. Once that option is selected the Purchase dropdown will auto-populate and the option for the Hydrology will be made available. During the purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list

Once a Project Level Access user has created the purchase, the user would then be able to create the relevant Tasks associated with the specific Purchase as listed in the Purchases and Tasks Overview section of this document

FEMA Official MIP Studies Guidance Highlights:

• Purchase Geography: The geography of a levee purchase will typically be the county and communities impacted by the levee system. The typical purchase-Task set-up would be a single levee system, linked to a single LAMP Plan or Levee data package. However, for a Project with multiple systems the purchase geography should be comprehensive reflecting all communities impacted by all the levee systems within the Project footprint. Wherever multiple levee systems within in the same county have separate data packages (e.g. sound reach submittal, PAL offer, etc.) the Project creator could set-up multiple levee Tasks within the same purchase to capture each levee data package separately
• Purchase Contacts: Suzanne Vermeer, Michael Nakagaki, Brian Koper
• Purchase Field Description: Enter all levee System IDs from the National Levee Database associated with the purchase
• Purchase Type Indicator: PMR or Revised Preliminary as applicable
• Tasks Required to Support Purchase
  • KDP 0 and 1, if not already completed
  • Validation
• Task Name: LeveeName_Approach (Accreditation or LAMP)
• Task Description: Consider including whether the Task associated with new, restudied, or leveraged analysis. Include a list of stakeholders, the study extent, a description of the associated Geography, and Mapping Partner (PTS/CTP) information. Include any other relevant information the Project Access Level user deems useful.
• Tasks Assignments:
  • KDP Zero: FEMA Region or their designee
  • KDP One: FEMA Region or their designee
  • Levee or LAMP Data Capture: Mapping Partner (funded to perform work)
  • Levee or LAMP Validation: FEMA Region or their designee (MIP BB or Regional POC)
  • Levee or LAMP Independent QA/QC: Mapping Partner (funded to review work)
• EV Information: Will be tracked at the Task Level for the Levee/LAMP Data Capture Task and the Levee/LAMP Independent QA/QC Task

Capture Levee Data Task

Task Start: This Task is primarily a file storage mechanism that can be triggered by submittal of a certification package, determination that a PAL offer is required, LAMP Phase Two that includes a procedure other than natural valley, or a natural valley concurrence letter. KDP 0 and KDP 1 would typically be required prior to starting this Task.

Below is the view of the Capture Levee Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Levee Data and perform the automated Metadata Validation
• Analysis Section allows the user to indicate details specific to the Task such as NLD System ID (enter levee system identification number(s) from the National Levee Database), LAMP Plan Completion Date (enter date LAMP Plan was completed), FAST Levee Studies ID (enter Primary Key from the FAST database), Levee Analysis that is applicable and Leverage information
• Auto-Generate Tasks allows the user to choose to auto-generate the Levee Data Validation Task
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Levee Validation and Levee Independent QA/QC Tasks

The only editable sections of this Task are the Submit Data, Analysis, add Leverage, Auto-Generate Tasks, and Comments sections. Steps include:

1. A user can upload a data file
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. To view uploaded files in File Explorer, select the View in File Explorer link
2. A user can add NLD System ID by selecting the Edit button to the right of the NLD System ID section
   1. The user will then be required to select which NLD System ID from a prepopulated table
   2. Once the NLD System ID are selected the user must select the Add button

      

3. A user can enter the LAMP Levee Studies ID
4. A user can add Levee Analysis or Approach by selecting one of the options (65.10 Compliant, Natural Valley, Provisional Accreditation, Freeboard Deficient, Overtopping, Other)
5. A user can add Leverage to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

6. Auto-Generate Tasks: The user can choose to auto-generate the Levee Data Validation Task when creating the Levee Data Capture Task. To do so, the steps are:
   1. Check the "Auto-Generate Tasks" box
   2. Enter a descriptive suffix in the "Generated Task Suffix" field
7. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Capture LAMP Data Task

Task Start: LAMP Phase One (Identification) and Two (Plan Preparation) tend to go in order. KDP 0 is needed before starting.

Below is the view of the Capture LAMP Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload LAMP Data and perform the automated Metadata Validation
• Analysis Section allows the user to indicate details specific to the Task such as NLD System ID (enter levee system identification number(s) from the National Levee Database, Modeling approach (select all that apply), LAMP Meeting information and Leverage information
• Auto-Generate Tasks allows the user to choose to auto-generate the LAMP Data Validation Task
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the LAMP Validation and LAMP Independent QA/QC Tasks

The only editable sections of this Task are the NLD System ID, LAMP Plan, Modeling Approach, Local Levee Partnership Team (LAMP) Meetings, add Leverage, Auto-Generate Tasks, and Comments sections. Steps include:

1. A user can upload a data file
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. To view uploaded files in File Explorer, select the View in File Explorer link
2. A user can add NLD System ID by selecting the Edit button to the right of the NLD System ID section
   1. The user will then be required to select which NLD System ID from a prepopulated table
   2. Once the NLD System ID are selected the user must select the Add button

      

3. Next a user can enter the LAMP Plan Completion Date
4. A user can indicate which Modeling Approach was used by selecting either: Freeboard Deficient, Natural Valley, Overtopping, Sound Reach, Structural Inundation, 65.10 Compliant, or Other
5. A user can add Local Levee Partnership Team (LAMP) Meeting by selecting the Add button
   1. The user will then be required to enter the Meeting Name, Meeting Type, and Date
   2. Meeting name should include levee location, and meeting city and state (example: Arkham City LLPT Meeting Arkham ST)
   3. Meeting type should identify details of the type of meeting held (webinar, in-person, etc.)
   4. LAMP completion date is the date the plan was finalized
   5. Once those fields are completed the user must select the Add button

      

6. A user can add Leverage to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

7. Auto-Generate Tasks: The user can choose to auto-generate the LAMP Data Validation Task when creating the LAMP Data Capture Task. To do so, the steps are:
   1. Check the "Auto-Generate Tasks" box
   2. Enter a descriptive suffix in the "Generated Task Suffix" field
8. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Levee Validation Task

Below is the view of the Validate Levee Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validation Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a Validation document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the validation Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

LAMP Validation Task

Below is the view of the Validate LAMP Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validation Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a Validation document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the validation Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Levee Independent QA/QC Task

The Independent QA/QC Task is initiated when the Data Capture Task is completed, and the Validation Task is completed/approved. The Independent QA/QC checks the technical correctness of the mapping and submittal files for completeness and quality excellence. This Task may be completed by a Mapping Partner; the Independent QA/QC is conducted by either the same Mapping Partner who completed the Data Capture Task (but by a different and independent production group) or by an independent technical reviewer.

Below is the view of the Validate Levee Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• QA/QC Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary QA/QC checklists as well as provide general comments related to this independent review

The only editable sections of this Task are the QAQC Status fields. Steps include:

1. A user must select Approve or Reject QAQC
2. Next a user can upload a QAQC document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the validation Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

LAMP Independent QA/QC Task

The Independent QA/QC Task is initiated when the Data Capture Task is completed, and the Validation Task is completed/approved. The Independent QA/QC checks the technical correctness of the mapping and submittal files for completeness and quality excellence. This Task may be completed by a Mapping Partner; the Independent QA/QC is conducted by either the same Mapping Partner who completed the Data Capture Task (but by a different and independent production group) or by an independent technical reviewer.

Below is the view of the Validate LAMP Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• QA/QC Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary QA/QC checklists as well as provide general comments related to this independent review

The only editable sections of this Task are the QAQC Status fields. Steps include:

1. A user must select Approve or Reject QAQC
2. Next a user can upload a QAQC document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the validation Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Survey Purchase

This purchase will allow a user to Capture, Validate, and complete an Independent QA/QC of Survey Data, and complete KDP Zero and One.

Purpose: Tasks associated with this activity are performed to upload Survey Data and associated metadata to the MIP for auto QA.

Tasks:

• Survey Data Capture (with option to auto-generate the Survey Data Validation Task)
• Survey Data Validation
• Survey Data Independent QA/QC
• KDP Zero
• KDP One

Data Upload:

• For reference to the data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, Data Capture - General, Data Capture - Workflow Details, and related guidance documents

Validation:

• All Project data uploaded to the MIP workflow needs to be reviewed and validated for completeness against the current Data Capture standards by a MIP super-user, typically a MIP Black Belt

Create Survey Purchase & Tasks

While in the purchase creation process, a Project Level Access user would locate the Survey purchase by selecting Data Development Purchase Group. Once that option is selected the Purchase dropdown will auto-populate and the option for the Survey purchase will be made available. During the purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list.

Once a Project Level Access user has created the purchase, the user would then be able to create the relevant Tasks associated with the specific Purchase as listed in the Purchases and Tasks Overview section of this document.

FEMA Official MIP Studies Guidance Highlights:

• Purchase Geography: Purchase geography can be county, watershed, multiple CIDs, dependent on the scope of work
• Purchase Contacts: Regional FEMA Contact, TO manager, PM for PTS or CTP. This could also include State and Federal Agency contacts.
• Purchase Field Description: Provide a short narrative of study type (new, re-studied, leveraged), the area studied and unique identifiers of the stakeholders, geography, and communities.
• Purchase Type Indicator: PMR or Revised Preliminary as applicable
• Tasks Required to Support Purchase:
  • KDP 0 and 1, if not already completed
  • Validation
• Task Name: should include a descriptor of the associated Geography(ies) and/or data creator, such as Flood Watershed (County, Jurisdiction) Survey Data Capture, or Flood Watershed (County, Jurisdiction) Survey Fan Data Capture.
• Task Description: Consider including whether the Task associated with new, restudied, or leveraged analysis and include a list of stakeholders, the study extent, a description of the associated Geography, and Mapping Partner (PTS/CTP) information. Include any other relevant information the Project Access Level user deems useful.
• Task Assignments:
  • KDP Zero: FEMA Region or their designee
  • KDP One: FEMA Region or their designee
  • Survey Data Capture: Mapping Partner (funded to perform work)
  • Survey Validation: FEMA Region or their designee (MIP BB or Regional POC)
  • Survey Independent QA/QC: Mapping Partner (funded to review work)
• EV Information: Will be tracked at the Task Level for the Levee/LAMP Data Capture Task and the Levee/LAMP Independent QA/QC Task

Capture Survey Data Task

Task Start: This data capture Task can start once confirmation is received that both KDP 0 and KDP 1 have been completed

The Capture Survey Task includes the following sections, as shown in the example below:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Survey Data and perform the automated Metadata Validation
• Analysis Section allows the user to indicate Leveraged datasets and details
• Auto-Generate Tasks Section allows the user to choose to auto-generate the Survey Data Validation Task
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Survey Data Validation and Survey Data Independent QA/QC Tasks

The only editable sections of this Task are the Submit Data, Analysis, add Leverage, Auto-Generate Tasks, and Comments sections. Steps include:

1. Upload Survey data
   1. Keep in mind that regardless of the Purchase Geography type set during the Purchase setup phase by the Project Level Access User, the Data Capture Standards specify that Survey Data be uploaded per HUC8 entity. For reference to the data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, and the Data Capture - General and Data Capture - Workflow Details Guidance.
   2. After selecting the file, a user must select the Upload File button to have the file saved to the Task
   3. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   4. After uploading the file, select Run Validation button to trigger metadata validation.
   5. To view uploaded files in File Explorer, select the View in File Explorer link
   6. Select the View Details link for more information on the results of the auto validation. If the status displays Failed, the View Details link provides specific information on what part of the metadata failed the review
2. Add Leverage to the Task:
   1. Under the Leverage section, select the Add button
   2. Enter the Quantity, Type, Unit, Contributed By, Federal Fiscal Year (all required fields) and Comments
   3. Once those fields are completed the user must select the Save button.

      

3. Auto-Generate Tasks: The user can choose to auto-generate the Survey Data Validation Task when creating the Survey Data Capture Task. To do so, the steps are:
   1. Check the "Auto-Generate Tasks" box
   2. Enter a descriptive suffix in the "Generated Task Suffix" field
4. A user can select the Save button at any point during this process. Once all the mandatory fields are completed, the user can select the Submit button.

Survey Validation Task

The Validate Survey Validation Task includes the following sections, as shown in the example below:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validation Status fields. To edit these sections, steps include:

1. Approve or Reject Validation (user must select one)
2. Upload a Validation document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. The Validator may also enter any comments regarding the Validation Task.
4. The user can select the Save button at any point during this process. Once all the mandatory fields are completed the user can select the Submit button

Survey Independent QA/QC Task

The Independent QA/QC Task is initiated when the Data Capture Task is completed, and the Validation Task is completed/approved. The Independent QA/QC checks the technical correctness of the mapping and submittal files for completeness and quality excellence. This Task may be completed by a Mapping Partner; the Independent QA/QC is conducted by either the same Mapping Partner who completed the Data Capture Task (but by a different and independent production group) or by an independent technical reviewer.

The Survey Independent QA/QC Task includes the following sections, as shown in the example below:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• QA/QC Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary QA/QC checklists as well as provide general comments related to this independent review

The only editable sections of this Task are the Independent QA/QC Status fields. To edit these sections, steps include:

1. Approve or Reject Validation (user must select one)
2. Upload a QA/QC document.
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task.
3. The Independent Reviewer may also enter any comments regarding the QA/QC Task
4. A user can select the Save button at any point during this process. Once all the mandatory fields are completed the user can select the Submit button

Terrain Purchase

This Purchase will allow a user to Capture, Validate, and complete an Independent QA/QC of Terrain Data, the finished elevation surface used for modeling.

Purpose: Capture final terrain dataset(s) to support floodplain mapping activities and development of flood risk products. Input elevation datasets are captured under the Topographic data Tasks.

Tasks:

• Terrain Data Capture (with option to auto-generate the Terrain Data Validation Task)
• Terrain Data Validation
• Terrain Data Independent QA/QC
• KDP Zero
• KDP One

Data Upload:

• For reference to the data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, Data Capture - General, Data Capture - Workflow Details, and related guidance documents
• Source data sets for a Project should be uploaded under a Topographic Data Purchase. There are Task types for new topographic data and existing topographic data. If some of the source elevation data used for this Project was uploaded on a different MIP Project, you do not need to upload it again. Instead, you reference the data from the other Project in the Terrain Data Capture Task.

Validation:

• All Project data uploaded to the MIP through a Project workflow needs to be reviewed and validated for completeness against the current Data Capture standards by a MIP super-user, typically a MIP Black Belt.

Create Terrain Purchase & Tasks

While in the purchase creation process, a Project Level Access user would locate the Terrain Data Purchase by selecting Data Development Purchase Group. Once that option is selected the Purchase dropdown will auto-populate and the option for the Terrain will be made available. During the purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list.

Once a Project Level Access user has created the purchase, the user would then be able to create the relevant Tasks associated with the specific Purchase as listed in the Purchases and Tasks Overview section of this document.

FEMA Official MIP Studies Guidance Highlights:

• Purchase Geography: Typically, A single purchase should be created for terrain purchase to cover the extent of the Project, However, if a Project has two or more distinct engineering purchases with separate geographies where separate terrain surfaces will be compiled for each, then there should be a corresponding Terrain Purchase for each distinct engineering geography. An example of this would be a Project with riverine and coastal component where each activity built their own elevation surface for modeling. Each area could be represented by separate Terrain purchases with appropriate geography.
• Purchase Contacts: Regional FEMA Contact, Lead FEMA Engineer, Task Order Manager, PM for PTS or CTP
• Purchase Field Description: Provide a short narrative of study type (new, re-studied, leveraged), the area studied and unique identifiers of the stakeholders, geography, and communities for the final terrain dataset(s) which support floodplain mapping activities and development of flood risk products.
• Purchase Type Indicator: PMR or Revised Preliminary as applicable
• Tasks Required to Support Purchase:
  • KDP 0 and 1, if not already completed
  • Validation
• Task Name: Development of Terrain data for "watershed name", "county name", or "community name"
• Task Description: The development of Terrain data that meet FEMA standards and guidance for use in a Risk MAP Project
• Task Assignments:
  • KDP Zero: FEMA Region or their designee
  • KDP One: FEMA Region or their designee
  • Terrain Data Capture: Mapping Partner (funded to perform work)
  • Terrain Validation: FEMA Region or their designee (MIP BB or Regional POC)
  • Terrain Independent QA/QC: Mapping Partner (funded to review work)
• EV Information: Will be tracked at the Task Level for the Terrain Data Capture Task, the Terrain Validation Task, and the Terrain Independent QA/QC Task

Capture Terrain Data

Task Start: This Task typically starts at the beginning of modeling activities since the terrain surface is central to most of the modeling work. Some Projects may begin with Large Scale Automated Engineering or Base Level Engineering work prior to Discovery. In these cases, compilation of a terrain surface will usually need to take place prior to these engineering activities, so a Capture Terrain Data Task will be needed along with the H&H purchases. KDP 0 and 1 would typically be required prior to starting this Task.

Below is the view of the Capture Terrain Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Terrain Data and perform the automated Metadata Validation
• Analysis Section allows the user to indicate details specific to the Task and Leverage information
• Auto-Generate Tasks Section allows the user to choose to auto-generate the Terrain Data Validation Task
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Terrain

The only editable sections of this Task are the Submit Data, Analysis, add Leverage, Auto-Generate Tasks, and Comments sections. Steps include:

1. Within the Submit Data Section, a user must select a Data Location from the drop-down menu.
   1. Pre-populated options are listed, and a user can select:
   • MIP - Select this option if data is being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer
   • Risk MAP IT Help - Select this option if data is not being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer. Instead this data must be physically sent to CDS for uploading, please see MIP Guidance document for further details on this process.
2. Upload Terrain data
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task.
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. After uploading the file, select Run Validation to trigger metadata validation.
   4. To view uploaded files in File Explorer, select the View in File Explorer link
   5. Select the View Details link for more information on the results of the auto validation. If the status displays Failed, the View Details link provides specific information on what part of the metadata failed the review
3. A user can add Data Sources from Other Projects to the Task by selecting the Add button under the Data Sources from Other Projects section. This section is only used when there are source datasets incorporated into the final terrain that are not uploaded in other purchases is the current Project because they were previously uploaded to the MIP in a different Project. This allows all the source data for this Project to be accounted for.
   1. The user will then be required to enter Data Source and Data Type. A user can also enter the Purchase ID
   2. Once those fields are completed the user must select the Save button

      

4. A user can add Leverage to the Task by selecting the Add button under the Leverage section. Only include leverage specific to compiling the source topographic data into the final terrain surface. Leverage associated with the source data should be captured under the topographic data Tasks.
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

5. Auto-Generate Tasks: The user can choose to auto-generate the Terrain Data Validation Task when creating the Terrain Data Capture Task. To do so, the steps are:
   1. Check the "Auto-Generate Tasks" box
   2. Enter a descriptive suffix in the "Generated Task Suffix" field
6. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Terrain Validation Task

Below is the view of the Validate Terrain Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validation Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a Validation document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the validation Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Terrain Independent QA/QC Task

The Independent QA/QC Task is initiated when the Data Capture Task is completed, and the Validation Task is completed/approved. The Independent QA/QC checks the technical correctness of the mapping and submittal files for completeness and quality excellence. This Task may be completed by a Mapping Partner; the Independent QA/QC is conducted by either the same Mapping Partner who completed the Data Capture Task (but by a different and independent production group) or by an independent technical reviewer.

Below is the view of the Independent QA/QC Terrain Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• QA/QC Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary QA/QC checklists as well as provide general comments related to this independent review

The only editable sections of this Task are the Independent QA/QC Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a QA/QC document
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
3. A reviewer can also enter any comments regarding the QA/QC Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Topographic Purchase

This purchase will allow a user to capture new or existing Topographic Data, Validate the Topographic Data, and complete an Independent QA/QC.

Purpose: Capture new or existing topographic data or any partner leverage. Topographic data will be used for the development of terrain data to support floodplain mapping activities and Risk MAP flood risk products. Topographic data deliverables must comply with FEMA data capture standards and comply with Federal Geographic Data Committee (FGDC) metadata requirement. The source elevation data for a Project is uploaded under the Topographic Purchase, the finished elevation surfaces used for the modeling are uploaded under Terrain Purchases.

• New Topographic Data - FEMA purchased LiDAR data / data partially funded by FEMA
• Existing Topographic Data Capture - gathered topographic data from existing sources, which may also quality as leverage data

Tasks:

• New Topographic Data Capture (FEMA purchase LiDAR data, with option to auto-generate New Topographic Data Validation Task)
• Existing Topographic Data Capture (Gathered topographic data from existing sources, which may also quality as leverage data. Option to auto-generate Existing Topographic Data Validation Task)
• New Topographic Data Validation
• Existing Topographic Data Validat`ion
• New Topographic Data Independent QA/QC
• Existing Topographic Data Independent QA/QC
• KDP Zero
• KDP One

Data Upload:

• For reference to the data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, Data Capture - General, Data Capture - Workflow Details, and related guidance documents

Validation:

• All Project data uploaded to the MIP through a Project workflow needs to be reviewed and validated for completeness against the current Data Capture standards by a MIP super-user, typically a MIP Black Belt

Create Topographic Purchase & Tasks

While in the purchase creation process, a Project Level Access user would locate the Topographic purchase by selecting Data Development Purchase Group. Once that option is selected the Purchase dropdown will auto-populate and the option for the Topographic will be made available. During the purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list.

Once a Project Level Access user has created the purchase, the user would then be able to create the relevant Tasks associated with the specific Purchase as listed in the Purchases and Tasks Overview section of this document

FEMA Official MIP Studies Guidance Highlights:

• Purchase Geography:
  • New Topographic Data Capture: A single purchase should be created for each new topographic purchase to cover the extent of the Project.
  • Existing Topographic Data Capture: Typically, a single purchase should be created for each existing topographic purchase to cover the extent of the Project. However, if a Project has two or more distinct engineering purchases with separate geographies where separate topographic data will be compiled for each, then there should be a corresponding Topographic Purchase for each distinct engineering geography. An example of this would be a Project with riverine and coastal component where each activity built their own elevation surface for modeling. Each area could be represented by separate Terrain purchases with appropriate geography.
• Purchase Contacts: FEMA Contact, Lead FEMA Engineer, Task Order Manager, PM for PTS or CTP
• Purchase Field Description: Data collected must cover the geography of the purchase and will be used as the source for developing the final terrain data to support floodplain mapping activities and the development of flood risk products
• Purchase Type Indicator: PMR or Revised Preliminary as applicable
• Tasks Required to Support Purchase:
  • KDP 0 and 1, if not already completed
  • Validation
• Task Name: Development of Terrain data for "watershed name", "county name", or "community name"
1. New Topographic Data Capture: Acquisition of new topographic data for 'watershed name', 'county name', or 'community name'
2. Existing Topographic Data Capture: Acquisition of existing topographic data for 'watershed name', 'county name', or 'community name'
• Task Description: The acquisition of new topographic data that meet FEMA standards and guidance for use in a Risk MAP Project
• Task Assignments:
  • KDP Zero: FEMA Region or their designee
  • KDP One: FEMA Region or their designee
  • New or Existing Topographic Data Capture: Mapping Partner (funded to perform work)
  • New or Existing Topographic Validation: FEMA Region or their designee (MIP BB or Regional POC)
  • New or Existing Topographic Independent QA/QC: Mapping Partner (funded to review work)
• EV Information: Will be tracked at the Task Level for the New Topographic Capture Task and the New Topographic Independent QA/QC Tasks. EV information is optional for Existing Data Capture and Existing QA/QC Tasks.

Capture New Topographic Data Task

Task Start: New Topographic Data collection can start at any point. Often topographic data collection is the first activity in a Project or the only activity. Topographic data collection is often seasonal, so even if the Task order is awarded, the scheduled start date for collecting the data may be several months away. New topographic data also requires substantial processing of the data once collected and internal QA/QC. The end date for the New Topographic Data Collection Task should account for this time.

For New topographic data independent QA/QC must be completed prior to validation. This is due to the delivery requirements for large datasets. Validation would occur after the data has been received by Risk MAP IT Help/ Data Depot or the FEMA library. After the data has been validated then the Task would be complete.

Below is the view of the Capture New Topographic Data Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload New Topographic and Existing Topographic Data Capture Tasks and perform the automated Metadata Validation
• Analysis Section allows the user to indicate details specific to the Task and Leverage information (including Database Schema, Vertical & Horizontal Accuracy, and Leverage data sets)
• Auto-Generate Tasks allows the user to choose to auto-generate the New Topographic Data Validation Task
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the New Topographic Data Validation and New Topographic Data Independent QA/QC Tasks

The only editable sections of this Task are the Submit Data, Analysis, add Leverage, Auto-Generate Tasks, and Comments sections. Steps include:

1. Within the Submit Data Section, a user must select a Data Location from the drop-down menu.
   1. Pre-populated options are listed, and a user can select:
   • MIP - Select this option if data is being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer
   • Risk MAP IT Help - Select this option if data is not being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer. Instead this data must be physically sent to CDS for uploading, please see MIP Guidance document for further details on this process.
2. Upload Topographic data
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task.
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. After uploading the file, select Run Validation to trigger metadata validation.
   4. To view uploaded files in File Explorer, select the View in File Explorer link
   5. Select the View Details link for more information on the results of the auto validation. If the status displays Failed, the View Details link provides specific information on what part of the metadata failed the review
3. A User can add both CTP and Non-CTP Leverage to the Task by selecting the Add button under the Leverage section. Leverage for new Topographic data collection is typically cost share funding, though sometimes there can be in-kind contributions like field survey or QA/QC.
   1. A user can select either the CTP or Non- CTP button to indicate which type of Leverage to add to the Task
   2. Based on the selection of either CTP or Non-CTP Leverage the user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments. Please note, if Non-CTP Leverage is chosen the Unit field will be predefined to Dollar(s)and users can enter the amount in the Type field
   3. Once those fields are completed the user must select the Save button

      

      

4. Auto-Generate Tasks: The user can choose to auto-generate the New Topographic Data Validation Task when creating the New Topographic Data Capture Task. To do so, the steps are:
   1. Check the "Auto-Generate Tasks" box
   2. Enter a descriptive suffix in the "Generated Task Suffix" field
5. A user can select on the Save button at any point during this process or once all the mandatory fields are completed the user can click on the Submit button

Capture Existing Topographic Data Task

Task Start: This Task can take place at a variety of different points in a Project depending on the Project structure. In a typical watershed Project that begins with Discovery, finding and gathering topographic data will typically be part of Discovery and can occur as part of the pre-Discovery research and preparation or any time throughout Discovery. Typically, a Capture Existing Topographic Data Task should be created whenever there is a Discovery purchase. However, some Projects may begin with Large Scale Automated Engineering or Base Level Engineering work prior to Discovery. In these cases, finding existing topographic data will usually need to take place prior to these engineering activities, so a Capture Existing Topographic Data Task will be needed along with the H&H purchases. It may also sometimes be the case that existing topographic data is gathered after Discovery. If a Project is planned this way, a Capture Existing Topographic Data Task can be created as part of the other Data Development purchases. If additional existing topographic data is unexpectedly received after Discovery or closing out the prior Capture Existing Topographic Data Task, the Project owner can reopen the Existing Topographic Data Task, so the data can be uploaded.

Below is the view of the Existing Topographic Data Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Existing Topographic Data and perform the automated Metadata Validation
• Analysis Section allows the user to indicate details specific to the Task and Leverage information
• Leveraged Datasets: existing elevation datasets not funded by FEMA and not previously used on a FEMA mapping Project. Leverage for existing lidar / topo will normally be reported in terms of square miles of data.
• Non-Leverage Datasets: existing elevation from other sources used but not considered leverage or to count toward leverage quantities. Generally, we only want to count leverage once, so if a dataset was used previously on a flood map, we don't want to count it again. This can be difficult to determine, so a simple rule is if the data is older than the prior map revision do not count it as leverage. Lidar data from 3DEP can also be difficult to determine if we should count it as leverage. For many USGS / 3DEP Projects it can also be difficult to know if FEMA already contributed funds to the data collection or not.
• Auto-Generate Tasks Section allows the user to choose to auto-generate the Existing Topographic Data Validation Task
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Existing Topographic Data Validation and Existing Topographic Data Independent QA/QC Tasks

The only editable sections of this Task are the Submit Data, Add Leveraged Datasets, Add Non-Leveraged Datasets, Auto-Generate Tasks, and Comments sections. Steps include:

1. Within the Submit Data Section, a user must select a Data Location from the drop-down menu.
   1. Pre-populated options are listed, and a user can select:
   • MIP - Select this option if data is being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer
   • Risk MAP IT Help - Select this option if data is not being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer. Instead this data must be physically sent to CDS for uploading, please see MIP Guidance document for further details on this process.
2. Upload Topographic data
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task.
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. After uploading the file, select Run Validation to trigger metadata validation.
   4. To view uploaded files in File Explorer, select the View in File Explorer link
   5. Select the View Details link for more information on the results of the auto validation. If the status displays Failed, the View Details link provides specific information on what part of the metadata failed the review
3. A user can add Leveraged datasets to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Vertical Accuracy, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

4. A user can add Non-Leveraged datasets to the Task by selecting the Add button under the Non-Leverage datasets section
   1. The user will then be required to enter Quantity, Type, Unit, Vertical Accuracy, Contributed By, Federal Fiscal Year, and Comments
   2. Once those fields are completed the user must select the Save button

      

5. Auto-Generate Tasks: The user can choose to auto-generate the Existing Topographic Data Validation Task when creating the Existing Topographic Data Capture Task. To do so, the steps are:
   1. Check the "Auto-Generate Tasks" box
   2. Enter a descriptive suffix in the "Generated Task Suffix" field
6. A user can select on the Save button at any point during this process or once all the mandatory fields are completed the user can click on the Submit button

Topographic Validation Task

This is the view of the Validate Topographic Data Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validation Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a Validation file
3. A reviewer can also enter any comments regarding the validation Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Topographic Independent QA/QC Task

The Independent QA/QC Task is initiated when the Data Capture Task is completed, and the Validation Task is completed/approved. The Independent QA/QC checks the technical correctness of the mapping and submittal files for completeness and quality excellence. This Task may be completed by a Mapping Partner; the Independent QA/QC is conducted by either the same Mapping Partner who completed the Data Capture Task (but by a different and independent production group) or by an independent technical reviewer.

Below is the view of the Independent QA/QC Topographic Data Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• QA/QC Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary QA/QC checklists as well as provide general comments related to this independent review

The only editable sections of this Task are the Independent QA/QC Status fields. Steps include:

1. A user must select Approve or Reject QAQC
2. Next a user can upload a QA/QC document
3. A reviewer can also enter any comments regarding the QA/QC Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

General Purchase

This purchase will allow a user to Capture, Validate, and complete an Independent QA/QC of General Data.

Purpose: This purchase accommodates data that may not align directly to the other purchase groups in the MIP. It allows for data to be stored and tracked in the MIP that otherwise would not have had that level of transparency, such as management, costs, additional provider support that is outside of other MIP Purchases. These purchases can be used for activities within Risk MAP projects in addition to being used for Projects that fall outside of the Risk MAP process and do result in mapping products. FEMA has determined that the MIP should be used for these items, allowing for costs to be captured and reports to be pulled. This purchase will allow a user to capture and validate General Data, and complete Independent QA/QC, if applicable.

The following General Data Task Types, which may be included in Risk MAP Projects, occur outside of mapping activities and program related activities:

Tasks:

• the Capture General Data (with option to auto-generate the General Data Validation Task)
• Validation of General Data
• Independent QA/QC of General Data

Data Upload:

• For reference to the data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, Data Capture - General and Data Capture - Workflow Details, and related guidance documents

Validation:

• All Project data uploaded to the MIP through a Project workflow needs to be reviewed and validated for completeness against the current Data Capture standards by a MIP super-user, typically a MIP Black Belt

Create General Purchase & Tasks

While in the purchase creation process, a Project Level Access user would locate the General purchase by selecting Data Development Purchase Group: Data Development. Once that option is selected the Purchase dropdown will auto-populate and the option for the General will be made available. During the purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list

Once a Project Level Access user has created the purchase, the user would then be able to create the relevant Tasks associated with the specific Purchase as listed in the Purchases and Tasks Overview section of this document. During the creation of the General Data Capture Task a Project Access Level User will be able to choose the Task Type to associate to the General Data Capture Task. Drop down options include: CERC Mitigation Action, CERC Mitigation Planning, CERC-MS (Regionally funded Mission Support), CERC-PS (Project Support), CTP-COMS-SOW (CERC-type- Support from CTP), CTP-PM-SOW (Program Management Grant), Due Process and Adoption Management, HMTAP-Non A&E (Disaster Dollars for non-A&E Services), HMTAP-PTS(Disaster Dollars for A&E Services), PM-Enhancements(PM contract - Additional Regional Support), Project Management Fees (CERC,PTS,CTP, PTS-MS (Regional Mission Support), PTS-TARC (Other Contract Dollars and Efforts for Research Information), Quality Assurance Management, RSC Enhancements, and RSO Management.

FEMA Official MIP Studies Guidance Highlights (For more detailed information see the individual General Purchase Section for the type of provider and task type):

• Purchase Contacts: PTS, CERC, CTP, PM
• Purchase Field Description: Briefly describe the purpose of the purchase specifically identifying the purchase type especially if "Other" is used for the purchase type
• Task Description: Briefly describe the purpose of the Task specifically identifying the Task type
• EV Information: Will be optional at the Task Level for the General Capture Task and the General QA/QC Tasks

General Data Capture

Below is the view of the General Data Capture Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload General Data and perform the automated Metadata Validation
• Analysis Section allows the user to indicate details specific to the Task and Leverage information
• Auto-Generate Tasks allows the user to choose to auto-generate the General Data Validation Task
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the General Validation and General Independent QA/QC Tasks

The only editable sections of this Task are the Submit Data, add Leverage, Auto-Generate Tasks, and Comments sections. Steps include:

1. A user can upload data files as long as the task has not been submitted
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. It is suggested that users create a file and folder structure that makes the most sense to the activity/ies being captured within the General Task. Since there is such a broad range of activities that can occur and/or type of data that may uploaded, it is recommended that providers follow any internal guidance that may have been created for uploads for their specific task types.
   4. To view uploaded files in File Explorer, select the View in File Explorer link
2. A user can add Leverage to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

3. Auto-Generate Tasks: The user can choose to auto-generate the General Data Validation Task when creating the General Data Capture Task. To do so, the steps are:
   1. Check the "Auto-Generate Tasks" box
   2. Enter a descriptive suffix in the "Generated Task Suffix" field
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

General Data Capture Validation

This is the view of the Validate General Data Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validation Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a Validation file
3. A reviewer can also enter any comments regarding the validation Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

General Data Capture Independent QA/QC

The Independent QA/QC Task is initiated when the Data Capture Task is completed, and the Validation Task is completed/approved. The Independent QA/QC checks the technical correctness of the mapping and submittal files for completeness and quality excellence. This Task may be completed by a Mapping Partner; the Independent QA/QC is conducted by either the same Mapping Partner who completed the Data Capture Task (but by a different and independent production group) or by an independent technical reviewer.

Below is the view of the Independent QA/QC General Data Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• QA/QC Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary QA/QC checklists as well as provide general comments related to this independent review

The only editable sections of this Task are the Independent QA/QC Status fields. Steps include:

1. A user must select Approve or Reject QAQC
2. Next a user can upload a QA/QC document
3. A reviewer can also enter any comments regarding the QA/QC Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

KDP 0 Task

Below is the view of the KDP 0 Task. A KDP 0 Task can be created under any of the Data Development or Discovery Purchases. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, and Purchase Geography(ies)
• Analysis Section allows user to enter if KDP is needed and the approval date as well as a reason if KDP is not needed
• Comments Section allows the user to enter any relevant comments

The only editable sections of this Task KDP 0 fields. Steps include:

1. A user must indicate where KDP 0 is needed or not
2. Next a user must enter the KDP 0 Approval Date
3. If a KDP 0 is not needed, then a user must provide a reason why
4. A reviewer can also enter any comments regarding the KDP 0 Task
5. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

KDP 1 Task

Below is the view of the KDP 1 Task. A KDP 1 Task can be created under any of the Data Development or Discovery Purchases. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, and Purchase Geography(ies)
• Analysis Section allows user to enter if KDP is needed and the approval date as well as a reason if KDP is not needed
• Comments Section allows the user to enter any relevant comments

The only editable sections of this Task KDP 1 fields. Steps include:

1. A user must indicate where KDP 1 is needed or not
2. Next a user must enter the KDP 1 Approval Date
3. If a KDP 1 is not needed, then a user must provide a reason why
4. A reviewer can also enter any comments regarding the KDP 1 Task
5. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

Preliminary Map Production Purchase

This purchase will allow a user to Produce Preliminary Product Data, Validate Preliminary Products, Complete an Independent QA/QC of Preliminary Products, Distribute Preliminary Products, and complete QR3, KDP 2, and KDP 3.

Purpose: Tasks associated with this activity are completed for any Preliminary Map Product Purchase, to upload and validate the Preliminary Map Products and associated metadata into the MIP for QA and auto QA.

Tasks:

• Produce Preliminary Products Data (option to auto-generate Preliminary Products Data Validation, QR3, KDP 3, and Distribute Preliminary Products Tasks)
• Validation of Preliminary Products Data
• Independent QA/QC of Preliminary Products Data
• Distribute Preliminary Products
• QR3
• KDP 2
• KDP 3

Data Upload:

• For reference to the data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, Data Capture - General, Data Capture - Workflow Details, and related guidance documents

Validation:

• All Project data uploaded to the MIP through a Project workflow needs to be reviewed and validated for completeness against the current Data Capture standards by a MIP super-user, typically a MIP Black Belt

Create Preliminary Purchase & Tasks

While in the purchase creation process, a Project Level Access user would locate the Preliminary purchase by selecting Purchase Group: Preliminary. Once that option is selected the Purchase dropdown will auto-populate and the option for the Preliminary purchase will be made available. During the purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list

If Revised Preliminary materials become necessary, this requires a second Preliminary Purchase. A Purchase Level Access user should use the "Revised Preliminary" Purchase Type Indicator when creating this second purchase. Include a Purchase description such as, "Revised Preliminary due to appeals" or, "Revised Preliminary materials due to new data received."

Once a Project Level Access user has created the purchase, the user would then be able to create the relevant Tasks associated with the specific Purchase as listed in the Purchases and Tasks Overview section of this document

FEMA Official MIP Studies Guidance Highlights:

• Purchase Geography: The associated Geography for the Preliminary Purchase should always be at the Jurisdiction level (County entity or Single-Jurisdiction entity) due to how DVT processes the FIRM Database, and due to how Regulatory Flood Risk Products are delivered to the MSC. For Countywide Flood Risk Projects, the Geography for the Purchase should include all communities within the County. For PMR studies, the Geography for the Purchase should only include those communities that are within the PMR footprint. If the incorrect type of Geography is chosen during Preliminary Purchase setup (i.e., a Single-Jurisdiction entity is set up as a County entity), this causes multiple errors and extraneous workarounds during DVT processing and during Preliminary Distribution.
• Purchase Contacts: Key contacts that should be listed for the Preliminary Purchase include, at a minimum, the study manager.
• Purchase Field Description: For revised prelims, please include description of why the revised prelim is issued, such as 'revised prelim due to appeals' or 'revised prelim due to new data received'
• Purchase Type Indicator: PMR or Revised Preliminary as applicable. For Revised Prelims, use the Revised Prelim indicator.
• Tasks Required to Support Purchase:
  • Validation
  • QR 3
  • KDP 3
• Task Name: Include County name and whether the Task is for producing Preliminary Map Data or for producing Revised Preliminary Map Data.
• Task Description: Specify if study is a full countywide, PMR, or Partial Countywide.
• Task Assignments:
  • KDP Three: FEMA Region or their designee
  • Produce Preliminary Maps Data Capture: Mapping Partner (funded to perform work)
  • Preliminary Validation: FEMA Region or their designee (MIP BB or Regional POC)
  • Preliminary Independent QA/QC: Mapping Partner (funded to review work)
  • Quality Review 3: PTS, typically the RSC or Quality Lead
  • Distribute Preliminary Products: Mapping Partner (funded to perform work)
• EV Information: Will be tracked at the Task Level for the Produce Preliminary Products Data Capture and QA/QC Tasks.

Produce Preliminary Map Data Task

Task Start: The Mapping Partner should start this Task only after completion of KDP 2 and completion of QR1. If a revised preliminary purchase is needed, the mapping partner may not need KDP2 approval, yet this should be verified prior to Task creation.

The Produce Preliminary Map Data Capture Task includes the following sections, as shown in the example below:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Preliminary Data and perform the automated Metadata and Database Validation
• Analysis Section allows the user to indicate Leveraged datasets and details (including KDP 2 Approval Date, Projected Preliminary Date, Total Number of Panels in Study, Number of Revised/Updated Panels and Leverage). Enter leverage for contributed work or funds in the production of the FIRM database that was not already reported in the Draft FIRM Database Capture Task. Do not count base map, elevation data, or other contributed spatial data sets here.
• Auto-Generate Tasks Section allows the user to choose to auto-generate the Validation, QR3, KDP 3, and Distribute Preliminary Products Tasks
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Produce Preliminary Data Validation and Preliminary Independent QA/QC

The only editable sections of this Task are the Submit Data, Analysis, add Leverage, Auto-Generate Tasks, and Comments sections. Steps include:

1. Select a Database Schema
   1. Prior to initiating data submission, confirm that the Purchase Geography is correct (County; Single-Jurisdiction).
   2. A user must select a Database Schema from the buttons (2003, 2011, or 2013).
   3. Refer to the Risk MAP ID Tables information on the FEMA Guidelines & Standards Maintenance web page for further details on Database schemas.
2. Upload Preliminary materials
   1. These materials include FIRM, FIS, FIRM Database, and metadata files. The upload of this data is the submission for QR2 and QR3.
   2. For reference to the data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, Data Capture - General and Data Capture - Workflow Details guidance documents.
   3. After selecting the file, a user must select the Upload File button to have the file saved to the Task
   4. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   5. After uploading the file, select Run Validation button to trigger metadata validation. If the metadata validation passes, the folder validation is started automatically. If the folder validation passes, DVT is triggered by the system. Please Note: Tasks that involve DVT Validation, the CID to validate selected during task creation should match the CID within the metadata file and the CID in the file naming convention
      1. The Submission Status will then be displayed for the FIS, FIRM, metadata, and FIRM Database files.
      2. The QR2 Completion Date will be displayed once all DVT errors are resolved.
   6. To view uploaded files in File Explorer, select the View in File Explorer link
   7. Select the View Details link for more information on the results of the auto validation. If the status displays Failed, the View Details link provides specific information on what part of the metadata failed the review. In some instances, there may be a need to bypass a failing DVT validation. Common bypass needs are described in the DVT Guidance in G&S. If you feel that the DVT validation has failed your submission when it should not have, please contact Risk MAP IT Help and provide your case number, validation URL, and reasoning
3. Upload a Pre and Post QR3 files
   1. Upload the Pre-QR3 File in preparation for initiating the QR3 Review.
   2. Upload the Post-QR3 File once QR3 is complete
   3. After selecting the file, a user must select the Upload File button to have the file saved to the Task
4. Add Study-specific information.
   1. Enter a total Number of Panels in the Flood Risk Project (required).
   2. Enter the Number of Revised/Updated Panels in the Flood Risk Project (required).
   3. The KDP 2 Date and Projected Preliminary Date will be populated based on information entered by the Purchase Level Access user.
5. Add Leverage to the Task
   1. Under the Leverage section, select the Add button
   2. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   3. Once those fields are completed the user must select the Save button

      

6. Auto-Generate Tasks: The user can choose to auto-generate the Preliminary Products Data Validation, QR3, KDP 3, and Distribute Preliminary Prodcuts Tasks when creating the Coastal Data Capture Task. To do so, the steps are:
   1. Check the "Auto-Generate Tasks" box
   2. Enter a descriptive suffix in the "Generated Task Suffix" field
   3. Enter the community to validate against (county FIPS) in the "Relevant Geography" field
7. Add Comments relevant to the Task.
8. A user can select the Save button at any point during this process.
9. This Task should be kept open by the user until QR3 is approved. Task updates can be saved as data is updated as part of the QR2/QR3 Review process.
10. Once all the mandatory fields are completed the user can select the Submit button
1. A user should not select Submit until QR3 has been approved.

Preliminary Map Production Validation Task

This is the view of the Validate Preliminary Map Production Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validation Status fields. Steps include:

1. Approve or Reject Validation (user must select one)
2. Upload a Validation document
   1. After selecting the file, a user must select the Upload File button in order to have the file saved to the Task.
3. The Validator can also enter any comments regarding the Validation Task
4. The user can select the Save button at any point during this process. Once all the mandatory fields are completed the user can select the Submit button

Preliminary Map Production Independent QA/QC Task

The Independent QA/QC Task is initiated when the Data Capture Task is completed, and the Validation Task is completed/approved. The Independent QA/QC checks the technical correctness of the mapping and submittal files for completeness and quality excellence. This Task may be completed by a Mapping Partner; the Independent QA/QC is conducted by either the same Mapping Partner who completed the Data Capture Task (but by a different and independent production group) or by an independent technical reviewer.

Below is the view of the Independent QA/QC Preliminary Map Production Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• QA/QC Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary QA/QC checklists as well as provide general comments related to this independent review

The only editable sections of this Task are the Independent QA/QC Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a QA/QC document
3. A reviewer can also enter any comments regarding the QA/QC Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Distribute Preliminary Products Task

Task Start: The Mapping Partner starts this Task only once QR3 is completed and KDP 3 is approved. The purpose of this Task is to distribute the Preliminary materials, which have now successfully passed QR3 and are approved for distribution via KDP 3. Completion of this Task will trigger an Actual Preliminary Date being reported in the MIP.

Below is the view of the Produce Preliminary Map Data Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Preliminary Data and perform the automated Metadata and Database Validation
• Analysis Section allows the user to enter an Actual Prelim Date and provides a list of Communities that are appealable as well as whether the Preliminary SOMA is complete.
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Produce Preliminary Data Validation and Preliminary Independent QA/QC

The only editable sections of this Task are the Submit Data, and Comments sections. Steps include:

1. Upload Delivery Receipts
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. To view uploaded files in File Explorer, select the View in File Explorer link
2. Review Appeal and SOMA information
   1. The Mapping Partner should review the table containing "Appeal Changes" (Yes/No) and "Preliminary SOMA" (Yes/No).
3. Add Comments relevant to the Task.
4. A user can select the Save button at any point during this process.
5. Once the Produce Preliminary Data Capture Task is submitted and the KDP 3 Task is complete, the Mapping Partner will enter the Actual Preliminary Date, and select Send to MSC.
   1. At this point, all subsequent workflow Tasks should be completed. The Mapping Partner should confirm this before completing the Distribute Preliminary Products Task.
   2. The Actual Preliminary Date should be the same date that is shown on the FIRMs. This will be reported as such once the Distribute Preliminary Products Task is completed.
6. Once all the mandatory fields are completed, the user can select the Submit button.

KDP 3 Task

Below is the view of the KDP 3 Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, and Purchase Geography(ies)
• Analysis Section allows user to enter if KDP is needed and the approval date as well as a reason if KDP is not needed
• Comments Section allows the user to enter any relevant comments

The only editable sections of this Task KDP 3 fields. Steps include:

1. A user must indicate where KDP 3 is needed or not
2. Next a user must enter the KDP 3 Approval Date
3. If a KDP 3 is not needed, then a user must provide a reason why
4. A reviewer can also enter any comments regarding the KDP 3 Task
5. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

QR3 Task

The QR3 Task is initiated once the initial QR2 submittal has been Validated. The Mapping Partner should coordinate with the Reviewer PTS by email to initiate the QR3 Review process. This Task facilitates the QR3 visual review of submitted Preliminary materials. The Reviewer PTS will review a 10% subset of the revised panels.

The QR3 Task includes the following sections, as shown in the example below:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Review Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary QR checklists as well as provide general comments related to this quality review.

The only editable sections of this Task are the Analysis and QA Status fields. Steps include:

1. The QR3 Reviewer must enter the Number of Panels Reviewed
2. The QR3 Reviewer must either select Approve or Reject and enter his/her name
1. If comments must be addressed, the Data Capture Task would be reopened, revised, and resubmitted. The Validation Task would then be reopened for Approval or Rejection.
3. Upload QR documents
   1. Materials uploaded include the FEMA-approved QR3 checklist, and any other supplemental comments such as screen shots or spatial files, if necessary.
   2. After selecting the file, a user must select the Upload File button in order to have the file saved to the Task.
4. The QR3 Reviewer may also enter any comments regarding the QA/QC Task. If the QR3 submission is rejected, briefly state here why the submission was rejected.
5. A user can select the Save button at any point during this process.
6. Once all the mandatory fields are completed the user can select the Submit button to submit the Independent QA/QC results.

Revised Preliminary

When a Flood Risk Project has been issued Preliminary and needs significant modification, it may be necessary to issue a revised set of Preliminary materials. The need for Revised Preliminary materials is determined by FEMA through coordination with the community. The Revised Preliminary process usually requires a contract modification in order to change the Flood Risk Project scope, Period of Performance, and funding. The Revised Preliminary Task requires a second Purchase under the Preliminary Purchase Level. Please reference the above section, 'Create Preliminary Purchase & Task's,' for more details.

If Revised Preliminary materials become necessary, a Purchase Level Access user should use the Revised Preliminary Purchase Type Indicator to create a second set of Purchases to collect data for the Revised Preliminary. The revised Preliminary Purchase will behave like a normal Purchase in that they will be assigned, completed, and validated in the same way.

Below is the Create Purchase screen where the Purchase Indicator drop option is accessible.

The options within the Purchase Type Indicator include

• Revised Prelim
• PMR
• Large Scale Automated Engineering
• Base Level Engineering

Once the Revised Prelim Purchase Type Indicator is chosen, users will see Revised Prelim inserted in the Purchase Title field across all associated screens.

Due Process Purchase

This purchase will allow a user to Populate FHD, Consolidate FHD, Appeal Start Docket Approval, Initiate Appeal/Comment, Record Appeal/Comment, and complete Validation for Record Appeal/Comment, QR 4 Part 1, QR 4 Part 2, and KDP 4. Please note: While the system does not require Tasks be created in a certain order, some Tasks are dependent on others. The Populate FHD Task within the Due Process Purchase Group should always be created and completed before QR 4 Part 1. While the Initiate Appeal/Comment Task should be created and completed before QR 4 Part 2 , Record Appeal/Comment Task or Validation Tasks. Below are all the Tasks within the Due Process Purchase in the suggested creation/completion order. Users have the option to auto-generate all other tasks when creating the Due Process Management Task by inputting a descriptive suffix and the geography. Auto-generated tasks will have the naming convention task type+suffix+County FIPS.

Tasks:

• KDP 4
• Due Process Management (option to auto-generate all other tasks in purchase)
• Populate FHD
• QR4 Part 1
• Initiate Appeal/Comment
• QR4 Part 2
• Consolidate FHD
• Affidavit Receipt Data Capture
• Appeal Start Docket Approval
• Record Appeal/Comment
• Validation for Record Appeal/Comment
• Due Process Management

Data Upload:

• For reference to the data requirements for upload as well as the required folder structure please reference the FEMA Data Capture Technical Reference, Post Preliminary Deliverables, and related guidance documents

Validation:

• All Project data uploaded to the MIP needs to be reviewed and validated for completeness against the current Data Capture standards by a MIP super-user, typically a MIP Black Belt.

Create Due Process Purchase & Tasks

While in the purchase creation process, a Project Level Access user would locate the Due Process purchase by selecting Purchase Group: Post Preliminary Processing. Once that option is selected the Purchase dropdown will auto-populate and the option for the Due Process purchase will be made available. During the purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list.

Once a Project Level Access user has created the purchase, the user would then be able to create the relevant Tasks associated with the specific Purchase as listed in the Purchases and Tasks Overview section of this document

FEMA Official MIP Studies Guidance Highlights:

• Purchase Creation Consideration: Populate FHD and Consolidate FHD (2x, one for Proposed Notice and one for Final Notice) should be created at the time the Due Process Purchase is set up
• EV Information: Will be tracked at the Task Level for Due Process Management Task.
• Purchase Geography Consideration: Due process geography is specific to only those communities which are part of the 90-day appeal period.

Initiate Appeal/Comment Task

Below is the view of the Initiate Appeal/Comment Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Discovery Data and perform the automated Metadata Validation
• Analysis Section allows the user to indicate details specific to the Task and Leverage information (including Initiate Appeal/Comment, and Leverage)
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the QR4 Part 1 Task

The only editable sections of this Task are the Submit Data, Initiate Appeal/Comment, and Leverage and Comments sections. Steps include:

1. Upload a file(s) required for the QR4 Part 2 review. See Data Capture Technical Reference for file requirements.
   1. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   2. To view uploaded files in File Explorer, select the View in File Explorer link
2. A user must enter the Federal Register Publish Date
3. A user must enter the Federal Register Docket Number (Four-digit docket number found on the published Proposed Notice, e.g. 1704)
4. A user must enter dates for the first newspaper publication date, target mail date, second newspaper publication date, and appeal end date for each community displayed within that Task. The target mailed date, first newspaper publication date, and second newspaper publication date are each typically scheduled seven days apart, see example below.
   1. Target mail date = date the appeal start letters mail date (e.g. 05/01/2017)
   2. First newspaper publication date = date that the first newspaper notice is published in a community’s local newspaper (e.g. 05/08/2017)
   3. Second newspaper publication date = the appeal start date (e.g. 05/14/2017)
   4. Appeal end date = the end date of the 90-day appeal period which is the appeal start date plus 89 days (e.g. 05/14/2017 + 89 days = 08/11/2017)
5. A user can add Leveraged datasets to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

6. A user can select on the Save button at any point during this process or once all the mandatory fields are completed the user can click on the Submit button.

Record Appeal/Comment Task

Below is the view of the Record Appeal/Comment Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Discovery Data and perform the automated Metadata Validation
• Analysis Section allows the user to indicate details specific to the Task and Leverage information
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Validation for Record Appeal/Comment Task

The only editable sections of this Task are the Record Appeal/Comment and Comments sections. Steps include:

1. A user must add an Appeal/Comment or select the option to indicate there was No Appeal/Comment Received
2. A user can add an Appeal or Comment by selecting the Add button under the Record Appeal/Comment section
   1. The user will then be required to enter Community, Appeal Status, Date Received, and Changes to Product. A user can also choose to complete the other fields listed
   2. Type: Select if the document received classifies as an appeal or a comment. Users should refer to FEMA's Appeal and Comment Processing guidance document for support in determining this classification.
   3. Appeal Status Options Clarification:
      • To be Reviewed – Appeal/Comment package has been received but not yet acknowledged through a letter or response to the community and initial review has not been initiated.
      • Acknowledged – An initial acknowledgement letter or response after receiving an appeal or comment has been sent to the community. Refer to the Appeal and Processing Guidance Document.
      • Under Review – Initial review of Appeal/Comment package has been initiated but initial review is not yet complete.
      • Resolved – Appeal review and follow up actions have all been completed and Appeal/Comment is considered completely addressed. No additional actions required.
      • In Progress – Appeal/comment package initial review completed but requires follow up action, such as request for additional data, incorporation of data or perhaps a revised preliminary issuance.
   4. Date Received: This is the date the letter, email, fax, or other correspondence was received by FEMA
   5. Acknowledgement Date: This is the date FEMA sent an acknowledgement back to the submitter
   6. Resolution Date: This is the date FEMA sent a resolution back to the submitter
   7. Changes to product: Users should note "yes" only if changes in the product were related to comments and/or appeals
   8. Comments: Use this section to clarify what the changes to products are and what the basis for appeal is; for example, if other is checked, more detail should be provided here
   9. Once those fields are complete, the user must select the Save button

      

3. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can click on the Submit button.

Populate FHD

Below is the view of the Populate FHD Task. This task is assigned to the Mapping Partner responsible for determining which communities are receiving an appeal period and should therefore be on the Federal Register Proposed Notice. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Preliminary Data and perform the automated Metadata and Database Validation
• Analysis Section allows the user to indicate Analysis details such as Project Information, CEO Information, and Map Repository Information and Leveraged datasets
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Produce Preliminary Data Validation and Preliminary Independent QA/QC

Geography:

• Prior to completing this task, the Mapping Partner responsible must ensure all the communities listed in the Geography section are correct (i.e., those communities are to receive an appeal period/appear on the Proposed Notice of Flood Hazard Determinations). Any changes to Geography should be submitted as a Risk MAP IT Help Ticket noting which CIDs should be added or removed.

CIS Data:

• Please note: Community Information and CEO Information from CIS is pre-populated into the Populate FHD Task and users manually adjust entries in accordance with Federal Register Guidelines and add Map Repository information. Please note that changes made in Populate FHD Task are not pushed to CIS. It is recommended any changes necessary to the CEO Information be made 24 hours prior to completing the Populate FHD Task. Otherwise changes will need to be made in both CIS and the Populate FHD task.

Common updates to CEO information include and are not limited to: changing the name of the community from ALL CAPS to Case Lower Case (i.e., “MARION COUNTY Unincorporated Areas” to “Unincorporated Areas of Marion County”), adding “The Honorable” before the CEO’s name, correcting the CEO’s title (ie. Mayor, City of [Community Name], adding or deleting phone numbers, changing numbers that are currently spelled out to a numeric (ie. Second to 2nd), making sure the correct address where the community can send comments is populated (ie. P.O. Box or physical street address – do not include both a P.O. Box and street address, use one or the other), making sure the Map Repository Information entered into the Populate FHD Task matches the Map Repository Information on the Index/FIS. Please contact your Regional MIP Point of Contact if changes to the Index/FIS and L_COMM_INFO are needed.

General Guidelines

The only editable sections of this Task are the Analysis, Leverage and Comments sections. Steps include:

1. A user must populate the Project Information, CEO Information, and Map Repository Information fields
1. A user must populate all fields which have a red asterisk (*)
2. A user can add Leveraged datasets to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

3. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can click on the Submit button.

Consolidate FHD

The Consolidate FHD Task is not a true Task, but rather the functionality to combine multiple FHD notices. When a Project Access Level user creates and assigns a Consolidate FHD Task for a Project, it will appear on the assigned user's Task Workbench just like any other Task. This task will be assigned to PTS Provider in order to process the Proposed and Final Notice of Flood Hazard Determinations all of which are published in the Federal Register. This task pulls information for the Community Map Repository directly from the "Populate FHD" task so it is important to ensure the information entered for the Community Name and Community Map Repository meet Federal Register guidelines. The Community Map Repository is reviewed for adherence to Federal Register guidelines in the "Quality Review 4, Part 1" task.

To process the Proposed or Final Notice, the PTS Provider will select the "Consolidate FHD" MIP task or tasks they will be preparing. The PTS provider will select all the “Consolidated FHD” MIP tasks that will appear together on a Proposed Notice Docket, or that are on the same Letter of Final Determination (LFD) date. Once all "Consolidate FHD" MIP tasks are selected, the PTS Provider will select the "Consolidate FHD Export" button, not the "Work on Task" button.

The “Consolidate FHD Export” button will open a smaller window where the PTS Provider will enter the File Name, Docket Number, and select the Type of Notice to create (i.e. Proposed, Final, Correction, and Withdrawal). Currently, only the Proposed and Final Notice buttons are being utilized.

The “File Name” will be dependent on the type of notice being created. Please note: for “File Name” the MIP only accepts alphanumeric characters (i.e. dashes and underscores cannot be used). For a Part 67 Proposed Notice the file naming convention is “P67BXXXX,” where “XXXX” is the next available internal docket identification number to be used. For a Part 67 Final Notice the file naming convention is “P67NDDMMYYYY,” where “DDMMYYYY” is the Letter of Final Determination date.

The “Docket Number” for the Proposed Notice is the four digit numeric internal docket identification number the PTS Provider uses. For the Final Notice “Docket Number” is the Docket Number that was used on the Proposed Notice. Please note: If the PTS Provider is consolidating notices for multiple counties that were on different Proposed Notice dockets, the Docket No. in the exported Word document will need to be manually updated for each county on the consolidated notice as the PTS Provider can only enter one (1) docket number at this stage.

For “Type of Notice” the PTS Provider will select the “Proposed” button if they are preparing a Proposed Notice and will select the “Final” button if they are preparing a Final Notice.

Once the “File Name,” Docket Number,” and “Type of Notice” is entered the PTS Provider will export the notice using the “Export” button. A word document of the Proposed or Final Notice will be exported to the MIP K:/drive Due Process/Consolidate FHD folder. For a Final Notice the PTS Provider will have to manually change the “Docket No.” in the Word document if the counties being consolidated were on different Proposed Notices.

Affidavit Receipt Data Capture

This is the view of the Affidavit Receipt Data Capture Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Affidavit Receipt and perform the automated Metadata and Database Validation
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Produce Preliminary Data Validation and Preliminary Independent QA/QC

The only editable sections of this Task are the Submit Data and Comments fields. Steps include:

1. Users Can Upload Files
1. After selecting the file to upload, a user must select the Upload File button to have the file saved to the Task
2. After submitting the file, a user must select either the Direct Upload button, which uploads the file directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time
3. After uploading the file, select Run Validation button to trigger metadata validation
4. To view uploaded files in File Explorer, select the View in File Explorer link
5. Select the View Details link for more information on the results of the auto validation. If the status displays Failed, the View Details link provides specific information on what part of the metadata failed the review
2. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Appeal Start Docket Approval

This is the view of the Appeal Start Docket Approval Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Preliminary Data and perform the automated Metadata and Database Validation
• Analysis Section allows the user to indicate Leveraged datasets and details
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Produce Preliminary Data Validation and Preliminary Independent QA/QC

The only editable sections of this Task are the Appeal Initiation Information and QA Status fields. Please note this task will be completed by FEMA HQ. Steps include:

1. A user must enter the HQ approval Date
2. A user must select Approve or Reject QA
3. Next a user can upload a QA file
4. A reviewer can also enter any comments regarding the Appeal Start Docket Approval Task
5. A user prior to completing the task should click Publish Notice. This function will publish the approved FHD notice to the FEMA’s Flood Hazard Determination Notices webpage.
6. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

Validation for Record Appeal/Comment

This is the view of the Validate Record Appeal/Comment Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validate Record Appeal/Comment and Validation Status fields. Steps include:

1. If no Appeals/Comments have been recorded A user must indicate No Comments/Appeals have been received by clicking the check box within the Validate Record Appel/Comment section
2. A user must select Approve or Reject Validation
3. Next a user can upload a Validation file
4. A reviewer can also enter any comments regarding the Appeal Start Docket Approval Task
5. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

QR4 Part 1

This is the view of the Quality Review 4 Part 1 Task (QR4 Pt1). This task is assigned to the PTS Provider responsible for performing the QR4 Part 1 Quality Review. In order for the CEO and CMR information to be available to Quality Reviewers for Quality Review 4 Part 2, this task should be saved, not submitted when the QR4 P1 review is completed. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The QR4 Part 1 Reviewer uses this screen to verify that the information inputted in the “Populate FHD” task is correct and adheres to FEMA’s Federal Register Guidelines, such as community names are Case Lower Case, CEO Names have “The Honorable” added, CEO tiles are correct (ie. Mayor, City of), that Map Repository Information is correct and matches the Index/FIS Report. . The QR4 Part 1 Reviewer will verify that the Purchase Geography is correct and the communities listed in the Purchase Geography match the communities that should be receiving an appeal and be placed on the Federal Register notice. The QR4 Part 1 Reviewer will also make sure KDP 4 has been approved. The QR4 Part 1 Reviewer checks to make sure all comments are entered into the QR4 Part 1 Regulatory checklist which is uploaded to the MIP.

The QR4 Part 1 checklist is uploaded to the MIP in the “Review Status” section of this task, through the “Upload Review File” button. Please note: the checklist must be in .xlsx or .xls format and the file name cannot contain dashes (-).

If the QR4 Part 1 Reviewer identifies changes are required, the review first uploads the QR4 Part 1 checklist and then “Reject” button is selected. If necessary the QR4 Part 1 Reviewer may add additional comments before selecting the “Submit” button. By rejecting this task, the “Populate FHD” task is re-opened for corrections.

Upon completion of the QR4 Part 1 review, after the checklist has been uploaded, the QR4 Part 1 Reviewer will save the MIP task. This will leave the task available during QR4 Part 2 so the review can check that CEO names, addresses, etc have not changed from the time Populate FHD was completed and the Appeal Start Materials prepared. If changes are warranted, QR4 P1 can be rejected, opening Populate FHD to make changes to CEO information. NOTE: Once the Proposed Notice has published in the Federal Register changes must not be made to the CMR information in Populate FHD.

The only editable sections of this Task are the QA Status fields. Please note this task will be completed by FEMA HQ. Steps include:

1. A user must select Approve or Reject QA
2. Next a user can upload a QA file.
3. A reviewer can also enter any comments regarding the Quality Review 4 Part 1 Task (QR4 Pt1) Task.
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

QR4 Part 2

This is the view of the Quality Review 4 Part 2 Task (QR4 Pt2). This task is assigned to the PTS Provider responsible for performing the QR4 Part 2 Quality Review. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The QR4 Part 2 Reviewer uses this screen to verify that the information inputted in the “Initiate Appeal/Comment” task is correct. The QR4 Part 2 Reviewer will verify that the Purchase Geography is correct and the communities listed in the Purchase Geography match the communities that should be receiving an appeal and were published on the Federal Register notice. The QR4 Part 2 Reviewer downloads the Appeal Start Letters and Newspaper Notice from the MIP K drive which was uploaded by the Study Team during the “Initiate Appeal/Comment” MIP task. The QR4 Part 2 Reviewer confirms the Target Mail Date, 1st and 2nd Newspaper Publication Dates and Appeal End Date are correct and match the documents submitted. All comments are entered into the QR4 Part 2 Regulatory checklist which is uploaded to the MIP.

The QR4 Part 2 Reviewer also uses the QR4 P1 task to verify the CEO information (name, address) in the Appeal Start Letters matches what was entered into Populate FHD. Should CEO information need to be updated the QR4 Part 2 Reviewer will reject QR4 P1. This will open Populate FHD for the Mapping Partner to make the applicable changes to CEO information. NOTE: Once the Proposed Notice has published in the Federal Register changes must not be made to the CMR information in Populate FHD.

The QR4 Part 2 checklist is uploaded to the MIP in the “Review Status” section of this task, through the “Upload Review File” button. Please note: the checklist must be in .xlsx or .xls format and the file name cannot contain dashes (-). The QR4 Part 2 Reviewer may also upload additional files with comments on the Appeal Start Materials (letters and newspaper notice). This is done through the “Review Status” section of this task, through the “Upload Review File” button.

If the QR 4 Part 2 Reviewer identifies changes are required, the review first uploads the QR4 Part 2 checklist and then “Reject” button is selected. If necessary the QR4 Part 2 Reviewer may add additional comments before selecting the “Submit” button. By rejecting this task, the “initiate Appeal/Comment” MIP task is re-opened for corrections and the Mapping Partner can access the QR4 Part 2 checklist and any other files from the MIP K drive.

The only editable sections of this Task are the QA Status fields. Steps include:

1. A user must select Approve or Reject QA
2. Next a user can upload a QA file
3. A reviewer can also enter any comments regarding the Quality Review 4 Part 2 Task (QR4 Pt2) Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

KDP 4 Task

Below is the view of the KDP 4 Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, and Purchase Geography(ies)
• Analysis Section allows user to enter if KDP is needed and the approval date as well as a reason if KDP is not needed
• Comments Section allows the user to enter any relevant comments

The only editable sections of this task are the KDP 4 fields. Steps include:

1. A user must indicate where KDP 4 is needed or not
2. Next a user must enter the KDP 4 Approval Date
3. If a KDP 4 is not needed, then a user must provide a reason why
4. A reviewer can also enter any comments regarding the KDP 4 Task
5. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

Due Process Management Task

The Due Process Management Task is not a true Task, but rather the functionality to track Earned Value (EV) for the Due Process Purchase. When a Project Access Level user creates and assigns a Due Process Management Task for a Project, it will solely appear on the Track Task Workbench for that user. The Due Process Management Task will have the same functionality as other Tasks on the Track Progress Workbench. For more information on the Track Progress Workbench please refer to the Track Progress Section of this User Care. Please note, since this Task only appears on Track Progress Workbench only Project and Task + EV users will have access to it, thus assignments should only be made to those access level users. When creating the Due Process Management Task, the user has the option to auto-generate all other tasks for the Due Process Purchase by inputting a descriptive suffix and the relevant geography, and checking the "Auto-Generate Tasks" box.

Final Map Production and Distribution Purchase

This purchase will allow a user to Develop Final Mapping Products, Validate Final Mapping Products, LFD Docket, Finalize LFD, LFD Approval, QR 5, QR 6, QR 7, Suspension Notifications Letters, Prepare Revalidation, Review Revalidation, Revalidation Approval, Distribute Revalidation and KDP 5. Please note: While the system does not require Tasks be created in a certain order, some Tasks are dependent on others. The Develop Final Mapping Products Data Capture Task within the Final Mapping Production and Distribution Purchase Group should always be created and completed before Develop Final Mapping Validation, QR 5, 7, and 8. While the LFD Docket Task should be created and completed before QR 6 , LFD Approval, Finalize LFD and Suspension Notification. The Prepare Revalidation Task should be created and completed before, Review Revalidation, Revalidation Approval, and Distribute. Below are all the Tasks within the Final Mapping Production Purchase in the suggested creation/completion order.

Tasks

• KDP 5
• Develop Final Mapping Product
• Validate Final Mapping Products
• QR 5
• QR 7
• QR 8
• LFD Docket
• QR 6
• LFD Approval
• Finalize LFD
• Suspension Notifications Letters
• Prepare Revalidation
• Review Revalidation
• Revalidation Approval
• Distribute Revalidation
• KDP 5
• Final Mapping Products Management (with option to auto-generate all other tasks in purchase)

Validation:

• All Project data uploaded to the MIP through a Project workflow needs to be reviewed and validated for completeness against the current Data Capture standards by a MIP super-user, typically a MIP Black Belt.

Create Final Map Production and Distribution Purchase and Tasks

While in the purchase creation process, a Project Level Access user would locate the Due Process purchase by selecting Purchase Group: Post Preliminary Processing. Once that option is selected the Purchase dropdown will auto-populate and the option for the Final Map Production and Distribution will be made available. During the purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list.

Once a Project Level Access user has created the purchase, the user would then be able to create the relevant Tasks associated with the specific Purchase as listed in the Purchases and Tasks Overview section of this document

FEMA Official MIP Studies Guidance Highlights:

• EV Information: Will be tracked at the Task Level for Final Mapping Products Management Task.

Develop Final Mapping Products Data Capture

Below is the view of the Develop Final Mapping Products Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Submit Data Section allows the user to upload Preliminary Data and perform the automated Metadata and Database Validation.
• Analysis Section allows the user to indicate Leveraged datasets and details
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the Produce Preliminary Data Validation and Preliminary Independent QA/QC

The only editable sections of this Task are the Submit Data, Analysis, Leverage and Comments sections. Steps include:

1. A user must select a Database Schema
2. A user must select a Data Location from the drop-down menu
   1. Pre-populated options are listed, and a user can select:
      • MIP - Select this option if data is being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer
      • Risk MAP IT Help - Select this option if data is not being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer. Instead this data must be physically sent to CDS for uploading, please see MIP Guidance document for further details on this process.
3. Next a user can upload data file
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. After uploading the file, select Run Validation button to trigger metadata validation. If the metadata validation passes, DVT is automatically started right after metadata validation. Please Note: Tasks that involve DVT Validation, the CID to validate selected during task creation should match the CID within the metadata file and the CID in the file naming convention
   4. To view uploaded files in File Explorer, select the View in File Explorer link
   5. Select the View Details link for more information on the results of the auto validation. If the status displays Failed, the View Details link provides specific information on what part of the metadata failed the review. In some instances, there may be a need to bypass a failing DVT validation. Common bypass needs are described in the DVT Guidance in G&S. If you feel that the DVT validation has failed your submission when it should not have, please contact Risk MAP IT Help and provide your case number, validation URL, and reasoning
4. A user must enter the Number of Printed Panels
5. A user can add Leveraged datasets to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

6. A user can select on the Save button at any point during this process or once all the mandatory fields are completed the user can click on the Submit button.

Validation of Final Mapping Products

This is the view of the Validate Final Mapping Products Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Validation Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a Validation file
3. A reviewer can also enter any comments regarding the validation Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

Prepare Revalidation

Below is the view of the Prepare Revalidation Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Analysis Section allows the user to view the completed analysis of the prior related Tasks (including: Affected Communities)

The only editable sections of this Task are the Submit Data and Approval Status fields. Steps include:

1. A user can upload Final Revalidation Data file
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
2. A user can also enter any comments regarding the approval Task
3. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

No LOMCs to Be Revalidated:

• When all the LOMCs for a project are classified as Category 1, 2B, 3 or 4, or when there are no LOMCs in the SOMA tool for the community(ies) in the Project, a Revalidation letter is not required. If either of these conditions are met, the Mapping Partner should prepare a README text file for upload that reads “All LOMCs for all communities in this project are classified as Category 1, 2B, 3 or 4; therefore, a revalidation letter is not required.” Or “There are no LOMCs in the SOMA tool for the communities within this project; therefore, a revalidation is not required.” The README text file is then uploaded through the Upload File button and the user can select the Submit button. NOTE: The Mapping Partner must still alert the PTS Provider the task has been completed as the PTS Provider must confirm, through the Review Revalidation Task, this condition to be true.

Review Revalidation

Below is the view of the Review Revalidation Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Analysis Section allows the user to view the completed analysis of the prior related Tasks (including: submitted revalidation files and revalidation docket)

The only editable sections of this Task are the Submit Data and Approval Status fields. Steps include:

1. A user must select Approve or Reject Validation
2. Next a user can upload a Validation file
3. A reviewer can also enter any comments regarding the validation Task
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

No LOMCs to Be Revalidated:

• When all the LOMCs for a project are classified as Category 1, 2B, 3 or 4, or when there are no LOMCs in the SOMA tool for the community(ies) in the Project, a Revalidation letter is not required. If either of these conditions are met, the Mapping Partner should prepare a README text file for upload that reads “All LOMCs for all communities in this project are classified as Category 1, 2B, 3 or 4; therefore, a revalidation letter is not required.” Or “There are no LOMCs in the SOMA tool for the communities within this project; therefore, a revalidation is not required.” NOTE: The PTS Provider must confirm, through the Review Revalidation Task, this condition to be true. The PTS Provider will confirm this condition to be true and upload a README file noting they have verified that revalidation is not required.

Revalidation Approval

Below is the view of the Revalidation Approval Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Analysis Section allows the user to view the completed analysis of the prior related Tasks (including: submitted revalidation files and revalidation docket)

The only editable sections of this Task are the Analysis and Approval Status fields. Steps include:

1. A user must enter the HQ Approval Date/li>
2. A user must select Approve or Reject Validation
3. Next a user can upload a Validation file
4. A reviewer can also enter any comments regarding the validation Task
5. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

No LOMCs to Be Revalidated:

• When PTS Provider confirms, through the Review Revalidation Task, revalidations are not required, the Approve Revalidation Task is not required. Mapping Partners should reach out to their FEMA Regional MIP representative and request this task be removed from the Purchase.

Distribute Revalidation

Below is the view of the Distribute Revalidation Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Analysis Section allows the user to view the completed analysis of the prior related Tasks (including: Distribute Revalidation Letter Date, Date Letter Sent to Communities, HQ Approval Date, and Affected Communities)

The only editable sections of this Task are the Submit Data and Analysis Status fields. Steps include:

1. A user can upload Final Stamped Revalidation file
   1. After selecting the file, a user must select the Update File button to have the file saved to the Task
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. To view uploaded files in File Explorer, select the View in File Explorer link
2. A user must enter the Letter Sent to Communities' Date
3. A user must enter the HQ Approval Date
4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

No LOMCs to Be Revalidated:

• When PTS Provider confirms, through the Review Revalidation Task, revalidations are not required, the Distribute Revalidation Task is not required. Mapping Partners should reach out to their FEMA Regional MIP representative and request this task be removed from the Purchase.

LFD Approval

Below is the view of the LFD Approval Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Analysis Section allows the user to view the completed analysis of the prior related Tasks (including: KDP 5, QR 5, QR 6, QR 7 Approval Dates)
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the Approval Status fields. Steps include:

1. A user must enter an Actual LFD Date
2. A user must must enter the HQ Approval Date
3. A user must must Approve or Reject the validation
4. Next a user can upload a Validation file
5. A reviewer can also enter any comments regarding the approval Task
6. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

LFD Docket

Below is the view of the LFD Docket Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Analysis Section allows the user to indicate details specific to the Task and Leverage information (including LFD Date, Effective Date, and Leverage)
• Comments Section allows the user to enter any relevant comments. These comments will be visible within the QR4 Part 1 Task

The only editable sections of this Task are Analysis, Leverage, and Comments sections. Steps include:

1. A user can upload the LFD Docket
   1. After selecting the file, a user must select the Update File button to have the file saved to the Task
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. To view uploaded files in File Explorer, select the View in File Explorer link
2. A user must indicate which Affected Communities have a Suspension Notification
   1. If a community does not have a Suspension Notification, the user is required to add a FEMA Approval Date
3. A user must indicate the New 60.3 Code for each Affected Community
4. A user can add Leveraged datasets to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

5. A user can select the Save button at any point during this process. Once all the mandatory fields are completed the user can click on the Submit button.

Finalize LFD

Below is the view of the Finalize LFD Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment History
• Analysis Section allows the user to indicate details specific to the Task and Leverage information
• Comments Section allows the user to enter any relevant comments.

The only editable sections of this Task are the Leverage and Comments sections. Steps include:

1. A user can upload a Data File
   1. After selecting the file, a user must select the Update File button to have the file saved to the Task
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. To view uploaded files in File Explorer, select the View in File Explorer link
2. A user can view the table of Affected Communities
3. A user can add Leveraged datasets to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

4. A user can select on the Save button at any point during this process or once all the mandatory fields are completed the user can click on the Submit button.

KDP 5

Below is the view of the KDP 5 Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, and Purchase Geography(ies)
• Analysis Section allows user to enter if KDP is needed and the approval date as well as a reason if KDP is not needed
• Comments Section allows the user to enter any relevant comments

The only editable sections of this task are the KDP 5 fields. Steps include:

1. A user must indicate where KDP 5 is needed or not
2. Next a user must enter the KDP 5 Approval Date
3. If a KDP 5 is not needed, then a user must provide a reason why
4. A reviewer can also enter any comments regarding the KDP 5 Task
5. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

Suspension Notification Letters

Below is the view of the Suspension Letters Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Analysis Section allows the user to view the completed analysis of the prior related Tasks (including: FEMA HQ Docket Approval 90 Date, FEMA HQ Docket Approval 30 Date, and Affected Communities)

The only editable sections of this Task are the Submit Data and Analysis Status fields. Steps include:

1. A user can upload Suspension file
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. To view uploaded files in File Explorer, select the View in File Explorer link
2. A user can make edits to the Affected Communities table which is pre-populated from the LFD Docket Task
3. A user must enter the FEMA HQ Docket Approval 30 Date
4. A user must enter the FEMA HQ Docket Approval 90 Date
5. A user can add Leverage to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

6. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

QR 5

This is the view of the Quality Review 5(QR5). From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the QA Status fields. Steps include:

1. A user must select Approve or Reject QA
2. A user must enter the Reviewer Name
3. Next a user can upload a Review file
4. A reviewer can also enter any comments regarding the Quality Review 5 Task
5. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

QR 6

This is the view of the Quality Review 6(QR6). From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the QA Status fields. Steps include:

1. A user must select Approve or Reject QA
2. A user must enter the Reviewer Name
3. Next a user can upload a Review file
4. A reviewer can also enter any comments regarding the Quality Review 5 Task
5. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

QR 7

This is the view of the Quality Review 7(QR7). From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the QA Status fields. Steps include:

1. A user must select Approve or Reject QA
2. A user must enter the Reviewer Name
3. Next a user can upload a Review file
4. A reviewer can also enter any comments regarding the Quality Review 7 Task
5. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

QR 8

This is the view of the Quality Review 8(QR8). From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Validation Status allows the user to either reject or approve the Task, enter the reviewer name and upload the necessary validation checklists as well as provide general comments related to this validation

The only editable sections of this Task are the QA Status fields. Steps include:

1. A user must select Approve or Reject QA
2. A user must enter the Reviewer Name
3. Next a user can upload a Review file
4. A reviewer can also enter any comments regarding the Quality Review 7 Task
5. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

Flood Elevation Determination Docket (FEDD)

Below is the view of the FEDD Data File Capture. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Analysis Section allows the user to view the completed analysis of the prior related Tasks (including: FEMA HQ Docket Approval 90 Date, FEMA HQ Docket Approval 30 Date, and Affected Communities)

The only editable sections of this Task are the Submit Data and Analysis Status fields. Steps include:

1. A user must select a Data Location from the drop-down menu
1. Pre-populated options are listed, and a user can select:
   • MIP - Select this option if data is being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer
   • Risk MAP IT Help - Select this option if data is not being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer. Instead this data must be physically sent to CDS for uploading, please see MIP Guidance document for further details on this process.
2. A user can upload FEDD data file
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. After uploading the file, select Run Validation button to trigger metadata validation
   4. To view uploaded files in File Explorer, select the View in File Explorer link
   5. Select the View Details link for more information on the results of the auto validation. If the status displays Failed, the View Details link provides specific information on what part of the metadata failed the review.
3. A user can add Leverage to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

Technical Support Data Note Book (TSDN)

Below is the view of the TSDN Data File Capture. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Analysis Section allows the user to view the completed analysis of the prior related Tasks (including: FEMA HQ Docket Approval 90 Date, FEMA HQ Docket Approval 30 Date, and Affected Communities)

The only editable sections of this Task are the Submit Data and Analysis Status fields. Steps include:

1. A user must select a Data Location from the drop-down menu
1. Pre-populated options are listed, and a user can select:
   • MIP - Select this option if data is being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer
   • Risk MAP IT Help - Select this option if data is not being uploaded directly to the MIP using the MIP Task or placed directly to the submission folder on File Explorer. Instead this data must be physically sent to CDS for uploading, please see MIP Guidance document for further details on this process.
2. A user can upload TSDN data file
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. After uploading the file, select Run Validation button to trigger metadata validation
   4. To view uploaded files in File Explorer, select the View in File Explorer link
   5. Select the View Details link for more information on the results of the auto validation. If the status displays Failed, the View Details link provides specific information on what part of the metadata failed the review.
3. A user can add Leverage to the Task by selecting the Add button under the Leverage section
   1. The user will then be required to enter Quantity, Type, Unit, Contributed By, Federal Fiscal Year, and Comments.
   2. Once those fields are completed the user must select the Save button

      

4. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button.

Final Mapping Management Task

The Final Mapping Management Task is not a true Task, but rather the functionality to track Earned Value (EV) for the Final Map Production and Distribution Purchase. When a Project Access Level user creates and assigns a Final Mapping Management Task for a Project, it will solely appear on the Track Task Workbench for that user. The Final Mapping Management Task will have the same functionality as other Tasks on the Track Progress Workbench. For more information on the Track Progress Workbench please refer to the Track Progress Section of this User Care. Please note, since this Task only appears on Track Progress Workbench only Project and Task + EV users will have access to it, thus assignments should only be made to those access level users. When creating the Final Mapping Management Task, the user has the option to auto-generate all other tasks for the Final Mapping Purchase by inputting a descriptive suffix and the relevant geography, and checking the "Auto-Generate Tasks" box.
In addition, users will be able to add and update the Projected LFD Date through this task.

Outreach Purchase

This Purchase will allow a user to capture CCO Meeting Data, Feedback, and Event Information.

Purpose: This purchase will allow a user to capture Outreach efforts for a Risk MAP Project. It is important to note that when these efforts occur outside of the Risk MAP process, a new Project should be created to track this effort. This new Project should include the associated geography and may only include an Outreach Purchase (for instance, if a High-Water Mark event is supported by FEMA in a community outside of any ongoing Risk MAP Project). See the Project Creation section of the MIP User Care for more information on how to create a Project.

Tasks:

• Consultation Coordination Office (CCO) Meeting Data Capture
• Feedback Data Capture
• Event Data Capture

While in the purchase creation process, a Project Level Access user would locate the Outreach purchase by selecting Purchase Group: Outreach. Once that option is selected the Purchase dropdown will auto-populate and the option for the Outreach Purchase will be made available. During the Purchase creation, the Project Level Access user will also be able to select a Purchase Type Indicator from the auto-populated list.

Once a Project Level Access user has created the Purchase, the user would then be able to create the relevant Tasks associated with the specific Purchase as listed in the Purchases and Tasks Overview section of this document

FEMA Official MIP Studies Guidance Highlights:

• Purchase Geography:
  • CCO Meeting Data Capture Task: Should align with the Post-Preliminary Processing geography and be captured at the County and community level. In the case of more than one CCO Meeting (for a large county or watershed, for example), the geography for each CCO Meeting should include only those communities that are invited to each meeting. This can be done with multiple meetings under the task.
  • Feedback Data Capture Task: Should align with the overall Project geography (e.g., watershed or county) OR with specific communities that submit comments or data in support of a Risk MAP Project (except during the appeals period). When this task is being used for SID 620 and 621 it should align with communities in which SID 620 and 621 have occurred.
  • Event Data Capture Task: Should align with the geography specific to the meeting, event, or outreach effort.
• Purchase Contacts: CERC, PTS, CTP as appropriate
• Purchase Field Description:
  • CCO Meeting Data Capture Task: This should include information about the CCO Meeting that may be important to see in the Task Workbench.
  • Feedback Data Capture Task: This should include information that is helpful in describing the activity purchased, including phase of the Risk MAP Project if appropriate.
  • Event Data Capture Task: This should include information about the event that may be important to see in the Task Workbench.
• Task Name:
  • CCO Meeting Data Capture Task:
    • CCO Meeting_Meeting Geography Name (if more than one CCO Meeting is held, the Geography Name may be Western County Name or other appropriate distinguishing name.)
  • Feedback Data Capture Task:
    • Feedback_Geography
    • This may be used as a placeholder to receive generic feedback but it is highly recommended that the task name be more specific as shown below
    • Feedback_SID###_Geography Name (when the feedback is directly related to a SID)
    • Feedback_Feedback Type_Geography
      • Feedback type could indicate what it is directly about, such as Hydrology, and the geography could refer to community or water source, etc.
  • Event Data Capture Task:
    • Meeting/Event Name_Meeting Geography Name
    • SID622###_Geography Name
    • Outreach Effort_Geography Name
• Task Description:
  • CCO Meeting Data Capture Task: Any additional information that could be helpful in distinguishing this Task from others in the Task Workbench.
  • If multiple CCO meetings occur for a geography in order to accommodate communities it should be described here. Additionally, if the task is specific to a certain provider that information should be captured here if it has not been included in the Task Name. This is helpful when multiple providers may be scoped to work on a task. For example, if a PTS Provider and CERC Provider are both working on a CCO Meeting, the two tasks should be differentiated as CERC and PTS here.
  • Feedback Data Capture Task: Any additional information that could be helpful in distinguishing this Task from others in the Task Workbench.
  • Event Data Capture Task: Since this covers a range of events/activities it is important that the task description include information specific to the event/activity – the event type, such as the meeting type, notification type, or other event type and description. The meeting date can be included if known at the time of task creatio, as well as any additional information that could be helpful in distinguishing this Task from others in the Task Workbench. Additionally, if the task is specific to a certain provider, that information should be captured here if it has not been included in the Task Name.
• EV Information:
  • CCO Meeting Data Capture Task: Will be tracked at the Task Level.
  • Feedback Data Capture Task: Not Applicable
  • Event Data Capture Task: Will be tracked at the Task Level. The Project Level Access user indicates if EV needs to be tracked or not.

CCO Meeting Data Capture

The CCO Meeting Data Capture Task captures the CCO meeting information. The CCO meeting is required as part of the Risk MAP process. Note that Open House Meetings should be tracked separately, even if they occur on the same day.

• Purpose: To track CCO Meeting information. This includes deliverables that occur throughout the CCO Meeting process from preparation, meeting execution and post meeting activities.
• Task Start: After KDP3 and preliminary map release and prior to the Appeal Period Start. Project should have regulatory products to include this Task.
• Uploads: Any deliverable that occurs during the preparation, execution, or post meeting. This includes meeting invitation, sign-in sheets, post-meeting surveys, etc. Files should be organized into a folder structure that includes a folder for each: Prepare, Meeting, and Post Meeting. In order to have files organized and easily identifiable when searching for them in the File Explorer, files should be included in the appropriate folder and that the folder is zipped and uploaded. Files should be named in such a way that when they are retrieved from the File Explorer it is clear what the file is for.
• Comments: Comments should be made as appropriate and if they will better inform those assigned to the Task
• Leverage: Not Applicable
• Task Completion: The Task can be completed after the post meeting phase is complete and all deliverables have been uploaded to the MIP.
• Validation: Not Applicable

Below is the view of the CCO Meeting Data Capture Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Analysis Section allows the user to view the completed analysis of the prior related Tasks (including: CCO Meetings, Leverage, and Comments)

The only editable sections of this Task are the Submit Data, Analysis, add Leverage, and Comments sections. Steps include:

1. Next a user must upload CCO data file before the CCO Data Task is submitted. Uploads can occur as long as the task has not been submitted. There can be multiple uploads, if needed.
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. To view uploaded files in File Explorer, select the View in File Explorer link
2. A user can add CCO Meeting to the Task by selecting the Add button under the CCO Meeting section. Users can add multiple CCO meetings if need, for example if a County needs multiple meetings to accommodate all of the communities, a CCO meeting can be added for each meeting that was held.
   1. The user will then be required to enter
   • Outreach Type - for CCO this is Meeting Held
   • Description – Meeting Name should be entered, if multiple meetings occurred name each CCO meeting to better describe a specific meeting on a specific date
   • Date – date for specific meeting added
   • Comments - any comments that better describe the meeting, this may include attendees
   2. Once those fields are completed the user must select the Save button in order to add the CCO meeting information into the MIP

      

3. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Feedback Data Capture

The Feedback Data Capture Task captures stakeholder comments and data submissions that may occur throughout the Project lifecycle, with the exception of information received during the 90-day Appeal Period (see section Due Process Purchase for more information). The Feedback Data Capture should be limited to tracking information submitted within a Risk MAP Project, if feedback occurs outside of a Risk MAP Project that information should be tracked elsewhere.

• Purpose: To collect feedback or community comments received from various 30-day comment periods (e.g., SID 620 and 621 letters, Preliminary Distribution, etc.) or outreach events (e.g., CCO Meeting, FRR Meeting, Resilience, etc.) The work/activities for SIDs and event information (preparation, execution and post meeting activities are captured in the Event Data Capture section, please see that section for additional information. Feedback Data Capture does not include comments or feedback received from the 90-day Appeal Period.
• Task Start: This Task could occur at any time in a Risk MAP Project timeline.
• Uploads: Uploads of should include proof of compliance with SID 620 and 621 (letters sent, for example) any supporting data or documentation related to feedback or community comments received from 30-day comment periods or Project outreach events. Upload any supporting data or documentation related to feedback or community comments received from 30-day comment periods or Project outreach events. Files should be named in such a way that when they are retrieved from the File Explorer it is clear what the file is for. If feedback is received for different 30-day comment periods and outreach events, a folder structure should be created to reflect the different feedback areas and files should be put into the appropriate folders. Folders should be zipped and uploaded to the MIP.
• Comments: Comments should be made as appropriate and if they will better inform those assigned to the Task.
• Leverage: Applicable if data are received that are usable in developing regulatory products or risk products.
• Task Completion: When the associated Risk MAP Project is complete.
• Validation: Not Applicable.

Below is the view of the Feedback Data Capture Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Analysis Section allows the user to view the completed analysis of the prior related Tasks (including: Outreach Feedback, Leverage, and Comments)

The only editable sections of this Task are the Submit Data, Analysis, add Leverage, and Comments sections. Steps include:

1. A user can upload Outreach Feedback data file. Uploads can occur as long as the task has not been submitted. There can be multiple uploads, if needed
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task.
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. To view uploaded files in File Explorer, select the View in File Explorer link
2. A user can add Outreach Feedback to the Task by selecting the Add button under the Outreach Feedback section. Users can add multiple Outreach Feedback if needed and as the Feedback is received throughout the life of the task.
   1. The user will then be required to enter:
      • Feedback Phase from the Dropdown – this includes Discovery, Data Development, Preliminary, Post Preliminary Processing and Other. If other is selected the user should give detailed information explaining the selection in the Comments field.
      • Date Received - date feedback was received
      • Received from - who submitted the feedback, this should include, at minimum, the organization name and title of who submitted the data
      • Response Date – date feedback was responded to. This field is not required
      • Comments - this should be used if Other was selected from the Feedback Phase dropdown or if there is any relevant information that should be shared. This field is not required but is highly recommended
      • Outcome - this should how the feedback was handled. This field is not required
   2. Once those fields are completed the user must select the Save button in order to add the Feedback to the MIP

      

3. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button

Event Data Capture

The Event Data Capture is meant to capture all meetings, other events or outreach touchpoints, and other communications or outreach-related efforts not already captured within other purchases in the MIP both in and outside of the Risk MAP Process. They include but are not limited to: Project Kickoff Meetings with communities, SIDs 620 and 621 notifications, Flood Risk Review Meetings, Work Map Meetings, Resilience Meetings, Open House Meetings, and High-Water Mark events.

If the event happens outside of a Risk MAP Project a new Project should be created with separate Outreach Purchase and Event Data Capture Tasks.

• Purpose: To track other Risk MAP Meeting and Engagement information - including meetings, workshops, trainings, Mitigation Planning Technical Assistance engagements; and any special outreach efforts, and for documenting compliance with SIDs 620, 621, 622 (stakeholder comments and/or data submissions received from these events are captured in the Feedback Data Capture section – please see that section for additional guidance about feedback)
• Task Start: May occur at any time
• Uploads:
• For meetings/events any deliverable that occurs during the preparation, execution, or post meeting/event should be uploaded. Files should be organized into a folder structure that includes a folder for each: Prepare, Meeting, Post Meeting. In order to have files organized and easily identifiable when searching for them in the File Explorer files should be included in the appropriate folder and that the folder is zipped and uploaded. Files should be named in such a way that when they are retrieved from the File Explorer it is clear what the file is for.
• For SIDs 620 and 621 the upload should include proof of compliance with SID 620 and 621 (letters sent, for example). Files should be named in such a way that when they are retrieved from the File Explorer it is clear what the file is for.
• For SID 622 any documentation of the radio and TV ads should be uploaded. Files should be named in such a way that when they are retrieved from the File Explorer it is clear what the file is for.
• Comments: Comments should be made as appropriate and if they will better inform those assigned to the Task
• Leverage: Not Applicable
• Task Completion: When all post meeting/event/outreach effort activities are complete, and all deliverables have been uploaded to the MIP and when all updates in the Task accurately reflect all phases of meeting/ event/ outreach effort are complete.
• Validation: Not Applicable

Below is the view of the Outreach Event Capture Task. From this screen a user will see:

• Project and Task Information Section displays important information including Project Name and Case Number, Purchase Title, Purchase Description if available, Task Name, who the Task is assigned to, Baseline Task Start and End Dates. This also includes Geography(ies) and Comment history
• Submit Data Section allows the user to view uploaded data in File Explorer and the validation status of the data uploaded
• Analysis Section allows the user to view the completed analysis of the prior related Tasks (including: Outreach Events, Leverage, and Comments)

The only editable sections of this Task are the Submit Data, Analysis, add Leverage, and Comments sections. Steps include:

1. A user can upload an Outreach Meeting File(s)
   1. After selecting the file, a user must select the Upload File button to have the file saved to the Task.
   2. After selecting the file, a user must select the either the Direct Upload button, which uploads the via directly into the MIP, or the Managed Upload button, which engages Aspera software to facilitate a smoother, quicker upload for larger files (>2GB). Reference the Aspera Software instructions for details when using Aspera for the first time.
   3. To view uploaded files in File Explorer, select the View in File Explorer link
2. A user can add Outreach Events to the Task by selecting the Add button under the Outreach Events section. Users can add multiple Outreach events, if needed.
   1. The user will then be required to enter:
   • Event Name this should include the event name, if multiple events of the same name are going to be created, please make sure that the description clearly identifies the differences in the meeting
   • Event Description - This should include any additional relevant event information. This field is not required but it is highly recommended
   • Event Start Date - the date the meeting occurred
   • Event End Date – this will be used when events take place over multiple days, such as a conference. This field is not required and should only be used when an event take place more than a single day
   • Event Location - the specific location of the event, if the event was not an in-person event, it can still be captured, for example as “webinar”. This is not a required field but highly recommended
   • Event Attendance – a list of attendees can be added to the Event Attendance Field or an attendee list can be uploaded using the Upload Event Data option. This is not required, however if an attendee list is a deliverable it must be uploaded.
   • Comments - Any additional comments can be added here. This field is not required
   2. Once those fields are completed the user must select the Save button in order to add the Event to the MIP

      

3. A user can select the Save button at any point during this process or once all the mandatory fields are completed the user can select the Submit button