DOCUMENT
B. Industry Day Slides 030622.pdf
OVERVIEW
Original Source
Contract Opportunity
Related Opportunity
Related Agency
Posted
June 23, 2022
Type
.pdf
Size
3.21MB
DOCUMENT PREVIEW
EXTRACTED TEXT
PMW 230 Logistics Integrated Information Solutions
Marine Corps (LI2S-MC)
Industry Day
08 June 2022
Admin Notes
Location Set Up
Restrooms
Places to eat
Schedule
Rules of Engagement
2
Why Are We Here?
Where are we?
LI2S-MCs current portfolio of capabilities
Why are we changing?
Historical Information
Problem Set
Where are we going?
CONOPS and ICD
USMC LOG IT C2 Roadmap
What now? What dont we know?
Industry Questions, Answers, & Clarifications
RFI
Critical Data Analysis and Capability-Based Assessment ISO of the
3
Where Are We?
We sustain and transform the Marine Corps
logistics information technology capability.
LI2S Mission
5
Organizational Chart
PdM Global Combat Support System
Marine Corps (GCSS-MC)
GCSS-MC Mission
To develop and implement deployable, leading-edge technology
that enables logistics modernization and maximizes combat
effectiveness of the Marine Corps through improved logistics
visibility.
GCSS-MC Vision Statement
High performing professionals delivering the most advanced,
intuitive, reliable and capable system to support the Marine
Corps logistics operations.
Operations Team manages daily
GCSS-MC operations to support
System Users. Responsibilities
include: deployed operations
support, GCSS-MC Operations
Center, Enterprise Service Desk,
Continuity of Operations Planning
and Training.
PdM GCSS-MC Teams
New Capabilities Development
Team manages the development
and deployment of all new
capabilities. NCD Team efforts
include: Fixed Asset Module, Mobile
Field Service, E-Mail Mobile Query,
and Desktop Virtualization.
Sustainment Team ensures GCSS-MC
meets operational performance
expectations and system services are
available to GCSS-MC Users. This
includes hardware/software
management, obsolescence, tech
refresh and interface performance/
management
PdM GCSS-MC (contd)
PdM Data Environment & Integration (DE&I)
1. Advanced Tech
DDIL will extend user access to GCSS-MC
capabilities to all operational environments,
specifically to disadvantaged networks and
disconnected environments to better support
garrison, shipboard, and expeditionary operational
environments.
IUID establishes unique item identifiers (UII) within
the DoD by assigning a machine-readable
character string or number to a discrete item,
which will interface with Global Combat Support
System-Marine Corps (GCSS-MC) / Logistics Chain
Management (LCM).
Joint Systems
Adv.
IUID/IMC
4. LDS/DaaS
LDS will focus on data preparation and access
including data modeling, design and integration
into common functional schemas, building of a
single USMC Logistics Data Warehouse,
supporting Business Intelligence (BI), Analytics,
Machine Learning (ML) and Artificial Intelligence
(AI).
LDS Phase 2 will make data via Marine Corps
Enterprise Network (MCEN) for analytics, which
retains current Enterprise Ground Equipment
Management (EGEM) governance board defined
business operations of EGEM Data Repository
(EDR) and Master Data Repository (MDR) by
creating a cloud-based data hub.
Daas
TDM-CATALYST
TDM-Publications
2. Logistics Digitial
Transformation
TDM-CATALYST and TDM-Publications
synchronize weapons systems
requirements data from TFSMS and
technical data from industry to provide
accurate data in GCSS-MC to the
warfighter, and registers vetted,
accurate demand signals to the rest of
the Department of Defense.
Tech & Non
Tech
Publications
3. Enterprise Logistics Support
Services
Legacy ELS2
Applications
MCDSS,
WRS and
TDM-CATALYST provides capabilities for
provisioning and cataloging, and subsumes
the functionality of the MICAPS, ITEM APPS,
TDMS and Provisioning.
In FY22 additional capabilities for technical
and non technical publications and subsume
APS, Tech Pub Library, NAVMC, LOGWAY,
PLMS, MCPDS and SL-1/SL-2/SL-3) ELS2 will
continue to support MCDSS, TMS and WRS.
PdM Tactical Logistics Systems (TLS)
TLS Mission
To develop, sustain and deploy enterprise and disconnected
mobile logistics information technology tools in support of
garrison and operational forces in low bandwidth/degraded
environments. Tactical Logistics Systems will provide enhanced
visibility for commanders dashboard, transportation
management and warehousing and inventory management
systems thereby increasing logistics visibility and capability to
the Marine Corps.
TLS End State Technology
Fully synchronized, automated, integrated, and innovative 21st
century technologies supplying the Marine with real-time and
accurate logistics data from both the garrison and operational
environment.
Why Are We Changing?
Historical Background and Problem Set
At this time, the only portion of the high-level GCSS-MC Capability Development Document
requirements that was decomposed into an actionable set of lower level requirements for
supply and maintenance in the LCM increment one Capability Production Document.
Much of the LI2S-MC portfolio of today is still GCSS MC increment 1 and a collection of
legacy Business Information Technology (IT) programs which were developed individually to
address specific Logistics Business IT functions with minimal consideration for integration
across the portfolio.
(hardware, software,
Due to technology limitations at
bandwidth), these systems do not support logistics in a contested battlespace to the extent
needed.
the time of development
The lack of current integrated requirements and Concept of Operations (CONOPS) has
limited the availability of funding and resources and hamstrung any ability for rapid
capability development not based on historical requirements, this has limited the ability to
provide operators with an integrated solution that encompasses all the capabilities of these
legacy systems and limited development of new capabilities.
Where Are We Going?
Future Intent
USMC intent is to replace the numerous legacy LOG IT systems with a Log IT C2
capability that operates in a disconnected, disadvantaged environment and acts as
the user interface to GCSS-MC. (Estimated contract award FY 26).
14
Logistics Information Technology
Command & Control (C2) Roadmap
Model Based Mission Engineering (MBME)
Strategy
The disciplined and consistent implementation of model-based engineering at the
Enterprise level to:
Enable Marine Corps operational logistics success in contested operating environments, with a
specific focus on tactical logistics functions as described in the Marine Corps Expeditionary
Advanced Basing Operations (EABO) future operating concept.
Model logistics IT systems capable of supporting operations in Denied, Degraded, Intermittent, and
or Latent (DDIL) communications and otherwise contested operating environments.
The LOG IT C2 Working Group
Is comprised of a broad array of representatives from DC I&L, DC CD&I, PM LI2S, Logistics
Command and the Fleet Marine Force.
Integrates the approved scenarios, wargame outputs, and logistics subject matter expertise into
an integrated set of models and requirements that enable Expeditionary Advanced Base
Operations (EABO).
MBME Approach to deliver LOG IT C2 Capability
Phase 1: Establish LOG C2/IT priorities (Scenarios / Vignettes)
Establish a prioritized backlog of vignettes that will fuel model development and ultimately
the MBME analysis that will shape the CBA.
Phase 2: Define the current state operations and architecture
Develop models of current state operations in Business Process Model and Notion (BPMN)
that depict the mission threads.
Identify the current state enablers that support the mission thread. These systems in
aggregate comprise the current state architecture.
Phase 3 Identify the current state capability gaps and threats
Scan the current state mission threads and enablers to identify potential gaps and threats
created by the implementation of EABO.
Phase 4 Identify future state operations and architecture
Develops future state mission threads and determine required future enablers.
Phase 5 Conduct model-based analysis
EXAMPLE of Phase 4
Future State Operator Maintenance Thread
Model-Based Analysis
What if analyses to be incorporated into the CBA process include
assessing changes to:
The mission
The capabilities necessary to support the mission
The attributes and standards required to provide effective capabilities
The capability gaps
The operational risks and prioritization of capability gaps
Non-material solutions that can address gaps (i.e. DOTMLPF)
The MMBE (CDA) Output will support the CBA in the development
of CONOPS and Initial Capabilities Documents in support of POM
26 funding initiative for full LOG IT C2 Capability Development and
Delivery.
Endstate
Critical Data Analysis and Capability-Based Assessment ISO of the
CONOPS and ICD
CONOPS and ICD along with the Meta Data Models of to be business
processes and our ongoing interactions(RFIs) produce an RFP which is
well understood and a low risk for you to bid to.
CONOPS+ICD +
Outcome of RFI = RFP
Industry
builds
MVP1 of
LOG IT C2
Capability
20
Lunch
Industry Day will resume at xxxx
What Dont We Know?
Questions & Answers
What Now?
Next Steps
What does industry want/need from us?
Watch this Space anticipate semi-annual Industry
Days as models and analyses mature
24
RFI Responses
RFI: https://sam.gov/opp/a07c7fa3a26941808562d35801144ac9/view
Expected Products
White Paper on approach to similar issues in the past.
Industry to let us know if a demo will/may/could be provided as supplement
Technologies you have used to solve similar issues (technical solutions
will not be requested until requirements have been received)
25
Key Dates
Industry Day: 9:00 a.m. 4:00 p.m. ET on 8 June 2022.
Questions
Marine Corps (LI2S-MC)
Industry Day
08 June 2022
Admin Notes
Location Set Up
Restrooms
Places to eat
Schedule
Rules of Engagement
2
Why Are We Here?
Where are we?
LI2S-MCs current portfolio of capabilities
Why are we changing?
Historical Information
Problem Set
Where are we going?
CONOPS and ICD
USMC LOG IT C2 Roadmap
What now? What dont we know?
Industry Questions, Answers, & Clarifications
RFI
Critical Data Analysis and Capability-Based Assessment ISO of the
3
Where Are We?
We sustain and transform the Marine Corps
logistics information technology capability.
LI2S Mission
5
Organizational Chart
PdM Global Combat Support System
Marine Corps (GCSS-MC)
GCSS-MC Mission
To develop and implement deployable, leading-edge technology
that enables logistics modernization and maximizes combat
effectiveness of the Marine Corps through improved logistics
visibility.
GCSS-MC Vision Statement
High performing professionals delivering the most advanced,
intuitive, reliable and capable system to support the Marine
Corps logistics operations.
Operations Team manages daily
GCSS-MC operations to support
System Users. Responsibilities
include: deployed operations
support, GCSS-MC Operations
Center, Enterprise Service Desk,
Continuity of Operations Planning
and Training.
PdM GCSS-MC Teams
New Capabilities Development
Team manages the development
and deployment of all new
capabilities. NCD Team efforts
include: Fixed Asset Module, Mobile
Field Service, E-Mail Mobile Query,
and Desktop Virtualization.
Sustainment Team ensures GCSS-MC
meets operational performance
expectations and system services are
available to GCSS-MC Users. This
includes hardware/software
management, obsolescence, tech
refresh and interface performance/
management
PdM GCSS-MC (contd)
PdM Data Environment & Integration (DE&I)
1. Advanced Tech
DDIL will extend user access to GCSS-MC
capabilities to all operational environments,
specifically to disadvantaged networks and
disconnected environments to better support
garrison, shipboard, and expeditionary operational
environments.
IUID establishes unique item identifiers (UII) within
the DoD by assigning a machine-readable
character string or number to a discrete item,
which will interface with Global Combat Support
System-Marine Corps (GCSS-MC) / Logistics Chain
Management (LCM).
Joint Systems
Adv.
IUID/IMC
4. LDS/DaaS
LDS will focus on data preparation and access
including data modeling, design and integration
into common functional schemas, building of a
single USMC Logistics Data Warehouse,
supporting Business Intelligence (BI), Analytics,
Machine Learning (ML) and Artificial Intelligence
(AI).
LDS Phase 2 will make data via Marine Corps
Enterprise Network (MCEN) for analytics, which
retains current Enterprise Ground Equipment
Management (EGEM) governance board defined
business operations of EGEM Data Repository
(EDR) and Master Data Repository (MDR) by
creating a cloud-based data hub.
Daas
TDM-CATALYST
TDM-Publications
2. Logistics Digitial
Transformation
TDM-CATALYST and TDM-Publications
synchronize weapons systems
requirements data from TFSMS and
technical data from industry to provide
accurate data in GCSS-MC to the
warfighter, and registers vetted,
accurate demand signals to the rest of
the Department of Defense.
Tech & Non
Tech
Publications
3. Enterprise Logistics Support
Services
Legacy ELS2
Applications
MCDSS,
WRS and
TDM-CATALYST provides capabilities for
provisioning and cataloging, and subsumes
the functionality of the MICAPS, ITEM APPS,
TDMS and Provisioning.
In FY22 additional capabilities for technical
and non technical publications and subsume
APS, Tech Pub Library, NAVMC, LOGWAY,
PLMS, MCPDS and SL-1/SL-2/SL-3) ELS2 will
continue to support MCDSS, TMS and WRS.
PdM Tactical Logistics Systems (TLS)
TLS Mission
To develop, sustain and deploy enterprise and disconnected
mobile logistics information technology tools in support of
garrison and operational forces in low bandwidth/degraded
environments. Tactical Logistics Systems will provide enhanced
visibility for commanders dashboard, transportation
management and warehousing and inventory management
systems thereby increasing logistics visibility and capability to
the Marine Corps.
TLS End State Technology
Fully synchronized, automated, integrated, and innovative 21st
century technologies supplying the Marine with real-time and
accurate logistics data from both the garrison and operational
environment.
Why Are We Changing?
Historical Background and Problem Set
At this time, the only portion of the high-level GCSS-MC Capability Development Document
requirements that was decomposed into an actionable set of lower level requirements for
supply and maintenance in the LCM increment one Capability Production Document.
Much of the LI2S-MC portfolio of today is still GCSS MC increment 1 and a collection of
legacy Business Information Technology (IT) programs which were developed individually to
address specific Logistics Business IT functions with minimal consideration for integration
across the portfolio.
(hardware, software,
Due to technology limitations at
bandwidth), these systems do not support logistics in a contested battlespace to the extent
needed.
the time of development
The lack of current integrated requirements and Concept of Operations (CONOPS) has
limited the availability of funding and resources and hamstrung any ability for rapid
capability development not based on historical requirements, this has limited the ability to
provide operators with an integrated solution that encompasses all the capabilities of these
legacy systems and limited development of new capabilities.
Where Are We Going?
Future Intent
USMC intent is to replace the numerous legacy LOG IT systems with a Log IT C2
capability that operates in a disconnected, disadvantaged environment and acts as
the user interface to GCSS-MC. (Estimated contract award FY 26).
14
Logistics Information Technology
Command & Control (C2) Roadmap
Model Based Mission Engineering (MBME)
Strategy
The disciplined and consistent implementation of model-based engineering at the
Enterprise level to:
Enable Marine Corps operational logistics success in contested operating environments, with a
specific focus on tactical logistics functions as described in the Marine Corps Expeditionary
Advanced Basing Operations (EABO) future operating concept.
Model logistics IT systems capable of supporting operations in Denied, Degraded, Intermittent, and
or Latent (DDIL) communications and otherwise contested operating environments.
The LOG IT C2 Working Group
Is comprised of a broad array of representatives from DC I&L, DC CD&I, PM LI2S, Logistics
Command and the Fleet Marine Force.
Integrates the approved scenarios, wargame outputs, and logistics subject matter expertise into
an integrated set of models and requirements that enable Expeditionary Advanced Base
Operations (EABO).
MBME Approach to deliver LOG IT C2 Capability
Phase 1: Establish LOG C2/IT priorities (Scenarios / Vignettes)
Establish a prioritized backlog of vignettes that will fuel model development and ultimately
the MBME analysis that will shape the CBA.
Phase 2: Define the current state operations and architecture
Develop models of current state operations in Business Process Model and Notion (BPMN)
that depict the mission threads.
Identify the current state enablers that support the mission thread. These systems in
aggregate comprise the current state architecture.
Phase 3 Identify the current state capability gaps and threats
Scan the current state mission threads and enablers to identify potential gaps and threats
created by the implementation of EABO.
Phase 4 Identify future state operations and architecture
Develops future state mission threads and determine required future enablers.
Phase 5 Conduct model-based analysis
EXAMPLE of Phase 4
Future State Operator Maintenance Thread
Model-Based Analysis
What if analyses to be incorporated into the CBA process include
assessing changes to:
The mission
The capabilities necessary to support the mission
The attributes and standards required to provide effective capabilities
The capability gaps
The operational risks and prioritization of capability gaps
Non-material solutions that can address gaps (i.e. DOTMLPF)
The MMBE (CDA) Output will support the CBA in the development
of CONOPS and Initial Capabilities Documents in support of POM
26 funding initiative for full LOG IT C2 Capability Development and
Delivery.
Endstate
Critical Data Analysis and Capability-Based Assessment ISO of the
CONOPS and ICD
CONOPS and ICD along with the Meta Data Models of to be business
processes and our ongoing interactions(RFIs) produce an RFP which is
well understood and a low risk for you to bid to.
CONOPS+ICD +
Outcome of RFI = RFP
Industry
builds
MVP1 of
LOG IT C2
Capability
20
Lunch
Industry Day will resume at xxxx
What Dont We Know?
Questions & Answers
What Now?
Next Steps
What does industry want/need from us?
Watch this Space anticipate semi-annual Industry
Days as models and analyses mature
24
RFI Responses
RFI: https://sam.gov/opp/a07c7fa3a26941808562d35801144ac9/view
Expected Products
White Paper on approach to similar issues in the past.
Industry to let us know if a demo will/may/could be provided as supplement
Technologies you have used to solve similar issues (technical solutions
will not be requested until requirements have been received)
25
Key Dates
Industry Day: 9:00 a.m. 4:00 p.m. ET on 8 June 2022.
Questions
Show All