MIL STD 3011 - idlsoc.com

← Back to document page

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 CUNCLASSIFIED3The 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 makingUNCLASSIFIED4Early 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 DAMASerial JInterface to ADSIPoint-to-PointSHF SATCOMLegacyPoint-to-PointSocket JLegacy IP InterfacesUNCLASSIFIED51996CVBGRJE-2 HAWKEYEJSTARSF14/F15AOC(JFACC)TAOC(FJUA/ B)E-3 AWACS(NCS)Link 16Link 16PATRIOTLink 11BLink 11BATDLATDL--11CRECRC(FPU)TACCATDLATDL-- 11AMDPCS(AAMDC)Link 11 BLink 11 BLink 11Link 11PATRIOTPATRIOTPATRIOTPATRIOTICCICCAMDP CSLink 11Link 11BLink 16ATDL-1PADILBackupUNCLASSIFIED61999Link 11Link 11BSerial JLink 16CRCTF HAWKCRECRCCRE CREAegis CG/DDLeyte GulfCVBGE-3E-3E-3RJJSTARSABCCCE-2UNCLASS IFIED72000SAGBG AlphaBG BravoLink 11Link 11BS

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

  Jreap