OctetView
0x00000…00100 (0, 0, 0) Sector 00014130303031 ┆ A0001A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00ffe0c0ff80 ┆ `@ ~p x @ ~ ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x00, d01=0x05, d02=0x41, ptr=(56,0, 8), d05=0x00}
0x00306…0030c WangDocument {d00=0x00, d01=0x32, d02=0x41, ptr=(61,0, 0), d05=0x00}
0x0030c…00312 WangDocument {d00=0x01, d01=0x46, d02=0x41, ptr=(24,0, 0), d05=0x00}
0x00312…00318 WangDocument {d00=0x01, d01=0x57, d02=0x41, ptr=(47,0, 8), d05=0x00}
0x00318…0031e WangDocument {d00=0x01, d01=0x58, d02=0x41, ptr=(43,0, 8), d05=0x00}
0x0031e…00324 WangDocument {d00=0x01, d01=0x63, d02=0x41, ptr=(68,0, 0), d05=0x00}
0x00324…0032a WangDocument {d00=0x01, d01=0x85, d02=0x41, ptr=(46,0, 0), d05=0x00}
0x0032a…00330 WangDocument {d00=0x02, d01=0x10, d02=0x41, ptr=(66,0, 8), d05=0x00}
0x00330…00336 WangDocument {d00=0x02, d01=0x16, d02=0x41, ptr=(67,0, 8), d05=0x00}
0x00336…0033c WangDocument {d00=0x02, d01=0x21, d02=0x41, ptr=(57,0, 0), d05=0x00}
0x0033c…00340 02 21 41 39 ┆ !A9┆
0x00340…00360 00 00 02 21 41 2c 08 00 02 26 41 4a 00 42 02 21 41 2c 08 00 02 20 41 4a 00 00 02 20 41 4a 00 00 ┆ !A, &AJ B !A, AJ AJ ┆
0x00360…00380 02 20 41 4a 00 00 02 20 41 4a 00 00 02 20 41 4a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ AJ AJ AJ ┆
0x00380…003a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
[…0x2…]
0x003e0…00400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3c ┆ <┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 86312020202020 ┆ 1 8 7 Q? > 7 N d N N ^<) 0u &4'>( 1c5 & & ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' ; X% % PO P ; 2A8/ C h x h V W O 8 :D C- % 0032A h L | {C < ; c b bP n W 9 8 : > 3 B$ B$B# ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0xa…]
0x01b00…01c00 (1, 0, 11) Sector 010cff00016341 ┆ cA 1 Alfast Kjeld KJA Logistics Support 355 Caspersen Finn FC Logistics Support 354 Dunbak Kirsten Tandskov KTD Logistics Support Secr. 350 Eskedal Ole OE Logistics Support Manag┆
0x01c00…01d00 (1, 0, 12) Sector 010dff00016341 ┆ cAer 349 Haureberg Hans Erik HAU Logistics Support 346 Irgens Birthe BI Logistics Support 352 Mikkelsen Kurt KM Logistics Support 348 Nielsen Per PNN Logistics Support 355 Nielsen Peter Licht PLN Logistics Support 346 Pedersen Niels Peder NPP Logisti┆
0x01d00…01e00 (1, 0, 13) Sector 010e5300016341 ┆ S cAcs Support 346 Petersen Ole Ren} ORP Logistics Support 353 Uldam Leif LU LogiR CAMPS Operational Procedure, Performance Guide. 074 321 810928 R CAMPS Terminal Locaocessing of Classified Material 028 - (Returneret 81.03.30) ┆
0x01e00…01f00 (1, 0, 14) Sector 00009800016341 ┆ cAstics Support 345 Wunsch Erik Peter EW Logistics Support 355 Fremming Annette AF Teknisk tegner 397 Olsen Kirsten Richter KRO Teknisk tegner 397 3 129 01 10 81 12 57 30 10 81 15 21 0001A 2 7 17 48 4977 f @*J 7 _┆
0x01f00…02000 (1, 0, 15) Sector 0100ff00016341 ┆ cAen Bent M]ller BMN S/W Eng. 388 Nielsen Vini Hauris VHN Sekret`r 381 Nybroe-Nielsen Kurt KNN Software Manager 395 Olsen Svend SVO QA Manager 398 Raaschou Keld KR System Eng. 385 Rasmussen S]ren SRA H/W Eng. 384 Rommedahl Anne Marie [rum AM[ Sekret`┆
0x02000…02100 (2, 0, 0) WangDocumentBody
[…0x1…]
0x02200…02300 (2, 0, 2) Sector 0203f600015741 ┆ v WA......................... 3.5 LOGISTICS ................................ 3.5.1 Maintenance .......................... 3.5.2 Supply ............................... 3.5.3 Facilities and Facility Equipment .... ┆
0x02300…02400 (2, 0, 3) Sector 0204ff00015741 ┆ WA 1 3.6 PERSONNEL AND TRAINING ................... 3.6.1 Personnel ............................ 3.6.2 Training ............................. 3.7 FUNCTIONAL AREA ┆
0x02400…02500 (2, 0, 4) Sector 0205ff00015741 ┆ WACHARACTERISTICS .......... 3.8 PRECEDENCE ............................... 4 QUALITY ASSURANCE PROVISIONS ................. 4.1 GENERAL .................................. 4.1.1 Responsibiliby for Tests ............. 4.┆
0x02500…02600 (2, 0, 5) Sector 0206fa00015741 ┆ z WA1.2 Special Tests and Examinations ....... 4.2 QUALITY CONFORMANCE INSPECTIONS .......... 5 PREPARATION FOR DELIVERY ..................... 6 NOTES ........................................ 7 APPENDIX I .................icati┆
0x02600…02700 (2, 0, 6) Sector 00001d00015741 ┆ WA.................. vhn vhn M>ske slettes 28 08 80 09 55 42 2026 28 08 80 14 35 37 2699 28 08 80 15 14 15 09 80 14 24 0001A 2 1 19 48 4725 % f ! *J 7 _┆
0x02700…02800 (2, 0, 7) Sector 0108ff00007741 ┆ wAates. The following course dates at CR were agreed. 1 Serial Period Course Dates Students (a) (b) (c) (d) 1 May-Jun 82 17 May-18 Jun 82 10 2 Sep-┆
0x02800…02900 (2, 0, 8) WangDocumentBody
[…0x8…]
0x03100…03200 (3, 0, 1) Sector 03026000014641 ┆ ` FAperformed by project management, Quality Assurance and Customer Representative. rd SD/STD/013 Issue 1 801020 B-E Software Module/Package Documentation Standard SD/STD/008 Issue 1.1 810422 B-F SOURCE CODE LAYOUT STANDARD ┆
0x03200…03300 (3, 0, 2) Sector 0303ff00014641 ┆ FA 1 5 DISTRIBUTION A number of copies of this Manual will have an official status and their availability and updating will be controlled by The Configuration Management. One per┆
0x03300…03400 (3, 0, 3) Sector 0304f300014641 ┆ s FAson will be assigned responsible for each copy as listed: 1 COPY VOLUMES PLACE RESPONSIBLE 1 A-B-C QA Department SVO 2 A-B-C Project Manager GJ 3 A-B-CIGIN OF STAN┆
0x03400…03500 (3, 0, 4) Sector 00009200014641 ┆ FA Systems Engineering FE 4 A-B-C ILS OE 5 A-B-C Software Management KNN 6 A-B-C Hardware Management BHB 7 8 9 10 STEM DESIGN SPECIFICATION STANDARD CPS/STD/002 Issue 1 801103 3.3 SYSTEM ENGINEERING AND CONFIGURATIO┆
0x03500…03600 (3, 0, 5) Sector 0306ff00003241 ┆ 2Asisted Message Distribution System (CAMPS) Site Survey Questionnaire. 047 130 810206 R 6040/80-9009-3/SHHNC/81 SHAPE - Christian Rovsing Agreement on VDU, Frequency Stabilizer, RF Filters and EMI Racks. 048 143 810209 R 3115/SHHNS/81 Site Surveys ┆
0x03600…03700 (3, 0, 6) Sector 00001900003241 ┆ 2AData Requirements. ignals). 003 007 80-09-22 R C-M(55)15 Final W/Transmittal Letter. 004 008 80-09-22 U ACE Personnel Requisition. 005 009 80-09-22 R KN-7/BID/ 610 Interface. 006 010 80-09-22 U ACP 131 (B) Jul. 64. 007 011 80-09-22 R NICS TARE ┆
0x03700…03800 (3, 0, 7) Sector 0208ff00007741 ┆ wA Also within their reply CR will indicate the required currency mixed in accordance with the price revision procedure stipulated in appendix E.11 and E 12 of the Contract. The reply will be provided to SHAPE as soon as possible. Within two working d┆
0x03800…03900 (3, 0, 8) WangDocumentBody
[…0x46…]
0x07f00…08000 (7, 0, 15) Sector 0308ff00021041 ┆ A 15 Site No 6 ILS Week 17 Site No 3 ILS Week 20 Site No 7 ILS Week 20 Site No 2 ILS Week 24 2.6 3.Activities Du- 1981 ring the Site Pre- Week 4 through paration period ILS Week 40 2.7 4.Site Verifi- 2 Weeks fication All Sites ILS/┆
0x08000…08100 (8, 0, 0) WangDocumentBody
[…0x3…]
0x08400…08500 (8, 0, 4) Sector 0805ff00000541 ┆ A ( NAUSOUTH (AFSOUTH TBD ( MARAIRMED ) SAME ( SUBMED ) COMCONTOR ( ┆
0x08500…08600 (8, 0, 5) Sector 0806e600000541 ┆ f A ( AFSOUTH ADV. CMD POST ( LS (LANDSOUTH TBD 5 ATAF ( LSE (LSE/6 ATAF TBD 6 ATAF ( tified: REMOTE LOCATION┆
0x08600…08700 (8, 0, 6) Sector 00007400000541 ┆ t A SONOR (SONOR I NAUSONOR ( TBD MEDEAST MEDEAST TBD MEDNOREAST MEDNOREAST TBD BALTAP stallation, the Contractor will be required to verify that the site is acceptable within fourteen calender days of a fo┆
0x08700…08800 (8, 0, 7) Sector 0708ff00016341 ┆ cAg LSN Program Manager 131 Nybroe-Nielsen Kurt KNN Engineering Manager 194 Olsen Svend SVO QA Manager 285 Poulsen Leif LP System eng. 272 Rasmussen S]ren SRA H/W Eng. 272 Ringgaard Jens Peter JPR Principal Systems Eng. 193 Rommedahl Anne Marie [ru┆
0x08800…08900 (8, 0, 8) Sector 0809ff00016341 ┆ cADorte DHH Sekret`r 382 Hansen Jens E. Heldbo JHH S/W Engineer 391 Hervik Ole OHE H/W Engineer 417 Holgersen Erik EHO S/W Engineer 399 Johannsen Niels NJO Technician 408 J]rgensen Finn FNJ System Engineer 385 Kristensen Henning D HDK S/W Engineer 389┆
0x08900…08a00 (8, 0, 9) Sector 080aff00016341 ┆ cA K`rvang Ejler EK S/W Engineer 401 Larsen Irene IL System Engineer 379 Larsen Poul POL H/W Engineer 355 Larsen Djon DL H/W Engineer 354 Lauridsen Jan JAL Program Manager 394 Madsen Bent G>rds]e BGM S/W Engineer 358 Mortensen Peter PFM System Engine┆
0x08a00…08b00 (8, 0, 10) Sector 080bff00016341 ┆ cAer 379 Nielsen Lars LN S/W Engineer 369 Pedersen Carsten CP Sekret`r assistance 381 Petersen Allan AAP Technician 408 Rosendahl J]rgen JRD H/W Engineer 353 Schlichter Torben TS S/W Engineer 306 Schmidt Lise Rerup LRS S/W Engineer 378 Siomka J]rgen B┆
0x08b00…08c00 (8, 0, 11) Sector 080cd800016341 ┆ X cAjarne JBS S/W Engineer 386 Ultved Peter PU S/W Engineer 401 Verwohlt Hans HAV S/W Engineer 391 Waldhauer Poul Erik PEW Technician 408 West Annette R]nnow ARW S/W Engineer 392 Wunsch Erik EPW H/W Engineer 417 lket? Bytte med? S]ge hvilket? ┆
0x08c00…08d00 (8, 0, 12) Sector 080d5700016341 ┆ W cA 1 ommando JA eller ANNULLER Kun tal Kun mellemrum eller retur Under redigering nu Ukendt dokument Fundet I brug nu Allerede p> systemdiskette ┆
0x08d00…08e00 (8, 0, 13) Sector 0000e500016341 ┆ e cAAfdeling 3031 - Special Projects Abdulrahman Ilyas IA H/W Engineer 342 Bjorholm Peder Lindel]v S]ren SL S/W Engineer 343 Nielsen Pia PAN Sekret`r 339 Nissen Nis NMN S/W Engineer 412 Petersen Allan APE S/W Engineer 342 ┆
0x08e00…08f00 (8, 0, 14) Sector 080fff00016341 ┆ cA 1 Alfast Kjeld KJA Logistics Support 355 Caspersen Finn FC Logistics Support 354 Dunbak Kirsten Tandskov KTD Logistics Support Secr. 350 Eskedal Ole OE Logistics Support Manag┆
0x08f00…09000 (8, 0, 15) Sector 0100ff00016341 ┆ cAer 349 Haureberg Hans Erik HAU Logistics Support 402 Hervik Ole Logistics Support 355 Irgens Birthe BI Logistics Support 352 Larsen Leif O. LOL Logistics Support 355 Lyngby Christian CL Logistics Support 345 Mikkelsen Kurt KM Logistics Support 348┆
0x09000…09100 (9, 0, 0) WangDocumentBody
[…0x7c…]
0x10d00…10e00 (16, 0, 13) Sector 100eff00016341 ┆ cA 1 850530/dhh 0 LOKALNUMRE OG INITIALER I GSD LOKALNUMRE OG INITIALER I GSD LOKA┆
0x10e00…10f00 (16, 0, 14) Sector 100fff00016341 ┆ cALNUMRE OG INITIALER I GSD LOKALNUMRE OG INITIALER I GSD LOKALNUMRE OG INITIALER I GSD 1 Afdeling 3032 - CAMPS Andersen Janet JAA Sekret`r 381 Awaad Mohamed MA S/W Engineer┆
0x10f00…11000 (16, 0, 15) Sector 0808ff00016341 ┆ cA 358 Christensen Tom TC S/W Engineer 392 Christiansen Jan Sch]nnemann JSC S/W Engineer 389 Elleboe Flemming FLE S/W Engineer 396 Farver Niels NIF S/W Engineer 392 Frederiksen J]rn J[F Technician 408 Gudjonsson Jens Oddur OJG H/W Engineer 398 Hansen ┆
0x11000…11100 (17, 0, 0) WangDocumentBody
[…0x9…]
0x11a00…11b00 (17, 0, 10) Sector 110bff00015841 ┆ XArrupts with priority higher than or equal to the priority of the process executing in the CPU are serviced. I/O interrupts can be handled by user defined microprogram or result in swithching of software process. TIMER interrupts normally occur every┆
0x11b00…11c00 (17, 0, 11) Sector 110cff00015841 ┆ XA 150 us and are serviced by u-program. When received the TIMER register is decremented and tested (takes 2 cycles). If negative a local interrupt is generated. CPU interrupts are serviced by the u-program, handling the message related to the interru┆
0x11c00…11d00 (17, 0, 12) Sector 110dff00015841 ┆ XApt. Depending on the message a switch of software process may take place or he current process may continue. 2.2.1.3 Memory Modules 2.2.1.3.1 CR80D Memory Management Background to Address Translation The concept behind the various memory m┆
0x11d00…11e00 (17, 0, 13) Sector 110eff00015841 ┆ XAanagement features available with the CR80D computer is that of "Logical-to-Physical Address Translation". The amount of memory required by a user's program is defined to be his "logical address space". This space may be as large as 64 1K pages. The┆
0x11e00…11f00 (17, 0, 14) Sector 110fff00015841 ┆ XA areas of physical storage assigned to the user are defined to be his "physical address space". The address translation function that converts addresses in the logical space to address in the physical space is called the "address map segment" for th┆
0x11f00…12000 (17, 0, 15) Sector 1100ff00015841 ┆ XAat user. Each user has his own, unique logical-to-physical address map. In addition, there are separate map segments for I/O data channel. The CR80D Advanced Multiprocessing Operating System (DAMOS) determines what thes maps are to be, and then rela┆
0x12000…12100 (18, 0, 0) WangDocumentBody
[…0x5e…]
0x17f00…18000 (23, 0, 15) Sector 1008ff00003241 ┆ 2A 1 054 197 810504 C Discrepancy List to CR Document CPS/TCN/022, Issue 1. 055 - 810508 R CID Appendix E1 Format Definitions (Burroughs) 056 - 810508 R Memorandum: CAMPS Address┆
0x18000…18100 (24, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(24,0, 1), len=0xff, h3=41014641}, f00=»0146A «, f01=»CPS/STM/001 «, f02=»vhn/sdv «, f03=»SVO «, f04=»CAMPS STD. MANUAL «, f05=22-08-80 09:42, f06=» «, f07=»11 «, f08=» 247 «, f09=22-05-81 09:33, f10=» «, f11=»02 «, f12=» 51 «, f13=22-05-81 09:36, f14=22-05-81 09:38, f15=»0001A «, f16=» 9 «, f17=» 7 «, f18=»15 «, f19=» 120 «, f20=» 10698 «, f21=» «, f22=» «, f99=020001000120056610a10a80aaca15050000000000000030032900df}
0x18100…18200 (24, 0, 1) WangDocumentBody
[…0x136…]
0x2b800…2b900 (43, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(43,0, 9), len=0xff, h3=41015841}, f00=»0158A «, f01=»PROPOSED CAMPS HARDWARE C «, f02=»ONFIGURATION AM[ «, f03=»BHB «, f04=»FRA STARTEN «, f05=29-08-80 15:23, f06=» 4 «, f07=»24 «, f08=» 13747 «, f09=10-09-80 09:19, f10=» «, f11=»19 «, f12=» 501 «, f13=10-09-80 12:26, f14=11-09-80 09:37, f15=»0001A «, f16=»108 «, f17=» 18 «, f18=»02 «, f19=» 1328 «, f20=» 33470 «, f21=» «, f22=» «, f99=300030000120056610a10a80aaca15050000000000000030038a01df}
0x2b900…2ba00 (43, 0, 9) WangDocumentBody
[…0x26…]
0x2e000…2e100 (46, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(46,0, 1), len=0xff, h3=41018541}, f00=»0185A «, f01=»SW Terminology Standard «, f02=»vhn «, f03=»KFL «, f04=»SD/STD/009 «, f05=12-09-80 10:32, f06=» 5 «, f07=»53 «, f08=» 22743 «, f09=07-05-81 11:10, f10=» «, f11=»00 «, f12=» 6 «, f13=07-05-81 11:13, f14=14-05-81 12:00, f15=»0001A «, f16=» 21 «, f17=» 7 «, f18=»55 «, f19=» 364 «, f20=» 27364 «, f21=» «, f22=» «, f99=800001000120056610a10a80aaca15050000000000000037037000df}
0x2e100…2e200 (46, 0, 1) WangDocumentBody
[…0x16…]
0x2f800…2f900 (47, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(47,0, 9), len=0xff, h3=41015741}, f00=»0157A «, f01=»TABLE OF CONTENTS «, f02=»vhn «, f03=»vhn «, f04=»M>ske slettes «, f05=28-08-80 09:55, f06=» «, f07=»42 «, f08=» 2026 «, f09=22-09-80 13:04, f10=» «, f11=»00 «, f12=» 6 «, f13=22-09-80 13:04, f14=22-09-80 13:07, f15=»0001A «, f16=» 2 «, f17=» 2 «, f18=»46 «, f19=» 64 «, f20=» 5937 «, f21=» «, f22=» «, f99=020020000120056610a10a80aaca15050000000000000037031200df}
0x2f900…2fa00 (47, 0, 9) WangDocumentBody
[…0x8e…]
0x38800…38900 (56, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(56,0, 9), len=0xff, h3=41000541}, f00=»0005A «, f01=»site preparation «, f02=»am] «, f03=»oe «, f04=» «, f05=07-05-80 13:05, f06=» 1 «, f07=»42 «, f08=» 8959 «, f09=17-10-80 09:24, f10=» «, f11=»01 «, f12=» 9 «, f13=17-10-80 09:26, f14=17-10-80 09:27, f15=»0001A «, f16=» 39 «, f17=» 20 «, f18=»44 «, f19=» 556 «, f20=» 33410 «, f21=» «, f22=» «, f99=300020000100006610a10a80aaca1505000000000000003703b400df}
0x38900…38a00 (56, 0, 9) WangDocumentBody
[…0x6…]
0x39000…39100 (57, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(57,0, 1), len=0xff, h3=41022141}, f00=»0221A «, f01=»CPS/QAP/001 «, f02=»vhn «, f03=»SVO «, f04=»CPS QAP PLAN «, f05=29-09-80 14:46, f06=» 3 «, f07=»16 «, f08=» 11301 «, f09=21-01-82 11:53, f10=» «, f11=»00 «, f12=» 6 «, f13=19-01-82 10:10, f14=26-01-82 12:36, f15=»0001A «, f16=» 15 «, f17=» 5 «, f18=»46 «, f19=» 228 «, f20=» 16231 «, f21=» «, f22=» «, f99=110021000120056610110480aaca15050000000000000037034300df}
0x39100…39200 (57, 0, 1) WangDocumentBody
[…0x3e…]
0x3d000…3d100 (61, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(61,0, 1), len=0xff, h3=41003241}, f00=»0032A «, f01=»bibliotek CAMPS «, f02=»am] «, f03=»am] «, f04=»multi l`kkert N<! «, f05=23-09-80 14:22, f06=» «, f07=»58 «, f08=» 1302 «, f09=11-01-83 18:13, f10=» «, f11=»16 «, f12=» 1105 «, f13=11-01-83 18:31, f14=11-01-83 18:44, f15=»0001A «, f16=» 12 «, f17=» 4 «, f18=»05 «, f19=» 168 «, f20=» 10521 «, f21=» «, f22=» «, f99=020010000110066610110260aaca15050000000000000028033700df}
0x3d100…3d200 (61, 0, 1) WangDocumentBody
[…0x56…]
0x42800…42900 (66, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(66,0, 9), len=0xff, h3=41021041}, f00=»0210A «, f01=»Supp. by ILS to FIKS «, f02=»kk «, f03=»KM «, f04=» «, f05=22-09-80 10:53, f06=» 3 «, f07=»13 «, f08=» 15245 «, f09=30-10-80 10:03, f10=» «, f11=»12 «, f12=» 629 «, f13=30-10-80 10:20, f14=30-10-80 10:23, f15=»0001A «, f16=» 25 «, f17=» 11 «, f18=»46 «, f19=» 312 «, f20=» 28902 «, f21=» «, f22=» «, f99=300020000120056610a10a80aaca15050000000000000030036700df}
0x42900…42a00 (66, 0, 9) WangDocumentBody
[…0xe…]
0x43800…43900 (67, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(67,0, 9), len=0xff, h3=41021641}, f00=»0216A «, f01=»TEST PROCEDURE STANDARD «, f02=»VHN «, f03=»KFL «, f04=»SD/STD/011 «, f05=25-09-80 10:54, f06=» 1 «, f07=»36 «, f08=» 9378 «, f09=13-07-83 08:40, f10=» «, f11=»37 «, f12=» 40 «, f13=13-07-83 08:34, f14=13-07-83 09:18, f15=»0001A «, f16=» 10 «, f17=» 3 «, f18=»52 «, f19=» 144 «, f20=» 20450 «, f21=» «, f22=» «, f99=020030010020056610110280aaca94050000000000000037033000df}
0x43900…43a00 (67, 0, 9) WangDocumentBody
[…0x6…]
0x44000…44100 (68, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(68,0, 1), len=0xff, h3=41016341}, f00=»0163A «, f01=»Personliste ECC «, f02=»dhh «, f03=»dhh «, f04=» «, f05=02-09-80 10:24, f06=» «, f07=»34 «, f08=» 868 «, f09=08-10-86 08:40, f10=» 1 «, f11=»27 «, f12=» 1669 «, f13=02-12-85 13:36, f14=09-12-85 16:16, f15=»0001A «, f16=» 3 «, f17=» 18 «, f18=»24 «, f19=» 76 «, f20=» 15507 «, f21=» «, f22=» «, f99=100020000000542710110260aaca17040000000000000137031500df}
0x44100…44200 (68, 0, 1) WangDocumentBody
[…0x6…]
0x44800…44900 (68, 0, 8) Sector 4409ff00021641 ┆D Ae 36 (35): M]de for nye medlemmer. Aftale dato m.v. med v`lgerforeningens formand. (Kjeld Lund og Hans Brusch). Uge 37: M]de med Annelise Gotfredsen og Lars P. Gammelgaard. (Kjeld Lund). Uge 41: Et erhvervsorienteret m]de med f.eks. C┆
0x44900…44a00 (68, 0, 9) Sector 440aff00021641 ┆D Alaus Toksvig, T. Bak Jensen eller Preben Juel Kj`r (Peter Skafte og Poul Posander). Uge 45: M]de med borgmesteren (Kjeld Lund). 28. december: Julefest (Peter Skafte). Uge 2, 1984: Andespil, helst torsdag 12. januar. (Peter Skafte o┆
0x44a00…44b00 (68, 0, 10) Sector 440bff00021641 ┆D Ag Poul Posander). 2. Der har v`ret fremsat forslag om "G>-Hjem-M]der" eller "Klokken-Fem-M]der" eller lignende. Hanne Weng arbejder med id}en. 3. Kvindekredsen afholder skovtur den 15. august til Annelise Gotfredsens sommerhus. 4. N`ste udvalg┆
0x44b00…44c00 (68, 0, 11) Sector 440c6b00021641 ┆D k Asm]de afholdes mandag den 6. juni 1983 hos Kjeld Lund, Dalstr]get 112. 18. maj 1983 Kjeld Lund sary to obtain the expected output. b) If some data cannot be determined in beforehand (e.g. date, operator code), and these data have influence o┆
0x44c00…44d00 (68, 0, 12) Sector 440dff00021641 ┆D A 1 Kjeld Lund Dalstr]get 112 2860 S]borg Tlf. 01 - 69 22 25, arb: 02 - 65 11 44 18. maj 1983 J.C. Holst & S]n A/S att: forretningsf┆
0x44d00…44e00 (68, 0, 13) Sector 440eff00021641 ┆D A]rer Togo Christoffersen Rugmarken 27 B 3520 Farum K`re Togo! Da du tilsyneladende ikke tager mig alvorligt, n>r jeg taler med dig, skal jeg hermed give dig en skriftlig reklamation. Du erindrer sikkert, at vi talte om oplakering af min bil┆
0x44e00…44f00 (68, 0, 14) Sector 440fff00021641 ┆D A i midten af april i >r. Vi talte om prisen, men diskuterede den egentlig ikke. Du sagde, at det ville koste ca. 4.000 - 4.500 kr. at f> udf]rt en perfekt oplakering, s> bilen kom til at se ud som ny, incl. total "afkl`dning" og "p>kl`dning" af bile┆
0x44f00…45000 (68, 0, 15) Sector 4400ff00021641 ┆D An, og ef- ter en s>dan oplakering ville du give et >rs garanti mod gennem- rustning af lakken. (Oven i prisen ville antagelig komme nogle f> monteringsclips). Jeg accepterede prisen uden diskussion, fordi jeg foretrak et godt stykke arbejde fremfor ┆
0x45000…45100 (69, 0, 0) Sector 4501ff00021641 ┆E A 1 c) If such a action shall be performed simultaneously with an ordinary action, and an assistant to the test conductor is thus necessary, this must be stated. 3.6 INTERMEDIATE RE┆
0x45100…45200 (69, 0, 1) Sector 4502ff00021641 ┆E ASULTS a) This section deals with intermediate results, i.e. output which cannot be recorded. That comprises e.g. "Bell rings for 10 seconds", "Alarm light switched on". b) Such intermediate results shall be listed in their order of appearance an┆
0x45200…45300 (69, 0, 2) Sector 4503ff00021641 ┆E Ad numbered by the number of the input step performed immediately before the result. 3.7 EXPECTED OUTPUT 3.7.1 Description of Expected Output a) Expected output shall be described exactly as it is expected to appear. b) This includes an ind┆
0x45300…45400 (69, 0, 3) Sector 4504ff00021641 ┆E Aication of which output medium is used for output. c) If some output is dependent on input not determinable in beforehand, (e.g. date, operator code), it shall be stated which relation the output must have to the input. 3.7.2 Recording of Outpu┆
0x45400…45500 (69, 0, 4) Sector 4505c300021641 ┆E C At a) To facilitate a thorough scrutiny of the output it should be logged or hard copies printed to an extent which is reasonable, the importance of the specific test taken into account. erstandable and to ensure proper test of any requirement. ┆
0x45500…45600 (69, 0, 5) Sector 4506ff00021641 ┆E A 1 b) Hardcopies and log prints shall be marked sufficiently to identify them to the test run producing them. 3.7.3 Identification of Output a) The expected output shall be liste┆
0x45600…45700 (69, 0, 6) Sector 4507eb00021641 ┆E k Ad in the order of appearance. b) The expected output list shall be numbered in accordance with the input list. Any output item shall bear the number of the input step performed immediately before the appearance of the output. ly stated. b) Spec┆
0x45700…45800 (69, 0, 7) Sector 4408ff00021641 ┆D A 1 M[DEUDVALGET Udvalgsm]de afholdtes 26. april 1983 hos Hans Brusch. Alle var til stede. 1. Det besluttedes at arbejde p> at f> f]lgende program stablet p> benene: Ug┆
0x45800…45900 (69, 0, 8) Sector 4509ff00021641 ┆E A demanded shall also be clearly stated. b) Other special set-up may be e.g. cold start, absence of some databases, etc. 3.5 INPUT 3.5.1 General a) In this section the term "input" is used in a very broad sense meaning any sort of action pe┆
0x45900…45a00 (69, 0, 9) Sector 450a2600021641 ┆E & Arformed by the test conductor. 3.1.1.3 Special Set-Up If a special set-up is necessary for the execution of the test procedure this must be clearly stated. ┆
0x45a00…45b00 (69, 0, 10) Sector 450bff00021641 ┆E A 1 b) Any input must be clearly and unambiguously described. c) The input descriptions must be consecutively numbered commencing with 1. Each separate action must be considered a nu┆
0x45b00…45c00 (69, 0, 11) Sector 450cff00021641 ┆E Ambered step. 3.5.2 Data Input a) All data input must be described in details to the extent necessary to obtain the expected output. b) If some data cannot be determined in beforehand (e.g. date, operator code), and these data have influence o┆
0x45c00…45d00 (69, 0, 12) Sector 450dff00021641 ┆E An the expected output, this must be considered when constructing the expected output. c) It must be clearly stated which medium carries the input. If several identical media are connected to the system, it must be stated which medium to use (e.g. ┆
0x45d00…45e00 (69, 0, 13) Sector 450eff00021641 ┆E Anot "a VDU terminal" but "VDU terminal No. 3"). 3.5.3 Other Ordinary Input a) Other ordinary input comprises actions normally performed in the systems environment, e.g. pressing a function key. b) Also this sort of input shall be described un┆
0x45e00…45f00 (69, 0, 14) Sector 450fff00021641 ┆E Aambiguously. 3.5.4 Extraordinary Input a) Extraordinary input is actions not normally performed during operation of the system. It might be the swithching off of a VDU terminal to simulate a break-down. b) It is essential to describe exactly ┆
0x45f00…46000 (69, 0, 15) Sector 45002e00021641 ┆E . Ahow such an action shall be performed. which they are tested. Such requirements may be described in a "dummy" test procedure referring to representative tests. 3.2.2 Listing of Requirements a) All specific require┆
0x46000…46100 (70, 0, 0) Sector 4601ff00021641 ┆F Aments tested in the procedure shall be listed by reference to the Systems Requirements Specification (SRS) by numbers. b) This list shall be sequenced by the SRS requirements numbers. c) The step number of the test in which a requirement is demo┆
0x46100…46200 (70, 0, 1) Sector 4602ff00021641 ┆F Anstrated shall be placed in the requirements list adjacent to the requirement number (if applicable) 3.3 CONFIGURATION 3.3.1 Standard Configuration a) If a test may be run in any configuration of a system this shall be clearly stated. b) I┆
0x46200…46300 (70, 0, 2) Sector 4603ff00021641 ┆F Af a test can be run in any configuration but for some reason should be run in one or several special environment(s), standard configuration must not be stated. In such cases the special environment shall be described either in the Configuration sect┆
0x46300…46400 (70, 0, 3) Sector 4604ff00021641 ┆F Aion or in the Special Sut-Up section. 3.3.2 Minimum Configuration a) If a minimum configuration of the system (hardware as well as software) is necessary for a successful test run, this minimum must be clearly described. b) The reason for the┆
0x46400…46500 (70, 0, 4) Sector 46054c00021641 ┆F L A demand for a minimum configuration must be stated if not obvious. his standard is to ensure that all test procedures are constructed in a homogenous way in order to make them easily understandable and to ensure proper test of any requirement. ┆
0x46500…46600 (70, 0, 5) Sector 4606ff00021641 ┆F A 1 3.3.3 Maximum Configuration a) If a maximum configuration for some reason is demanded (e.g. to demonstrate the ability to run a task in a small system) this shall be clearly state┆
0x46600…46700 (70, 0, 6) Sector 4607ff00021641 ┆F Ad. b) Only relevant limitations of the configuration must be stated in this section. 3.4 SPECIAL SET-UP 3.4.1 Special Hardware Set-Up a) Any special hardware set-up demanded prior to the start of the test shall be clearly stated. b) Spec┆
0x46700…46800 (70, 0, 7) Sector 4508ff00021641 ┆E Aial hardware set-up may be simulated break-down or malfunction. c) Simulation of break-down or repair of hardware during test is considered input and should be described in the input section. 3.4.2 Other Special Set-Up a) Other special set-up┆
0x46800…46900 (70, 0, 8) Sector 4609ff00021641 ┆F Ahe requirements tested in the test procedure must be listed in an unambiguous way by references to the System Requirements Specification. 3.1.1.2 Configuration A description of the minimum and/or maximum hardware and software configuration that┆
0x46900…46a00 (70, 0, 9) Sector 460aac00021641 ┆F , A must be available for the test. 3.1.1.3 Special Set-Up If a special set-up is necessary for the execution of the test procedure this must be clearly stated. ┆
0x46a00…46b00 (70, 0, 10) Sector 460bff00021641 ┆F A 1 3.1.1.4 Input The input to the test procedure must be described thouroughly and in the sequence in which it should be input. 3.1.1.5 Intermediate Results Intermediate results┆
0x46b00…46c00 (70, 0, 11) Sector 460cff00021641 ┆F A which should be checked during the test must be clearly stated in conjunction with the instants in which they should appear. 3.1.1.6 Output A complete list of expected output must be included in the test procedure stating both the output mediu┆
0x46c00…46d00 (70, 0, 12) Sector 460dff00021641 ┆F Am and the instant in which the output is expected. 3.1.1.7 Cross Reference A list of all requirements referring to the test procedures in which they are tested is established in accordance with TBD. 3.2 REQUIREMENTS TESTED 3.2.1 Verbal De┆
0x46d00…46e00 (70, 0, 13) Sector 460eff00021641 ┆F Ascription a) The Requirements Tested section shall commence with a brief verbal description of the specific requirements, thus enlightening the purpose of the test procedure. b) General requirements which are tested or demonstrated repeatedly in┆
0x46e00…46f00 (70, 0, 14) Sector 460f8200021641 ┆F A a great number of test procedures (e.g. the output format of certain data) need not be described in all test procedures in 3.2 REQUIREMENTS TESTED .................. 6 3.2.1 Verbal Description ............... 6 3.2.2 Listing of Re┆
0x46f00…47000 (70, 0, 15) Sector 4600ff00021641 ┆F A 1 which they are tested. Such requirements may be described in a "dummy" test procedure referring to representative tests. 3.2.2 Listing of Requirements a) All specific require┆
0x47000…47100 (71, 0, 0) Sector 4701ff00021641 ┆G AUP ....................... 8 3.4.1 Special Hardware Set-Up .......... 8 3.4.2 Other Special Set-Up ............. 8 3.5 INPUT ................................ 8 3.5.1 General .......................... 8 3.5.2 Data ┆
0x47100…47200 (71, 0, 1) Sector 4702ff00021641 ┆G AInput ....................... 9 3.5.3 Other Ordinary Input ............. 9 3.5.4 Extraordinary Input .............. 9 3.6 INTERNEDIATE RESULTS ................. 10 3.7 EXPECTED OUTPUT ...................... 10 3.7.1 ┆
0x47200…47300 (71, 0, 2) Sector 47039300021641 ┆G ADescription of Expected Output ... 10 3.7.2 Recording of Output .............. 10 3.7.3 Identification of Output ......... 11 C_* ┆
0x47300…47400 (71, 0, 3) Sector 4704ff00021641 ┆G A 1 1 SCOPE AND PURPOSE 1.1 SCOPE This standard is applicable to all formal test procedures necessary to verify the correct function of all parts of a system and to ensure that a┆
0x47400…47500 (71, 0, 4) Sector 4705ff00021641 ┆G All requirements have been fulfilled. 1.2 PURPOSE The purpose of this standard is to ensure that all test procedures are constructed in a homogenous way in order to make them easily understandable and to ensure proper test of any requirement. ┆
0x47500…47600 (71, 0, 5) Sector 47063700021641 ┆G 7 A 2 APPLICABLE DOCUMENTS TBD ┆
0x47600…47700 (71, 0, 6) Sector 4707ff00021641 ┆G A 1 3 TEST PROCEDURES 3.1 GENERAL a) This section deals with the general contents and logical sequence of a test procedure. b) All of the items identified by the headings of se┆
0x47700…47800 (71, 0, 7) Sector 4608ff00021641 ┆F Actions 3.1.1.1 through 3.1.1.6 shall be present in a test procedure. and in the sequence used herein. c) If one or more of the items are not applicable, this shall be stated. 3.1.1 Contents of a Test Procedure 3.1.1.1 Requirements Tested T┆
0x47800…47900 (71, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(71,0, 9), len=0xff, h3=41021641}, f00=»0216A «, f01=»TEST PROCEDURE STANDARD «, f02=»VHN «, f03=»KFL «, f04=»SD/STD/011 «, f05=25-09-80 10:54, f06=» 1 «, f07=»36 «, f08=» 9378 «, f09=19-05-83 02:37, f10=» «, f11=»59 «, f12=» 8697 «, f13=18-05-83 18:19, f14=18-05-83 18:33, f15=»0001A «, f16=» 14 «, f17=» 3 «, f18=»14 «, f19=» 368 «, f20=» 20393 «, f21=» «, f22=» «, f99=020030010020056610110280aaca94050000000000000037035b00df}
0x47900…47a00 (71, 0, 9) Sector 470a0e00021641 ┆G A G G G G F F F E E E E D D C > ┆
0x47a00…47b00 (71, 0, 10) Sector 470b9000021641 ┆G A 1 SD/STD/011 KFL/801020 # TEST PROCEDURE STANDARD SD 'C*-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x47b00…47c00 (71, 0, 11) Sector 470cff00021641 ┆G A 1 1 TABLE OF CONTENTS 1 SCOPE AND PURPOSE ....................... 4 1.1 SCOPE ........................┆
0x47c00…47d00 (71, 0, 12) Sector 470dff00021641 ┆G A........ 4 1.2 PURPOSE .............................. 4 2 APPLICABLE DOCUMENTS ..................... 4 3 TEST PROCEDURES .......................... 5 to 11 3.1 GENERAL .............................. 5 3.1.1 Contents o┆
0x47d00…47e00 (71, 0, 13) Sector 470eff00021641 ┆G Af a Test Procedure ..... 5 3.1.1.1 Requirements Tested .......... 5 3.1.1.2 Configuration ................ 5 3.1.1.3 Special Set-Up ............... 5 3.1.1.4 Input ........................ 6 3.1.1.5 Intermedia┆
0x47e00…47f00 (71, 0, 14) Sector 470fff00021641 ┆G Ate Results ......... 6 3.1.1.6 Output ....................... 6 3.1.1.7 Cross Reference .............. 6 3.2 REQUIREMENTS TESTED .................. 6 3.2.1 Verbal Description ............... 6 3.2.2 Listing of Re┆
0x47f00…48000 (71, 0, 15) Sector 4700ff00021641 ┆G Aquirements .......... 7 3.3 CONFIGURATION ........................ 7 3.3.1 Standard Configuration ........... 7 3.3.2 Minimum Configuration ............ 7 3.3.3 Maximum Configuration ............ 8 3.4 SPECIAL SET-┆
0x48000…48100 (72, 0, 0) Sector 4801ff00000341 ┆H An and maximum ranges for each radar will be shown. 4.10 History plots will be presented along with current plots (different symbols) - 1,2,3,4,5 or 6 history plots may be selected by the operator and they will be presented in ripple┆
0x48100…48200 (72, 0, 1) Sector 4802ff00000341 ┆H A fashion - history plots may be turned off but preserved. 4.11 Coastline, GEOREF, and time segment maps will be stored and displayed on demand. 4.12 Tracks will be displayed by vectors originating at the track position, extending in th┆
0x48200…48300 (72, 0, 2) Sector 4803ff00000341 ┆H Ae direction of movement (within 2 degrees of tolerance), and extending 1.5mm for each 50 knots of speed. 4.13 Track numbers will be selectable for each track, displayed close to the track, and movable by operator command. 4.14 NAI ┆
0x48300…48400 (72, 0, 3) Sector 4804ff00000341 ┆H Aareas, blank areas, and TXA areas will be displayed separately. 5. Link-1 Communication with NADGE Site 5.1 Link-1 duplex communication - crosstell protocol. 5.2 Receipt of remote tracks. 5.3 Linkage to single NADGE site - relinking if ┆
0x48400…48500 (72, 0, 4) Sector 48058400000341 ┆H Aappropriate. 5.4 Fallback functioning upon NADGE failure. 5.5 Crosstell system strobes to NADGE via Link-1 S.6 message. recursive 2nd or 3rd order filter which must be adaptive and especially suited to maneuvers. 2.11 Automatic inser┆
0x48500…48600 (72, 0, 5) Sector 4806ff00000341 ┆H A W 5.6 S.O./S.O. test message exchanged both ways every 10 + 1 seconds. 5.7 Crosstell track information both ways using S.4, S.3, S.5, and S.14 messages. 5.8 Utilize a cross┆
0x48600…48700 (72, 0, 6) Sector 4807ff00000341 ┆H Atell area (TXA) for crosstell from CRIS to NADGE. 5.9 TXA must be variable in size and proportion with sides parallel to X & Y axes. 5.10 NADGE will tell CRIS all tracks except those outside CRIS coverage, tracks told by CRIS, and tra┆
0x48700…48800 (72, 0, 7) Sector 4708ff00000341 ┆G Acks referenced in S.14 STOP TELL message. 5.11 CRIS will tell NADGE all tracks except tracks known to NADGE, tracks outside the TXA, and tracks with an ID not qualified for crosstell. 5.12 Common tracks will be told by CRIS if CRIS tra┆
0x48800…48900 (72, 0, 8) Sector 4809ff00000341 ┆H A W 2.20 Control and track repair shall include: W - Mask entry - Maps raid designation (with area 16,32, or 64 ┆
0x48900…48a00 (72, 0, 9) Sector 480aff00000341 ┆H A DM/side). These will be treated as blank areas - at least 3 must be supported - New track/position update - Enter height - Interchange track data (except position) - Drop track W ┆
0x48a00…48b00 (72, 0, 10) Sector 480bff00000341 ┆H A 3. Passive Tracking W 3.1 Generation of strobe line symbols from strobe data. 3.2 Designation of system strobes via switch action. 3.3 Control and manage system ┆
0x48b00…48c00 (72, 0, 11) Sector 480cff00000341 ┆H Astrobes with following switch actions: - Enter strobe - Enter strobe width - Update strobe - Drop strobe 3.4 Process up to six system strobes 4. Display of Plot, Track, Strobe and Background Picture Data 4.1 Generation and update of┆
0x48c00…48d00 (72, 0, 12) Sector 480dff00000341 ┆H A 7168 point, 3 bit amplitude clutter maps for each radar. 4.2 Calculate time reference for each plot by using time of receipt for a North Mark, the time interval between North Marks, and plot azimuth. 4.3 Display of strobe line symbols┆
0x48d00…48e00 (72, 0, 13) Sector 480ec600000341 ┆H F A at original radar positions on the display. 4.4 Removal of strobe line symbols at cessation of update. 4.5 Display results of multiradar tracking as a surveillance air picture. tracks. 2.2 Track within the following performance param┆
0x48e00…48f00 (72, 0, 14) Sector 480fff00000341 ┆H A W 4.6 Track symbols will initially be NADGE standard but will later be STANAG 1241. 4.7 Display of all plot data from one or more (to 8) radar heads (200 plots/head). 4.8 ┆
0x48f00…49000 (72, 0, 15) Sector 4800ff00000341 ┆H AFor single radar presentation, the RH must be centered and range rings generated every 10 miles from center to 50 miles (selectable by operator). 4.9 For multiple radar presentation, RH position will be marked relative to a common origi┆
0x49000…49100 (73, 0, 0) Sector 4901ff00000341 ┆I Aor less heading error : 4 o or less - 3 radar coverage, maneuvering target position error : 1.3 DM or less W 2.3 Local track store capacity of 275 tracks (60% growth ┆
0x49100…49200 (73, 0, 1) Sector 49026100000341 ┆I a A factor). 2.4 Automatic initiation and tracking with minimum operator intervention. ┆
0x49200…49300 (73, 0, 2) Sector 4903ff00000341 ┆I A W 2.5 Switch action designation of following based on clutter maps: - Auto initiate and tracking allowed (AI areas). - Auto initiate not allowed, auto tracking allowed ┆
0x49300…49400 (73, 0, 3) Sector 4904ff00000341 ┆I A(NAI areas). - Auto initiate and tracking not allowed (Blank areas). 2.6 Masking on radar head tests and reflected UTA display. 2.7 Storage of masking areas as 800 cells/radar (corresponding to clutter map data ). 2.8 Selection of ┆
0x49400…49500 (73, 0, 4) Sector 4905ff00000341 ┆I Amasking areas by selection of point pairs. 2.9 Track update based on all radar input. 2.10 Smoothing based on up-to-date recursive 2nd or 3rd order filter which must be adaptive and especially suited to maneuvers. 2.11 Automatic inser┆
0x49500…49600 (73, 0, 5) Sector 4906ff00000341 ┆I Ation of blank areas and generation of alerts if input reaches limits. 2.12 Variable track quality system for promotion from tentative to system track. 2.13 Associate relevant plots to remote tracks told by NADGE. 2.14 Estimate height ┆
0x49600…49700 (73, 0, 6) Sector 4907ff00000341 ┆I Aof targets. 2.15 Secondary surveillance radar data must be used but not required. 2.16 Manual track initiation (indication of 2 consecutive plot positions). 2.17 Performance of rate and manual tracking (auto update w/manual correction┆
0x49700…49800 (73, 0, 7) Sector 48089800000341 ┆H A). 2.18 Local track ID will be non UTN (AA...). NADGE ID's will be used for NADGE told tracks. 2.19 19 bits/track must be used for storage. 5. Communication with NADGE Site 6. Recording and Reduction 7. Simulation 8. System Control and Co┆
0x49800…49900 (73, 0, 8) Sector 4909ff00000341 ┆I Anditioning 9. Communication with Remote Controller 10. Software Development Support 11. General System Performance Requirements W The following is a summary listing of requiremen┆
0x49900…49a00 (73, 0, 9) Sector 490aff00000341 ┆I Ats in each category. 1. Communication with Radar Heads W 1.1 HDLC - like duplex communication. 1.2 Live data receipt and input to plot correlation and display. 1.3 Receipt┆
0x49a00…49b00 (73, 0, 10) Sector 490bff00000341 ┆I A of strobe data. 1.4 Receipt of 200 (normal) to 400 (heavy) plots/scan. 1.5 Masking or filtering of 400 plot input to the degree necessary to track. 1.6 2400 baud communication to/from 5 (8) radar heads. 1.7 Receipt of radar status data. 1.┆
0x49b00…49c00 (73, 0, 11) Sector 490c7500000341 ┆I u A8 Receipt of clutter data (one minute dedicated transmission). 1.9 Continual surveillance (24 hours/day). etter) (S]ger) (Udf]rer) Inds`t hvilket? Slette hvilket? Flytte hvilket? Kopiere hvilket? Bytte hvilket? Bytte med? S]ge hvilket? ┆
0x49c00…49d00 (73, 0, 12) Sector 490dff00000341 ┆I A W 1.10 Recognition of and routing to Remote Controller all "DESTINATION FLAG" messages. 1.11 Recognition and transmission of Remote Control Orders to proper radar heads. 1┆
0x49d00…49e00 (73, 0, 13) Sector 490eff00000341 ┆I A.12 Receive and process North Mark in real-time. 1.13 Receive and utilize air reports or surface reports or both. 2. Multiradar Tracking 2.1 Correlation of plot reports and display as tracks. 2.2 Track within the following performance param┆
0x49e00…49f00 (73, 0, 14) Sector 490fff00000341 ┆I Aeters: W - Heading stability 9 degrees - Speed stability 5% of ground speed - Single radar, non-maneuvering target position error : 1.25 data miles or less speed erro┆
0x49f00…4a000 (73, 0, 15) Sector 4900ff00000341 ┆I Ar : 60 DM/hour or less heading error : 6 o or less - Single radar, maneuvering target position error : 2 DM or less - 3 radar coverage, non-maneuvering target position error : 0.4 DM or less speed error : 25 DM/hour ┆
0x4a000…4a100 (74, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(74,0, 1), len=0xff, h3=41000341}, f00=»0003A «, f01=»Appendix A 216B-6 «, f02=» «, f03=» «, f04=» «, f05=09-09-90 00:05, f06=» «, f07=»08 «, f08=» 135 «, f09= - - : , f10=» «, f11=» «, f12=» «, f13= - - : , f14=09-02-83 20:15, f15=»0001A «, f16=» 20 «, f17=» «, f18=»08 «, f19=» 312 «, f20=» 135 «, f21=» «, f22=» «, f99=020020000220056610a10a01aaca1f000000000000000037036400df}
0x4a100…4a200 (74, 0, 1) Sector 4a021400000341 ┆J A J J J J J I I H H H G G F F C C > = ┆
0x4a200…4a300 (74, 0, 2) Sector 4a03a100000341 ┆J ! A 1 COMMENT DD 12/16/82 Thu 10:36:23 DD 12/17/82 Fri 13:48:13 DD 2/25/83 Fri 10:02:14 C*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x4a300…4a400 (74, 0, 3) Sector 4a048700000341 ┆J A 1 comment T82-164 16 December 1982 x2"<!Z="(=^#Vk"$<:]=2#<:^=~ J6.! <6 M8) R6.> I! <6 M8)I!h=6 ! =6 M")IM"):g=~ J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x4a400…4a500 (74, 0, 4) Sector 4a058600000341 ┆J A 1 top CRIS/2477/PRP/001 ISSUE 1 M)(I:g=~ J /Mj'! "(=~ R*/!/=6jM (*(=~ R;/!/=6nM (*(=~ RM/!/=6iM (*(=~ R`/!/=6WM (*(=~ Rt/!/=6lM (*(=~ R ┆
0x4a500…4a600 (74, 0, 5) Sector 4a065b00000341 ┆J [ A 1 bottom A- p :i=>Jf0C.1:.= Rp0C%0! <6 M1' R 0C 0! <6 M1' R 0C 0! <6 M1' Z 0CR0Mc&!.=6 ! <6 M1' R40C.1! <6 M1' RC0C.1! <6 M1' RR0C.1!$<5CQ0!$<6 !&<6 Mc&! "(=6 E '<M% ! "2<┆
0x4a600…4a700 (74, 0, 6) Sector 4a07ff00000341 ┆J A W SOFTWARE REQUIREMENTS Software requirements for the CRIS fall into 11 categories. These are as follows: W 1┆
0x4a700…4a800 (74, 0, 7) Sector 4908ff00000341 ┆I A. Communication with Radar Heads 2. Multiradar Tracking 3. Passive Tracking 4. Display of Plot, Track, Strobe, and Background Pic- ture Data 5. Communication with NADGE Site 6. Recording and Reduction 7. Simulation 8. System Control and Co┆
0x4a800…4a900 (74, 0, 8) Sector 4a09ff00003841 ┆J 8Andress messages with encrypted text. cr will ignore the first mentioned contradiction (i.e. plaindress may include format line 10, also with prosign "gr" etc. as indicated in your last telex), but adapt the idea of normal distribution for encrypted ┆
0x4a900…4aa00 (74, 0, 9) Sector 4a0aff00003841 ┆J 8Aplaindress. w e e x p e c t a s h a p e r e a c t i o n. normal distribution/reception will include queuing to message service in case a message has no camps relevant pla's (for that cohmcen) or a "t" instruction in format line 4, thus pro┆
0x4aa00…4ab00 (74, 0, 10) Sector 4a0bff00003841 ┆J 8Aviding the r e f i l e facility. section 3.10 of the icd/0003 will be updated as follows: fm start "3.10 accounting information ---------------------------- 3.10.1 acp127 ------------- gr(fs)1234(ls)eolf for codress messages. for cod┆
0x4ab00…4ac00 (74, 0, 11) Sector 4a0cff00003841 ┆J 8Aress messages this line etc." section 3.10.3: "this format line shall indicate special system action when it follows directly after the format line 5 and commences with the sequence "gr(fs)" as described in section 3.5.3. in other cases reception┆
0x4ac00…4ad00 (74, 0, 12) Sector 4a0dff00003841 ┆J 8A criteria not related to this line shall apply" section 3.10.4: "the accounting information in this line shall be inserted at a message service position to off-line encrypted messages and those unclassified messages with plain text addressed to h┆
0x4ad00…4ae00 (74, 0, 13) Sector 4a0eb300003841 ┆J 3 8Aeadquarters (plain language addressees) specified to the system by the supervisor" 097 cr will add the following text in section 3.12.4 p57, format line 12a, end of para: ring preparation will be inserted in fl4 and/or fl5 up to max. 10 operating ┆
0x4ae00…4af00 (74, 0, 14) Sector 4a0fff00003841 ┆J 8A 1 "messages with classification/special category warning combinations of type nato(sp)unclas/spec.cat.warning (except "notional" e y e s o n l y) or c l e a r /spec. cat. warni┆
0x4af00…4b000 (74, 0, 15) Sector 4908ff00003841 ┆I 8Ang shall not be accepted for acp127 conversion. 100 please refer to final decision on srs dn5l. 106 cr will insert the following text in section 3.12.4 p57, format line 12c: "this line shall be inserted as derived from exercise sic's specified b┆
0x4b000…4b100 (75, 0, 0) Sector 4b01ff00003841 ┆K 8Atomatically) as specified in section ibd of cps/icd/0001 or inserted by message service (if specified signal is not recognised by the system) similar text will be inserted in 3.4.4 p27. 091+093 format line 10 -------------- general: -------┆
0x4b100…4b200 (75, 0, 1) Sector 4b02ff00003841 ┆K 8A ifb annex 3b.2.10 requires contents to be a c c o u n- t i n g i n f o r m a t i o n preceeded by "gr". acp127, ns-3, chapter 2, section II, p. 2-9 to 2-14 requires format line 10 to be an accounting line in general, with "gr(fs)1234(ls┆
0x4b200…4b300 (75, 0, 2) Sector 4b03ff00003841 ┆K 8A)edf" o n l y in case of messages with encrypted text (plaindress or codress), whereas for non-encrypted messages it might be acex. acp127, ns-3, appendix bII, 1 contradicts this: formal line 10 only for codress. acp117-nsI-para 111a (pxv II┆
0x4b300…4b400 (75, 0, 3) Sector 4b04ff00003841 ┆K 8AI) acex, but also acef and aclant might be used for c o m m e r c i a l r e - f i l e, but n o t for p l a i n l a n g u a g e messages. ifb 3.8.2.10 (o u t g o i n g m e s s a g e s): format line 10 may be required with respect to┆
0x4b400…4b500 (75, 0, 4) Sector 4b05ff00003841 ┆K 8A unclassified messages to certain headquarters; supervisor to insert accounting information. ifb 3.9.2.10 (incoming messages): format line 10 is only of r e l e v a n c e when it follows directly after the format line 5 and commences with seq┆
0x4b500…4b600 (75, 0, 5) Sector 4b06ff00003841 ┆K 8Auence gr(sp), i.e. the case of ifb 3.9.2.5(i) ("grifs)1234(ls)eolf" and format lines 11, 13, and 16 also present, in which case it shall be sent to a supervisor specified position, otherwise rejection to message service). in no other case need it be┆
0x4b600…4b700 (75, 0, 6) Sector 4b071100003841 ┆K 8A detected. lash in 3.2.3.a, a c c e p t a b l e d e v i a t i o n s, second para. to avoid confusion item i) in section 3.2.2., p 14, should be changed to read "acp127: precedence warning (ls)jjjjjsssss(fs) (bell signal associated with flash m┆
0x4b700…4b800 (75, 0, 7) Sector 4a08ff00003841 ┆J 8A 1 the last quotation from the ifb either follows appendix b of acp127 ns-3 (i.e. format line 10 for codress only) or it tells camps to have no special distribution provisions for plai┆
0x4b800…4b900 (75, 0, 8) Sector 4b09ff00003841 ┆K 8A 1 052 cr will insert the following text in section 3.4.1(c) p23: line 7: the number of different operating signals of this form to be detected shall not...... line 17 max. 10 oper┆
0x4b900…4ba00 (75, 0, 9) Sector 4b0aff00003841 ┆K 8Aating signals will require any action to be taken by the system. 054 last 8 lines of subpara c) p 23 of 341 changed to read: "the instruction signifies that the camps related to routing indicator 1 shall pass the message to the station indicat┆
0x4ba00…4bb00 (75, 0, 10) Sector 4b0bff00003841 ┆K 8Aed by routing indicator 2. routing indicator 1 may not always be repeated after the sequence (sp)t(sp), if present this indicates internal distribution and retransmission according to routing indicator 2. in case of instruction "t" alone (no routing┆
0x4bb00…4bc00 (75, 0, 11) Sector 4b0cff00003841 ┆K 8A indicators) the message shall be queued for message servicing (before retransmission). 056 n o n e of the recommendations to section 3.4.2 are accepted: you recommend to have n o alternatives, which is exactly as is (n o n e on page 24). the ┆
0x4bc00…4bd00 (75, 0, 12) Sector 4b0dff00003841 ┆K 8Areferenced contents/variations mentioned in your dn are already in section 3.4.3. 070 3.5.1(d) is according to ifb, 3b.2.5(d). annex (operating signals in fl4 of incoming messages will result in queuing to mdco. operating signals of format l┆
0x4bd00…4be00 (75, 0, 13) Sector 4b0eff00003841 ┆K 8Aine 5 (book messages?) have no relevance to camps; fl5 will, however, be present in the distributed copy. on o u t g o i n g messages the operating signals specified during preparation will be inserted in fl4 and/or fl5 up to max. 10 operating ┆
0x4be00…4bf00 (75, 0, 14) Sector 4b0faf00003841 ┆K / 8Asignals, which are known to the system. when different operating signals are specified the message will be queued for message servicing). 78 insert in 3.5.4 item (d): t being received (additional (ls) characters being exempted) 017 cr proposes d┆
0x4bf00…4c000 (75, 0, 15) Sector 4b00ff00003841 ┆K 8A 1 "o p e r a t i n g s i g n a l s shall be inserted automatically by the system according to the entry during preparation (max. 10 operating signals for fl4 and/or fl5 inserted au┆
0x4c000…4c100 (76, 0, 0) Sector 4c011a00003841 ┆L 8Aian calender day)). > IM1' R(3> I!L<"2<M*(My,> I!3<6n \Mo M *y= "(= q#p! =6 M] : =V V I: =~ B 3: = R 3*$<MMY *%<MMY !\<6 C 3M, !\<6 : =~ B 5: = R$3C/4!e=6 !f=6 !g=6 !h=6 Ml+M;) RE3C#4: 2i=:g=~ JV3C/4!"<6 #6 MB&! =6 !,<6 :]=2'< AMD MB&!,<6 ! ┆
0x4c100…4c200 (76, 0, 1) Sector 4c02ff00003841 ┆L 8A 1 022 dn closed by shape as withdrawn. possible changes/additions introduced by shape later on will be handled as change notices. 025 as already explained in cps/101/tlx/0032 the sup┆
0x4c200…4c300 (76, 0, 2) Sector 4c03ff00003841 ┆L 8Aervisor will n o t leave to insert the security warning prosigns (i.e. cr agrees with shape). a suitable text has been inserted in icd/0003. concerning check of security mismatch in fl4 versus fl12a cr will introduce this n e w requirement (c┆
0x4c300…4c400 (76, 0, 3) Sector 4c04ff00003841 ┆L 8Aontractual implications not covered here) in the icd/0003, section 3.12.3, fl12a: "this format line containing the classification word(s) together with special category warnings (if used) shall be checked with the corresponding security data i┆
0x4c400…4c500 (76, 0, 4) Sector 4c05ff00003841 ┆L 8An format line 4. if a mismatch is detected the message shall be queued for message servicing, and a plaindress service message shall be generated and transmitted automatically by the system to the originating station (format line 3). format of ┆
0x4c500…4c600 (76, 0, 5) Sector 4c06ff00003841 ┆L 8Athe service message is as specified below for format line 12g: action shape tbd (shape to specify)" ------------ ref. to 3.12.3 will be inserted in 3.4.3.a. 030 cr will update document according to shape original dn, i.e. insert i m m e d i a┆
0x4c600…4c700 (76, 0, 6) Sector 4c07ff00003841 ┆L 8A t e for flash in 3.2.3.a, a c c e p t a b l e d e v i a t i o n s, second para. to avoid confusion item i) in section 3.2.2., p 14, should be changed to read "acp127: precedence warning (ls)jjjjjsssss(fs) (bell signal associated with flash m┆
0x4c700…4c800 (76, 0, 7) Sector 4b089b00003841 ┆K 8Aessages only (refer to 3.2.3.a, however)" (if the alternative in section 3.2.2.i) is exercised this will not impact the requirement in 3.2.3.a!) ┆
0x4c800…4c900 (76, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(76,0, 9), len=0xff, h3=41003841}, f00=»0038A «, f01=»telex to shape (acp-127) «, f02=»rt «, f03=»fah «, f04=»kan slettes senere «, f05=26-09-80 09:35, f06=» 3 «, f07=»05 «, f08=» 9294 «, f09= - - : , f10=» «, f11=» «, f12=» «, f13=26-09-80 12:46, f14=26-09-80 12:57, f15=»0001A «, f16=» 6 «, f17=» 3 «, f18=»05 «, f19=» 152 «, f20=» 9294 «, f21=» «, f22=» «, f99=020010000120056610a10a01aaca1f000000000000000030032b00df}
0x4c900…4ca00 (76, 0, 9) Sector 4c0a0600003841 ┆L 8A L L K K K J DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / ┆
0x4ca00…4cb00 (76, 0, 10) Sector 4c0bff00003841 ┆L 8A 1 1980-09-26 gj/rt to: shnmo division att: mr. paul f. shey, contracting officer c.c: lt.col. manfred stoltz, camps program manager fm: christian rovsing a/s, denmark gert je┆
0x4cb00…4cc00 (76, 0, 11) Sector 4c0cff00003841 ┆L 8Ansen our ref: cps/tlx/0064 subj: acp-127 nato supp-3 procedures --------------------------------------- 001 cr considers the dn closed by the following text change to para 2.2 page 2: "these messages shall contain as a minimum format lines 1, 2,┆
0x4cc00…4cd00 (76, 0, 12) Sector 4c0dff00003841 ┆L 8A 3, 4, 5, 11, 12a (except for codress), 12b (except for codress), 12g, 13, and 16" format lines 12c and 12d are not mandatory; they will be checked as referenced elsewhere in document. 004 cr considers this dn closed by the following change of ┆
0x4cd00…4ce00 (76, 0, 13) Sector 4c0eff00003841 ┆L 8Atext to para 2.2 (4) (a) page 3: "they shall as a minimum contain format lines 1, 2, 3, 4, 12g, and 16" according to ifb 3b.2.12, line 12g contains the mandatory text (older versions of ns-3 only refers to line 12c for all types of messages; cr p┆
0x4ce00…4cf00 (76, 0, 14) Sector 4c0fff00003841 ┆L 8Arefers some terminology for all types). 014 cr proposes dn closed by the following text inserted in para 3.1.3 (b), p.9 first entry: "- three consecutive letters not being received (additional (ls) characters being exempted) 017 cr proposes d┆
0x4cf00…4d000 (76, 0, 15) Sector 4c00ff00003841 ┆L 8An closed by the following text inserted in para 3.1.3.(c) page 9, r e j e c t a b l e c o n d i t i o n s: "non successful validation check on transmissions serial number (n + 1 per channel and, where applicable, as dependent on r a d a y (=jul┆
