TT_Vol3 Issue2 - Raytheon

• Sea Power 21: NCO’s Vision for
Maritime Operations in the 21st
Century.
• Operational Maneuver From the
Sea: Commandant’s Vision for
Marine Corps Projection of Naval
Power Ashore.
• Air Force Vision 2020: CSAF Vision for
Air Operations into the 21st Century.
To adequately understand these documents,
the CFM process distills the visions down to
a few important statements and then validates
the key themes through customer
interactions. For example, the above vision
documents all have a common theme as
they describe the future:
• “The services want to fight Joint”
• “The services want to mass effects
not forces”
• “The services want to fight Non
Linear”
• “The services want to influence two
to three times more battlespace than
they do today”
• “The services want to be ready to
fight in less time”
To achieve the services’ “Future Vision”,
doctrinal and material changes will follow
as a matter of course. These changes
include:
• The Line of Sight (LOS) engagement
will occur by exception not by rule
• The dominant killer on the battlefield
will be Non-Line Of Sight (NLOS)
weapons
• Persistent situational awareness is
essential to executing these concepts
• The force must be more agile and
deployable
• The way we perform BMC4I today
will have to change
The Reference Architecture provides the
conceptual framework for specifying the
four aspects (social, cognitive, information
and physical) of systems within the bounds
of operational, system and technical views
prescribed by the DoD Architecture
Framework (DoDAF). It also provides architectural
guidelines for domain-specific
implementations, while allowing a range of
design solutions. Finally, it defines the architectural
patterns for discussion and analysis
purposes, how the patterns communicate
with each other, the basic operations associated
with each pattern and the nature of
the communications. In the NCO Case
Study the patterns included:
• Common Decision and Execution
Capability (CDEC) Architectural
Pattern
– A remote, distributed, and nondedicated
BMC2 system that
develops, builds, and executes
optimum real-time kill chains from
all available Communications,
Sensors, C2, Platforms and
Effectors.
• Infosphere Architectural Pattern
– Encyclopedia of past, present and
predicted state
– A combat information
management system that
integrates, aggregates,
and distributes information in
appropriate form and level of
detail to users at all echelons.
• Global Communications Grid
Architectural Pattern
– Communications mechanism for
element interactions
– An integrated wideband
communications, netted sensor, and
advanced data fusion system that
employs the Infosphere and the
CDEC as they are developed.
• Strategic Planning Functional Pattern
– The definition and allocation of
resources for a mission
– Provides strategic to campaign level
planning to include worldwide data
base access and fusion in support of
the Warfighting Function
• Logistics Functional Pattern
– The supply of resources specified in
plans supporting the tactical and
operational application of
combat power
– Includes global logistics and
sustainment elements in support of
the warfighting function
• Execution (warfighting, peacekeeping,
policing, etc.) Functional Pattern
– The enactment of the strategic plan
using the resources supplied and
maintained by logistics
– Contains all the elements required
to effectively employ resources
and effects.
Through Customer-Focused Marketing and
interactions, the CONOPS for Net-Centric
Operations is captured and mapped onto
the Reference Architecture in an iterative
process. The Reference Architecture provides
viewpoints (from the perspective of
key stakeholders) to validate the patterns.
The domain layers are used as constraints
on the development of domain specific
architectures defined by individual programs.
The effectiveness of the resulting
architectures is then evaluated through
modeling and simulation, and limited
objective experiments and demonstrations.
The final results are then fed back into the
Reference Architecture maintenance process
to validate or drive changes to the core
Reference Architecture.
The reference architecture process described
in this article is leading the way to the
development of a seamlessly integrated
network of remoted, distributed, non-dedicated
components, creating warfighter
dominance through information superiority.
The NCO patterns (sensors, effectors and
Command and Control) described above
are used in the Reference Architecture to
provide guidance to the domain-specific
architects in each strategic Raytheon business
area. Raytheon’s domain expertise
spans the breadth of Net-Centric
Operations, from sensing to distributed
command and control, to effects, and
finally to complex systems integration. �
9