Transcription of MIL STD 3011 - idlsoc.com
{{id}} {{{paragraph}}}
Example: air traffic controller
MIL STD 3011 - idlsoc.com
MIL STD 3011 How can we make it better?Mr. Brian BassAllied Training ManagerJoint Interoperability DivisionFort McPherson, GA, Historical development of Joint Range Extension Application Protocols ( jreap ) MIL-STD 3011 Organization Applicable Documents Definitions, Terms, and Acronyms General Requirements Detailed Requirements Notes Appendices A, B, and C Technical Review of Appendices A, B, and CUNCLASSIFIED3 The Beginnings of jreap The requirement: Exchange tactical data beyond line of sight in such a manner that the data can be used for situational awareness, planning, and limited decision makingUNCLASSIFIED4 Early BLOS Link 16 Efforts Limited Interoperability Work-around was required Funding did not tie improvements in one system to the otherService UniqueNon-standardized ProtocolsSTJUHF SATCOMNavy UHF DAMAS erial JInterface to ADSIP oint-to-PointSHF SATCOML egacyPoint-to-PointSocket JLegacy IP InterfacesUNCLASSIFIED51996 CVBGRJE-2 HAWKEYEJSTARSF14/F15 AOC(JFACC)TAOC(FJUA/B)E-3 AWACS(NCS)Link 16 Link 16 PATRIOTLink 11 BLink 11 BATDLATDL--11 CRECRC(FPU)TACCATDLATDL--11 AMDPCS(AAMDC)Link 11 BLink 11 BLink 11 Link 11 PATRIOTPATRIOTPATRIOTPATRIOTICCICCAMDPCS Link 11 Link 11 BLink 16 ATDL-1 PADILB ackupUNCLASSIFIED61999 Link 11 Link 11 BSerial JLink 16 CRCTF HAWKCRECRCCRE CREA egis CG/DDLeyte GulfCVBGE-3E-3E-3 RJJSTARSABCCCE-2 UNCLASSIFIED72000 SAGBG Al
UNCLASSIFIED 3 The Beginnings of JREAP • The requirement: – Exchange tactical data beyond line of sight in such a manner that the data can be used for
Loading..
Tags:
Information
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document: