Interoperability Problems Caused by Transitioning to a Service Oriented Environment
A major Department of Defense challenge continues to be the synchronized interoperability of multiple command and control and M&S programs. The Army has three major Command and Control (C2) efforts to contend with: ABCS migration, FCS development, and the Joint Net Enabled Command and Control (N...
Gespeichert in:
Hauptverfasser: | , , , |
---|---|
Format: | Report |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
Zusammenfassung: | A major Department of Defense challenge continues to be the synchronized interoperability of multiple command and control and M&S programs. The Army has three major Command and Control (C2) efforts to contend with: ABCS migration, FCS development, and the Joint Net Enabled Command and Control (NECC) program. These C2 systems will be operating in a Service Oriented Environment (SOE) that will be implemented/fielded in phases over time. There is no single process that is aligning these efforts at a level that includes totally synchronized technical exchanges of standards, data, and re-use of components. Two of the Army's key M&S initiatives also have development cycles that do not parallel the C2 schedules and do not yet fully address operating in a SOE. The JLCCTC development has to date been on an annual development cycle but is currently moving to a 2 year cycle. The other big M&S initiative, LVC-IA, is developing a prototype system with a target date of FY10. Integrating all of these phased C2 and M&S programs will require innovative technical and programmatic methods.
Presented at AFCEA-GMU C4I Center Symposium: Critical Issues In C4I at George Mason University, Fairfax, VA on 20-21 May 2008. The original document contains color images. |
---|