\*\*\*Note: This template can be used for CTPs, IDIQs, or OFAs. Please
delete those sections that do not apply to this statement when filling
out this template.\*\*\*

![](media/image1.png){width="2.0861111111111112in"
height="0.75in"}[{Insert CTP Name(s)}]{.mark}

Cooperating Technical Partners

Mapping Activity Statement

**Mapping Activity Statement No.** {Insert Mapping Activity Statement
Number }

In accordance with the Cooperating Technical Partners (CTP) Partnership
Agreement dated {Insert CTP Partnership Agreement date} between {Insert
CTP name} and the Federal Emergency Management Agency (FEMA), Mapping
Activity Statement (MAS) No. {Insert MAS No.} is as follows:

## Or {#or .unnumbered}

##  {#section .unnumbered}

![](media/image1.png){width="2.0861111111111112in" height="0.75in"}

statement of work

[{Insert IDIQ or OFA Name(s)}]{.mark}

Contract no. \_\_\_\_\_\_\_\_\_\_\_

Task Order no. \_\_\_\_\_

The Flood Map Project described in this Statement of Work (SOW) shall be
completed in accordance with Contract No. {Insert IDIQ Contract No.,
Task Order No., } dated {Insert date contract signed}, between {Insert
IDIQ,OFA name} and the Federal Emergency Management Agency (FEMA).

## SECTION 1---OBJECTIVE AND SCOPE {#section-1objective-and-scope .unnumbered}

The objective of the Flood Map Project documented in this {MAS/SOW} is
to develop a Digital Flood Insurance Rate Map (DFIRM) and Flood
Insurance Study (FIS) report for {Insert county or community name(s)}.
All processes and deliverables shall be completed in accordance to the
Federal Emergency Management Agency's (FEMA's) *Guidelines and
Specifications for Flood Hazard Mapping Partners* (G&S) and effective
Procedure Memoranda (PMs). These documents can be found on FEMA's
website at <http://www.fema.gov/plan/prevent/fhm/gs_main.shtm> and
<http://www.fema.gov/plan/prevent/fhm/gs_memos.shtm>.

The DFIRM and FIS report will be produced in the FEMA {Insert Countywide
or Community-Based} format in the North American Vertical Datum of 1988
(NAVD88). (Refer to PM 41 for exceptions.)

\<Delete the text and the table below if the Flood Map Project includes
only conversion of effective flood maps to DFIRM format. Table may be
placed on separate page to enhance readability for large projects.\> In
addition, the Mapping Partners involved in this project will develop new
and/or updated flood hazard data, as summarized in Table 1.1, Flooding
Source(s) to be Studied.

Table 1.1 Flooding Source(s) to be Studied

<table>
<colgroup>
<col style="width: 8%" />
<col style="width: 10%" />
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 7%" />
<col style="width: 10%" />
<col style="width: 9%" />
</colgroup>
<tbody>
<tr class="odd">
<td rowspan="2"><strong>Flooding Source</strong></td>
<td rowspan="2"><strong>Reach Limits</strong></td>
<td rowspan="2"><strong>Reach Length</strong></td>
<td colspan="2"><strong>Detailed Riverine</strong></td>
<td colspan="5"><strong>Detailed Coastal</strong></td>
<td rowspan="2"><strong>Limited Detail Study</strong></td>
<td rowspan="2"><strong>Redelineation of SFHAs Using Effective Profiles
and New Topography</strong></td>
<td rowspan="2"><strong>Refine/ Establish Zone A</strong></td>
</tr>
<tr class="even">
<td><blockquote>
<p><strong>Hydrology</strong></p>
</blockquote></td>
<td><blockquote>
<p><strong>Hydraulics</strong></p>
</blockquote></td>
<td><strong>Stillwater</strong></td>
<td><strong>Setup</strong></td>
<td><strong>Wave Height</strong></td>
<td><strong>Wave Runup</strong></td>
<td><strong>Erosion</strong></td>
</tr>
<tr class="odd">
<td>{Insert name of flooding source}</td>
<td>{Insert upstream and downstream limits}</td>
<td>{Insert reach length in feet and/or miles}</td>
<td><blockquote>
<p>{Check if applicable}</p>
</blockquote></td>
<td><blockquote>
<p>{Check if applicable}</p>
</blockquote></td>
<td><blockquote>
<p>{Check if applicable}</p>
</blockquote></td>
<td><blockquote>
<p>{Check if applicable}</p>
</blockquote></td>
<td><blockquote>
<p>{Check if applicable}</p>
</blockquote></td>
<td><blockquote>
<p>{Check if applicable}</p>
</blockquote></td>
<td><blockquote>
<p>{Check if applicable}</p>
</blockquote></td>
<td><blockquote>
<p>{Check if applicable}</p>
</blockquote></td>
<td><blockquote>
<p>{Check if applicable}</p>
</blockquote></td>
<td><blockquote>
<p>{Check if applicable}</p>
</blockquote></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>

This Flood Map Project will be completed by the following Mapping
Partners:

-   {Insert CTP name};

-   {Insert name of CTP contractor, if applicable}; and

-   {Insert name of IDIQ or other FEMA Study Contractor, if applicable}.

The Mapping Partner shall notify FEMA and all applicable parties of all
meetings with community officials at least two weeks prior to the
meeting (with as much notice as possible). FEMA and/or its contractor
may or may not attend the community meetings.

The Mapping Partner shall maintain an archive of all data submitted.
(All supporting data must be retained for three years from the date a
funding recipient submits its final expenditure report to FEMA.)

The activities for this Flood Map Project, including any required
Quality Control Requirements as outlined in PM 42, and the Mapping
Partners that will complete them are summarized in Table 1.2, Flood
Mapping Project Activities. The sections of this {MAS/SOW} that follow
the table below describe the specific mapping activities, responsible
Mapping Partner(s), FEMA standards that must be met, and resultant map
deliverables.

\<Include only those tasks in Table 1.2 that apply to this mapping
project\>

**Table 1.2 Flood Mapping Project Activities**

TASK ASSIGNMENTS![](media/image2.wmf)

\<Optional Paragraph and Table\> The {Insert name of responsible Mapping
Partner} assigned the floodplain mapping task will include the
Provisionally Accredited Levee (PAL) classification if known. Levee
classification will be documented in Table 1.3, Levee PAL
Classification. If the PAL Classification for a levee changes during the
course of the project FEMA will contact the {Insert name of responsible
Mapping Partner} to discuss the need to revise the statement of work.

Table 1.3 -- Levee PAL Classification

+----------------+-------------------+--------------+-----------------+
| ###            | ### Le            | ##           | ### Additional  |
| County {#count | vee Name {#levee- | # Provisiona |  Mapping Requir |
| y .unnumbered} | name .unnumbered} | lly Accredit | ed {#additional |
|                |                   | ed Levee Cla | -mapping-requir |
|                |                   | ssification  | ed .unnumbered} |
|                |                   | {#provisiona |                 |
|                |                   | lly-accredit |                 |
|                |                   | ed-levee-cla |                 |
|                |                   | ssification  |                 |
|                |                   | .unnumbered} |                 |
+----------------+-------------------+--------------+-----------------+
| #              | ###  {#secti      | ### [A,      | ### []{.        |
| ##  {#section- | on-2 .unnumbered} | B or not eli | mark} {#section |
| 1 .unnumbered} |                   | gible]{.mark | -3 .unnumbered} |
|                |                   | } {#a-b-or-n |                 |
|                |                   | ot-eligible  |                 |
|                |                   | .unnumbered} |                 |
+----------------+-------------------+--------------+-----------------+
| #              | ###  {#secti      | ###          | ###  {#section  |
| ##  {#section- | on-5 .unnumbered} | {#section-6  | -7 .unnumbered} |
| 4 .unnumbered} |                   | .unnumbered} |                 |
+----------------+-------------------+--------------+-----------------+
| #              | ###  {#secti      | ###  {       | ###  {#section- |
| ##  {#section- | on-9 .unnumbered} | #section-10  | 11 .unnumbered} |
| 8 .unnumbered} |                   | .unnumbered} |                 |
+----------------+-------------------+--------------+-----------------+
| ##             | ###  {#sectio     | ###  {       | ###  {#section- |
| #  {#section-1 | n-13 .unnumbered} | #section-14  | 15 .unnumbered} |
| 2 .unnumbered} |                   | .unnumbered} |                 |
+----------------+-------------------+--------------+-----------------+
| ##             | ###  {#sectio     | ###  {       | ###  {#section- |
| #  {#section-1 | n-17 .unnumbered} | #section-18  | 19 .unnumbered} |
| 6 .unnumbered} |                   | .unnumbered} |                 |
+----------------+-------------------+--------------+-----------------+

{Insert name of responsible Mapping Partner} is responsible for the
implementation of an independent Quality Assurance/Quality Control
(QA/QC) plan for all assigned activities. The {Insert name of
responsible Mapping Partner}will submit a Summary Report that describes
and provides the results of all automated or manual QA/QC review steps.
The report should include the process for all assigned activities.

Independent QC review activities may be performed by the [{CTP, IDIQ,
OFA}]{.mark}s or FEMA's contractor at the discretion of FEMA. If the
[{CTP, IDIQ, OFA}]{.mark} will be utilizing its [{staff, contractors,
partners}]{.mark} to do the QC review, this should be identified during
scoping. The [{CTP, IDIQ, OFA}]{.mark} will need to submit its QC plan
to the Regional Project Officer for approval. Please note FEMA will also
be performing periodic audits and overall study/project management to
ensure study quality. The {CTP, IDIQ, OFA} will be responsible for
addressing any and all comments resulting from independent QC, including
re-submittal of deliverables as needed to pass technical review.

Metadata is required for all activities. {Insert appropriate Data
Capture Standards (DCS) language applicable to this Mapping Activity
Statement. PLEASE NOTE: The DCS are being updated. FEMA Regions should
update this document accordingly once the DCS update is complete.}

DFIRM-related tasks require a passing QC Report from FEMA's National
DFIRM database auto-validation tool for Quality Review (QR) #1, #2, and
#5 as described in PM 42. Training materials for this step are available
on the MIP at MIP User Care\>Training Materials.

FEMA will provide download/upload capability for data submittals through
the Mapping Information Platform (MIP) located at
https://hazards.fema.gov. As each activity is completed, the data must
be submitted to the MIP.

The {Insert name of responsible Mapping Partner} assigned the activity
will respond to any comments generated as a result of the mandatory
quality control checks by the National Service Provider (NSP) as
described in PM 42. The NSP QC process is nationally funded and required
on each FIS. The NSP QC process includes the following activities:

-   **Validate Content Submission.** Automatic metadata and visual RMC
    validation of submitted data for Perform Field Survey, Develop
    Topographic Data, Develop Hydrologic Data, Develop Hydraulic Data,
    Perform Coastal Analysis, Acquire Base Map Data, Perform Floodplain
    Mapping, Develop DFIRM Database, Produce Preliminary Map Products
    and Final Map Products tasks.

-   **QR #1.** Performed after the Develop DFIRM Database task.

-   **QR #s 2 and 3.** Performed after the Produce Preliminary Map
    Products task.

-   **QR #4.** Performed after the Create Base Flood Elevation (BFE)
    Notices step in the MIP workflow during Post Preliminary Processing.

-   **QR #5.** Performed after the Produce Final Map Products task
    during Post Preliminary Processing.

-   **QR #6.** Performed after the Prepare LFD Docket step in the MIP
    workflow during Post Preliminary Processing.

-   **QR #7.** Performed after the Submit MSC Deliverable step in the
    MIP workflow during Post Preliminary Processing.

In cooperation with the FEMA Project Officer, a Project Management Team
(PMT) will be established by the {Insert name of responsible Mapping
Partner}consisting of representatives from the [{Insert name of Mapping
Partner, and their mapping team if appropriate}]{.mark}, FEMA's regional
engineer, the RMC, and other appropriate parties. The PMT will be
responsible for coordinating the activities identified in this
[{MAS/SOW}]{.mark}. The FEMA Region will be provided with documentation
identifying the established PMT.

The MIP shall be updated for status reporting of each of the data
development activities within the Manage Data Development task, not less
than every thirty days, when the activity is complete, and also include
leverage data. Similarly the Manage Preliminary Map Production and
Manage Post Preliminary Processing tasks shall be updated monthly when
the producer is performing work on a task in those modules. The "Manage"
tasks will be open and accepting updates for up to 90 days after the
completion of the last producer task in each module. The MIP shall also
be populated with appropriate leverage information regarding who paid
for the data provided and the amount of data used by the Flood Map
Project.

**Scoping**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

[Scope:]{.underline} The Project Scoping phase typically begins once
some level of a community's mapping needs have been identified and FEMA
and the community have decided to initiate a Flood Map Project to create
or update the FIRM. The scoping process is divided into three main parts
-- Pre-Scoping Meeting Activities, the Scoping Meeting Activities, and
the Post-Scoping Meeting Activities.

Pre-Scoping Meeting Activities

-   Initiate the Pre-Scoping activities by identifying the PMT,
    determining the community contacts, and collecting pertinent
    information about the community. Conduct background research to
    collect current mapping needs and begin available geospatial data
    search.

-   Obtain spatial data to be used during the meeting preparation
    effort.

-   Acquire the current effective data for the community, such as the
    flood hazard data shown in effective FIS reports and on effective
    FIRMs and Flood Boundary and Floodway Maps (FBFMs), and pertinent
    flood structure data.

-   If pre-scoping steps are performed by a separate Contractor, submit
    a report summarizing the data collection efforts and deliverables.

Preliminary Research Activities can be separated into three
categories---researching selected needs, effective information and
researching available data for the Flood Map Project. The selected needs
data identified during the Mapping Needs Assessment process can be
obtained through the FEMA Region/RMC and plotted on the scoping map for
discussion during the scoping meeting. The following tasks shall be
completed to research effective information: inventory the FEMA's
archives and/or information management systems for effective FIRM
panels, FBFM panels, FIS reports, and other flood hazard data or
existing study data; summarize the information in the effective streams
file and effective coastal study; summarize contiguous community
agreement checks; review Community Assistance Visit (CAV) and Community
Assistance Contact files; and develop a "scoping map" and an overview of
the results of the research. Other data collected during preliminary
research activities will include obtaining community information and the
best readily available base map materials (political areas,
transportation, hydrology, shorelines orthoimagery, and topography
data). Stream centerlines should be populated with the limits of the
effective FEMA studies and selected needs attributes.

Scoping Meeting

-   Coordinate, setup, and hold the Scoping Meeting to inform the
    community of the upcoming flood study and of their responsibilities
    related to it; this includes identifying a time, place, and
    participants. The purpose of this meeting is to present the
    information gathered during the preliminary research activities to
    the local officials (State, county, and municipal) and coordinate on
    prioritization and identification of study areas. {Insert name of
    responsible Mapping Partner}shall be responsible for compiling the
    necessary information for the meeting.

```{=html}
<!-- -->
```
-   Review list of selected needs and capture additional community needs
    and/or wants in order to determine the level of effort and the
    extent of any new/updated studies. Review the selected needs list,
    effective and other data research findings, and make selections of
    proposed methods for obtaining/producing flood data.

-   Compile the information prepared for and recorded during the Scoping
    Meeting

During the Scoping Meeting, the PMT shall review the needs list. Any
additions or changes to the selected needs list shall be discussed with
all members.

The {Insert name of responsible Mapping Partner}will be acting as the
Consultation Coordination Officer (CCO) for this flood study as
identified in 44 CFR Part 66. During the Scoping Meeting, the {Insert
name of responsible Mapping Partner}must inform the communities of their
responsibilities as described under the above-referenced regulation.
Following initial contact with the communities, the {CTP, IDIQ, OFA}
will prepare and setup the Community Case File and Flood Elevation
Determination Docket for the maintenance of all communication and
coordination throughout the project as outlined in 44CFR Parts 66 and
67.

Post-Scoping Meeting Activities

-   Select available and needed geospatial data to be used in the study
    and update FEMA's geospatial data tracking systems, National Digital
    Elevation Program (NDEP) and National Digital Orthophoto Program
    (NDOP) located at <http://hazards.fema.gov/metadata/NDEP> and
    <http://hazards.fema.gov/metadata/NDOP>.

-   Evaluate selected needs and community requests and/or wants to
    determine the community's unmet needs and develop the final Scope of
    Project document for delivery to FEMA and the community

-   Update FEMA's needs management tracking and other geospatial
    tracking systems (Mapping Needs Update Support System (MNUSS), NDEP,
    and NDOP).

Based on the discussion of flood data update and base map update
requests, {Insert name of responsible Mapping Partner}and the FEMA
Project Officer will finalize the areas to be included in the final
scope of project (based on recommendations provided by the PMT). Areas
to be studied by detailed, limited detailed, redelineation, and
approximate methods shall be identified. The following issues will be
discussed and refined: Review and Refinement of Flood Hazard
Identification Methodologies, Review of Proposed Paneling Scheme, Review
and Refinement of Base and Topographic Map Source, and Finalization of
Map Production and Database Options.

Identify all stream/coastal reaches where levees are shown as providing
protection against the 1‑percent‑annual-chance flood. {Insert name of
responsible Mapping Partner} should work with the FEMA Regional Office
to request the information specified in Title 44 Code of Federal
Regulations (CFR) 65.10, mapping of areas protected by levee systems,
from the community or other party seeking continued recognition of the
levee and provide this information to the FEMA Regional Office and/or
PMT.

Many of the activities at each phase can take place concurrently and are
not contingent on the completion of previous tasks. The FEMA Project
Officer, working in close coordination with the PMT, has the flexibility
of tailoring the Scoping process to best fit the needs of the project.
{Insert name of responsible Mapping Partner}will evaluate the effective
flood data, available base data and selected needs to determine the
scope of project to be approved by FEMA.

[Standards]{.underline}: All Scoping work shall be performed in
accordance with the standards specified in Section 5 - Standards.

\<Add, modify or delete deliverables below, as necessary\>

[Deliverables:]{.underline} {Insert name of responsible Mapping Partner}
shall make the following products available to FEMA by uploading the
digital data to the MIP.

-   Final Scope of Project documented in MAS or SOW will be delivered in
    accordance with the schedule outlined in Section 6 - Schedule to the
    Regional Project Officer for approval.

-   QA/QC Plan for the review of the mapping project outlined in this
    {MAS/SOW}. This will include the checklists developed for that
    review in accordance with the schedule included in Section 6 -
    Schedule.

-   Updated list of CEO or local FPA contacts.

-   Report documenting levee information transmitted to the FEMA
    Regional office and/or the PMT.

-   Report from MNUSS and/or other FEMA needs management system, showing
    needs identified during the scoping process that will not be
    addressed in the final scope of project are entered.

-   Report showing that, if obtained from non-Federal sources,
    information on available terrain and ortho-imagery data has been
    entered into the NDEP and NDOP project tracking Web sites,
    respectively.

-   Other deliverables including reports, correspondence, agenda,
    meeting summaries, tabular data, and geospatial files to be
    submitted throughout the scoping process as specified in FEMA's G&S,
    Appendix I and Appendix M.

**Outreach**

*(NOTE: The performance of outreach takes place throughout the life of
the flood study project. Therefore, we recommend tracking the outreach
budget, in the MIP Workflow, equally between Produce Preliminary Map
Products and Post Preliminary Processing. An alternate tracking method
is acceptable with approval from the FEMA Regional Office.)*

The outreach activities for a Flood Map Project can best be understood
as a process that begins during the Project Scoping phase and continues
through the map production and post-preliminary phases.

The overarching goal for conducting outreach is to create a climate of
understanding and ownership of the mapping process at the State and
local levels. Well-planned outreach activities can reduce political
stress, confrontation in the media, and public controversy, which can
arise from lack of information, misunderstanding, or misinformation.
These outreach activities also can assist FEMA and other members of the
PMT in responding to congressional inquiries.

The {Insert name of responsible Mapping Partner}}will work with the
Regional Office during the initiation of this activity to determine an
Outreach Plan for implementation throughout the mapping project. The
Regional Office will have access to many outreach tools that have been
developed for this process that can be utilized or customized. Volume 1
of the G&S provides specific outreach goals that can be considered.

All communication with local governments will be done in accordance with
44 CFR Part 66.

[Deliverables:]{.underline}

-   Upon determination of an Outreach and Coordination Approach, the
    {Insert name of responsible Mapping Partner}shall deliver the
    following to the FEMA Regional Project Officer in accordance with
    the schedule outlined in Section 6 - Schedule:

    -   A report detailing outreach and coordination activities

    -   Backup or supplemental information used in writing this report

**Field Survey**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

[Scope]{.underline}: To supplement any field reconnaissance conducted
during the Project Scoping phase of this project, {Insert name of
responsible Mapping Partner} shall conduct a detailed field
reconnaissance of the specific study area to determine conditions along
the floodplain(s), types and numbers of hydraulic and/or flood-control
structures, apparent maintenance or lack thereof of existing hydraulic
structures, locations of cross sections to be surveyed, and other
parameters needed for the hydrologic and hydraulic analyses.

{Insert name of responsible Mapping Partner} shall conduct field
surveys, including obtaining channel and floodplain cross sections,
identifying or establishing temporary or permanent bench marks, and
obtaining the physical dimensions of hydraulic and flood-control
structures. If appropriate {Insert name of responsible Mapping Partner}
shall also identify items needed for coastal analyses including land
cover, vegetation types, housing, dunes, beach nourishment, and coastal
structures. {Insert name of responsible Mapping Partner} also shall
coordinate with other Mapping Partners that are involved in the
Topographic Data Development process regarding ongoing activities and
deliverables.

\<Add additional details regarding the scope of this task, as
appropriate\>

[Standards]{.underline}: All Field Survey work shall be performed in
accordance with the standards specified in Section 5 - Standards.

[Deliverables]{.underline}: {Insert name of responsible Mapping Partner}
shall make the following products available to FEMA by uploading the
digital data to the MIP. A metadata file complying with the NFIP
Metadata Profiles Specifications, must accompany the G&S compliant
digital data. Additionally, the Technical Support Data Notebook (TSDN)
format described in the G&S must be delivered in accordance with Section
2 -- Technical and Administrative Support Data Submittal.

This submittal will occur in accordance with the schedule outlined in
Section 6 - Schedule. Where paper documentation is required by State Law
for Professional certifications, you may submit the paper in addition to
a scanned version of the paper for the digital record.

\<Add, modify or delete deliverables below, as necessary\>

-   A report summarizing the findings of the field reconnaissance;

-   Maps and drawings that provide the detailed survey results;

-   Survey notebook containing cross section and structure data;

-   Documentation of the horizontal and vertical datum;

-   Digital versions of draft text for inclusion in the FIS report;

-   Digital survey data consistent with the DCS as described in the G&S,
    and

-   A Summary Report that describes and provides the results of all
    automated or manual QA/QC review steps taken during the preparation
    of the DFIRM as outlined in the approved QA/QC Plan.

**Topographic Data Development**

**\<Every MAS for a flood data update must include this task to ensure
the topography used is documented and submitted. Normally this task will
be assigned to the same mapping partner that will be the primary user
(i.e. hydraulics or floodplain mapping).\>**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

[Scope]{.underline}: {Insert name of responsible Mapping Partner} shall
obtain additional topographic data of the overbank areas of the flooding
sources and coastal floodplains studied. These data will be used \<add
or deleted as needed\> for hydrologic analysis, hydraulic analysis,
floodplain boundary delineation and/or testing of floodplain boundary
standard compliance. {Insert name of responsible Mapping Partner} shall
gather information on what topographic data is available for the given
community and what accuracy and currency it meets. {Insert name of
responsible Mapping Partner} shall use this topographic data that is
better than that of the original study. In coordination with the partner
who performed scoping, ensure that the FEMA Geospatial Data Coordination
Policy and Implementation Guide is followed and the data obtained or to
be produced are documented properly. {If necessary, describe additional
steps that may need to be taken to use the available data.}

\<Optional Paragraph, as appropriate\> {Insert name of responsible
Mapping Partner} shall generate new topographic data for {Insert name of
flooding souce(s)}. {Insert name of responsible Mapping Partner} also
shall coordinate with team members conducting field surveys. Accuracy
for the topographic data shall be selected based on the current FEMA
requirements as documented in the G&S. Normally this is 37cm RMSE except
for extremely flat areas. No FEMA funds shall be expended on new
topographic data unless prior approval is given by the Regional Project
Officer after analyzing the need for updated topographic data at the end
of the scoping period.

For this activity, {Insert name of responsible Mapping Partner} also
shall generate the data collected under this Topographic Data
Development task and via field surveys to create a best available
digital elevation model for the subject flooding sources. In addition,
{Insert name of responsible Mapping Partner} shall address all concerns
or questions regarding the topographic data development and processing
that are raised by {Insert name of responsible Mapping Partner} during
the independent QA/QC review. {Insert name of responsible Mapping
Partner} should confirm with the COTR the automated appropriate data
model(s) (i.e. contours, Digital Elevation Models (DEMs), TIN, mass
points and breaklines) for the intended use of the data \<Add additional
details regarding the scope of this task, as appropriate\>

\<Optional Paragraph and Table, as appropriate\> [{Insert name of
responsible Mapping Partner}]{.mark} shall use topographic data for the
areas described in the Table 1.4 Summary of Topographic Data table. The
source of the topographic data should be indicated as well. [{Insert
name of responsible Mapping Partner}]{.mark} also shall coordinate with
other team members conducting field surveys. Contour interval and/or
accuracy for the topographic data shall be selected based on the current
FEMA requirements as documented in the G&S*.*

For this activity, [{Insert name of responsible Mapping Partner}]{.mark}
also shall develop topographic maps and/or DEMs for the subject flooding
sources using the data collected under this Topographic Data Development
process and via field surveys. In addition, [{Insert name of responsible
Mapping Partner}]{.mark} shall address all concerns or questions
regarding the topographic data development that are raised by [{Insert
name of Mapping Partner responsible for this activity}]{.mark} during
the independent QC review, or during the PM 42 defined Validation
Process.

**Table 1.4** Summary of Topographic Data

  -------------- ---------------------------- ----------------------------
  **County**     **Description**              **Source**

                                              [Public domain, community
                                              supplied, procured as part
                                              of this activity,
                                              etc.]{.mark}

  []{.mark}                                   

                                              

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

[Standards]{.underline}: All Topographic Data Development work shall be
performed in accordance with the standards specified in Section 5 -
Standards.

[Deliverables]{.underline}: In accordance with the G&S, {Insert name of
responsible Mapping Partner} shall make the following products available
to FEMA by uploading the digital data to the MIP and submitting in
Technical Support Data Notebook (TSDN) format so that {Insert name of
Mapping Partner responsible for Independent QA/QC} can access it for an
independent QA/QC review in accordance with the schedule outlined in
Section 6 - Schedule. A metadata file complying with the NFIP Metadata
Profiles Specifications, must accompany the uploaded G&S compliant
digital data. Additionally, the TSDN format described in the G&S must be
delivered in accordance with Section 2 -- Technical and Administrative
Support Data Submittal.

Where paper documentation is required by State Law for Professional
certifications, you may submit the paper in addition to a scanned
version of the paper for the digital record.

\<Add, modify or delete deliverables below, as necessary. Only include
data formats needed for the project\>

-   Digital contour data;

-   Report summarizing methodology and results;

-   Mass points and breaklines data;

-   Gridded digital elevation model data

-   TIN data

-   Checkpoint analyses to assess the accuracy of data, including Root
    Mean Square Error calculations to support vertical accuracy;

-   Identification of data voids and methods used to supplement data
    voids;

-   National Geodetic Survey data sheets for Network Control Points used
    to control remote-sensing and ground surveys;

-   Other supporting files consistent with the DCS in the G&S; and

-   A Summary Report that describes and provides the results of all
    automated or manual QA/QC review steps taken during the preparation
    of the DFIRM as outlined in the approved QA/QC Plan.

**Independent QA/QC Review of Topographic Data**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

[Scope]{.underline}: {Insert name of responsible Mapping Partner} shall
review the mapping data generated by {Insert party responsible for
conducting the topographic information} under Topographic Data
Development to ensure that these data are consistent with FEMA standards
and standard engineering practice, and are sufficient to prepare the
DFIRM. If {Insert name of responsible Mapping Partner}utilizes a
contractor to perform the QA/QC, the contractor must be a different
contractor than who performed the original analyses. FEMA may audit or
assist in these activities if deemed to be necessary by the Regional
Project Officer.

\<Add additional details regarding the scope of this task, as
appropriate\>

[Standards]{.underline}: All Topographic Data Development work shall be
reviewed in accordance with the standards specified in Section 5 -
Standards.

[Deliverables]{.underline}: In accordance with the G&S, {Insert name of
responsible Mapping Partner} shall make the following products available
to FEMA by uploading the digital data to the MIP. Additionally, the TSDN
format described in the G&S must be delivered in accordance with Section
2 -- Technical and Administrative Support Data Submittal.

This submittal will occur in accordance with the schedule outlined in
Section 6 - Schedule.

\<Add, modify or delete deliverables below, as necessary\>

-   A Summary Report that describes the findings of the independent
    QA/QC review; and

-   Recommendations to resolve any problems that are identified during
    the independent QA/QC review.

**Base Map Acquisition and Preparation**

**\<Every MAS for a flood data update must include this task to ensure
the base map used is documented and submitted. Normally it will be
assigned to the same mapping partner that will be the primary floodplain
mapping partner.\>**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

[Scope]{.underline}: Base Map Acquisition consists of obtaining the
digital base map, {specify which one}, for the project and as necessary,
preparing the base map for use. {Insert name of responsible Mapping
Partner}shall provide the digital base map. The required activities are
as follows:

\<Add, modify or delete tasks below, as necessary\>

-   Obtain digital files (raster or vector) of the base map. In
    coordination with the partner who performed scoping, ensure that the
    FEMA Geospatial Data Coordination Policy and Implementation Guide is
    followed.

-   Secure necessary permissions from the map source to allow FEMA's use
    and distribution of hardcopy and digital map products using the
    digital base map, free of charge.

-   Review and supplement the content of the acquired base map to comply
    with the requirements of the G&S.

-   For the base map components that have a mandatory data structure,
    convert the base map data to the format required in the G&S.

-   Certify that the digital data meets the minimum standards and
    specifications that FEMA requires for DFIRM production.

\<Optional Paragraph and Table, as appropriate\> In addition, [{Insert
name of responsible Mapping Partner}]{.mark}shall address all concerns
or questions regarding the base map that are raised during the
Independent QC review performed by [{Insert name of Mapping Partner
responsible for Independent QA}]{.mark}, or during the NSP's Validate
Content Submission Process. Optional Table 1.5 Summary of Base Map is
useful if multiple counties are involved with this map update. [{Insert
name of responsible Mapping Partner}]{.mark}shall summarize the base map
that will be used for each county in optional Table 1.5 Summary of Base
Map

**Table 1.5** Summary of Base Map

  -------------- -------------------------- ------------------------------
  **County**     **Description**            **Source**

                                            

                                            

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

[Standards]{.underline}: All Base Map Acquisition work shall be
performed in accordance with the standards specified in Section 5 -
Standards. The DCS must be met for this deliverable to be acceptable.

[Deliverables]{.underline}: In accordance with the G&S, {Insert name of
responsible Mapping Partner} shall make the following products available
to FEMA by uploading the digital data to the MIP so that {Insert name of
Mapping Partner responsible for Independent QA/QC} can access it for an
independent QA/QC review in accordance with the schedule outlined in
Section 6 - Schedule. A metadata file complying with the NFIP Metadata
Profiles Specifications, must accompany the uploaded digital data.
Additionally, the TSDN format described in the G&S must be delivered in
accordance with Section 2 -- Technical and Administrative Support Data
Submittal.

\<Add, modify or delete deliverables below, as necessary\>

-   Digital base map files that comply with the G&S requirements

-   Written certification that the digital data meet the minimum
    standards and specifications;

-   Digital versions of draft text for inclusion in the FIS report;

-   Documentation that FEMA can use the digital base map; and

-   Documentation of the Datum, if appropriate.

**Independent QA/QC Review of Base Map**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

[Scope]{.underline}: {Insert name of responsible Mapping Partner} shall
review the base map acquired by {Insert party responsible for acquiring
the Base Map} to ensure it includes data consistent with FEMA standards
and sufficient to include on the DFIRM. Any needed edits should be made
to the product to comply with FEMA standards.

\<Add additional details regarding the scope of this task, as
appropriate\>

[Standards]{.underline}: All Independent QA/QC work shall be performed
in accordance with the standards specified in Section 5 - Standards.

[Deliverables]{.underline}: In accordance with the G&S, {Insert name of
responsible Mapping Partner} shall make the following products available
to FEMA by uploading the digital data to the MIP. Additionally, the TSDN
format described in the G&S must be delivered in accordance with Section
2 -- Technical and Administrative Support Data Submittal.

This submittal will occur in accordance with the schedule outlined in
Section 6 - Schedule.

\<Add, modify or delete deliverables below, as necessary\>

-   A Summary Report that describes the findings of the independent
    QA/QC review;

-   Recommendations to resolve any problems that are identified during
    the independent QA/QC review; and

-   If the data is changed during review, then updated deliverables from
    previous tasks will be submitted at this time.

**Hydrologic Analyses**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

[Scope]{.underline}: {Insert name of responsible Mapping Partner}shall
perform hydrologic analyses for approximately {insert number of square
miles} square miles of drainage area for the flooding source(s) listed
earlier in Table 1.1. {Insert name of responsible Mapping Partner}shall
calculate peak flood discharges for the 10-, 2-, 1-, and
0.2-percent-annual-chance storm events using the {Insert name of
program}computer program. These flood discharges will be the basis for
subsequent Hydraulic Analyses performed under this {MAS/SOW}. In
addition, {Insert name of responsible Mapping Partner}shall address all
concerns or questions regarding the hydrologic analyses that are raised
during the independent QA/QC review performed by {Insert name of Mapping
Partner responsible for Independent QA/QC} during the QA/QC review.

\<Optional paragraph for GIS-based modeling\> If GIS-based modeling is
used, {Insert name of responsible Mapping Partner}shall document
automated data processing and modeling algorithms, and provide the data
to FEMA to ensure these are consistent with FEMA standards Digital
datasets (such as elevation, basin, or land use data) are to be
documented and provided to FEMA for approval before performing the
hydrologic analyses to ensure the datasets meet minimum requirements. If
non-commercial (i.e., custom-developed) software is used for the
analysis, then {Insert name of responsible Mapping Partner}shall provide
full user documentation, technical algorithm documentation, and the
software to FEMA for review before performing the hydrologic analyses.

\<Optional paragraph for Limited Detail modeling\> \<Add additional
details regarding the scope of this task if Limited Detail Study is to
be included\>

\<Add additional details regarding the scope of this task, as
appropriate\>

**\<Optional Table\>** Table 1.6 Summary of Hydrologic Analysis is
useful when multiple counties are involved in a project. The table to
summarize the hydrology analysis that will be used for each county and
is useful to define the scope. [{Insert name of responsible Mapping
Partner}]{.mark}shall summarize the hydrologic analysis for each county
in optional Table 1.6 Summary of Hydrologic Analysis.

**Table 1.6** Summary of Hydrologic Analysis

  -------------------- ------------------- -------------------------------
  **County Name**      **Method**          **Square Miles of New Detailed
                                           Hydrology**

  []{.mark}            []{.mark}           []{.mark}

  []{.mark}            []{.mark}           []{.mark}

  []{.mark}            []{.mark}           []{.mark}

  []{.mark}            []{.mark}           []{.mark}

  []{.mark}            []{.mark}           []{.mark}
  -------------------- ------------------- -------------------------------

[Standards]{.underline}: All Hydrologic Analyses work shall be performed
in accordance with the standards specified in Section 5 - Standards.

[Deliverables]{.underline}: In accordance with the G&S, {Insert name of
responsible Mapping Partner} shall make the following products available
to FEMA by uploading the digital data to the MIP so that {Insert name of
Mapping Partner responsible for Independent QA/QC} can access it for an
independent QA/QC review in accordance with the schedule outlined in
Section 6 - Schedule. A metadata file complying with the NFIP Metadata
Profiles Specifications, must accompany the uploaded digital data.
Additionally, the TSDN format described in the G&S must be delivered in
accordance with Section 2 -- Technical and Administrative Support Data
Submittal.

\<Include deliverables specific to Limited Detail Study if proposed\>

\<Add, modify or delete deliverables below, as necessary\>

-   Digital copies of all hydrologic modeling (input and output) files
    for the 10-, 2-, 1-, and 0.2‑percent-annual-chance storm events;

-   Digital Summary of Discharges Tables presenting discharge data for
    the flooding sources for which hydrologic analyses were performed;

-   Digital versions of draft text for inclusion in the FIS report;

-   Digital versions of all backup data used in the analysis including
    work maps;

-   Format Hydrology Database or Data Delivery consistent with the
    DCS--in the G&S; and

-   A Summary Report that describes and provides the results of all
    automated or manual QA/QC review steps taken during the preparation
    of the DFIRM as outlined in the approved QA/QC Plan.

-   \<Optional for GIS-based modeling\> For GIS-based modeling,
    deliverables shall include all input and output data, intermediate
    data processing products, and GIS data layers.

-   \<Optional for Limited Detail modeling\> For Limited Detail Study
    modeling, define the deliverables to be included.

-   Where paper documentation is required by State Law for Professional
    certifications, you may submit the paper in addition to a scanned
    version of the paper for the digital record.

**Independent QA/QC Review of Hydrologic Analyses**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

[Scope]{.underline}: {Insert name of responsible Mapping Partner} shall
review the technical, scientific, and other information submitted by
{Insert name of Mapping Partner responsible for hydrologic analyses}
specific to the hydrologic analyses to ensure that the data and modeling
are consistent with FEMA standards and standard engineering practice,
and are sufficient to prepare the DFIRM. If {Insert name of responsible
Mapping Partner}utilizes a contractor to perform the QA/QC, the
contractor must be a different contractor than who performed the
original analyses. FEMA may audit or assist in these activities if
deemed to be necessary by the Regional Project Officer. This work shall
include, at a minimum, the activities listed below.

\<Delete or add tasks below, as necessary\>

-   Review the submittal for technical and regulatory adequacy,
    completeness of required information, and supporting data and
    documentation. The technical review is to focus on the following:

    -   Use of acceptable models;

    -   Use of appropriate methodology(ies);

    -   Correctly applied methodology(ies)/model(s), including QC of
        input parameters;

    -   Comparison with gage data and/or regression equations, if
        appropriate; and

    -   Comparison with discharges for contiguous reaches or flooding
        sources.

```{=html}
<!-- -->
```
-   Maintain records of all contacts, reviews, recommendations, and
    actions and make the data readily available to FEMA; and

-   If data changed during review, then updated deliverables for
    previous tasks will be submitted at this time.

[Standards]{.underline}: All Independent QA/QC work shall be performed
in accordance with the standards specified in Section 5 - Standards.

[Deliverables]{.underline}: In accordance with the G&S, {Insert name of
responsible Mapping Partner} shall make the following products available
to FEMA by uploading the digital data to the MIP. Additionally, the TSDN
format described in the G&S must be delivered in accordance with Section
2 -- Technical and Administrative Support Data Submittal.

This submittal will occur in accordance with the schedule outlined in
Section 6 - Schedule.

\<Add, modify or delete deliverables below, as necessary\>

-   A Summary Report that describes the findings of the independent
    QA/QC review and

-   Recommendations to resolve any problems that are identified during
    the independent QA/QC review.

-   Where paper documentation is required by State Law for Professional
    certifications, you may submit the paper in addition to a scanned
    version of the paper for the digital record.

**Hydraulic Analyses**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

[Scope]{.underline}: {Insert name of responsible Mapping Partner}shall
perform hydraulic analyses for approximately {insert number of miles}
miles of the flooding sources listed earlier in Table 1.1. The modeling
will include the 10-, 2-, 1-, and 0.2-percent-annual-chance events based
on peak discharges computed under Hydrologic Analyses. The hydraulic
methods used for this analysis will include {insert the hydraulic
methods to be used. Include a table if multiple methods are used.}.

{Insert name of responsible Mapping Partner}shall use the cross-section
and field data collected during Field Survey and the topographic data
collected during the Topographic Data Collection, when appropriate, to
perform the hydraulic analyses. The hydraulic analyses will be used to
establish flood elevations and regulatory floodways for the subject
flooding sources.

{Insert name of responsible Mapping Partner}shall use the FEMA CHECK-2
or CHECK-RAS checking program to verify the reasonableness of the
hydraulic analyses. To facilitate the independent QA/QC review, {Insert
name of responsible Mapping Partner}shall provide explanations for
unresolved messages from the CHECK-2 or CHECK-RAS program, as
appropriate. In addition, {Insert name of responsible Mapping
Partner}shall address all concerns or questions regarding the hydraulic
analyses that are raised by {Insert name of Mapping Partner responsible
for Independent QA/QC} during the independent QA/QC review.

\<Optional paragraph for GIS-based modeling\> {Insert name of
responsible Mapping Partner}shall document automated data processing and
modeling algorithms for GIS-based modeling and provide the data to FEMA
for review to ensure these are consistent with the standards outlined
above. Digital datasets are to be documented and provided to FEMA for
approval before performing the hydraulic analyses to ensure the datasets
meet minimum requirements. If non-commercial (i.e., custom-developed)
software is used for the analyses, then {Insert name of responsible
Mapping Partner}shall provide full user documentation, technical
algorithm documentation, and software to FEMA for review before
performing the hydraulic analyses

\<Optional paragraph for Limited Detail modeling\> \<Add additional
details regarding the scope of this task if Limited Detail Study is to
be included\>

\<Add additional details regarding the scope, as appropriate\>

\<Optional paragraph for Levees\> Any flooding sources associated with a
levee that are mapped as providing protection on effective FIRMs, but
will not meet certification requirements for the new FIRMs, will require
revised hydraulic analysis. This revised analysis should be done in
accordance with the G&S*,* PMs 34, 43 and others that may be
appropriate.

\<Optional Paragraph and Table\> In cases where the MAS/SOW includes
multiple counties it is beneficial to summarize the hydraulic analysis
that will be used for each county in Table 1.7 Summary of Hydraulic
Analysis. [{Insert name of responsible Mapping Partner}]{.mark}shall
summarize the hydrologic analysis for each county in optional Table 1.7
Summary of Hydraulic Analysis.

**Table 1.7** Summary of Hydraulic Analysis

  ------------------ ----------------------- ----------------------------
  **County Name**    **Method**              **Total Miles of New
                                             Detailed or Approximate
                                             Hydraulics**

  []{.mark}          []{.mark}               []{.mark}

  []{.mark}          []{.mark}               []{.mark}

  []{.mark}          []{.mark}               []{.mark}

  []{.mark}          []{.mark}               []{.mark}

  []{.mark}          []{.mark}               []{.mark}
  ------------------ ----------------------- ----------------------------

[Standards]{.underline}: All Hydraulic Analyses work shall be performed
in accordance with the standards specified in Section 5 - Standards.

[Deliverables]{.underline}: In accordance with the G&S, {Insert name of
responsible Mapping Partner} shall make the following products available
to FEMA by uploading the digital data to the MIP so that {Insert name of
Mapping Partner responsible for Independent QA/QC} can access it for an
independent QA/QC review in accordance with the schedule outlined in
Section 6 - Schedule. A metadata file complying with the NFIP Metadata
Profiles Specifications, must accompany the uploaded compliant digital
data. Additionally, the TSDN format described in the G&S must be
delivered in accordance with Section 2 -- Technical and Administrative
Support Data Submittal.

\<Include deliverables specific to Limited Detail Study if proposed\>

\<Add, modify or delete deliverables below, as necessary\>

-   Digital profiles of the 10-, 2-, 1- and 0.2-percent-annual-chance
    water-surface elevations representing existing conditions using the
    FEMA RASPLOT program or similar software;

-   Digital Floodway Data Tables for each flooding source that is
    compatible with the DFIRM database;

-   Digital hydraulic modeling (input and output) files;

-   Digital tables with range of Manning's "n" values;

-   Explanations for unresolved messages from the CHECK-2 or CHECK-RAS
    program, as appropriate;

-   Digital versions of all backup data used in the analyses;

-   Digital versions of draft text for inclusion in the FIS report;

-   Format Hydraulic Database or Data Delivery consistent with the Data
    Capture Standards--in the G&S; and

-   A Summary Report that describes and provides the results of all
    automated or manual QA/QC review steps taken during the preparation
    of the DFIRM as outlined in the approved QA/QC Plan.

-   \<Optional for GIS-based modeling\> For GIS-based modeling,
    deliverables include all input and output data, intermediate data
    processing products, GIS data layers, and final products in the
    format of the DFIRM database structure;

-   \<Optional for Limited Detail modeling\> For Limited Detail Study
    modeling, define the deliverables to be included.

-   Where paper documentation is required by State Law for Professional
    certifications, you may submit the paper in addition to a scanned
    version of the paper for the digital record. Appropriate leverage
    information includes who paid for the data and the amount of data
    used by the Flood Map Project.

**Independent QA/QC Review of Hydraulic Analyses**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

[Scope]{.underline}: {Insert name of responsible Mapping Partner} shall
review the technical, scientific, and other information submitted by
{Insert name of Mapping Partner responsible for Hydraulic Analysis}
under Hydraulic Analysis to ensure that the data and modeling are
consistent with FEMA standards and standard engineering practice, and
are sufficient to revise the FIRM. If {Insert name of responsible
Mapping Partner}utilizes a contractor to perform the QA/QC, the
contractor must be a different contractor than who performed the
original analyses. FEMA may audit or assist in these activities if
deemed to be necessary by the Regional Project Officer. This work shall
include, at a minimum, the activities listed below.

\<Delete or add tasks below, as necessary\>

-   Review the submittal for technical and regulatory adequacy,
    completeness of required information, and supporting data and
    documentation. The technical review is to focus on the following:

    -   Use of acceptable model(s);

    -   Starting water-surface elevations;

    -   Cross-section geometry;

    -   Manning's "n" values and expansion/contraction coefficients;

    -   Bridge and culvert modeling;

    -   Flood discharges;

    -   Regulatory floodway computation methods; and

    -   Tie-in to upstream and downstream non-revised Flood Profiles.

```{=html}
<!-- -->
```
-   Use the CHECK-2 or CHECK-RAS program, as appropriate, to flag
    potential problems and focus review efforts.

-   Maintain records of all contacts, reviews, recommendations, and
    actions and make the data readily available to FEMA.

-   Maintain an archive of all data submitted for hydraulic modeling
    review. (All supporting data must be retained for three years from
    the date a funding recipient submits its final expenditure report to
    FEMA, and once the study is effective all associated data should be
    submitted to the FEMA library); and

-   If data changed during review, then updated deliverables for
    previous tasks will be submitted at this time.

[Standards]{.underline}: All Independent QA/QC work shall be performed
in accordance with the standards specified in Section 5 - Standards.

[Deliverables]{.underline}: In accordance with the G&S, {Insert name of
responsible Mapping Partner} shall make the following products available
to FEMA by uploading the digital data to the MIP. Additionally, the TSDN
format described in the G&S must be delivered in accordance with Section
2 -- Technical and Administrative Support Data Submittal.

This submittal will occur in accordance with the schedule outlined in
Section 6 - Schedule.

\<Add, modify or delete deliverables below, as necessary\>

-   A Summary Report that describes the findings of the independent
    QA/QC review;

-   Recommendations to resolve any problems that are identified during
    the independent QA/QC review; and

-   If the data changed during the Hydrologic and/or Hydraulic Analyses
    QA/QC process, then the updated and verified deliverables from these
    activities will be resubmitted at this time.

**Coastal Flood Hazard Analyses**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

[Scope]{.underline}: {Insert name of responsible Mapping Partner}shall
perform coastal flood hazard analyses for approximately {Insert Number
of Transects} transects along {Insert Number of Miles} miles of
shoreline including the following coastal flooding sources: {Insert
names of flooding source(s) or reference attached list}. These analyses
are to include: {Insert all that apply to this activity (e.g.,
Stillwater Elevations (SWEL) determinations, wave setup, erosion,
overland propagation of wave heights analyses, and wave runup and
Primary Frontal Dune(PFD))}. In addition, {Insert name of responsible
Mapping Partner} shall address all concerns or questions regarding the
Coastal Flood Hazard Analyses that are raised by {Insert name of Mapping
Partner responsible for Independent QA/QC} during the independent QA/QC
review.

\<Optional Paragragh for Levees \> Any flooding sources associated with
a levee that are mapped as providing protection on effective FIRMs, but
will not meet certification requirements for the new FIRMs, will require
revised hydraulic analysis. This revised analysis should be done in
accordance with the G&S*,* PMs 34, 43 and others that may be
appropriate.

\<Add additional details regarding the scope of this task, as
appropriate\>

[Standards]{.underline}: All Coastal Flood Hazard Analyses work shall be
performed in accordance with the standards specified in Section 5 -
Standards.

[Deliverables]{.underline}: In accordance with the G&S, {Insert name of
responsible Mapping Partner} shall make available to FEMA the following
products by uploading the digital data to the MIP so that {Insert name
of Mapping Partner responsible for Independent QA/QC} can access it for
an independent QA/QC review in accordance with the schedule outlined in
Section 6 - Schedule. A metadata file complying with the NFIP Metadata
Profiles Specifications, must accompany the uploaded compliant digital
data. Additionally, the TSDN format described in the G&S must be
delivered in accordance with Section 2 -- Technical and Administrative
Support Data Submittal.

-   Draft digital work maps showing the 1- and 0.2-percent-annual-chance
    floodplain boundaries, BFEs, and flood insurance risk zones;

```{=html}
<!-- -->
```
-   Digital wave envelope profiles for each transect representing the
    1-percent-annual-chance stillwater elevation including setup wave
    crest or runup elevations, location of the heel of the PFD, and
    ground profile conditions including eroded dune profile;

-   Digital versions of draft text for inclusion in the FIS report;

-   Draft work maps showing each transect located accordingly;

-   Digital coastal modeling (input and output files);

-   Digital versions of any other supporting computations;

-   All backup data used in the analyses;

-   Coastal Hydrology Database or Data Delivery consistent with the G&S;
    and

-   A Summary Report that describes and provides the results of all
    automated or manual QA/QC review steps taken during the preparation
    of the DFIRM as outlined in the approved QA/QC Plan.

-   Where paper documentation is required by State Law for Professional
    certifications, you may submit the paper in addition to a scanned
    version of the paper for the digital record.

In addition, {Insert name of responsible Mapping Partner} shall submit a
coastal study technical documentation notebook with all backup data,
description of methodology, and input and output files used in the
analyses and mapping as discussed in the G&S.

**Independent QA/QC Review of Coastal Hazard Analyses**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

[Scope]{.underline}: {Insert name of responsible Mapping Partner}shall
review the technical, scientific, and other information submitted by
{Insert name of Mapping Partner responsible for conducting the
hydrologic analysis} under Coastal Flood Hazard Analyses to ensure that
the data and modeling are consistent with FEMA standards and standard
engineering practice, and are sufficient to prepare the DFIRM. If
{Insert name of responsible Mapping Partner}utilizes a contractor to
perform the QA/QC, the contractor must be a different contractor than
who performed the original analyses. FEMA may audit or assist in these
activities if deemed to be necessary by the Regional Project Officer.
This work is to include, at a minimum, the activities listed below.

\<Delete or add tasks below, as necessary\>

-   Review the submittal for technical and regulatory adequacy,
    completeness of required information, and supporting data and
    documentation. The technical review is to focus on the following:

    -   Use of acceptable models;

    -   Use of appropriate methodology(ies);

    -   Correctly applied methodology(ies)/model(s) including QC of
        input parameters.

    -   Comparison with gage data, if appropriate; and

    -   Comparison with contiguous reaches or flooding sources.

```{=html}
<!-- -->
```
-   Maintain records of all contacts, reviews, recommendations, and
    actions and make the data readily available to FEMA.

-   Maintain an archive of all data submitted for coastal modeling
    review. (All supporting data must be retained for three years from
    the date a funding recipient submits its final expenditure report to
    FEMA, and once the study is effective all associated data should be
    submitted to the FEMA library).

[Standards]{.underline}: All Independent QA/QC work shall be performed
in accordance with the standards specified in Section 5 - Standards.

[Deliverables]{.underline}: In accordance with the G&S, {Insert name of
responsible Mapping Partner} shall make the following products available
to FEMA by uploading the digital data to the MIP. Additionally, the TSDN
format described in the G&S must be delivered in accordance with Section
2 -- Technical and Administrative Support Data Submittal.

This submittal will occur in accordance with the schedule outlined in
Section 6 - Schedule.

\<Add, modify or delete deliverables below, as necessary\>

-   A Summary Report that describes the findings of the independent
    QA/QC review.

-   Recommendations to resolve any problems that are identified during
    the independent QA/QC review.

-   If the data changed during the QA/QC process, then the updated
    deliverables from the Coastal Flood Hazard Analyses will be
    resubmitted at this time.

**Floodplain Mapping**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

**[Scope for Detailed Riverine or Coastal Analysis]{.underline}**:
{Insert name of responsible Mapping Partner}shall delineate the 1- and
0.2-percent-annual-chance floodplain boundaries and the regulatory
floodway boundaries (if required) and any other applicable elements for
the flooding sources for which detailed hydrologic, hydraulic, and/or
coastal analyses were performed. {Insert name of responsible Mapping
Partner}shall incorporate all new or revised hydrologic, hydraulic,
and/or coastal modeling and shall use the topographic data acquired
under Topographic Data Development to delineate the floodplain and
regulatory floodway boundaries on a digital work map.

[**Scope of Redelineation of Detailed Floodplain Boundaries Using
Updated Topographic Data**:]{.underline} {Insert name of responsible
Mapping Partner}shall delineate the 1- and 0.2-percent-annual-chance
floodplain boundaries, regulatory floodway boundaries, and coastal high
hazard zones (if required) for the flooding sources listed earlier in
Table 1.1. {Insert name of responsible Mapping Partner}shall use the
topographic data acquired under Topographic Data Development to
delineate the floodplain and regulatory floodway boundaries, as
appropriate, on a digital work map. If the new topographic data do not
reflect the same hydraulic characteristics as in the effective study,
{Insert name of responsible Mapping Partner}shall evaluate the
topographic data to determine if changes are significant enough to
invalidate the floodplain boundary and regulatory floodway boundary
redelineations. If so, {Insert name of responsible Mapping Partner}shall
contact the FEMA Regional Project Officer, identified in Section 12 --
Points of Contact, with a recommendation.

Coastal redelineation involves the following steps: redelineate the
landward extent of the coastal flooding based on existing Stillwater
elevations and the new topography. All gutters (elevation change lines
between open water and the landward extent of the coastal flooding) need
to be digitized (these lines are not directly related to the topography
so should be digitized directly). If converting between National
Geodetic Vertical Datum (NGVD) and NAVD and the difference is close to
1.0 foot, the elevation can be changed on the map and the gutters will
stay at the same location. If the difference between NGVD and NAVD is
between 0.1 and 0.9 foot, or greater than 1.1 feet, contact FEMA and the
RMC for guidance on how to move the gutters.

If the PFD VE Zone has not been mapped this must also be done during
redelineation. PFD involves using the best available topographic data
and mapping the heel or landward side of the PFD. The VE zone shall then
be extended landward to that line.

**[Scope for Limited Detail Study]{.underline}**: {Describe Scope for
Limited Detail Study}

**[Scope for Refinement or Creation of Zone A]{.underline}**: {Insert
name of responsible Mapping Partner}shall delineate the
1-percent-annual-chance floodplain boundaries for the flooding sources
listed earlier in Table 1.1 or in the subsequent Scoping Report. {Insert
name of responsible Mapping Partner}shall use existing topographic data
or the topographic data acquired under Topographic Data Development to
delineate the floodplain boundaries on a digital work map. {Insert name
of responsible Mapping Partner} may expand on the approaches for
analyzing Zone A areas outlined in G&S and in FEMA 265, *Managing
Floodplain Development in Approximate Zone A Areas* (April 1995), and/or
develop new approaches. Such approaches must be coordinated with and
approved by the FEMA Regional Project Officer identified in Section 12
-- Points of Contact, before analysis and mapping begin.

**[Scope for Non-revised Areas]{.underline}**: For all flooding sources
except those segments for which updated flood data will be developed,
{Insert name of responsible Mapping Partner}shall convert the
information shown on the effective FIRM and FBFM panels for all
incorporated and unincorporated areas of {Insert County name} County to
digital format in conformance with FEMA DFIRM specifications. {Insert
name of responsible Mapping Partner}shall use the acquired base map for
the conversion. {Insert name of responsible Mapping Partner}shall
digitize {insert number of panels} FIRM panels and {insert number of
panels} FBFM panels. {Insert name of responsible Mapping Partner}shall
not digitize the flood theme for those segments of flooding sources for
which updated flood data will be developed. It is estimated that {insert
number of panels} county-wide DFIRM panels will be produced by {Insert
name of responsible Mapping Partner}.

**[Scope for Merging Revised and Non-Revised Information]{.underline}**:
Upon completion of the floodplain mapping activities for the revised and
non-revised areas, {Insert name of responsible Mapping Partner}shall
merge the digital floodplain data into a single, updated DFIRM. This
work is to include tie-in of flood hazard information for areas that
were not studied as part of the Flood Map Project documented in this
{MAS/SOW}. {Insert name of responsible Mapping Partner}also shall tie in
the revised and non-revised Flood Profiles, floodplain boundaries,
coastal gutters, and regulatory floodway boundaries with contiguous
communities that were not studied as part of the Flood Map Project
documented in this {MAS/SOW}. {Insert name of responsible Mapping
Partner} shall coordinate with FEMA and any additional Mapping Partners
responsible for other components of Floodplain Mapping, as necessary, to
resolve any potential tie-in issues.

{Insert name of responsible Mapping Partner} shall incorporate the
results of all effective Letters of Map Change (LOMCs) for all affected
communities on the DFIRM. Also, {Insert name of responsible Mapping
Partner}shall address all concerns or questions regarding Floodplain
Mapping that are raised by {Insert name of Mapping Partner responsible
for Independent QA/QC} during the independent QA/QC review.

\<Add additional details regarding the scope of these activities, as
appropriate\>

[Standards]{.underline}: All Floodplain Mapping work shall be performed
in accordance with the standards specified in Section 5 - Standards.
Mapping quality standards must be consistent with PM 38, dated October
17, 2007. {Insert name of responsible Mapping Partner} will perform
self-certification audits for the Floodplain Boundary Standards, as
described in PM 38 and all subsequent revisions, for all flood hazard
areas. {Insert name of responsible Mapping Partner} may expand on the
approaches for analyzing Zone A areas outlined in G&S and in FEMA 265,
*Managing Floodplain Development in Approximate Zone A Areas* (April
1995), and/or develop new approaches. Such approaches must be
coordinated with and approved by the FEMA Regional Project Officer
before analysis and mapping begin.

The {Insert name of responsible Mapping Partner} assigned the floodplain
mapping task will complete all activities pertaining to levees in
accordance with the G&S*,* PMs 34, 43 and others that may be
appropriate.

[Deliverables]{.underline}: In accordance with the G&S, and upon
completion of floodplain mapping for {Insert flooding sources; specify a
subset of all flooding sources being remapped and/or panels including
digitization of non-revised areas}, {Insert name of responsible Mapping
Partner}shall make the following products available to FEMA by uploading
the digital data to the MIP so that {Insert name of Mapping Partner
responsible for Independent QA/QC} can access it for the independent
QA/QC review in accordance with the schedule outlined in Section 6 --
Schedule. A metadata file complying with the NFIP Metadata Profiles
Specifications, must accompany the compliant digital data. Additionally,
the TSDN format described in the G&S must be delivered in accordance
with Section 2 -- Technical and Administrative Support Data Submittal.
The mapping for the remaining flooding sources including any non-revised
digital panels and all merged revised and non-revised floodplain mapping
data is to be submitted for the Independent QA/QC review at the
completion of this activity.

This submittal will occur in accordance with the schedule outlined in
Section 6 - Schedule.

\<Add, modify or delete deliverables below, as necessary\>

-   Digital work map showing the Coastal High Hazard Area (V zone)
    delineated along {Indicate Atlantic Ocean, Gulf of Mexico, Great
    Lakes, Pacific Ocean, or other} shorelines, transect locations, 1-
    and 0.2-percent-annual-chance floodplain boundary delineations,
    regulatory floodway boundary delineations, cross sections, BFEs,
    flood insurance risk zone designation labels, gutters, PFD, and all
    applicable base map features;

-   Draft DFIRM database prepared in accordance with the requirements in
    G&S;

-   Digital versions of input and output for any computer programs that
    were used consistent with the DCS--in the G&S;

```{=html}
<!-- -->
```
-   A Summary Report that describes and provides the results of all
    automated or manual QA/QC review steps taken during the preparation
    of the DFIRM as outlined in the approved QA/QC Plan;

```{=html}
<!-- -->
```
-   Any backup or supplemental information including supporting
    calculations and assumptions used in the mapping required for the
    independent QA/QC review of Hydrologic, Coastal and /or Hydraulic
    Analyses and Floodplain Mapping consistent with the DCS--in the G&S;

-   An explanation for the use of existing topography for the studied
    reaches, if appropriate.

```{=html}
<!-- -->
```
-   Written summary of the analysis methodologies;

```{=html}
<!-- -->
```
-   Digital versions of draft FIS report, Floodway Data Tables and
    updated profiles including all profiles and tables converted
    appropriate datum, as well as any other necessary items for the
    finalization of the preliminary FIS;

```{=html}
<!-- -->
```
-   If automated GIS-based models are applied, all input data, output
    data, intermediate data processing products, and GIS data layers
    shall be submitted consistent with the DCS--in the G&S;

-   Where paper documentation is required by State Law for Professional
    certifications, you may submit the paper in addition to a scanned
    version of the paper for the digital record.

**Independent QA/QC Review of Floodplain Mapping**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

[Scope]{.underline}: {Insert name of responsible Mapping Partner} shall
review the floodplain mapping submitted by {Insert name(s) of Mapping
Partner(s) responsible for Floodplain Mapping} under Floodplain Mapping
to ensure that the results of the analyses performed are accurately
represented, the redelineation of existing data on new, updated
topography is appropriate, and to ensure that the new DFIRM panels
accurately represent the information shown on the effective FIRMs and
FBFMs for the unrevised areas that are mapped. If {Insert name of
responsible Mapping Partner}utilizes a contractor to perform the QA/QC,
the contractor must be a different contractor than who performed the
original floodplain mapping. FEMA may audit or assist in these
activities if deemed to be necessary by the Regional Project Officer.
This work shall include, at a minimum, the activities listed below.

\<Add, modify or delete tasks below, as necessary\>

-   Review the Summary of Stillwater Elevations and Transect Data tables
    for agreement with the coastal modeling results.

-   Review the coastal transects for proper location and orientation on
    the work maps and agreement with the Transect Descriptions table.
    Ensure that the transects on the work maps extend to the inland
    limit of the coastal modeling results used for mapping.

-   Review the cross sections for proper location and orientation on the
    work map and agreement with the Floodway Data Table.

-   Review the BFEs and coastal flood zones (both Zones VE and Zones AE)
    shown on the work map for proper location and agreement with the
    results of the coastal modeling.

```{=html}
<!-- -->
```
-   Review the regulatory floodway widths for agreement with the widths
    shown in the Floodway Data Table and the results of the hydraulic
    modeling.

-   Review the PFD and Zone VE/Zone AE boundary delineations to ensure
    that the PFD delineation is coincident with, or seaward of, the Zone
    VE/Zone AE boundary.

-   Review the floodplain widths at cross sections as shown on the work
    maps to ensure the data matches the Floodway Data Table.

-   Review the floodplain boundaries as shown on the work maps to ensure
    the data matches the Flood Profiles.

-   For non-revised floodplain areas, the 1- and
    0.2-percent-annual-chance floodplain boundaries agree with the
    floodplain boundaries shown on the FIRM, the contour lines, other
    topographic information, and planimetric information shown on the
    DFIRM base.

-   Road and floodplain relationships are maintained for all unrevised
    areas.

-   Review the flood insurance risk zones as shown on the work maps to
    ensure the data are labeled properly.

-   Review the DFIRM mapping files to ensure the data were prepared in
    accordance with the requirements in G&S.

-   Review the metadata files to ensure the data includes all required
    information shown in the NFIP Metadata Profiles Specifications.

\<Add, modify or delete tasks below, as necessary\>

[Standards]{.underline}: All Independent QA/QC work shall be performed
in accordance with the standards specified in Section 5 - Standards.

[Deliverables]{.underline}: In accordance with the G&S, {Insert name of
responsible Mapping Partner} shall make the following products available
to FEMA by uploading the digital data to MIP. Additionally, the TSDN
format described in the G&S must be delivered in accordance with Section
2 -- Technical and Administrative Support Data Submittal.

This submittal will occur in accordance with the schedule outlined in
Section 6 - Schedule.

\<Add, modify or delete deliverables below, as necessary\>

-   A Summary Report that describes the findings of the QA/QC review,
    noting any deficiencies in or agreeing with the mapping results;

-   Recommendations to resolve any problems that are identified during
    the independent QA/QC review;

-   An annotated work map with all questions and/or concerns indicated,
    if necessary; and

-   If data changed during review, then updated deliverables for
    previous tasks will be submitted at this time.

**Develop Draft DFIRM Database**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

[Scope]{.underline}:  {Insert name of responsible Mapping Partner} shall
prepare the database in accordance with G&S*,* for upload to the MIP. 
{Insert name of responsible Mapping Partner} shall coordinate with
appropriate Mapping Partners, as necessary, to resolve any problems that
are identified during development of the DFIRM Database. 

[Standards:]{.underline}  All DFIRM Database work shall be performed in
accordance with the standards specified in Section 5 - Standards.

[Deliverables]{.underline}:  In accordance with G&S, {Insert name of
responsible Mapping Partner} shall make the following products available
to FEMA by uploading the digital data to the MIP.  Additionally, the
Technical Support Data Notebook format described in G&S must be
delivered in accordance with Section 2 -- Technical and Administrative
Support Data Submittal.

-   DFIRM database files prepared in accordance with the requirements in
    G&S and in the required format(s) and

-   A metadata file complying with the FEMA NFIP Metadata Profile
    Specifications.

**Produce Preliminary Map Products**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

[Scope]{.underline}: {Insert name of responsible Mapping Partner}shall
apply the final FEMA DFIRM graphic and database specifications to the
DFIRM files produced under Floodplain Mapping. This work shall include
adding all required annotation, line pattern, area shading, and map
collar information (e.g., map borders, title blocks, legends, notes to
user). {Insert name of responsible Mapping Partner}will be preparing the
database for this project in the {Insert Standard or Enhanced} format.
The Enhanced database is the preferred product as it is prepared to
incorporate a full GIS database product for this study. The database
shall be produced in accordance with the G&S. {Insert name of
responsible Mapping Partner} shall coordinate with those Mapping
Partners responsible for Floodplain Mapping and/or Redelineation, as
necessary, to resolve any problems that are identified during
development of the DFIRM Database and graphics.

\<Add additional details regarding the scope of this task, as
appropriate\>

*Preliminary Summary of Map Actions (SOMA) Preparation:* The {Insert
name of responsible Mapping Partner}shall prepare Preliminary SOMAs for
all affected communities, if appropriate. The SOMA shall list pertinent
information regarding LOMCs that will be affected by the issuance of the
DFIRM (i.e., superseded, incorporated, revalidated).

[Standards]{.underline}: All DFIRM Database work shall be performed in
accordance with the standards specified in Section 5 - Standards. All
work must pass the automated and visual "National QA/QC" reviews prior
to the distribution of the preliminary copies of the DFIRM and FIS
report and the Preliminary SOMA.

[Deliverables]{.underline}: In accordance with the G&S, {Insert name of
responsible Mapping Partner} shall make the following products available
to FEMA by uploading the digital data to the MIP. A metadata file
complying with the NFIP Metadata Profiles Specifications, must accompany
the compliant digital data. Additionally, the TSDN format described in
the G&S must be delivered in accordance with Section 2 -- Technical and
Administrative Support Data Submittal.

This submittal will occur in accordance with the schedule outlined in
Section 6 - Schedule.

\<Add, modify or delete deliverables below, as necessary\>

-   Preliminary DFIRM database or revised Preliminary DFIRM database
    prepared in accordance with the requirements in G&S;

-   FIS Report and the Preliminary SOMA prepared using the SOMA Tool on
    the MIP.

-   Complete set of plots of DFIRM panels showing all detailed flood
    hazard information at a suitable scale; and

-   A Summary Report that describes and provides the results of all
    automated or manual QA/QC review steps taken during the preparation
    of the DFIRM as outlined in approved QA/QC Plan.

-   Passing Quality Review report

> **Independent QA/QC Review of Produce Preliminary Map Products**

[Responsible Mapping Partner]{.underline}: {Insert name of responsible
Mapping Partner}

[Scope]{.underline}: Upon completion of the floodplain mapping and
redelineation activities, {Insert name of responsible Mapping
Partner}shall review the DFIRM spatial database to determine if it meets
current FEMA database specifications. In addition, {Insert name of
responsible Mapping Partner}shall review the DFIRM to ensure it meets
current FEMA graphic specifications. {Insert name of responsible Mapping
Partner} shall coordinate with other Mapping Partners, as necessary, to
resolve any problems identified during this QA/QC review. If {Insert
name of responsible Mapping Partner}utilizes a contractor to perform the
QA/QC, the contractor must be a different contractor than who performed
the original analyses. FEMA may audit or assist in these activities if
deemed to be necessary by the Regional Project Officer. This work shall
ensure that the requirements below are met.

-   All required DFIRM features are accurately and legibly labeled and
    following the examples shown in the FEMA DFIRM specifications. This
    includes all flood insurance risk zones, BFEs, gutters, cross
    sections, transects, studied streams and shorelines, mapped
    political entities, and all roads within and adjacent to the
    1‑percent-annual-chance floodplains.

-   All DFIRM features are correctly symbolized with the appropriate
    symbol, line pattern, or area shading and follow the requirements in
    G&S.

-   All map collar information is complete, correct, and follows the
    requirements specified in G&S.

-   Preliminary DFIRM database is in a GIS file and database format as
    specified in FEMA's G&S, and conform to those specifications for
    content and attribution.

-   DFIRM database files are in one of the database formats specified in
    FEMA's G&S, and conform to those specifications for content and
    attribution.

\<Add additional details regarding the scope of this task, as
appropriate\>

[Standards]{.underline}: All DFIRM Database Development work shall be
performed in accordance with the standards specified in Section 5 -
Standards.

[Deliverables]{.underline}: In accordance with the G&S, {Insert name of
responsible Mapping Partner} shall make the following products available
to FEMA by uploading the digital data to the MIP. Additionally, the TSDN
format described in the G&S must be delivered in accordance with Section
2 -- Technical and Administrative Support Data Submittal.

This submittal will occur in accordance with the schedule outlined in
Section 6 -- Schedule.

\<Add, modify or delete deliverables below, as necessary\>

-   A Summary Report that describes the findings of the QA/QC review
    noting any deficiencies in or agreeing with the mapping results and
    the results of all automated or manual QA/QC steps taken during the
    independent QA/QC review;

-   Recommendations to resolve any problems that are identified during
    the independent QA/QC review; and

-   An annotated copy of the DFIRM with all questions and/or concerns
    indicated, if necessary.

-   If the data changed during the QA/QC process, then the updated
    deliverables from Floodplain Mapping and Redelineation will be
    resubmitted at this time.

**Distribute Preliminary Map Products**

[Responsible Mapping Partners]{.underline}: {Insert name of responsible
Mapping Partner(s)}

[Scope]{.underline}: Preliminary Map Products consists of the final
preparation, review, and distribution of the Preliminary copies of the
DFIRM and FIS report and the Preliminary SOMA for community officials
and the general public review and comment. FEMA may audit or assist in
these activities if deemed to be necessary by the Regional Project
Officer. The activities to be performed are summarized below.

\<Add, modify or delete tasks below, as necessary\>

*Preliminary Transmittal Letter Preparation*: The {Insert name of
responsible Mapping Partner}shall prepare letters and transmit the
Preliminary copies of the DFIRM and FIS report and related enclosures to
all affected communities, all other Project Team members, the State NFIP
Coordinator, the FEMA Regional Office, and others as directed by FEMA.
This letter may be prepared for FEMA only or for signature by FEMA and
{Insert name of responsible Mapping Partner}.

*Distribution of Preliminary DFIRM and FIS Report:* The {Insert name of
responsible Mapping Partner}shall distribute the Preliminary copies of
the DFIRM and FIS report to all affected communities, all other Project
Team members, the State NFIP Coordinator, the FEMA Regional Office, and
others as directed by FEMA.

*News Release Preparation::* The {Insert name of responsible Mapping
Partner}shall use the BFEs on the Web tool in accordance with PM 44 to
create BFE notices for studies that result in new or modified BFEs. The
{Insert name of responsible Mapping Partner}shall prepare the BFE
determination letters as well as the news release notifications of BFE
changes for all affected communities. The {Insert name of responsible
Mapping Partner}shall perform QA/QC reviews of the notices for accuracy
and compliance with FEMA format requirements. The {Insert name of
responsible Mapping Partner}shall file the notifications for later
submittal to FEMA for review.

[Standards]{.underline}: All Preliminary Map Products work shall be
performed in accordance with the standards specified in Section 5 -
Standards. Mapping quality standards must be consistent with PM 38,
dated October 17, 2007. Preliminary DFIRM Maps shall pass the QRs, as
outlined in PM 42, before this activity is completed and the maps are
issued Preliminary.

[Deliverables]{.underline}: In accordance with the G&S, {Insert name of
responsible Mapping Partner} shall make the appropriate deliverables
available to FEMA by uploading the digital data to the MIP.
Additionally, the TSDN format described in the G&S must be delivered in
accordance with Section 2 -- Technical and Administrative Support Data
Submittal.

This submittal will occur in accordance with the schedule outlined in
Section 6 - Schedule.

Preliminary transmittal letters shall be prepared and transmitted. These
letters and any additional letters requested by FEMA shall be prepared
in accordance with the current version of the FEMA *Document Control
Procedures Manual* and in conjunction with Guidance provided by the
Region and/or its contractor*.*

-   Preliminary copies of the DFIRM and FIS report, including all
    updated data tables and Flood Profiles shall be mailed to the Chief
    Executive Officer (CEO) and floodplain administrator of each
    affected community, all other Project Team members, the State NFIP
    Coordinator, the FEMA Regional Office, and others as directed by
    FEMA.

-   Preliminary SOMAs, prepared in accordance with FEMA requirements,
    shall be provided as appropriate.

-   A Summary Report that describes and provides the results of all
    automated or manual QA/QC review steps taken during the final
    preparation of the preliminary DFIRM shall be provided as outlined
    in the approved QA/QC Plan.

-   {Insert name of responsible Mapping Partner}will submit a summary of
    outreach activities and any changes made in the outreach approach
    based on the actual implementation.

**Post-Preliminary Processing**

[Responsible Mapping Partners]{.underline}: {Insert name of responsible
Mapping Partner}and FEMA

[Scope]{.underline}: Post-Preliminary Processing includes coordination
with FEMA and the Community to schedule a Community Meeting(s) for
review of the Preliminary DFIRM, if required. This activity consists of
finalizing the DFIRM and FIS report after the Preliminary copies of the
DFIRM and FIS report have been issued to community officials and the
public for review and comment. FEMA may audit or assist in these
activities if deemed to be necessary by the Regional Project Officer.
The activities to be performed are summarized below.

\<Add, modify or delete tasks below, as necessary\>

*Community Coordination Meeting*: If a community coordination meeting is
required it is recommended that it be held within 60 days of the
issuance of the Preliminary DFIRM and, {Insert name of responsible
Mapping Partner}shall arrange for and verify that the following
activities are completed:

-   Establish invitee list,

-   Schedule meeting date and place,

-   Complete and Distribute Meeting Notice/Letter,

-   Record Meeting Minutes, and

-   Identify any/all communities with BFE changes for required appeal
    period.

*Initiation of Statutory 90-Day Appeal Period:* When required, upon
completion of a 30-day community comment period and/or final
coordination meeting with the affected communities, FEMA and/or {Insert
name of responsible Mapping Partner(s)}shall arrange for and verify that
the following activities are completed in accordance with the current
version of the FEMA G&S, appropriate PMs and Document Control Procedures
Manual:

-   Proposed BFE determination letters are sent to the community CEOs
    and floodplain administrators.

-   Ensure that news release notifications of BFE changes are published
    in prominent newspapers with local circulation in accordance with 44
    CFR.

-   The {Insert name(s) of responsible Mapping Partner(s)}shall prepare
    the appropriate notices (Proposed Rules) that are to be published in
    the *Federal Register*. The {Insert name(s) of responsible Mapping
    Partner(s)}shall then deliver those notices to FEMA for publication.

-   When {Insert name(s) of responsible Mapping Partner(s)}holds public
    meetings to present and discuss the results of this Flood Map
    Project, FEMA may attend the meetings and assist where possible, if
    requested.

*Resolution of Appeals and Protests:* {Insert name(s) of responsible
Mapping Partner(s)}shall review and resolve appeals and protests
received during the 90-day appeal period. For each appeal and protest,
the following activities shall be conducted as appropriate:

-   Initial processing and acknowledgment of submittal;

-   Technical review of submittal;

-   Preparation of letter(s) requesting additional supporting data;

-   Performance of revised analyses; and

-   Preparation of a draft resolution letter for signature with FEMA and
    revised DFIRM and FIS report materials for FEMA review.

{Insert name(s) of responsible Mapping Partner(s)}shall mail all
associated correspondence upon authorization by FEMA.

*Preparation of Special Correspondence:* {Insert name(s) of responsible
Mapping Partner(s)}shall support FEMA in responding to comments not
received within the 90-day appeal period (referred to as "special
correspondence") including drafting responses for FEMA review when
appropriate and finalizing responses for co-signature. {Insert name(s)
of responsible Mapping Partner(s)}also shall mail the final
correspondence (and enclosures, if appropriate) and distribute
appropriate copies of the correspondence and enclosures upon receipt of
authorization from FEMA.

*Revision of FIRM and FIS Report:* If necessary, {Insert name(s) of
responsible Mapping Partner(s)}shall work together with FEMA to revise
the DFIRM and FIS report and shall distribute revised Preliminary copies
of the DFIRM and FIS report to the CEO and floodplain administrator of
each affected community, all other Project Team members, the State NFIP
Coordinator, the FEMA Regional Office, and others as directed by FEMA.

*Final SOMA Preparation:* {Insert name(s) of responsible Mapping
Partner(s)}shall prepare Final SOMAs for the affected communities with
assistance from FEMA, as appropriate.

*Processing of Letter of Final Determination:* The {Insert name(s) of
responsible Mapping Partner(s)}shall work with FEMA to establish the
effective date for the DFIRM and FIS report, and shall prepare Letters
of Final Determination (LFDs) for each affected community for FEMA
review in coordination with the Region and its contractor, and in
accordance with the FEMA *Document Control Procedures Manual*. FEMA or
its designated contractor shall mail the final signed LFDs and
enclosures and distribute appropriate copies of the signed LFDs. All
work must pass the automated and visual "National QA/QC" reviews and
review of LFD prior to the distribution of the LFD.

-   The {Insert name(s) of responsible Mapping Partner(s)}shall prepare
    the appropriate notices (Final Rules) that are to be published in
    the *Federal Register*. The {Insert name(s) of responsible Mapping
    Partner(s)}shall then deliver those notices to FEMA for publication.

*Processing of Final DFIRM and FIS Report for Printing:* {Insert name(s)
of responsible Mapping Partner(s)} shall prepare final reproduction
materials for the DFIRM and FIS report and provide these materials to
{Insert name of FEMA, NSP or MSC} in accordance with PM 42 for printing
by the United States Government Printing Office. {Insert name(s) of
responsible Mapping Partner(s)}shall also prepare the appropriate
paperwork to accompany the DFIRM and FIS report (including Print
Processing Worksheet, Printing Requisition Forms, and Community Map
Actions Form) and transmittal letters to the community CEOs.

*Revalidation Letter Processing*: {Insert name(s) of responsible Mapping
Partner(s)}shall prepare and distribute letters for FEMA signature to
the community CEOs and floodplain administrators to notify the affected
communities about LOMCs for which determinations will remain in effect
after the DFIRM and FIS report become effective.

*Archiving Data:* {Insert name(s) of responsible Mapping
Partner(s)}shall ensure that technical and administrative support data
are packaged in the FEMA required format and stored properly in the
library archives until transmitted to the FEMA Engineering Study Data
Package Facility. In addition, the {Insert name(s) of responsible
Mapping Partner(s)}will maintain copies of all data for a period of no
less than three years.

[Standards]{.underline}: All Post Preliminary DFIRM work shall be
performed in accordance with the standards specified in Section 5 -
Standards.

[Deliverables]{.underline}: In accordance with the G&S, {Insert name of
responsible Mapping Partner} shall make the following products available
to FEMA by uploading the digital data to the MIP. A metadata file
complying with the NFIP Metadata Profiles Specifications, must accompany
the compliant digital data. Additionally, the TSDN format described in
the G&S must be delivered in accordance with Section 2 -- Technical and
Administrative Support Data Submittal.

This submittal will occur in accordance with the schedule outlined in
Section 6 - Schedule.

\<Add, modify or delete deliverables below, as necessary\>

-   Documentation that the news releases were published in accordance
    with FEMA requirements;

-   Documentation that the appropriate *Federal Register* notices
    (Proposed and Final Rules) were published in accordance with FEMA
    requirements;

-   Draft and final Special Correspondence (and all associated
    enclosures, backup data, and other related information) for FEMA
    review and signature, as appropriate;

-   Draft and final Appeal and Protest acknowledgment, additional data,
    and resolution letters (and all associated enclosures, backup data,
    and other related information) for FEMA review and signature, as
    appropriate;

-   Draft and final LFDs (and all associated enclosures, backup data,
    and other related information) for FEMA review and signature;

-   DFIRM negatives and final FIS report materials including all updated
    data tables and Flood Profiles;

-   Paperwork for the final DFIRM and FIS report materials;

-   Transmittal letters for the printed DFIRM and FIS report;

-   LOMC Revalidation Letters, if appropriate;

-   Completed, organized, and archived technical and administrative
    support data; and

-   Completed, organized, and archived case files and flood elevation
    dockets.

## SECTION 2---Technical and Administrative Support Data Submittal  {#section-2technical-and-administrative-support-data-submittal .unnumbered}

#### The Project Team members for this Flood Map Project that have responsibilities for activities included in this **{MAS/SOW}** shall comply with the data submittal requirements summarized below. {#the-project-team-members-for-this-flood-map-project-that-have-responsibilities-for-activities-included-in-this-massow-shall-comply-with-the-data-submittal-requirements-summarized-below. .unnumbered}

All supporting documentation for the activities in this MAS/SOW shall be
submitted in the TSDN format in accordance with the FEMA G&S. Table 2.1
Mapping Activities and Applicable TSDN Sections indicates the sections
of the TSDN that apply to each mapping activity.

If any issues arise that could affect the completion of an activity
within the proposed scope or budget, the responsible Mapping Partner
shall complete a Special Problem Report (SPR) as soon as possible after
the issue is identified and submitted to FEMA. The SPR is to describe
the issue and propose possible resolutions. (For additional information
on SPRs, refer to the G&S.)

\<Include only those tasks listed below that apply to this Flood Mapping
Project in Table 2.1.\>

###### Table 2.1- Mapping Activities and Applicable TSDN Sections {#table-2.1--mapping-activities-and-applicable-tsdn-sections .unnumbered}

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 8%" />
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 6%" />
<col style="width: 7%" />
<col style="width: 6%" />
</colgroup>
<thead>
<tr class="header">
<th rowspan="2"><blockquote>
<p><strong>TSDN Section</strong></p>
</blockquote></th>
<th colspan="14"><h6 id="mapping-activities"> Mapping
Activities</h6></th>
</tr>
<tr class="odd">
<th><blockquote>
<p><strong>Scoping</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Field Survey</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Topo Data</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>QA/QC of Topo</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Base Map</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Hydrology/ Coastal</strong></p>
</blockquote></th>
<th><strong>QA/QC of Hydrology/ Coastal</strong></th>
<th><blockquote>
<p><strong>Hydraulic Analysis</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>QA/QC of Hydraulics</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Flood-plain Mapping (and Re-delineation)</strong></p>
<p><strong>g</strong></p>
</blockquote></th>
<th><strong>QA/QC of FP Mapping</strong></th>
<th><blockquote>
<p><strong>DFIRM Database</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Preliminary Map Products</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Post-Preliminary</strong></p>
</blockquote></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><strong>General Documenta-tion</strong></td>
<td colspan="14"></td>
</tr>
<tr class="even">
<td>Special Problem Reports</td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
</tr>
<tr class="odd">
<td>Telephone Conversation Reports</td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
</tr>
<tr class="even">
<td>Meeting Minutes/ Reports</td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
</tr>
<tr class="odd">
<td>General Correspon-dence</td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
</tr>
<tr class="even">
<td><strong>Engineering Analyses</strong></td>
<td colspan="14"></td>
</tr>
<tr class="odd">
<td>Hydrologic Analyses</td>
<td></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Hydraulic Analyses</td>
<td></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Key to Cross-Section Labeling</td>
<td></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Key to Transect Labeling</td>
<td></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><strong>Draft FIS Report</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><strong>Mapping Information</strong></td>
<td><strong>X</strong></td>
<td></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
</tr>
<tr class="odd">
<td><strong>Miscellan-eous Reference Information</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
</tr>
</tbody>
</table>

######  {#section-20 .unnumbered}

## [SECTION 3---PERIOD OF PERFORMANCE (for CTPs)]{.mark} {#section-3period-of-performance-for-ctps .unnumbered}

The mapping activities outlined in this MAS will be completed as
specified in the Agreement Articles of the Cooperative Agreement. The
Mapping Activities may be terminated at the option of FEMA or {Insert
CTP Name}{Insert Name of CTP} in accordance with the provisions of the
Partnership Agreement dated {Insert Partnership Agreement Date}. If
these mapping activities are terminated, all products produced to date
must be returned and updated into the MIP and the remaining funds from
uncompleted activities, provided by FEMA for this MAS, will be returned
to FEMA.

**OR**

## [SECTION 3---PERIOD OF PERFORMANCE (for IDIQ or OFA)]{.mark} {#section-3period-of-performance-for-idiq-or-ofa .unnumbered}

The mapping activities outlined in this SOW will be completed as
specified in the {Insert Contract and/or Task order no.}.

## [SECTION 4---Funding/LEVERAGE (For CtP, OFA and/or Community)]{.mark} {#section-4fundingleverage-for-ctp-ofa-andor-community .unnumbered}

FEMA is providing funding, in the amount of {Insert amount of funding
provided by FEMA through a Cooperative Agreement}}, to {Insert CTP
name}for the completion of this Flood Map Project. {Insert CTP name}
shall provide any additional resources required to complete the assigned
activities for this Flood Map Project. During the scoping process,
additional needs may be identified. Activities associated with any
additional needs would be performed based on availability of additional
funds. The leverage listed below includes in-kind services and blue book
values for acquired information (i.e. base map data, hydrologic and
hydraulic analyses, etc.). These values should also be reported in the
MIP by the appropriate task owner. The current Blue Book is dated
November 2006 and can be downloaded from FEMA's Information Resource
Library at http://www.fema.gov/library/index.jsp. {Insert name of
responsible Mapping Partner} shall complete Table 4.1 Contribution and
Leverage

Table 4.1Contribution and Leverage

  ------------------------ ---------------- ---------------- ------------ -----------
  **Project Task**         **FEMA           **Partner        **% Partner  **Total
                           Contribution**   Contribution**   Leverage**   Project
                                                                          Cost**

  \[Insert Task name here}                                                

                                                                          

  TOTAL FUNDING AMOUNTS    \$               \$               \%           \$
  ------------------------ ---------------- ---------------- ------------ -----------

## Leverage dollars or units shall be entered as applicable within the Manage Data Development task in the MIP workflow. {#leverage-dollars-or-units-shall-be-entered-as-applicable-within-the-manage-data-development-task-in-the-mip-workflow. .unnumbered}

##  {#section-21 .unnumbered}

[OR]{.mark}

## [SECTION 4---Funding (For IDIQ)]{.mark} {#section-4funding-for-idiq .unnumbered}

FEMA is providing funding, in the amount of {Insert amount of funding
provided by FEMA through an IDIQ Contract and/or Task Order}, to {Insert
name of responsible Mapping Partner} for the completion of this Flood
Map Project.

## SECTION 5---STANDARDS {#section-5standards .unnumbered}

The standards relevant to this MAS are provided in Tables 5-1 Applicable
Standards for Project Activities and 5-2 Project Activities and
Applicable Portions of FEMA Guidelines and Specifications. Information
on the correct volume and appendix of the G&S to be referenced for each
mapping activity are summarized in Table 5-2 for convenience. However,
all mapping partners working on a Flood Map Project are responsible for
complying with all appropriate requirements in FEMA's G&S including the
[Final Draft Guidelines for Coastal Flood Hazard Analysis and Mapping
for the Pacific Coast of the United States]{.underline} and [Atlantic
Ocean and Gulf of Mexico Coastal Guidelines Update Final
Draft]{.underline}, collectively referred to as "Coastal Guidelines
Updates"; and related PMs published by FEMA as of the date of this
agreement.

These guidelines may be downloaded from the FEMA Flood Hazard Mapping
website at http://www.fema.gov/plan/prevent/fhm/dl_cgs.shtm. The
Geospatial Data Coordination Policy and the Geospatial Data Coordination
Implementation Guide are located at https://hazards.fema.gov under
"Tools & Links."

**Table 5-1. Applicable Standards for Project Activities**

<table>
<colgroup>
<col style="width: 26%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 3%" />
</colgroup>
<thead>
<tr class="header">
<th></th>
<th colspan="17"><strong>Activities</strong></th>
</tr>
<tr class="odd">
<th><strong>Applicable Standards</strong></th>
<th><blockquote>
<p><strong>Scoping</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Field Survey</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Topo Data</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>QA/QC Topo Data</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Base Map</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Coastal</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>QA/QC Coastal</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Hydrology</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>QA/QC Hydrology</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Hydraulic Analysis</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>QA/QC of Hydraulic Analysis</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Floodplain Mapping (inc. Redelineation</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>QA/Qc Flood-plain Mapping</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>DFIRM Dbase</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>QA/QC DFIRM Database</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Preliminary Map Products</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Post-Preliminary Processing</strong></p>
</blockquote></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><em>Guidelines and Specifications for Flood Hazard Mapping Partners
and Procedure Memorandums</em></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
</tr>
<tr class="even">
<td>FEMA’s Geospatial Data Coordination Policy</td>
<td><strong>X</strong></td>
<td></td>
<td><strong>X</strong></td>
<td></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>FEMA’s Geospatial Data Coordination Implementation Guide</td>
<td><strong>X</strong></td>
<td></td>
<td><strong>X</strong></td>
<td></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Engineer Manual 1110-2-1003, <em>Hydrographic Surveys</em> (USACE),
January 1, 2002</td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>“Numerical Models Accepted by FEMA for NFIP Usage,” Updated April
2003</td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>NFIP Metadata Profile Specifications</td>
<td><strong>X</strong></td>
<td></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
</tr>
<tr class="odd">
<td><em>Document Control Procedures Manual</em></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
</tr>
<tr class="even">
<td><em>44 Code of Federal Regulations Parts 65, 66 and 67</em></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
<td><strong>X</strong></td>
</tr>
</tbody>
</table>

Table 5-2. Project Activities and Applicable Portions of FEMA Guidelines
and Specifications

+-------------------------------+--------------------------------------+
| **Activity Description**      | **Applicable Volume,                 |
|                               | Section/Subsection, and Appendix**   |
+===============================+======================================+
| Scoping                       | Volume 1                             |
+-------------------------------+--------------------------------------+
|                               | Appendix I                           |
+-------------------------------+--------------------------------------+
|                               | Scoping Report document              |
+-------------------------------+--------------------------------------+
|                               | 44 Code of Federal Regulations Part  |
|                               | 66 and 67                            |
+-------------------------------+--------------------------------------+
| Outreach                      | Volume 1                             |
+-------------------------------+--------------------------------------+
|                               | Appendix I                           |
+-------------------------------+--------------------------------------+
| Field Survey                  | Volume 1                             |
+-------------------------------+--------------------------------------+
|                               | Appendices A, B, C, F, and M         |
+-------------------------------+--------------------------------------+
| Topographic Data Development  | Volume 1,                            |
| and Independent QA/QC Review  |                                      |
| of Topographic Data           |                                      |
+-------------------------------+--------------------------------------+
|                               | Appendices A and M                   |
+-------------------------------+--------------------------------------+
| Base Map Acquisition and      | Volume 1                             |
| Preparation                   |                                      |
|                               |                                      |
| And Independent QA/QC Review  |                                      |
| of Base Map                   |                                      |
+-------------------------------+--------------------------------------+
|                               | Appendices A, K, L, and M            |
+-------------------------------+--------------------------------------+
| Hydrologic Analyses and       | Volume 1                             |
| Independent QA/QC             |                                      |
|                               |                                      |
| Review of Hydrologic Analyses |                                      |
+-------------------------------+--------------------------------------+
|                               | Appendices A, C, E, F, G, H, and M   |
+-------------------------------+--------------------------------------+
| Hydraulic Analyses and        | Volume 1                             |
| Independent QA/QC Review of   |                                      |
| Hydraulic Analyses            |                                      |
+-------------------------------+--------------------------------------+
|                               | Appendices A, B, C, E, F, G, H, and  |
|                               | M                                    |
+-------------------------------+--------------------------------------+
| Coastal Hazard Analyses and   | Volume 1                             |
| Independent QA/QC of Coastal  |                                      |
| Hazard Analyses               |                                      |
+-------------------------------+--------------------------------------+
|                               | Appendices A, B, C, D, H, and M      |
+-------------------------------+--------------------------------------+
|                               | Coastal Guidelines Updates"          |
+-------------------------------+--------------------------------------+
| Floodplain Mapping and        | Volume 1                             |
| Independent QA/QC             |                                      |
|                               |                                      |
| Floodplain Mapping (including |                                      |
| Redelineation/Digitization)   |                                      |
+-------------------------------+--------------------------------------+
|                               | Appendices C, D, E, F, G, H, K, L,   |
|                               | and M                                |
+-------------------------------+--------------------------------------+
| Produce Preliminary Map       | Volume 1                             |
| Products and Independent      |                                      |
| QA/QC Review of Produce       |                                      |
| Preliminary Map Products      |                                      |
+-------------------------------+--------------------------------------+
|                               | Appendices K, L, and M               |
+-------------------------------+--------------------------------------+
| Distribute Preliminary Map    | Volume 1                             |
| Products and Independent      |                                      |
| QA/QC Review of Distribute    |                                      |
| Preliminary Map Products      |                                      |
+-------------------------------+--------------------------------------+
|                               | Appendices J, K, L, and M            |
+-------------------------------+--------------------------------------+
| Post-Preliminary Processing   | Volume 1                             |
+-------------------------------+--------------------------------------+
|                               | Appendices J, K, L, and M            |
+-------------------------------+--------------------------------------+

## SECTION 6--- SCHEDULE {#section-6-schedule .unnumbered}

## The activities documented in this [{MAS/SOW}]{.mark} shall be completed in accordance with Table 6.1 Mapping Activities Schedule. If changes to this schedule are required, the responsible Mapping Partner shall coordinate with FEMA and the other Mapping Partners in a timely manner. Please also identify to whom the products associated with each task are to be submitted to (i.e. the MIP, FEMA Regional Office, etc.).[\<Include only those activities that apply to this Flood Map Project in the table below. Place table on separate page if all activities are to be included.\>]{.mark}  {#the-activities-documented-in-this-massow-shall-be-completed-in-accordance-with-table-6.1-mapping-activities-schedule.-if-changes-to-this-schedule-are-required-the-responsible-mapping-partner-shall-coordinate-with-fema-and-the-other-mapping-partners-in-a-timely-manner.-please-also-identify-to-whom-the-products-associated-with-each-task-are-to-be-submitted-to-i.e.-the-mip-fema-regional-office-etc..include-only-those-activities-that-apply-to-this-flood-map-project-in-the-table-below.-place-table-on-separate-page-if-all-activities-are-to-be-included. .unnumbered}

Table 6.1 Mapping Activities Schedule

  ----------------------------------------------------------------------------------
  **ACTIVITIES**                       **RESPONSIBLE   **START   **END    **COST**
                                       PARTNER(S)**    DATE**    DATE**   
  ------------------------------------ --------------- --------- -------- ----------
  Scoping                                                                 

  Field Surveys                                                           

  Topographic Data Development                                            

  Independent QA/QC Review of                                             
  Topographic Data                                                        

  Base Map Acquisition                                                    

  Independent QA/QC Review of Base Map                                    

  Hydrologic Analyses                                                     

  Independent QA/QC Review of                                             
  Hydrologic Analyses                                                     

  Hydraulic Analyses                                                      

  Independent QA/QC Review of                                             
  Hydraulic Analyses                                                      

  Coastal Flood Hazard Analyses                                           

  Independent QA/QC Review of Coastal                                     
  Hazard Analyses                                                         

  Floodplain Mapping: Detailed                                            
  Riverine or Coastal Analysis                                            

  Floodplain Mapping: Refinement or                                       
  Creation of Zone A                                                      

  Floodplain Mapping: Merging Revised                                     
  and Unrevised Areas                                                     

  Floodplain Mapping: Redelineation                                       

  Independent QA/QC Review of                                             
  Floodplain Mapping                                                      

  Develop Draft DFIRM Database                                            

  Produce Preliminary Map Products                                        
  (including Graphic Specifications)                                      

  Independent QA/QC Review of Produce                                     
  Preliminary Map Products                                                

  Distribute Preliminary Map Products                                     

  Post-Preliminary Processing                                             

  **TOTAL COST**                                                          
  ----------------------------------------------------------------------------------

{Insert name of responsible Mapping Partner} shall to the MIP workflow
tasks with schedule and cost information within {Enter period of time}
once funds are awarded.

## SECTION 7---CERTIFICATIONS {#section-7certifications .unnumbered}

###### Data Capture Standards {#data-capture-standards .unnumbered}

###### DCS Certification Form {Insert appropriate Data Capture Standards (DCS) language applicable to this Mapping Activity Statement. PLEASE NOTE: The DCS are being updated. FEMA Regions should update this document accordingly once the DCS update is complete.}

###### Field Surveys and Topographic Data Development {#field-surveys-and-topographic-data-development .unnumbered}

A Registered Professional Engineer or Licensed Land Surveyor shall
provide an accuracy statement for field surveys and/or topographic data
used and shall certify these data meet the accuracy statement provided.
Data accuracy should be stated used the Federal Geographic Data
Committee National Standards for Spatial Data Accuracy, but the American
Society for Photogrammetry and Remote Sensing accuracy reporting
standards are acceptable.

###### Base Map Acquisition and Preparation {#base-map-acquisition-and-preparation .unnumbered}

-   A community official or responsible party shall provide written
    certification that the digital data meet FEMA minimum standards and
    specifications.

-   The responsible Mapping Partner shall provide documentation that the
    digital base map can be used by FEMA. Please note that uploading
    base map data to the MIP does not constitute agreement that the
    digital base map can be used by FEMA. Documentation that the digital
    base map can be used by FEMA is still required.

-   Certifications must be made at the time the intermediate data is
    submitted. For example, if hydrologic data is submitted,
    certification will be required at the time it is submitted.

######### **Hydrologic Analyses, Hydraulic Analyses, Coastal Analyses, and Floodplain Mapping** {#hydrologic-analyses-hydraulic-analyses-coastal-analyses-and-floodplain-mapping .unnumbered}

-   A Registered Professional Engineer shall certify hydrologic and
    hydraulic and coastal analyses and data in accordance with 44 CFR
    65.6(f).

-   Any levee systems to be accredited will be certified in accordance
    with 44 CFR 65.10.

## section 8---technical Assistance and Resources  {#section-8technical-assistance-and-resources .unnumbered}

Project Team members may obtain copies of FEMA-issued LOMCs, archived
engineering backup data, and data collected as part of the Mapping Needs
Assessment Process from FEMA and/or your Regional Project Officer.

General technical and programmatic information, such as FEMA 265 and the
Quick‑2 computer program, can be downloaded from the FEMA website at
<http://www.fema.gov/plan/prevent/fhm/frm_soft.shtm> Specific technical
and programmatic support may be provided through FEMA and/or its
contractor; such assistance should be requested through the FEMA Project
Officer specified in Section 12 -- Points of Contact.

Project Team members also may consult with the FEMA Regional Project
Officer to request support in the areas of selection of data sources,
digital data accuracy standards, assessment of vertical data accuracy,
data collection methods or subcontractors, and GIS-based engineering and
modeling training.

Assistance with the MIP may be requested at miphelp@mapmodteam.com.

## [SECTION 9---contractors (CTP)]{.mark} {#section-9contractors-ctp .unnumbered}

{Insert Name of CTP} intends to use the services of {Insert name of CTP
contractor} as a contractor for this Flood Map Project. {Insert Name of
CTP}shall ensure that the procurement for all contractors used for this
Flood Map Project complies with the requirements of 44 CFR 13.36.

**OR**

{Insert Name of CTP} does not intend to use the services of a contractor
for the Flood Map Project documented in this MAS. {Insert Name of
CTP}shall ensure that the procurement for all contractors, if any, are
used for this Flood Map Project complies with the requirements of 44 CFR
13.36.

Part 13 may be downloaded in PDF or text format from the United States
Government Printing Office website at
http://www.access.gpo.gov/nara/cfr/waisidx_04/44cfr13_04.html.

## [SECTION 9---contractors (IDIQ, OFA)]{.mark} {#section-9contractors-idiq-ofa .unnumbered}

{Insert name of IDIQ or OFA} does not plan to retain the services of
subcontractors for this project. If subcontractors are to be used,
{Insert name of IDIQ or OFA} shall notify the FEMA Regional Project
Officer and Contracting Officer in accordance with the terms of the
contract referenced in the opening paragraph.

## [section 10---Reporting (CTP)]{.mark} {#section-10reporting-ctp .unnumbered}

[Financial Reporting]{.underline}: Because funding has been provided to
{Insert Name of CTP} by FEMA, financial reporting requirements for
{Insert Name of CTP}will be in accordance with Cooperative Agreement
Articles. {Insert Name of CTP} shall also refer to 44 CFR 13.41.

{Insert Name of responsible Mapping Partner}shall provide financial
reports to the FEMA Regional Project Officer and Assistance Officer in
accordance with the terms of the signed Cooperative Agreement for this
MAS.

\<Add/delete/modify information activities, as necessary\>

[Status Reporting:]{.underline} Status reports will be submitted on a
quarterly basis in accordance with the financial reporting submittals.
{Insert Name of CTP} shall refer to 44 CFR 13.4 to obtain minimum
requirements for status reporting. The Project Officer, as needed, may
request additional information on status.

{Insert Name of CTP}may meet with FEMA and/or its contractor up to
bi-weekly, or more frequently if needed, to review the progress of the
project in addition to the quarterly financial and status submittals.
These meetings will alternate between FEMA's Regional Office, the
{Insert CTP Name} office, and conference calls, as necessary.

\<Add/delete/modify information activities, as necessary\>

[Earned Value Reporting:]{.underline} The MIP Workflow is designed to
track the Earned Value of mapping projects. This information is
automatically calculated by the MIP, using the Actual cost and schedule
of work performed, or "actuals" and comparing them to the expected cost
and schedule of work performed, or "baseline".

Once the FEMA Regional office has funded a project {Insert name of FEMA
or NSP}, will complete the "Obligate Project Funds" screen in the MIP.
This step establishes the baseline for the project in the MIP, using the
cost and schedule information for each task as outlined in this document
and agreed to at the completion of the scoping process.

The MIP study workflow allows {Insert name of responsible Mapping
Partner} to report on the status of these projects at a task level. The
cost and schedule information, updated by the {Insert name of
responsible Mapping Partner} for each contracted task, is compared to
the baseline established for those tasks. This information is rolled up
to a project level and monitored by the FEMA Region to assess progress
and Earned Value.

Earned Value reporting involves the reporting of cost, schedule and
performance (physical percent complete) in the MIP by the {Insert name
of responsible Mapping Partner}.

Once the baseline has been established in the MIP, the {Insert name of
responsible Mapping Partner}shall input the performance and actual cost
to date for each contracted task for each project. This must be
completed at minimum every thirty days and at the completion of the
task. When a task is completed, including all QA/QC activities in this
MAS plus the Quality Control Reviews established in PM 42. the {Insert
name of responsible Mapping Partner} shall enter 100% complete, enter
the actual completion cost, and the actual completion date within the
Manage Data Development, Manage Preliminary Map Production, or Manage
Post Preliminary Processing, as applicable.

The Project Officer, as needed, may request additional information on
status on an ad hoc basis.

\<Add/delete/modify information activities, as necessary\>

## [section 10---Reporting (IDIQ, OFA)]{.mark} {#section-10reporting-idiq-ofa .unnumbered}

[Financial Reporting:]{.underline} {Insert IDIQ, OFA Name} shall provide
financial reports to the FEMA Regional Project Officer and Contracting
Officer in accordance with the terms of {Insert IDIQ Contract, Task
Order No.} dated {Insert IDIQ Contract, Task Order Date}.

\<Add/delete/modify information, as necessary\>

[Status Reporting:]{.underline} Status reports will be submitted on a
monthly basis in accordance with the financial reporting submittals. At
a minimum, these reports will include a summary of the work completed to
date. The Project Officer, as needed, may request additional information
on status.

{Insert IDIQ, OFA Name} may meet with FEMA and/or its contractor up to
bi-weekly, or more frequently if needed, to review the progress of the
project, in addition to the financial and status submittals. These
meetings will alternate between FEMA's Regional Office, the {Insert
IDIQ, OFA Name} office and conference calls, as necessary

\<Add/delete/modify information, as necessary\>

[Earned Value Reporting:]{.underline} The MIP was developed in part to
track the Earned Value of mapping projects. This information is
automatically calculated by the MIP, using the Actual cost and schedule
of work performed, or "actuals" and comparing them to the expected cost
and schedule of work performed, or "baseline".

Once the FEMA Regional office has issued a task order {Insert name of
FEMA or NSP}, will complete the "Obligate Project Funds" screen in the
MIP. This step establishes the baseline for the project in the MIP,
using the cost and schedule information for each task as outlined in
this document and agreed to at the completion of the scoping process.

The MIP study workflow allows {Insert name of responsible Mapping
Partner} to report on the status of these projects at a task level. The
cost and schedule information, updated by the {Insert name of
responsible Mapping Partner} for each contracted task, is compared to
the baseline established for those tasks. This information is rolled up
to a project level and monitored by the FEMA Region to assess progress
and Earned Value.

Earned Value reporting involves the reporting of cost, schedule and
performance (physical percent complete) in the MIP by the {Insert name
of responsible Mapping Partner}.

Once the baseline has been established in the MIP, the {Insert name of
responsible Mapping Partner}shall input the performance and actual cost
to date for each contracted task for each project. This must be
completed every thirty days. When a task is completed, the {Insert name
of responsible Mapping Partner} shall enter 100% complete, enter the
actual completion cost, and the actual completion date within the Manage
Data Development, Manage Preliminary Map Production, or Manage Post
Preliminary Processing as applicable.

The Project Officer, as needed, may request additional information on
status on an ad hoc basis.

\<Add/delete/modify information, as necessary\>

## Section 11---Project Coordination {#section-11project-coordination .unnumbered}

Throughout the project, all members of the Project Team will coordinate,
as necessary, to ensure the products meet the technical and format
specifications required and contain accurate, up-to-date information.
Coordination activities shall include:

\<Add/delete/modify information, as necessary\>

-   Meetings, teleconferences, and video conferences with FEMA and other
    Project Team members {specify frequency or dates for meetings};

-   Telephone conversations with FEMA and other Project Team members on
    a scheduled basis {specify schedule for calls} and an ad hoc basis,
    as required;

-   Updates to the MIP and other FEMA status information systems in
    accordance with requirements in Volumes 1 and 3 of G&S; and

-   E-mail, facsimile transmissions, and letters, as required.

## [section 12---points of Contact (CTP)]{.mark} {#section-12points-of-contact-ctp .unnumbered}

The points of contact for this Flood Map Project are{Insert name of FEMA
Regional Projetc Officer}, the FEMA Regional Project Officer; {Insert
name of CTP Project Manager}, the Project Manager for {Insert CTP name};
or subsequent personnel of comparable experience who are appointed to
fulfill these responsibilities. When necessary, any additional FEMA
assistance should be requested through the FEMA Regional Project
Officer.

Each party has caused this MAS to be executed by its duly authorized
representative.

{Insert name of CTP Project Manager} Date

Project Manager

{Insert CTP name}

{Insert name of FEMA Regional Project Officer} Date

Regional Project Officer

Federal Emergency Management Agency, Region Region \#

{Insert name of State authorized representative} Date {Insert title of
State authorized representative}

\<In States where statutory and/or regulatory requirements require the
State's review and/or approval of new flood hazard data, the State will
be a signatory to a community's agreement. Otherwise, delete the State
representative signature line.\>

## [section 12---points of Contact (IDIQ, OFA)]{.mark} {#section-12points-of-contact-idiq-ofa .unnumbered}

The points of contact for this Flood Map Project are {Insert name of
FEMA Regional Project Officer}, and/or the FEMA {Insert name of
Contracting Officer\'s Technical Representative (COTR)}, {Insert Name of
IDIQ, OFA Project Manager}, the Project Manager for {Insert IDIQ, OFA
Name}; or subsequent personnel of comparable experience who are
appointed to fulfill these responsibilities. When necessary, any
additional FEMA assistance should be requested through the FEMA Regional
Project Officer and/or COTR.