317:
288:. The NetOps framework, effects, and organizational relationships described herein formulate a foundation for the operational future of the GIG, but these will not happen automatically, nor will they occur without significant effort from the entire NetOps Community. Attaining the vision will require cooperation, innovation, and execution from all mission partners and everyone who touches the GIG.” (From
49:
45:
Combatant
Commanders (COCOMs) with GIG Situational Awareness to make informed Command and Control decisions. GIG SA is gained through the operational and technical integration of enterprise management and defense actions and activities across all levels of command (strategic, operational and expeditionary forces).
233:
The original NetOps construct consisted of
Network Management (NM), Information Assurance (IA), and Information Dissemination Management (IDM). Today the construct has evolved into GIG Enterprise Management (GEM), GIG Net Assurance(GNA), and GIG Content Management which roughly equates to the intent
339:
If the decision maker is not getting the needed net-centric services, the GIG NetOps community must collaboratively determine who must take action and how information flow can be optimized. This requires NetOps personnel to have a shared SA as well as the technologies, procedures, and collaborative
307:
is part of a new wave of automation assistance for network operators, and there are a few methodologies out there to help others. One prominent methodology is aptly named DIRE NetOps. It focuses on
Documentation, Isolation, Repair, and Escalation to guide the user through the transformation process,
268:
and the NetOps community through operations, exercises, and other events. We will continue to work with the NetOps
Community as we translate the concepts set forth in this document into doctrine, policy and joint tactics, techniques, and procedures that strengthen the operations and defense of the
93:
The DoD NetOps
Community strives to obtain common visibility of network resources so that these can be managed, anticipate and mitigate problems, ensuring uninterrupted availability and protection of the GIG and provide for graceful degradation, self-healing, failover, diversity, and elimination of
89:
This shared
Situational Awareness is derived from common reporting requirements using functionally standardized management tools and common data information exchange formats across the Defense Department. These capabilities collect (or receive), and fuse (enterprise management, network defense and
144:
Network
Operations. This “NetOps CONOPS” provided the common framework and command and control structure to conduct the USSTRATCOM Unified Command Plan (UCP) - assigned mission of Global Network Operations (NETOPS), combining the disciplines of Enterprise Systems (EM) and Network Management (NM),
85:
The element of NetOps known as
Situational Awareness (SA), is the primary ability to improve the quality and timeliness of collaborative decision-making. To be effective, much of the SA must be shared in near-real-time by the decision-makers who have the ability to take this information, conduct
178:
and Joint Vision 2010 arrived in the mid 1990s, it became clear that the center of gravity for U.S. military warfighting capability was shifting towards the network. A corresponding capability was required to move beyond managing the network as a back-office system into a domain of warfighting.
44:
DoD Instruction (DoDI) 8410.02 defines NetOps as the DoD-wide operational, organizational, and technical capabilities for operating and defending the Global
Information Grid. NetOps includes, but is not limited to, enterprise management, net assurance, and content management. NetOps provides
343:
The effectiveness of NetOps will be measured in terms of availability and reliability of net-centric services, across all domains, in adherence to agreed-upon service levels and policies. The method for service assurance in a NetCentric collaborative environment is to establish operational
351:
will enable monitoring of adherence to these SLAs, as well as enable timely decision-making, service prioritization, resource allocation, root cause, and mission impact assessment. Subsequent TTPs and SLAs will be formalized with appropriate implementation policies to enforce compliance.
108:
JTF-GNO directs the operation and defense of the GIG to assure timely and secure Net-Centric capabilities across strategic, operational, and expeditionary boundaries in support of full spectrum warfighting, intelligence, and business missions for the
Defense Department.
335:
enterprises, seamlessly, end-to-end. An objective of NetCentric services is to quickly get information to decision makers, with adequate context, to make better decisions affecting the mission and to project their decisions forward to their forces for action.
70:
The synergy achieved by each integrated relationship between any two of the essential tasks (GEM, GNA, and GCM) produces the following NetOps desired effects in support of the overall goal of NetOps which is to provide the right information to the edge:
242:“We must change the paradigm in which we talk and think about the network; we must ‘fight’ rather than ‘manage’ the network and operators must see themselves as engaged at all times, ensuring the health and operation of this critical weapons system.”
121:
recognized a growing cyber threat and in response created the Joint Task Force — Computer Network Defense (JTF-CND), which achieved Initial Operational Capability (IOC) on 30 December 1998 and Full Operational Capability (FOC) by June 1999.
221:
TCCC was a pilot program for the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASD/C3I) NetOps concept. The NetOps concept began with the development of the architectural framework for NetOps, and a
340:
organizational structures to rapidly assess and respond to system and network degradations, outages, or changes in operational priorities. All functions required to most effectively support GIG operations will be holistically managed.
94:
critical failure points. Through effective visibility, the NetOps community endeavors to attain the three goals of NetOps: Assured System and Network Availability, Assured Information Protection and Assured Information Delivery.
590:
595:
52:
The GIG includes any DoD system, equipment, software, or service that transmits, stores, or processes DoD information, and any other associated services necessary to achieve information superiority.
253:"The US government and the US military must become still more joint, more agile, more decentralized, more networked, and better arranged to share information and coordinate actions."
344:
thresholds, compliance monitoring, and a clear understanding of the capabilities between enterprise service/resource providers and consumers through Service Level Agreements (SLAs).
90:
configuration management) data in a real time or near real-time fashion to produce defined views of the mission critical GIG information of concern to a commander or NetOps center.
328:. Unlike many missions with a defined completion date, NetOps has been established as a standing Joint Force mission necessitating dedicated leadership and resources to execute.
320:
The Unified Command Plan (UCP) assigns the Cyber Mission to Commander, US Strategic Command. NetOps falls under the Cyber-Umbrella as a construct to "operate and defend the GIG."
129:
doctrine, JTF-CND became the Joint Task Force — Computer Network Operations (JTF-CNO). In October 2002, the new Unified Command Plan (UCP), Change 2, re-aligned JTF-CNO under the
296:, February 2006. The adaptive force assures availability, delivery and protection of infrastructure, systems, and information.) LtGen Charles E. Croom, Commander,
331:
NetOps provides assured NetCentric services to the DoD in support of full spectrum of warfighting operations, intelligence, and business missions throughout the
361:
297:
291:
281:
265:
168:
157:
103:
381:
376:
223:
218:
214:
191:
126:
118:
423:
258:
247:
206:
153:
149:
230:
outlining the key players and their roles and responsibilities necessary to develop the NetOps construct in the Pacific Theater.
198:, Hawaii in 1999. The TCCC initiative was constructed of two distinct components - the technology that formed the vision of the
27:
that the Commander (CDR) of US Strategic Command (USSTRATCOM), in coordination with DoD and Global NetOps Community, employs to
585:
366:
274:
520:
509:
510:
IA Newsletter, Volume 3, Number 4, USPACOM Theater Network Operations, Ensuring Information Superiority for the 21st Century
570:
183:
371:
270:
171:
mission and objectives in achieving the Joint Vision 2020 Objective Force and the evolving concept of Net-Centricity.
521:
IA Newsletter, Volume 4, Number 4, Partnership's - The Key to Success for Pacific Theater Network Operations (NetOps)
495:
Network-Centric Warfare: Its Origin and Future, By Vice Admiral Arthur K. Cebrowski, U.S. Navy, and John J. Garstka,
464:
316:
160:. With this designation, the new command assumed the responsibility for directing the operation and defense of the
217:
TCCC made the initial strides towards achieving Information Superiority and true enterprise-level processes. The
86:
critical analysis and act on those decisions with regards to employment, protection and defense of the GIG.
409:
Joint Concept of Operations (CONOPS) for Global Information Grid (GIG) NetOps Version 3, dated August 4, 2006
38:
348:
332:
325:
285:
199:
175:
161:
141:
34:
494:
227:
210:
136:
The JTF-CNO began its largest and most comprehensive transformation in April 2004 when the Commander of
24:
20:
560:
437:
187:
284:
is to lead an adaptive force that assures the availability, delivery, and protection of the
195:
531:
441:
254:
243:
269:
Global Information Grid in support of warfighter business and intelligence operations.”
542:
JTF GNO Strategic Plan, An Adaptive Force Ensuring Information Delivery, February 2006
579:
424:
DoDI 8410.02, NetOps for the Global Information Grid (GIG), dated December 19, 2008
303:
There is also a new paradigm shift occurring in NetOps from 1.0 to 2.0, or DevOps.
152:
signed a delegation of authority letter on 18 June 2004, designating the Director,
209:, the Service Components, Sub-Unified Commands, JTFs, other CINC TCCC's, and the
145:
Computer Network Defense (CND), and Information Dissemination Management (IDM).
19:
is defined as the operational framework consisting of three essential tasks,
532:
Secretary Rumsfeld speaking at a NetCentric Warfare Conference (NCW) 2008.
137:
130:
471:
202:
and the NetOps initiative; and the partnerships that made it a reality.
561:
Joint Task Force Global Network Operations (JTF GNO) - Requires PKI/CAC
566:
Defense Information Systems Agency (DISA) Information Assurance/NetOps
264:“This version of the NetOps CONOPS documents the lessons learned by
304:
48:
315:
47:
294:
Strategic Plan, An Adaptive Force Ensuring Information Delivery"
565:
182:
NetOps was originally developed under the leadership of then
555:
452:
591:
United States Department of Defense information technology
308:
ensuring high value tasks are supported with automation.
596:
Joint military units and formations of the United States
434:
571:
DoD IA Policy Chart - Build and Operate a Trusted GIG
98:
Joint Task Force Global Network Operations (JTF-GNO)
556:United States Strategic Command Official Website
453:United States Strategic Command Official Website
324:The NetOps mission is to operate and defend the
140:approved the Joint Concept of Operations for
8:
131:United States Strategic Command (USSTRATCOM)
362:Joint Task Force-Global Network Operations
292:Joint Task Force-Global Network Operations
266:Joint Task Force-Global Network Operations
194:Theater C4I Coordination Center (TCCC) at
158:Joint Task Force-Global Network Operations
104:Joint Task Force-Global Network Operations
56:The three essential tasks are as follows:
382:Information Assurance Vulnerability Alert
405:
403:
401:
399:
397:
125:In the fall of 2000, in accordance with
393:
377:Global Information Network Architecture
205:Through its working relationships with
190:James Bryan during the stand-up of the
75:Assured System and Network Availability
419:
417:
415:
7:
259:United States Secretary of Defense
248:United States Secretary of Defense
14:
167:This transformation enhanced the
234:of the original NetOps concept.
367:United States Strategic Command
275:United States Strategic Command
60:GIG Enterprise Management (GEM)
435:JTF-GNO Website, December 2008
347:Proper instrumentation of the
280:“The Strategic Vision for the
228:Concept of Operations (CONOPS)
78:Assured Information Protection
1:
184:United States Pacific Command
156:as the new Commander of the
81:Assured Information Delivery
66:GIG Content Management (GCM)
372:United States Cyber Command
271:General James E. Cartwright
612:
101:
30:operate, manage and defend
25:Command & Control (C2)
21:Situational Awareness (SA)
174:As new concepts such as
286:Global Information Grid
176:Network-centric warfare
63:GIG Net Assurance (GNA)
41:for the United States.
39:information superiority
35:Global Information Grid
586:21st-century conflicts
321:
53:
319:
305:NetOps Transformation
119:Department of Defense
51:
277:(2004- August 2007)
150:Secretary of Defense
138:US Strategic Command
465:"Joint Vision 2010"
440:2007-03-23 at the
322:
54:
188:Brigadier General
603:
543:
540:
534:
529:
523:
518:
512:
507:
501:
492:
486:
485:
483:
482:
476:
470:. Archived from
469:
461:
455:
450:
444:
432:
426:
421:
410:
407:
196:Camp H. M. Smith
37:(GIG) to ensure
611:
610:
606:
605:
604:
602:
601:
600:
576:
575:
552:
547:
546:
541:
537:
530:
526:
519:
515:
508:
504:
493:
489:
480:
478:
474:
467:
463:
462:
458:
451:
447:
442:Wayback Machine
433:
429:
422:
413:
408:
395:
390:
358:
314:
255:Donald Rumsfeld
244:Donald Rumsfeld
240:
115:
106:
100:
12:
11:
5:
609:
607:
599:
598:
593:
588:
578:
577:
574:
573:
568:
563:
558:
551:
550:External links
548:
545:
544:
535:
524:
513:
502:
499:, January 1998
487:
456:
445:
427:
411:
392:
391:
389:
386:
385:
384:
379:
374:
369:
364:
357:
354:
313:
310:
261:(2001 - 2006)
250:(2001 - 2006)
239:
236:
114:
111:
102:Main article:
99:
96:
83:
82:
79:
76:
68:
67:
64:
61:
13:
10:
9:
6:
4:
3:
2:
608:
597:
594:
592:
589:
587:
584:
583:
581:
572:
569:
567:
564:
562:
559:
557:
554:
553:
549:
539:
536:
533:
528:
525:
522:
517:
514:
511:
506:
503:
500:
498:
491:
488:
477:on 2016-12-24
473:
466:
460:
457:
454:
449:
446:
443:
439:
436:
431:
428:
425:
420:
418:
416:
412:
406:
404:
402:
400:
398:
394:
387:
383:
380:
378:
375:
373:
370:
368:
365:
363:
360:
359:
355:
353:
350:
345:
341:
337:
334:
329:
327:
318:
311:
309:
306:
301:
299:
295:
293:
287:
283:
278:
276:
273:, Commander,
272:
267:
262:
260:
256:
251:
249:
245:
238:NetOps Vision
237:
235:
231:
229:
225:
220:
216:
212:
208:
203:
201:
197:
193:
189:
185:
180:
177:
172:
170:
165:
163:
159:
155:
151:
146:
143:
139:
134:
132:
128:
123:
120:
117:In 1998, the
112:
110:
105:
97:
95:
91:
87:
80:
77:
74:
73:
72:
65:
62:
59:
58:
57:
50:
46:
42:
40:
36:
32:
31:
26:
22:
18:
538:
527:
516:
505:
496:
490:
479:. Retrieved
472:the original
459:
448:
430:
346:
342:
338:
330:
323:
302:
289:
279:
263:
252:
241:
232:
204:
181:
173:
166:
147:
135:
124:
116:
107:
92:
88:
84:
69:
55:
43:
29:
28:
16:
15:
497:Proceedings
211:Joint Staff
580:Categories
481:2008-03-29
388:References
226:developed
113:Background
224:USCINCPAC
219:USCINCPAC
215:USCINCPAC
192:USCINCPAC
169:JTF GNO's
438:Archived
356:See also
312:Mission
298:JTF GNO
282:JTF GNO
23:, and
17:NetOps
475:(PDF)
468:(PDF)
207:DISA
154:DISA
148:The
33:the
349:GIG
333:GIG
326:GIG
200:GIG
186:J6
164:.
162:GIG
142:GIG
127:DoD
582::
414:^
396:^
300:.
257:,
246:,
213:,
133:.
484:.
290:"
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
