1 / 28

References in support of a contingency with CG personnel ALCOAST 160/11 ALCOAST 590/09

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 9730-10 COMDTINST 5400.2

myles-scott
Download Presentation

References in support of a contingency with CG personnel ALCOAST 160/11 ALCOAST 590/09

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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 9730-10 COMDTINST 5400.2 LANT/PAC AREA 1330.1

  2. Benefits of using MRTT at Incident level • Incident requirements are more detailed in MRTT. • Significantly increases probability to received most qualified person for the requirement. • Approved incident requirements are instantly advertised on Volunteer Bulletin Board. • 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. • Surge capability and level of response can be monitored by parent commands.

  3. 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 =

  4. MRTT Recommend Use Under The ICS System 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. MOB/DEMOB UNIT RESOURCE UNIT MOB/DEMOB unit will check members in and out of from incident. LOGISTICS 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.

  5. Where It All Starts ICS 213 RR URI 1149

  6. Building The Request For Individual Skills 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. Commands/ICPs build the basic request for personnel from 213 RR.

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

  8. 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.

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

  10. 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.

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

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

  13. 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.

  14. ICS 213 RR For Teams URI 1150

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

  16. Edit The Operational Requirement

  17. 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.

  18. 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.

  19. 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.

  20. 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.

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

  22. 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.

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

  24. IMT Processing For Incidents Check Out members IMPORTANT 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.

  25. SPODEMOB E-mail Notification The SPO will receive an E-Mail notifying the member has been demobilized from the incident.

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

  27. 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.

  28. Program Manager LCDR Thomas Gwilliam CG-1B1 202-475-5043 Thomas.V.Gwilliam@uscg.mil Development Team Leader PERS3 Ray Dalton Sector HR 757-295-2070 Raymond.R.Dalton@uscg.mil Questions

More Related