R 261900Z OCT 21
MSGID/GENADMIN/CMC DCI IC4 WASHINGTON DC//
SUBJ/MARINE CORPS ENTERPRISE INFORMATION TECHNOLOGY SERVICE MANAGEMENT (E-ITSM) SERVICE ASSET AND CONFIGURATION MANAGEMENT (SACM) DIRECTIVE FOR REMEDY RECORDS//
REF/A/MSG/JTHQ DODIN FT GEORGE G MEADE MD/121907Z JUL 18//
REF/B/MSG/JTHQ DODIN FT GEORGE G MEADE MD/252150Z JUL 18//
REF/C/DOC/MCSC PFM SES PM N&I CONFIGURATION MANAGEMENT PLAN (CMP)/31 DEC 2018//
REF/D/DOC/HQMC DIR C4 IRM 2300-06C/11 OCT 18//
NARR/(U/FOUO) REF A IS JFHQ-DODIN OPORD 18-0168 IT BASELINE ELEMENTS OF INFORMATION (BEI) AUTOMATED DATA CALL IN SUPPORT OF ENDPOINT ASSET IDENTIFICATION AND STATUS, INCLUDES ATTACHMENT SPECIFYING REQUIRED DATA ELEMENTS FOR DOD COMPONENTS. REF B IS JFHQ-DODIN FRAGO 1 TO OPORD 18-0168. REF C IS THE PROGRAM MANAGEMENT OFFICE CONFIGURATION MANAGEMENT POLICY FOR GARRISON IT SERVICES PROVIDED TO THE MARINE CORPS ENTERPRISE NETWORK (MCEN). REF D IS THE DEPUTY DON CHIEF INFORMATION OFFICER (CIO) POLICY FOR THE E-ITSM SACM PROCESS.//
POC1/DEB HARCHER/CIV/PEO DIGITAL/MCSC/TEL: 703-784-6736/EMAIL: DEBORAH.HARCHER@USMC.MIL//
POC2/LETICIA FRIEND/MFCC/MCCOG/TEL: 571-697-4704/EMAIL: LETICIA.FRIEND@USMC.MIL//
POC3/TREVOR DANIEL/DCI/IC4/TEL: 571-256-9082/EMAIL: TREVOR.DANIEL@USMC.MIL//
GENTEXT/REMARKS/1. PURPOSE. This document provides interim policy for managing Remedy records in support of the E-ITSM SACM process, in order to support IT asset inventory requirements for cybersecurity of the MCEN. Remedy asset records tracked within the BMC Atrium Configuration Management Data Base (CMDB) function as the initial set of Configuration Items (CIs) associated with USMC IT services.
2. Scope. Initial scope for this effort will be Remedy asset records in the computer system class, ensuring entries correlate to physical equipment authoritative records within the asset management repositories Global Command Support System-MC (GCSS-MC) and Defense Property Accounting System (DPAS), and to the operational systems for physical and virtual equipment authorized on the MCEN. All computer system class assets authorized and active on the MCEN are in scope, including contractor furnished equipment such as end user devices. As SACM procedures are developed, asset record management will be matured through supporting processes including request fulfillment (RQF), release and deployment management (RDM) and change management (CHM). The scope for this requirement will expand remaining CI classes.
3. Asset record requirements. The following mandated standard attributes must be completed for all Remedy asset records for CIS on the MCEN unclassified but sensitive internet protocol (IP) router network (MCEN-N) and MCEN secret IP router network (MCEN-S). Required attributes include: CI name, CI description, primary capability, serial number, UIC, support company, (lifecycle) status, is virtual, product name, manufacturer, region, site+, and site group. Details on required attributes and example information are maintained on homeport [https:(slash)(slash)homeport.usmc.mil/eitsm/esacm/sitepages/home.aspx?rootfolder=%2feitsm%2fesacm%2fdocuments%2fremedy%5fimport%5ftemplates&folderctid=0x012000273020632dc7194cad8ca171747036b2&view=%7bc04598ba%2dd269%2d4520%2D9552%2d74732759ed77%7d]. The spreadsheet identifies CI classes and attributes.
4.a. Marine Corps Systems Command (MCSC).
4.a.1. Tracking and management activities. Maintain central attribute spreadsheet, tracking all asset attributes to be recorded and updated through this effort. The enterprise SACM team will schedule regular follow on meetings with these points of contact (POCs) to assess progress and aid in updating records within Remedy.
4.a.2. Integration with trusted data sources. Support integrations of Remedy CMDB with trusted data sources to retrieve required system information associated with authorized asset attributes and relationships to properly address reporting requirements as defined within References (a) and (b).
4.a.3. Ensure fielded computer system class products have correct product catalog entries within Remedy based on product type. Enter the respective organizational POCs for email notifications via the asset import console when records are imported.
4.a.4. Ensure Programs of Record (POR) asset records in GCSS-MC are accurate and complete for fielded systems.
4.b. Marine Corps Cyberspace Operations Group (MCCOG).
4.b.1. Ensure the Enterprise Service Desk (ESD) captures and validates minimum information for assets when users submit support requests or report incidents. Submit details for required changes to the appropriate asset manager. Details shall include CI name (computer name), serial number, manufacturer, product name, support company/organization, location (region/site group/site), room, floor, cube. CI records shall be related to respective tickets.
4.c. PORs and/or other funding sources (e.g., Next Generation Enterprise Network (NGEN), Secure Operational Network Infrastructure and Communication (SONIC), and Hybrid Cloud Services (HCS) funded Contractor Furnished Equipment (CFE), and Government Furnished Equipment (GFE).
4.c.1. Hardware Technical Refresh. PORs and/or other funding sources shall formally publish detailed list via Naval Message, Don Tasker or other formal correspondence to current owning organizations of assets in scope for technical refresh once replacement candidates have been formally identified and prior to contract award of replacements. Details include, but are not limited to: POR/funding source, support company/organization, Unit Identification Code (UIC), hostname, manufacturer, product name, and serial number. Adjustments to refresh candidate list shall be coordinated with respective organizations as required to ensure list of End of Life (EOL) systems and replacements are finalized. Project managers/logisticians shall ensure assets not processed through Enterprise Staging and Delivery (ES&D) facilities (e.g., direct ship) have all relevant contract and support details captured within the Remedy contracts console and all required asset details are captured as defined within the enclosed spreadsheet.
4.d. All Marine Corps activities, agencies, and FMF units.
4.d.1. Identify a primary asset management POC to support efforts NLT 10 business days from release of this message.
4.d.2. Ensure any assets added, removed or modified have a corresponding ticket in Remedy to support activities required, and corresponding asset records within MCEN-N/S Remedy accurately reflect the appropriate lifecycle status on the production network. CI records shall be related to respective tickets.
4.e. Asset Managers.
4.e.1. Enter and update asset records for owned computer systems. Data recorded in Remedy must also be furnished to responsible officers (ROs) to obtain detailed location information (e.g., building, floor, room, cube) to ensure common data elements between the asset accounting systems (DPAS, GCSS-MC) and Remedy CMDB remain synchronized.
4.e.2. Collaborate with change managers within their respective as necessary to ensure CI changes authorized in an approved change request (CRQ) reflect the appropriate lifecycle status and CRQ’s are related to the affected asset record.
4.f. Change Managers and Change Coordinators.
4.f.1. Provide all relevant details to support proper configuration control of CI’s prior to implementation of an authorized change to ensure assets added, removed, modified (upgraded, renamed) or moved are captured within respective change requests.
5. Cancellation contingency. This MarAdmin cancels one (1) year from date of release, unless superseded.
6. Release authorized by BGen J. A. Matos, Director, Information, C4 Division, Deputy Commandant for Information.//