ICS 213 Personnel Resource Requests, Mobilization Readiness Tracking Tool (MRTT) & Request For Forces (RFF) process for Type 3 Incidents or Higher References in support of a contingency with CG personnel ALCOAST 160/11 ALCOAST 590/09 DCMS/SUPPLAN COMDTINST LANT/PAC AREA

Benefits of using MRTT at Incident level Incident requirements are more detailed in MRTT. Incident requirements are more detailed in MRTT. Significantly increases probability to received most qualified person for the requirement. Significantly increases probability to received most qualified person for the requirement. Approved incident requirements are instantly advertised on Volunteer Bulletin Board. Approved incident requirements are instantly advertised on Volunteer Bulletin Board. Know when requirements are filled/ordered by using Unique Request Identifier URI report. Know when requirements are filled/ordered by using Unique Request Identifier URI report. Tracking of incident requirements is a collaborated effort between incident and supporting commands. Tracking of incident requirements is a collaborated effort between incident and supporting commands. Surge capability and level of response can be monitored by parent commands. Surge capability and level of response can be monitored by parent commands.

What MRTT Is Not = MRTT does not replace ICS. MRTT is not an ICS system. MRTT is not a reserve tool. MRTT is a Coast Guard system inject to the incident command system to track CG personnel, and order CG personnel resources to the incident. MRTT is the only approved system for tracking CG personnel. 213 RR # ICS PROCESS MRTT URI # CG PROCESS

MRTT Recommend Use Under The ICS System MOB/DEMOB UNIT RESOURCE UNIT LOGISTICS MOB/DEMOB unit will check members in and out of from incident. RESOURCE unit will enter in members for tracking their assets and pre-staged resources. When resources are re-leveled/reallocated to new requirements, resource unit will make the new entries. LOGISTICS section will order personnel resources, when organic resources are unavailable. These functions must be completed to capture CG personnel resources regardless of how the ICS structure is setup.

Where It All Starts ICS 213 RR URI 1149

Building The Request For Individual Skills Commands/ICPs build the basic request for personnel from 213 RR. A Unique Requesting Identifier (URI) is created for each individual request and can be used in RMT for quick and accurate identification 213 RR # is referenced and tied to the URI in MRTT and message traffic.

Edit Operational Requirements Commands can edit each of their requirements for competencies for TMT or DA, Schools, etc. Each URI will identify each requirement with a Requirement Tracking Number (RTN) and can be used to track RFF’s to TDY orders issuance Automatic solicitation on VBB once approved.

RFF Message Traffic CG Message traffic like the RFF will have the referenced URI in MRTT and ICS 213 RR #. Sourcing commands can go in MRTT and complete requirement fills.

Resource Request Status Report Requirement title Member sourced and or ordered to incident REQUEST REPORT FOR URI: 1149

Requirement Search In the Volunteer Bulletin Board (VBB) CG members can search for open requirements via search fields. These requirements are advertised as soon as the incident command approves the RTN.

Application/Resume Via VBB Members can apply for multiple requirements and submit resume.

Automated Notification to Command and Member Member and Command receive e- notification of members application. Commands will approve/deny RTN’s that member applied for. This is done via and does not require logging into MRTT.

RFF MRTT entries completed at ICP level….Why? For the Japan earthquake, SSB built 25 jobs, all ICS positions except 2 (PI and FOSCR). They were built and announced at 1300 Thursday. More than 900 volunteered by 1000 Friday. Approved requirements built at the SECTOR will have time to attract volunteers by the time it reaches SSB. This is extremely important when we are usually looking at immediate to 72 hour fill requirements.

ICS 213 RR For Teams URI 1150

Building The Request For Teams Commands/ICPs build the basic request for personnel from 213 RR.

Edit The Operational Requirement

RFF Message Traffic CG Message traffic like the RFF will have the referenced URI in MRTT and ICS 213 RR #. LANT/PAC/DCMS can go in MRTT and complete the requirement fills.

Sourcing Team Requirements LANT/PAC AREA – DCMS can find the URI, add/duplicate and edit the requirements requested and source the personnel that will fill the requested incident TEAMS.

Source Members with Member Match Sourcing commands can search for members by criteria, i.e. AOR, Units, and personnel for competencies. Commands can verify members readiness status. So it is important for members to reflect green.

Source Members From VBB Sourcers can view readiness status and approved volunteers in each open requirement. Once volunteers are approved by their command, the volunteer’s name will populate in the requirement. SSB can see mbr’s IMR status and if the mbr meets all the requirements of the position.

SPO NOTIFICATION When a member is sourced/mobilized in MRTT, the SSB can have an notification sent to the members SPO. It is sent to SPO distribution list.

Members Ordered In Members ordered in by SSB will have RTN info for easy identification of responding members. Not all sourcing commands I.E. District, LANT, DCMS release message traffic.

Resource Request Beginning to End ICS 213 RR Q100E – URI 1149 ICS 213 RR Q100E – URI 1149 RFF MSG MSG ORDERS 213 RR FORM Request completed with all supporting documentation and can be filed as completed. Check status date: 6 Sep 11

IMT Processing For Incidents It is important to check the members into the incident. ICP IMT’s will check-in/check-out members from the incident. They can update members geographic locations if changed. Member will reflect ‘mobilized’ as soon as they are checked in and “demobilized” when checked out. Gives the truth test to those mobilized to an incident. Check Out members

SPO DEMOB Notification The SPO will receive an notifying the member has been demobilized from the incident.

SPO/Command entries in MRTT Return home safely date. Date member reports back to unit Original ordered date for member. Change to RELAD date or reported back date.

Members have returned home safely in system Once the SPO/Command has entered in a return home date it will reflect in MRTT. Can run reports to check.

Questions Program Manager LCDR Thomas Gwilliam LCDR Thomas Gwilliam CG-1B CG-1B Development Team Leader PERS3 Ray Dalton PERS3 Ray Dalton Sector HR Sector HR