MCTFS FoS Access Policy and Procedures 8.0 with Addendum 9

Scope

This policy governs access to the Marine Corps Total Force System Family of Services (MCTFS FoS), which holds Marine Corps pay and personnel data on the mainframe plus the Marine-On-Line (MOL) services layered on top. It supersedes prior editions and sets the standard approval process, AutoSAAR submission, levels of privilege, account management, MOS-to-role mapping, annual recertification, and de-provisioning. Addendum 9 is dated 15 April 2026 and takes effect immediately.

Audience

S-1 and IPAC admin specialists who request and provision MCTFS access. Supervisors and security managers who sign the SAAR. TASOs who create and delete User ACIDs. Commanders, disbursing officers, and finance personnel holding privileged or command-authority roles.

Authority and responsibility

MCTFS access sits under the responsibility of the Manpower Information Systems Support Activity (MISSA), supported by the Manpower Information Systems Support Offices (MISSO) and the Marine Corps Resources Fiscal Finance (RFF). The Mainframe Security Office of the Technical Services Organization (TSO) in Indianapolis provisions every mainframe account. MISSA is the functional manager and action authority for manpower access. RFF is the functional manager for finance access and for the RFF-owned MOL services.

Process map

• Manpower MCTFS access. Submit through AutoSAAR at https://autosaar.usmc.mil. The form routes user, supervisor, security manager, then MISSA. MISSA validates, signs, and submits a JIRA request to TSO. TSO provisions the account.
• Finance MCTFS access. Complete the paper DD Form 2875 (SAAR) plus an INFOMGT or JIRA ticket through the TASO to the RFF OMB. TSO provisions. RFF holds the records.
• SAAR form. Effective 2026-03-25, the only acceptable form is the DD 2875 edition dated 2022-05 with the separate Marine Corps User Agreement Addendum Version 1.0 dated 2026-03.
• Account management. The TASO creates the User ACID at check-in and deletes it at check-out. Mainframe accounts auto-suspend at 30 days of non-use and auto-delete at 45 days per MCEN Operational Advisory 294-16.
• MOL and UDMIPS. Sections 7 through 9 cover MOL service responsibility, UDMIPS roles, post-provisioning activation, periodic reviews, and access revocation.

Connection to higher policy

• DD Form 2875, the DoD System Authorization Access Request, is the DoD-level access instrument. This policy sets the acceptable edition and the Marine Corps User Agreement Addendum requirement.
• MCEN Operational Advisory 294-16 drives the 30-day auto-suspend and 45-day auto-delete rule for mainframe accounts.

Connection to Marine Corps doctrine and lower policy

• MARADMIN 601/24 directs UD/MIPS as the central repository for MILPAY Key Supporting Documents. The UDMIPS roles in Sections 7 through 9 of this policy govern the accounts performing those uploads.
• The MCTFS PRIUM governs reporting once access exists. This policy governs who reaches the system.
• Portal admin systems-management pages execute this policy, covering account provisioning and SAAR-N processing, privileged certifier account authorization, MOL administrator permissions management, new system release onboarding, and account closure at detach. The MCAAT systems management checklist inspects compliance.

Access

Active and gated. The source sits behind DoD authentication on the MISSA SharePoint. Reach the SAAR landing page and the policy PDF at the external link above. The MISSA point of contact is listed in the addendum. Confirm the current addendum before relying on a specific paragraph.