System Outage and Backup Processing - S-1 Procedural Page

Role and responsibility

S-1 admin specialists own outage detection and backup processing at the unit level. The S-1 clerk detects the outage and runs paper backup. The S-1 chief coordinates with MISSO and tracks outage status. The S-1 officer notifies the chain and briefs the commander on impact. The IPAC outage coordinator runs parallel response for installation-tied systems.

Source documents flow from system error messages, MISSO outage bulletins, network status updates, and the unit outage log. Backup actions live on paper templates queued for post-outage entry. Outputs include the outage report, the queued transaction log, the reconciliation roster on return to service, and the unit system log entry.

MCAAT inspects the outage log for response timeliness, paper queue completeness, and reconciliation audit trail. Lost transactions during outage, no reconciliation on return to service, and absent backup kit trigger findings under MCO 5000.14DMCO 5000.14D enclosure 6. Stage the backup kit before the outage, not during.

Trigger events

• MCTFS unreachable from the unit network.
• UD-MIPS rejects all transactions with a system error.
• MOL self-service portal returns server error.
• RAPIDS workstation fails to connect to PRIDE.
• Network outage cuts the unit off from the M&RA backend.
• MISSO issues a planned maintenance window notification.
• Cyber incident triggers system isolation.

Processing workflow

1. Detect the outage. Confirm the outage hits multiple users, not a single workstation, by cross-checking with another clerk. The S-1 clerk runs detection.
2. Notify MISSO. Submit an outage trouble ticket through the MISSO support portal per MCO 5000.14DMCO 5000.14D enclosure 6. Pull the outage status.
3. Notify the chain. Brief the S-1 officer on outage scope, affected systems, and expected duration. The S-1 officer notifies the commander.
4. Activate the paper backup processing kit. Pull the kit from the staged location. The kit contains paper UD-MIPS diary templates, MCTFS transaction sheets, and the MCTFSPRIUMMCTFSPRIUM code reference.
5. Queue inbound transactions. Capture join, detach, leave, promotion, and pay transactions on paper templates during the outage. Mark urgent transactions for priority processing.
6. Track urgent transactions. Maintain a priority queue for pay-affecting and casualty transactions. The S-1 chief tracks.
7. Pull MISSO updates. Refresh outage status on a fixed cycle (every hour for active outage, daily for planned maintenance) per MCO 5000.14DMCO 5000.14D.
8. Run reconciliation on return to service. At system restore, enter every queued transaction in the order received. Cross-check against the paper queue. The S-1 chief reconciles per MCTFSPRIUMMCTFSPRIUM outage reconciliation procedures.
9. Document the outage. Record outage start, end, affected systems, queued transaction count, and reconciliation outcome in the unit system log per MCO 5239.2BMCO 5239.2B.
10. Brief the commander. Present outage impact, response actions, and lessons learned on a fixed cycle. Update the backup kit and procedures based on lessons learned.

Systems of record and forms

Systems

• MISSO support portal. Outage notification and status.
• Paper backup processing kit. Local kit with templates and references.
• Unit system log. Local register of outages and reconciliation outcomes.
• MCTFS, UD-MIPS, MOL, RAPIDS. Systems affected by outage events.

Forms

• Paper UD-MIPS Diary Template. Captures diary lines during outage.
• Paper MCTFS Transaction Sheet. Captures pay and personnel transactions during outage.
• Outage Report. Local report of outage scope and response.
• Reconciliation Roster. Tracks queued transactions through post-outage entry.

Common pitfalls

• Backup kit not staged. The outage hits and the unit lacks templates. Stage the kit at the moment of every quarterly review per MCO 5000.14DMCO 5000.14D enclosure 6.
• Transactions lost during outage. The clerk does not capture inbound work on paper. Queue every transaction on paper, no exceptions.
• No reconciliation on return to service. The system restores but queued work sits unprocessed. Run reconciliation within 24 hours of restore per MCTFSPRIUMMCTFSPRIUM.
• MISSO not notified. The unit handles the outage in silence. Submit the ticket within 30 minutes of detection.
• Outage not documented in the system log. The audit trail breaks. Update the log at every outage per MCO 5239.2BMCO 5239.2B.

Decision points

• Local outage versus system-wide outage. Cross-check with another clerk before activating backup processing. Local issues route to local IT, not MISSO.
• Priority queue criteria. Pay-affecting and casualty transactions get priority on return to service. The S-1 chief sets the priority order per MCTFSPRIUMMCTFSPRIUM.
• Cyber incident versus outage. The outage shows signs of a cyber event. The S-1 officer routes to the unit cybersecurity officer per MCO 5239.2BMCO 5239.2B.

Authority

This sub-page sits under MCO 5000.14DMCO 5000.14D MCAP enclosure 6, which establishes MISSO support for outages. MCTFSPRIUMMCTFSPRIUM defines paper backup procedures and reconciliation rules. NAVMC 3500.3ENAVMC 3500.3E T-R event 0102-GENA-1015 covers outage response as part of administrator duties. MCO 5239.2BMCO 5239.2B Marine Corps Cybersecurity Program governs cyber incident routing. MCO P1070.12KMCO P1070.12K sets records retention for outage logs.

Related references

• MCO 5000.14D Marine Corps Administrative Procedures. MISSO outage support at enclosure 6.
• MCTFSPRIUM. Paper backup procedures and reconciliation rules.
• MCO 5239.2B Marine Corps Cybersecurity Program. Cyber incident routing.
• MCO P1070.12K Individual Records Administration Manual. Records retention for outage logs.
• NAVMC 3500.3E Manpower and Administration T-R Manual. Event 0102-GENA-1015 outage response.