DPAS SCR: 02172

• SCR Number
  02172
• Title
  Communication Tracking and Tasking Tool
• DPAS Module
  PA,MU,Warehouse,Materiel Management
• Reporting Organization
  USMC
• State
  New
• History
  6/27/2025
• Description
  Change Request: New Process

  
  

  Description:

   

  ELMS currently lacks a centralized, audit-ready task management capability, resulting in fragmented communication, inconsistent accountability, and limited visibility across MARCORLOGCOM and enterprise stakeholders. If unchanged, task coordination will depend on manual tools such as emails and spreadsheets, which lack standardization, traceability, and support for audit compliance (e.g., FIAR, OMB A-123). This capability gap is a Significant Deficiency that impairs ELMS’s ability to synchronize logistics operations, defend audit findings, and ensure timely execution of mission-critical actions. Implementing the Communication Tracking and Tasking Tool (CTTT) will close this gap by enabling structured, role-based tasking with integrated workflow, sub-tasking, document management, scheduling, and dashboard oversight.

   

  Recommended:

   

  (Requirement Group 1.0: Task Initiator Information)

  REQ-1.1 - Title: Capture Task Initiator Full Name Requirement Statement: The system shall capture and display the Task Initiator’s full name (Last Name, First Name, Middle Initial) at the time of task submission to ensure traceability and accountability of the originator. A temporary Task identification number will be assigned to the draft request and will only be deleted once a CTTT tracking number has been assigned and the task is saved and submitted.

  REQ-1.2 - Title: Record ELMS User Number Requirement Statement: The system shall record the unique ELMS User Identification Number associated with the Task Initiator's user profile to facilitate system-level traceability and user authentication.

  REQ-1.3 - Title: Capture Organizational Details Requirement Statement: The system shall capture the Task Initiator’s organizational details, to include:

  •DoDAAC (Department of Defense Activity Address Code) or UIC (Unit Identification Code),

  •TAC-1 Address (Transportation Account Code primary mailing address), to enable command-level attribution and routing.

  REQ-1.4 - Title: Capture Task Initiator Contact Information Requirement Statement: The system shall record and store the Task Initiator’s primary contact information, including:

  •Government Email Address

  •Commercial or DSN Telephone Number to support communication and task validation efforts.

  REQ-1.5 - Title: Autofill from User Profile Requirement Statement: The system shall autofill all Task Initiator information (Full Name, ELMS ID, DoDAAC/UIC, TAC-1, Contact Info) from the authenticated user’s profile upon new task creation to reduce data entry errors and streamline workflow.

  REQ-1.6 - Title: Display Initiator Information in Task Header Requirement Statement: The system shall display the captured Task Initiator data in the task header of each record for visibility to all users with access to that task.

  REQ-1.7 - Title: Editability Restriction of Initiator Fields Requirement Statement: The system shall restrict manual edits to Task Initiator information by non-system administrators to ensure data integrity. Only the authenticated user or authorized admin may update profile-linked initiator data.

  REQ-1.8 - Title: Retain Historical Initiator Information Requirement Statement: The system shall retain the original Task Initiator information even if the user’s profile is later updated or deactivated to ensure historical audit traceability.

  REQ-1.9 - Title: Capture Task Initiation Timestamp Requirement Statement: The system shall automatically timestamp the date and time (in UTC) a new task is initiated to support time-sensitive performance tracking and compliance reporting.

  REQ-1.10 - Title: Capture Initiator’s Command Hierarchy Requirement Statement: The system shall optionally allow the capture of the initiating command’s hierarchy (e.g., MARCORLOGCOM > WSMC > Section) to enhance filtering, reporting, and command-level oversight.

  B.

  CTTT Header Section – Task Metadata and Assignment Requirements (Requirement Group 2.0: Task Details and Assignment Routing)

  REQ-2.1 - Title: Capture Task Title Requirement Statement: The system shall provide a mandatory field for users to enter a concise Task Title (maximum 150 characters) that summarizes the task’s purpose for identification in dashboards, notifications, and search queries.

  REQ-2.2 - Title: Capture Task Description Requirement Statement: The system shall provide a mandatory rich text field (maximum 1,000-character limit) to allow users to describe the purpose, background, scope, and objectives of the task in narrative format.

  REQ-2.3 - Title: Capture Classification Level Requirement Statement: The system shall require the user to select a Classification Level from a predefined list (e.g., Unclassified, Controlled Unclassified Information (CUI), Confidential, Secret) to ensure proper handling of sensitive information. Note: Only Unclassified and CUI tasks may be processed through ELMS; others will be rejected or flagged.

  REQ-2.4 - Title: Capture Urgency of Need (Priority) Requirement Statement: The system shall require the user to select an Urgency of Need level from the following dropdown values:

  •Critical (Immediate action required)

  •High (Action required within 3 business days)

  •Medium (Action required within 5–10 business days)

  •Routine (No fixed suspense, monitoring required) This selection shall influence dashboard filtering and notification frequency.

  REQ-2.5 - Title: Provide Free-form Text Block (Operational Notes) Requirement Statement: The system shall provide an optional free-form text field (max 2,000-character limit) titled Operational Notes where the Task Initiator can input supplemental, non-structured data such as references, coordination history, or unofficial context not suitable for the formal Task Description.

  REQ-2.6 - Title: Capture and Display ELMS Government Task Manager (Assignment Target) Requirement Statement: The system shall populate the ELMS Government Task Manager field based on pre-defined business rules or assignment criteria (e.g., by DoDAAC, task category, functional module). If assignment criteria are not met or unknown, the field shall

  remain blank and routed to the MARCORLOGCOM CTTT Office for manual task manager assignment.

  REQ-2.7 - Title: Allow Manual Override of Task Manager Assignment Requirement Statement: For users with appropriate permissions (e.g., CTTT Admin, ELMS PMO), the system shall allow manual override of the assigned Task Manager to accommodate exceptions or emergent reassignments.

  REQ-2.8 - Title: Include Pre-Tasking Workflow Routing Flag Requirement Statement: The system shall include a logic-driven routing flag that indicates whether the task requires pre-tasking coordination or approvals (e.g., Immediate Supervisor, Commanding Officer, SupO, Finance, etc.), and dynamically generate a corresponding workflow approval path if applicable.

  REQ-2.9 - Title: Auto-Save Function During Header Data Entry Requirement Statement: The system shall support auto-save functionality every 60 seconds while users are entering header data, preserving partial entries in draft status to prevent data loss due to session timeout or system interruption.

  REQ-2.10 - Title: Unique Task Draft ID Requirement Statement: The system shall assign a temporary Task Draft ID to each initiated task before final submission and tracking number assignment. This ID shall be visible to the user and included in the activity log for traceability.

  C.

  CTTT Header Section – Task Classification & Equipment Details (Requirement Group 3.0: Task Type and Item Metadata)

  REQ-3.1 - Title: Capture Type of Request Requirement Statement: The system shall provide a required dropdown field labeled “Type of Request”, allowing users to select the nature of the task from a predefined list, including but not limited to:

  •Supply

  •Maintenance

  •Data

  •Quality Assurance

  •Services

  •Financial

  •Audit/Compliance

  •Policy/Instruction

  •Technology/IT

  •Facilities/Infrastructure

  •Training The list shall be configurable by system administrators to support future task type additions.

  REQ-3.2 - Title: Allow Editable Task Type by Authorized Users Requirement Statement: The system shall allow authorized personnel (e.g., ELMS PMO, Task Manager) to edit or refine the Type of Request during the Task Acceptance/Assignment phase prior to official task activation and routing.

  REQ-3.3 - Title: Enable Entry of Equipment-Related Task Data Requirement Statement: If the task type selected requires identification of specific equipment (e.g., Supply or Maintenance tasks), the system shall display a conditional “Type of Equipment” entry section with fields for:

  •National Stock Number (NSN)

  •TAMCN (Table of Authorized Materiel Control Number)

  •Serial Number

  •Nomenclature (Item Name)

  •Manufacturer/Model (if applicable)

  •Quantity

  REQ-3.4 - Title: Integrate with ELMS Catalog for Item Lookup Requirement Statement: When a valid NSN is entered, the system shall query the ELMS Item Catalog to retrieve and auto-populate known extended attributes of the item (e.g.,

  Nomenclature, Unit of Issue, Unit Price, Condition Code) to reduce manual data entry and improve accuracy.

  REQ-3.5 - Title: Support Manual Entry of Equipment Data Requirement Statement: If a match to the ELMS Catalog is not found or the NSN field is left blank, the system shall allow the user to manually enter equipment-related metadata using free-text or selectable List of Values (LOVs), with required fields highlighted dynamically.

  REQ-3.6 - Title: Allow Multiple Equipment Line Items Requirement Statement: The system shall allow users to enter multiple equipment line items within a single task record, each with its own equipment metadata and associated task notes (e.g., one task with five NSN/TAMCN items needing separate tracking).

  REQ-3.7 - Title: Track Equipment Metadata Edits by Authorized Users Requirement Statement: The system shall allow authorized users during the Task Acceptance/Assignment phase to update or correct equipment details, with all changes logged in the task audit trail to maintain data integrity and version control.

  REQ-3.8 - Title: Conditional Required Fields for Equipment Tasks Requirement Statement: If the Type of Request is classified as Supply, Maintenance, or Quality, the system shall require entry of at least one equipment item record before allowing task submission or activation.

  REQ-3.9 - Title: Validate NSN Format Requirement Statement: The system shall validate NSN inputs for proper format (13-digit numeric) and display user guidance or input constraints to reduce formatting errors during task entry.

  REQ-3.10 - Title: Support Attachment of Item Documentation Requirement Statement: The system shall allow users to upload supporting item documentation (e.g., technical manuals, calibration reports, service histories) alongside the equipment metadata to provide full context to downstream reviewers and action officers.

  D.

  CTTT – Task Acceptance, Approval, and Assignment Requirements (Requirement Group 4.0: Government Task Manager Controls)

  REQ-4.1 - Title: Automatic Assignment of CTTT Tracking Number Requirement Statement: Upon task approval by the Government Task Manager, the system shall automatically assign a unique CTTT Tracking Number formatted as: [Requestor DoDAAC]-CTTT-[YYMMDD]-[Serial Number] (e.g., M30201-CTTT-250527-0012), which shall serve as the system’s primary key, official task ID, and reference point for audit and tracking purposes. This action shall also capture the origination system date/time stamp for reporting.

  REQ-4.2 - Title: Refine Type of Request from Assignment-Level List of Values (LOV) Requirement Statement: The system shall allow the Government Task Manager to select a refined Type of Request from an expanded List of Values (LOV), specific to assignment-level tasking needs. Example values include but are not limited to:

  •Supply

  •Maintenance

  •Equipment Return

  •EOP (Equipment Optimization Plan)

  •M2OG (Material Management Operating Group)

  •Data Analysis

  •Transportation

  •Inventory Adjustment

  •Customer Assistance

  •Technical Support This refined list is used for downstream reporting, routing logic, and priority scoring.

  REQ-4.3 - Title: Assign and Update Task Request Status Requirement Statement: The system shall allow the Government Task Manager or authorized personnel to assign and update the Task Status field using a predefined set of values, including:

  •Pending Review

  •Working

  •Awaiting Information

  •Awaiting Shipment

  •Assigned

  •Response Provided

  •Returned

  •Closed

  •Reopened

  •Cancelled Task Status shall be system-audited and version-controlled with timestamps and user ID for all changes.

  REQ-4.4 - Title: Derive and Apply Task Priority Using UMMIPS Format Requirement Statement: The system shall enable the Government Task Manager to assign task Priority using UMMIPS-aligned urgency formatting (e.g., “01-F/AD I UND A”), composed of:

  •Force/Activity Designator (F/AD I–III)

  •Urgency of Need Designator (UND A–C) This value may be either manually selected or automatically derived based on business logic using task metadata (e.g., Request Type, Mission Dependency, Source of Request, Equipment Type).

  REQ-4.5 - Title: Permit Authorized Priority Overrides Requirement Statement: The system shall allow authorized personnel to override automatically derived UMMIPS priority values when validated by supporting justification or command authority. All overrides shall be logged and require a mandatory justification note.

  REQ-4.6 - Title: Record Task Approval Date and Approving Official Requirement Statement: Upon assignment of a CTTT Tracking Number, the system shall capture and store the Task Approval Date/Time and Approving Official (Full Name and Role) as part of the official task metadata.

  REQ-4.7 - Title: Assign Task to Action Office or Entity Requirement Statement: The Government Task Manager shall be able to assign the task to a designated Action Officer, Team, or Organizational Entity (e.g., Warehouse Ops Team, WSMC Branch, etc.), based on role-based selection menus. Assignment metadata shall be included in the task header and used to generate routing logic and notifications.

  REQ-4.8 - Title: Editable Assignment Fields by Authorized Users Requirement Statement: During the Task Acceptance/Assignment phase, all assignment-related fields (e.g., Refined Type of Request, Status, Priority, Assigned Entity) shall remain editable by users with elevated permissions (e.g., Task Manager, CTTT Admin, ELMS PMO) until the task is officially moved to "Working" status.

  REQ-4.9 - Title: Task Routing Audit Trail Requirement Statement: The system shall maintain an audit log of all assignment actions, including field changes, status updates, and reassignments, with time stamps and user ID visible through the task’s activity history tab for transparency and compliance tracking.

  REQ-4.10 - Title: Task Assignment Comment Block Requirement Statement: The system shall provide a required Assignment Comments text box during task approval/assignment for the Task Manager to enter rationale, expectations, or context for the task. This comment shall be visible to all task participants and remain part of the permanent record.

  E.

  CTTT – Task Acceptance, Approval, and Assignment Requirements (Requirement Group 5.0: WORMG Assignment, Task Assessment, Equipment Status, Document Tracking)

  REQ-5.1 - Title: Assign Work Order Resource Manager Group ID (WORMG_ID) Requirement Statement: The system shall provide the Government Task Manager with a searchable List of Values (LOV) for selecting a Work Order Resource Manager Group Identification Number (WORMG_ID). The format shall follow [DODAAC]-[Command]-[Functional Area], such as:

  •M98822-LOGCOM-DISPO

  •M67854-MARCORSYSCOM-ENGSUP This value shall be stored as a primary grouping element for analytics, reporting, and workload segmentation.

  REQ-5.2 - Title: Capture and Store Task Assessment Problem Statement Requirement Statement: The system shall include a required Task Assessment Problem Statement field for the Task Manager to input a succinct operational-level summary of the task’s underlying issue or challenge. This problem statement should be written in a clear, mission-relevant format suitable for command reviews and risk discussions (max 2000 characters).

  REQ-5.3 - Title: Capture Operational Status of Selected Equipment (When Applicable) Requirement Statement: If the task involves specific equipment, the system shall display an Operation Status dropdown for the Task Manager to select one of the following predefined values:

  •Supply Action Pending

  •In-Service

  •Out-of-Service

  •Awaiting Parts

  •Transferred

  •Disposed

  •Returned to Stock This field shall appear conditionally based on the equipment metadata fields entered during task creation.

  REQ-5.4 - Title: Assign USMC Document Number (When Applicable) Requirement Statement: For applicable tasks (e.g., involving property movement, supply issue/return, or disposition), the system shall allow the Task Manager to generate and assign a USMC-standard Document Number using the format:

  [DODAAC]-[Julian Date]-[4-digit Serial Number] Example: M98822-2135-0001 This document number shall be uniquely associated with the CTTT tasker and linked to any subsequent logistics transactions, audit logs, or warehouse actions.

  REQ-5.5 - Title: Ensure Document Number Uniqueness and Reusability Controls Requirement Statement: The system shall ensure that each generated Document Number is unique per DODAAC and Julian date and may not be reused for another task. In the case of correction or cancellation, the Document Number must retain association with the original task ID and reflect its changed status.

  REQ-5.6 - Title: Editable Fields by Authorized Task Owners Post-Acceptance Requirement Statement: Fields in this section (WORMG_ID, Task Assessment, Operational Status, Document Number) shall remain editable during the Task Acceptance/Assignment phase by authorized personnel (e.g., Task Lead, Program Manager, CTTT Admin), and locked once the task reaches “Working” or “Open” status unless elevated access rights are applied.

  REQ-5.7 - Title: Link Document Number to Audit Trail and Transactions Requirement Statement: The assigned Document Number shall be linked to the CTTT task audit trail and visible in all task-related transactions, comments, or document uploads to ensure traceability and alignment with USMC logistics audit standards (e.g., FIAR compliance).

  REQ-5.8 - Title: Conditional Prompt for Document Number Generation Requirement Statement: The system shall prompt the Task Manager to generate a Document Number only when applicable task types are selected (e.g., “Supply,” “Return,” “Disposition”), reducing clutter for non-logistics task types (e.g., Training, IT, Policy).

  REQ-5.9 - Title: Document Number History View Requirement Statement: For any task assigned a Document Number, the system shall allow users with view permissions to access a Document History View showing the original number, issuing official, timestamp, and any status changes or transaction references (e.g., DD1348, shipping label, RCN).

  F.

  CTTT – Task Creation and Tracking Requirements (Requirement Group 6.0: Sub-Task Tasking, Assignment, and Workload Deconfliction)

  REQ-6.1 - Title: Assign Task to Individual or Group within WORMG_ID Requirement Statement: The system shall allow the Task Lead to assign individual task records to any authorized individual user or group entity associated with their assigned WORMG_ID, with role-based controls to prevent assignment outside their organizational scope.

  REQ-6.2 - Title: Split Parent CTTT into Multiple Sub-Tasks Requirement Statement: The system shall allow the Task Lead to logically split the parent CTTT record into an unlimited number of Sub-Task taskers, each assigned a unique Sub-Task Number using a suffix linked to the parent task (e.g., M98822-CTTT-250527-0003-01, -02, etc.). All Sub-Task taskers shall maintain a reference link to the parent task record.

  REQ-6.3 - Title: Assign Sub-Task Task Status Requirement Statement: Each Sub-Task shall have an independently assigned Task Status from the following predefined list:

  •In Planning

  •Assigned

  •Cancelled

  •Completed

  •Closed Sub-Task task statuses may differ from the parent task status and shall be independently tracked and reportable.

  REQ-6.4 - Title: Select Owner Type from LOV Requirement Statement: For each Sub-Task, the Task Lead shall select an Owner Type from a dropdown List of Values (LOV), including:

  •Employee Resource

  •Group Resource

  •Supplier Contract

  •Team Resource This value enables accurate reporting and contracting data integration (if applicable).

  REQ-6.5 - Title: Assign Sub-Task Task to Individual by ELMS User ID Requirement Statement: When assigning a Sub-Task to an individual, the system shall

  allow the Task Lead to search by ELMS User ID or name and automatically populate associated contact fields (e.g., email, phone, role, location).

  REQ-6.6 - Title: Enter Sub-Task Task Subject Requirement Statement: Each Sub-Task shall have a unique subject label (max 100 characters) that distinguishes it from other subtasks and reflects the discrete nature of the assigned work.

  REQ-6.7 - Title: Enter Sub-Task Description Requirement Statement: The Task Lead shall be required to enter a brief narrative description (max 1000 characters) to clarify the scope, expectations, or deliverables of each Sub-Task.

  REQ-6.8 - Title: Set Scheduled Start Date via Calendar Selector Requirement Statement: The system shall allow the Task Lead to set a Scheduled Start Date for each Sub-Task task using a calendar pop-up interface with date validation against the parent task start date.

  REQ-6.9 - Title: Set Forecast Completion Date via Calendar Selector Requirement Statement: The system shall allow the Task Lead to set a Forecast Completion Date using a calendar pop-up, with validations to ensure the end date is after the start date and within parent task parameters (unless override permission is granted).

  REQ-6.10 - Title: Automatically Calculate Task Period Requirement Statement: The system shall automatically calculate and display the Task Duration in business days based on the Scheduled Start Date and Forecast Completion Date, providing visual confirmation to the Task Lead.

  REQ-6.11 - Title: Alert for Task Scheduling Conflict / Overload Requirement Statement: The system shall perform a Schedule Deconfliction Check by assessing the total number of overlapping task assignments per user or group. If a task period exceeds recommended load thresholds (e.g., >3 concurrent Sub-Task assignments), the system shall issue a warning alert to the Task Lead with an option to proceed or reassign.

  REQ-6.12 - Title: Link Sub-Task Task Completion to Parent Task Workflow Requirement Statement: The system shall automatically update the parent task record with a Sub-Task Task Completion Summary (e.g., 3 of 5 subtasks completed) and provide a visual progress tracker within the parent CTTT dashboard view.

  G.

  CTTT – Sub-Task Notes and History Requirements (Requirement Group 7.0: Task Executor Activity Capture, Documentation, and Sub-Tasking)

  REQ-7.1 - Title: Create Unlimited Sub-Tasks from Assigned Task Requirement Statement: The system shall allow Task Executors to create an unlimited number of Sub-Tasks under any assigned Tier-1 task. Each Sub-Task shall be assigned a unique sequence number with a hierarchical reference linking it to the parent Tier-1 and original CTTT (e.g., M98822-CTTT-250527-0003-01-001).

  REQ-7.2 - Title: Assign Sub-Task Start Date via Calendar Selector Requirement Statement: The system shall allow the Task Executor to assign a Start Date for each Sub-Task using a calendar pop-up tool, with system checks to ensure the date falls within the scheduled duration of the parent task unless override permissions are enabled.

  REQ-7.3 - Title: Select Type of Sub-Task from Predefined LOV Requirement Statement: The system shall require the Task Executor to select a Type of Sub-Task from a configurable dropdown List of Values (LOV), including but not limited to:

  •Investigation

  •Manufacture

  •Miscellaneous Task

  •Purchase Order

  •Recovery

  •Request for Disposition

  •Requisition Resource Move

  •Salvage

  •Selective Interchange

  •Service This value shall support operational categorization and downstream workflow/routing rules.

  REQ-7.4 - Title: Assign Sub-Task to User via ELMS User ID Requirement Statement: The Task Executor shall be able to assign a Sub-Task to any ELMS-authorized user by querying the ELMS User ID, which shall auto-populate user details (name, email, organizational affiliation) for task routing and communication.

  REQ-7.5 - Title: Record Secondary Response Note Requirement Statement: The system shall provide a Secondary Response Note dialog box for Task Executors to document key insights, decisions, actions taken, or clarifying remarks related to Sub-Task execution. Notes shall support rich-text entry and be stored with a timestamp and user ID.

  REQ-7.6 - Title: Select Sub-Task Status Requirement Statement: Each Sub-Task shall carry its own Status Field, editable by the assigned user or Task Executor, with the following valid values:

  •In Planning

  •Assigned

  •Cancelled

  •Completed

  •Closed The status field shall update Sub-Task dashboards and roll up progress indicators at the parent task level.

  REQ-7.7 - Title: Enable Attachment Upload Option Requirement Statement: The system shall present users with a binary Upload Attachments option (Yes/No). If “No” is selected, the file upload section shall be skipped. If “Yes,” upload fields will be presented for further entry.

  REQ-7.8 - Title: Select Attachment Data Type from Dropdown LOV Requirement Statement: If file upload is enabled, the system shall require users to select the Attachment Data Type from a List of Values (LOV), including but not limited to:

  •SL-3 (Stock List)

  •LTI (Limited Technical Inspection)

  •DD-1348 (Issue/Turn-in Document)

  •DD-1149 (Transfer Document)

  •GBL (Government Bill of Lading)

  •Technical Drawing

  •Photographic Evidence

  •Maintenance Log The LOV shall be configurable to support additional document types.

  REQ-7.9 - Title: Provide Description for Uploaded Attachment Requirement Statement: For each uploaded file, the system shall require a brief user-provided description (max 500 characters) to explain the content and relevance of the attachment. This information shall be searchable in the task document repository.

  REQ-7.10 - Title: Close-Out Functionality for Sub-Tasks and Parent Tasks Requirement Statement: Upon marking a Sub-Task or Parent Task as “Closed,” the system shall automatically archive the following in a structured and retrievable format:

  •All communications and Secondary Response Notes

  •Sub-Task details and execution metadata

  •User assignments and status changes

  •All associated file attachments and document metadata This archive shall be viewable under a historical tab and exportable as part of the CTTT audit package.

  H.

  CTTT – Notifications, Routing Rules, and Alerting Functions (Requirement Group 8.0: System-Driven Communications and Escalation Management)

  REQ-8.1 - Title: Notification of Task Creation Requirement Statement: The system shall send an automated email and ELMS dashboard notification to the Government Task Manager upon submission of a new task by a Task Initiator, including task metadata (title, description, initiator info, priority).

  REQ-8.2 - Title: Notification of Task Assignment Requirement Statement: The system shall notify all assigned Individuals and Groups via email and system dashboard when a task, Tier-1 task, or sub-task has been assigned to them, including task title, due dates, and required actions.

  REQ-8.3 - Title: Role-Based Routing Logic Requirement Statement: The system shall apply role-based routing rules to ensure tasks are routed automatically to the correct Task Manager, Action Office, or Program Owner based on metadata such as:

  •Type of Request

  •DoDAAC / WORMG_ID

  •Task Category

  •Equipment Type (if applicable) Routing rules shall be configurable and maintained by CTTT administrators.

  REQ-8.4 - Title: Notification on Status Changes Requirement Statement: The system shall generate an automated notification to assigned users and stakeholders when any of the following status changes occur:

  •Task Status

  •Tier-1 Task Status

  •Sub-Task Status

  •Priority Change The notification shall include who made the change, when it occurred, and any associated comments.

  REQ-8.5 - Title: Deadline-Based Alerts Requirement Statement: The system shall issue automated alert notifications when the following conditions are met:

  •72 hours before scheduled due date (reminder)

  •On due date (alert)

  •Overdue status (escalation notification sent to Task Lead and PMO)

  REQ-8.6 - Title: Escalation Notifications Requirement Statement: The system shall escalate overdue tasks based on their priority as follows:

  •Critical/Urgent tasks escalate at 24 hours overdue

  •High tasks escalate at 72 hours overdue

  •Medium/Routine tasks escalate at 5 business days overdue Escalations shall be sent to the assigned user, Task Lead, and responsible Government Task Manager.

  REQ-8.7 - Title: In-App Dashboard Alerts Requirement Statement: The system shall display all alerts in a user-specific dashboard under an "Action Required" panel, with filterable categories (e.g., Assigned to Me, Overdue, Due This Week, Awaiting My Review).

  REQ-8.8 - Title: Custom Notification Preferences Requirement Statement: Users shall be able to configure notification preferences (e.g., email, in-app, daily digest, real-time alert) from a personal settings menu, while critical alerts (e.g., overdue, escalations) shall remain mandatory.

  REQ-8.9 - Title: Routing Failover Logic Requirement Statement: If automated task routing fails (e.g., no responsible Task Manager found for routing rule), the system shall route the task to a designated CTTT Default Manager Queue and alert the PMO for reassignment within 1 business day.

  REQ-8.10 - Title: Real-Time Activity Feed Requirement Statement: Each CTTT task shall include a real-time Activity Feed viewable by stakeholders showing:

  •User actions

  •Comments

  •Sub-task changes

  •Document uploads

  •Notifications sent This feed shall serve as a system-of-record for communication traceability.

  REQ-8.11 - Title: Digest Summary Report Requirement Statement: The system shall provide users with an optional daily or weekly digest report via email, summarizing:

  •Assigned tasks

  •Tasks nearing due dates

  •Tasks recently completed

  •Notifications received Digest content and frequency shall be user-configurable.

  REQ-8.12 - Title: Alert on Excessive Concurrent Assignments Requirement Statement: If an individual is assigned more than a system-defined threshold of concurrent tasks (e.g., 5 open Tier-1 tasks), the system shall alert the assigning Task Lead and suggest workload review or reassignment.

  I.

  CTTT – Dashboard Requirements (Requirement Group 9.0: User Dashboard, Visualization, and Workload Awareness)

  REQ-9.1 - Title: Role-Based Dashboard Customization Requirement Statement: The system shall provide role-based dashboards tailored to each user’s function, including:

  •Task Initiator

  •Task Executor

  •Task Lead

  •Government Task Manager

  •ELMS PMO/Admin Each role-specific view shall include widgets, filters, metrics, and charts relevant to the user’s responsibilities and access rights.

  REQ-9.2 - Title: My Tasks Widget Requirement Statement: The dashboard shall include a “My Tasks” widget displaying all tasks, Tier-1 taskers, and Sub-Tasks assigned to the user, sortable by:

  •Priority

  •Due Date

  •Status

  •Last Activity

  •Parent CTTT Number

  REQ-9.3 - Title: Assigned Team Tasks View Requirement Statement: Users with group assignment roles (e.g., Task Lead or WORMG_ID Owner) shall have access to a “Team Tasks” tab showing all active tasks for their team or WORMG_ID group, with filtering by individual assignee, task type, or due date.

  REQ-9.4 - Title: Task Status Summary Panel Requirement Statement: The dashboard shall provide a status summary visualization showing total tasks across the following statuses:

  •In Planning

  •Assigned

  •Working

  •Awaiting Information

  •Completed

  •Closed

  •Overdue This panel shall support drill-down into each category.

  REQ-9.5 - Title: Calendar View of Tasks Requirement Statement: The dashboard shall offer a calendar view of all assigned or managed tasks (parent and Tier-1) that displays:

  •Scheduled Start Dates

  •Forecast Completion Dates

  •Due Date Alerts Color-coded entries shall reflect task status or priority.

  REQ-9.6 - Title: Visual Priority Indicator Requirement Statement: Tasks on the dashboard shall include a visual priority indicator (color-coded or icon-based) based on UMMIPS priority code (e.g., 01-F/AD I UND A) to highlight critical and urgent taskings for fast triage.

  REQ-9.7 - Title: Filter and Search Capabilities Requirement Statement: The dashboard shall provide advanced filtering and search options based on:

  •Task Number (any level)

  •DoDAAC / WORMG_ID

  •Task Owner / Assignee

  •Type of Request

  •Equipment NSN or TAMCN

  •Priority

  •Status Filters can be saved as user-defined views.

  REQ-9.8 - Title: Notifications Panel Requirement Statement: The dashboard shall include a real-time notifications panel showing alerts, escalations, overdue tasks, task acceptance requests, and file upload notifications. Users can mark notifications as read or archive them.

  REQ-9.9 - Title: Task Progress Charts Requirement Statement: The system shall support dashboard charts that visualize:

  •% of Tier-1 Tasks Completed per Parent Task

  •Tasks Closed vs Open by Time Period

  •Sub-Task Completion Trends

  •Assignment Load by Individual or Group Charts shall be exportable and drillable to underlying task records.

  REQ-9.10 - Title: Overdue Task Tracker Requirement Statement: Each dashboard shall include an “Overdue Task Tracker” section

  listing all tasks that have exceeded their Forecast Completion Date, sortable by days overdue, assigned user, or priority.

  REQ-9.11 - Title: Export Dashboard Data Requirement Statement: Users shall be able to export dashboard data into common formats (e.g., Excel, PDF, CSV) for reporting, data calls, or analysis, with the option to apply current filters to the export set.

  REQ-9.12 - Title: Quick Access to Recently Viewed Tasks Requirement Statement: The dashboard shall include a “Recently Viewed Tasks” section listing the last 10 task records (any level) accessed by the user, enabling fast navigation back to ongoing work.

  REQ-9.13 - Title: Dashboard Refresh Interval Requirement Statement: The dashboard shall refresh automatically every 5 minutes and also support a manual refresh button to pull the latest task and status information in real-time.

  REQ-9.14 - Title: Dashboard Configurability Requirement Statement: Users shall have the ability to configure their dashboard layout (e.g., drag-and-drop widgets, hide/show components, save personalized layouts) while retaining system-default dashboards for enterprise standards.

  J.

  General Requirements

  REQ-10.1 - The system shall support the use of controlled List of Values (LOVs) for all dropdown fields defined in CTTT requirements (i.e., Task Type, Sub-Task Type, Owner Type, Priority, Attachment Data Type, etc.). During solution development, the MARCORLOGCOM Implementation Lead shall collaborate with the ELMS PMO development team to define, validate, and finalize each LOV to ensure alignment with enterprise standards, user roles, and business processes. All LOVs shall be system-configurable to support future updates and enterprise governance.

  REQ-10.2 – Expanded Routing Rules. Following assignment of a Work Order Resource Manager Group Identification Number (WORMG_ID), the system shall apply additional task routing logic within the Material Management module. Specifically, ELMS shall route applicable tasks to the designated Inventory Manager based on the associated Program Name and Materiel Designator Code (MDC) in accordance with existing Material Management routing protocols. This ensures that logistics tasks requiring item-level disposition, coordination, or oversight are properly aligned with responsible inventory authorities, enhancing traceability, responsiveness, and accountability.

  REQ-10.3 – Problem Descriptions. The system shall provide an expanded free-form text field labeled Problem Description, with a minimum character limit of 3,000, and support for longer entries to accommodate detailed task narratives such as Disposition Instructions for Turn-Ins. Additionally, the system shall allow users to upload disposition instructions as a file attachment in lieu of, or in addition to, the text field. Supported file types shall include PDF, DOCX, and TXT, and the uploaded document shall be linked directly to the task record for traceability, user reference, and audit compliance. This functionality shall mirror and expand upon the Problem Description format used in GCSS-MC induction records, while meeting the broader requirements of ELMS logistics workflows.

   

  Note: the following Disposition Instruction example is provided for REQ 10.3 clarification and to demonstrate the type of task response and data upload requirement that are routinely executed. DISPOSITION INSTRUCTIONS FOR AAV P7 DIVESTMENT CROWS EQUIPPED VEHICLES – TO ALBANY
  

  THE FOLLOWING TAMCN, NSN, SR & SN’s ARE APPLICABLE: TAMCN: E0846

  NSN: 2350-01-458-7410

  SR: 36330892

  SN(s): 522492, 522609, 522689, 522756, 522943, 522995, 523007

  QTY: 07

  1.Units are to retain SL-3's and redistribute within the unit, the AAV community or send to DRMO.

  2.It is authorized that CROWS configured AAV-P7s may be harvested for LRU items identified in the tables below prior to divestment. Unit is required to debrief the CROWS (1090-01-682-2770 NSN) from the vehicle.

  3.The affected unit will collect up all LRU that make up the CROWS (1090-01-682-2770), retire the (1090-01-682- 2770 NSN) serial number, and then turn in LRU to the appropriate Repairable Issue Point (RIP) under turn-in without issue.

  4.Units will then DRMO remaining portion of the CROWS as the rest of the AAV-P7 is sent for divestment.

  5. Unit is to remove all EAAK from assets returning to LOGCOM. EAAK is to be disposed of through local means. If units possess unserviceable EAAK plates on assets being retained, they are to selectively interchange with serviceable panels pending DRMO. No AAV’s are to be returned to LOGCOM with EAAK installed on or contained in the vehicle.

  6.For Communication equipment, Weaponry and Computer/Data storage devices:

  *Unit is required to break parent/child relationships in GCSS-MC from the respective vehicle.

  *Unit is required to submit separate SR's requesting Disposition from the respective WSMT Teams:

  -Weapons - Contact 

  -Communication Equipment – Contact 

  -Computer/Digital Data Storage Devices - Contact 

  * Unit is to leave any 7800i INTERCOM upgrade installed and return with AAV.

  7.In addition to those items called out in the AAV FoV Disposal Plan (DP) for unit level removal, the following items are hereby directed to be removed from each vehicle prior to shipping and disposed of locally by the using unit:

  - Taillight NSN 6620-00-669-5623 - Qty (2)

  NOEM

  NSN

  PART NUMBER

  ARMAMENT SUBSYSTEM: M153A5

  1090-01-682-2770

  60201886-13-C01-L01

  Armament Subsystem, Remotely operated

  1090-25-161-6440

  60201888-01-C01-L01

  Bracket Mounting (LSSA)

  5340-25-161-7073

  60205363-00-C01-L01

  Right Side Support Assembly (RSSA)

  1005-25-161-6922

  60205362-00-C01-L01

  THERMAL IMAGING MODULE (TIM)

  5855-25-160-7363

  8404363-2

  Sight Servo Assembly

  5860-25-161-6459

  60202017-01-C01-L01

  Cradle, Machine Gun (Soft Mount)

  1005-25-162-0443

  60235616-01-C01-L01

  Visual Imaging Module (VIM)

  5895-25-161-7071

  60235971-00-C01-L01

  Range Finder, Laser

  1240-25-161-3161

  60233586-00-C01-L01

  Grip Assembly, Controller, Weapon (CG)

  1290-25-160-3141

  60205254-00

  Control, Optoelectronic display (DCP)

  5980-25-160-3143

  68113473-02

  Electronic unit, Fire control computer (MPU)

  1220-25-160-5111

  68113472-02

  W2 & W3 Connector Cap Kits consist of:

  NOEM

  NSN

  PART NUMBER

  *CLAMP,LOOP,

  5340-01-543-3594

  S325SSG12

  COVER,ELECTRICAL CONNECTOR

  5935-01-282-7231

  D38999/33W19R

  *COVER,ELECTRICAL CONNECTOR

  5935-01-282-7232

  D38999/32W19R

  Screw, Cap, Socket Head

  5305-12-390-0050

  ISO 7380-1-M4X12-A4-70

  *Washer, Flat

  ISO 7089-4-200 HV-A4

  *Washer, Lock

  AEW16X40M000WJ7A11

  *Nut, Plain, Hexagon

  5310-01-306-9820

  Iso 4032-M4-A4-70

  - Dome Light NSN 6220-00-337-7463 - Qty (5)

  - Radio Stack lights NSN/NIIN 01-421-0093 (C), 01-444-1218

  8.Vehicles are to be relatively clean and free of any oil, trash, or debris in the back. Absolutely no excess spare parts to be returned in the back of vehicle.

  - Questions concerning the above are to be directed to the AAV Weapon System Support Manager

  IMPORTANT: *DO NOT* return any of the aforementioned assets, SL-3 back to LOGCOM in the vehicle.

  Vehicle is to be shipped with no more than ¼ tank of fuel contained in the fuel tanks.

  * ADDITIONAL REMARKS:

  Unit required to change condition code of assets to condition code F.

  KSD’s (LTI, DD FORM 1348, 1149) are required to be loaded to this service request, per HQMC.

  9. SHIP TO INSTRUCTIONS:

  - Induct Material Redistribution inside of this Service Request in GCSS-MC, PRIOR TO PHYSICALLY SHIPPING to

  DODAAC MMSA51, RIC MSA.

  DODAAC: MMSA51, RIC: MSA

  Distribution Management Office Wilkinson Way, BLDG 1221 Door 20 MF: MMSA51, 2D Force Storage BN Albany GA 31704-5000

  TAC Code M2LL Applies

  
  

  Mission Critical:

  OMB Circular A-123 and DoD FIAR guidance

   

  Benefits:

  - Meets MARCORLOGCOM's business model

  - Assists in 100% accountability of assets

  - Complies with current audit controls 

  
  

  Frequency: 

  Daily

  
  

  Users: 

  All USMC Users

×

×

Welcome to the NEW ELMS Support Site. You may still see some documents or other items still referencing DPAS, but we are working to update our remaining content as soon as possible. Be sure to update your bookmark to https://elmssupport.golearnportal.org.

 

Please note that the URL for the live Production environment has changed due to the ELMS name rebranding process. The new URL for ELMS Production is: https://prod.elms.dla.mil