File:Enterprise Command and Control requirements and common architecture on U.S. Navy surface combatants (IA enterprisecomman109456939).pdf

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search
Go to page
next page →
next page →
next page →

Original file(1,275 × 1,650 pixels, file size: 2.03 MB, MIME type: application/pdf, 198 pages)

Captions

Captions

Add a one-line explanation of what this file represents

Summary

[edit]
Enterprise Command and Control requirements and common architecture on U.S. Navy surface combatants   (Wikidata search (Cirrus search) Wikidata query (SPARQL)  Create new Wikidata item based on this file)
Author
Acosta, Elvis
Barta, Jordan
Beger-Mason, Joanna
Donovan, Harry
Eak, Matt
Finley, Dave
Galace, Llewelynn
Jones, Brian
Maurseth, Andrina
Metz, Lee
Painchaud, Lesley
Pepper, Josh
Suchit, Reshma
Tidwell, Rob
Yu, David
Zanella, Bob
image of artwork listed in title parameter on this page
Title
Enterprise Command and Control requirements and common architecture on U.S. Navy surface combatants
Publisher
Monterey, California. Naval Postgraduate School
Description

Across the U.S. Navy, each new ship class implements a new command and control (C2) system design, leading to separate design and development efforts, training pipelines, support requirements, and upgrade activities. This project serves as an initial step in determining whether the Navy can consolidate C2 systems by defining a common C2 system architecture and requirements that can be applied across all surface combatants for the Surface Warfare and Maritime Interception Operations missions. The project applied a systems engineering process consisting of a needs analysis, functional analysis, and modeling and cost analysis. The needs analysis defined key user objectives and needs and identified threats to Navy platforms. The functional analysis included the core tasks of requirements definition and enterprise architecture. The modeling and cost analysis task verified the C2 system architecture and evaluated possible training course hour savings. The project found that the definition of a common set of C2 system requirements and system architecture is feasible and does provide possible life cycle cost savings to the Navy. In order to fully evaluate a proposed common C2 system, further work will be required, expanding the analysis to other missions and assessing the cost impacts of a common C2 system


Subjects: Naval Vessels (Combatant); Computer Architecture; Systems Engineering; Command and Control Systems; Life Cycle Costs; Courses (Education); Functional Analysis; Naval Equipment; Classification; Cost Analysis; User Needs
Language English
Publication date June 2009
Current location
IA Collections: navalpostgraduateschoollibrary; fedlink
Accession number
enterprisecomman109456939
Source
Internet Archive identifier: enterprisecomman109456939
https://archive.org/download/enterprisecomman109456939/enterprisecomman109456939.pdf

Licensing

[edit]
Public domain
This work is in the public domain in the United States because it is a work prepared by an officer or employee of the United States Government as part of that person’s official duties under the terms of Title 17, Chapter 1, Section 105 of the US Code. Note: This only applies to original works of the Federal Government and not to the work of any individual U.S. state, territory, commonwealth, county, municipality, or any other subdivision. This template also does not apply to postage stamp designs published by the United States Postal Service since 1978. (See § 313.6(C)(1) of Compendium of U.S. Copyright Office Practices). It also does not apply to certain US coins; see The US Mint Terms of Use.

File history

Click on a date/time to view the file as it appeared at that time.

Date/TimeThumbnailDimensionsUserComment
current01:55, 20 July 2020Thumbnail for version as of 01:55, 20 July 20201,275 × 1,650, 198 pages (2.03 MB) (talk | contribs)FEDLINK - United States Federal Collection enterprisecomman109456939 (User talk:Fæ/IA books#Fork8) (batch 1993-2020 #15234)

Metadata