110 likes | 281 Views
Integrating Leading US C4ISR Technologies to Support Nations’ Capabilities. Bill Skidmore Engineering Manager, FMS & International Business TAMSCO. US’ Situation Awareness Communications Infrastructure Digitized Voice C2 Applications Information Sharing Security
E N D
Integrating Leading US C4ISR Technologies to Support Nations’ Capabilities Bill Skidmore Engineering Manager, FMS & International Business TAMSCO
US’ Situation Awareness Communications Infrastructure Digitized Voice C2 Applications Information Sharing Security Responds to documented recent Operational Doctrine Coalition Members Analog voice telephone and radio communications Computer-generated paper reports Responds to 1970’s Doctrine Typically Employed Technologies
Typical Nations’ Capability Requirements • Communications Infrastructure • Support Infrastructure • Information Processing • Country-specific reports • Coalition-required reporting • “Situation Awareness”
Develop Operational Concept Overview Define Organizations Develop System Architecture Capture Information Flows & Characterize Data Develop a C4ISR System Architecture using Mission Threads
Communications Infrastructure Business Process (re)Engineering using appropriate framework Identify Solution Technologies for Nations’ C4ISR Requirements Nations Requirements Roadmap Tasks Buy Communications Stuff Derive • Communications System Design Don’t forget • Define Support Infrastructure • Training • Maintenance • Transportation
Considerations for Integrating US C4ISR Technologies • Suitability • Does it address the requirements? • How much ancillary technology is needed? • Exportability • Cost • Capital • Recurring • Support
Integrating US C4ISR Technologies • Communications interoperability with legacy systems • Interoperability by purchasing the same systems - retire legacy elements • Limited interoperability because the exported capability is usually at least one version older than what the US is using • Interoperation by utilizing a gateway that can translate between legacy and objective interface • NATO telephony interoperability standards support this approach, but inherent loss of some functionality • Near-universal use of TCP/IP increases probability of success for IP-based voice and data applications (still not guaranteed) • Candidate interoperability techniques can be assessed at interoperability exercises (e.g., Combined Endeavor) But, rate of military technology improvements > military technology interoperability
Integrating US C4ISR Technologies (cont’d) • Information interoperability with legacy systems • Purchasing the same systems is unlikely due to export control restrictions • Utilizing a gateway for interoperability inherently inserts error, or causes a loss of granularity or functionality • Relying on standards is not fail-safe • Standards’ interpretation is notoriously inconsistent unless market driven (e.g., Java and XML)
Integrating US C4ISR Technologies (cont’d) • Given the significant investment to achieve infrastructure and information interoperability, probably the best way is to utilize Web Portals with underlying TCP/IP infrastructure • Often, dynamic translation is supported • Easily maintained • Relatively low cost Portal demonstrated at AFCEA Europe 2000