R 091200Z JUN 23
MARADMIN 296/23
MSGID/GENADMIN/CMC DCI WASHINGTON DC//
SUBJ/MARINE CORPS CIRCUIT MANAGEMENT OFFICE TRANSITION FROM DEPUTY COMMANDANT FOR INFORMATION TO MARINE FORCES CYBERSPACE COMMAND//
REF/A/MARADMIN 356-22/131630Z JUL 22//
REF/B/DOD MEMORANDUM -TDM ELIMINATION/YMD: 20211018//
NARR/REF A IS THE USMC POLICY GUIDANCE FOR CIRCUIT TELECOMMUNICATIONS REQUESTS (TR). REF B IS THE TIME DIVISION MULTIPLEXING TECHNOLOGY (TDM) ELIMINATION MEMORANDUM//
POC/M. R. RUIZ/LTCOL/HQMC DC I IC4 ICN BRANCH/TEL: 571-256-9089/MICHAEL.RUIZ@USMC.MIL//
POC/C. E. DAY/CIV/MARFORCYBERCOM-G36/TEL: 667-812-6405/CEDAY@NSA.GOV//
POC/J. G. PROUDFOOT/CIV/ MARFORCYBERCOM-MCCOG/TEL: 571-697-4195/JEFFREY.PROUDFOOT@USMC.MIL//
GENTEXT/REMARKS/1. Purpose. Publish a coordinated Deputy Commandant for Information (DC I) Information, Command, Control, Communications, and Computers (IC4) and Marine Forces Cyberspace Command (MFCC) message to direct the actions required to plan for and execute transition of the Marine Corps Circuit Management Office (MCCMO) to MFCC.
2. Background.
2.a. The MCCMO is the primary manager of the service-level enterprise circuits as part of DC I. The MCCMO is responsible for planning and modernizing circuit infrastructure which includes receiving, reviewing, and managing all Marine Corps circuit requests. The MCCMO leverages DC I, Information Resources Division (IRD) as the resource sponsor for funding circuits across the Marine Corps Enterprise Network (MCEN).
2.b. Marine Corps Cyberspace Operations Group (MCCOG) serves as the operational organization on behalf of MFCC and is responsible for the management and operation of the MCEN.
2.c. This MARADMIN directs no changes to the circuit management process. MFCC will make no changes to the circuit management process without proper vetting, coordination, and adjudication across Service stakeholders.
3. Policy. Thirty days after receipt of this message, MFCC will assume the duties of the MCCMO.  Prior to the official assumption of duties, MFCC and IC4 will coordinate meetings to ensure a smooth transition of the roles and responsibilities.  IC4 Network, Services, and Strategies (ICN) will conduct validation meetings with MFCC/MCCOG at 30, 60, and 90 days to validate the turnover process. During this period, MCCOG will assess their mission and Mission Essential Tasks (MET) and refine them, as required.
4. Roles and Responsibilities.
4.a. DC I, IRD. The following roles and responsibilities will be retained by DC I, IRD.
4.a.1. Retain the roles of assisting the MCCMO with establishing, funding, and maintaining program designator codes (PDCs).
4.a.2. Retain direct funding responsibility and management of the Enterprise PDCs until funding has transferred to MFCC no earlier than fiscal year 2025 (FY25). Coordination with MCCOG will be required to ensure operational requirements are met within a timely manner.
4.a.3. Manage all contract support for General Services Administration (GSA) Enterprise Information Services (EIS). IRD and MCCOG coordination is necessary to ensure appropriate funding and timely approval of TRs. The Technical Point of Contact (TPOC) for the MCCMO will reside at MCCOG.
4.b. DC I, IC4. The following roles and responsibilities will be retained by DC I, IC4.
4.b.1. Immediately initiate the hiring process of one GS/GG13 0391 Billet Identification Code (BIC) and advertise as a detail to MCCOG S3 SPE Circuit Actions, at release of this MARADMIN. No more than 30 days after the hiring process has completed, coordinate and submit a Table of Organization/Equipment Change Request (TOECR) for the GS/GG13 0391 BIC from IC4 to MCCOG, inclusive of funding. At least one (1) MCCOG personnel will partake in the hiring board for this position.
4.b.2. IC4 will plan and coordinate with DoD CIO and DISA for revision, publication, and oversight of policies related to circuit management and provisioning. MFCC/MCCOG will be included in the planning and coordination to ensure collaboration and ability to execute the roles and responsibilities of the MCCMO.
4.c. MFCC. The following roles and responsibilities will be transitioned from IC4 to MFCC and delegated to MCCOG.
4.c.1. Circuit Provisioning.
4.c.1.a. Establish and maintain necessary DISA Direct Storefront (DDSF) accounts and assign appropriate roles within the MCCOG.  Ensure DDSF roles are validated, coordinated, and submitted to the Navy Circuit Management Office (NCMO).
4.c.1.b.  Manage role requests and provide annual validation of Fleet Marine Force (FMF) commands and supporting establishment DDSF roles.
4.c.1.c. Review and approve Telecommunication Requests (TR). Provide training and assistance to new and existing users on TR submission within the DDSF system.
4.c.1.d. Review and validate USMC circuit requests.
4.c.1.e. Provide input to the DC I IRD Service Requirement Review Board (SRRB) for annual and Fiscal Year (FY) requirements, to include planning, budgeting, and briefing the SRRB on enterprise circuit requirements.  
4.c.1.f. Review and validate annual Program Objective Memorandum (POM) requirements.
4.c.2. Circuit Management.
4.c.2.a. Review, validate, revalidate, and or process re-awards for circuit requests. Modernize circuits to support of high-speed and cloud-ready access, as required.
4.c.2.b. Manage the MCCMO PDC database through Defense Information Systems Network (DISN) Subscription Services.
4.c.2.c. Ensure project costs for enterprise telecommunications requirements are within budget to include circuit costs, equipment costs, and monthly recurring and non-recurring costs.
4.c.2.d. Develop appropriate databases to track and validate PDC requests as well as create, maintain, review, and revalidate DDSF roles.
4.c.3. Circuit Planning.
4.c.3.a. Assume duties for the reporting and collection for the modernization of USMC Time Division Multiplexing (TDM) to Internet Protocol (IP) technologies per Ref (b).  Reporting occurs every six months, which is reported to the Department of Defense (DoD) Chief Information Officer (CIO) via DC I IC4.  The schedule is determined by the Department of the Navy (DoN) and the DoD CIO; the report is due two weeks before the date established.
4.c.3.b. Coordinate with Marine Corps stakeholders in support of network modernization.
4.c.3.c. Perform all functions as the USMC Enterprise Designated Agency Representative (DAR) and for circuit related Information Technology Procurement Requests (ITPR).
4.c.4. Stakeholder Engagement.
4.c.4.a. Coordinate and collaborate with circuit stakeholders to ensure proper submission of circuit requests, planning for circuit upgrades and modernization efforts, and for enterprise-level circuit meetings.
4.c.4.b. Coordinate with the DoD CIO, DISA, and IC4 ICN for guidance on implementation of all circuit related policies, directives, and planning initiatives.
4.c.5. Additional Roles and Responsibilities
4.c.5.a. Receive and validate the Defense Information Systems Agency’s (DISA) Fiscal Year (FY) Defense Working Capital Fund (DWCF) billing prices for consolidated services, to include responding to all DISA service requests and concerns. Coordinate with DC I, IRD and necessary stakeholders to identify and resolve billing delinquencies.
4.c.5.b. Coordinate with DC I, IRD to ensure lines of accounting are established and funding is available for USMC customers.  Local comptrollers will remain responsible for the base or unit level PDCs (to include in the MEFs). Work with customers to find reasonable solutions or alternative means of funding requirements. IRD and MCCOG will only review and verify that an LOA/SLOA is applied for services in each fiscal year (FY). 
4.c.5.c. Establish an updated circuit MARADMIN to replace Ref (a), assuming all MCCMO duties and providing support for all non-MCEN and Marine Corps Information Environment Enterprise (MCIEE) functions within the MCCMO portfolio.
5. Coordinating Instructions.
5.a. Customers must notify MFCC if their request requires expedited processing.
5.b. All emerging non-enterprise circuit and equipment must be properly funded by requester/customer, to include vendor provided equipment or security devices as required.
5.c. Customers are responsible for funding and accreditation actions which includes proper coordination with IC4 and MFCC.  Funding must be available and accreditation must be complete prior to circuit activation.   
5.d.  The funding identified to transfer to MFCC accounts for the current level of support provided to the enterprise, IAW paragraph 4.a.2.  Any growth or new requirements will be funded by the individual unit requesting the additional services and functionally transferred to MFCC during the appropriate POM cycle. 
5.e. Customers requiring non-enterprise circuits should establish and maintain DDSF, Telecommunication Certification Office Support System (TCOSS), World-Wide Online Support System (WWOLS), Systems Network Approval Process (SNAP) and Secure Internet Protocol Routing Network (SIPRNet) (SGS) / Global Information Grid (GIG) Interconnection Approval Process System (GIAP) accounts to request and validate circuit needs.
5.f. There are numerous functions of the MCCMO portfolio.  The following are the primary functions which require a higher priority: support to the Marine Corps Intelligence Agency at the Top-Secret classification level, Installation Communications Grid (ICG) of Marine Corps Installation Command (MCICOM) functions, Commercial Internet Service Provider (C-ISP), Public Safety Net (PSNet), and DML300388 (includes tactical circuits supporting the FMF).
6. Questions or assistance regarding the MCCMO Transition Plan should be directed to the points of contact listed in this message.
7.  Release authorized by LtGen Matthew G. Glavy, Headquarters Marine Corps, Deputy Commandant for Information.//