Elements of Future COP Elements of Future COP Elements of Future - PowerPoint PPT Presentation

Elements of Future COP Elements of Future COP Elements of Future COP Elements of Future COP Patterns Patterns Applying Net Applying Net- -Centric Principles Centric Principles Hans W. Polzer Hans W. Polzer Lockheed Martin Fellow Lockheed Martin Fellow L L kh kh d M d M ti ti F ll F ll 18 May, 2010 18 May, 2010 Based in part on work done with NCOIC Based in part on work done with NCOIC – – www.ncoic.org www.ncoic.org Reflects the personal opinion of the author and not a Lockheed Reflects the personal opinion of the author and not a Lockheed T-Presentation-1 5/17/2010 1 Martin position Martin position

The Common Operational Picture The Common Operational Picture The Common Operational Picture The Common Operational Picture (COP) (COP) • Is anything but common (or single) Is anything but common (or single) • Is not a “picture” in the literal sense of the word Is not a “picture” in the literal sense of the word • Has implicit and fuzzy operational scope • Has implicit and fuzzy operational scope Has implicit and fuzzy operational scope Has implicit and fuzzy operational scope • Depicts a perspective of operational space Depicts a perspective of operational space beyond that justified by raw sensor inputs beyond that justified by raw sensor inputs y y j j y y p p • Increasingly requires social and “human terrain” Increasingly requires social and “human terrain” perspectives perspectives • Needs to recognize multiplicity and diversity in Needs to recognize multiplicity and diversity in COPs COPs Consistency and convergence is the goal, rather than Consistency and convergence is the goal, rather than Consistenc Consistenc and con ergence is the goal rather than and con ergence is the goal rather than commonality commonality T-Presentation-1 5/17/2010 2

Why COP Patterns? Why COP Patterns? • Because a single COP architecture is not feasible Because a single COP architecture is not feasible – Too many diverse force element “owners” Too many diverse force element “owners” – – – Too many different perspectives, scopes, and Too many different perspectives, scopes, and information representation needs information representation needs information representation needs information representation needs – A COP has to work in (and with) a larger A COP has to work in (and with) a larger – enterprise context – enterprise context p – and many such contexts and many such contexts y • Patterns are architecture fragments Patterns are architecture fragments – Partially decoupled from specific operational Partially decoupled from specific operational and enterprise contexts and enterprise contexts – d d i i – i.e. abstractions i i.e. abstractions i b b i i – And therefore applicable in a broader set of And therefore applicable in a broader set of operational and enterprise contexts operational and enterprise contexts operational and enterprise contexts operational and enterprise contexts T-Presentation-1 5/17/2010 3

Net Net Net-Centricity Net-Centricity Centricity Centricity • Is about achieving Is about achieving operational objectives operational objectives via via interaction with interaction with others others over a network over a network • Facilitated by open protocols and broad F F Facilitated by open protocols and broad ilit t d b ilit t d b t t l l d b d b d d accessibility accessibility • Entails a “business model” and/or a “social Entails a “business model” and/or a “social relationship” among the “others” relationship” among the “others” • Brings diverse perspectives, frames of reference, Brings diverse perspectives, frames of reference, and operational scope/purpose together and operational scope/purpose together d d ti ti l l / / t t th th – Suggests a need for explicit representation of Suggests a need for explicit representation of same same same same T-Presentation-1 5/17/2010 4

Net Net- -Centric Principles Centric Principles • Explicitness Explicitness – An entity should make all information about itself explicit An entity should make all information about itself explicit • Symmetry/Reciprocal Behaviors Symmetry/Reciprocal Behaviors – Relations and entities should exhibit symmetric Relations and entities should exhibit symmetric characteristics and behaviors characteristics and behaviors characteristics and behaviors characteristics and behaviors • Dynamism Dynamism – Entities Entities should support dynamic behaviors should support dynamic behaviors • Globalism Globalism – There should be no a priori bounds on the scope of There should be no a priori bounds on the scope of operational applicability operational applicability p p pp pp y y • Omnipresent/Ubiquitous Accessibility Omnipresent/Ubiquitous Accessibility – Entities should have access to resources (i.e., each other) Entities should have access to resources (i.e., each other) at any time and any where at any time and any where at any time and any where at any time and any where 5 T-Presentation-1 5/17/2010 5

Net Net- -Centric Principles Centric Principles • Entity Primacy Entity Primacy – Entities have identity distinct from the contexts in which – Entities have identity distinct from the contexts in which Entities have identity distinct from the contexts in which Entities have identity distinct from the contexts in which they participate they participate • Relationship Management Relationship Management – Relations among entities should be explicitly represented Relations among entities should be explicitly represented and provide for negotiation, creation, change, and and provide for negotiation, creation, change, and termination termination • Scale Scale-free free – The scale of the enterprise or system context should not The scale of the enterprise or system context should not have an impact on operational functionality have an impact on operational functionality p p p p y y • Pragmatism Pragmatism – The ability to improve operational effectiveness is The ability to improve operational effectiveness is paramount paramount paramount paramount 6 T-Presentation-1 5/17/2010 6

COP Pattern Elements COP Pattern Elements • The COP as an incomplete, focused, model of reality The COP as an incomplete, focused, model of reality – Multiple realities: CPX, field exercises, training, planning, Multiple realities: CPX, field exercises, training, planning, rehearsal, after action analysis rehearsal, after action analysis h h l l ft ft ti ti l l i i – Multiple operational/functional contexts: ops, Multiple operational/functional contexts: ops, intel intel, logistics, , logistics, COA development, COA development, replanning replanning, deployment, etc. , deployment, etc. – Coupling to contexts/realities should be explicit Coupling to contexts/realities should be explicit • The COP as a consistent (vice) common model The COP as a consistent (vice) common model – Adaptive Adaptive tailorable Adaptive, Adaptive, tailorable tailorable user context tailorable, user context , user context relevant /sensitive user context-relevant /sensitive relevant /sensitive relevant /sensitive – “common” mode as an option (visual display slaving/sync) “common” mode as an option (visual display slaving/sync) • The COP as collaborative The COP as collaborative – Support for collaborative (i.e., limited sets of users) contexts Support for collaborative (i.e., limited sets of users) contexts – Users as sources of COP model data values (not just sensors, Users as sources of COP model data values (not just sensors, systems of record), explicit attribution attribution systems of record), explicit y y ), ), p p – Controlled release to larger user set of selected COP entities Controlled release to larger user set of selected COP entities and entity attributes and entity attributes 7 T-Presentation-1 5/17/2010 7