Human Factors Implications and Issues in Network Enabled Operations

PDF

Authors
  1. English, A.
  2. Gimblett, R.
  3. Coombs, H.
Corporate Authors
Defence R&D Canada - Toronto, Toronto ONT (CAN);KMG Associates, Kingston ONT (CAN)
Abstract
Network Enabled Operations (NEOps) seems poised to become the driving concept behind CF transformation for a number of reasons, not the least of which is Canada’s tendency to follow the American lead in new concepts related to war and other operations. This paper concludes that Canada and the CF should be cautious about using NCW as the foundation for NEOps, because the context and needs that are the basis for NCW may not be congruent with Canadian requirements. The paper noted that NCW is not really a theory of war, as its proponents claim, but a series of largely untested hypotheses or assumptions that require validation before they should be accepted as a basis for transformation. Recent Canadian Forces’ (CF) operations have shown that a “one size fits all” approach to command and control, as proposed by many NCW advocates, may not be the best approach for networked operations, even in an increasingly integrated joint and combined operating environment. Perhaps most importantly, from a Canadian point of view, using NEOps in the Joint, Interagency, Multinational, and Public (JIMP) or integrated context will require network architects not only to consider the use of information technology as an enabler, but also for them to address the much more complex issue of the creation of effective social networks. In summary, NEOps as a concept has a promising future if it is predicated on Canadian needs and culture. However, there is significant risk in placing too much relia

Il y a un résumé en français ici.

Keywords
Network Enabled Operations;Human Factors;Network-Centric Warfare;CF Transformation
Report Number
DRDC-TORONTO-CR-2006-217 — Contractor Report
Date of publication
26 Aug 2006
Number of Pages
55
DSTKIM No
CA030333
CANDIS No
528814
Format(s):
Electronic Document(PDF)

Permanent link

Document 1 of 1

Date modified: