OctetView
0x00000…00100 (0, 0, 0) Sector 01264130313236 ┆ &A0126A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00fefff0ffff ┆ ~ p |x ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x16, d01=0x89, d02=0x41, ptr=( 5,0, 8), d05=0x00}
0x00306…0030c WangDocument {d00=0x17, d01=0x02, d02=0x41, ptr=(29,0, 8), d05=0x00}
0x0030c…00312 WangDocument {d00=0x17, d01=0x96, d02=0x41, ptr=(32,0, 8), d05=0x00}
0x00312…00318 WangDocument {d00=0x18, d01=0x89, d02=0x41, ptr=(14,0, 8), d05=0x00}
0x00318…00320 17 43 41 4b 08 00 17 43 ┆ CAK C┆
0x00320…00340 41 4b 08 00 17 43 41 4b 08 00 17 43 41 4b 08 00 17 43 41 4b 08 00 17 43 41 4b 08 00 17 43 41 4b ┆AK CAK CAK CAK CAK CAK┆
0x00340…00360 08 00 17 43 41 4b 08 00 17 43 41 4b 08 00 17 43 41 4b 08 00 17 43 41 4b 08 00 17 43 41 4b 08 00 ┆ CAK CAK CAK CAK CAK ┆
0x00360…00380 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 ┆ ┆
[…0x3…]
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 18 ┆ ┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 86312020202020 ┆ 1 B 7 Q? > 7 | T d N ~< v <+&4'>( 1c5 & & ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' X% % PO P ; A? C g x g V W O 7 :AH AK < 1689A g s < {C < { ; 9 b b bD W K : 9 8 t x f AK>E >K ;N ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x6…]
0x01700…01800 (1, 0, 7) Sector 00000000000000 ┆ ┆
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0xb…]
0x02400…02500 (2, 0, 4) Sector 00000000000000 ┆ ┆
[…0x3…]
0x02800…02900 (2, 0, 8) WangDocumentBody
[…0x2f…]
0x05800…05900 (5, 0, 8) WangDocumentHead {hdr=WangSectHead {next=( 5,0, 9), len=0xff, h3=41168941}, f00=»1689A «, f01=»CROSS FOX Tilbud (final) «, f02=»kk «, f03=»ALF «, f04=»Program Impl. Plan O «, f05=12-02-82 13:53, f06=» 1 «, f07=»54 «, f08=» 10296 «, f09=16-02-82 15:35, f10=» «, f11=»06 «, f12=» 159 «, f13=15-02-82 15:46, f14=25-02-83 11:19, f15=»0126A «, f16=» 17 «, f17=» 2 «, f18=»39 «, f19=» 164 «, f20=» 12517 «, f21=» «, f22=» «, f99=020010000110066610110180aaca15050000000000000137033c00df}
0x05900…05a00 (5, 0, 9) WangDocumentBody
[…0xc…]
0x06600…06700 (6, 0, 6) Sector 06075300169641 ┆ S Aontractor will install 4 message compilation units (MCU) in the crypto room. Fig. 6.1-2 Packing of a Crate ointly perform a site verification. very of equipment installation drawings 3 months prior to on-site in┆
0x06700…06800 (6, 0, 7) Sector 01089a00169641 ┆ A 1 Fig. 6.1-3 Site 101, equipment room layout procedures based on the site preparation requirements and the site installation drawings. These pro┆
0x06800…06900 (6, 0, 8) WangDocumentBody
[…0x4…]
0x06d00…06e00 (6, 0, 13) Sector 060eff00179641 ┆ A Functional Verification ....... 353 7.2.4 MPF Subsystem Verification ............. 353 7.2.5 Reliability and Maintainability Verification ........................... 354 7.2.5.1 Hardware Reliabilty Verification ..... 354 ┆
0x06e00…06f00 (6, 0, 14) Sector 060ff500179641 ┆ u A 7.2.5.2 Software Reliability Verification .. 355 7.2.5.3 Hardware Maintainability Verification ....................... 355 7.2.5.4 Software Maintainability Verification ...................... 355 9 Site Ins┆
0x06f00…07000 (6, 0, 15) Sector 0600ff00179641 ┆ A 1 7.3 FACTORY POST PRODUCTION TEST ................ 356 7.4 ON SITE TESTS ...........┆
0x07000…07100 (7, 0, 0) WangDocumentBody
[…0x77…]
0x0e800…0e900 (14, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(14,0, 9), len=0xff, h3=41188941}, f00=»1889A «, f01=»Tilbud til Norge «, f02=»kk «, f03=»PEH «, f04=»Gemmes «, f05=23-03-82 13:31, f06=» «, f07=»39 «, f08=» 9818 «, f09=23-03-82 16:09, f10=» «, f11=»07 «, f12=» 102 «, f13=23-03-82 16:22, f14=25-03-82 15:28, f15=»0126A «, f16=» 8 «, f17=» «, f18=»46 «, f19=» 160 «, f20=» 9920 «, f21=» «, f22=» «, f99=020010000110066610110180aaca15050000000000000037032f00df}
0x0e900…0ea00 (14, 0, 9) WangDocumentBody
[…0xee…]
0x1d800…1d900 (29, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(29,0, 9), len=0xff, h3=41170241}, f00=»1702A «, f01=»Managem. Proposal Final «, f02=»kk «, f03=»ALF «, f04=»Volume II «, f05=16-02-82 11:33, f06=» 1 «, f07=»02 «, f08=» 592 «, f09=20-08-82 08:31, f10=» «, f11=»27 «, f12=» 60 «, f13=30-06-82 13:45, f14=02-09-82 08:16, f15=»0126A «, f16=» 57 «, f17=» 1 «, f18=»36 «, f19=» 748 «, f20=» 771 «, f21=» «, f22=» «, f99=460052000110062710110390aa8a3704000000000000013703f600df}
0x1d900…1da00 (29, 0, 9) WangDocumentBody
[…0x6…]
0x1e000…1e100 (30, 0, 0) Sector 1e01ff00170241 ┆ Af significant computer projects. MPF implementation will be based on the CR80 computer which is produced by the Electronics Division of Christian Rovsing. Production facilities in the Electronics Division belong to the most modern to be found, an┆
0x1e100…1e200 (30, 0, 1) Sector 1e023300170241 ┆ 3 Ad they have recently been expanded to allow 23 2.2 INVOLVEMENT IN DATA COMMUNICATION ......... 23 2.3 DESCRIPTION OF MAJOR CONTRACTS ............ 28 2.3.1 NICS-TARE ............................. 29 2.3.2 FIKS ..................┆
0x1e200…1e300 (30, 0, 2) Sector 1e03ff00170241 ┆ A 1 production of the latest CR80M version of the CR80. Improvements in technology and the demands for more powerful and reliable computer architectures with high growth potential hav┆
0x1e300…1e400 (30, 0, 3) Sector 1e04ff00170241 ┆ Ae led to the introduction of the CR80M. More than 200 CR80M systems are currently on order from major customers such as NATO, ICL and L.M. Ericsson. The MPF project will be supported by the Integrated Logistics Support Group which provides servic┆
0x1e400…1e500 (30, 0, 4) Sector 1e05ff00170241 ┆ Aes including site surveys, installation, training, documentation preparation, maintenance, spares and other support services. This group is part of the Systems Division. In the following sections, the company will be presented in detail - its his┆
0x1e500…1e600 (30, 0, 5) Sector 1e06ff00170241 ┆ Atory, organisation, and financial status. Then our involvement in Data Communication will be discussed and relevant projects undertaken, related to the scope of the MPF, will be outlined. Finally, procedures for management and logistics support an┆
0x1e600…1e700 (30, 0, 6) Sector 1e072300170241 ┆ # Ad services are descriped. ntenance ....................... 86 3.3.2 Field Support ..................... 86 3.3.3 Spares Management ................. 87 3.3.4 Codification of Supply Items ...... 87 3.3.5 Tools and Test Equi┆
0x1e700…1e800 (30, 0, 7) Sector 1d08ff00170241 ┆ A 1 1.2 CORPORATE HISTORY AND ORGANIZATION 1.2.1 Introduction to Christian Rovsing A/S Christian Rovsing is Denmark's fastest growing high-technology computer and aerospace-electro┆
0x1e800…1e900 (30, 0, 8) Sector 1e092400170241 ┆ $ A Handbooks ............. 89 ┆
0x1e900…1ea00 (30, 0, 9) Sector 1e0aff00170241 ┆ A 1 1. Christian Rovsing A/S 1.1 Introduction The decision to bid the Cross Fox/Message Processing Facility (MPF) represents a definite commitment on the part of Christian Rovs┆
0x1ea00…1eb00 (30, 0, 10) Sector 1e0bff00170241 ┆ Aing to devote its resources and technical talents to specialized computer system applications. For the past six years, a large percentage of Christian Rovsing resources has been devoted towards advanced data communications systems. The company has┆
0x1eb00…1ec00 (30, 0, 11) Sector 1e0cff00170241 ┆ A participated in several major programs, either as prime contractor or principal sub-contractor. System contracts awarded to the company are typically worth several millions of dollars. Considerable experience in the field of data communications c┆
0x1ec00…1ed00 (30, 0, 12) Sector 1e0dff00170241 ┆ Aombined with our experience in the management of large computer system projects provides a solid basis for successful design and implementation of the Cross Fox/ MPF. Responsibility for major computer systems, particularly for military customers su┆
0x1ed00…1ee00 (30, 0, 13) Sector 1e0eff00170241 ┆ Ach as NATO-SHAPE, has demanded a professional approach to turn-key project management with particular emphasis on planning and documentation in all phases from system design and development through production, integration, installation, maintenance ┆
0x1ee00…1ef00 (30, 0, 14) Sector 1e0fff00170241 ┆ Aand training. Each major project at Christian Rovsing is under the cognizance of a Project Office with total system responsibility and control authority to co-ordinate in-house activities and to provide close liaison with the customer throughout t┆
0x1ef00…1f000 (30, 0, 15) Sector 1e00ff00170241 ┆ Ahe duration of the project. Thus an administratively distinct Project office will be established in the Systems Division of Christian Rovsing to manage the MPF project. The Systems Division has been specially structured to consolidate management o┆
0x1f000…1f100 (31, 0, 0) Sector 1f01ff00170241 ┆ A............ 21 1.3.2 Statement of Income ................... 21 1.3.3 Balance Sheet ......................... 22 1.3.4 Key Figures over Four Years ........... 22 2. RELEVANT EXPERIENCE .......................... 23 2.1 ┆
0x1f100…1f200 (31, 0, 1) Sector 1f02ff00170241 ┆ AINTRODUCTION .............................. 23 2.2 INVOLVEMENT IN DATA COMMUNICATION ......... 23 2.3 DESCRIPTION OF MAJOR CONTRACTS ............ 28 2.3.1 NICS-TARE ............................. 29 2.3.2 FIKS ..................┆
0x1f200…1f300 (31, 0, 2) Sector 1f03ff00170241 ┆ A................ 34 2.3 3 CAMPS ................................. 39 2.3.4 LME-NET ............................... 45 2.3.5 HAWK Converter ........................ 49 2.3.5.1 Introduction ...................... 49 2.3.┆
0x1f300…1f400 (31, 0, 3) Sector 1f04a200170241 ┆ " A5.2 Interface Description ............. 50 2.3.5.3 Environmental Description ......... 50 2.3.6 ADA Compiler .......................... 53 te hvilket? Flytte hvilket? Kopiere hvilket? Bytte hvilket? Bytte med? S]ge hvilket? ┆
0x1f400…1f500 (31, 0, 4) Sector 1f05ff00170241 ┆ A 1 3 LOGISTICS SUPPORT AND CAPABILITIES ........ 83 3.1 Organization .........................┆
0x1f500…1f600 (31, 0, 5) Sector 1f06ff00170241 ┆ A. 83 3.2 Installation Service .................. 85 3.2.1 Site Preparation and Verification . 85 3.2.2 Transportation and Installation ... 85 3.2.3 Packaging Requirements ............ 86 3.3 Maintenance and Support .....┆
0x1f600…1f700 (31, 0, 6) Sector 1f07ff00170241 ┆ A.......... 86 3.3.1 Maintenance ....................... 86 3.3.2 Field Support ..................... 86 3.3.3 Spares Management ................. 87 3.3.4 Codification of Supply Items ...... 87 3.3.5 Tools and Test Equi┆
0x1f700…1f800 (31, 0, 7) Sector 1e08ff00170241 ┆ Apment .......... 87 3.3.6 Failure Reporting ................. 87 3.4 Training and Documentation ............ 88 3.4.1 Organization ...................... 88 3.4.2 Training Courses .................. 88 3.4.3 Manuals and┆
0x1f800…1f900 (31, 0, 8) Sector 1f09ff41170241 ┆ A A1702A Managem. Proposal Final kk ALF Volume II 16 02 82 11 33 1 02 592 21 04 82 09 18 07 119 30 06 82 13 45 13 07 82 14 43 0126A 63 1 09 856 711 F R ' * 7 7 _┆
0x1f900…1fa00 (31, 0, 9) Sector 1f0a3f00170241 ┆ ? A VITET DATO TID ANV.TID ANSLAG Oprettet / / : : S SDATO TID ANV.TID ANSLAG Oprettet / / : : S S┆
0x1fa00…1fb00 (31, 0, 10) Sector 1f0bcc00170241 ┆ L A 1 VOLUME II 1982-02-16 CORPORATE CAPABILITIES Page 1 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x1fb00…1fc00 (31, 0, 11) Sector 1f0cd400170241 ┆ T A 1 VOLUME II CORPORATE CAPABILITIES C R O S S F O X MESSAGE PROCESSING FACILITY CHRISTIAN ROVSING A/S BALLERUP, DENMARK J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x1fc00…1fd00 (31, 0, 12) Sector 1f0dff00170241 ┆ A 1 TABLE OF CONTENTS 1 1. CHR┆
0x1fd00…1fe00 (31, 0, 13) Sector 1f0eff00170241 ┆ AISTIAN ROVSING A/S ........................ 1 1.1 INTRODUCTION .............................. 1 1.2 CORPORATE HISTORY AND ORGANIZATION ........ 3 1.2.1 Introduction to Christian Rovsing A/S . 3 1.2.2 Corporate History ....┆
0x1fe00…1ff00 (31, 0, 14) Sector 1f0fff00170241 ┆ A................. 8 1.2.3 Company Organization .................. 9 1.2.3.1 The Electronics Division .......... 12 1.2.3.2 The Systems Division .............. 13 1.2.3.3 The Data Processing Division ...... 17 1.2.4┆
0x1ff00…20000 (31, 0, 15) Sector 1f00ff00170241 ┆ A Personnel and Facilities .............. 19 1.2.4.1 Employee Profile .................. 19 1.2.4.2 Facilities ........................ 19 1.3 FINANCIAL STATUS .......................... 21 1.3.1 1980 Annual Report Excerpt ┆
0x20000…20100 (32, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(32,0, 1), len=0xff, h3=41170241}, f00=»1702A «, f01=»Managem. Proposal Final «, f02=»kk «, f03=»ALF «, f04=»Volume II «, f05=16-02-82 11:33, f06=» 1 «, f07=»02 «, f08=» 592 «, f09= - - : , f10=» «, f11=» «, f12=» «, f13=16-02-82 12:43, f14=25-03-82 16:02, f15=»0126A «, f16=» 63 «, f17=» 1 «, f18=»02 «, f19=» 908 «, f20=» 592 «, f21=» «, f22=»; «, f99=020010000110066610110180aaca15050000000000000137031601df}
0x20100…20200 (32, 0, 1) Sector 20023f00170241 ┆ ? A VITET DATO TID ANV.TID ANSLAG Oprettet / / : : S SDATO TID ANV.TID ANSLAG Oprettet / / : : S S┆
0x20200…20300 (32, 0, 2) Sector 2003cc00170241 ┆ L A 1 VOLUME II 1982-02-16 CORPORATE CAPABILITIES Page 1 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x20300…20400 (32, 0, 3) Sector 2004d400170241 ┆ T A 1 VOLUME II CORPORATE CAPABILITIES C R O S S F O X MESSAGE PROCESSING FACILITY CHRISTIAN ROVSING A/S BALLERUP, DENMARK J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x20400…20500 (32, 0, 4) Sector 2005ff00170241 ┆ A 1 TABLE OF CONTENTS 1 1. CHR┆
0x20500…20600 (32, 0, 5) Sector 2006ff00170241 ┆ AISTIAN ROVSING A/S ........................ 1 1.1 INTRODUCTION .............................. 1 1.2 CORPORATE HISTORY AND ORGANIZATION ........ 3 1.2.1 Introduction to Christian Rovsing A/S . 3 1.2.2 Corporate History ....┆
0x20600…20700 (32, 0, 6) Sector 2007ff00170241 ┆ A................. 8 1.2.3 Company Organization .................. 9 1.2.3.1 The Electronics Division .......... 12 1.2.3.2 The Systems Division .............. 13 1.2.3.3 The Data Processing Division ...... 17 1.2.4┆
0x20700…20800 (32, 0, 7) Sector 1f08ff00170241 ┆ A Personnel and Facilities .............. 19 1.2.4.1 Employee Profile .................. 19 1.2.4.2 Facilities ........................ 19 1.3 FINANCIAL STATUS .......................... 21 1.3.1 1980 Annual Report Excerpt ┆
0x20800…20900 (32, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(32,0, 9), len=0xff, h3=41179641}, f00=»1796A «, f01=»Crossfox Tilbud «, f02=»kk «, f03=»ALF «, f04=»Indholdsfortegnelse «, f05=04-03-82 14:51, f06=» 1 «, f07=»02 «, f08=» 1807 «, f09=04-05-82 13:01, f10=» 1 «, f11=»37 «, f12=» 2142 «, f13=24-03-82 13:00, f14=10-05-82 13:29, f15=»0126A «, f16=» 14 «, f17=» 5 «, f18=»01 «, f19=» 408 «, f20=» 11071 «, f21=» «, f22=» «, f99=020010000110066610110180aaca15050000000000000128036d00df}
0x20900…20a00 (32, 0, 9) WangDocumentBody
[…0x6…]
0x21000…21100 (33, 0, 0) Sector 2101ff00170241 ┆! A............ 21 1.3.2 Statement of Income ................... 21 1.3.3 Balance Sheet ......................... 22 1.3.4 Key Figures over Four Years ........... 22 2. RELEVANT EXPERIENCE .......................... 23 2.1 ┆
0x21100…21200 (33, 0, 1) Sector 2102ff00170241 ┆! AINTRODUCTION .............................. 23 2.2 INVOLVEMENT IN DATA COMMUNICATION ......... 23 2.3 DESCRIPTION OF MAJOR CONTRACTS ............ 28 2.3.1 NICS-TARE ............................. 29 2.3.2 FIKS ..................┆
0x21200…21300 (33, 0, 2) Sector 2103ff00170241 ┆! A................ 34 2.3 3 CAMPS ................................. 39 2.3.4 LME-NET ............................... 45 2.3.5 HAWK Converter ........................ 49 2.3.5.1 Introduction ...................... 49 2.3.┆
0x21300…21400 (33, 0, 3) Sector 2104a200170241 ┆! " A5.2 Interface Description ............. 50 2.3.5.3 Environmental Description ......... 50 2.3.6 ADA Compiler .......................... 53 Disk table access for FROM PLA; isolate local RIs, validation 51 1 Write item to disk ┆
0x21400…21500 (33, 0, 4) Sector 2105ff00170241 ┆! A 1 3 LOGISTICS SUPPORT AND CAPABILITIES ........ 83 3.1 Organization .........................┆
0x21500…21600 (33, 0, 5) Sector 2106ff00170241 ┆! A. 83 3.2 Installation Service .................. 85 3.2.1 Site Preparation and Verification . 85 3.2.2 Transportation and Installation ... 85 3.2.3 Packaging Requirements ............ 86 3.3 Maintenance and Support .....┆
0x21600…21700 (33, 0, 6) Sector 2107ff00170241 ┆! A.......... 86 3.3.1 Maintenance ....................... 86 3.3.2 Field Support ..................... 86 3.3.3 Spares Management ................. 87 3.3.4 Codification of Supply Items ...... 87 3.3.5 Tools and Test Equi┆
0x21700…21800 (33, 0, 7) Sector 2008ff00170241 ┆ Apment .......... 87 3.3.6 Failure Reporting ................. 87 3.4 Training and Documentation ............ 88 3.4.1 Organization ...................... 88 3.4.2 Training Courses .................. 88 3.4.3 Manuals and┆
0x21800…21900 (33, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(33,0, 9), len=0xff, h3=41170241}, f00=»1702A «, f01=»Managem. Proposal Final «, f02=»kk «, f03=»ALF «, f04=»Volume II «, f05=16-02-82 11:33, f06=» 1 «, f07=»02 «, f08=» 592 «, f09= - - : , f10=» «, f11=» «, f12=» «, f13=16-02-82 12:43, f14=16-02-82 13:50, f15=»0126A «, f16=» 63 «, f17=» 1 «, f18=»02 «, f19=» 908 «, f20=» 592 «, f21=» «, f22=»; «, f99=020010000110066610110180aaca15050000000000000137031601df}
0x21900…21a00 (33, 0, 9) Sector 210a3f00170241 ┆! ? A ! ! ! ! VITET DATO TID ANV.TID ANSLAG Oprettet / / : : S SDATO TID ANV.TID ANSLAG Oprettet / / : : S S┆
0x21a00…21b00 (33, 0, 10) Sector 210bcc00170241 ┆! L A 1 VOLUME II 1982-02-16 CORPORATE CAPABILITIES Page 1 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x21b00…21c00 (33, 0, 11) Sector 210cd400170241 ┆! T A 1 VOLUME II CORPORATE CAPABILITIES C R O S S F O X MESSAGE PROCESSING FACILITY CHRISTIAN ROVSING A/S BALLERUP, DENMARK J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x21c00…21d00 (33, 0, 12) Sector 210dff00170241 ┆! A 1 TABLE OF CONTENTS 1 1. CHR┆
0x21d00…21e00 (33, 0, 13) Sector 210eff00170241 ┆! AISTIAN ROVSING A/S ........................ 1 1.1 INTRODUCTION .............................. 1 1.2 CORPORATE HISTORY AND ORGANIZATION ........ 3 1.2.1 Introduction to Christian Rovsing A/S . 3 1.2.2 Corporate History ....┆
0x21e00…21f00 (33, 0, 14) Sector 210fff00170241 ┆! A................. 8 1.2.3 Company Organization .................. 9 1.2.3.1 The Electronics Division .......... 12 1.2.3.2 The Systems Division .............. 13 1.2.3.3 The Data Processing Division ...... 17 1.2.4┆
0x21f00…22000 (33, 0, 15) Sector 2100ff00170241 ┆! A Personnel and Facilities .............. 19 1.2.4.1 Employee Profile .................. 19 1.2.4.2 Facilities ........................ 19 1.3 FINANCIAL STATUS .......................... 21 1.3.1 1980 Annual Report Excerpt ┆
0x22000…22100 (34, 0, 0) Sector 2201ff00170041 ┆" Aghput is thus secured in the absolute worst case traffic load situation. Finally, we will consider the peak character rate specified in the IFB to last for up to 5 min. in any one hour: 600 char./sec. incom,ing traffic 800 char./sec. outgoing ┆
0x22100…22200 (34, 0, 1) Sector 2202ff00170041 ┆" Atraffic Comparing these character rates to the expanded configuration rates used for the throughput calculations above, the following factors of increase are found incoming traffic: 600/315 = 1.91 outgoing traffic: 800/631 = 1.29 These cha┆
0x22200…22300 (34, 0, 2) Sector 2203b500170041 ┆" 5 Aracter rates are only obtained with the introduction of considerably more external channels and local terminals than the number corresponding to the expanded configuration . transmissions). Worst case retrieval (DTG and TO PLA) is assumed. - 10%┆
0x22300…22400 (34, 0, 3) Sector 2204ff00170041 ┆" A 1 The loads corresponding to the high character rates are Each CPU 42% Disk 75% It has here been assumed that ┆
0x22400…22500 (34, 0, 4) Sector 2205eb00170041 ┆" k Aall S/W modules, except the reception which works at the higher input rate, work at the outgoing traffic rate. Concerning the connectivity of internal terminals and external channels a discussion is presented in section 1.2.1. of system calls (I/O┆
0x22500…22600 (34, 0, 5) Sector 2206ff00170041 ┆" A 1 MSG, RECEPTION ITEM PU(ms) NUMBER OF DISK R W Read from Channel 60 Create item 16 Prelim. Analysis 30 Write to disk 140 4 Trans.Acknowledgement 25 Checkpoint to disk┆
0x22600…22700 (34, 0, 6) Sector 2207ff00170041 ┆" A 35 1 306 5 Unload to off line disk 67 2 3 373 2 8 MSG. TRANSMISSION (1.2 transmissions per msg.) NUMBER OF DISK ITEM PU(ms) R W Read item 144 4.8 Table access for serial no. plus direct CPU ┆
0x22700…22800 (34, 0, 7) Sector 1000ff00170041 ┆ A time 36 Transmission to channel 72 Receive acknowledgement 25 Checkpoint to disk 42 1.2 319 4.8 1.2 TRANSMISSION TO STANDBY SYSTEM (VIA MC) Approximately as for MSG TRANSMISSION divided by the transmission mul┆
0x22800…22900 (34, 0, 8) Sector 2209ff00170041 ┆" Arack; the seek time is caluclated in fig. 4.7.2-1. As a worst case data have been assumed located randomly on the whole disk; on this point improvements may be gained: Data which are often required, such as tables, may be constrained to smaller ar┆
0x22900…22a00 (34, 0, 9) Sector 220aff00170041 ┆" Aeas. t SEEK = 34.7 ms. TRANSFER = time for transfer of data to/from disk from/to the controller; time is negligible Consequently t acess = 49 ms. 1 The access time thu┆
0x22a00…22b00 (34, 0, 10) Sector 220bff00170041 ┆" As calculated is the time for executing a READ to any of the two mirrored disks. since in average any of the two disks may used half this time shall be used for load calculations. Disk WRITE accesses are executed to both disks and are in both case┆
0x22b00…22c00 (34, 0, 11) Sector 220cff00170041 ┆" As followed by a READ for check. The READ after WRITE will experience the average rotational delay plus some validation time in the PU: A total of 10 ms is added per WRITE access to each disk: hence the resulting access time for disk writes to be ┆
0x22c00…22d00 (34, 0, 12) Sector 220d3900170041 ┆" 9 Aused for load calculations is t WRITE = 59 ms. f outgoing messages for the expanded configuration is 674 msg/hour. It is seen that the busy hour rate of 500 messages specified in the IFB is included in these figures. A peak (character) throug┆
0x22d00…22e00 (34, 0, 13) Sector 220eff00170041 ┆" A 1 In order to include the effect to the system load of the support functions - log, statistics, storage catalog creation, status preparation, report generation, security functions - ┆
0x22e00…22f00 (34, 0, 14) Sector 220fff00170041 ┆" Aexperience factors shall be used which have been taken from a similar project (CAMPS). The factors are PU 1.26 DISK READS 1.11 DISK WRITES ┆
0x22f00…23000 (34, 0, 15) Sector 2200ff00170041 ┆" A 1.43 The final result thus obtained is then according to table 4.7.2-9. PU 63% CPU load (2 CPUs) 31.5% DISK load 53% The throu┆
0x23000…23100 (35, 0, 0) Sector 2301ff00170041 ┆# Aroughput calculation. The corresponding traffic flow is explained in section 4.7.1. With the addition of one function-retrieval for rerun of outgoing messages - the functions of the flow have been analysed and the resource consumption in terms of┆
0x23100…23200 (35, 0, 1) Sector 2302ff00170041 ┆# A PU processing time and number of disk reads and writes has been calculated. The result is presented in the tables 4.7.2-1 to 9, the last table containing the summation. The following assumptions have been made in addition to section 4.7.1: - ┆
0x23200…23300 (35, 0, 2) Sector 2303ff00170041 ┆# Athere is one edit session per prepared message - retrieval is based on request for rerun and corresponds to 5% of the transmitted messages (including the effect of multiple transmissions). Worst case retrieval (DTG and TO PLA) is assumed. - 10%┆
0x23300…23400 (35, 0, 3) Sector 2304ff00170041 ┆# A additional resource needs have been added to message analysis and conversion to cover reprocessing after message service (worst case corresponding to 10% of messages going to message service) The PU time needs correspond to instruction times with┆
0x23400…23500 (35, 0, 4) Sector 2305ff00170041 ┆# Aout CACHE HITS and is thus a conservative estimate. Since the direct CPU time for an application process is known to be small from experience with appliations of this kind a fairly accurate estimate is possible, based on number of system calls (I/O┆
0x23500…23600 (35, 0, 5) Sector 23063000170041 ┆# 0 A access, disk access, table access etc.) e average number of multiple transmissions per outgoing message. This number is found as the ratio between the incoming character capacity and the outgoing character capacity of external channels for the pe┆
0x23600…23700 (35, 0, 6) Sector 2307ff00170041 ┆# A 1 The disk access time is given as t access = t HANDLER + t channel + t rot + t SEEK + t TRANSFER t HANDLER = Disk handler CPU time = 6 ms. 1 ┆
0x23700…23800 (35, 0, 7) Sector 2208ff00170041 ┆" A t CHANNEL = transfer time to/from disk controller of data and instructions, time is negligible t ROT = rotational delay of disk = 8.3 ms. average t SEEK = time for locating the proper t┆
0x23800…23900 (35, 0, 8) Sector 2309ff00170041 ┆# Areation rate for the system), i.e. 200 char./sec. minus 10% due to CTS & ATOMAL messages which are deleted = 180 char/sec. Fig. 4.7.1-1 presents the peak traffaic flow in terms of characters; the equivalent number of messages is simply derived fro┆
0x23900…23a00 (35, 0, 9) Sector 230aff00170041 ┆# Am the size of the average message. 1500 x 0.84 + 400 x 0.1 + 7000 + 0.04 = 1610 char. where the distribution of operational, service, and data messages corresponds to the figures from the IFB. The peak number of incoming and hence outgoing mes┆
0x23a00…23b00 (35, 0, 10) Sector 230bff00170041 ┆# Asages for the present configuration is found as 0.12 msg/sec. = 432 msg/hour- According to the IFB, section 5.1.3(01) a 25% increase in local (internal) and external communication lines (terminals) combined with a 30% increase of message traffi┆
0x23b00…23c00 (35, 0, 11) Sector 230cff00170041 ┆# Ac shall be possible without hardware or software changes. A 30% increase will result in a peak number of incoming and hence outgoing messages for the expanded configuration of 0.16 msg/sec. = 562 msg/hour Taking into account the maximum amount ┆
0x23c00…23d00 (35, 0, 12) Sector 230dff00170041 ┆# Aof multiple transmissions (factor 1.2) the number of outgoing messages for the expanded configuration is 674 msg/hour. It is seen that the busy hour rate of 500 messages specified in the IFB is included in these figures. A peak (character) throug┆
0x23d00…23e00 (35, 0, 13) Sector 230eff00170041 ┆# Ahput rate of 600 char/sec incoming, and 800 char/sec. outgoing has been specified in the IFB, section 5.1.4.2(g). The sytem character throughput is discussed in section 4.7.2 and it is shown how the system also will accept this peak rate whic┆
0x23e00…23f00 (35, 0, 14) Sector 230fc600170041 ┆# F Ah is well above the maximum possible rate in a system with a 30% traffic expansion: 242 x 1.3 = 315 char/sec incoming, and 478 x 1.3 = 631 char/sec outgoing Refer to fig. 4.7.1-1. 28 6 43 408 26461 ' * 7 7 _┆
0x23f00…24000 (35, 0, 15) Sector 2300ff00170041 ┆# A 1 4.7.2 Throughput The expanded configuration flow, i.e. the configuration corresponding to 30% traffic expansion and with continous maximum character transfer rates is used for th┆
0x24000…24100 (36, 0, 0) Sector 2401ff00170041 ┆$ A 1 - 10% of outgoing messages are locally prepared is a Christian Rovsing assumption which is supported by the fact that 10% of all messages are service messages out of which a certai┆
0x24100…24200 (36, 0, 1) Sector 2402ff00170041 ┆$ An part is prepared at supervisory positions. This is also the reasonable the amount of messages which may be prepared considering that message reception will take place simultaneously. - external channel capabilities are taken from the IFB. - c┆
0x24200…24300 (36, 0, 2) Sector 2403ff00170041 ┆$ Aharacter flows for the internal terminals are calculated from the above flow figures assuming maximum external character input rate and the following assumptions plus derivations from the IFB: - messages are presented in full with annotation for ┆
0x24300…24400 (36, 0, 3) Sector 2404ff00170041 ┆$ Amessage service, and returned in full (1500 char.) - a guiding format is presented to the user for message preparation and full message is returned (400 char for supervisory positions, 1500 char. for the MCSF). - delivery of messages as receiv┆
0x24400…24500 (36, 0, 4) Sector 2405ff00170041 ┆$ Aed: 400 char. for supervisory positions and 1500 char for the MCSF. - The outgoing character rate for external channels has an upper limit given by the capacity; the ratio between the actual number of outgoing messages and the possible number o┆
0x24500…24600 (36, 0, 5) Sector 2406ff00170041 ┆$ Af outgoing messages is the maximum possible average number of multiple transmissions per outgoing message. This number is found as the ratio between the incoming character capacity and the outgoing character capacity of external channels for the pe┆
0x24600…24700 (36, 0, 6) Sector 24079c00170041 ┆$ Aak traffic flow and is 240/200 = 1.2. - input character rate on the MC channel (from standby system) is low and disregarded in these calculations. e extent that sufficient evidence is available for judgement of performance compliance. In order ┆
0x24700…24800 (36, 0, 7) Sector 2308ff00170041 ┆# A 1 - output rate to the MC channel (to standby system) is assumed to be of the same size as the total outgoing character rate for other external channels (which reflects the message c┆
0x24800…24900 (36, 0, 8) Sector 2409ff00170041 ┆$ Ae compliance; deviations from these additional assumptions, which are of conservative nature, are not expected to degrade the performance appreciably and never to the extent of non-compliance. Whenever additional assumptions have been made this fac┆
0x24900…24a00 (36, 0, 9) Sector 240aff00170041 ┆$ At is made clear in the text. 4.7.1 Message Traffic Flow Refer to fig. 4.7.1-1. The message traffic flow has been derived as follows: - number of incoming messages equal to number of outgoing is a direct consequence of the figures from the┆
0x24a00…24b00 (36, 0, 10) Sector 240b4200170041 ┆$ B A IFB reflecting the fact that the MPF is a relay facility. =~ BL5C`5M{) RV5Cq5M . R`5Cq5M@1MI1:h= Rp5Cr4IMM.:^=~ B}5I:g=~ J 5IC$3I > S C_* ┆
0x24b00…24c00 (36, 0, 11) Sector 240cff00170041 ┆$ A 1 - 50% ACP 127 formatted incoming messages which are broadcasted, and 50% ACP126 formatted incoming messages which are transmitted on TARE and TRC is a correct case assumption givin┆
0x24c00…24d00 (36, 0, 12) Sector 240dff00170041 ┆$ Ag the maximum processing load for message analysis and conversion. - 10% of incoming messages need service (garbled etc.) is a Christian Rovsing assumption. 3 of 4 supervisory positions are service positions. - 20% of incoming message for local┆
0x24d00…24e00 (36, 0, 13) Sector 240eff00170041 ┆$ A delivery is a conservative Christian Rovsing and supported by the fact that 10% of all incoming messages are service messages out of which a certain part are directed to the supervisors attention. - 10% of outgoing messages need routing assignmen┆
0x24e00…24f00 (36, 0, 14) Sector 240f2b00170041 ┆$ + At is a Christian Rovsing assumption. FIH 4.7 - 4.7.4 16 02 82 09 10 5 21 23940 05 03 81 12 39 01 14 05 03 82 19 24 11 03 82 11 01 0126A 28 6 43 408 26461 ' * 7 7 _┆
0x24f00…25000 (36, 0, 15) Sector 24008500170041 ┆$ A 1 Fig. 4.7.1-1 ┆
0x25000…25100 (37, 0, 0) Sector 2501ff00172141 ┆% !A 1 After completion of the functional subtest the final operational subtest can be initiated. The test scenarios and procedures for the operational test shall be prepared by the purc┆
0x25100…25200 (37, 0, 1) Sector 2502ff00172141 ┆% !Ahaser together with the contractor. The operational test shall be successfully performed by exercising the complete CROSS FOX network over 3 periods each lasting at least 10 days. Any software modifications required to comply with operational an┆
0x25200…25300 (37, 0, 2) Sector 25036f00172141 ┆% o !Ad security requirements shall have to be made and demonstrated by the contractor before the final accpetalure Reporting System described in section 6.4. ┆
0x25300…25400 (37, 0, 3) Sector 00001a00172141 ┆ !Ance of the software. 7.2.5.2 Software Reliability Verification The software reliability will be assessed by monitoring if the MDSD during the 240 hours accumulated test time of the MPF Subsystem Verif┆
0x25400…25500 (37, 0, 4) Sector 2505ff00171241 ┆% A 1 All terminal equipment, communication lines, and users of the MPF subsystem will be associated with a security profile. This profile determines the allowed functions, and the high┆
0x25500…25600 (37, 0, 5) Sector 2506ff00171241 ┆% Aest permissible classification level to be accessed. The system will always check against these profiles before any exchange of data are to be performed In the absense of a reply or incase of an erroneous answer to the securith procedures describ┆
0x25600…25700 (37, 0, 6) Sector 25072600171241 ┆% & Aed above the user will be deniedempts to violate the security rules will immediately cause the terminal to be blocked and the event to be reported to the supervisor for further action. 2.6 ACCOUNTABILITY PROCEDURES The system will account for ┆
0x25700…25800 (37, 0, 7) Sector 00002f00171241 ┆ / A access and the terminal will be blocked.nd transactions between the user/supervisor and the terminals. Whenever anomalies are detected a suitable warning and report will be generated to the supervisor. Based on the og of informaton in the histori┆
0x25800…25900 (37, 0, 8) Sector 25099700171241 ┆% Am which provides a high operational security, the proposed MPF includes security checks as an integral well-embedded part of the entire system. d for users of the system, specifying the maximum classification level and special handling category of ┆
0x25900…25a00 (37, 0, 9) Sector 250aff00171241 ┆% A 1 The most important security procedure is the terminal access control, i.e. ensuring that only certain people can gain access to the system via a terminal. This is achieved by key ┆
0x25a00…25b00 (37, 0, 10) Sector 250bff00171241 ┆% Alock function and by a sign-on procedure implemented in the terminals. These procedures, the physical and the logical, are effective protection against unauthorized use of the system. While the physical key is in the "OFF" state the terminal is b┆
0x25b00…25c00 (37, 0, 11) Sector 250cff00171241 ┆% Alocked and no data can be entered or fetched via the terminal. By turning the key to the "ON" state the terminal will be ready for the sign-on-procedure, where a correct password and identification code shall be entered before access to the system ┆
0x25c00…25d00 (37, 0, 12) Sector 250dff00171241 ┆% Acan be obtained. Once the user has passed the sign-on-procedure, the system will check his authorization whenever information is to displayed on the terminal. This is done via the security warning procedure which requires a valid security keyword┆
0x25d00…25e00 (37, 0, 13) Sector 250eff00171241 ┆% A to be entered before display of information of specific classification and/or special handling type as specified by the supervisor. All terminal equipment, communication lines, and users of the MPF subsystem will be associated with a security pro┆
0x25e00…25f00 (37, 0, 14) Sector 250fdb00171241 ┆% [ Afile. This profile determines the allowed functions and the highest permissible classification level to be accessed. The system will always check against these profiles before any exchange of data are performed.i.e. recovery not possible via switc┆
0x25f00…26000 (37, 0, 15) Sector 0000b000171241 ┆ 0 A In the absence of a reply or in case of an erroneous answer to the security procedures described above the user will be denied access and the terminal will be blocked.This corresponds to absolute worsecase of recovery and is only of interest in c┆
0x26000…26100 (38, 0, 0) Sector 2601ff00171241 ┆& Aase of fatal damage to the on-line mirrored-disks. In almost all cases of recovery it is based on the historical data base on the mirrored-disks combined with frequent checkpointing of transactinos. 2.8 ACCOUNTABILITY PROCEDURES The system wi┆
0x26100…26200 (38, 0, 1) Sector 2602ff00171241 ┆& All account for messages exchanged with external stations and transactions between the user/supervisor and the terminals. Whenever anomalies are detected a suitable warning and report will be generated to the supervisor. Based on the log of informa┆
0x26200…26300 (38, 0, 2) Sector 26036b00171241 ┆& k Ation in the historical data base the supervisor will be able to inspect the sequence of messages and messages over the channels. Further the supervisor will be able to specify the periodicity of service messages to be received/transmitted automat┆
0x26300…26400 (38, 0, 3) Sector 2604ff00171241 ┆& A 1 transactions. By using proper procedures he will be able to effect tracer actions. Each record of the accountbility log will be uniquely identified by a reference identifier, a t┆
0x26400…26500 (38, 0, 4) Sector 2605ff00171241 ┆& Aime stamp and a code indicating the type of the record, i.e. type of message, type of transaction. Furthermore, each record will contain sufficient information as to the action taken. The second part of the accountability is performed through the┆
0x26500…26600 (38, 0, 5) Sector 2606ff00171241 ┆& A control of messages exchanged with the external stations connected to the Message Subsystem. The transmission and receiption of messages will be controlled by using unique channel designators together with the transmission serial number. The sys┆
0x26600…26700 (38, 0, 6) Sector 2607ff00171241 ┆& Atem will continously monitor the continuity of traffic based on the transmission serial numbers. If discrepancies are discovered a warning message will be forwarded to the supervisor indicating the error and the transmission identification of the m┆
0x26700…26800 (38, 0, 7) Sector 2508ff00171241 ┆% Aessage involved. Further, to ensure continuity of the traffic on some channels, procedures will be implemented for sending/receiving channel check and channel continuity service messages. 2.9 OPERATIONAL SECURITY In order to achieve a syste┆
0x26800…26900 (38, 0, 8) Sector 2609ff00171241 ┆& Ano data can be entered or received by unauthorized people. The supervisor maintains security profiles for communication lines, for terminals and for users of the system, specifying the maximum classification level and special handling category of ┆
0x26900…26a00 (38, 0, 9) Sector 260aff00171241 ┆& Ainformation that are allowed to be exchanged over the external lines and to/from the terminals and users. It will be possible for the supervisor at any time to change the password for the users and to block terminals so no access to the system can ┆
0x26a00…26b00 (38, 0, 10) Sector 260bff00171241 ┆& Abe achieved. Any attempts to violate the security rules will immediately cause the terminal to be blocked and the event to be reported to the supervisor for further action. 2.6 STORAGE & RETRIEVAL All messages reloged or generated by the MPF ┆
0x26b00…26c00 (38, 0, 11) Sector 260cff00171241 ┆& Awill be stored for later retrieval in the Historical Data Base. Each valume of storage will account for 7 days of traffic. Retrieval keys are based on address information, time of file, sequence numbering, and internal item references facilitati┆
0x26c00…26d00 (38, 0, 12) Sector 260d2300171241 ┆& # Ang unique identification. 2.5.2 Message Handling The operational staff will have different facilities for supervision and control of relay of messages from the ship commanders to the shore commanders and ┆
0x26d00…26e00 (38, 0, 13) Sector 260eff00171241 ┆& A 1 2.7 SYSTEM CONFIGURATION CONTROL, INITIALIZATION & RECOVERY An engineering position is available for the following tasks - physical reconfiguration - loading and control of di┆
0x26e00…26f00 (38, 0, 14) Sector 260fff00171241 ┆& Aagnostic and maintenance S/W (standby PU in off-line mode) - manual initialization of switchover. Switchover to standby PU is normally automatic. - control of different start up modes in case of total error, i.e. recovery not possible via switc┆
0x26f00…27000 (38, 0, 15) Sector 2600ff00171241 ┆& Ahover. Dump of new system data base based on present configuration may be initiated by the supervisor. This data base is used at reinitialization from off line disk. This corresponds to absolute worsecase of recovery and is only of interest in c┆
0x27000…27100 (39, 0, 0) Sector 2701cd00171241 ┆' M Alease is requested by the originator the message is displayed at the supervisor terminal requesting release authorization. The supervisor may then decide to release, defer or reject the message. trol o System Monitoring o Message Service. ┆
0x27100…27200 (39, 0, 1) Sector 2702ff00171241 ┆' A 1 2.5.4 Channel Control The supervisor will have facilities to control the external as well as the internal channels by means of the procedures for open and close of channels, the ┆
0x27200…27300 (39, 0, 2) Sector 2703ff00171241 ┆' Aprocedures for channel accountability, the procedures for traffic of operational messages and service messages over the channels. Further the supervisor will be able to specify the periodicity of service messages to be received/transmitted automat┆
0x27300…27400 (39, 0, 3) Sector 2704ff00171241 ┆' Aically over a channel and to specify the maximum classification of a message that may be transmitted over a channel. 2.5.5 System Monitoring To draw the attention of the supervisory staff to specific events, the MPF will be implemented with an ┆
0x27400…27500 (39, 0, 4) Sector 2705ff00171241 ┆' Aextensive reporting facility. The reports will fall into the following categories: o warning reports o channel status reports o queue status reports o command completion reports o security reports The reports will be printed at the┆
0x27500…27600 (39, 0, 5) Sector 2706ff00171241 ┆' A supervisory printer. Besides the reporting of specific events, log printouts of all transactions and events make it possible for the supervisory staff to reconstruct any sequence of past transactions and events. Statistical data are compiled and ┆
0x27600…27700 (39, 0, 6) Sector 27078200171241 ┆' Aprinted out every hour, day, week and month, among other things facilitating the performance measurements of the system. sefull supervisory capabilities such as: o system control o message handling o message release o channel control ┆
0x27700…27800 (39, 0, 7) Sector 2608ff00171241 ┆& A 1 2.5.6 Security Control The supervisor will be in charge of controlling the security procedures (see section 2.7) proposed in the system solution for the purpose of ensuring that ┆
0x27800…27900 (39, 0, 8) Sector 2709ff00171241 ┆' A 1 o system monitoring o security control The functions and transactions to be performed by the MPF are requested by the operator by use of commands entered via the formatted VD┆
0x27900…27a00 (39, 0, 9) Sector 270aff00171241 ┆' AU dialog. To protect against unintended actions each command is to be accompanied by a permisive entry code and a confirmation code. 2.5.1 Systems Control Commands will exist that allow the supervisor to achieve access to the system data for ┆
0x27a00…27b00 (39, 0, 10) Sector 270bff00171241 ┆' Athe purpose of generating, updating and printing the stored data. System data consist of: o addressing tables o ACP127/ACP126 format parameters o counters o terminal/operator information o external channel information The superviso┆
0x27b00…27c00 (39, 0, 11) Sector 270ce800171241 ┆' h Ar will also be capable of controlling the print out of messages and supervisory data, controlling the off-line storage to fulfil the archiving and retrieval requirements, and controlling the security aspects of the system. e available for common ┆
0x27c00…27d00 (39, 0, 12) Sector 270dff00171241 ┆' A 1 2.5.2 Message Handling The operational staff will have different facilities for supervision and control of relay of messages from the ship commanders to the shore commanders and ┆
0x27d00…27e00 (39, 0, 13) Sector 270eff00171241 ┆' Avice versa. The main facilities are: o retransmission of previously transmitted messages o screening and vetting of messages before transmittal o allow specification of different actions to be performed for mesages of certain classificatio┆
0x27e00…27f00 (39, 0, 14) Sector 270fff00171241 ┆' An levels, special handling categories, or precedence levels. o correction of garbled incoming messages o routing assignment of messages when the automatic translation fails. 2.5.3 Message Release Each locally prepared message, shall befo┆
0x27f00…28000 (39, 0, 15) Sector 2700ff00171241 ┆' Are transmittal, have a release authorization. The MCSF user and the supervisor have authorization to release messages themselves, whereas messages drafted by other supervisory staff need to be released by the supervisor before transmittal. When re┆
0x28000…28100 (40, 0, 0) Sector 2801ff00171241 ┆( Ag operator. The main functions related to the interface fall into the following categories: o Access Control o Message Preparation o Message Retrieval o Status Enquiries o System Control o System Monitoring o Message Service. ┆
0x28100…28200 (40, 0, 1) Sector 2802ff00171241 ┆( A 2.4 LOCAL MESSAGE PREPARATION The MPF will provide facilities for local message preparation at the MCSF user terminal and at any of the four supervisory terminals. The drafter of a message will be advised, by the interactive dialog's use of f┆
0x28200…28300 (40, 0, 2) Sector 2803a200171241 ┆( " Aormatted screen layouts, how to prepare a correct message. The message will be validated when entered into the host, and, if invalid, the drafter will be sy to use man-machine interfaces and operational aspects. The objectives for the MS design ┆
0x28300…28400 (40, 0, 3) Sector 2804ff00171241 ┆( A 1 notified by an error code/message, with the erroneous field highlighted. The drafter may then, by use of the convenient edit functions, correct the invalid data. Related functio┆
0x28400…28500 (40, 0, 4) Sector 2805ff00171241 ┆( Ans to the message preparation function are: o Message delivery, i.e. display/printing of a incoming/outgoing message at a terminal for read only purposes. o Message retrieval, i.e. display of a previously processed and stored message for the pur┆
0x28500…28600 (40, 0, 5) Sector 2806ff00171241 ┆( Apose of read only or retransmission. o Message status, i.e. keep track of messages prepared and displayed at each terminal. To facilitate a CAMPS-compatible user-interface, the work station in the MCSF room has been equiped with a VDU and receiv┆
0x28600…28700 (40, 0, 6) Sector 2807ff00171241 ┆( Ae-only-printer. 2.5 SUPERVISORY FUNCTIONS The operational staff running the Message Subsystem are provided with many usefull supervisory capabilities such as: o system control o message handling o message release o channel control ┆
0x28700…28800 (40, 0, 7) Sector 27080700171241 ┆' A ansmission is send to the ship. The messages sent from the ship after "go ahead" will be either acknowledged or not; the MPF supervisior may request a retransmission in case of message garbling. The transmission session will end with an end-of-┆
0x28800…28900 (40, 0, 8) Sector 28097000171241 ┆( p Atransmission-signal and the MPF will mark the channel "available for common trafic" in the status table. ACP 127 supp. 3 with format lines 1 to 4 and 7 and 8 removed. Each message destined for transmission on the broadcast may, if specified by th┆
0x28900…28a00 (40, 0, 9) Sector 280aff00171241 ┆( A 1 If the message is of an unacceptable quality then the supervisor shall be informed and the received message shall be queued at the supervisor's printer. Apart from issuing a pre-t┆
0x28a00…28b00 (40, 0, 10) Sector 280bff00171241 ┆( Aransmission request the action to be taken by the supervisor may be to advise the ship to change frequency by sending a service message. 2.2.2 Dissemination of traffic control Information The MPF will have facilities for monitoring channel usa┆
0x28b00…28c00 (40, 0, 11) Sector 280cff00171241 ┆( Age and supporting the supervisor in disseminating the proper information and advice to the users. The following support is provided o Dissemination of a channel availability list, including information on which channels are available for common ┆
0x28c00…28d00 (40, 0, 12) Sector 280dff00171241 ┆( Ause. A status list will be maintained by the MPF o Assessing circuit quality and contention and advising ships to change frequency. 2.3 OPERATOR SYSTEM INTERFACE The MPF will be implemented with a user-convenient man/machine interface based┆
0x28d00…28e00 (40, 0, 13) Sector 280eff00171241 ┆( A on a VDU. This has been developed by Christian Rovsing A/S together with NATO staff for use in the CAMPS system. The interface is based on an interactive dialog that assists the user in entering data, so a fast and error free data entry can be ac┆
0x28e00…28f00 (40, 0, 14) Sector 280fc000171241 ┆( @ Ahieved. The dialog is partly based on menues-to facilitate a quick change among the different functions and transactions, and partly on a form-completion procedure-to ease date entry. , and the MPF will automatically retransmit the required messag┆
0x28f00…29000 (40, 0, 15) Sector 2800ff00171241 ┆( A 1 The man/machine interface will be implemented for the following users of the MPF subsystem: o MCSF user o Supervisor o Message service operator o Maintenance engineerin┆
0x29000…29100 (41, 0, 0) Sector 2901ff00171241 ┆) A subject to modifications as introduced by expiration time and message screening and vetting. 2.1.4 Procedure for Crypto Handling. To allow the accomplishment of key change procedures, the supervisor can suspend broadcast traffic in an orderly ┆
0x29100…29200 (41, 0, 1) Sector 2902ff00171241 ┆) Afashion for a specified period of the day. The MPF will support the supervisor in transmitting the proper service messages and in the execution of the message transmission procedures. Initialization and synchronization of the crypto's will be co┆
0x29200…29300 (41, 0, 2) Sector 29039d00171241 ┆) Antrolled from the MPF through a crypto control box. The MPF will use V24 lines to request synchronization and receive a ready-to-transmit-message. nd easy to use man-machine interfaces and operational aspects. The objectives for the MS design ┆
0x29300…29400 (41, 0, 3) Sector 2904ff00171241 ┆) A 1 2.2 SHIP-TO-SHORE MESSAGE HANDLING The processing of the Ship-To-Shore message traffic implemented in the MPF will support the operational procedures laid down in the relevant par┆
0x29400…29500 (41, 0, 4) Sector 2905ff00171241 ┆) Aagraphs of ACP127 Supp. 1, as listed in the IFB. Below a short description of the operational procedures will be given. For further details please refer to section 4.2.1 of this appendix. 2.2.1 Receipt of Messages on Ship-to-Shore When ships┆
0x29500…29600 (41, 0, 5) Sector 2906ff00171241 ┆) A wish to send a message via the Ship-to-Shore, they will choose one of the available channels and continue to send an initial test message until answer from the MPF is received. When the MPF registers the test message, the supervisor will be infor┆
0x29600…29700 (41, 0, 6) Sector 2907ff00171241 ┆) Amed, and the channel will be marked "in use" in the channel status. If the quality of the received message compiled by the MCM is accpetable according to the character ambiguity level defined by the supervisor, then an invitation to commence the t┆
0x29700…29800 (41, 0, 7) Sector 2808ff00171241 ┆( Aransmission is send to the ship. The messages sent from the ship after "go ahead" will be either acknowledged or not; the MPF supervisior may request a retransmission in case of message garbling. The transmission session will end with an end-of-┆
0x29800…29900 (41, 0, 8) Sector 2909ff00171241 ┆) Athe broadcast. The format of the messages to be transmitted on the broadcast will be in accordance with ACP 127 supp. 3 with format lines 1 to 4 and 7 and 8 removed. Each message destined for transmission on the broadcast may, if specified by th┆
0x29900…29a00 (41, 0, 9) Sector 290aff00171241 ┆) Ae supervisor, be subject to vetting and/or screening by an operator before its entry into a broadcast channel queue. The MPF will have facilities for minimimizing transmission on the broadcast taking into account that a given ship may be listening┆
0x29a00…29b00 (41, 0, 10) Sector 290bff00171241 ┆) A to more than one Broadcast channel. 2.1.2 Dissemination of traffic control Information. The MPF will have the facilities for transmitting service messages informing of broadcast channel assignment and disseminated message traffic. The followi┆
0x29b00…29c00 (41, 0, 11) Sector 290cff00171241 ┆) Ang information is transmitted: o Channel allocation list, indicating to ships and other copying authorities the assignment of Broadcast Channels. This service message is sent via the Broadcast service channel. o ZOU list will be routed to super┆
0x29c00…29d00 (41, 0, 12) Sector 290dae00171241 ┆) . Avisor specified authorities giving the routing information. This service message will be compiled and transmitted at 23.59 each day or at the supervisors discretion. tion of Information .......... 2.2 SHIP-to-SHORE MESSAGE HANDLING .....┆
0x29d00…29e00 (41, 0, 13) Sector 290eff00171241 ┆) A 1 o Channel frequency change, notifying the ships of changes to the frequency of the broadcast channels. o Traffic check list, including an identification of all messages transmitt┆
0x29e00…29f00 (41, 0, 14) Sector 290fff00171241 ┆) Aed on a channel basis will be transmitted periodically on each channel. 2.1.3 Retransmission on Broadcast Ships can send requests for retransmission via the ship-to-shore subsystem, and the MPF will automatically retransmit the required messag┆
0x29f00…2a000 (41, 0, 15) Sector 2900ff00171241 ┆) Ae. Also the supervisor will have the facility to request retransmissions. The MPF will provide for re-runs of traffic. The supervisor will specify the level of precedence above which messages shall be subject to re-run. The above precedures are┆
0x2a000…2a100 (42, 0, 0) Sector 2a01ff00172041 ┆* Aface to the SSP (Support Software Package) and the OLP (Offline Package) in the off-line PU and allocation of resources for off-line operations. 4.6.2.6.8 Watchdog Firmware Functions These include the following functions: - Watchdog line comm┆
0x2a100…2a200 (42, 0, 1) Sector 2a02ff00172041 ┆* Aunication firmware. This supports communication to the two PUs, the operator VDU, and the operator printer. - Switch logic This controls the physical connection of H/W modules based on - commands from PUs - no keep alive messages recei┆
0x2a200…2a300 (42, 0, 2) Sector 2a032100172041 ┆* ! Aved from either of the PUs - MC-Checkpoint Transmission - MC-Checkpoint Reception - Online diagnostics - Line Monitoring and Control - Reception of Technical Error Reports - Operator Commands┆
0x2a300…2a400 (42, 0, 3) Sector 2a04ff00172041 ┆* A 1 - commands from the operator - direct monitoring of discrete points in the crates. (this is done through the Configuration Control Bus by a periodic scanning. - Enforceme┆
0x2a400…2a500 (42, 0, 4) Sector 2a05ff00172041 ┆* Ant of switchover to the standby PU. - WD-standard Firmware The WD-Kernel and start up firmware. 4.6.2.7 Table Management Package (TMP) The Table Management Package administers a data base containing: . Tables (e.g. PLA-tables (Plain Langua┆
0x2a500…2a600 (42, 0, 5) Sector 2a06ff00172041 ┆* Ages Address) . System Parameters (e.g Device Parameters) . Global Serial Numbers (e.g. Transmission Serial Nos). TMP searches and delivers data to various other packages on request. TMP may update the data base automatically or on request. ┆
0x2a600…2a700 (42, 0, 6) Sector 2a070d00172041 ┆* A An acc 4.6.2.6.3 On-line Diagnostics These programs are low priority tasks aiming at limiting the effect of an error by - timely detection of errors - reporting the error condition ┆
0x2a700…2a800 (42, 0, 7) Sector 0000d000172041 ┆ P Aess control is employed in the search and update functions. TMP is composed of the following subpackages: . TMP Search . TMP Update . TMP Monotor (For interfacing to the process being served). ing Units) for VDUs, external channels, stand a┆
0x2a800…2a900 (42, 0, 8) Sector 2a09ff00172241 ┆* "A 1 The user may access the receive queue, which is a queue of the precedence type into which CROSSFOX interts all messages destined to the terminal. The user may inspect/remove/get a┆
0x2a900…2aa00 (42, 0, 9) Sector 2a0aff00172241 ┆* "A printed copy of the queued elements. The operator may also instruct the system to print all messages below a certain security level on the printer immediately on arrival to the queue. The user may access the response queue, which is a queue of ┆
0x2aa00…2ab00 (42, 0, 10) Sector 2a0ba800172241 ┆* ( "Athe non-precedence type into which CROSSFOX inserts responses to user issued requests with long or unpredictable response times. The user may inspect/remove/get a a person without Supervisor Capability is not possible even if there is an application┆
0x2ab00…2ac00 (42, 0, 11) Sector 00008d00172241 ┆ "A printed copy of the queued elements. The user may issue requests/commands to the system, e.g. retrieve a message, delete a message.DU a second VDU can be connected to SVUP (by issuing Assign Supervisor Command). Only one of these VDUs can access┆
0x2ac00…2ad00 (42, 0, 12) Sector 00000000000000 ┆ ┆
[…0x3…]
0x2b000…2b100 (43, 0, 0) Sector 2b01ff00172141 ┆+ !A Before shipment to site the complete MPF subsystem is assembled at the factory and the functional verification of hardware and software is performed with a customer approved subset of the FQT test procedure. 7.4 ON SITE TESTS 7.4.1 Provision┆
0x2b100…2b200 (43, 0, 1) Sector 2b02ff00172141 ┆+ !Aal Site Acceptance Test The objective of this test is to verify that all equipment contained in the MPF subsystem have been correctly installed. The verification will consist of execution of the functional hardware and software test. 7.4.2 Su┆
0x2b200…2b300 (43, 0, 2) Sector 2b03f200172141 ┆+ r !Abnetwork Test The objective of these tests are to verify the functions of the subnetwork consisting of the MPF subsystem interfaced to the: o SNT category iii - NICS TARE Network - Ship-to-Shore Stations - Broadcast Stations The test s┆
0x2b300…2b400 (43, 0, 3) Sector 2b04ff00172141 ┆+ !A 1 o SNT category iv - Alternate MPF The test will consist of a complete verification of all functions to be provided by the subnetwork. 7.4.3 Overall System Acceptance Test ┆
0x2b400…2b500 (43, 0, 4) Sector 2b05ff00172141 ┆+ !AAfter completion of all individual subnetwork tests an overall sytem test shall be performed. The objective of the overall system test is to demonstrate that the delivered system will provide the required functions, facilities and softare reliabil┆
0x2b500…2b600 (43, 0, 5) Sector 2b06ff00172141 ┆+ !Aity. The test shall be performed by continuous operation of the MPF system for a period of 90 days without "Software failures". The concept "Software failure" will be defined in the Acceptance Test Plan. We are prepared to divide the overall s┆
0x2b600…2b700 (43, 0, 6) Sector 2b07ff00172141 ┆+ !Aystem test into two subtests. The first subtest will consist of a complete functional test. Test procedures will be specified by the contractor and shall be agreed by the purchaser. Initially all functions shall be exercised one by one, subseque┆
0x2b700…2b800 (43, 0, 7) Sector 2500e600172141 ┆% f !Ant Zunctional testing shall be performed by execution of functions in parallel. Any deviation from the specified functional requirements shall be corrected and all functions affected by the corrections shall be retested. bility Verification The┆
0x2b800…2b900 (43, 0, 8) Sector 2b09ff00172041 ┆+ Alone devices, the WatchDog Processor (WDP), the WDP-VDU, the WDP-printer, and the Standby PU (Processing-Unit). LIMCO performs two functions: - Logical control, e.g. access control (block/unblock) delivery control(security ┆
0x2b900…2ba00 (43, 0, 9) Sector 2b0aff00172041 ┆+ A function) - Monitoring of the system connection and subsequent execution of control. (The system connection is used by applications to communicate with the system software which handles security functions. 4.6.2.6.5 Reception of Te┆
0x2ba00…2bb00 (43, 0, 10) Sector 2b0b7500172041 ┆+ u Achnical Error Reports Technical errors are errors resulting from - system calls - instruction execution which, on top of DAMOS, performs the overall control of the particular dualized H/W and S/W configuration of one site. Within a site (e.┆
0x2bb00…2bc00 (43, 0, 11) Sector 2b0cff00172041 ┆+ A 1 - validity checks - WDP-monitoring (Watch Dog Processor) For the error reports, SSC performs: - Update of the configuration table - Update of configuration display - Prin┆
0x2bc00…2bd00 (43, 0, 12) Sector 2b0dff00172041 ┆+ Ating of an error report on the WDP printer. Tha actions for error fix-up depend on the type of error. The actions automatically performed may include: - the retiring of an application process - reconfiguration - emergency switchover to the┆
0x2bd00…2be00 (43, 0, 13) Sector 2b0eff00172041 ┆+ A standby Processing Unit (PU) of the same site. 4.6.2.6.6 Operator Commands to an on-line PU (Processing Unit) Operator commands control the Crossfox Hardware and Software configuration. The execution of the control is shared between the active┆
0x2be00…2bf00 (43, 0, 14) Sector 2b0f7600172041 ┆+ v A PU and the WDP. Some operator functions are: - start-up of all modes of the system - ordered close-down ently settable by decision of the local supervisor. If the incomming MC-traffic indicates problems, the local supervisor will be notif┆
0x2bf00…2c000 (43, 0, 15) Sector 2a00ff00172041 ┆* A 1 - switch between redundant H/W units - device control - control of line attributes - load of new software 4.6.2.6.7 Off-line PU-operation (Processing Unit) Command inter┆
0x2c000…2c100 (44, 0, 0) Sector 2c01ff00172041 ┆, Azed system consisting on an active PU (Processing Unit) and associated peripherals and a standby PU. - A degraded system consisting of one active PU and associated peripherals and one offline PU and associated peripherals. The explicite functi┆
0x2c100…2c200 (44, 0, 1) Sector 2c02f500172041 ┆, u Aonal requirements of the SSC are described in sections 4.2.8, 4.2.9 and 4.2.10. A workable solution poses further implicite requirements to be covered in the SSC-design. This is based on the following partitioning into subpackages: artly rese┆
0x2c200…2c300 (44, 0, 2) Sector 2c03ff00172041 ┆, A 1 - MC-Checkpoint Transmission - MC-Checkpoint Reception - Online diagnostics - Line Monitoring and Control - Reception of Technical Error Reports - Operator Commands┆
0x2c300…2c400 (44, 0, 3) Sector 2c04ff00172041 ┆, A to an online PU - Offline PU operation - Watchdog Firmware Functions. These subpackages are briefly described in the following subsections. 4.6.2.6.1 MC-Checkpoint Transmission This subpackage is active if the site is in the message ┆
0x2c400…2c500 (44, 0, 4) Sector 2c05ff00172041 ┆, Aprocessing state.It receives checkpoint records from MMS, LOG and CSF and transmits checkpoint information via IOC to the other site. 4.6.2.6.2 MC-Checkpoint Reception This subpackage is active if the site is in the MC-Checkpoint-receiving stat┆
0x2c500…2c600 (44, 0, 5) Sector 2c06ae00172041 ┆, . Ae. Via IOC it communicates with the message processing site. The information received is recorded on disk, and the system is kept in a state ready for changeover. 4.6.2.1.8 Error Processor Handles errors detected at the hardware and KERNEL le┆
0x2c600…2c700 (44, 0, 6) Sector 2c07ff00172041 ┆, A 1 4.6.2.6.3 On-line Diagnostics These programs are low priority tasks aiming at limiting the effect of an error by - timely detection of errors - reporting the error condition ┆
0x2c700…2c800 (44, 0, 7) Sector 2b08ff00172041 ┆+ A A specific test program i checksums the read-only system software periodically or on request. 4.6.2.6.4 Line Monitoring and Control (LIMCO) LIMCO monitors and controls the LTU-lines (Line Terminating Units) for VDUs, external channels, stand a┆
0x2c800…2c900 (44, 0, 8) Sector 2c09ea00172041 ┆, j Ator Provision of a tool for communication between application processes. - Message Monitor Application interface to MESSAGE MANAGEMENT SYSTEM - Coroutine Monitor Monitoring of multiprogramming within a process. l and device specific┆
0x2c900…2ca00 (44, 0, 9) Sector 2c0aff00172041 ┆, A 1 - System Call Monitor To serve as a control waiting facility for interfaces to system tasks performed on behalf of application programs. 4.6.2.6 System Status and Control ┆
0x2ca00…2cb00 (44, 0, 10) Sector 2c0bff00172041 ┆, ADAMOS is the general operating system for any local CR80 configuration. SSC is the specific system software, which, on top of DAMOS, performs the overall control of the particular dualized H/W and S/W configuration of one site. Within a site (e.┆
0x2cb00…2cc00 (44, 0, 11) Sector 2c0cff00172041 ┆, Ag. no. 01) it starts and allocates resources to the two PU's, the peripherals and the operator and monitors and controls the Crossfox-MPF on-line and off-line system through interaction between the Watchdog. Modes of Operation For a start it is ┆
0x2cc00…2cd00 (44, 0, 12) Sector 2c0ddb00172041 ┆, [ Aworth clarifying the different scopes of the total system. a) The two sites as a whole The normal state of operation is: One site (e.g. No.01) being active, message-processing and sending MC-checkpoints. plicable for these entities. Major┆
0x2cd00…2ce00 (44, 0, 13) Sector 2c0eff00172041 ┆, A 1 The standby site (in case No.301) being active in receiving MC-checkpoints. The process of initiating message processing at the other site will be termed changeover. There is n┆
0x2ce00…2cf00 (44, 0, 14) Sector 2c0fff00172041 ┆, Ao central equipment to automatically set the overall state. The state of the individual site must be independently settable by decision of the local supervisor. If the incomming MC-traffic indicates problems, the local supervisor will be notif┆
0x2cf00…2d000 (44, 0, 15) Sector 2c00ff00172041 ┆, Aied automatically. b) The individual site As indicated, an operational site may be in the message processing or in the MC-checkpoint-receiving state. In either of these states the site may operate in one of the following two modes: - A duali┆
0x2d000…2d100 (45, 0, 0) Sector 2d013a00172041 ┆- : Aurity profile of the user with that of the file. hem. The processes are scheduled on the basis of a priority scheme. 4.6.2.1.4 Process Communication Facility This provides the basic mechanisms for exchange of information between processes. ┆
0x2d100…2d200 (45, 0, 1) Sector 2d02ff00172041 ┆- A 1 4.6.2.4 Message Management System (MMS) The Message Management System is concerned with specific information files of a fault tolerant message processing system, so it partly rese┆
0x2d200…2d300 (45, 0, 2) Sector 2d03ff00172041 ┆- Ambles the FILE MANAGEMENT SYSTEM (FMS) which is the general system S/W package dealing with backing storage. The two systems, MMS and FMS, are complementary and are incorporated in a single process. MMS interfaces to the application side (comman┆
0x2d300…2d400 (45, 0, 3) Sector 2d04ff00172041 ┆- Ads) and to the disk buffers. Further, the major functions are: - Info File Handling (In a Short Term Storage) Storage and Retrieval Handling of Intermediate and Long Term Storage of message incarnations. Checkpointing and Recovery ┆
0x2d400…2d500 (45, 0, 4) Sector 2d05ff00172041 ┆- A Facilities for continuation after restart or after switchover to the standby processing unit. 4.6.2.5 Crossfox-MPF System Functions (CSF) CSF is a system software package on top of KERNEL which supplies a set of support tools for applicatio┆
0x2d500…2d600 (45, 0, 5) Sector 2d061300172041 ┆- An packages. ity offers functions for reading and setting the system clock, tying the execution of processes to time, and conversion between different time-formats. 4.6.2.1.8 Error Processor Handles errors detected at the hardware and KERNEL le┆
0x2d600…2d700 (45, 0, 6) Sector 2d07ff00172041 ┆- A 1 CSF combines the provision of these tools with a mechanism for: - Error detection and handling - Security and access control - Protection of data - Checkpointing and recove┆
0x2d700…2d800 (45, 0, 7) Sector 2c08ff00172041 ┆, Ary. With reference to the subpackage names, the support tools comprise: - Common Functions Utilities for the other CSF subpackages - Time Monitor Timer driven event facilities and manipulation with current time and date. - Queue Moni┆
0x2d800…2d900 (45, 0, 8) Sector 2d09ff00172041 ┆- A 1 - Line Interface Control This covers common S/W for interface to lines via LTUs (Line Terminanation Units) - Device and Line Control All line, channel and device specific┆
0x2d900…2da00 (45, 0, 9) Sector 2d0aff00172041 ┆- A S/W and firmware for - TARE and MC control - TRC, MRL, S/S and Broadcast control - VDU control - Software Development VDU control - SSC interface (for watchdog console). The IOC package is subdivided into subpackages of the follow┆
0x2da00…2db00 (45, 0, 10) Sector 2d0bff00172041 ┆- Aing categories: - Format Handling (on VDUs) - LTU Handling - LTU Functions - SSC Interface 4.6.2.3 File Management System (FMS) The File Management System is a general system software package used for management of backing starage i.e. dis┆
0x2db00…2dc00 (45, 0, 11) Sector 2d0cbb00172041 ┆- ; Ak and floppy disk storage. The entities managed are the following: - Users (i.e. processes or groups of processes) - Devices (e.g. disk drives) - Volumes (e.g. disk packs) al relationships among processes. This will enable the various DAMOS┆
0x2dc00…2dd00 (45, 0, 12) Sector 2d0dff00172041 ┆- A 1 Files (i.e. logical sequences of backing storage blocks). Management consists of naming, handling, description, functions, etc. as, applicable for these entities. Major┆
0x2dd00…2de00 (45, 0, 13) Sector 2d0eff00172041 ┆- A aspects are those of reliability and security. As for reliability it should be noted that the device management of FMS supports the concept of fault tolerant mirrored disks. This implies that if both on-line disks are operational they are updated┆
0x2de00…2df00 (45, 0, 14) Sector 2d0fff00172041 ┆- A concurrently. If one of the disks for some reason is not operational it will later be updated to re-establish a state with two identical disk contents. Security Whenever file access is attempted information related to users and files are comp┆
0x2df00…2e000 (45, 0, 15) Sector 2d00ff00172041 ┆- Aared in order to two kinds of security measures: - Access Control - Security Check The Access Control checks whether the particular user has the right to the intended kind of access to the particular file. The security Check compares the sec┆
0x2e000…2e100 (46, 0, 0) Sector 2e01ff00172041 ┆. A and with the functions available for operating on them. The processes are scheduled on the basis of a priority scheme. 4.6.2.1.4 Process Communication Facility This provides the basic mechanisms for exchange of information between processes. ┆
0x2e100…2e200 (46, 0, 1) Sector 2e02ff00172041 ┆. AA set of procedures are provided. Two types of resources are used: synchronization elements and communication elements. 4.6.2.1.5 Memory Management At any one time, a process can address 2 x 64 K words (code and data respectively) indirectly ┆
0x2e200…2e300 (46, 0, 2) Sector 2e03ff00172041 ┆. Avia translation tables. This leads to reentrant and unmodifiable code. The Page Manager (PM) allows changing the "position" of the addressing window thus leading to practically unlimited addressing capabilities. The page manager contains basic m┆
0x2e300…2e400 (46, 0, 3) Sector 2e048700172041 ┆. Aechanisms for security and protection by administering the addressing capabilities of processes to data and program segments. t Output Control (IOC) . Message Management System (MMS) . Crossfox MPF System Functions (CSF) . System Status ┆
0x2e400…2e500 (46, 0, 4) Sector 2e05ff00172041 ┆. A 1 4.6.2.1.6 Device Management Device Management controls the device handlers which are handling the direct Input/Output execution and device interrupts. 4.6.2.1.7 Real Time Clock┆
0x2e500…2e600 (46, 0, 5) Sector 2e06ff00172041 ┆. A This facility offers functions for reading and setting the system clock, tying the execution of processes to time, and conversion between different time-formats. 4.6.2.1.8 Error Processor Handles errors detected at the hardware and KERNEL le┆
0x2e600…2e700 (46, 0, 6) Sector 2e07ff00172041 ┆. Avel and provides a central error reporting mechanism. 4.6.2.1.9 Transfer Module For hardware based transfer of data in a Processing Unit. 4.6.2.2 Input Output Control (IOC) The I/O Control S/W package provides the necessary interfaces to t┆
0x2e700…2e800 (46, 0, 7) Sector 2d08d500172041 ┆- U Ahe DAMOS Terminal Management System, TMS, so that it can establish the connection between Crossfox application S/W and terminals and lines. The control functions can be devided into two distinct functions: objects of the CR80M, namely: CPUs, memor┆
0x2e800…2e900 (46, 0, 8) Sector 2e09ff00172041 ┆. Ay modules, memory mapping module, I/O buses and I/O devices. The KERNEL, together with the MAP module, provides a secure means of protecting all data and resources from unauthorized use. The major components of KERNEL are: * Resource Managemen┆
0x2e900…2ea00 (46, 0, 9) Sector 2e0a9800172041 ┆. At * Directory Functions * Process Management and Scheduling * Process Communication Facilities * Memory Management * Device Management ┆
0x2ea00…2eb00 (46, 0, 10) Sector 2e0bff00172041 ┆. A 1 * Real Time Clock * Error Processor * Transfer Module These functions are briefly described in the following subsections. 4.6.2.1.1 Resource Management The Resource Mana┆
0x2eb00…2ec00 (46, 0, 11) Sector 2e0cff00172041 ┆. Agement Module deals with synchronization elements and governs references to e.g. processes and memory segments, for example. Such resources are handled in accordance with hierachical relationships among processes. This will enable the various DAMOS┆
0x2ec00…2ed00 (46, 0, 12) Sector 2e0dff00172041 ┆. A modules to handle resources in a coherent way. 4.6.2.1.2 Directory Functions These are common service functions for the other KERNEL components. The Directory Functions are tools for allocation of resources, i.e. memory segments, processes,┆
0x2ed00…2ee00 (46, 0, 13) Sector 2e0eff00172041 ┆. A CPUs and synchronization elements. 4.6.2.1.3 Process Management and Scheduling A process is defined as the incarnation of the data transformation obtained by execution of a program. During the lifetime of a process it is found in different p┆
0x2ee00…2ef00 (46, 0, 14) Sector 2e0f4600172041 ┆. F Arocess states, e.g. it may be waiting for some event to occur. 4.6.2.6 System Status and Control (SSC) ... 4.6.2.6.1 MC-Checkpoint Transmission ..... 4.6.2.6.2 MC Checkpoint Reception ....... 4.6.2.6.3 On-line┆
0x2ef00…2f000 (46, 0, 15) Sector 2e00ff00172041 ┆. A 1 Each process competes with other processes for system resources, e.g. processor power, physical memory, and I/O-service. Process Management deals with implementation of processes┆
0x2f000…2f100 (47, 0, 0) Sector 2f015a00172041 ┆/ Z A Firmware Functions .... 4.6.2.7 Table Management Package (TMP)...... : =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 ! ┆
0x2f100…2f200 (47, 0, 1) Sector 2f02ff00172041 ┆/ A 1 4.6.2 System Software The MPF system software will be based on the CR80 DAMOS operating system. (Distributed Advanced Multiprocessor Operating System). On top of this highly ve┆
0x2f200…2f300 (47, 0, 2) Sector 2f03ff00172041 ┆/ Arsatile CR80/DAMOS architecture, Christian Rovsing has created a set of Special System Software packages for message processing systems like Crossfox-MPF. The major components in DAMOS are: . KERNEL . Terminal Management System (TMS) . Fi┆
0x2f300…2f400 (47, 0, 3) Sector 2f04ff00172041 ┆/ Ale Management System (FMS) . Root Operating System The Special System Software consists of the following packages: . Input Output Control (IOC) . Message Management System (MMS) . Crossfox MPF System Functions (CSF) . System Status ┆
0x2f400…2f500 (47, 0, 4) Sector 2f05ff00172041 ┆/ Aand Control (SSC) . Table Management Package (TMP) The major features of the system software, described in the following subsections, are: . DAMOS KERNEL . Input Output Control, IOC (incl. DAMOS-TMS) . DAMOS-File Manamement System, FMS┆
0x2f500…2f600 (47, 0, 5) Sector 2f060700172041 ┆/ A 1 ┆
0x2f600…2f700 (47, 0, 6) Sector 2f07ff00172041 ┆/ A 1 . Message Management System, MMS . Crossfox-MPF System Functions, CSF . System Status and Control, SSC (incl. ROS) . Table Management Package 4.6.2.1 Kernel The DAM┆
0x2f700…2f800 (47, 0, 7) Sector 2e08ff00172041 ┆. AOS KERNEL provides the lowest level of system service above the CR80 hardware and firmware level. Thus the KERNEL and the CR80 instruction set is the interface between other S/W modules and the low level H/W objects of the CR80M, namely: CPUs, memor┆
0x2f800…2f900 (47, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(47,0, 9), len=0xff, h3=41172041}, f00=»1720A «, f01=»Crossfox Tilbud «, f02=»birgit «, f03=»KR «, f04=»4.6.2 - 4.6.2.6.8 «, f05=19-02-82 08:53, f06=» 2 «, f07=»32 «, f08=» 16572 «, f09=02-03-82 14:28, f10=» «, f11=»33 «, f12=» 714 «, f13=04-03-82 19:54, f14=11-03-82 11:06, f15=»0126A «, f16=» 17 «, f17=» 3 «, f18=»40 «, f19=» 292 «, f20=» 18739 «, f21=» «, f22=» «, f99=020010000110062710110380aa8a37040000000000000137035000df}
0x2f900…2fa00 (47, 0, 9) Sector 2f0a1100172041 ┆/ A / / / . . . - - - - , , , , + + * DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID AN┆
0x2fa00…2fb00 (47, 0, 10) Sector 2f0bff00172041 ┆/ A 1 1 4.6.2 System Softwa┆
0x2fb00…2fc00 (47, 0, 11) Sector 2f0cff00172041 ┆/ Are ........................ 4.6.2.1 Kernel ............................. 4.6.2.1.1 Resource Management ............ 4.6.2.1.2 Directory Functions ............ 4.6.2.1.3 Process Management and Schedul┆
0x2fc00…2fd00 (47, 0, 12) Sector 2f0dff00172041 ┆/ Aing...................... 4.6.2.1.4 Process Communication Facility . 4.6.2.1.5 Memory Management .............. 4.6.2.1.6 Device Management .............. 4.6.2.1.7 Real Time Clock ................ 4┆
0x2fd00…2fe00 (47, 0, 13) Sector 2f0eff00172041 ┆/ A.6.2.1.8 Error Processor ................ 4.6.2.1.9 Transfer Module ................ 4.6.2.2 Input Output Control (IOC) ......... 4.6.2.3 File Management System (FMS) ....... 4.6.2.4 Message Management System (MM┆
0x2fe00…2ff00 (47, 0, 14) Sector 2f0fff00172041 ┆/ AS) .... 4.6.2.5 Crossfox MC System Functions (CSF) 4.6.2.6 System Status and Control (SSC) ... 4.6.2.6.1 MC-Checkpoint Transmission ..... 4.6.2.6.2 MC Checkpoint Reception ....... 4.6.2.6.3 On-line┆
0x2ff00…30000 (47, 0, 15) Sector 2f00ff00172041 ┆/ A Diagnostics ............ 4.6.2.6.4 Line Monitoring and Control .... 4.6.2.6.5 Reception of Technical Error Reports 4.6.2.6.6 Operator Commands to an on-line PU 4.6.2.6.7 Off-line PU-operation 4.6.2.6.8 Watchdog┆
0x30000…30100 (48, 0, 0) Sector 3001ff00172141 ┆0 !A hardware reliability verification will be provided by calculations of reliability figures in accordance with the principles described in MIL HDBK 217: "Reliability Prediction of Electronic Equipment". Reliability figures have been calculated for┆
0x30100…30200 (48, 0, 1) Sector 3002ff00172141 ┆0 !A all units contained in the MPF subsystem. The calculated values show that no unit has a predicted MTBF value lower than 17000 hours. Due to the high predicted reliability values no test verification of MTBF values is planned. However, the hardwa┆
0x30200…30300 (48, 0, 2) Sector 3003a200172141 ┆0 " !Are reliability will be monitored throughout the development, test and warranty period by means of the Failure Reporting System described in section 6.4. ┆
0x30300…30400 (48, 0, 3) Sector 3004ff00172141 ┆0 !A 1 7.2.5.2 Software Reliability Verification The software reliability will be assessed by monitoring if the MDSD during the 240 hours accumulated test time of the MPF Subsystem Verif┆
0x30400…30500 (48, 0, 4) Sector 3005ff00172141 ┆0 !Aication. 7.2.5.3 Hardware Maintainability Verification A set of maintenance and diagnostics (M&D) programs will be provided as tools for corrective maintenance actions. A demonstration of the M&D program capabilities will provide verification┆
0x30500…30600 (48, 0, 5) Sector 3006ff00172141 ┆0 !A of the predicted MTTR values. Preventive maintenance procedures will be provided in a maintenance manual. 7.2.5.4 Software Maintainability Verification A set of utility programs, editor, compiler, linker and debugger will be provided as tool┆
0x30600…30700 (48, 0, 6) Sector 30079600172141 ┆0 !As for software maintenance. A demonstration of the utility program capabilities will provide verification of the software maintainability. n compliance with the IFB as follows. 7.2.1 Hardware Functional Verification When the first MPF subs┆
0x30700…30800 (48, 0, 7) Sector 2b00ff00172141 ┆+ !A 1 7.3 FACTORY POST PRODUCTION TEST (FPPT) The objective of this test is to provide a final verification of the actual site equipment configuration before shipment from the factory. ┆
0x30800…30900 (48, 0, 8) Sector 3009ff00172141 ┆0 !A 1 7.2.2 Environmental Verification After completion of the functional hardware verification a verification of all environmental requirements will be performed. 7.2.3 Software Fun┆
0x30900…30a00 (48, 0, 9) Sector 300aff00172141 ┆0 !Actional Verification This activity will consist of a verification of the Operating System functions including security features contained herein. Further, all functions provided by the application software will be verified. 7.2.4 MPF Subsytem ┆
0x30a00…30b00 (48, 0, 10) Sector 300bff00172141 ┆0 !AVerification This verification will be performed under simulated, operational conditions by means of a Standard Test Environment simulator. The test simulator will be used for simulation of external interfaces of the MPF subsystem. The test s┆
0x30b00…30c00 (48, 0, 11) Sector 300cff00172141 ┆0 !Aimulator will be able to generate pseudorandom MPF input traffic, which is representative of the specified operational message traffic. The generated message traffic load will be at least 0.5 Erlang for low speed channels and 0.3 Erlang for medium ┆
0x30c00…30d00 (48, 0, 12) Sector 300d7800172141 ┆0 x !Aspeed channels. The simulation will include message traffic corruption by transmission media failure and noise. them with the required test results. These procedures will be prepared and approved prior to the test operation. Verification at any┆
0x30d00…30e00 (48, 0, 13) Sector 300eff00172141 ┆0 !A 1 The objective of the MPF Subsystem verifiation is to verify the operational requirements and to provide a demonstration of the softare reliability. The software reliability will b┆
0x30e00…30f00 (48, 0, 14) Sector 300fff00172141 ┆0 !Ae assessed by monitoring the Mean time between Discovery of Software Defects (MDSD). The acceptance criteria for the MPF Subsystem verification is an accumulated test time of 240 hours, with no more than one failure during the 240 hours. 7.2.5 R┆
0x30f00…31000 (48, 0, 15) Sector 3000ff00172141 ┆0 !Aeliability and Maintainability Verification The objective of this verification is to demonstrate compliance with the reliability and maintainability characteristics specified in the IFB, para 4.5. 7.2.5.1 Hardware Reliability Verification The┆
0x31000…31100 (49, 0, 0) Sector 3101ff00172141 ┆1 !Af hardware and/or software such that measurements and observations of correct operation can be made. A test is where the element of verification is instrumented, measured or displayed directly. A demonstration is where the element of verification ┆
0x31100…31200 (49, 0, 1) Sector 3102ff00172141 ┆1 !Ais logically obvious, as being a necessary constraint to some other result, but is not itself displayed. 7.1.2 Product Assurance Provisions All products manufactured by Christian Rovsing A/S are subject to the provisions of the company's Qualit┆
0x31200…31300 (49, 0, 2) Sector 31037f00172141 ┆1 !Ay Assurance Program. This program is compliant with AQAP-1: "Nato Quality Control System Requirements for Industri". ┆
0x31300…31400 (49, 0, 3) Sector 3104ff00172141 ┆1 !A 1 7.1.3 First Article Qualification Tests (FAQT) All the hardware items included in this proposal either have previously been approved or are now being approved by NATO for use on t┆
0x31400…31500 (49, 0, 4) Sector 3105ff00172141 ┆1 !Ahe CAMPS program as part of a CAMPS First Article Qualification Program. As the hardware requirements for the CROSSFOX MPF equipment are identical to those for the CAMPS equipment it is assumed that no additional FAQT is necessary. The FAQT docum┆
0x31500…31600 (49, 0, 5) Sector 3106ff00172141 ┆1 !Aentation from the CAMPS program will be provided on customer request. 7.2 FACTORY QUALIFICATION AND PROVING TEST (FQT) The objective of this test is to verify that the MPF subsystem hardware and software have been designed and manufactured in a┆
0x31600…31700 (49, 0, 6) Sector 3107ff00172141 ┆1 !Accordance with the functional, environmental, operational and reliability requirements specified. The verification activity will be performed in compliance with the IFB as follows. 7.2.1 Hardware Functional Verification When the first MPF subs┆
0x31700…31800 (49, 0, 7) Sector 3008b800172141 ┆0 8 !Aystem hardware has been integrated a functional verification will be performed. The verification will consist of interface requirements and functional hardware requirements. eptance Test .............. I:g= Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x31800…31900 (49, 0, 8) Sector 3109ff00172141 ┆1 !A 1 7. ACCEPTANCE TEST PROGRAM PLAN. 7.1 General The test program for the MPF subsystem has the objective to provide a systematic, incremental verification of the subsystem's compl┆
0x31900…31a00 (49, 0, 9) Sector 310aff00172141 ┆1 !Aiance with all baseline requirements. The objective of the test program is accomplished by means of the existing, general Christian Rovsing A/S Product Assurance provisions supplemented with the specific test activities outlined in this section. ┆
0x31a00…31b00 (49, 0, 10) Sector 310bff00172141 ┆1 !A The overall test program will be described in a Test Plan in accordance with ACE MANUAL No. 96-1-1, Annex I ADP Standard 007-3. The Test Plan will contain a list of the tests to be performed, test objectives, methods and criterias. The Test Plan┆
0x31b00…31c00 (49, 0, 11) Sector 310cff00172141 ┆1 !A will further contain the schedule and time phasing of the tests 7.1.1 Verification Procedures Throughout the test program all verification will be accomplished by using approved procedures describing the actions, objectives and required test ┆
0x31c00…31d00 (49, 0, 12) Sector 310dff00172141 ┆1 !Aresults for each test segment. A method will be provided for recording the actual test results and for comparing them with the required test results. These procedures will be prepared and approved prior to the test operation. Verification at any┆
0x31d00…31e00 (49, 0, 13) Sector 310e4d00172141 ┆1 M !A level or category will be performed by one of the following methods: erial Numbers (e.g. Transmission Serial Nos). TMP searches and delivers data to various other packages on request. TMP may update the data base automatically or on request. ┆
0x31e00…31f00 (49, 0, 14) Sector 310fff00172141 ┆1 !A 1 a. Examination This method is a non-functional verification, such as visual inspection of the physical characteristics of an item or of the documentation associated with an item┆
0x31f00…32000 (49, 0, 15) Sector 3100ff00172141 ┆1 !A. b. Analysis This method is a non-functional verification, such as reduction or translation of data, review of analytical data or review of performance from a detailed test. c. Test/Demonstration This method is a functional verification o┆
0x32000…32100 (50, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(50,0, 1), len=0xff, h3=41172141}, f00=»1721A «, f01=»Crossfox Tilbud «, f02=»birgit «, f03=»URH «, f04=»7. - 7.4.3 «, f05=19-02-82 09:02, f06=» 1 «, f07=»16 «, f08=» 10433 «, f09=04-03-82 15:50, f10=» «, f11=»02 «, f12=» 45 «, f13=03-03-81 11:13, f14=11-03-82 11:07, f15=»0126A «, f16=» 10 «, f17=» 1 «, f18=»56 «, f19=» 208 «, f20=» 12460 «, f21=» «, f22=» «, f99=020010000110062710110380aa8a37040000000000000137033400df}
0x32100…32200 (50, 0, 1) Sector 32020a00172141 ┆2 !A 2 1 1 1 0 0 0 0 + % DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet┆
0x32200…32300 (50, 0, 2) Sector 3203ff00172141 ┆2 !A 1 TABLE OF CONTENTS 1 ┆
0x32300…32400 (50, 0, 3) Sector 3204ff00172141 ┆2 !A7 ACCEPTANCE TEST PROGRAM PLAN ....................... 7.1 GENERAL ........................................ 7.1.1 Verification Procedures .................... 7.1.2 Product Assurance Provisions ............... 7.1.┆
0x32400…32500 (50, 0, 4) Sector 3205ff00172141 ┆2 !A3 First Article Qualification Tests .......... 7.2 FACTORY QUALIFICATION AND PROVING TEST ......... 7.2.1 Hardware Functional Verificaiton ........... 7.2.2 Environmental Verification ................. 7.2.3 Soft┆
0x32500…32600 (50, 0, 5) Sector 3206ff00172141 ┆2 !Aare Functional Verification ............ 7.2.4 MPF Subsystem Verification ................. 7.2.5 Reliability and Maintainability Verification 7.2.5.1 Hardware Reliabilty Verification ....... 7.2.5.2 Softare Rel┆
0x32600…32700 (50, 0, 6) Sector 3207ff00172141 ┆2 !Aiability Verification ....... 7.2.5.3 Hardware Maintainability Verification .. 7.2.5.4 Softare Maintainability Verification ... 7.3 FACTORY POST PRODUCTION TEST ..................... 7.4 ON SITE TESTS ...........┆
0x32700…32800 (50, 0, 7) Sector 3108d900172141 ┆1 Y !A......................... 7.4.1 Provisional Site Acceptance Test ........... 7.4.2 Subnetwork Test ............................ 7.4.3 Overall System Acceptance Test .............. I:g= Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x32800…32900 (50, 0, 8) Sector 3209ff00172241 ┆2 "Ant, to the MSO, information sent to his VDU 4) Supervise/allow the MSO to prepare service messages and annotation 5) Allow the MSO to make service on outgoing/incoming messages, e.g. Garble Correction, Relay Assistance, Pilot Control, Outgoing┆
0x32900…32a00 (50, 0, 9) Sector 320aff00172241 ┆2 "A Routing Indicator Assignment 4.6.3.2.3 Printer Function The main functions implemented by the Printer Function PRIP, are: 1. Formatting and printout 2. Document accounting a) Formatting and Printout Some of the items queued for print ┆
0x32a00…32b00 (50, 0, 10) Sector 320bff00172241 ┆2 "Acontain binary data which will have to be converted into a displayable form before being printed. The items do not contain all of the data to be printed. The predefined part of it is contained in the Print Format File (PFF) and must be merged wit┆
0x32b00…32c00 (50, 0, 11) Sector 320c9000172241 ┆2 "Ah the variable part to form the complete text. The formatting also includes placing of the text so that a readable layout is obtained. n Functions Prepare Service Message Continue Preparation Delete Service Message Outgoing Service Messa┆
0x32c00…32d00 (50, 0, 12) Sector 320dff00172241 ┆2 "A 1 After the text has been formatted, it will be output to the printer in blocks of upto 512 bytes. b) Document Accounting Document Accounting is to be carried out for the foll┆
0x32d00…32e00 (50, 0, 13) Sector 320eff00172241 ┆2 "Aowing items: - Messages - Service Messages - Reports 4.6.3.2.4 MCSF User Function a) In this section the functions to be performed by VDU User Package (VUP) are outlined. The main task of VUP is to implement the CROSSFOX MPF user functio┆
0x32e00…32f00 (50, 0, 14) Sector 320fff00172241 ┆2 "An. The CROSSFOX MPF user function and the related requirements will be treated as a whole, i.e. the three subfunctions Preparation, Reception, and Release constitute the CROSSFOX MPF user function, and access to each must be granted by the superviso┆
0x32f00…33000 (50, 0, 15) Sector 2a08e600172241 ┆* f "Ar. b) As a short overview, of the services of VUP are outlined below. The user may access the preparation database, where all messages under preparation are kept. The user may insert/delete/edit items in the database. rocess (VUS) User Messag┆
0x33000…33100 (51, 0, 0) Sector 33012a00172241 ┆3 * "Ae Access Monitoring Process (UMAM) ┆
0x33100…33200 (51, 0, 1) Sector 3302ff00172241 ┆3 "A 1 UMAM is used for control of Service Messages under preparation and is shared with all VDU User Subprocesses. VUS is the VDU User Subprocess giving the Supervisor access to user F┆
0x33200…33300 (51, 0, 2) Sector 3303ff00172241 ┆3 "Aunctions when he has User Capability or MSO Capability. The Supervisor Functions are contained in a separate process to ensure that access to these functions by a person without Supervisor Capability is not possible even if there is an application┆
0x33300…33400 (51, 0, 3) Sector 3304ff00172241 ┆3 "A software malfunction. Further, to ensure that Supervisor Control over the system can be maintained after failure of the Supervisor VDU a second VDU can be connected to SVUP (by issuing Assign Supervisor Command). Only one of these VDUs can access┆
0x33400…33500 (51, 0, 4) Sector 3305ff00172241 ┆3 "A VUS as a user only has access to one VDU. 4.6.3.2.2 MSO Function The VDU MSO Package (MSOP) constitutes the only means by which Crossfox Personnel may gain access to the services of the CROSSFOX user function. a) The CROSSFOX MSO function is┆
0x33500…33600 (51, 0, 5) Sector 3306ff00172241 ┆3 "A made up of six subfunctions: Service Message Preparation, Retrieval for Readdressing, Retrieval for Rerun, Incoming Message Service Assistance, Outgoing Message Service Assistance, and Display of Retrieval Messages. A VDU or MSO may have access rig┆
0x33600…33700 (51, 0, 6) Sector 3307de00172241 ┆3 ^ "Ahts to one or more of the subfunction services as specified by the Supervisor. b) The VDU MSO package (MSOP) implements all the services of the CROSSFOX MSO function, which implies the following responsibilities: as shown on Figure 4.6.3.2.1-1. ┆
0x33700…33800 (51, 0, 7) Sector 3208ff00172241 ┆2 "A 1 1) Interface the MSO to the CROSSFOX system, i.e. Man/Machine I/F Support and Monitoring 2) Direct all MSO requests/commands to the relevant package within CROSSFOX 3) Prese┆
0x33800…33900 (51, 0, 8) Sector 3309ff00172241 ┆3 "A 1 Supervisor Printout Control Security Control Global No. Series Control System Parameter Control System Information Extract Table Print These functions enable the supervisor ┆
0x33900…33a00 (51, 0, 9) Sector 330a4800172241 ┆3 H "Ato control the operational and functional aspects of the system. g4:^=~ BV4C75:g=~ Bf4 ZMo Ck4 KMo Mj ~ B 4:g=~ J 4Cq5M")IMy,M1' R 4 'M, CV4:g=~ Bg4M73~ B)4Cq5! ="(=*(=N#FMC 2.=M ':>=V V u:A=!>= AH1 R^4 ]M, C 4:>=2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x33a00…33b00 (51, 0, 10) Sector 330ba000172241 ┆3 "A 1 Fig. 4.6.3.2.1-1 Supervisor Functions ┆
0x33b00…33c00 (51, 0, 11) Sector 330cff00172241 ┆3 "A 1 The Message Handling Functions allow: a) Service Message Preparation Functions Prepare Service Message Continue Preparation Delete Service Message Outgoing Service Messa┆
0x33c00…33d00 (51, 0, 12) Sector 330dff00172241 ┆3 "Age Status b) Retrieval Retrieval for Rerun Retrieval for Re-distribution Retrieval for Local use These functions enable the supervisor to prepare and edit Service Messages, to send Service Messages, to delete Service Messages and to obtai┆
0x33d00…33e00 (51, 0, 13) Sector 330eff00172241 ┆3 "An status regarding Service Messages under preparation or sent for transmission. The retrieval functions enable the supervisor to retrieve any message in a suitable format and to specify re-run or redistribution for local use. The Supervisor Engine┆
0x33e00…33f00 (51, 0, 14) Sector 330fff00172241 ┆3 "Aering Functions enable the supervisor to perform engineering/operator type functions upon the system. Due to the nature of these functions they will be defined during system definition phase. The Supervisor VDU Package interfaces with other parts ┆
0x33f00…34000 (51, 0, 15) Sector 3300ff00172241 ┆3 "Aof the Terminal Package (TEP) as well as other packages of the CROSSFOX MPF System. The interfaces between the Supervisor VDU Process (SVUP) and the other TEP processes are: Supervisor Print Process (SPRI) VDU User Subprocess (VUS) User Messag┆
0x34000…34100 (52, 0, 0) Sector 3401bb00173641 ┆4 ; 6Aon of Man-Machine interface. - Predefined Message Generator To generate predefined messages directly from VDU input on a Message by Message basis. - Configuration Table Gener ┆
0x34100…34200 (52, 0, 1) Sector 0000b400173641 ┆ 4 6Aator Maintains all information relevant for generating site specific software. It generates additionally all input needed by the SSC package for initialization of sites. y program development, systems generation and documentation. 4.6.4.1.2 S┆
0x34200…34300 (52, 0, 2) Sector 00003600173341 ┆ 6 3Ar the analysis is discussed in section 7.2.5.1. isk error provide the traffic accounting necessary to restore the information of not fully received messages and transactions and to reissue information not fully transmitted. Similar situations may ┆
0x34300…34400 (52, 0, 3) Sector 00000000000000 ┆ ┆
[…0x4…]
0x34800…34900 (52, 0, 8) Sector 3409f800172341 ┆4 x #Ato fig. 4.6.3.6-1. Invocation of delivering statistics (4a). Read the appropriate statistics information (4b) and copy it into 2 CIFs, as much as they can accomodate (4c). Send CIFs to printer process (4d) and await reply when next CIF sng volu┆
0x34900…34a00 (52, 0, 9) Sector 00005000172341 ┆ P #Ahall be created and sent (c). Request storage occupancy, from MMS (4f). 5 Statistics Package (STP) This section describes the statistical functions under normal operation. The Statistics Package supports 4 functions outlined in the package de┆
0x34a00…34b00 (52, 0, 10) Sector 340bff00172341 ┆4 #A6.3.6-1 for event numbers): Invocation of generation part of statistics package (3a). Calculate from the dumped statistics, statistics for the last hour and output to statistics files (3c and 3f). Statistics are kept on an hourly basis for 24 h┆
0x34b00…34c00 (52, 0, 11) Sector 340cff00172341 ┆4 #Aours, on a daily basis for 1 day and on a weekly basis for 4 weeks. 4.6.3.6.4 Statistics Request Response Statistics print is output by the terminal package. STP deliers the statistics information to TEP. The processing is (for event numbers,┆
0x34c00…34d00 (52, 0, 12) Sector 340dff00172341 ┆4 #A refer to fig. 4.6.3.6-1. Invocation of delivering statistics (4a). Read the appropriate statistics information (4b) and copy it into 2 CIFs, as much as they can accomodate (4c). Send CIFs to printer process (4d) and await reply when next CIF s┆
0x34d00…34e00 (52, 0, 13) Sector 00005000172341 ┆ P #Ahall be created and sent (c). Request storage occupancy, from MHS (4f). ge description - Statistics collection - Statistics dump - Statistics generation - Statistics delivery 4.6.3.6.1 Statistics Collection The statistics collection i┆
0x34e00…34f00 (52, 0, 14) Sector 00000000000000 ┆ ┆
[…0x1…]
0x35000…35100 (53, 0, 0) Sector 3501ff00172341 ┆5 #Aameters by access to the Table in the shared data and updates the shared area at addresses specified in the Table (1b). During update and access of the shared data area, exclusive accesses is granted by requesting CSF. The STP collector returns to┆
0x35100…35200 (53, 0, 1) Sector 3502ff00172341 ┆5 #A the application (1c). When different applications request statistics, collection specific parameters are supplied. 4.6.3.5.2 Statistics Dump The statistics package is activated every 6 minutes to dump the collected data. The timing is contr┆
0x35200…35300 (53, 0, 2) Sector 3503ff00172341 ┆5 #Aolled by a request to the CROSFOX MPF System Function timer. The dump processing is (Refer fig. 4.6.3.6-1 for event numbers): Invocation of the Statistics Package by CROSFOX MPF System Functions (2a). Request to CROSFOX MPF System Function for e┆
0x35300…35400 (53, 0, 3) Sector 35047c00172341 ┆5 | #Axclusive access to the shared data area (2b). Dump the data area (2e) and (2d). Give up the exclusive access (2f). incoming log records are read by the LOG application and processed as follows: eceived. - appending temporary storage area to o┆
0x35400…35500 (53, 0, 4) Sector 3505ff00172341 ┆5 #A 1 If a system switch-over or restart has taken place the shared data area will be marked as invalid and the dump will generate a dummy dump. The dummy dump is a version of the shar┆
0x35500…35600 (53, 0, 5) Sector 3506ff00172341 ┆5 #Aed data area which does not contribute any informatin during generation of the statistics. 4.6.3.5.3 Statistics Generation The statistics package generates statistics is once per hour for the last hour. The processing is (refer to figure 4.6.┆
0x35600…35700 (53, 0, 6) Sector 3507ff00172341 ┆5 #A3.6-1): for event numbers): Invocation of generation part of statistics package (3a). Calculate from the dumped statistics, statistics for the last hour and output to statistics files (3c and 3f). Statistics are kept on an hourly basis for 24 h┆
0x35700…35800 (53, 0, 7) Sector 3408ff00172341 ┆4 #Aours, on a daily basis for 1 day and on a weekly basis for 4 weeks. 4.6.3.5.4 Statistics Delivery Statistics print is output by the terminal package. STP delivers the statistics information to TEP. The processing is (for event numbers, refer ┆
0x35800…35900 (53, 0, 8) Sector 35098200172341 ┆5 #A appended to a trace CIF. d) The trace CIF-ref is sent to tep via a queue element when the trace action is completed. esult shows not found, the request remains in the offline list if DTG is contained in the DTG interval of the succeeding volu┆
0x35900…35a00 (53, 0, 9) Sector 350aff00172341 ┆5 #A 1 4.6.3.5 Statistics Package (STP) This section describes the statistical functions under normal operation. The Statistics Package supports 4 functions outlined in the package de┆
0x35a00…35b00 (53, 0, 10) Sector 350bff00172341 ┆5 #Ascription: - Statistics collection - Statistics dump - Statistics generation - Statistics delivery 4.6.3.5.1 Statistics Collection The statistics collection is perfomed by the STP collection monitor procedure and statistics are stored i┆
0x35b00…35c00 (53, 0, 11) Sector 350cff00172341 ┆5 #An the shared data area. The collection procedures include: - Count increment - Add a number to a value - Boundary (minimum + maximum) - Cumulative time periods (i.e. how many percent on for a switch) The table is defined by the Statistics ┆
0x35c00…35d00 (53, 0, 12) Sector 350d9800172341 ┆5 #APackage in such a way that the processing by STP is defined by the table in conjunction with the parameters specified by the calling application. Time of File Window (TOF window) The retrieval keys used during automatic retrieval are: Action a┆
0x35d00…35e00 (53, 0, 13) Sector 350e8c00172341 ┆5 #A 1 Fig. 4.6.3.5-1 Statistics. equired. 4.6.3.3.3 Retrieval Catalogues The following catalogue structure or file structure is proposed: - ┆
0x35e00…35f00 (53, 0, 14) Sector 350fff00172341 ┆5 #A 1 The request for statistics is made by supplying: - Statistics group number - Statistics sub-group number - Statistics record number - Statistics parameter The group and numb┆
0x35f00…36000 (53, 0, 15) Sector 3500ff00172341 ┆5 #Aer are verified against the requestor. The events in the processing are (refer to fig. 4.6.3.6-1 for event numbers): Application calls Statistics Package (STP) with a request to generate statistics (1a). The STP collector checks the request par┆
0x36000…36100 (54, 0, 0) Sector 3601ff00172341 ┆6 #A 1 When correspondance has been obtained in one of the above mentioned three primary catalogues the corresponding main entry is found for check of remaining parameters. The primary c┆
0x36100…36200 (54, 0, 1) Sector 3602ff00172341 ┆6 #Aatalogues contain pointers to the main catalogue. 4.6.3.3.4 Retrieval Result The result of a retrieval request will be the first message found which fits the retrieval request keys. If no message fits the request keys, a not found completion re┆
0x36200…36300 (54, 0, 2) Sector 3603ff00172341 ┆6 #Aport will be returned as the result of the retrieval. 4.6.3.4 Log Package (LOG) 4.6.3.4.1 Functional Breakdown The functions implemented by LOG are separated in two groups: 1) Log collection functions 2) Log trace functions 4.6.3.4.1.┆
0x36300…36400 (54, 0, 3) Sector 3604cd00172341 ┆6 M #A1 Log Collection Function Log records, generated by the applications, are transferred to the incoming log queue. The incoming log records are read by the LOG application and processed as follows: eceived. - appending temporary storage area to o┆
0x36400…36500 (54, 0, 4) Sector 3605ff00172341 ┆6 #A 1 a) The log record buffer is read and stored in a log CIF. b) An acknowledgement is returned to the log record sender. c) Every 10 minutes, or on supervisors request, the pre┆
0x36500…36600 (54, 0, 5) Sector 3606ff00172341 ┆6 #Asent log CIF is closed and stored via SAR. d) The closed log CIF is sent to the supervisory log print queue for printout. Storage of log CIF's Every 10 minutes the presently used log CIF is stored and catalogued via SAR. A new log CIF is reque┆
0x36600…36700 (54, 0, 6) Sector 3607ff00172341 ┆6 #Asted from MMS. If no log records were appended to the log CIF, no action will be taken. 4.6.3.4.1.2 Log Trace Functions The stored log records may be retrieved with respect to specific trace keys and sent to supervisor's position via TEP. The ┆
0x36700…36800 (54, 0, 7) Sector 3508ff00172341 ┆5 #Afollowing functions are implemented by LOG when log records are retrieved: a) The trace command is received from TEP. b) The pertinent time interval is computed, and the CIF-refs. are retrieved via SAR. c) The wanted log records are traced and┆
0x36800…36900 (54, 0, 8) Sector 3609ff00172341 ┆6 #A 1 If offline retrieval is of type DTG-retrieval and the result shows not found, the request remains in the offline list if DTG is contained in the DTG interval of the succeeding volu┆
0x36900…36a00 (54, 0, 9) Sector 360aff00172341 ┆6 #Ame 4.6.3.3.1.4 Dump Dump performs the transfer of messages and transactions from on-line disk to the off-line disk. A report to supervisor's report printer will indicate that dump has been performed. 4.6.3.3.2 Retrieval Keys A primary l┆
0x36a00…36b00 (54, 0, 10) Sector 360bff00172341 ┆6 #Aist of retrieval keys used by the supervisor or message service position for retrieval of the previous stored messages are given below. The keys include security and access parameters used for directing the message to the right operator with the a┆
0x36b00…36c00 (54, 0, 11) Sector 360ceb00172341 ┆6 k #Allowed classification level. The primary key list is: 1) Internal serial number 2) Channel Identification Transmission sequence number Time of File (TOF) 3) Originating Station Routing Indicator Time of File (TOF) ff-line Retrieval .┆
0x36c00…36d00 (54, 0, 12) Sector 360dff00172341 ┆6 #A 1 4) Action Addressee (AO) Date Time Group (DTG) 5) Channel Identification Time of File Window (TOF window) The retrieval keys used during automatic retrieval are: Action a┆
0x36d00…36e00 (54, 0, 13) Sector 360eff00172341 ┆6 #Addresse (TO) Date time Group (DTG), which will be forwarded by the traffic handling package (THP) when an automatic retrieval is required. 4.6.3.3.3 Retrieval Catalogues The following catalogue structure or file structure is proposed: - ┆
0x36e00…36f00 (54, 0, 14) Sector 360fff00172341 ┆6 #AInternal Message Number (IMN) - Time of File (TOF) - Date Time Group (DTG) - Main Catalogue The DTG catalogue consists of 7, one day catalogues where the day cataloguqe including the DTG is searched first. If not found the next day's catalo┆
0x36f00…37000 (54, 0, 15) Sector 36005800172341 ┆6 X #Ague is searched until a fit is found or until DTG is out of DTG catalogue range. e and Retrieval Package (SAR) SAR is an application package, performing storage and retrieval of messages 4.6.3.3.1 Functional Specifications The main function┆
0x37000…37100 (55, 0, 0) Sector 3701ff00172341 ┆7 #As performed by SAR are: - storage of messages on-line - on-line retrieval of messages - off-line retrieval of messages - dump of messages to off-line disk - execution of supervisory commands. SAR consists of four subpackages each perform┆
0x37100…37200 (55, 0, 1) Sector 3702ff00172341 ┆7 #Aing one of the above mentioned functions. 4.6.3.3.1.1 Storage of Messages The storage of messages is performed by a STORE module, the store subpackage. Main functions performed by this module are: - waiting of storage requests in the incom┆
0x37200…37300 (55, 0, 2) Sector 37036c00172341 ┆7 l #Aing storage queue. - identification of message and pick up of retrieval key for temporary storage. Cr4IMM.:^=~ B}5I:g=~ J 5IC$3I > S C_* ┆
0x37300…37400 (55, 0, 3) Sector 3704ff00172341 ┆7 #A 1 - emptying of temporary storage when either a certain time interval has elapsed or a certain number of storage requests has been received. - appending temporary storage area to o┆
0x37400…37500 (55, 0, 4) Sector 3705ff00172341 ┆7 #An-line catalogue. - actual storage of message text by request to message management system (MMS). 4.6.3.3.1.2 Online Retrieval The on-line retrieval sub-package handles the retrieval of messages from the on-line disk. Retrieval requests are┆
0x37500…37600 (55, 0, 5) Sector 3706ff00172341 ┆7 #A received from the retrieval requests queue (RRQ) and treated in an FIFO manner. The retrieval requests are sorted according to TOC +DTG retrievals, TOC-window retrievals and OFFLINE retrievals, and they are inserted in corresponding lists. For o┆
0x37600…37700 (55, 0, 6) Sector 3707ff00172341 ┆7 #Anline DTG retrieval that results in a not found completion code. the request is inserted in the offline list if DTG is contained in DTG intervals for the offline volumes. The message corresponding to the retrieval keys is retrieved using MMS and i┆
0x37700…37800 (55, 0, 7) Sector 3608ef00172341 ┆6 o #As finally returned to requestor. 4.6.3.3.1.3 Off-line Retrieval Off-line retrieval requests are handled in the same manner as on-line retrievals. Mount requests for off-line disk are delivered to supervisor's report printer. ┆
0x37800…37900 (55, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(55,0, 9), len=0xff, h3=41172341}, f00=»1723A «, f01=»Crossfox Tilbud «, f02=»birgit «, f03=»RIM «, f04=»4.6.3.4-4.6.3.6.4 «, f05=19-02-82 09:10, f06=» 1 «, f07=»54 «, f08=» 11022 «, f09=05-03-82 19:32, f10=» «, f11=»02 «, f12=» 30 «, f13=05-03-82 19:39, f14=11-03-82 11:07, f15=»0126A «, f16=» 11 «, f17=» 2 «, f18=»57 «, f19=» 200 «, f20=» 13252 «, f21=» «, f22=» «, f99=400010000110066610110480aaca15050000000000000137033200df}
0x37900…37a00 (55, 0, 9) Sector 370a0b00172341 ┆7 #A 7 7 7 6 6 6 6 5 5 5 5 DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprere┆
0x37a00…37b00 (55, 0, 10) Sector 370bff00172341 ┆7 #A 1 TABLE OF CONTENTS 1 ┆
0x37b00…37c00 (55, 0, 11) Sector 370cff00172341 ┆7 #A 4.6.3.3 Storage and Retrieval Package (SAR) 4.6.3.3.1 Functional Specifications ..... 4.6.3.3.1.1 Storage of Messages ....... 4.6.3.3.1.2 Online Retrieval .......... 4.6.3.3.1.3 Off-line Retrieval .┆
0x37c00…37d00 (55, 0, 12) Sector 370dff00172341 ┆7 #A....... 4.6.3.3.1.4 Dump ...................... 4.6.3.3.2 Retrieval keys ................ 4.6.3.3.3 Retrieval Catalogues .......... 4.6.3.3.4 Retrieval Result .............. 4.6.3.4 Log Package ┆
0x37d00…37e00 (55, 0, 13) Sector 370eff00172341 ┆7 #A....................... 4.6.3.4.1 Functional Breakdown .......... 4.6.3.4.1.1 Log Collection Function ... 4.6.3.4.1.2 Log Trace Functions ....... 4.6.3.5 Statistics Package (STP) .......... 4.6.┆
0x37e00…37f00 (55, 0, 14) Sector 370fd100172341 ┆7 Q #A3.5.1 Statistics Collection ......... 4.6.3.5.2 Statistics Dump ............... 4.6.3.5.3 Statistics Generation .......... 4.6.3.5.4 Statistics Delivery ........... (= <q#p!"<6 !#<6 ! "$<!&<6$`i6 {M)(sM &M7 ┆
0x37f00…38000 (55, 0, 15) Sector 3700ff00172341 ┆7 #A 1 4.6.3.3 Storage and Retrieval Package (SAR) SAR is an application package, performing storage and retrieval of messages 4.6.3.3.1 Functional Specifications The main function┆
0x38000…38100 (56, 0, 0) Sector 3801ff00172941 ┆8 )Aes. r) To provide for the exchange of updating information between the controlling and stand-by MPF. 1.3.2 MCU Function The Message compilation Unit receives four serial data streams from four ship-to-shore access sites. The four data stream┆
0x38100…38200 (56, 0, 1) Sector 3802f400172941 ┆8 t )As are identical except for transmission errors and delay. A single message is compiled from the four data streams using a majority voting algorithm. This message is conveyed to the MPF through a KW-7 crypto. In addition, character an~ B}4C75! ┆
0x38200…38300 (56, 0, 2) Sector 00003900172941 ┆ 9 )Ad channel status are supplied directly to the MPF. b) To receive and analyze messages in ACP126 (modified) format from the Ship-to-Shore system and from the MRLS. c) To automatically translate messages received in ACP126 (modifi┆
0x38300…38400 (56, 0, 3) Sector 3804ff00172941 ┆8 )Aecial RI. m) Periodically to exchange accounting information with CROSS FOX ship users and shore users to protect against loss of traffic. n) To compile and periodically print out traffic statistics o) To be capable of handling at least 2000 i┆
0x38400…38500 (56, 0, 4) Sector 3805f500172941 ┆8 u )Ancoming and 2000 outgoing messages per day with an average length of 1500 characters each. p) To meet the user response time requirements for the cross-office handling time and the response time for command entry and message retrieval. MF and LF ┆
0x38500…38600 (56, 0, 5) Sector 3806ff00172941 ┆8 )A 1 q) To provide for future expansion. 30% increase in the future message traffic and 25% increase in the total number of local terminals and external communication lines. r) To pr┆
0x38600…38700 (56, 0, 6) Sector 38075400172941 ┆8 T )Aovide for the exchange of updating information between the controlling and staecurity relay of messages, management of communication channels, supervisory control of message traffic and message assembly. 1.3.1 MPF Functions Below is listed the┆
0x38700…38800 (56, 0, 7) Sector 00001000172941 ┆ )And-by MPF.lities and functions which will be provided by the MPF. a) To receive and analyze messages in ACP127 format from any of the communication channels. b) To receive and analyze messages in ACP126 (modified) format from the ship-to-shore s┆
0x38800…38900 (56, 0, 8) Sector 3809ff00172941 ┆8 )A 1 i) To produce a hard copy log record of all important system actions and terminal transactions for security, accounting, and recovery purposes. j) To provide capabilities for mes┆
0x38900…38a00 (56, 0, 9) Sector 380aff00172941 ┆8 )Asage delivery and message preparation at local terminals placed in the MCSF area (one terminal) and the MPF area (four terminals). An interactive dialog will assist the user in preparation of a message. k) To provide comprehensive supervisory and┆
0x38a00…38b00 (56, 0, 10) Sector 380bff00172941 ┆8 )A control facilities and a suitable engineering operator position for effective control and operation of the MPF including start up, recovery, and maintenance. l) To provide message service operator positions with appropriate facilities for message┆
0x38b00…38c00 (56, 0, 11) Sector 380cff00172941 ┆8 )A service and other functions, such as: o message retrieval o message servicing o maintenance of routing and address information o management of Ship-to-Shore channels o screening and vetting of messages destined for broadcast o rou┆
0x38c00…38d00 (56, 0, 12) Sector 380d9300172941 ┆8 )Ating assistance for messages when format translation cannot be fully effected o routing of messages for broadcast containing special RI. utomated interface between the NICS TARE and the CROSS FOX HF and LF radio telegraph systems. It will provi┆
0x38d00…38e00 (56, 0, 13) Sector 380eff00172941 ┆8 )A 1 m) to exchange accounting information periodically with CROSS FOX ship users and shore users to protect against loss of traffic. n) To compile and periodically print out traffic ┆
0x38e00…38f00 (56, 0, 14) Sector 380fff00172941 ┆8 )Astatistics. o) To be capable of handling at least 2000 incoming and 2000 outgoing messages per day with an average length of 1500 characters each. p) To meet the user response time requirements for the cross-office handling time and the response┆
0x38f00…39000 (56, 0, 15) Sector 3800ff00172941 ┆8 )A time requirements for command entry and message retrieval. q) To provide for future expansion; 30% increase in future message traffic and 25% increase in the total number of local terminals and external communication lines without hardware chang┆
0x39000…39100 (57, 0, 0) Sector 3901ff00172941 ┆9 )Arelay of messages, management of communication channels, supervisory control of message traffic and message assembly. 1.3.1 MPF Functions The main facilities and functions to be provided by the MPF are: a) To receive and analyze messages in ┆
0x39100…39200 (57, 0, 1) Sector 39023d00172941 ┆9 = )AACP127 format from any of the communication channels. =6A:g= RK4Cg4:^=~ BV4C75:g=~ Bf4 ZMo Ck4 KMo Mj ~ B 4:g=~ J 4Cq5M")IMy,M1' R 4 'M, CV4:g=~ Bg4M73~ B)4Cq5! ="(=*(=N#FMC 2.=M ':>=V V u:A=!>= AH1 R^4 ]M, C 4:>=2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x39200…39300 (57, 0, 2) Sector 3903ff00172941 ┆9 )A 1 b) To receive and analyze messages in ACP126 (modified) format from the Ship-to-Shore system and from the MRLS. c) To automatically translate messages received in ACP126 (modifi┆
0x39300…39400 (57, 0, 3) Sector 3904ff00172941 ┆9 )Aed) into ACP127 before relaying them (retransmission) to any of the communication systems. d) To process and route received messages based on address information in the message and in accordance with the rules and procedures laid down in ACP127 an┆
0x39400…39500 (57, 0, 4) Sector 3905ff00172941 ┆9 )Ad in the IFB. e) To transmit messages to ships via the Broadcast system and/or an MRL, to sites via the collocated NICS TARE and/or TRC, and/or to local users via directly connected terminals according to the routing information in each message. ┆
0x39500…39600 (57, 0, 5) Sector 3906ff00172941 ┆9 )A f) To make a reduced ACP126 to ACP127 conversion of messages received in ACP126 (modified) format, before relaying. This will apply to messages with RI's included in a supervisor specified list. The reduced conversion includes enveloping the ACP1┆
0x39600…39700 (57, 0, 6) Sector 3907ff00172941 ┆9 )A26 formatted message with an ACP127 header. g) To provide on-line message storage for 7 days of traffic and off-line storage for up to 30 days of message traffic with facilities for both on-line and off-line retrieval. h) To account for all mess┆
0x39700…39800 (57, 0, 7) Sector 3808a200172941 ┆8 " )Aages received and transmitted by producing log records for each incoming and outgoing message on a per channel basis. The log record will be printed out. ┆
0x39800…39900 (57, 0, 8) Sector 39093500173641 ┆9 5 6Atructure. It may also list directory entries. ious units of general CR80-software that are independent of the actual use of the CR80 (Crossfox-MPF), but used for software development, test, and diagnostics as well as for diagnostics of hardware. ┆
0x39900…39a00 (57, 0, 9) Sector 390aff00173641 ┆9 6A 1 c) Print Queue Rectification To check, rectify, or initialize the print queue. 4.6.4.1.3 Diagnostics Software The maintenance and Diagnostics (M&D) Package is a collection ┆
0x39a00…39b00 (57, 0, 10) Sector 390bff00173641 ┆9 6Aof standard test programs which are used to verify proper operation of the CR80 system and to detect and isolate faults in replaceable modules. The relevant programs of the off-line M&D software package are briefly mentioned in the following: * ┆
0x39b00…39c00 (57, 0, 11) Sector 390cff00173641 ┆9 6ACPU test program * CPU CACHE test program * Memory MAP test comprising - Memory MAP subtest - DMA subtest (Memory to Memory XFRS) - Interrupt subtest - V24 Communication Port subtest * RAM test program, comprising tests on all RAM module┆
0x39c00…39d00 (57, 0, 12) Sector 390dff00173641 ┆9 6As, namely: - Bus interface - RAM internal addressing circuitry - RAM storage circuitry * LTU tests (Line Termination Unit) * Disk system Test program, testing: - Disk controller - Disk controller adapter - Disk drive * Floppy Disk Tes┆
0x39d00…39e00 (57, 0, 13) Sector 390e1300173641 ┆9 6At Program b) General Text Formatter For margin justification, page headings, and underlining of key words. c) A program for merging of source files. 4.6.4.1.1.3 Development and Test ┆
0x39e00…39f00 (57, 0, 14) Sector 390fff00173641 ┆9 6A 1 4.6.4.2 Off-Line Package (OLP) The Off-Line Package is used for the generation and maintenance for Crossfox-MPF specific data. The data is created/updated off-line for subsequent ┆
0x39f00…3a000 (57, 0, 15) Sector 3400ff00173641 ┆4 6Aincorporation into the operational system. The OLP consists of the following subpackages: - Table Generator For addressing tables as well as user and terminal profiles. - VDU Format Generator For all formats required for the implementati┆
0x3a000…3a100 (58, 0, 0) Sector 3a01ab00173341 ┆: + 3Aent of the S/W failure rates in terms of Mean Time Between Detection of Software Defects (MDSD) shall be conducted using the STE as described in section 7.2.5.2. a unit, which may be withdrawn from operation as discussed above, shall not disrupt ┆
0x3a100…3a200 (58, 0, 1) Sector 3a02ff00173341 ┆: 3A 1 3.4.5 A&R Analysis The A&R analysis shall provide the figure for unit reliabilities to be used in availability calculations as presented in section 3.4.3. The method adapted fo┆
0x3a200…3a300 (58, 0, 2) Sector 00003600173341 ┆ 6 3Ar the analysis is discussed in section 7.2.5.1. disk error, provide the traffic accounting necessary to restore the information of not fully received messages and transactions and to reissue information not fully transmitted. Similar situations ma┆
0x3a300…3a400 (58, 0, 3) Sector 3a04a500173341 ┆: % 3Aarise in case of PU failure, which are solved in the same way (including switchover etc.). Refer section 4.6.2-6 for further discusson of the above subject. esents the reliability block diagram for the serving equipment specific for this case, the┆
0x3a400…3a500 (58, 0, 4) Sector 3a059b00173341 ┆: 3A 1 Fig. 3.4.3.6-1 Availability Block Diagram A. the LTUs shall cause failure of the groups, i.e. half of the external channels of one set. The eq┆
0x3a500…3a600 (58, 0, 5) Sector 3a069a00173341 ┆: 3A 1 Fig. 3.4.3.6-1 Availability Block Diagram B indicated in the diagram fig. 3.4.3.3-1 (diagram B) The key for dominating contribution to ther MTB┆
0x3a600…3a700 (58, 0, 6) Sector 3a07ce00173341 ┆: N 3A 1 Table 3.4.3.6-1 Availability of the Minimum Operational Configuration for Supervisor Position. discussio in section 3.4.3.1. Refer table 3.4.┆
0x3a700…3a800 (58, 0, 7) Sector 3908ce00173341 ┆9 N 3A 1 Table 3.4.3.6-2 Availability of the Minimum Operational Configuration for User Position (MCSF) MTBF and MTTR. Refer to ltable 3.4.3.3-1 for p┆
0x3a800…3a900 (58, 0, 8) Sector 3a09cf00173341 ┆: O 3A 1 Table 3.4.3.6-3 Availability of the Minimum Operational Configuratin for External Channel Group. Table 3.4.3-1 . The FAN in diagram A┆
0x3a900…3aa00 (58, 0, 9) Sector 3a0aff00173341 ┆: 3A 1 3.4.3.7 Specific MTBF and Downtime Requirements It is important to note that the downtime specified here is different from the MTTR, which is the downtime per failure. The downt┆
0x3aa00…3ab00 (58, 0, 10) Sector 3a0bff00173341 ┆: 3Aime specified in this requirement is the accumulated downtime over a certain period. The following specific requirements for MTBF and downtime have been stated in the IFB. The compliance is described for each case. - MPF central processor MTBF ┆
0x3ab00…3ac00 (58, 0, 11) Sector 3a0cff00173341 ┆: 3Ashall be at least 10,000 hours. The downtime shall not exceed 8 hours per year. The MPF central Processor corresponds to the case discussed in section 3.4.3.1. The MTBF is found from the following formula (refer section 3.4.1): MTTR/MTBF ┆
0x3ac00…3ad00 (58, 0, 12) Sector 3a0d4c00173341 ┆: L 3A1-A = 11 x 10 -6 . The availability is found from table 3.4.3.1-1. m operational configurations, the corresponding avaiability being calculated in table 3.4.3.6-1 to -3 The system is brought back to a fully configured state from the engineering┆
0x3ad00…3ae00 (58, 0, 13) Sector 3a0eff00173341 ┆: 3A 1 Since the MTTR is never less than 1/2 hour (redundant units) the result is: MTBF = 45,450 hours. Since the MTTR per failure does not exceed 1 hour and the MTBF is much more th┆
0x3ae00…3af00 (58, 0, 14) Sector 3a0fff00173341 ┆: 3Aan 1 year the downtime requirement is fulfileld as well. - the PRINTERS shall have a MTBF of at least 3000 hours and the downtime shall not exceed 30 minutes per month. These figures will be fulfilled. - The VDUs shall have a MTBF of at least ┆
0x3af00…3b000 (58, 0, 15) Sector 3a00ff00173341 ┆: 3A5000 hours and the downtime shall not exceed 30 minutes per month. These figures will be fulfilled. 3.4.4 STE and S/W Failure Rates Sectin 7.2.4 presents the STE. The S/W defects will be monitored as part of the A&R program plan. Assessm┆
0x3b000…3b100 (59, 0, 0) Sector 3b01ff00173341 ┆; 3A 1 The system is designed in such a manner (S/W and H/W) that the occurence of a single failure in a unit, which may be withdrawn from operation as discussed above, shall not disrupt ┆
0x3b100…3b200 (59, 0, 1) Sector 3b02ff00173341 ┆; 3Afurther operation. Degraded performance under high traffic conditions may be experienced if one mirrored disk is withdrawn from operation. B means of control via SS&C, however, it is possible to configure the external channel connections to adjus┆
0x3b200…3b300 (59, 0, 2) Sector 3b03ff00173341 ┆; 3At the traffic load. The S/W will, in case of a disk error, provide the traffic accounting necessary to restore the information of not fully received messages and transactions and to reissue information not fully transmitted. Similar situations ma┆
0x3b300…3b400 (59, 0, 3) Sector 3b04ab00173341 ┆; + 3Ay arise in case of PU failure, which are solved in the same way (including switchover, etc.). Refer to section 4.6.2-6 for further discusson of the above subject. nts the reliability block diagram for the equipment specific for this case, the gene┆
0x3b400…3b500 (59, 0, 4) Sector 3b059b00173341 ┆; 3A 1 Fig. 3.4.3.6-1 Availability Block Diagram A. ause failure of the groups, i.e. half of the external channels of one set (refer to the discussion i┆
0x3b500…3b600 (59, 0, 5) Sector 3b069a00173341 ┆; 3A 1 Fig. 3.4.3.6-1 Availability Block Diagram B indicated in the diagram fig. 3.4.3.3-1 (diagram B). The key dominating contribution to the MTBF i┆
0x3b600…3b700 (59, 0, 6) Sector 3b07ce00173341 ┆; N 3A 1 Table 3.4.3.6-1 Availability of the Minimum Operational Configuration for Supervisor Position. 0.99994. This requirement - which is stronger th┆
0x3b700…3b800 (59, 0, 7) Sector 3a08ce00173341 ┆: N 3A 1 Table 3.4.3.6-2 Availability of the Minimum Operational Configuration for User Position (MCSF) TBF and MTTR, namely 0.9998. Refer to table 3.4┆
0x3b800…3b900 (59, 0, 8) Sector 3b099700173341 ┆; 3A 1 Fig. 3.4.3.5-1 Reliable Block Diagram B V24 500.000 2 OMD 500.000 2 Table 3.4.3-1 . The FAN in diagram A┆
0x3b900…3ba00 (59, 0, 9) Sector 3b0ac000173341 ┆; @ 3A 1 Table 3.4.3.5-1 Availability for Equipment Serving Groups of External Channels. ncerning single failures and the role of the SS&C have been dis┆
0x3ba00…3bb00 (59, 0, 10) Sector 3b0bff00173341 ┆; 3A 1 3.4.3.6 Degraded Modes & System Degradation The system may be brought in a degraded mode for the following reasons: - repair as a result of failure, i.e. replacement of modules┆
0x3bb00…3bc00 (59, 0, 11) Sector 3b0cff00173341 ┆; 3A - test of part of the equipment during diagnostic phases - parts of equipment are made unoperational for maintenance purposes - test of new s/w using parts of the equipment - training and exercises using part of the equipment. Fig. 3.4.3.┆
0x3bc00…3bd00 (59, 0, 12) Sector 3b0dff00173341 ┆; 3A6-1 and -2 present the reliability block diagram for one of the minimum operational configurations, the corresponding avaiability being calculated in table 3.4.3.6-1 to -3 The system is brought back to a fully configured state from the engineering┆
0x3bd00…3be00 (59, 0, 13) Sector 3b0eff00173341 ┆; 3A position at the SS&C, (refer to section 4.6.2.6 for a further description). Redundant items which are temporarely taken out of operation but still fully serviceable if used may be brought back into operation within 5 minutes. An even more degra┆
0x3be00…3bf00 (59, 0, 14) Sector 3b0fff00173341 ┆; 3Aded configuration may exist where the SS&C control is without the Watchdog: In this case the engineering position VDU is connected directly to the MAP of the PU. It is seen that the system despite the degradation of configuration has all the units┆
0x3bf00…3c000 (59, 0, 15) Sector 3b002900173341 ┆; ) 3A necessary for normal operations. Table 3.4.3.4-1 Availability for Equipment serving individual External Channels. namely 0.99994. This requirement is met . Table 3.4.3.1-1 Av┆
0x3c000…3c100 (60, 0, 0) Sector 3c01ff00173341 ┆< 3A 1 3.4.3.5 Equipment Serving Groups of External Channels The requirements are: - it shall be possible to divide the outgoing and incoming external channels into at least two group┆
0x3c100…3c200 (60, 0, 1) Sector 3c02ff00173341 ┆< 3As so that no single failure shall cause the loss of more than one such group. - the availability of the equipment serving any group shall be at least 0.9999 - the MTBF of the equipment serving any group shall be at least 1 year with an MTTR not ┆
0x3c200…3c300 (60, 0, 2) Sector 3c03ff00173341 ┆< 3Ato exceed 1 hour. Fig. 3.4.2-5 displays the solution to the first requirement: Any of the following sets of external channels - Broadcast, TRC plus MRL, and S/S with the corresponding monitor lines to the MCUs, have been divided into two groups. ┆
0x3c300…3c400 (60, 0, 3) Sector 3c04ff00173341 ┆< 3A A single failure (say in a LTU) may result in the loss of only half of the channels for only one of the above groups of channels. Fig. 3.4.3.5-1 (diagram B) presents the reliability block diagram for the equipment specific for this case, the gene┆
0x3c400…3c500 (60, 0, 4) Sector 3c05ff00173341 ┆< 3Aral equipment being presented in fig. 3.4.2-6A (diagram A). From diagram B it is deducted that no single failure above the level of the LTUs shall cause failure of the groups, i.e. half of the external channels of one set (refer to the discussion i┆
0x3c500…3c600 (60, 0, 5) Sector 3c066900173341 ┆< i 3An section 3.4.2). The equipment serving a group of external channels is indicated in diagram B. ock diagram A of section 3.4.2 plus the equipment indicated in the diagram fig. 3.4.3.3-1 (diagram B). The key dominating contribution to the MTBF i┆
0x3c600…3c700 (60, 0, 6) Sector 3c07ff00173341 ┆< 3A 1 The fulfilment of the specific requirements for MTBF and MTTR is with a minimum MTTR of 1/2 hour, equivalent to an availability of 0.99994. This requirement - which is stronger th┆
0x3c700…3c800 (60, 0, 7) Sector 3b088800173341 ┆; 3Aan the availability requirement - is met. Refer to table 3.4.3.5-1 for proof of the fulfilment of the availability requirement. ting from calculating the availability based on the requirements for MTBF and MTTR, namely 0.9998. Refer to table 3.4┆
0x3c800…3c900 (60, 0, 8) Sector 3c094e00173341 ┆< N 3A.3.3-1 for proof of the fulfilment of the requirement for availability. DUAL 36.9 36.9 CR8082M/010--/00 LIA-N 10,000,000 01 V24 500.000 2 OMD 500.000 2 Table 3.4.3-1 . The FAN in diagram A┆
0x3c900…3ca00 (60, 0, 9) Sector 3c0a9900173341 ┆< 3A 1 Fig. 3.4.3.3-1 Reliability Block Diagram B Connecting Points The requirements concerning single failures and the role of the SS&C have been dis┆
0x3ca00…3cb00 (60, 0, 10) Sector 3c0bba00173341 ┆< : 3A 1 Table 3.4.3.3-1 Availability for Equipment Serving user connecting points. ubsystem downtime or MTTR is of course less than the largest MTTR of ┆
0x3cb00…3cc00 (60, 0, 11) Sector 3c0cff00173341 ┆< 3A 1 3.4.3.4 Equipment Serving Individual External Channels The requirements are - availability shall be at least 0.9995 - The MTBF shall be at least 3 months with a MTTR not to e┆
0x3cc00…3cd00 (60, 0, 12) Sector 3c0dff00173341 ┆< 3Axceed 40 minutes. The equipment configuration in question is presented as the reliability block diagram A of section 3.4.2 plus the equipment indicated in the diagram fig. 3.4.3.4-1 (diagram B). Concerning the specific requirements for MTBF and ┆
0x3cd00…3ce00 (60, 0, 13) Sector 3c0ed200173341 ┆< R 3Afor MTTR the same remarks as in section 3.4.3.3 shall apply. The requirement for availability is again 0.9998. Refer to table 3.4.3.4-1 for proof of the fulfilment of the requirement for availability. - availability shall be at least 0.9999 ┆
0x3ce00…3cf00 (60, 0, 14) Sector 3c0f9a00173341 ┆< 3A 1 Fig. 3.4.3.4-1 Reliability Block Diagram B. s presenting all the reliability units of the main configuration items, refer fig. 3.4.2-2 to 3.4.2-5┆
0x3cf00…3d000 (60, 0, 15) Sector 3c00c000173341 ┆< @ 3A 1 Table 3.4.3.4-1 Availability for Equipment serving individual External Channels. namely 0.99994. This requirement is met . Table 3.4.3.1-1 Av┆
0x3d000…3d100 (61, 0, 0) Sector 3d01ff00173341 ┆= 3Aailability of Equipment Serving all External Channels and Local Terminal Connecting Points. Table 3.4.3.1-2 Availability of Equipment Serving all External Channels and Local Terminal Connecting Points. The equipment configuration in question is ┆
0x3d100…3d200 (61, 0, 1) Sector 3d02da00173341 ┆= Z 3Apresented as the reliability block diagram A of section 3.4.2 plus the equipment indicated in the diagram fig. 3.4.3.2-1 (diagram B) Table 3.4.3.2-1 proves the fulfilment of the requirement for availability. reliability configurations to be cons┆
0x3d200…3d300 (61, 0, 2) Sector 3d039900173341 ┆= 3A 1 Fig. 3.4.3.2-1 Reliability Block Diagram B. ctio 3.4.1 for D x 1 and with the assumption of section 3.4.2: D = 1 (MTTR = 1 hour) for all unit┆
0x3d300…3d400 (61, 0, 3) Sector 3d04c400173341 ┆= D 3A 1 Table 3.4.3.2-1 Availability for Equipment Serving Supervisory and Service Positions. value is equal to the value for the single units. All ┆
0x3d400…3d500 (61, 0, 4) Sector 3d05ff00173341 ┆= 3A 1 3.4.3.3 Equipment Serving Individual User Connecting Point The requirements are: - availability shall be at least 0.9995 - the MTBF shall be at least 3 months with a MTTR not┆
0x3d500…3d600 (61, 0, 5) Sector 3d06ff00173341 ┆= 3A to exceed 40 minutes. The equipment configuration in question is presented as the reliability block diagram A of section 3.4.2 plus the equipment indicated in the diagram fig. 3.4.3.3-1 (diagram B). The key dominating contribution to the MTBF i┆
0x3d600…3d700 (61, 0, 6) Sector 3d07ff00173341 ┆= 3As seen to be the units the diagram B. As alredy mentioned in section 3.4.1 the assumption of an MTTR of 1 hour is due to conservative assumption: The equipment supporting the user connecting point in diagram B will be replaceable within 40 minutes┆
0x3d700…3d800 (61, 0, 7) Sector 3c08ff00173341 ┆< 3A. Also in this case, with a MTTR of 1/2 hour, it is found that the availability requirement is harder to meet than the one resulting from calculating the availability based on the requirements for MTBF and MTTR, namely 0.9998. Refer to table 3.4┆
0x3d800…3d900 (61, 0, 8) Sector 3d09e700173341 ┆= g 3AR8400/--- DISK DRIVE, SMD 40-400 MB 4000 250 CR8086M/010AB/00 LTU, DUAL 36.9 36.9 CR8082M/010--/00 LIA-N 10,000,000 01 V24 500.000 2 OMD 500.000 2 Table 3.4.3-1 . The FAN in diagram A┆
0x3d900…3da00 (61, 0, 9) Sector 3d0aff00173341 ┆= 3A 1 3.4.3.1 Equipment Serving all External Circuits, Channels and Local Terminal Connecting Points The requirements concerning single failures and the role of the SS&C have been dis┆
0x3da00…3db00 (61, 0, 10) Sector 3d0bff00173341 ┆= 3Acussed in section 3.4.2. Further requirements are: - the availability shall be at least 0.99995 - the MTBF shall be at least 2 years with a MTTR not to exceed 1 hour. The subsystem downtime or MTTR is of course less than the largest MTTR of ┆
0x3db00…3dc00 (61, 0, 11) Sector 3d0cff00173341 ┆= 3Aany unit, i.e. it is less than one. By assuming an MTTR of 1 hour and an MTRF of 2 years the availability requirement is 0.99994, which is a less strong requirement than the first requirement calling for 0.99995. The lower limit for the MTTR is ┆
0x3dc00…3dd00 (61, 0, 12) Sector 3d0dff00173341 ┆= 3A1/2 hour for redundant units each with an MTTR of 1 hour. In this case the availability requirement is 0.99997 and this is now the stronger requirement. This requirement is met. The equipment configuration in question is presented as the reliabi┆
0x3dd00…3de00 (61, 0, 13) Sector 3d0eff00173341 ┆= 3Ality block diagram A of section 3.4.2. Refer to the tables 3.4.3.1-1 and 3.4.3.1-2 for the availability calculations. 3.4.3.2 Equipment Serving Supervisory and Service Position The requirements are: - availability shall be at least 0.9999 ┆
0x3de00…3df00 (61, 0, 14) Sector 3d0f4c00173341 ┆= L 3A- the MTBF shall be at least 1 year with an MTTR not to exceed 1 hour Fig. 3.4.2-4 I/O Bus 2. - overview diagrams presenting all the reliability units of the main configuration items, refer fig. 3.4.2-2 to 3.4.2-5┆
0x3df00…3e000 (61, 0, 15) Sector 3d00ff00173341 ┆= 3A 1 As in section 3.4.3.2 it is found that the availability requirement corresponding to MTTR = 1/2 hour is the stronger namely 0.99994. This requirement is met . Table 3.4.3.1-1 Av┆
0x3e000…3e100 (62, 0, 0) Sector 3e019a00173341 ┆> 3A 1 Fig. 3.4.2-6A Reliability Block Diagram A. ptors in the crates (the CCAs), have not been shown in the above diagrams in order to simplify the ov┆
0x3e100…3e200 (62, 0, 1) Sector 3e029900173341 ┆> 3A 1 Fig. 3.4.2-6B Reliability Block diagram B. 3.4.2-6 A&B: Diagram A presents the units which support all the reliability configurations to be cons┆
0x3e200…3e300 (62, 0, 2) Sector 3e03ff00173341 ┆> 3A 1 3.4.3 A&R Calculations The calculations shall be based on the formulas of sectio 3.4.1 for D x 1 and with the assumption of section 3.4.2: D = 1 (MTTR = 1 hour) for all unit┆
0x3e300…3e400 (62, 0, 3) Sector 3e04ff00173341 ┆> 3As. The results may then be presented in a clear and simple form (refer table 3.4.3.1-1): In cases of series with redundant (always 1 of 2 redundancy) units and non-redundant items, the s value is equal to the value for the single units. All ┆
0x3e400…3e500 (62, 0, 4) Sector 3e058a00173341 ┆> 3A values are in units of FPM = failure per million. The reliability figures used in the calculations are listed in table 3.4.3-1. ram A , this equipment forming the subsystem which supports all other configurations. A single error whereby a single┆
0x3e500…3e600 (62, 0, 5) Sector 3e06ff00173341 ┆> 3A 1 ITEM MTBF (Hours) FPM. SS&C WD SUBSYSTEM 7782 128.5 CR8087MM/010--/00 SFA 10,000,000 0.1 CR8047M/010A-/00 FLOP CTRL 59500 16.8 REQUIRED VDU 5000 200 REQUIRED┆
0x3e600…3e700 (62, 0, 6) Sector 3e07ff00173341 ┆> 3A PRINTER 3000 333 CR8050M/-----/00POWER SUPPLY 26800 37.3 CR8106M/220--/00 MAINS FILTER & DIST. 600.000 1.6 CR8105M/020--/00 FAN 5000.000 20.0 CR8089M/----/00 CCA 29674 33.7 CR8055M/010PC/00 MBT 286000 3.5 CR8071M/010--/00 M1A ┆
0x3e700…3e800 (62, 0, 7) Sector 3d08ff00173341 ┆= 3A 85500 11.7 CR802OM/000PC/00 MAP 19400 51.6 CR8016M/128PC/00 RAM, 128 K 17000 58.8 CR8003M/040PC/00 CPU+CACHE 26100 38.3 CR8081M/010--/00 CIA 71400 14.0 CR8044M/040AB/00 DISK CTRL 32200 33.1 CR8084M/010--/00 DCA 46900 21.3 C┆
0x3e800…3e900 (62, 0, 8) Sector 3e09ff00173341 ┆> 3Any part of the rest of the system, which is the D value for the total configuration in question including VDUs and printers. For ease of calculation the worst case value including all equipment, will be used in all cases. The FAN in diagram A┆
0x3e900…3ea00 (62, 0, 9) Sector 3e0aff00173341 ┆> 3A (in I/O Bus) is not a single unit; actually it is composed of 8 fans in a cluster and the corresponding high reliability is reflected in the MTBF used for the calculations. The off-line disk does not contribute to the disk redundancy and is thus ┆
0x3ea00…3eb00 (62, 0, 10) Sector 3e0b2f00173341 ┆> / 3Anot included in the reliability diagram. - repair will be limited to simple replacement of units; it is assumed that spares are available fully adjusted for insertion (refer sections 6.4 and 6.5 for Maintenance and Spare┆
0x3eb00…3ec00 (62, 0, 11) Sector 3e0c8d00173341 ┆> 3A 1 Fig. 3.4.2-1 System Overview. on the availability calculated here. - Environmental conditions outside the control of the equipment manufactur┆
0x3ec00…3ed00 (62, 0, 12) Sector 3e0d8c00173341 ┆> 3A 1 Fig. 3.4.2-2 Processor Unit d to be 1 hour in all calculations; this is a conservative assumption which has been introduced partly for safety a┆
0x3ed00…3ee00 (62, 0, 13) Sector 3e0e8800173341 ┆> 3A 1 Fig. 3.4.2-3. I/O Bus 1. han 6 hours more than once a year is hereby fulfilled. 3.4.2 A&R Models The presentation of the models will includ┆
0x3ee00…3ef00 (62, 0, 14) Sector 3e0f8700173341 ┆> 3A 1 Fig. 3.4.2-4 I/O Bus 2. - overview diagrams presenting all the reliability units of the main configuration items, refer fig. 3.4.2-2 to 3.4.2-5┆
0x3ef00…3f000 (62, 0, 15) Sector 3e009a00173341 ┆> 3A 1 Fig. 3.4.2-5 Types of LTUs and Connections. ┆
0x3f000…3f100 (63, 0, 0) Sector 3f01ff00173341 ┆? 3A 1 The Watchdog Monitor and Control Bus (the Crate Configuration Bus), and the adaptors in the crates (the CCAs), have not been shown in the above diagrams in order to simplify the ov┆
0x3f100…3f200 (63, 0, 1) Sector 3f02ff00173341 ┆? 3Aerview. The corresponding units have been shown in the reliability block diagrams, however. Reliability block diagrams. 2 diagrams exist, fig. 3.4.2-6 A&B: Diagram A presents the units which support all the reliability configurations to be cons┆
0x3f200…3f300 (63, 0, 2) Sector 3f03ff00173341 ┆? 3Aidered, and Diagram B, dedicated to the units out of which only a subset shall be considered in each reliability configuration. Diagram B shall be used in different versions to indicate the exact configuration in each case. In subsection 3.4.3 ea┆
0x3f300…3f400 (63, 0, 3) Sector 3f04ff00173341 ┆? 3Ach of the reliability cases from the IFB has been considered separately, first considering case corresponding to diagram A, which forms the basis for the other cases. Special consideration will be given to the following requirement, however: No s┆
0x3f400…3f500 (63, 0, 4) Sector 3f05ff00173341 ┆? 3Aingle failure shall cause a total subssystem failure. Such a failure may not happen within the configuration corresponding to diagram A , this equipment forming the subsystem which supports all other configurations. A single error whereby a single┆
0x3f500…3f600 (63, 0, 5) Sector 3f06ff00173341 ┆? 3A user connection or external channel is lost is, provided the availability figures are otherwise sufficient, not included in this requirement. In this connection the SS&C unit is of special interest, this apparently being the only unit which is no┆
0x3f600…3f700 (63, 0, 6) Sector 3f07dc00173341 ┆? \ 3At redundant. However, the SS&C, including the watchdog with VDU, printer and floppy disk, only has to be working in case of a failure in the rest of the system, i.e. at least two errors are needed for a failure. Hence ┆
0x3f700…3f800 (63, 0, 7) Sector 3e08ff00173341 ┆> 3A 1 The availability contribution from the SS&C, or rather unavailability contribution, expressed as Ds s is given as the value D of the SS&C times the probability of a failure in a┆
0x3f800…3f900 (63, 0, 8) Sector 3f09ff00173341 ┆? 3And multiplication of terms D . It is seen that the downtime and uptime within the approximation D s 1 which shall always hold for these calculations, will never have to be known separately except in case of the basic units. e) Assumptions┆
0x3f900…3fa00 (63, 0, 9) Sector 3f0ae700173341 ┆? g 3A The following assumptions will apply for the availability calculations: - The stand-by MC will not contribute to the availability - preventive maintenance will be limited to a minimum (cleaning of air filters, etc.). ed according to the modu┆
0x3fa00…3fb00 (63, 0, 10) Sector 3f0bff00173341 ┆? 3A 1 - repair will be limited to simple replacement of units; it is assumed that spares are available fully adjusted for insertion (refer sections 6.4 and 6.5 for Maintenance and Spare┆
0x3fb00…3fc00 (63, 0, 11) Sector 3f0cff00173341 ┆? 3A Parts). - Power sources are assumed available at the sites (with the quality as defined in section 6.1.10 e) and will have no impact on the availability calculated here. - Environmental conditions outside the control of the equipment manufactur┆
0x3fc00…3fd00 (63, 0, 12) Sector 3f0dff00173341 ┆? 3Aer shall not be considered: Fire, fload, explosion, etc. Refer section 3.2 for environmental conditions. - the Unit MTTR is assumed to be 1 hour in all calculations; this is a conservative assumption which has been introduced partly for safety a┆
0x3fd00…3fe00 (63, 0, 13) Sector 3f0eff00173341 ┆? 3And partly for ease of calculations. The requirement for no equipment being without the planned degree of redundancy for longer than 6 hours more than once a year is hereby fulfilled. 3.4.2 A&R Models The presentation of the models will includ┆
0x3fe00…3ff00 (63, 0, 14) Sector 3f0fff00173341 ┆? 3Ae the folowing components. - overview diagram presenting the main configuration items of the total system, refer fig. 3.4.2-1 - overview diagrams presenting all the reliability units of the main configuration items, refer fig. 3.4.2-2 to 3.4.2-5┆
0x3ff00…40000 (63, 0, 15) Sector 3f000900173341 ┆? 3A. N ┆
0x40000…40100 (64, 0, 0) Sector 4001ff00173341 ┆@ 3A A = A =1 z i ┆
0x40100…40200 (64, 0, 1) Sector 4002ff00173341 ┆@ 3A For Ds/Us 1 (D/U 1) : N ┆
0x40200…40300 (64, 0, 2) Sector 4003ff00173341 ┆@ 3A N A (1-Ds s) 1 - Ds s i=1 i=1 ┆
0x40300…40400 (64, 0, 3) Sector 4004ff00173341 ┆@ 3A 1 The following usage of the availability definition is useful in applying the derived result as the availability for a subsystem in further calculations: H ┆
0x40400…40500 (64, 0, 4) Sector 4005ff00173341 ┆@ 3A u A = ┆
0x40500…40600 (64, 0, 5) Sector 4006ff00173341 ┆@ 3A U+D For D/U 1 : A 1 - D/U = 1 ┆
0x40600…40700 (64, 0, 6) Sector 4007ff00173341 ┆@ 3A- D N Hence ┆
0x40700…40800 (64, 0, 7) Sector 3f08ff00173341 ┆? 3AD = Ds s. i=1 1 Consequently all calculations may be performed by summation a┆
0x40800…40900 (64, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(64,0, 9), len=0xff, h3=41172241}, f00=»1722A «, f01=»Crossfox Tilbud «, f02=»birgit «, f03=»RIM «, f04=»4.6.3.3 - 4.6.3.3.4 «, f05=19-02-82 09:04, f06=» 1 «, f07=»00 «, f08=» 7161 «, f09=05-03-82 19:24, f10=» «, f11=»02 «, f12=» 46 «, f13=04-03-82 20:01, f14=11-03-82 11:07, f15=»0126A «, f16=» 9 «, f17=» 1 «, f18=»43 «, f19=» 128 «, f20=» 8686 «, f21=» «, f22=» «, f99=020010000110062710110380aa8a37040000000000000137032400df}
0x40900…40a00 (64, 0, 9) Sector 400a0900172241 ┆@ "A @ @ 3 3 3 3 3 2 * DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet ┆
0x40a00…40b00 (64, 0, 10) Sector 400bff00172241 ┆@ "A 1 TABLE OF CONTENTS 1 4.6.3.2 Terminal P┆
0x40b00…40c00 (64, 0, 11) Sector 400cf000172241 ┆@ p "Aackage ................. 4.6.3.2.1 Supervisor VDU Functions ..... 4.6.3.2.2 MSO Function ................. 4.6.3.2.3 Printer Function ............. 4.6.3.2.4 MCSF User Function ........... *:=k 0wM% !;=4C┆
0x40c00…40d00 (64, 0, 12) Sector 400dff00172241 ┆@ "A 1 4.6.3.2 Terminal Package The terminal package constitutes the operator interface to the CROSSFOX system and consists of 4 sub-packages that provides a fully compliant high level o┆
0x40d00…40e00 (64, 0, 13) Sector 400eff00172241 ┆@ "Aperator interface using menu selection and form-filling-out procedures. Corresponding parts of the man-machine interface (MMI) are identical with the CAMPS MNI, where possible. The sub-packages are: - Supervisor VDU Package (SUP) - Message Ser┆
0x40e00…40f00 (64, 0, 14) Sector 400fff00172241 ┆@ "Avice Operation Package (MSOP) - Printer Package - VDU User Package (VUP) 4.6.3.2.1 Supervisor VDU Functions The Supervisor VDU Package (SUP) contains the software to support the three main supervisor functions as shown on Figure 4.6.3.2.1-1. ┆
0x40f00…41000 (64, 0, 15) Sector 3308e200172241 ┆3 b "A System Control (SYSC) Message Handling (MSGH) Supervisor Engineering Functions (SENF) The System Control Functions: Device Control Addressing Scheme Control User Profile Update Queue Control Report Control /2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x41000…41100 (65, 0, 0) Sector 41017000172841 ┆A p (Athe file-system. - File Management System (FMS), handles the different files allocated to the system. 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 ! ┆
0x41100…41200 (65, 0, 1) Sector 4102ff00172841 ┆A (A 1 - Message Management System (MMS), performs the message handling, i.e. create, modify, append, read, deletion, etc. of messages. - Crossfox System Function (CSF), performs a nu┆
0x41200…41300 (65, 0, 2) Sector 41034500172841 ┆A E (Amber of user functions that require execution at system level. BL5C`5M{) RV5Cq5M . R`5Cq5M@1MI1:h= Rp5Cr4IMM.:^=~ B}5I:g=~ J 5IC$3I > S C_* ┆
0x41300…41400 (65, 0, 3) Sector 41047200172841 ┆A r (A 1 Her inds`ttes tegning 4.6.1-1 ss (2f). incoming log records are read by the LOG application and processed as follows: eceived. - appending temporary storage area to o┆
0x41400…41500 (65, 0, 4) Sector 41057100172841 ┆A q (A 1 Her inds`ttes tegning 4.6.1-2 taken place the shared data area will be marked as invalid and the dump will generate a dummy dump. The dummy dump is a version of the shar┆
0x41500…41600 (65, 0, 5) Sector 4106ff00172841 ┆A (A 1 - System Status and Control (SSC), handles the supervision of the system and the alternative MC communication. - Table Management (TMP), contains all tables related to the syst┆
0x41600…41700 (65, 0, 6) Sector 4107ff00172841 ┆A (Aem and handles all table updates performed by supervisor. The system software is further described in section 4.6.2. b) Application Software The application software handles the special functions related to the specific CROSSFOX MPF requirem┆
0x41700…41800 (65, 0, 7) Sector 0c00ff00172841 ┆ (Aents. The application software includes: - Traffic Handling Package (THP), receives the external traffic and performs conversion, analysis, and distribution. Further, THP handles the messages for transmission. - Logging Package (LOG), perform┆
0x41800…41900 (65, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(65,0, 9), len=0xff, h3=41172841}, f00=»1728A «, f01=»Cross fox tilbud «, f02=»kk «, f03=»RIM «, f04=»4.6.1 «, f05=19-02-82 12:38, f06=» «, f07=»06 «, f08=» 875 «, f09=02-03-82 14:18, f10=» «, f11=»10 «, f12=» 126 «, f13=03-03-81 10:44, f14=11-03-82 11:07, f15=»0126A «, f16=» 7 «, f17=» «, f18=»39 «, f19=» 56 «, f20=» 2338 «, f21=» «, f22=» «, f99=020010000110062710110380aa8a37040000000000000137031500df}
0x41900…41a00 (65, 0, 9) Sector 410a0700172841 ┆A (A A A A A A A ┆
0x41a00…41b00 (65, 0, 10) Sector 410bff00172841 ┆A (A 1 TABLE OF CONTENTS 1 4.6 Software Specificati┆
0x41b00…41c00 (65, 0, 11) Sector 410c5700172841 ┆A W (Aon .................. 4.6.1 Software Configuration ............... Cp.:]=~ Bp.MP- Rm.> IM)-MI,:^=~ B~.> IMB'IM2& 9x2"<!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┆
0x41c00…41d00 (65, 0, 12) Sector 410dff00172841 ┆A (A 1 4.6 SOFTWARE SPECIFICATION 4.6.1 Software Configuration The MPF software system will, to a high degree, be based on CAMPS software, presently being developed for NATO. The hig┆
0x41d00…41e00 (65, 0, 13) Sector 410eff00172841 ┆A (Ah commonality with CAMPS software will reduce software maintenance costs and reduced life time costs for NATO. The MPF software system is composed of three subsystems: - System software - Application software - Support software The overall s┆
0x41e00…41f00 (65, 0, 14) Sector 410fff00172841 ┆A (Aoftware structure of the MPF and the packet interrelationship is shown on figure 4.6.1-1 Figure 4.6.1-2 presents the hierachical relationship of the MPF software in a visual table of contents. a) System Software The system software include th┆
0x41f00…42000 (65, 0, 15) Sector 4100ff00172841 ┆A (Ae following packets: - KERNEL, performs the functions closest to the hardware, i.e. interrupt handling, process concept, CPU management, process communication, etc. - I/O CONTROL, that performs the interface link between the various users and ┆
0x42000…42100 (66, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(66,0, 1), len=0xff, h3=41172941}, f00=»1729A «, f01=»Crossfox tilbud «, f02=»kk «, f03=»TDJ «, f04=»1.3 «, f05=19-02-82 12:40, f06=» «, f07=»22 «, f08=» 4267 «, f09=02-03-82 10:50, f10=» «, f11=»13 «, f12=» 580 «, f13=04-03-82 15:20, f14=11-03-82 11:08, f15=»0126A «, f16=» 5 «, f17=» 1 «, f18=»08 «, f19=» 96 «, f20=» 5621 «, f21=» «, f22=» «, f99=500050000110062710110380aa8a37040000000000000137031b00df}
0x42100…42200 (66, 0, 1) Sector 42020500172941 ┆B )A B B 9 8 8 DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / ┆
0x42200…42300 (66, 0, 2) Sector 4203ff00172941 ┆B )A 1 TABLE OF CONTENTS 1 ┆
0x42300…42400 (66, 0, 3) Sector 4204ab00172941 ┆B + )A 1.3 FUNCTIONAL HIGHLIGHTS ..................... 1.3.1 MPF Functions ......................... 1.3.2 MCU Functions ......................... M8) R6.> I! <6 M8)I!h=6 ! =6 M")IM"):g=~ J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x42400…42500 (66, 0, 4) Sector 4205ff00172941 ┆B )A 1 1.3 FUNCTIONAL HIGHLIGHTS The Message Subsystem (MS) will provide an automated interface between the NICS TARE and the CROSS FOX HF and LF radio telegraph systems. It will provi┆
0x42500…42600 (66, 0, 5) Sector 4206ff00172941 ┆B )Ade relaying of ACP126/ACP127 messages between ship-borne and shore-based users and will hereto facilitate management/supervision and security of the message traffic. The MS functions match, to a high degree, the functions of the Computer Assigned ┆
0x42600…42700 (66, 0, 6) Sector 4207ff00172941 ┆B )AMessage Processing System-CAMPS, presently being being implemented by Christian Rovsing A/S for NATO. In addition to basic CAMPS functions, CROSSFOX further includes a number of special Maritime Message Handling functins to handle broadcast and rec┆
0x42700…42800 (66, 0, 7) Sector 3900ff00172941 ┆9 )Aeption over radio-links, to secure message delivery, and to provide accountability. This section will list the main functional requirements for the Message Processing Facility (MPF) and the Message Compilation Unit (MCU) with respect to security, ┆
0x42800…42900 (66, 0, 8) Sector 4209ff00173341 ┆B 3Avolved will be presented, system reliability figures shall then be calculated as expressed in availability. 3.4.1 Definitions, Formulas and Major Assumptions a) Definitions & Formulas The following set of definitions and formulas shall b┆
0x42900…42a00 (66, 0, 9) Sector 420aff00173341 ┆B 3Ae used for reliability calculations as expressed via availability: - The definition of terms of the IFB, section 4.5.1. - In further compliance with the IFB, section 4.5, the following set of definitions and formulas listed according to the modu┆
0x42a00…42b00 (66, 0, 10) Sector 420bff00173341 ┆B 3Ale categories of the IFB: b) Single Unit or Subsystem Mean Time Between Failure = MTBF = 1/2 Uptime = U = MTBF Mean Time To Repair = MTTR = D = Downtime H ┆
0x42b00…42c00 (66, 0, 11) Sector 420cff00173341 ┆B 3A u ; Availability A = U + D ┆
0x42c00…42d00 (66, 0, 12) Sector 420dff00173341 ┆B 3A For D/U 1 : A 1 - D/U = 1 - D 1 c) Redundant Units or Subsyst┆
0x42d00…42e00 (66, 0, 13) Sector 420e9f00173341 ┆B 3Aems 1 of 2 redundancy is applicable to these calculations. Uptime.......... For............. Downtime........ Availability.... F............... 's included in a supervisor specified list. The reduced conversion includes enveloping the ACP1┆
0x42e00…42f00 (66, 0, 14) Sector 420fff00173341 ┆B 3A 1 d) Series Configuration of Redunadant & Non-Redundant Units or Subsytems Each reliability element in the series has uptime U s = 1/ and downtime D S . H ┆
0x42f00…43000 (66, 0, 15) Sector 4000ff00173341 ┆@ 3A N ┆
0x43000…43100 (67, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(67,0, 1), len=0xff, h3=41173341}, f00=»1733A «, f01=»Crossfox Tilbud «, f02=»kk «, f03=»FAH «, f04=»3.4 - 3.4.5 «, f05=22-02-82 11:34, f06=» 4 «, f07=»02 «, f08=» 22147 «, f09=05-03-82 19:58, f10=» «, f11=»54 «, f12=» 2833 «, f13=05-03-81 08:49, f14=11-03-82 11:08, f15=»0126A «, f16=» 39 «, f17=» 4 «, f18=»56 «, f19=» 376 «, f20=» 24982 «, f21=» «, f22=» «, f99=020010000110062710110380aa8a37040000000000000137037300df}
0x43100…43200 (67, 0, 1) Sector 43022700173341 ┆C ' 3A C C B ? ? ? > > > > > > > > > = = = = = < < < < < < < ; ; ; ; ; ; ; ; : : : : DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer:rere┆
0x43200…43300 (67, 0, 2) Sector 4303ff00173341 ┆C 3A 1 TABLE OF CONTENTS 1 ┆
0x43300…43400 (67, 0, 3) Sector 4304ff00173341 ┆C 3A 3.4 AVAILABILITY AND RELIABILITY .............. 3.4.1 Definitions, Formulas and Major Assumptions, Definitions and Formulas .. 3.4.2 A&R Models ............................ 3.4.3 A&R Calculations ...................┆
0x43400…43500 (67, 0, 4) Sector 4305ff00173341 ┆C 3A... 3.4.3.1 Equipment Serving all External Circuits, Channels and Load Terminal Connecting Prints 3.4.3.2 Equipment Serving Supervisory and Service Position 3.4.3.3 Equipment Serving Individual User C┆
0x43500…43600 (67, 0, 5) Sector 4306ff00173341 ┆C 3Aonnecting Point 3.4.3.4 Equipment Serving Individual External 3.4.3.5 Equipment Serving Groups of External 3.4.3.6 Degraded Modes & System Degradation 3.4.3.7 Specific MTBF and Downtime Requireme 3.4.4 STE and┆
0x43600…43700 (67, 0, 6) Sector 43076400173341 ┆C d 3A S/W Failure Rates ............. 3.4.5 A&R Analysis ......................... 1{M40sI:^=~ J 1!"<6;!#<6 !&<6 ! "$<! <6 {M;(s! 9"c=! "(= Z=q#p!"<6 !&<6 ! "$<!#<6 ! <6 {M)(sC I! <6 ! "(= <q#p!"<6 !#<6 ! "$<!&<6$`i6 {M)(sM &M7 ┆
0x43700…43800 (67, 0, 7) Sector 4208ff00173341 ┆B 3A 1 3.4 AVAILABILITY AND RELIABILITY The MPF reliability as expressed in terms of availability exceeds each of the requirements of the IFB. The reliability figures for all units in┆
0x43800…43900 (67, 0, 8) Sector 4309ff00174341 ┆C CA The MCU interfaces to the crypto through a KW-7 adaptor. The MCU output to the KW7 adaptor is a V.24/V.28 compatible line. Connection is via standard 25 pole connector. 4.4.5.4 MPF Interface The status line to the MPF is an asynchronous V.24┆
0x43900…43a00 (67, 0, 9) Sector 430acf00174341 ┆C O CA/V.28 line. Data ratre is 1200 Baud. Connction is via standard 25 pole connectors. 4.4.6 Comparison with requirements The MCU, extended with the KW-7 adaptor, complies with the requirements of rom a particular channel (channel confidence). ┆
0x43a00…43b00 (67, 0, 10) Sector 00001e00174341 ┆ CAthe IFB in all respects. The two modules communicates the microbus. The input module performs the serial-to-parallel conversion, collects the framing status and compares the characters ┆
0x43b00…43c00 (67, 0, 11) Sector 00000000000000 ┆ ┆
[…0x4…]
0x44000…44100 (68, 0, 0) Sector 44014500173641 ┆D E 6Ao create a system load module from several program modules. ┆
0x44100…44200 (68, 0, 1) Sector 4402ff00173641 ┆D 6A 1 4.6.4.1.1.4 Librarian The Librarian organizes all information pertinent to systems development to satisfy program development, systems generation and documentation. 4.6.4.1.2 S┆
0x44200…44300 (68, 0, 2) Sector 4403ff00173641 ┆D 6Aoftware System Support This covers - File Manipulation Programs - Directory Maintenance Programs - High Level Operating System - Disk Manipulation 4.6.4.1.2.1 File Manipulation Programs These programs include functions for: - file copy┆
0x44300…44400 (68, 0, 3) Sector 4404e100173641 ┆D a 6Aing - file display - file comparison - file conversions (BIN/HEX) 4.6.4.1.2.2 Directory Maintenance This is a suite of programs for inspecting and modifying the contents of backing store file structures, i.e.: 4.6.4.1.1.2 Text Processors .┆
0x44400…44500 (68, 0, 4) Sector 4405ff00173641 ┆D 6A 1 - File creation, deletion, and renaiming - Entering of a file into a directory - Listing of the contents of a directory or the attributes of a file - Changing the protection of ┆
0x44500…44600 (68, 0, 5) Sector 4406ff00173641 ┆D 6Aa file 4.6.4.1.2.3 High Level Operating System The CR80 standard high level Terminal Operating System, TOS, supports interactive terminal users in a program development environment. A central part of this environment is the hierachically protec┆
0x44600…44700 (68, 0, 6) Sector 4407ff00173641 ┆D 6Ated file-store system. Normally, program development will be done on a site which is in "Degraded Availability Mode" and where the "off-line PU" plus peripherals are under the regime of TOS. 4.6.4.1.2.4 Disk Manipulation Programs a) Disk Init┆
0x44700…44800 (68, 0, 7) Sector 3908ff00173641 ┆9 6Aialization Program To create a preformatted but "empty" structure, e.g. on a virgin disk. b) Disk Salvation For a file structured volume the program is able to check the readability and validity and to rebuild the external file system data s┆
0x44800…44900 (68, 0, 8) Sector 4409ff00173641 ┆D 6At Software Package is a common name for the various units of general CR80-software that are independent of the actual use of the CR80 (Crossfox-MPF), but used for software development, test, and diagnostics as well as for diagnostics of hardware. ┆
0x44900…44a00 (68, 0, 9) Sector 440ab700173641 ┆D 7 6A The SSP software may be categorized as follows: - Software Development and Test o Language Processors o Text Processors o Development and Test Tools o Librarian 2.=M ':>=V V u:A=!>= AH1 R^4 ]M, C 4:>=2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x44a00…44b00 (68, 0, 10) Sector 440bff00173641 ┆D 6A 1 - Software System Support o File Manipulation Programs o Directory Maintenance o High Level Operating System o Disk Manipulation Programs - Diagnostics Software 4.┆
0x44b00…44c00 (68, 0, 11) Sector 440cff00173641 ┆D 6A6.4.1.1 Software Development and Test 4.6.4.1.1.1 Language Processors Those that are relevant for Crossfox are the compilers for - SWELL Development language for CAMPS on-line SW) - PASCAL - Assembler Language 4.6.4.1.1.2 Test Proc┆
0x44c00…44d00 (68, 0, 12) Sector 440d6800173641 ┆D h 6Aessors a) Editor This is an interactive line editor which is also available in batch mode. , the corresponding avaiability being calculated in table 3.4.3.6-1 to -3 The system is brought back to a fully configured state from the engineering┆
0x44d00…44e00 (68, 0, 13) Sector 440eff00173641 ┆D 6A 1 b) General Text Formatter For margin justification, page headings, and underlining of key words. c) A program for merging of source files. 4.6.4.1.1.3 Development and Test ┆
0x44e00…44f00 (68, 0, 14) Sector 440fff00173641 ┆D 6ATools a) Linker For generation of an object module from several compiled modules. b) Debuggers Containing the language Debugger which operates with symbolic names and the General Debugger which operates on relative program addresses. Both┆
0x44f00…45000 (68, 0, 15) Sector 4400ff00173641 ┆D 6A facilitate: Use of breakpoints, inspection and setting of current values of variables access to registers, creation and removal of synchronization elements. The debuggers may be operated interactively or by a test driver. c) System Generator T┆
0x45000…45100 (69, 0, 0) Sector 4501ff41173641 ┆E A 6A1736A Crossfox Tilbud kk KR 4.6.4 - 4.6.4.2 22 02 82 15 46 53 6416 03 03 81 09 40 02 58 03 03 81 11 01 11 03 82 11 08 0126A 8 1 20 108 6786 ' * 7 7 " _┆
0x45100…45200 (69, 0, 1) Sector 45020800173641 ┆E 6A E E D D D D 9 9 DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / ┆
0x45200…45300 (69, 0, 2) Sector 4503ff00173641 ┆E 6A 1 TABLE OF CONTENTS 1 ┆
0x45300…45400 (69, 0, 3) Sector 4504ff00173641 ┆E 6A 4.6.4 Support Software ...................... 4.6.4.1 Support Software Package (SSP) .... 4.6.4.1.1 Software Development and Test . 4.6.4.1.1.1 Language Processors ...... 4.6.4.1.1.2 Text Processors .┆
0x45400…45500 (69, 0, 4) Sector 4505ff00173641 ┆E 6A.......... 4.6.4.1.1.3 Development and Test Tools 4.6.4.1.1.4 Librarian .................. 4.6.4.1.2 Software System Support ........ 4.6.4.1.2.1 File Manipulation Programs . 4.6.4.1.2.2 Direct┆
0x45500…45600 (69, 0, 5) Sector 4506f500173641 ┆E u 6Aory Maintenance ...... 4.6.4.1.2.3 High Level Operating System 4.6.4.1.2.4 Disk Manipulation Programs . 4.6.4.1.3 Diagnostic Software ........... 4.6.4.2 Off-Line Package (OLP) ............. <M% ! "2<┆
0x45600…45700 (69, 0, 6) Sector 4507ff00173641 ┆E 6A 1 4.6.4 Support Software The support software includes all off-line software required to support the operational system. The support software will be provided by two different pac┆
0x45700…45800 (69, 0, 7) Sector 4408ff00173641 ┆D 6Akages: - Support Software Package (SSP), which is independent on the actual use of CR80. - Off Line Package (OLP), For the generation and maintenance of Crossfox-specific off-line data. 4.6.4.1 Support Software Package (SSP) The Suppor┆
0x45800…45900 (69, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(69,0, 9), len=0xff, h3=41173641}, f00=»1736A «, f01=»Crossfox Tilbud «, f02=»kk «, f03=»KR «, f04=»4.6.4 - 4.6.4.2 «, f05=22-02-82 15:46, f06=» «, f07=»53 «, f08=» 6416 «, f09=23-02-82 14:49, f10=» «, f11=»04 «, f12=» 45 «, f13=23-02-82 16:29, f14=23-02-82 16:38, f15=»0126A «, f16=» 7 «, f17=» «, f18=»57 «, f19=» 108 «, f20=» 6461 «, f21=» «, f22=» «, f99=020010000110062710110380aa8a37040000000000000137032000df}
0x45900…45a00 (69, 0, 9) Sector 450a0700173641 ┆E 6A E E E E D D D DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / ┆
0x45a00…45b00 (69, 0, 10) Sector 450bff00173641 ┆E 6A 1 TABLE OF CONTENTS 1 ┆
0x45b00…45c00 (69, 0, 11) Sector 450cff00173641 ┆E 6A 4.6.4 Support Software ...................... 4.6.4.1 Support Software Package (SSP) .... 4.6.4.1.1 Software Development and Test . 4.6.4.1.1.1 Language Processors ...... 4.6.4.1.1.2 Text Processors .┆
0x45c00…45d00 (69, 0, 12) Sector 450dff00173641 ┆E 6A.......... 4.6.4.1.1.3 Development and Test Tools 4.6.4.1.1.4 Librarian .................. 4.6.4.1.2 Software System Support ........ 4.6.4.1.2.1 File Manipulation Programs . 4.6.4.1.2.2 Direct┆
0x45d00…45e00 (69, 0, 13) Sector 450ef500173641 ┆E u 6Aory Maintenance ...... 4.6.4.1.2.3 High Level Operating System 4.6.4.1.2.4 Disk Manipulation Programs . 4.6.4.1.3 Diagnostics Software ........... 4.6.4.2 Off-Line Package (OLP) ............. <M% ! "2<┆
0x45e00…45f00 (69, 0, 14) Sector 450fff00173641 ┆E 6A 1 4.6.4 Support Software The support software comprises all off-line software required to support the operational system. The support software will be covered by two different pac┆
0x45f00…46000 (69, 0, 15) Sector 4500ff00173641 ┆E 6Akages: - Support Software Package (SSP), which is independent on the actual use of CR80. - Off Line Package (OLP), For the generation and maintenance of Crossfox-specific off-line data. 4.6.4.1 Support Software Package (SSP) The Suppor┆
0x46000…46100 (70, 0, 0) Sector 4601ff00174341 ┆F CA 1 4.4.5.1 Modem Interface The MCU inputs are V.24/V.28 asynchronous channels. Data rate is 75 baud. Connection is via standard 25 pole connectors. 4.4.5.2 Crypto interface ┆
0x46100…46200 (70, 0, 1) Sector 4602ff00174341 ┆F CA The MCU interfaces to the crypto through a KW-7 adaptor. The MCU output to the KW-7 adaptor is a V.24/V.28 compatible line. Connection is via standard 25 pole connector. 4.4.5.3 MPF Interface The status line to the MPF is an asynchronous V.2┆
0x46200…46300 (70, 0, 2) Sector 46030700174341 ┆F CA41 The two modules communicate via the microbus. Fig. 4.4-3 The input module performs the serial-to-parallel conversion, collects the framing status and compares t┆
0x46300…46400 (70, 0, 3) Sector 0000e600174341 ┆ f CA/V.28 line. Data rate is 1200 Baud. Connction is via standard 25 pole connectors. 4.4.6 Comparison with requirements The MCU, extended with the KW-7 adaptor, complies with the requirements of the IFB in all respects. 7. Provision of a chan┆
0x46400…46500 (70, 0, 4) Sector 4605ff00174341 ┆F CActer is chosen (provided this channel is among the channels which holds the high level) or the one with the lowest channel number is chosen for output. In this case, the charcter, transmitted simultaneously on the status line will indicate the ambi┆
0x46500…46600 (70, 0, 5) Sector 4606ff00174341 ┆F CAguity. For each block of TBD compiled characters or after TBD secnds of silence, a status message is sent on the status line in addition to the above character quality. The status message comprises four characters, reflecting the current channel ┆
0x46600…46700 (70, 0, 6) Sector 46077a00174341 ┆F z CAconfidence level. 4.4.5 Interface Characteristics 4.4.5.1 Power Supply Nominal 20V AC, appr. 50 watts. ion is o The hardware/software complexity required for the realization o The ability to react fast on burst errors o The abilit┆
0x46700…46800 (70, 0, 7) Sector 4308ff00174341 ┆C CA 1 4.4.5.2 Modem Interface The MCU inputs are V.24/V.28 asynchronous channels. Data rate is 75 baud. Connection is via standard 25 pole connectors. 4.4.5.3 Crypto interface ┆
0x46800…46900 (70, 0, 8) Sector 4609ff00174341 ┆F CA as the one in question, i.e. FC = 3 means that all four channels agree, FC = 0 that no other channel agrees with the one in question. Table look-up is a fast, very flexible and inexpensive method of implementing algorithms, in particular if the t┆
0x46900…46a00 (70, 0, 9) Sector 460aa800174341 ┆F ( CAable size is small. Data available, error and F c , together with channel confidence are used for table-look-up of a) Confidence level for present character ┆
0x46a00…46b00 (70, 0, 10) Sector 460bff00174341 ┆F CA 1 b) Updated channel confidence The contents of the table are determined to fulfil the specific requirements of the IFB on exclusion of garbled channels. The remaining degrees of ┆
0x46b00…46c00 (70, 0, 11) Sector 460cff00174341 ┆F CAfreedom are used to provide the optimum choice based on the statistical properties of the channel and taking into account the behaviour during initialization, burst error, etc. Having achieved the character confidence level, it takes only a simple┆
0x46c00…46d00 (70, 0, 12) Sector 460dff00174341 ┆F CA comparison to select the character with the highest value for output. Should more than one channel hold the same character confidence level but claim different character values, the one which was selected for the previous character is chosen (pro┆
0x46d00…46e00 (70, 0, 13) Sector 460eff00174341 ┆F CAvided this channel is among the channels which hold the high level) or the one with the lowest channel number is chosen for output. In this case, the character transmitted simultaneously on the status line will indicate the ambiguity. For each bl┆
0x46e00…46f00 (70, 0, 14) Sector 460fff00174341 ┆F CAock of TBD compiled characters or after TBD seconds of silence, a status message is sent on the status line in addition to the above character quality. The status message contains four characters, reflecting the current channel confidence level. ┆
0x46f00…47000 (70, 0, 15) Sector 46003c00174341 ┆F < CA 4.4.5 Interface Characteristics From mains supply s o Smooth initialization. data streams from four ship-to-shore access sites. The four data streams are identical except for transmission errors and delay. = Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x47000…47100 (71, 0, 0) Sector 4701ff00174341 ┆G CA 1 4.4.3 MCU Design Fig. 4.4-2 The MCU functions are performed by two LTUX-M-CPU plug-in modules, housed in a small crate with power supply. The LTUX-M-┆
0x47100…47200 (71, 0, 1) Sector 4702d700174341 ┆G W CACPU is a module designed for intelligent line termination of multiple (up to 4) V.24 type channels. The on-board microprocessor is programmed for the individual application and the program resides in a PROM. ectly received character from a particul┆
0x47200…47300 (71, 0, 2) Sector 4703ff00174341 ┆G CA 1 The two modules communicate via the microbus. Fig. 4.4-3 The input module performs the serial-to-parallel conversion, collects the framing status and compares t┆
0x47300…47400 (71, 0, 3) Sector 4704dc00174341 ┆G \ CAhe characters to achieve the correlation figure. The output module receives the four characters and the corresponding status and performs all message compilation, data output and character quality assignment. ld or not. 7. Provision of a chan┆
0x47400…47500 (71, 0, 4) Sector 4705ff00174341 ┆G CA 1 4.4.4 Functional Description The four serial, asynchronous data streams are converted to parallel data by a universal asynchronous receiver/transmitter (UART). This digital cir┆
0x47500…47600 (71, 0, 5) Sector 4706ff00174341 ┆G CAcuit provides an indication of framing error, i.e. incorrect frame format caused by , for example, a falsely detected start bit or a corrupted stop bit. A "data available" status is indicated as a separate signal when a character has been received┆
0x47600…47700 (71, 0, 6) Sector 4707ff00174341 ┆G CA. The received characters, together with the corresponding status, are read from the UART'S after the expiry of the max. delay period (20 msec) after the character of the leading channel has been completed. For each channel the following informa┆
0x47700…47800 (71, 0, 7) Sector 4608ff00174341 ┆F CAtion is derived: Data available yes/no Framing error yes/no Correction, Fc 0,1,2 or 3 Fc is the number of channels which show the same character┆
0x47800…47900 (71, 0, 8) Sector 4709ff00174341 ┆G CAers. 4.4.2.1 Character Status The character status is easily achieved. It should, however, be emphasized that the errors are strongly interrelated so a thorough knowledge of the failure mechanisms is necessary for the correct interpretation. ┆
0x47900…47a00 (71, 0, 9) Sector 470a8300174341 ┆G CA Framing error, as an example, could be caused by a) bit error on start bit b) bit error on stop bit c) bit slippage ┆
0x47a00…47b00 (71, 0, 10) Sector 470bff00174341 ┆G CA 1 Case a) Causes in general a data bit to be mistaken for a start bit and hence leads to a garbled character. Bit error on stop bit gives the same error indication, but the characte┆
0x47b00…47c00 (71, 0, 11) Sector 470cff00174341 ┆G CAr will be correct. Bit slippage will, in general, lead to a garbled character, but an error indication will only be given in certain cases. 4.4.2.2 Channel Status Determination of the method for achieving the channel status is quite complex.┆
0x47c00…47d00 (71, 0, 12) Sector 470dff00174341 ┆G CA The purpose of the channel status (channel confidence level) is to provide a figure which reflects the relative (priria facie) probability of receiving a correct character from a given channel. A means for determination of this probabiity is a ┆
0x47d00…47e00 (71, 0, 13) Sector 470eff00174341 ┆G CAfiltered version of the history of character status. The filter function should, ideally, be based on a comprehensive statistical modelling of the entire transmission channel. However, a sufficiently good result can fortunately be achieved with le┆
0x47e00…47f00 (71, 0, 14) Sector 470fff00174341 ┆G CAss work because the model is dominated by a few contributing mechanisms. Some of the more important aspects of the filter function are: o The hardware/software complexity required for the realization o The ability to react rapidly on burst erro┆
0x47f00…48000 (71, 0, 15) Sector 47005900174341 ┆G Y CArs o The ability to recover quickly from burst errors o Smooth initialization. data streams from four ship-to-shore access sites. The four data streams are identical except for transmission errors and delay. = Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x48000…48100 (72, 0, 0) Sector 4801ff00174341 ┆H CA 1 From the four channels, a single channel is compiled by a majority voting algorithm and delivered to the KW 7 crypto. The functional characteristics of the proposed MCU are 1. ┆
0x48100…48200 (72, 0, 1) Sector 4802ff00174341 ┆H CAReception of four 75 Baud V.24 channels. 2. Compensation for relative transmission delay on the four channels (20msec). 3. Calculation of statistics for the purpose of determining the probability of a correctly received character from a particul┆
0x48200…48300 (72, 0, 2) Sector 4803ff00174341 ┆H CAar channel (channel confidence). 4. Selection of most probably correct character among the four; the selection is based on the current channel confidence, combined with the character status in term of framing status and correlation with the other ┆
0x48300…48400 (72, 0, 3) Sector 4804ff00174341 ┆H CAthree channels. 5. Transmission of the character on a V24 line to the Crypto. 6. Provision of a character on a separate line to the MPF, indicating whether the confidence level of the character passed a threshold or not. 7. Provision of a chan┆
0x48400…48500 (72, 0, 4) Sector 4805ff00174341 ┆H CAnel confidence figure at regular intervals. 4.4.2 Compilation algorithm The IFB requires a message compilation by majority voting on a character-by-character basis. Heavily garbled channels shall be excluded from the voting process. In addit┆
0x48500…48600 (72, 0, 5) Sector 4806b500174341 ┆H 5 CAion, a confidence level of the channels shall be established in order to facilitate selection of the most probably correct character in case the majority voting is ambiguous. program for merging of source files. 4.6.4.1.1.3 Development and Test ┆
0x48600…48700 (72, 0, 6) Sector 4807ff00174341 ┆H CA 1 Since no a priori assumptions can be made about the information in the message, the parameters left for assigning a confidence level of a given character among the four received ar┆
0x48700…48800 (72, 0, 7) Sector 4708ff00174341 ┆G CAe: Character status: o Received/not received status o Correct/incorrect framing (start/stop bit) o Agreement/non agreement between channels Channel Status: o Channel confidence level based on the status of the previously received charact┆
0x48800…48900 (72, 0, 8) Sector 4809ff00169441 ┆H A presses the "start" button on the disk drives where a disk is mounted, and he presses the "reset" button on the watchdog processor and on the Processing Units. Thereafter he can interactively choose the appropriate start-up type from the watchdog ┆
0x48900…48a00 (72, 0, 9) Sector 480aff00169441 ┆H Aconsole (Engineering Position). When initialization is finished he will be notified. 4.2.8.2 Local System Data Base (LSDB) The LSDB contains the appropriate values of system parameters and address and routing information and is administered b┆
0x48a00…48b00 (72, 0, 10) Sector 480b2b00169441 ┆H + Ay the "Table Management Package". TABLE OF CONTENTS 1 4.2.8 System Initializati┆
0x48b00…48c00 (72, 0, 11) Sector 480cff00169441 ┆H A 1 4.2.8.3 Storage of the S/W and Data Required for Initializaton The means and the mediums used for the standard procedures have been described above, i.e. a procedure where the so┆
0x48c00…48d00 (72, 0, 12) Sector 480dff00169441 ┆H Aftware resides on the off-line disc drive. New software versions or data may be loaded/stored from floppy disk. The storage arrangements employ the use of various checks e.g. Cyclic Redundancy Check to detect corruption of data. Once loaded, th┆
0x48d00…48e00 (72, 0, 13) Sector 480eff00169441 ┆H Ae data is available on-line. 4.2.8.4 Storage of the System Programme and Current Data Base. It will be possible to "OFF-LOAD" these data as required. This can be performed periodically, but we recommend that the supervisor be notified period┆
0x48e00…48f00 (72, 0, 14) Sector 480fff00169441 ┆H Aically and that the off-load command will then be issued by a deliberate action. 4.2.9 Recovery Extensive use of checkpointing to the two mirrored disks is employed. The processing flow of the message processing system consists of a well def┆
0x48f00…49000 (72, 0, 15) Sector 07087000169441 ┆ p Ained set of successive steps where output for one step serves as input for one or more succeeding steps. c2! m"2< [MI !?=6 : #wI>K!8=>R 2!8=6 #4 E*8=k L<M% :8=F 28=I!#<:"<>R<2> I E*#<& "< DM L<M% :#<F 2#<> I:g= Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x49000…49100 (73, 0, 0) Sector 4901ff00169441 ┆I A 1 4.2.8 System Initialization 4.2.8.1 Initialization Procedure Initialization is the process of bringing the system into operational use without recovery. Three types of in┆
0x49100…49200 (73, 0, 1) Sector 4902ff00169441 ┆I Aitialization may be used: DEAD1: For the very first start of the system from an offline disk with the initial system parameters. DEAD2: From an offline disk containing updated system parameters reflecting the state of tables at the time o┆
0x49200…49300 (73, 0, 2) Sector 4903ff00169441 ┆I Af the latest OFF-LOAD (ref. IFB sec. 5.1.2.8.4). This type start-up makes use of mirrored, on-line disks that are preformatted (cleared) prior to the initialization process. COLD: From one of the mirrored on-line disks. This is based on t┆
0x49300…49400 (73, 0, 3) Sector 4904ff00169441 ┆I Ahe current system parameters and includes the proper purging of the historical data base. Once a DEAD-start has been performed, the MPF site software package will be available on the mirrored on-line disks for future COLD-starts or recovery situa┆
0x49400…49500 (73, 0, 4) Sector 4905df00169441 ┆I _ Ations. The data held on-line will initially be from the appropriate off-line MPF site software package. As described under "DEAD" and "COLD", the system will be initialized with an empty, historical data base. tte ┆
0x49500…49600 (73, 0, 5) Sector 4906ff00169441 ┆I A 1 As for the MPF site software package, the LSDB will be established as well. The maximum duration of initialization from an off-line disk will not exceed 5 minutes. The initi┆
0x49600…49700 (73, 0, 6) Sector 4907ff00169441 ┆I Aalization Procedure will progress as follows: Having switched on the power, the supervisor must make sure that the proper disks are physically mounted, i.e.: - on the "off-line drive" should be mounted the original system-parameter-disk or a d┆
0x49700…49800 (73, 0, 7) Sector 4808ff00169441 ┆H Aisk containing an off-loaded version for DEAD1 and DEAD2, respectively. - on the mirrored on-line drives should be mounted a set of cleared and preformatted disks or just the currently used on-line disks for DEAD or COLD, respectively. He then┆
0x49800…49900 (73, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(73,0, 9), len=0xff, h3=41169441}, f00=»1694A «, f01=»System Initialization «, f02=»kk «, f03=»KR «, f04=»4.2.8 og 4.2.9 «, f05=15-02-82 10:11, f06=» 2 «, f07=»29 «, f08=» 8053 «, f09=02-03-82 14:06, f10=» «, f11=»57 «, f12=» 692 «, f13=05-03-82 17:44, f14=11-03-82 11:01, f15=»0126A «, f16=» 9 «, f17=» 4 «, f18=»27 «, f19=» 180 «, f20=» 10586 «, f21=» «, f22=» «, f99=020010000110062710110380aa8a37040000000000000137032d00df}
0x49900…49a00 (73, 0, 9) Sector 490a0900169441 ┆I A I I I H DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet ┆
0x49a00…49b00 (73, 0, 10) Sector 490bff00169441 ┆I A 1 TABLE OF CONTENTS 1 4.2.8 System Initializati┆
0x49b00…49c00 (73, 0, 11) Sector 490cff00169441 ┆I Aon ................. 4.2.8.1 Initialization Procedure .......... 4.2.8.2 Local System Data Base (LSDB) ...... 4.2.8.3 Storage of the S/W and Data Required for Initialization ................. 4.2.9 Storag┆
0x49c00…49d00 (73, 0, 12) Sector 490dff00169441 ┆I Ae of the System Program and Current Data Base ...................... 4.2.10 Recovery .............................. 4.2.10.1 Information Integrity ............. 4.2.10.2 Scope of Recovery Procedure ....... ┆
0x49d00…49e00 (73, 0, 13) Sector 490eff00169441 ┆I A 4.2.10.3 Recovery Points ................... 4.2.10.4 Recovery Program ................ 4.2.10.6 Continuity of Message Traffic after Failure .................... 4.2.10.7 Continuity of Stored Message ┆
0x49e00…49f00 (73, 0, 14) Sector 490fff00169441 ┆I A Information ...................... 4.2.10.8 Continuity of the reporting System ........................... 4.2.10.9 Continuity of System Data. ........ 4.2.10.10 Resumption of local transaction afte┆
0x49f00…4a000 (73, 0, 15) Sector 49002a00169441 ┆I * Ar failure ................... ^=~ B<2:b= R<2M/,:g=~ BG2M")M2&! "(=~~ BW2I! <6 M /M?.I*:="8=IM2&MP'Mc2! m"2< [MI !?=6 : #wI>K!8=>R 2!8=6 #4 E*8=k L<M% :8=F 28=I!#<:"<>R<2> I E*#<& "< DM L<M% :#<F 2#<> I:g= Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x4a000…4a100 (74, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(74,0, 1), len=0xff, h3=41170041}, f00=»1700A «, f01=»CROSSFOX Tilbud final «, f02=»kk «, f03=»FIH «, f04=»4.7 - 4.7.4 «, f05=16-02-82 09:10, f06=» 5 «, f07=»21 «, f08=» 23940 «, f09=05-03-81 12:39, f10=» «, f11=»01 «, f12=» 14 «, f13=05-03-82 19:24, f14=11-03-82 11:01, f15=»0126A «, f16=» 28 «, f17=» 6 «, f18=»43 «, f19=» 408 «, f20=» 26461 «, f21=» «, f22=» «, f99=020080000110062710110380aa8a37040000000000000137037300df}
0x4a100…4a200 (74, 0, 1) Sector 4a021c00170041 ┆J A J J $ $ $ $ # # " " " DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITE┆
0x4a200…4a300 (74, 0, 2) Sector 4a03ff00170041 ┆J A 1 TABLE OF CONTENTS 1 4.7 SYSTEM PERFORMANCE .┆
0x4a300…4a400 (74, 0, 3) Sector 4a04fe00170041 ┆J ~ A...................... 4.7.1 Message Traffic Flow ................. 4.7.2 Throughput ............................ 4.7.3 Storage ................................ 4.7.4 Timing ................................. C┆
0x4a400…4a500 (74, 0, 4) Sector 4a05ff00170041 ┆J A 1 4.7 SYSTEM PERFORMANCE This section presents the evaluations of the porposed MPF system in terms of performance. The system is fully compliant with the IFB requirements (sectio┆
0x4a500…4a600 (74, 0, 5) Sector 4a06ff00170041 ┆J An 5.1.4) for - throughput - storage - timing with the message traffic characteristics presented in the IFB(section 5.1.4.1) as underlaying assumption. Detailed information on the requirements has been given in section 1.2 and will be repea┆
0x4a600…4a700 (74, 0, 6) Sector 4a07ff00170041 ┆J Ated again here in each subsection together with the proof of compliance. System characteristics and performance calculations will be presented to the extent that sufficient evidence is available for judgement of performance compliance. In order ┆
0x4a700…4a800 (74, 0, 7) Sector 2408ff00170041 ┆$ Ato perform these calculations it has been necessary in some cases to introduce assumptions concerning message characteristics and the message flow: Such assumptions are merely used in order to provide a rough estimate for proof of system performanc┆
0x4a800…4a900 (74, 0, 8) Sector 4a091f00171241 ┆J A................... ' 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 ! ┆
0x4a900…4aa00 (74, 0, 9) Sector 4a0aff00171241 ┆J A 1 2. OPERATIONAL PROCEDURES Implementation of the MSF operational procedures will be based on the experience that Christian Rovsing A/S has gained from implementation of similar c┆
0x4aa00…4ab00 (74, 0, 10) Sector 4a0bff00171241 ┆J Aommunication systems. During the design of CAMPS, for example, CR has conducted a number of reviews with SHAPE operational staff to ensure effective and easy to use man-machine interfaces and operational aspects. The objectives for the MS design ┆
0x4ab00…4ac00 (74, 0, 11) Sector 4a0cff00171241 ┆J Ahave been: to build a secure and reliable system; to provide the system with great modularity and flexibility in both software and hardware; and to retain as much commonality with other NATO systems as possible. This section describes the essentia┆
0x4ac00…4ad00 (74, 0, 12) Sector 4a0dff00171241 ┆J Al operational procedures performed by the proposed Message Subsystem. Further description of the function level is given in section 4.2 of this appendix. 2.1 BROADCAST OF MESSAGES The methods and procedures for the operation of the CROSSFOX B┆
0x4ad00…4ae00 (74, 0, 13) Sector 4a0eff00171241 ┆J Aroadcast will be implemented in the MPF in accordance with the relevant paragraphs in ACP127 Supplement 1 as listed in the IFB. Below, these operational procedures will briefly be described. For detailed information please refer to section 4.2.2 o┆
0x4ae00…4af00 (74, 0, 14) Sector 4a0ffa00171241 ┆J z Af this appendix. 2.1.1 Transmission on the Broadcast The MPF will automatically broadcast incoming messages destined for relay and locally generated messages in accordance with the message routing information and the channel assignment. 7 j _┆
0x4af00…4b000 (74, 0, 15) Sector 2908ff00171241 ┆) A 1 The supervisor will have facilities for channel assignment i.e. specifying which of the ships, or other authorities copying the broadcast, shall be associated with each channel of ┆
0x4b000…4b100 (75, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(75,0, 1), len=0xff, h3=41171241}, f00=»1712A «, f01=»CROSSFOX tilbud «, f02=»ktd «, f03=»TDJ «, f04=»kap 2 - 2.7 «, f05=18-02-82 12:29, f06=» 2 «, f07=»41 «, f08=» 16298 «, f09=02-03-82 11:12, f10=» «, f11=»57 «, f12=» 896 «, f13=03-03-81 14:49, f14=11-03-82 11:02, f15=»0126A «, f16=» 15 «, f17=» 5 «, f18=»10 «, f19=» 356 «, f20=» 21402 «, f21=» «, f22=» «, f99=020010000110062710110380aa8a37040000000000000137035800df}
0x4b100…4b200 (75, 0, 1) Sector 4b020f00171241 ┆K A K J J ) ) ( ( ( ' ' ' ' & & % DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLSL┆
0x4b200…4b300 (75, 0, 2) Sector 4b03ff00171241 ┆K A 1 TABLE OF CONTENTS 1 2. OPERATIONAL PROCEDURES ┆
0x4b300…4b400 (75, 0, 3) Sector 4b04ff00171241 ┆K A ...................... 2.1 BROADCAST OF MESSAGES ..................... 2.1.1 Transmission on Broadcast ............. 2.1.2 Dissemination of Traffic control Information ........................... 2.1.3 Retran┆
0x4b400…4b500 (75, 0, 4) Sector 4b05ff00171241 ┆K Asmission on Broadcast ........... 2.1.4 Procedure for Crypto Handling ......... 2.2.1 Receiving Messages on Ship-to-Shore ... 2.2.2 Dissemination of Information .......... 2.2 SHIP-to-SHORE MESSAGE HANDLING .....┆
0x4b500…4b600 (75, 0, 5) Sector 4b06ff00171241 ┆K A....... 2.3 OPERATOR SYSTEM INTERFACE ................. 2.4 LOCAL MESSAGE PREPARATION ................. 2.5 SUPERVISORY FUNCTIONS ..................... 2.5.1 Systems Control ....................... 2.5.2 Mess┆
0x4b600…4b700 (75, 0, 6) Sector 4b07ff00171241 ┆K Aage Handling ...................... 2.5.3 Message Release ....................... 2.5.4 Channel Control ....................... 2.5.5 System Monitoring ..................... 2.5.6 Security Control ...............┆
0x4b700…4b800 (75, 0, 7) Sector 4a08ff00171241 ┆J A....... 2.6 STORAGE & RETRIEVAL ....................... 2.7 SYSTEM CONFIGURATION CONTROL, INITIALIZATION & RECOVERY ................. 2.8 ACCOUNTABILITY PROCEDURES ................. 2.9 OPERATIONAL SECURITY ...┆
0x4b800…4b900 (75, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(75,0, 9), len=0xff, h3=41174341}, f00=»1743A «, f01=»Crossfox Tilbud «, f02=»kk «, f03=»PEH «, f04=»4.4 - 4.4.6 «, f05=23-02-82 13:29, f06=» «, f07=»38 «, f08=» 7810 «, f09=01-03-82 08:51, f10=» 1 «, f11=»19 «, f12=» 1593 «, f13=03-03-81 15:18, f14=11-03-82 11:08, f15=»0126A «, f16=» 10 «, f17=» 1 «, f18=»57 «, f19=» 180 «, f20=» 9403 «, f21=» «, f22=» «, f99=020010000110062710110380aa8a37040000000000000137032c00df}
0x4b900…4ba00 (75, 0, 9) Sector 4b0a0a00174341 ┆K CA K K H H G G G G F F DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Opretttt┆
0x4ba00…4bb00 (75, 0, 10) Sector 4b0bff00174341 ┆K CA 1 TABLE OF CONTENTS 1 ┆
0x4bb00…4bc00 (75, 0, 11) Sector 4b0cff00174341 ┆K CA 4.4 MESSAGE COMPILATION UNIT (MCU) ............ 4.4.1 General ............................... 4,4,2 Compilation algorithm ................. 4.4.2.1 Character Status .................. 4.4.2.2 Channel Status .┆
0x4bc00…4bd00 (75, 0, 12) Sector 4b0dff00174341 ┆K CA.................. 4.4.3 MCU Design ............................ 4.4.4 Functional Description ................ 4.4.5 Interface Characteristics ............. 4.4.5.1 Modem Interface .................... 4.┆
0x4bd00…4be00 (75, 0, 13) Sector 4b0ea300174341 ┆K # CA4.5.2 Crypto Interface .................. 4.4.5.3 MPF Interface ..................... 4.4.6 Comparison with requirements .......... ! <6 M1' R40C.1! <6 M1' RC0C.1! <6 M1' RR0C.1!$<5CQ0!$<6 !&<6 Mc&! "(=6 E '<M% ! "2<┆
0x4be00…4bf00 (75, 0, 14) Sector 4b0fff00174341 ┆K CA 1 4.4 MESSAGE COMPILATION UNIT (MCU) 4.4.1 General The MCU solution proposed by Christian Rovsing A/S is based on a military qualified, off-the-shelf micro- processor system ┆
0x4bf00…4c000 (75, 0, 15) Sector 4800dc00174341 ┆H \ CA Fig. 4.4-1 The message compilation Unit receives four serial data streams from four ship-to-shore access sites. The four data streams are identical except for transmission errors and delay. = Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x4c000…4c100 (76, 0, 0) Sector 00000000000000 ┆ ┆
[…0xf…]
