Please enable JavaScript.

Coggle requires JavaScript to display documents.

SRTP Development Plan - Coggle Diagram

- - - - 2 days
    - - 2 days
- - - - Include maintenance schedule (additional table with equipment and when it should be put under maintenance)
        
        5 days
      - Could add available/unable option to equipment. This would allow casualties where the equipment is used to be flagged an impacted. When starting a drill, an information popup could display that required equipment is down for maintenance
      - Opportunity to interface with automation system to read status of equipment?
  - - - 20 days
  - - - 1/2 day
    - - KeyValues
      - Crew
        
        1 day
      - EACs
    - - 2 days
  - - - 1 day
    - - 10 days
    - - 2 days
  - - - 5 days
    - - 5 days
    - - 2 days
    - - Make it clearer which machine to sync to (using drill IDs or timestamps)
      - Make it clearer the user has to do something as the window caption says 'please wait'. Use buttons/labels instead of table?
      - Mark the third node as not a sync source so that this machine is not used as a machine to sync to
  - - - 15 days
    - - 10 days
- - - - 5 days
    - - 5 days
    - - 1/2 day
    - - 5 days
    - - 2 days
    - - 15 days
  - - - Make master/slave more like a button
      - Edit/No Edit button to be moved to status or changed to "Preassignment"
        
        3 days
      - Admin Panel on status bar
      - Buttons like aDSS style
    - - 2 day
    - - 1 day
- - - - Heatmap shown by priority
      - Auto assign crew to EAC and position EAC within MVZ
        
        15 days
      - Auto assign priority 1 actions to EACs
    - - 20 days
  - - - 1 month
    - - 20 days
  - - - 5 days
      - Tablet to tablet communication
      - Access points for tablets (eg raspberry pi)
      - Overhaul manual messaging (UI easier to use)
    - - 2 days
      - Reiterated by Celebrity Apex crew
      - Need to tag systems with 1 hour, 2 hour times
    - - Allow leader assignment to made from popups
        
        5 days
    - - Allow users access to all actions
      - Allow users to take actions from teams so that a Special Team could carry out tasks.
        
        10 days
      - May need to update Tablet refresh rate
    - - 5 days
    - - 2 days
    - - 5 days
    - - 5 days
  - - - 5 days
    - - 1 day
    - - Months
    - - 2 days
    - - More than 1 action text for a piece of equipment for a particular scenario
        
        1 day
      - If Equipment in more than once for a particular scenario, get overlapping spaces/scenarios
        
        2 days
      - Check if the casualty and casualty spaces table exist
    - - 5 days
    - - Log File of import process
        
        2 days
      - Statistics
        
        Equipment
        
        Documentation
        
        Casualties
        
        3 days
        
        Scenarios
        
        Equipment Locations
        
        Subsystems
    - - Similar to subsystems, user can decide which scenarios to import for a subsystem
        
        3 days
    - - 5 days
    - - 2 days
    - - 5 days
      - Validating excel input against the ship model
- - - - 1 day
    - - 1 day
    - - 1 day
    - - 1 day
  - - - 20 days
  - - - 10 days
    - - 5 days
  - - - Assigned to Rory
    - - Assigned to Aly
    - - 2 days
    - - 2 days
    - - 2 days
    - - 1 day
    - - 1 day
- - - - 5 days
  - - - 1 day
    - - 1 day
- - - - 5 days
- - - - 2 days