M-SHARP SBTP Design Review

1
M-SHARP SBTPDesign Review

• Public LiveMeeting

16 Jan 2008
Jimmy Parker M-SHARP Product Manager InnovaSystems
, International LLC
2
Agenda

• Intro Background
• SBTP Forecast
• SBTP Execution
• Implementation
• FAQs

3
Agenda

• Intro Background
• SBTP Forecast
• SBTP Execution
• Implementation
• FAQs

4
Introduction

• Purpose of this meeting
• To introduce future users of M-SHARPs SBTP
  module to solicit feedback and overall assessment
  of usability.
• Note this is a pre-beta version
• Please ask questions along the way
• Please mute your phones mic if you can

5
Background / Timeline

• 4 Apr 05 FHP Order MCO 3125.1A
• SBTP data managed in MS Excel
• 4 May 07 Started M-SHARP rqmts
• HQMC APP LtCol Creed Ms. Tracy Guy
• 10 Jan 08 Notice of SBTP automation
• 16 Jan 08 (today) Stakeholder feedback
• 2 Apr 08 Activation of M-SHARP SBTP

6
Excel Page 1 (HMLA-UH)
All SBTP data handled by M-SHARP (yellow)
exceptTEEP events T-Level ratings (gray)
7
Excel Page 2 (HMLA-UH)
8
Expansion of SBTP

• Automation with M-SHARP
• HHQ pull vice monthly squadron push
• More data
• All syllabi (pilots, NFOs, enlisted aircrew)
• Core Plus skills
• More units participating
• FRSs (CMMR requirements not enforced)
• OSA reserves

9
Agenda

• Intro Background
• SBTP Forecast
• SBTP Execution
• Implementation
• FAQs

10
Navigation to SBTP Forecast

• Select Setup menu
• Select Sortie-Based Training
• Select SBTP Forecast

11
SBTP Forecast Page
Squadrons use it to submit once-a-year SBTP
forecast

• Orientation
• Action buttons
• Save/Cancel
• Submit Unsubmit
• Excel Export
• Quick filters
• FY/Unit/TMS
• Submission status
• Tabs
• Squadron TMS
• 1 or more syllabi

12
Submit/Unsubmit Rules

• Only squadrons can Submit
• Prevents HHQ from modifying squadron forecast
  without their knowledge
• Only HHQ can Unsubmit
• Prevents squadrons from modifying their
  submission without HHQ knowledge

13
Squadron Submission Process

• Enter forecast data save (not submit yet)
• Be sure to include all TMSs syllabi
• Export to Excel route to CO/OPSO
• If edits are needed, return to step 1
• Once approved by CO/OPSO, submit
• No edits allowed to submitted forecast

14
HHQ Review of Forecasts

• HHQ (Group/Wing/MARFOR/HQMC) will review
  forecasts per timetable established in DMS
  message
• If a submitted forecast must be modified
• HHQ must Unsubmit it contact squadron
• Squadron makes edits hits Submit again

15
Agenda

• Intro Background
• SBTP Forecast
• SBTP Execution
• Implementation
• FAQs

16
Navigation to SBTP Execution

• Select Reports menu
• Select SBTP Execution

17
SBTP Execution Report
Squadrons HHQ use it monthly to review
execution data

• Orientation
• Read-only
• Forecast execution data
• Excel Export
• Quick filters
• FY/Unit/TMS
• Submission status
• Tabs
• Squadron TMS
• 1 or more syllabi

18
SBTP section in Flight Logger
Used post-flight to allocate flight time to SBTP
Categories

• Select one or more categories
• Training
• Support
• Operational
• Contingency
• Exists today, but not required
• Must equal TFT or be left blank
• Will be mandatory
• Must equal TFT
• Pop-up help

19
Pop-up window for selection of SBTP hour types
Training Hours - Includes all flight training in
accordance with T/M/S TR manuals (initial or
refly), flight leadership, and OPNAV-directed
instrument training minimums.

• Whenever any member of the crew is receiving
  either an initial TR credit or an update of a
  TR code, they should log training hours
  specifically for the training portion of the
  sortie, including when participating in a frag or
  other operational sortie.  The only exception is
  for sorties flown in support of a contingency or
  combat operation, in which case they should be
  considered contingency hours.
• The key difference between a training and
  operational sortie is that if any member of the
  flight is able to log a TR code, whether it is
  initial or refly, the training portion of the
  sortie is logged as such.  The remaining portion
  of the flight, including the transit, is logged
  as operational time to capture the external
  requirements imposed on fleet units. 
• Note that any dedicated training flight that is
  aborted in-flight or is incomplete for any reason
  shall be attributed to support hours.

Support Hours - Includes all squadron-generated
sorties that do not fit the criteria for training
and are not specifically tasked by an outside
command or agency.

• Specific examples include FCFs, FCP under
  training, instructor under training (IUT),
  flights conducted at MAWTS-1 during a
  Weapons and Tactics Instructor Course, and
  non-training ferry/transit flights.
• Any dedicated training flight that is aborted
  in-flight or is incomplete for any reason shall
  be attributed to support hours.

Operational Hours - Includes all
squadron-generated sorties that do not fit the
criteria for training and are not specifically
tasked by an outside command or agency.

• If aircrew TR syllabus training is conducted in
  accordance with operational flights, log any
  non-TR producing time as operational once TR
  requirements have been satisfied or if there is
  significant non-TR transit or loiter time
  involved.
• The key difference between a training and
  operational sortie is that if any member of the
  flight is able to log a TR code, whether it is
  initial or refly, the training portion of the
  sortie is logged as such.  The remaining portion
  of the flight, including the transit, is logged
  as operational time to capture the external
  requirements imposed on fleet units.

Contingency Hours - Includes all sorties flown in
support of a contingency or combat operation,
whether or not a TR code can be logged.

• Assault support aircraft operating in geographic
  areas formally designated as contingency should
  log contingency hours for every flight in support
  of that contingency.. 

20
Update to Baseline Unit Flt Hrs
Used once by squadrons to baseline SBTP Category
Hours
SBTP Category
Training
Support
Operational
Contingency
Training
Support
Operational
Contingency
21
Monthly Review Process

• No action required by squadrons except to keep
  M-SHARP data accurate
• On or after the 10th of the month, HHQ reviews
  previous months execution data
• Any issues are handled as they are today (phone,
  email, etc.)

22
Agenda

• Intro Background
• SBTP Forecast
• SBTP Execution
• Implementation
• FAQs

23
Implementation Timeline

• 16 Jan 08 (today) M-SHARP Design Review
• Mar M-SHARP activates SBTP
• Squadron use optional until April
• Training will be conducted by the M-SHARP Support
  Team
• 2 Apr Squadrons re-submit FY-08 forecast
• 9 Apr MAG review of squadron forecasts
• 16 Apr Wing review of squadron forecasts
• 23 Apr MARFOR review of squadron forecasts
• 30 Apr HHQ begins pulling execution data

24
Key Question

• If HHQ can now access squadron-level data, how
  will they know if it is accurate?

25
Implementation Levels

• Level 2 CO declares unit data accurate
• Level 3 data baselined, daily scheduling
  logging flights, NALCOMIS interface
• Minimum training requirements met
• At least 1 M-SHARP Admin in Ops
• Units expected to reach level 1 in 3 months
• M-SHARP use required, but not trained
• M-SHARP use not required

26
Current Implementation Status
27
Agenda

• Intro Background
• SBTP Forecast
• SBTP Execution
• Implementation
• FAQs

wi
28
FAQs

• Can the monthly SBTP report be edited manually?
• Forecast data yes via Unsubmit/Resubmit process
• Execution data no
• If a pilot from Squadron A flies in an aircraft
  from Squadron B, which unit gets the
  hours/sorties toward their SBTP?
• Squadron B
• How will deployed hours/sorties get counted?
• Via SPIN files counts toward mother squadron

29
FAQs

• Will simulator time count toward SBTP?
• Sim hours counted in Total Sim Hours block
• TR code(s) logged in sim contribute to CSP
• How are sorties counted?
• sorties legs on a NAVFLIR
• Will ACMMR be used in SBTP?
• Yes, but not at the start. Well add that later.
• Do augment/staff aircrew count?
• All permanently assigned crew count

30
Questions

• M-SHARP SBTP Design Review

Jimmy Parker M-SHARP Product Manager InnovaSystems
, International LLC
31
CCRM Estimates Page
HQMC uses it once-a-year to input CCRM reference
for T-2.0