Logistics Command

1 / 65
About This Presentation
Title:

Logistics Command

Description:

N A V A L F A C I L I T I E S E N G I N E E R I N G S E R V I C ... Mutual funds are debited/credited at end of each day. Stocks don't break down. There's more ... – PowerPoint PPT presentation

Number of Views:33
Avg rating:3.0/5.0
Slides: 66
Provided by: bobha77

less

Transcript and Presenter's Notes

Title: Logistics Command


1
Logistics Command Control Opportunities
Opportunities for MS Support of CSS C2
Bob Hamber Very few slides have speaker notes
yet. Oh I wish Id written them up after I gave
this brief at the program review. I was all
charged up. A few of these slides have been added
and a few more revised since the ExLog prgm
review.
  • Bob Hamber
  • NFESC
  • Presented to
  • Logistics Forum
  • Fall 2001 Simulation Interoperability Workshop
  • 13 September 2001
  • Orlando, FL

2
Perspectives
  • Presenters background
  • USMC
  • Doctrinal pubs
  • Combat Service Support forward, tactical
    logistics
  • Consumption, ordering, shipping/distribution
  • Constructive MS
  • analytical domain
  • Modeling application developer
  • Simulation setup
  • Innovator
  • Conceptual
  • Systems approach
  • Paradigm shifter

3
Assumptions
  • Current popular initiatives will be in place
  • Focused logistics
  • Velocity management
  • Total asset visibility
  • Seabased logistics
  • Supply chain management
  • Autonomous logistics
  • Digitization of the battlefield
  • Doesnt require
  • Improvements in computing power
  • Improvements in bandwidth
  • Reliable comms

4
Conops Direction
5
What is a Conops?
  • No broadly accepted standard content
  • Examples vary greatly
  • Not a
  • Architecture
  • JTA technical, system, or operational
    architecture
  • Technical reference model
  • Conceptual model of mission space
  • More than a
  • Statement of work
  • Narrative description of what want the system to
    do
  • My take
  • A clear process of generically who, does what,
    when
  • Where, is included as necessary/worthwhile
  • How, implement the process, is not included
    (often is architecture)
  • Why, a supplement if need to sell a new process

6
Fundamentals of Proposed Conops
  • Founded on principles of C2 and Planning
  • OODA loop (Boyd cycle) and MCPP process
  • Planning horizion
  • Deliberate and rapid planning
  • Performs across a range of operations
  • Creates a learning organization
  • Many more -- doctrinal, emerging doctrine
  • Founded on principles of CSS
  • Balanced appropriate for the scenario
  • Doctrinal principles are insufficient for EMW Addl

7
Fundamentals of Proposed Conops
  • Manage (command and control)
  • Processes first
  • Resources second
  • Transactions third by exception
  • Three or four nested decision loops
  • one operation/mission cycle
  • one stage/phase/battle cycle
  • one Period cycle
  • one Transaction cycle

8
Fundamentals of Proposed Conops (contd)
  • Agile
  • Rapidly adjust CSS TTP to dynamic scenario
  • Proactive avoid problems instead of fixing them
  • Key to achieving precision logistics
  • Encompasses precision logistics
  • Intelligence
  • Awareness
  • Forecast
  • Feedback
  • Collaboration
  • Learning
  • Conditional cause and effect

Dont replace human decision making with computer
decision making if the latter doesnt do it
better than the average human it is replacing.
Bob Hamber Check characteristics of Intel Agents
for others might add
9
Fundamentals of Proposed Conops (contd)
Bob Hamber Add automation to list of Intel on
previous slide. Move this to a later detailed
slide and expand.
  • Slowly increase automation
  • DST provides info for human decisions
  • DST provides multiple recommendations for human
    choice
  • DST provides recommendation for human veto
  • DST automatically makes the decision w/o human
    intervention
  • Situational Awareness
  • Mission
  • Enemy
  • Troops and their equipment
  • Terrain and weather
  • Time available
  • Space available
  • External Logistics resources
  • Civilian considerations

Bob Hamber Work in queues? Or just a
process/resource detail?
10
Direction Elaboration
11
Two Processes to Manage
Log Forum Opportunity for standardization?
  • C2 Planning Process calls on MS repeatedly to
  • Mission Analysis
  • COA Development
  • COA Wargame
  • COA Comparison and Decision
  • Orders Development
  • Transition
  • MS the CSS Operations Process
  • Monitor situation
  • Identify task
  • Order task
  • Assign task to performer(s)
  • Fill (performers prep)
  • Route (aggregate entities)
  • Setup at task site
  • Perform task
  • Strike resources
  • Return resources and work
  • Restore resources

MCPP Version
Versions Compared
12
What is Management
Any source Looking for paper on just what
constitutes C2 once computers assist in so many
C2 functions? An expanded lexicon is needed
  • What is management
  • Defining policy options and general conditions
    for use
  • Establishing policies (doctrine)
  • Applying policies to local conditions (tactics)
  • When judgment plays a significant role
  • What isnt
  • Following a specific policy, technique or
    procedure
  • Prioritizing orders per procedures
  • Deploying resources between nodes per procedures
  • Assigning/grouping resources per procedures
  • Tracking, reporting per procedures
  • Recognizing problems when evident or per standard
    criteria
  • Relative to system level
  • Moving target as judgment is codified into
    procedures

13
Process, Process, Process
  • The significance of process it is key to
  • peak CSS system performance
  • Agility
  • CSS Operational C2
  • Tailor the system to the conditions
  • CSS Planning C2
  • COA Analysis

14
The Stock Portfolio Analogy
  • Knowing about the stocks e.g. what stocks
  • You have
  • You have ordered
  • You have bought and when you will get them
  • Others have and are ordering
  • Are for sale and where
  • Knowing about the companies e.g.
  • What their products are
  • How they are selling
  • What their costs are
  • What their research shows
  • What their plans are
  • Insider information

15
The Stock Portfolio Analogy contd
  • Knowing about the economy e.g.
  • What Fed is doing
  • How the industry is doing
  • The economic indicators
  • Long range weather forecast
  • Knowing the causes and effects the processes
    that drive stock values
  • What/who affects value
  • What affects what affect what affects value
  • What affects value when
  • What the interactions are between causes

16
The Stock Portfolio Analogy contd
  • Knowing the processes in effect
  • Currently
  • Planned
  • Knowing a stocks future value probabilities
  • If know all the above,
  • Can build a model, and
  • Can simulate the company performance, economy and
    the market to
  • Predict future stock value
  • If apply distributions to inputs
  • Can predict the probabilities over a range of
    values

17
The Stock Portfolio Analogy contd
  • As a stock investor, what info do you want?
  • Know about the stocks?
  • Know about the companies?
  • Know about the economy?
  • Know about the causes and effects?
  • Know the processes in effect?
  • Know future stock price probabilities?
  • Arent these in order of difficulty of knowing?
  • Except for company insider info
  • Since we dont know the fourth fifth ones very
    well,
  • we cant know the last one very well.

18
Process, Process, Process
  • As a stock investor, what info do you want?
  • Know about the stocks?
  • Know about the companies?
  • Know about the economy?
  • Know about the causes and effects?
  • Know the processes in effect?
  • Know future stock price probabilities?
  • Un-analogy
  • TAV
  • Sit A
  • Sit A
  • Process knowledge
  • TPV
  • CSS future probabilities

19
Process, Process, Process
  • CSS
  • Know about material
  • Know about the combat units
  • Know about the threat, terrain, weather
  • Know how the CSS processes act and interact
  • Know the CSS processes in effect
  • Know future CSS capabilities
  • Generic
  • TAV
  • Sit A
  • Sit A
  • Process knowledge
  • TPV
  • CSS future probabilities
  • Status
  • Well underway
  • Well underway,need to connect
  • Well underway,need to connect, threat info
    limits
  • Know options, dont know interactions
  • No effort to date, big deficiency
  • TLoaDS a good start

20
Process, Process, Process
  • Having the process knowledge and TPV is the key
    to simulation.
  • Process is the key to CSS forecasting.
  • CSS forecasting is the key to powerful CSS C2 COA
    analysis.
  • COA analysis is key to CSS C2
  • CSS C2 is the key to CSS system performance
  • CSS system performance is key to warfighting

21
Differences Between Stock Market and CSS
  • Most CSS processes are far more
  • Mechanistic
  • therefore more Understandable
  • therefore more Predictable,
  • There is, or could be, relatively little human
    behavioral influence compared to stock market
    (and combat)
  • Minor details
  • One stocks are bought, you have them instantly
  • No, check has to clear before can resell
  • Mutual funds are debited/credited at end of each
    day
  • Stocks dont break down
  • Theres more

22
Differences Between Stock Market and CSS
  • The Big One
  • We have control over the CSS processes
  • Hence we have far more control over the system
    performance
  • We can tailor the system to current conditions
  • Many processes can be changed instantly
  • Others take time to implement
  • Once you embark, the only? things the CSSE
    commander has under his control to improve system
    performance is
  • CSS processes (tactics, techniques, and
    procedures)
  • CSS resource allocation (can be considered a
    technique)
  • CSS resource maintenance
  • CSS communications

Most agileCan be least effort
23
The Essential Essence of CSS C2 is Tailoring CSS
Procedures to the Situation
  • The Essential Essence of MS for CSS C2 is
    Simulating Alternative CSS Process Courses of
    Action and Assessing the Merits

24
Control Clusters
  • Stock control
  • Order control
  • Schedule control
  • Packing control
  • Unitizing control
  • Transport pool control
  • Loading control
  • Release control
  • Distribution control
  • Transit control
  • Reception control
  • Storage control
  • Facility control
  • Support control
  • Network control

Taxonomy adopted by NAVMSMO for the Standards
Classification Framework.
SOST-LoRD-TReS-FaN
25
Doctrinal Principles of C2 and Planning
  • MCDP 6 Cmd Control
  • Boyd cycle (aka OODA loop) (p64)
  • info hierarchy (aka data gt info gt knowledge gt
    understanding) (p67)
  • image theory (p72)
  • C2 spectrum (mission to detailed continuum)
    (p77)
  • organizational width (aka span of control) and
    depth (number of echelons) (p91)
  • supply push / demand pull info mgmt (p119 MCDP
    2 p63)
  • MCDP 5 Planning
  • analysis and synthesis (p34)
  • planning horizion (conceptual gt functional gt
    detailed planning) (p36)
  • modes of planning (aka dealing with uncertainty)
    (p36)
  • decision and execution planning (p 43)
  • deliberate and rapid planning (p44)
  • forward and reverse planning (p45)
  • tight and loose coupling (p50)
  • simplicity and complexity (p52)

26
Emerging Principles of C2 and Planning
  • USMC Concepts Chap 5Beyond C2 A Concept for
    Comprehensive Command and Coordination of the
    MAGTF
  • policy gt intent gt orders (p v-4)
  • Facilitates interconnectivity / reachback
  • Supports OMFTS concept
  • Performs effectively across the range of
    operations
  • Serves as a cornerstone
  • Creates a learning organization
  • Encourages intuitive decision making
  • Enables mutual understanding w/ limited exchange
    of data
  • Exploits the power of implicit communications

27
Other Things to Consider
  • focus on the end user (MOEs gt MOPs)
  • transaction gt resource technique gt echelon
    network management
  • role of the user
  • total process visibility, total process
    management
  • control resolution (e.g. support relationships)
  • integration of ground and air, service pairs,
    joint
  • integration of strategic, operational and
    tactical logistics
  • integration of logistic functions
  • synchronization and independence
  • collaboration, man-in-the-loop, man-on-the-loop,
    automation
  • wizards, informers, tuners, optimizers, solvers,
    investigators, expert systems
  • principles gt techniques gt concepts gt abilities
    and their relationships
  • balanced comprehensive decision making
    (weigh/consider all principles appropriate to the
    situation)
  • agile decision making (rapidly revise how
    weigh/consider as volatile situations change)
  • focus on value added steps vice review, approval
    and rework
  • process control and predictability
  • complex adaptive systems, emergent behavior,
    chaos
  • feedback, self learning
  • knowledge discovery, data mining
  • concealment and deception
  • anticipation vice reaction
  • leading vice lagging indicators(MOPs)

28
Role of the User
C4ISR Forum This is part of a C2 very draft
TTP taxonomy. Potential new standard
  • Reacting / Responding
  • Approving
  • conditionally disapproving
  • conditionally approving
  • always approving/disapproving
  • Coordinating
  • synchronizing
  • negotiating
  • Problem solving
  • problem clarification, formulating
  • problem answering?
  • Leading / Initiating
  • directing
  • requesting? (presenting needs, and conditions)
  • managing?
  • Problem preventing
  • problem hunting
  • problem solving
  • (would like to have a distinctive term)
  • Bob Hamber
  • (poor outline as these are not distinct)
  • (and approving can be a coordinating step in the
    common sense of the term)

Bob Hamber I'm tempted to list "command" and
"control" here, but are reluctant to without
reviewing doctrine about exactly what these are
(ha! people have argued about this for centuries)
29
Multiple Levels of OODA
  • Mission Cycle
  • corresponds to
  • Campaign or Major Operations planning
  • Conceptual planning?
  • Period Cycle
  • corresponds to
  • Tactical planning
  • Functional planning
  • Detailed planning?
  • Transaction Cycle
  • corresponds to
  • Reacting
  • Rapid OODA
  • Detailed planning

30
MAGTF Activities Mapped to OODA at Mission Level
Bob Hamber Blue activities are preEMPRA and
relate to the National sublevel of the Mission
level.
Bob Hamber The yellow, red and orange blocks are
MAGTF activities.
NSA/CIA Activity
NCA/JCS Activity
Bob Hamber EMPRA AND BSRRR map to an OODA spiral
instead of a strict cycle -- generally the last
activity of an Act phase doesnt cycle into the
previous Ob-servation phase initial activity.
Msn Anal
COA Devl
Movement
Movementcond
Retrograde
Bob Hamber I distinguish between two sustainment
phases since they are sufficiently different in
character, and another phase, buildup, comes in
between them.
COA WarGm
Reconstitute
SOA Sustain
Buildup
ReAssault
COA Decision
Omfts Sustain
Rehearsal
Orders Devl
Assault
Revise
Embark
Transition
CINC/Joint Planning
Bob Hamber The gray text activities are ones I
consider optional
DON Planning
31
C2 Activities Mapped to OODA at Mission Level
Bob Hamber Only the MAGTF cycle
COMBAT READINESS REPORTING
INTELLIGENCE PREPARTION OF THE BATTLEFIELD
INTELLIGENCE FORCASTS
COLLABORATIVE LOG COA DEVL EVALUATION
Msn Anal
LOGISTIC READINESS REPORTING
COA Devl
COA WarGm
Bob Hamber I think IPB is also involved in the
Observation phase at least, and likely spans the
whole OODA. Intelligence includes threat,
neutral, friendly, allied, weather, terrain,
natural resources,
COMBAT COMMS
COA Decision
Orders Devl
HUMINT, IMINT SIGINT COMMS
Transition
LOG TACTICS LOG NETWORKCONTROL
SISO Should standardize the terms on these 5
slides.
LOG REQUESTS SENSOR MONITOR
Bob Hamber Incomplete
32
C2 Activities Mapped to OODA At Period Level
Bob Hamber As far as I know, Situational
Awareness is applied by others to all three
levels of C2 Ive illustrated. Here I choose to
focus this term on what I think is its most
common connotation.
  • Bob Hamber
  • I see the period cycle correspond to this cycle
    (ref my GLC2 COE e-m of 5/501)
  • major process tuning / resource allocation
    involving disnet design level (for when the
    operation changes phase) (corresponds to nearterm
    deliberate planning)
  • Depending upon how fast the period OODA cycle
    is going I see another level OODA loop operating
    if we have a robust GLC2 / SUL / SEAWAY / TLC2
    system This might be for only intra-node TTP
    where less internode coordination/negiotion is
    required
  • minor process tuning / resource allocation
    level (as scenario evolves, i.e. as METT factors
    change) (part operations, part hasty/reaction
    planning - a new term may be warranted)

COMBAT SITNL AWARENESS
COMBAT PRIORITIES
ENVIRO SITNL AWARENESS
RESOURCE REALLOCATION
EXPLORE ALT CSS COURSES OF ACTION
LOG SITNL AWARENESS
COMBATCLEARANCES
Bob Hamber Incomplete - surely more Period level
activities.
CSS PREPARATIONS MOVE FACILITIES TRANSFER
RESOURCES CONTROL CSS TTP
WEATHER CHECKS
Bob Hamber Cbt Engr and Unit maneuver too, even
though they are officially CS tasks?
REVISE CSS TACTICS AND TECHNIQUES
33
C2 Activities Mapped to OODA At Transaction Level
SPREADSHEETS DB CALCS ADVANCED OPTIMATION TECH
COMBAT ALERTS
ENVIRO ALERTS SPOT REPORTS
LOG TASK REPRIORITIZATION AND RESOURCE ASSIGNMENT
LOG SCHEDULED TASKS, RAPID REQUESTS SENSOR
REPORTS
COMBATCLEARANCES
CSS SERVICES SHIPMENTS MAINT REPAIRS CBT DEL
ENGR FIELD MEDICAL HYGIENE
Bob Hamber Note CSS Services are not C2
Activities per slide title.
WEATHER CHECKS
Bob Hamber Cbt Engr and Unit maneuver too, even
though they are officially CS tasks?
CSS JOB DISPATCH
Bob Hamber Incomplete
34
Additional CSS Principles
  • Military
  • Continuity
  • Covertness
  • Welfare
  • Systems
  • Balance
  • Synergy
  • Performance

35
Importance of Balance
  • MS helps quantify the tradeoffs of different
  • Combat CoAs
  • Strategic / Operational Log CoAs
  • CSS CoAs

36
Impacts of EMW / STOM / OMFTS on CSS
  • Increased Importance
  • Continuity
  • Survivability
  • At times, no FEBA
  • Urban ops a special challenge
  • Fewer secure MSRs and other LOCs
  • Covertness
  • Dont disclose combat force locations when
    providing CSS
  • Smaller unit operations in closer proximity to
    enemy
  • Enemy can close (respond) faster than before
  • Responsiveness
  • High tempo ops
  • Economy
  • Precision logistics smaller log tail

37
Agile CSS
  • What is agility?
  • Rapid appropriate reaction to changing conditions
  • Why agility is a key label
  • Good to focus on the customer objective
  • But for awhile need to focus on how the provider,
    us, are going to achieve the customer objective
  • Who else thinks so?
  • Army
  • ESC Pkg team?
  • ______

38
Agile CSS
  • Compared to Precision
  • Precision focuses on having the right amount at
    the right time
  • Agility focuses on how to getting the right
    amount at the right time
  • Precision Goal Agility Means
  • Precision customers point of view Agility
    providers point of view
  • Compared to Focused

39
Intelligence
SISO Candidate for standard taxonomy
  • Awareness
  • External
  • METT-TSL
  • Both
  • TAV
  • TPV
  • Forecast
  • Planning Factors
  • Models
  • static
  • Simulations
  • dynamic
  • Feedback
  • Collaboration
  • Man in the loop
  • Man beside the loop
  • Men in the loop
  • Learning
  • Data mining
  • _______ (Ref that article)
  • Intelligent Agents

40
What is Situational Awareness?
  • Situational info external to a system --
    certainly
  • info on things that affect your system
  • things you dont have total control over
  • Situational info on your own system a matter
    for debate
  • Is this also SA?
  • It is to anyone else's system when meets above
    criteria
  • Consider
  • To the GCE and ACE commanders,
  • the dump stat reports are SA,
  • equipment readiness reports are SA
  • To the CSSE This way, TAV and TPV of ones own
    system is not your situational awareness.

Bob Hamber Not Things you have no direct
control over because GCE cmdr has some direct
control over what his stocks are, say by decide
to pull back and take time to be resupplied.
41
Output For Two COAs
  • Two fundamentally different COA to address
  • External COAs
  • Mission options
  • Threat options
  • Task organization options
  • Weather options
  • Internal CoAs
  • CSS tactic, technique, and procedural options
  • CSS resource allocation options
  • CSS manpower options
  • CSS resource maintenance options
  • CSS equipment level operation options
  • CSS communication options

42
External Combat Driven COAs
  • 1a) Control Objective A
  • 1a1) via axis of advance Charlie
  • 1a1a) land the reserve RLT on D1
  • 1a1a1) land the reserve RLT at littoral
    penetration site Eel
  • 2a) Enemy doesnt use NBC
  • 3a) LAR Bn is an independent maneuver element
  • 4a) Typhoon Zach swings east and only modest
    rains hit AOA
  • 1b) Control Objective B
  • 1a2) via axis of advance Delta
  • 1a1b) land the reserve RLT on D3
  • 1a1a2) land the reserve RLT at LPS Fish
  • 2b) Enemy does use NBC
  • 3b) LAR Bn is attached to 1st Marines
  • Typhoon Zach strikes AOA on D5 and lingers thru
    D8
  • Each could involve different estimates of
    supportability for the MAGTF commander

43
External Combat Driven COAs - cont
  • Supporting Future Ops Planning Cell
  • 1a1a1a) projected reserve RLT JP-8 consumption
    for D1 thru D6 is 50Kgpd
  • Supporting current ops (say on D3)
  • 1a1a1d) projected reserve RLT JP-8 consumption
    for D4 thru D10 is 75 of the D3 actual
    consumption rate
  • 1a1a1b) projected reserve RLT JP-8 consumption
    for D1 thru D6 is 100Kgpd
  • 1a1a1c) projected reserve RLT JP-8 consumption
    for D4 thru D10 is the average of D1 thru D3
    actual consumption rate
  • Each could prompt the CSSE commander to consider
    multiple CSS COAs (next slide)

44
Internal CSS COAs
  • 1a) support each RLT with a CSSA in DS
  • 1a1) support each Bn with an MCSSD
  • 1a1a) use primarily ground vehicles to resupply
    MCSSD
  • 1b_a) use ground vehicles to resupply each CSSA
  • 1a1a1) set MCSSD stock objective at 2 DOS and
    safety level at 1 DOS
  • 1b1a1a) source all classes of supply for MCSSD
    from DS CSSD
  • 1b) support the force with a CSSA in GS and 3
    CSSDs in DS of each RLT
  • 1a2) support only heavy Bns with an MCSSD
  • 1a1b) use primarily helos to resupply MCSSD
  • 1b_b) use ground vehicles to resupply each CSSA
    except for hoselines for bulk Class III
  • 1a1a2) set MCSSD stock objective at 3 DOS and
    safety level at 2 DOS
  • 1b1a1b) source Class I, III and V for MCSSD from
    DS CSSD, and all other classes from GS CSSA

45
Conops Structure
Weaving it all together
  • 1st level for each operation, campaign, mission
  • 2nd level for each stage, phase, battle
  • 3rd level for each period (n per day)
  • 4th level for each transaction

46
First Level For Each Mission
47
Second Level For Each Phase
48
Conops Structure
49
My Conops Workspace
  • I use an Excel workbook to
  • Compile lists, hierarchies, taxonomies
  • Explore relationships
  • Create matrices to represent who does what, when.
  • PlanningProcess.xls

Bob Hamber The live presentation at Fall SIW
showed the workbook. Some images of it follow.
50
Use Case Factors
  • Mission Class (type of operation)
  • MAGTF type/size
  • C2 echelon
  • C2 Node
  • CSS C2 organizational structure
  • MAGTF type/size, mission, phase
  • Collapse levels of command
  • future USMC restructuring
  • C2 cycle level
  • Mission
  • Period
  • Transaction
  • CSS function
  • the six standard
  • Planning hierarchy
  • conceptual
  • functional
  • detailed
  • Planning mode
  • Commitment
  • Contingency
  • Orientation
  • Time available
  • deliberate
  • rapid

51
Potential Use Case Factors
  • Maybe
  • CSS Alignment
  • Levels of Service
  • CSS Principle/Virtue
  • CSS Issue/Decision
  • Probably not
  • Degree of coordination
  • Degree of MS use/support

52
C2 Staff Section Planning Level Matrix
Bob Hamber Per MCDP 5-1 Ap C, sec 3 Probably
more complex. Probably varies with use case.
53
Command Relationships One Aspect
Bob Hamber Looks too good to be true. Probably
more complex. Probably varies with use case.
54
Decision Cycle Level vs Decision Node
One to many relationship points to a use case
simplification.
55
Decision Cycle Level vs Decision Node (cont)
56
Where MS Can Be Used in MCPP
Near one to many relationship points to a
potential use case simplification.
57
Map MS Support
  • Annex D to OPORD Log/CSS
  • CSS Commander and staff estimate
  • Commanders daily brief
  • Present SUL process
  • CSS C2 Activity Model - (CSS C2 ToBe Arch, pp
    22-32)
  • And supporting operatinal views
  • Or my rework of them
  • CSS C2 Op Info Exchange Matrix (2B Arch ap A)

58
Summary
59
Program Review Takeaways
  • Process, process, process
  • Total Process Visibility
  • Process Understanding
  • Sell it
  • Standards needed
  • to flesh out common foundation
  • Joint, vice service specifics, pan-MS vice
    model specifics
  • Conditions taxonomy
  • CSS resource categories
  • Decision/Planning cycle
  • Decisions to be made
  • CSS process taxonomy
  • Outputs (MOEs, time plots, standard reports,
  • Use cases
  • prior to turning CSS C2 software developers loose

60
Relevance of the proposed SIW paper
Bob Hamber Ref Submission of Abstract (em dtd
5/5/01) to papersmgr_at_itcenter.org All text of
this em are on the slide, the 2 linked slides, or
the notes, except for the Endmatter that includes
more things to consider not submitted to SIW.
  • The logistics C2 development community is lagging
    on applying many useful principles of command,
    control and planning. (Principles Other
    Things)
  • The applications of these will have a profound
    impact upon logistic system performance,
    especially towards the tactical end of the the
    spectrum.
  • These improvements will provide the far more
    agile and robust logistics system that is needed
    to support high tempo, complex combat operations.
  • There is a large opportunity for the modeling and
    simulation community to assess alternative
    implementations of these C2 theories and
    constructs to logistics.

61
So What?
  • Many opportunities for terminology development,
    and standard taxonomies
  • Many data/info relationships still to develop
  • Develop a technical reference model
  • Collaborate with C4ISR Forum

62
BACKUP
Reward
63
Conops Issues
64
What Decision Process Cycle Steps
Bob Hamber Source spreadsheet has multiple new
columns but dont have to update this.
Military Decision Making Process .
1.5 . Receipt of Mission . Mission
Analysis . COA Development COA Analysis
. COA Comparison . COA Approval . Orders
Production . Rehearsal . Execution Assess
See PlanningProcess3.xls for common
alignment
Not including UJTL Ex Op C2 decision process
65
END
Write a Comment
User Comments (0)