New System Release Onboarding - S-1 Procedural Page

Role and responsibility

S-1 admin specialists own new system release onboarding at the unit level. The S-1 chief coordinates training before activation and routes activation requests through MISSA. The S-1 officer authorizes activation on completion of training and signs the release brief to the chain. The IPAC release coordinator runs parallel onboarding for installation-tied accounts.

Source documents flow from MISSA release notifications, MOL Users Manual updates, MCTFSPRIUM updates, and module-specific release notes. Onboarding actions touch every system the release affects. Outputs include the training roster, the activation confirmation per user, the unit system log entry, and the OMPF Field Folder Page 11 entry documenting training.

MCAAT inspects the system log for release documentation, training records for completion before activation, and the unit access roster for post-release accuracy. Access activated before training triggers a finding under MCO 5239.2BMCO 5239.2B. Train before activate, every release.

Trigger events

• MISSA releases a new MOL module or major MOL update.
• MCTFSPRIUM update changes transaction codes or KSD requirements.
• New UD-MIPS release alters certifier or clerk workflow.
• NIS releases or updates the access manager for Marine Online applications.
• RAPIDS release changes CAC or DEERS workflow.
• TFSMS release changes T-O or T-E reporting.
• Pre-release notification arrives requiring readiness check.
• Emergency patch release requires immediate onboarding.

Processing workflow

1. Receive the release notification. Pull from the MISSA support portal, the M&RA release feed, or the MOL administrator interface. Cross-check release date and affected systems. The S-1 clerk runs receipt.
2. Identify affected users. Cross-check the active account roster against the affected systems. Build a release impact list. The S-1 chief identifies.
3. Schedule release training. Set a training date before the activation date. The S-1 chief schedules.
4. Conduct release training. Run training to the updated MOL Users ManualMOL Users Manual or MCTFSPRIUMMCTFSPRIUM release notes per NAVMC 3500.3ENAVMC 3500.3E T-R event 0102-GENA-1015.
5. Document training. Cut a Page 11 entry per user recording release training and date completed per MCO P1070.12KMCO P1070.12K Chapter 6.
6. Request access activation. Route activation requests through MISSA per MCO 5000.14DMCO 5000.14D enclosure 6.
7. Validate the release. Run a test transaction in a training environment when available. Confirm functionality matches the user manual.
8. Document the change. Record the release date, affected systems, training date, activation date, and validation outcome in the unit system log per MCO 5239.2BMCO 5239.2B.
9. Brief the chain. Present the release scope, new functionality, and any process changes to the chain on a fixed cycle.
10. Refresh the manual on hand. Update the unit copy of the MOL Users ManualMOL Users Manual or MCTFSPRIUMMCTFSPRIUM with the release notes attached.

Systems of record and forms

Systems

• MISSA support portal. Source of release notifications and activation requests for MISSA-owned services.
• MOL, MCTFS, UD-MIPS, RAPIDS, TFSMS. Affected systems under release.
• Unit system log. Local register of release events.
• MOL Users Manual and MCTFSPRIUM. Authoritative release documentation.

Forms

• Release Training Roster. Local form documenting training per user.
• Unit System Log Entry. Local register of release events and validations.
• NAVMC 118 (11) Administrative Remarks. Page 11 documenting release training.

Common pitfalls

• Access activated before training. The clerk operates without release knowledge. Train first, activate second per MCO 5239.2BMCO 5239.2B.
• Release notification missed. The unit operates on the prior release while MISSA has rolled forward. Subscribe to the MISSA release feed.
• Test transaction skipped. The release defect surfaces in production. Test before live use when a training environment is available.
• Manual copy not refreshed. The unit references stale documentation. Refresh the local copy at every release.
• System log not updated. The audit trail breaks. Update at every release per MCO 5239.2BMCO 5239.2B.

Decision points

• Phased rollout versus full activation. MISSA releases in waves. The S-1 chief activates per the wave assigned to the unit, not ahead of schedule.
• Emergency patch versus scheduled release. The patch arrives outside the normal cycle. The S-1 officer authorizes immediate activation when MISSA designates the release as a security patch per MCO 5239.2BMCO 5239.2B.
• Training rollback. The release introduces a defect requiring rollback. Coordinate with MISSA and brief the chain on the temporary process per MCO 5000.14DMCO 5000.14D enclosure 6.

Authority

This sub-page sits under MCO 5000.14DMCO 5000.14D MCAP enclosure 6, MISSA release support, and MCTFS FoS Access Policy and Procedures 8.0MCTFS FoS Access Policy and Procedures 8.0 for MCTFS access changes. NAVMC 3500.3ENAVMC 3500.3E T-R event 0102-GENA-1015 covers training as part of MOL administrator duties. MCO 5239.2BMCO 5239.2B Marine Corps Cybersecurity Program sets the train-before-activate principle. The MOL Users ManualMOL Users Manual and MCTFSPRIUMMCTFSPRIUM are the authoritative release documentation.

Related references

• MCO 5000.14D Marine Corps Administrative Procedures. MISSA release coordination.
• MCO 5239.2B Marine Corps Cybersecurity Program. Train-before-activate framework.
• MCTFS FoS Access Policy and Procedures 8.0. MCTFS access changes under MISSA.
• MCTFSPRIUM. Release notes for MCTFS and UD-MIPS transactions.
• MOL Users Manual. Release notes for MOL modules.
• MCO P1070.12K Individual Records Administration Manual. Page 11 entries documenting training.
• NAVMC 3500.3E Manpower and Administration T-R Manual. Event 0102-GENA-1015 covers release training.