R 131630Z JUL 22
MARADMIN 356/22
MSGID/GENADMIN/CMC DCI IC4 WASHINGTON DC//
SUBJ/USMC POLICY GUIDANCE FOR CIRCUIT TELECOMMUNICATIONS REQUESTS (TR)//
REF/A/HQMC MCCMO CONOPS//
REF/B/DODD 5105.19p/JUL 2006//
REF/C/DISA DWCF/FY 2022//
REF/D/DOC/GSM-O DISA v.3/YMD: 20200508//   
REF/E/MARADMIN 307/20/271547ZMAY20//
REF/F/DOD MEMO – EIS CONTRACT GUIDANCE/YMD: 20200327//
REF/G/MARADMIN 432-20/281910ZJUL20//
REF/H/MCIEE BLUEPRINT//
REF/I/DOD INSTRUCTION 8010.01/SEPT 10, 2018//
REF/J/MCEN WAN TRANSPORT DECISION MEMO/MAR 15, 2022//
NARR/REF A IS THE HEADQUARTERS MARINE CORPS, MARINE CORPS CIRCUIT MANAGEMENT OFFICE (MCCMO) CONCEPT OF OPERATIONS. REF B IS THE DOD DIRECTIVE FOR THE DEFENSE INFORMATION SYSTEMS AGENCY (DISA). REF C IS THE DEFENSE WORKING CAPTIAL FUND (DWCF) BILLING PRICES FOR CONSOLIDATED SERVICES. REF D IS GLOBAL INFORMATION GRID (GIG) SERVICES MANAGEMENT (GSM)-OPERATIONS (GSM-O) DEFENSE INFORMATION SYSTEM AGENCY DISA DIRECT STOREFRONT (DDSF) GUIDE. REF E IS THE USMC IRIDIUM PROCEDURES. REF F IS THE MEMORANDUM FOR THE USE OF THE ENTERPRISE INFRASTRUCTURE SOLUTIONS (EIS) CONTRACT GUIDANCE. REF G IS THE POLICY GUIDANCE FOR THE PROCUREMENT OF COMMERCIAL SOLUTIONS FOR CLASSIFIED SYSTEMS. REF H IS THE MARINE CORPS INFORMATION ENTERPRISE ENVIRONMENT.  REF I IS THE DEPARTMENT OF DEFENSE INFORMATION NETWORK TRANSPORT. REF J IS THE MARINE CORPS ENTERPRISE NETWORK WIDE AREA NETWORK (MCEN WAN) TRANSPORT DECISION MEMORANDUM//                        POC/E. E. BURRELL/CIV/HQMC DC I-IC4-ICN BRANCH/TEL: 571-256-8820/EUGENE.E.BURRELL@USMC.MIL//
POC/MCCMO ORGANIZATIONAL MAILBOX/MCCMO@USMC.MIL//
GENTEXT/REMARKS/1.  Purpose.  This HQMC Marine Corps Circuit Management Office (MCCMO) Policy message is intended to define and outline the processes and procedures for circuit modernization and circuit provisioning.  This Policy is also meant to complement and serve as guidance for Ref (a) and Ref (j).  As local policy may be more restrictive, all subordinate commands should refer to their organization’s G6 or S6 for additional guidance regarding this MARADMIN. 
2.  Background. 
2.a.  The MCCMO is part of Deputy Commandant for Information (DC I) and are the primary managers of the service-level enterprise circuits.  The MCCMO is also responsible for planning and modernizing the USMC circuit infrastructure and receiving, reviewing, and managing all USMC circuit requests.  Current modernization efforts by the MCCMO seeks to expand current transport and cloud initiatives within the Marine Corps Information Environment Enterprise (MCIEE). The MCIEE encompasses the ecosystem of operations, networks, programs of record, etc., within the cybersecurity environment.  One key component of the MCIEE is the MCEN which is the Marine Corps’ network‐of‐networks and approved interconnected network segments.  This network comprises people, processes, logical and physical infrastructure, architecture, topology and Cyberspace Operations.  The MCEN is characterized at a minimum to include Programs of Record that provide network services to forward deployed forces operating in the USMC.mil namespace and in USMC routable IP addresses; and Operations and Maintenance functions that provision data transportation, enterprise IT, network services, and boundary defense.  The MCCMO is the resource sponsor for the MCEN.
2.a.1.  An access circuit is traditionally defined as a remote access lease connecting a non-DISN node to a DISN Service Delivery Node (SDN).
2.a.2.  The MCIEE does include both the Marine Corps Enterprise Network services and all other Community of Interest (COI) stakeholders (i.e., Marine Corps Recruiting Command (MCRC), Public Safety Net (PSNet), etc.) and associated systems.
2.b.  Ref (b) mandates DISA to plan, engineer, and support global net-centric information and communications solutions. DISA's procurement directorate, the Defense Information Technology Contracting Organization (DITCO), acquires telecommunication services globally for the DOD and other authorized Government agencies. DITCO receives mission partners' Telecommunications Service Requests (TSRs) and Telecommunications Service Orders (TSOs) from DISA via a Web service. DITCO establishes contracts, or communication service authorizations (CSAs), with vendors to satisfy the requirements of its mission partners. 
2.c.  Ref (c) defines the Defense Information Systems Network Infrastructure Solutions (DISN IS) as "the transport infrastructure, network operations/management, cyber security, and support services required to provide network services to each requesting agency (i.e. USMC)."  The USMC is allocated an annual share of the network infrastructure costs based on their percentage of total network capacity.  The DISN is the DISA-managed backbone of the Department of Defense Information Networks (DoDIN).
2.d.  DISA Direct Storefront (DDSF).  DDSF is a DISA ordering web-based application for transport, data, voice, satellite, wireless, and other services. All users are highly encouraged to download and review Ref (d) in its entirety.  Ref (d) is the DDSF user guide that provides information for storefront users. Topics include:  
2.d.1.  Access requirements and instructions to create an account.
2.d.2.  Using storefront, logging in to submit, track, and manage orders.
2.d.3.  Instructions on starting, changing, amending, discontinuing, and canceling Telecommunications Request (TR). 
2.d.4.  Available services. 
2.e.  Before submitting a TR, using units must ensure the following:  
2.e.1.  Establishment of a program designator code (PDC).  The MCCMO will establish the PDCs specifically for the Enterprise Services orders.
2.e.2.  Line of Accounting (LOA) associated with the PDC.
2.e.3.  DDSF appointment letter identifying roles and responsibilities with the assigned PDC.
2.e.4.  DDSF account to create, submit, and approveTR's. 
2.f.  Ref (c) details the pricing for the current fiscal year DISA services offered on a reimbursable basis through the Defense Working Capital Fund.  Annual pricing included in each FY publication is billed at a monthly recurring rate provided by DITCO.  This annual pricing book is located on the Mission Partner Portal under "CSM Home > Rate books" in the top navigation bar https:(slash)(slash)disa.deps.mil/ext/cop/mpp/index.aspx.   
3.  Policy. 
3.a.  There are four primary means for requesting Telecommunications products and Services. 
3.a.1.  The first option is DISA-Owned Infrastructure Resources, contractually known as the DISN IS, via DDSF. This category contains IP Transport, DISA Managed Network Resources, Optical Digital Transport System, DISA Unified Capabilities (UC) Transport, DISN Core Fiber Assets, and related allied networks.  Ref (i) provides guidance stating DoD components will “use the Defense Information System Network (DISN) as the core element of DODIN Transport.”  
3.a.2.  The second option is Primary DISN Commercial Lease Transmission Contracts.  This option contains General Service Administration Enterprise Infrastructure Services (GSA EIS) contract, Global Network Services (GNS), DISN Transmission Services-Pacific II (DTS-P II) or Indo-Pacific Transport Services (IPTS), Hawaii Network Services (HNS) Task Order (TO) under GNS, or an Inquiry/Quote/Order (IQO) Competitive Lease Contract.
3.a.3.  The third option is DISN Gateway Solutions.  This option is comprised of the Commercial Ethernet Gateway (CEG) and the Puerto Rico Area Wideband System (PRAWS).
3.a.4.  The fourth option is collectively the use of Last Resort Options.  These include utilization of services and/or networks germane to allied MOAs, or legacy technology systems like M13 multiplexers, Time Division Multiplexing, or any technology in the process of being eliminated from use in the DoDIN.
3.b.  DISN IS. 
3.b.1.  A customer may request telecommunications services via DDSF. MCCMO will receive notification of those requests after the internal routing customer's local agency. The customer may also contact the MCCMO office via email or phone call to verify receipt of the request for processing. The MCCMO will review the request for errors and confirm funding LOA before final processing. In addition, all enterprise-level submissions are reviewed as the MCCMO has overall responsibility for the annual planning, budgeting, and resource allocation for HQMC-funded circuit requests.  
3.b.2.  Once the MCCMO approves a request, the HQMC Resource Division (IRD) will validate the funding availability via DDSF.  Once IRD approves the request, the request will route from HQMC (DC I) to the Naval Circuit Management Office (NCMO).  Upon final review, the NCMO will process the request to DISA/DITCO.  These services are expected to utilize the active DISN core Multi-Protocol Label Switching (MPLS) nodes onsite that replaced or are replacing the previous DISN Multi-Service Provisioning Platform (MSPP) devices onsite/on premise.  This approach is to optimize capabilities covered under the mission partner “share” allocated for the Marine Corps.
3.b.3.  The customer will receive a TSR and TSO (with a Command Communications Service Designator (CCSD)) followed by necessary subsequent completion messages from DISA. 
3.c.  GSA EIS.
3.c.1.  The GSA EIS contract is the main component of GSA's telecommunications portfolio. The Office of Management and Budget (OMB) directed Federal Agencies to develop a plan for all telecommunications and Information Technology (IT) infrastructure services from their previous suite of contracts to the GSA EIS contract by September 30, 2022, per Ref (f).  DITCO is the lead in executing GSA EIS orders for the Department.  
3.c.2.  A customer may request telecommunications services to the MCCMO via DDSF. MCCMO will receive notification of those requests after the internal routing customer's local agency.  The customer may also contact the MCCMO office via email or phone call to verify receipt of the request for processing.  The MCCMO will review the request for errors and correct funding lines of accounting before final processing.
3.c.3.  Once the MCCMO approves a request, the HQMC IRD will validate the funding availability via DDSF. Once IRD approves the request, the request will route from HQMC (DC I) to the NCMO. Upon final review, the NCMO will process the request to DITCO to contract with the selected vendor and complete the requested service.
3.c.4.  MCCMO will review and process all enterprise-level submissions before the official requests to the vendor.  As with DISN IS, MCCMO has the overall responsibility for the annual planning, budgeting, and resource allocation for each HQMC-funded circuit request.  The customer will receive a TSR, TSO (with a CCSD), and a SAM detailing the recurring cost for services followed by necessary subsequent messages from DISA.
3.c.5.  Marine Corps Intranet Task Order. (MCI T.O)
3.c.5.1.  This is the network solution that replaced the USMC Homeland Defense Network (HDN) and consists of the commercial Advanced Virtual Private Network (AVPN) service awarded as a USMC-specific Task Order under the GSA EIS contract vehicle. A customer may request telecommunications services to the MCCMO directly via email, phone call, or an already agreed-upon communications means.  All MCCMO approved MCI T.O. service requests will then be processed via IRD.  Once IRD approves the request, the request will route from HQMC (DC I) to DITCO to contract with the MCI T.O. vendor and complete the service requested.
3.c.5.2.  MCCMO will review and process all enterprise-level submissions before the official requests to the vendor.  As with DISN IS, MCCMO has the overall responsibility for the annual planning, budgeting, and resource allocation for HQMC-funded circuit requests.  The customer and the MCCOG will receive recurring updates from origination of the requirement request through activation and acceptance.
3.d.  DISN Commercial Ethernet Gateway Solutions (CEG).
3.d.1.  A customer may request Gateway solutions such as CEG telecommunications services via DDSF. MCCMO will receive notification of those requests after the internal routing customer's local agency.  The customer may also contact the MCCMO office via email or phone call to verify receipt of the request for processing.  The MCCMO will review the request for errors and correct funding lines of accounting before final processing.  In addition, all enterprise-level submissions are reviewed as the MCCMO has overall responsibility for the annual planning, budgeting, and resource allocation for HQMC-funded circuit requests.  
3.d.2.  Once the MCCMO approves a request, IRD will validate the funding availability via DDSF. Once IRD approves the request, the request will route from HQMC (DC I) to the NCMO. Upon final review, the NCMO will process the request to DITCO to contract with the selected vendor and complete the requested service.
3.d.3. The customer will receive a TSR, TSO (with a CCSD), and SAM detailing the recurring cost for services followed by necessary subsequent completion messages from DISA.
3.d.4.  Currently, this solution is available within the Continental United States (CONUS) and is divided into seven (7) regions.
3.e.  Last Resort Options
3.e.1.  This option is presently not in use by USMC for new requirements.  In the event this option is required by exception the process will follow the same steps outlined in subsection “3.c.”
4.  Coordinating Instructions.
4.a.  DISN IS, GSA EIS, DISA CEG and other commercial options for TRs are meant to be complementary, not mutually exclusive.
4.a.1.  All requirements shall follow the process and guidance per Ref (a) unless otherwise required via HQMC DC I updated guidance.
4.a.2.  If no funding lines of accounting (LOAs) are established or available for the customer, the MCCMO will work with the customer to find reasonable solutions or alternatives to find available means of funding those requirements.
4.b.  The MCCMO, in coordination with the IC4/Networks Branch, will create an online, shared Circuit Management system.  This system will allow users to submit their requirements, track status approvals or rejections, make updates and collaborate with the MCCMO to review and respond to pending requests.
4.c.  The MCCOG will have input in all discussions on developing a solution to meet the security requirements of TRs, for which they are the Cyber Security Service Provider (CSSP).
5.  Guidance for submitting requests. Each customer should ensure the following measures are taken to have their circuit requests reviewed on time:
5.a.  Correct submission of requests
5.b.  Correct routing of requests
5.c.  Daily or weekly status check via DDSF for all DISN IS and CEG requests
5.d.  Clear understanding of the priority of requirements for how circuits are provisioned (i.e. DISN IS or GSA EIS or CEG or other), per Ref (a).  The MCCMO requirements form shall be completed prior to submission of all TR requests.  Additionally, there will be a decision support matrix provided to assist the user and the MCCMO on determining the best available service to use, prior to submission of a TR.
5.e. Participation (when required) in the weekly/bi-weekly HQMC MCCMO meetings designed to address TR requirements, TSRs, and circuit modernization efforts.
5.f.  For all new or revised circuits, the requester/customer needs to ensure authority to connect (ATO) is approved from IC4.  This process may vary depending on how each circuit is engineered.
5.g.  For circuit status monitoring, it is incumbent for the requester/customer to request a DISA/DITCO account to track installation or upgrade process.
5.h.  For all circuits, it is incumbent for the requester/customer to work with the Contracting Officer Representative (COR) for final approval.  The MCCMO does not provide authority for final approval.
5.i.  For all emerging, non-enterprise circuit technologies, within in addition to funding, the requester/customer must ensure additional funding is garnered to pay for any vendor specific equipment or additional security devices required by IC4, as required.
6.  Allow the MCCMO up to 30 days to approve or reject a TR.
6.a.  If there is a request that requires expedited processing (i.e., in support of a specific project), the customer is to alert the MCCMO.  
6.b.  The customer is responsible for ensuring that funding and accreditation actions are properly coordinated and complete before any circuit is activated.  This includes all security requirements being vetted through the Risk Management Framework (RMF) process (if applicable).  Additionally, all requesters/customers will be responsible to plan, annually budget, and brief the SRRB on their circuit requirements.
7.  Questions or assistance regarding the MCCMO Policy should be directed to the points of contact listed.
8.  Released authorized by BGen J. A. Matos, Director, Information C4 Division, Deputy Commandant for Information.//