A platform for research: civil engineering, architecture and urbanism
A platform for research: civil engineering, architecture and urbanism
Bilateral Interoperability through Enterprise Architecture
This paper addresses the important role of architecture planning for ensuring system interoperability in a network-centric coalition environment. As U.S. forces become more dependent upon coalition partners to support crises around the globe, systems interoperability becomes a major concern. This problem is more acute in the Pacific theater, where the United States has numerous bilateral agreements with allied nations and the degree of interoperability varies from country to country. A key to understanding interoperability shortfalls is documenting the 'as is' architecture for each allied nation to identify key information exchange requirements for critical C2 nodes. Enterprise architecture planning considers both the tactical and strategic need for information exchange in supporting the organization's mission. This is especially true with the plethora of C4ISR systems scattered throughout the U.S. Pacific Command (USPACOM) theater of operations where access to secure, quality data is vital to ongoing operations. HQ USPACOM recognized the need for documenting baseline architectures with the publication of USCINCPAC Instruction 2010-4. This instruction provided guidance to component commands on how to describe and construct systems and operational architectures. The Joint Forces Program Office was asked to assist with this effort at U.S. Alaskan Command (USALCOM) in the fall of 1999. The USALCOM architecture study, using a prototype version of the Joint C4I Architecture Planning System (JCAPS), illustrated the utility of having a clearer picture of the enterprise architecture described in common lexicon, and the need to consolidate the numerous architectures that had been developed in recent years. In this paper, the authors outline a practical strategy for consolidating existing C4ISR architectures. Using their practical architectural success at USALCOM, they suggest that this methodology can be applied across large, combined, theaters of operation.
Bilateral Interoperability through Enterprise Architecture
This paper addresses the important role of architecture planning for ensuring system interoperability in a network-centric coalition environment. As U.S. forces become more dependent upon coalition partners to support crises around the globe, systems interoperability becomes a major concern. This problem is more acute in the Pacific theater, where the United States has numerous bilateral agreements with allied nations and the degree of interoperability varies from country to country. A key to understanding interoperability shortfalls is documenting the 'as is' architecture for each allied nation to identify key information exchange requirements for critical C2 nodes. Enterprise architecture planning considers both the tactical and strategic need for information exchange in supporting the organization's mission. This is especially true with the plethora of C4ISR systems scattered throughout the U.S. Pacific Command (USPACOM) theater of operations where access to secure, quality data is vital to ongoing operations. HQ USPACOM recognized the need for documenting baseline architectures with the publication of USCINCPAC Instruction 2010-4. This instruction provided guidance to component commands on how to describe and construct systems and operational architectures. The Joint Forces Program Office was asked to assist with this effort at U.S. Alaskan Command (USALCOM) in the fall of 1999. The USALCOM architecture study, using a prototype version of the Joint C4I Architecture Planning System (JCAPS), illustrated the utility of having a clearer picture of the enterprise architecture described in common lexicon, and the need to consolidate the numerous architectures that had been developed in recent years. In this paper, the authors outline a practical strategy for consolidating existing C4ISR architectures. Using their practical architectural success at USALCOM, they suggest that this methodology can be applied across large, combined, theaters of operation.
Bilateral Interoperability through Enterprise Architecture
G. A. Catania (author) / J. J. Hamilton (author) / J. D. Rosen (author) / J. Melear (author)
2000
10 pages
Report
No indication
English
Computers, Control & Information Theory , Military Operations, Strategy, & Tactics , Common Carrier & Satellite , Methodology , Theater level operations , Interoperability , Joint military activities , Network architecture , Command and control systems , Military requirements , Manhours , Network centric warfare , Relational data bases , Centralized , Integrated systems , Symposia , Information exchange , Information systems , Enterprise architecture , Architecture consolidation , Architecture development , Coalition operations , Uspacom(Us pacific command) , Best practices , C4isr(Command control communications computers intelligence surveillance reconnaissance) , Interoperability shortfalls , Usalcom(Us alaskan command) , Jcaps(Joint c4i architecture planning system) , Staff hours
ITS Architecture, Interoperability and Standards
IEEE | 2007
Interoperability Through Standards
| Wiley | 2023
Collaboration based on product lifecycles interoperability for extended enterprise
| Springer Verlag | 2010
Effective enterprise architecture
| TIBKAT | 2019