OctetView
0x00000…00100 (0, 0, 0) Sector 02114130323131 ┆ A0211A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00feffffffff ┆ ~ ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x24, d01=0x98, d02=0x41, ptr=(32,0, 0), d05=0x00}
0x00306…0030c WangDocument {d00=0x25, d01=0x20, d02=0x41, ptr=(65,0, 0), d05=0x00}
0x0030c…00312 WangDocument {d00=0x25, d01=0x58, d02=0x41, ptr=(35,0, 8), d05=0x00}
0x00312…00320 25 58 41 24 00 00 00 00 00 00 00 00 00 00 ┆%XA$ ┆
0x00320…00340 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 ┆ ┆
[…0x5…]
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 12 ┆ ┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 86312020202020 ┆ 1 8 7 Q? > 7 T \ _ [ [ d d N ~<) 0uH &4'>( 1c5 & & ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' X% % PO P ; %XAT C g x g V WD O B :( ( w 2558A g q < {C < { ; 8 % h b bD 5 K 8 : 9 wx A ( ( ~ ~ ┆
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
[…0x1e7…]
0x20000…20100 (32, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(32,0, 1), len=0xff, h3=41249841}, f00=»2498A «, f01=»MWHQ «, f02=»rt «, f03=»FE «, f04=»TILBUD part 4 «, f05=22-07-82 10:15, f06=» 3 «, f07=»09 «, f08=» 24001 «, f09=04-08-82 13:05, f10=» «, f11=»02 «, f12=» 12 «, f13=04-08-82 12:38, f14=06-08-82 11:04, f15=»0211A «, f16=»093 «, f17=» 18 «, f18=»34 «, f19=»01980 «, f20=» 88272 «, f21=» «, f22=» «, f99=400009000110056610110190aaca1505000000000000014203b801df}
0x20100…20200 (32, 0, 1) WangDocumentBody
[…0x36…]
0x23800…23900 (35, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(35,0, 9), len=0xff, h3=41255841}, f00=»2558A «, f01=»MWHQ - tilbud «, f02=»pc «, f03=»ALF «, f04=»PRICE PROPOSAL «, f05=28-07-82 16:25, f06=» 2 «, f07=»44 «, f08=» 10983 «, f09=16-11-82 11:20, f10=» «, f11=»02 «, f12=» 75 «, f13=25-10-82 15:12, f14=04-11-83 11:36, f15=»0211A «, f16=» 26 «, f17=» 15 «, f18=»23 «, f19=» 364 «, f20=» 47021 «, f21=» «, f22=» «, f99=020040000110056610110480aaca15050000000000000142037700df}
0x23900…23a00 (35, 0, 9) WangDocumentBody
[…0x6…]
0x24000…24100 (36, 0, 0) Sector 2401ff00255841 ┆$ %XA Description Quantity 1. Word Processor(WP) 3 2. Line Printer(LP) 2 3. Teleprinter(TP) Supplied by Signaal 4. X-Net Controller(XCT) 1 5. Dual Terminal Adapter(XTA) 12 6. Floppy Disc Controller(XF┆
0x24100…24200 (36, 0, 1) Sector 2402ff00255841 ┆$ %XAD) 3 7. Floppy Disc Drive(FDD) 10 8. X-Net Administrator(XNA) 1 9. X-Net Port(XNP) 4 x V.24 1 8 x V.24 2 10. Low-Level Adapter(LLA) V.28 - 188c 15 V.28 - V11 18 11. Racks Supplied by Signaal 12. Crates 2 ┆
0x24200…24300 (36, 0, 2) Sector 24038600255841 ┆$ %XA13. PWR 2 14. FAN 2 15. Mains Filter/Switch 2 16. Bus Outlet 15 17. X-Net Cabling 100 Metres<~ B -!/=6'C*-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x24300…24400 (36, 0, 3) Sector 2404ff00255841 ┆$ %XA 1 2.2.2 Single Items The items listed below in this sub-section will be supplied in the quantities stated, i.e. not duplicated Decription Quantity 1. VDU 12 5 inch FLOPPY-D┆
0x24400…24500 (36, 0, 4) Sector 2405ff00255841 ┆$ %XAISC 150 (125 with protective cover) 2. Spares 1 month supply 2.2.3 Software and Service The software and service items listed below in this sub-section will be supplied: o System Operating Software o Application Software o Support Equi┆
0x24500…24600 (36, 0, 5) Sector 2406ff00255841 ┆$ %XApment o Documentation o Training Description of these items are given in the Engineering Proposal, Part III 2.3 Options Two training course options are offered; they are described in the section on training - Sec. 3 - in Part III of the propo┆
0x24600…24700 (36, 0, 6) Sector 2407ff00255841 ┆$ %XAsal. Prices for the training options are given in section 3 of this price proposal as "Stand-Alone" prices, i.e. they must be added to the price of the MEDS if the options are taken. Documentation for depot maintenance using a GENRAD tester is als┆
0x24700…24800 (36, 0, 7) Sector 2308ff00255841 ┆# %XAo included as an option. If the CR proposal to use a ZEHNTEL tester is accepted by DMKL, then this documentation is not needed and the depot maintenance course can be replaced by a field maintenance course. After-warranty maintainence would be sup┆
0x24800…24900 (36, 0, 8) Sector 2409ff00255841 ┆$ %XA.................. 4 2.1 BASIC OFFER ................................. 4 2.2 DELIVERABLE ITEMS ........................... 5 2.3 OPTIONS ..................................... 6 3. PRICE ....................................... 7 ┆
0x24900…24a00 (36, 0, 9) Sector 240aff00255841 ┆$ %XA3.1 WORK BREAKDOWN STRUCTURE .................... 7 3.2 WORK UNIT COST BREAKDOWN .................... 12 3.3 PROJECT COST ................................ 24 4. RELEVANT TERMS AND CONDITIONS ............... 27 4.1 CONTRACT CONDITIONS .┆
0x24a00…24b00 (36, 0, 10) Sector 240bff00255841 ┆$ %XA........................ 27 4.2 TAXES AND DUTIES ............................ 27 4.3 TERMS OF PAYMENT ............................ 27 4.4 VALIDITY .................................... 27 4.5 PATENT RIGHTS ............................... ┆
0x24b00…24c00 (36, 0, 11) Sector 240c7f00255841 ┆$ %XA 27 4.6 MARKETING AGREEMENT ......................... 27 4.7 FOREIGN PROCUREMENT.......................... 27 ger) (Udf]rer) Inds`t hvilket? Slette hvilket? Flytte hvilket? Kopiere hvilket? Bytte hvilket? Bytte med? S]ge hvilket? ┆
0x24c00…24d00 (36, 0, 12) Sector 240dff00255841 ┆$ %XA 1 1. INTRODUCTION PART II of the proposal for the MESSAGE ENTRY and DISTRIBUTION SYSTEM of the MOBILE WAR HEADQUARTERS (MWHQ-MEDS) for the Dutch Army contains the price proposal pre┆
0x24d00…24e00 (36, 0, 13) Sector 240eff00255841 ┆$ %XApared by Christian Rovsing A/S for Hollandse Signaalaparaten B.V. 2. SCOPE OG WORK 2.1 Basic Offer The Scope of work of this proposal for the MESSAGE ENTRY AND DISTRIBUTION SYSTEMS (MEDS) covers: o MEDS Project Management o System Enginee┆
0x24e00…24f00 (36, 0, 14) Sector 240fc200255841 ┆$ B %XAring o Hardware o Software o Quality Assurance o Reliability o Transport and Installation Aid o Acceptance Testing o Training o Maintenance and Spares o Documentation o Options 1A 26 15 21 444 46951 @ f *J B _┆
0x24f00…25000 (36, 0, 15) Sector 2400ff00255841 ┆$ %XA 1 2.2 Deliverable Items 2.2.1 Duplicated Items The set of items to follow will be supplied in duplicate, i.e. two(2) sets are to be delivered. 1 ┆
0x25000…25100 (37, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(37,0, 1), len=0xff, h3=41255841}, f00=»2558A «, f01=»MWHQ - tilbud «, f02=»pc «, f03=»ALF «, f04=»PRICE PROPOSAL «, f05=28-07-82 16:25, f06=» 2 «, f07=»44 «, f08=» 10983 «, f09=16-11-82 11:20, f10=» «, f11=»00 «, f12=» 5 «, f13=25-10-82 15:12, f14=19-01-83 14:09, f15=»0211A «, f16=» 26 «, f17=» 15 «, f18=»21 «, f19=» 444 «, f20=» 46951 «, f21=» «, f22=» «, f99=020040000110056610110480aaca15050000000000000142037700df}
0x25100…25200 (37, 0, 1) Sector 25021a00255841 ┆% %XA % % % $ $ $ # # # # " " " " ! ! ! ! DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET T ┆
0x25200…25300 (37, 0, 2) Sector 25037e00255841 ┆% ~ %XA 1 SYS/821020 # MWHQ - PRICE PROPOSAL MWHQ-MEDS Z -C7-:!<~ B -!/=6'C*-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x25300…25400 (37, 0, 3) Sector 2504ff00255841 ┆% %XA 1 PART II PRICE PROPOSAL MWHQ MESSAGE ENTRY and DISTRIBUTION SYSTEM Revised 22nd October 1982 CHRISTIAN ROVSING A/S This document contains infor┆
0x25400…25500 (37, 0, 4) Sector 2505ff00255841 ┆% %XAmation proprietary to Christian Rovsing A/S. The information, whether in the form of thext, schematics, tables, drawings or illustrations, must not be duplicated or used for purposed other than evaluation, or disclosed outside the recepient company┆
0x25500…25600 (37, 0, 5) Sector 2506ff00255841 ┆% %XA or organisation without the prior, written permission of Christian Rovsing A/S. This restriction does not limit the recipient's right to use information contained in the document if such information is received from another source without restric┆
0x25600…25700 (37, 0, 6) Sector 25077300255841 ┆% s %XAtion provided such source is not in brach of an obligation of confidentialty towards Christian Rovsing A/S. !"<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 ┆
0x25700…25800 (37, 0, 7) Sector 2408ff00255841 ┆$ %XA 1 TABLE OF CONTENTS 1. INTRODUCTION ................................ 4 2. SCOPE OF WORK .............┆
0x25800…25900 (37, 0, 8) Sector 25091800249941 ┆% $ Aided in phase I. 5.2.3.6 WP 236: Data Channel The design of the existing data channel is used as the basis for the design of the high speed data channel, connecting the processing chain with the S┆
0x25900…25a00 (37, 0, 9) Sector 250aff00249941 ┆% $ A 1 This work package covers the following activities: WP 332.1: FPP hardware detailed design, development and test WP 332.2: Basic firmware detailed design development and coding ┆
0x25a00…25b00 (37, 0, 10) Sector 250bff00249941 ┆% $ A WP 332.3: HW/FW integration and test WP 332.4: FPP handler design, development, coding and test WP 332.5: HW/FW/SW integration WP 332.6: M & D software design, development, coding and test. WP 332.7: Built-In-Tese design, development, codi┆
0x25b00…25c00 (37, 0, 11) Sector 250cff00249941 ┆% $ Ang and test. 5.3.3.3 WP 333: Spatial Resampling This work package covers all the software and firmware efforts required for performing the Spatial Resampling. The design, development, coding and testing of the following modules are comprised:┆
0x25c00…25d00 (37, 0, 12) Sector 250d7200249941 ┆% r $ A WP 333.1: Parameter calculation and formatting WP 333.2: Resample Driver WP 333.3: Output Handler kage covers the effort required for the procurement of all items at module level and above of the SDPS System. The activities are: WP 241┆
0x25d00…25e00 (37, 0, 13) Sector 250eff00249941 ┆% $ A 1 5.3.3.4 WP 334: Time Resampling This work package covers the software and firmware efforts required for performing the Time Resampling. The design, development, coding and testi┆
0x25e00…25f00 (37, 0, 14) Sector 250fff00249941 ┆% $ Ang of the following modules are comprised: WP 334.1: Parameter calculation and formatting WP 334.2: Resample driver WP 334.3: Output Handler 5.3.3.5 WP 335: SEG-D Formatter This work package covers the effort for the design, development, ┆
0x25f00…26000 (37, 0, 15) Sector 2500ff00249941 ┆% $ Acoding and test of the DEMUX SEG-D module. 5.3.3.6 WP 336: 1 MW RAM The design of the existing 128K RAM is used as the basis for the 1 MW RAM. The activities of this work package cover the re-design, test and manufacturing documentation for t┆
0x26000…26100 (38, 0, 0) Sector 2601ff00249941 ┆& $ A 1 5.2.6 WP 260: Delivery This work package covers all efforts required for the transportation and installation of the phase II delivery. The following activities are foreseen: W┆
0x26100…26200 (38, 0, 1) Sector 2602ff00249941 ┆& $ AP 261: Packing and shipping WP 262: Installation and verification Checkout 5.2.7 WP 270: Acceptance Test This work package covers the formal customer acceptance testing, evaluation and reporting. 5.3 Phase III: Implementation of Preprocess┆
0x26200…26300 (38, 0, 2) Sector 2603ff00249941 ┆& $ Aing System This Preliminary Phase III Project implementation plan is to be replaced by the one provided from WP 210 during phase II. Phase III starts after the phase II review. Working meetings will be held as needed, and design reviews will be ┆
0x26300…26400 (38, 0, 3) Sector 2604ff00249941 ┆& $ Aheld at the following milestones: D.R.5: Phase III HW design complete Phase III SW design complete D.R.6: HW prototypes and SW modules have been tested individually. See work breakdown on figure 5-3 overleaf. 5.3.1 WP 310: Phase III Mana┆
0x26400…26500 (38, 0, 4) Sector 26056000249941 ┆& ` $ Agement The activities are as described for WP 210, excluding the phase III planning. Formatter Software The MUX SEG-D software required for the Raw Data recording is designed, developed, coded and tested. 5.2.3.5 WP 235: 6250 BPI Tape Th┆
0x26500…26600 (38, 0, 5) Sector 2606ff00249941 ┆& $ A 1 5.3.2 WP 320: System Engineering The activities are as described for WP 220. 5.3.3 WP 330: Module Implementation This work package covers the efforts required for the provis┆
0x26600…26700 (38, 0, 6) Sector 2607ff00249941 ┆& $ Aion of the remaining modules for the upgrading of the phase II delivery to a full preprocessing system. 5.3.3.1 WP 331: SDI/MTC mfg. Documentation This work package covers the activities for providing the Printed Circuit Board (PCB) version of ┆
0x26700…26800 (38, 0, 7) Sector 2508ff00249941 ┆% $ Athe SDI and Tape Controller, i.e. manufacturing documentation, including PCB layout and testing. 5.3.3.2 WP 322: Floating Point Processor The FPP hardware, firmware and software is implemented according to the corresponding specifications, prov┆
0x26800…26900 (38, 0, 8) Sector 2609ff00249941 ┆& $ A 1 5.2.3.6 WP 236: Data Channel The design of the existing data channel is used as the basis for the design of the high speed data channel, connecting the processing chain with the S┆
0x26900…26a00 (38, 0, 9) Sector 260aff00249941 ┆& $ Atorage and I/O Unit. The activities are WP 236.1: Re-design, testing and manufacturing of the Data Channel Adapter (DACA) WP 236.2: Re-design, testing and manufacturing of the Data Channel Interface (DCI) WP 236.3: Re-design, coding and test┆
0x26a00…26b00 (38, 0, 10) Sector 260bff00249941 ┆& $ Aing of M & D Software 5.2.3.7 WP 237: Test Software This work package covers the Software efforts for performing the phase II Factory and Acceptance Test. The activities include: WP 237.1: Design, development, coding and testing of phase II┆
0x26b00…26c00 (38, 0, 11) Sector 260c8a00249941 ┆& $ A Factory Test SW. WP 237.2: Modifications to the phase II Factory Test Software to achieve the phase II Acceptance Test Software. ementation The work breakdown follows the modular approach of the hardware and software. This work package is a n┆
0x26c00…26d00 (38, 0, 12) Sector 260dff00249941 ┆& $ A 1 5.2.4 WP 240 Procurement This work package covers the effort required for the procurement of all items at module level and above of the SDPS System. The activities are: WP 241┆
0x26d00…26e00 (38, 0, 13) Sector 260eff00249941 ┆& $ A: Specification An ordering specification is worked out, based upon the proper Hardware Specification WP 242: Ordering and follow-up. Supplier schedule control WP 243: Incoming inspection and test The procurement action follows the ┆
0x26e00…26f00 (38, 0, 14) Sector 260fff00249941 ┆& $ Asame procedure for as well in-house products as bought-out equipment. 5.2.5 WP 250: System Integration This work package covers all the effort required for the integration and verification checkout of all hardware modules and equipment, and of ┆
0x26f00…27000 (38, 0, 15) Sector 2600fd00249941 ┆& } $ Aall software modules. The activities comprise: WP 251: Hardware mechanical integration WP 252: Hardware electrical subsystem and system integration testing WP 253: Software integration WP 254: Factory test, evaluation and reporting ┆
0x27000…27100 (39, 0, 0) Sector 2701ff00249941 ┆' $ AWP 232.1: Mechanical design at rack-level and front panel layout. WP 232.2: Electrical design, PU crate WP 232.3: Electrical design, S-I/O crate WP 232.4: Specification of cables 5.2.3.3 WP 233: Seismic Data Interface The SDI hardware┆
0x27100…27200 (39, 0, 1) Sector 2702ff00249941 ┆' $ A, firmware and software is implemented according to the corresponding specifications, provided in phase I. This work package covers the following activities: WP 233.1: Detailed SDI and Adapter hardware design, development, manufacturing and prel┆
0x27200…27300 (39, 0, 2) Sector 2703ff00249941 ┆' $ Aiminary test. This module will be delivered in a wire-wrap version. WP 233.2: Detailed firmware design development and coding WP 233.3: HW/FW integration and test WP 233.4: SDI handler detailed design, development, coding and test WP 23┆
0x27300…27400 (39, 0, 3) Sector 2704bb00249941 ┆' ; $ A3.5: HW/FW/SW integration WP 233.6: Maintenance & Diagnostic (M&D) Software design, development, coding and test WP 233.7 Built-In-Test design, development, coding and test. nation of activities o Schedule control o Action item control ┆
0x27400…27500 (39, 0, 4) Sector 2705ff00249941 ┆' $ A 1 5.2.3.4 WP 234: SEG-D Formatter Software The MUX SEG-D software required for the Raw Data recording is designed, developed, coded and tested. 5.2.3.5 WP 235: 6250 BPI Tape Th┆
0x27500…27600 (39, 0, 5) Sector 2706ff00249941 ┆' $ Ae firmware and software is implemented according to the corresponding specification provided in phase I. The design of the controller hardware is made under WP 233.1. The following activities are covered: WP 235.1: Adapter design and development┆
0x27600…27700 (39, 0, 6) Sector 2707ff00249941 ┆' $ A. Controller and Adapter hardware manufacturing and preliminary test. This module will be delivered in a wire-wrap version. WP 235.2: Detailed firmware development and coding WP 235.3: HW/FW integration and test WP 235.4: Handler, detaile┆
0x27700…27800 (39, 0, 7) Sector 2608f300249941 ┆& s $ Ad design, development, coding and test WP 235.5: HW/FW/SW integration WP 235.6: Maintenance and diagnostic (M & D) Software design, development, coding and test. WP 235.7: Built-In-Test design, development, coding and test re o Qua┆
0x27800…27900 (39, 0, 8) Sector 2709ff00249941 ┆' $ Ality control on hardware design, manufacturing and documentation o Quality control on software design and documentation o Configuration and change control o Reliability Supervision, control, analysis, trade-offs, testing Output: ┆
0x27900…27a00 (39, 0, 9) Sector 270a4400249941 ┆' D $ AInspection and test procedures Inspection and test reports 5.1.3 WP 130: System Design Specification (SDS) Purpose: The SDS shall provide the basis for a systems design which implements the required qualities. Activities: A system desig┆
0x27a00…27b00 (39, 0, 10) Sector 270bff00249941 ┆' $ A 1 WP 223: Test plans and procedures Purpose: Assuring Correct and reproducible tests, according to the requirements. Activities: Preparation of test plans and procedures Outpu┆
0x27b00…27c00 (39, 0, 11) Sector 270cff00249941 ┆' $ At: Factory test plan Factory test procedure Acceptance test plan Acceptance test procedure 5.2.3 WP 230: Module Implementation The work breakdown follows the modular approach of the hardware and software. This work package is a n┆
0x27c00…27d00 (39, 0, 12) Sector 270dff00249941 ┆' $ Aumber of sub-packages, each covering essentially all effort for the detailed design, development, manufacturing/coding and testing of all hard, firm and software required for the particular module. 5.2.3.1 WP 231: System Management The system m┆
0x27d00…27e00 (39, 0, 13) Sector 270eff00249941 ┆' $ Aanagement software is designed, developed, coded and tested according to the detailed design specification, provided in WP 222.2. The following modules are designed, developed, coded and tested: WP 231.1: Man-Machine Interface WP 231.2: Messag┆
0x27e00…27f00 (39, 0, 14) Sector 270f7700249941 ┆' w $ Ae Interpreter WP 231.3: Device Control and Monitor WP 231.4: Error Status Interpreter WO 232.5: Logging customer Output: SDPS Test Requirement Specification 5.1.7 WP 170: Documentation Requirement Specification Activities: Definiti┆
0x27f00…28000 (39, 0, 15) Sector 2700ff00249941 ┆' $ A 1 5.2.3.2 WP 232: Mechanical and electrical design This work package covers efforts related to the housing and interconnection of crates. The following activities are included: ┆
0x28000…28100 (40, 0, 0) Sector 2801ff00249941 ┆( $ A 1 5.2 Phase II: Implementation of Raw Data Recording System This preliminary phase II Project Implementation plan is to be replaced by the one, provided from WP 110 during phase I. ┆
0x28100…28200 (40, 0, 1) Sector 2802ff00249941 ┆( $ A The implementation phase starts after customer approval of the specifications, and working meetings will be held as needed. Design review will be held at the following milestones D.R.1: Phase II HW design complete Phase II SW design complet┆
0x28200…28300 (40, 0, 2) Sector 2803ff00249941 ┆( $ Ae D.R.2: HW prototypes have been tested individually SW modules have been tested individually D.R.3: HW/SW integration on subsystem level complete D.R.4: Phase II review Installation of phase II and Acceptance test successfully complete┆
0x28300…28400 (40, 0, 3) Sector 2804ff00249941 ┆( $ Ad See work breakdown on figure 5-2 overleaf 5.2.1 WP 210: Phase II Management The activities are a) Project management o Interface and communication with GECO o Coordination of activities o Schedule control o Action item control ┆
0x28400…28500 (40, 0, 4) Sector 2805f400249941 ┆( t $ Ab) Documentation, Reporting o Progress reports (monthly) o Arrange for meetings and reviews o Prepare schedules, agendas and minutes c) Phase III planning Output: Progress Reports Phase III Project Implementation Plan (SDS) .....┆
0x28500…28600 (40, 0, 5) Sector 2806ff00249941 ┆( $ A 1 5.2.2 WP 220: System Engineering The System engineering comprises o Technical coordination o Quality Assurance o Test plans and procedures WP 221: Technical coordination ┆
0x28600…28700 (40, 0, 6) Sector 2807ff00249941 ┆( $ APurpose: To assure the implementation of a system which fulfils the technical requirements The activities are o Technical coordination of all hardware and software development and procurement activities o Participation in all internal and ┆
0x28700…28800 (40, 0, 7) Sector 2708ff00249941 ┆' $ Aexternal technical reviews o Performance analysis Output: Engineering notes Test plans and procedures specification WP 222: Quality Assurance Purpose: To assure that required levels of quality are met The activities are o Qua┆
0x28800…28900 (40, 0, 8) Sector 28093100249941 ┆( 1 $ AOutput: SDPS Requirements Specification 5.2.3.6 WP 236: Data Channel ............... 5.2.3.7 WP 237: Test Software .............. 5.2.4 WP 240: Procurement .................... 5.2.5 WP 250: System Integration .┆
0x28900…28a00 (40, 0, 9) Sector 280aff00249941 ┆( $ A 1 5.1.3 WP 130: System Design Specification (SDS) Purpose: The SDS shall provide the basis for a systems design which implements the required qualities. Activities: A system desig┆
0x28a00…28b00 (40, 0, 10) Sector 280bff00249941 ┆( $ An specification is made based on the agreed requirements specification. The specification will, for example, consist of: 1 o system architecture, SW & HW o specification of major i┆
0x28b00…28c00 (40, 0, 11) Sector 280cb200249941 ┆( 2 $ Anterfaces, SW & HW o system performance o system operation 1 Output: System Design Specification 5.3.3.6 WP 336: 1 MW RAM ................... 5.3.3.7 WP 337: Test┆
0x28c00…28d00 (40, 0, 12) Sector 280dff00249941 ┆( $ A 1 5.1.4 WP 140: Hardware Specification Purpose: To assure a coherent hardware design with the required performance Activities: Specification of all hardware items to module level┆
0x28d00…28e00 (40, 0, 13) Sector 280eff00249941 ┆( $ A Output: SDPS Hardware Specification 5.1.5 WP 150: Software Specification Purpose: To assure a coherent software design with the requires performance Activities: Specification of all software to module level Output: SDPS Software Specif┆
0x28e00…28f00 (40, 0, 14) Sector 280fff00249941 ┆( $ Aication 5.1.6 WP 160: Test Requirement Spec. Activities: Definition of test requirements in cooperation with customer Output: SDPS Test Requirement Specification 5.1.7 WP 170: Documentation Requirement Specification Activities: Definiti┆
0x28f00…29000 (40, 0, 15) Sector 28008200249941 ┆( $ Aon of requirements to documentation in cooperation with customer Output: SDPS Documentation Requirement Specification ign, development, procurement, integration and delivery of a subset of the phase III delivery, capable of recording i┆
0x29000…29100 (41, 0, 0) Sector 2901ff00249941 ┆) $ An Raw Data mode Phase III: Design, development, procurement, integration and delivery of upgrades to the phase II delivery to provide the full SDPS processing system. As working-assumptions for this proposal, we have presumed the┆
0x29100…29200 (41, 0, 1) Sector 2902ff00249941 ┆) $ A following: a) The phase II delivery is returned TBD months after the delivery for upgrading to the full SDPS System. b) The customer furnishes a simulator which provides an interface equivalent to the "NESSIE", and sufficient types of test data┆
0x29200…29300 (41, 0, 2) Sector 2903ff00249941 ┆) $ A for development and, in particular, for the Acceptance testing. We want to emphasize that we are prepared to discuss alternatives to these working assumptions, or to other explicit or implicit presumptions. 5.1 Phase I: Specification Phase I┆
0x29300…29400 (41, 0, 3) Sector 2904ff00249941 ┆) $ A consists of a detailed requirement analysis and specification of the system to be provided in phase II and phase III. This is made in close cooperation between the customer and the contractor. The output from phase I is a mutually agreed upon tec┆
0x29400…29500 (41, 0, 4) Sector 29054900249941 ┆) I $ Ahnical specification for the SDPS, and a planning for phase II. .................. 5.1.1 WP 110: Phase I Management ............. 5.1.2 WP 120: Requirements Definition ........ 5.1.3 WP 130: System Design Spec. (SDS) .....┆
0x29500…29600 (41, 0, 5) Sector 2906ff00249941 ┆) $ A 1 5.1.1 WP 110: Phase I management The activities are a) Project management o Interface and communication with GECO o Coordination of activities o Schedule control o Acti┆
0x29600…29700 (41, 0, 6) Sector 2907ff00249941 ┆) $ Aon item control b) Documentation, reporting o Progress reports (monthly) o Arrange for meetings and reviews o Prepare schedules, agendas and minutes c) Phase II Planning Output: Progress reports Phase II Project Implementation Plan ┆
0x29700…29800 (41, 0, 7) Sector 2808ff00249941 ┆( $ A 5.1.2 WP 120: Requirements Definition Purpose: Definition of requirements in view of the proposed system design. Activities: Detailed review of the requirements in close cooperation with the customer and with the technical solution in view. ┆
0x29800…29900 (41, 0, 8) Sector 2909ff00249941 ┆) $ A2.3.5 WP 235: 6250 PBI Tape .............. 5.2.3.6 WP 236: Data Channel ............... 5.2.3.7 WP 237: Test Software .............. 5.2.4 WP 240: Procurement .................... 5.2.5 WP 250: System Integration .┆
0x29900…29a00 (41, 0, 9) Sector 290aff00249941 ┆) $ A............ 5.2.6 WP 260: Delivery ....................... 5.2.7 WP 270: Acceptance Test ................ 5.3 Phase III: Implementation of Preprocessing . System .......................... 5.3.1 WP 310┆
0x29a00…29b00 (41, 0, 10) Sector 290bff00249941 ┆) $ A: Phase III Management ........... 5.3.2 WP 320: System Engineering ............. 5.3.3 WP 330: Module Implementation .......... 5.3.3.1 WP 331: SDI/MTC mfg. Documentation . 5.3.3.2 WP 322: Floating Point Processor ┆
0x29b00…29c00 (41, 0, 11) Sector 290cff00249941 ┆) $ A... 5.3.3.3 WP 333: Spatial Resampling ......... 5.3.3.4 WP 334: Time Resampling ............ 5.3.3.5 WP 335: SEG-D Formatter ............ 5.3.3.6 WP 336: 1 MW RAM ................... 5.3.3.7 WP 337: Test┆
0x29c00…29d00 (41, 0, 12) Sector 290dff00249941 ┆) $ A Software .............. 5.3.4 WP 340: Procurement .................... 5.3.5 WP 350: System Integration ............. 5.3.6 WP 360: Delivery ....................... 5.3.7 WP 370: Acceptance Test ................ ┆
0x29d00…29e00 (41, 0, 13) Sector 290e7600249941 ┆) v $ A 5.3.8 WP 380: Documentation .................. 5.3.9 WP 390: Training ....................... ┆
0x29e00…29f00 (41, 0, 14) Sector 290fff00249941 ┆) $ A 1 5 PROJECT IMPLEMENTATION PLAN This section describes the proposed implementation plan for the Seismic Data Preprocessing System. See figure 5-1 overleaf. The work is divided i┆
0x29f00…2a000 (41, 0, 15) Sector 2900ff00249941 ┆) $ Anto three phases. Phase I: System specification, Hardware specification and Software specification Phase II: Design, development, procurement, integration and delivery of a subset of the phase III delivery, capable of recording i┆
0x2a000…2a100 (42, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(42,0, 1), len=0xff, h3=41249941}, f00=»2499A «, f01=»GECO «, f02=»pan «, f03=»PEH «, f04=»Management Proposal «, f05=22-07-82 13:51, f06=» 3 «, f07=»26 «, f08=» 14316 «, f09=04-08-82 09:40, f10=» «, f11=»56 «, f12=» 1399 «, f13=04-08-82 12:51, f14=06-08-82 11:06, f15=»0211A «, f16=» 19 «, f17=» 12 «, f18=»31 «, f19=» 360 «, f20=» 49227 «, f21=» «, f22=», «, f99=020010000110052710110290aaca15050000000000000142035d00df}
0x2a100…2a200 (42, 0, 1) Sector 2a021300249941 ┆* $ A * * ) ) ( ( ( ( ' ' ' & & & & % % % % $ DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO T T T Kommentarer: ┆
0x2a200…2a300 (42, 0, 2) Sector 2a03b400249941 ┆* 4 $ A 1 SEISMIC DATA PREPROCESSING SYSTEM 1982-07-30 SECTION II MANAGEMENT PROPOSAL I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x2a300…2a400 (42, 0, 3) Sector 2a04ff00249941 ┆* $ A 1 1 5 PROJECT IMPLEMENTAT┆
0x2a400…2a500 (42, 0, 4) Sector 2a05ff00249941 ┆* $ AION PLAN .................... 5.1 Phase I: Specification ..................... 5.1.1 WP 110: Phase I Management ............. 5.1.2 WP 120: Requirements Definition ........ 5.1.3 WP 130: System Design Spec. (SDS) .....┆
0x2a500…2a600 (42, 0, 5) Sector 2a06ff00249941 ┆* $ A. 5.1.4 WP 140: Hardware Specification ......... 5.1.5 WP 150: Software Specification ......... 5.1.6 WP 160: Test Requirement Spec. ......... 5.1.7 WP 170: Documentation Requirement Spec.. 5.2 Phase II: Imple┆
0x2a600…2a700 (42, 0, 6) Sector 2a07ff00249941 ┆* $ Amentation of Raw Data Recording System ................. 5.2.1 WP 210: Phase II Management ............ 5.2.2 WP 220: System Engineering ............. 5.2.3 WP 230: Module Implementation .......... 5.2.3.1┆
0x2a700…2a800 (42, 0, 7) Sector 2908ff00249941 ┆) $ A WP 231: System Management .......... 5.2.3.2 WP 232: Mechanical and Electrical Design ..................... 5.2.3.3 WP 233: Seismic Data Interface ..... 5.2.3.4 WP 234: SEG-D Formatter Software ... 5.┆
0x2a800…2a900 (42, 0, 8) Sector 2a09ff00103141 ┆* 1A had stopped at a level ensuring that the lowest identified software module did not exceed 250 SWELL statements. Furthermore, the identified functions are arranged in a logically correct order that satisfies a structured allocation of software modu┆
0x2a900…2aa00 (42, 0, 9) Sector 2a0aff00103141 ┆* 1Ales. 4.2.1.2.1 ACP127 Analysis Module (1.0) This is the highest level module the function of which is to: a) receive queue-elements from the ANQ. b) determine the originator of the message and based upon this information initiate either the┆
0x2aa00…2ab00 (42, 0, 10) Sector 2a0b4200103141 ┆* B 1A incoming analysis, complete analysis or the PTR analysis. =~ BL5C`5M{) RV5Cq5M . R`5Cq5M@1MI1:h= Rp5Cr4IMM.:^=~ B}5I:g=~ J 5IC$3I > S C_* ┆
0x2ab00…2ac00 (42, 0, 11) Sector 2a0cff00103141 ┆* 1A 1 c) when it gets control again, it will dismantle the queue-element from the ANQ that triggers all during the analysis sent message-views and commands to be checkpointed. d) befor┆
0x2ac00…2ad00 (42, 0, 12) Sector 2a0dff00103141 ┆* 1Ae returning to the start-point it will send a completion-code to the Incoming MSO command queue, if these procedures had been involved. 4.2.1.2.2 Level 1 Modules The level 1 modules are the Incoming analysis, the Complete analysis and the PTR a┆
0x2ad00…2ae00 (42, 0, 13) Sector 2a0eff00103141 ┆* 1Analysis modules. They will as input receive the information associated to the message view and the queue-element (View-info and Queue-info). Their functions are to control the lower level modules from where they receive control information that ┆
0x2ae00…2af00 (42, 0, 14) Sector 2a0fff00103141 ┆* 1Aforms the processing through that analysis. 4.2.1.2.2.1 Incoming Analysis Module (2.0) On the basis of already existing information and information supplied by the lower level modules (Info. Field, View Info. and Queue Info.) this module will ┆
0x2af00…2b000 (42, 0, 15) Sector 2a00ff00103141 ┆* 1Asequentially activate the needed modules to fulfil an incoming analysis. a) Initiate an incoming analysis: - determine the message type - set up pointers to the incoming analysis guide table. b) Determine if errors had occured during recept┆
0x2b000…2b100 (43, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(43,0, 1), len=0xff, h3=41103141}, f00=»1031A «, f01=»TRAFFIC HANDLING SW PACK. «, f02=»sdv «, f03=»KNB «, f04=»CPS/SDS/010, 4.2.1.2 «, f05=10-06-81 13:17, f06=» 12 «, f07=»59 «, f08=» 64043 «, f09=28-07-81 10:45, f10=» «, f11=»01 «, f12=» 28 «, f13=28-07-81 10:46, f14=29-07-81 12:29, f15=»0060A «, f16=» 83 «, f17=» 15 «, f18=»29 «, f19=» 944 «, f20=» 67867 «, f21=» «, f22=» @ «, f99=050010000110066610110480aaca15050000000000000037033101df}
0x2b100…2b200 (43, 0, 1) Sector 2b025300103141 ┆+ S 1A9 + + * * ) ) ) ( ( ' ' ' & & & & % % % % % % $ $ $ $ $ # # # # # # # # " " " " " " " " " ! ! ! ! ! D D D┆
0x2b200…2b300 (43, 0, 2) Sector 2b038b00103141 ┆+ 1A 1 CPS/SDS/010 KNB/810801 TRAFFIC HANDLING CAMPS -!/=6'C*-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x2b300…2b400 (43, 0, 3) Sector 2b04ff00103141 ┆+ 1A 1 4.2.1.2 Software Specification The structure of the ACP127 Analysis Subpackage is of uncomplex nature. It is one process receiving messages from the analysis Queue (ANQ) in an u┆
0x2b400…2b500 (43, 0, 4) Sector 2b05ff00103141 ┆+ 1Anlimited loop. The ANQ is organized on FIFO basis with one subqueue for flash and one for non-flash, plus a command subqueue to be used by SSC and TEP (reentering MSO). Because paging and unpaging of messages in ACP127 format is provided within t┆
0x2b500…2b600 (43, 0, 5) Sector 2b06ff00103141 ┆+ 1Ahe Transport Subpackage, this subpackage will not need to examine the text part of a message and will therefore have a good performance that will be satisfied with the use of a FIFO-queue. If however, these calculations should fail when coming to r┆
0x2b600…2b700 (43, 0, 6) Sector 2b07ff00103141 ┆+ 1Aeality, the Analysis Process can be implemented as two incarnated coroutines. The software structure of the analysis Process will be described in detail in the following. As reference to this description, the functional break down in section 4.2┆
0x2b700…2b800 (43, 0, 7) Sector 2a08ff00103141 ┆* 1A.1.1, the HIPO-diagrams and Flowgrams in section 4.2.1.3 will be used. Also this description will expand these sections to some extent. The functional break-downs depicted in figures 4.2.1.1-1 to 4.2.1.1-4 are kept on a level where the break-down┆
0x2b800…2b900 (43, 0, 8) Sector 2b097400102941 ┆+ t )AAnalysis (2.8) Finish Complete Analysis (3.3) Finish PTR Analysis (4.3) ....... 119 ......................... 39 3.3.2.7 Interface SSC ........................... 40 3.4 FUNCTIONS MAINTAINED BY OTHER PACKAGES.....┆
0x2b900…2ba00 (43, 0, 9) Sector 2b0aff00102941 ┆+ )A 1 4.2.1.2.4 Level 3 Modules ..................... 119 4.2.1.2.4.1 Message Type Determination Module .......................... 119 4.2.1.2.4.2 Relaying M┆
0x2ba00…2bb00 (43, 0, 10) Sector 2b0bff00102941 ┆+ )Aodule (2.4.2.3) ....... 120 4.2.1.2.4.3 Pilot Detect Module (2.4.2.2) ... 120 4.2.1.3 Data Flow and Control Logic............ 122 4.2.1.4 Subpackage Data........................ 159 4.2.1.4.1 Analysis Guide Tables.............┆
0x2bb00…2bc00 (43, 0, 11) Sector 2b0cff00102941 ┆+ )A. 159 4.2.1.4.2 Analysis Buffer.................... 166 4.2.1.4.3 Error List......................... 166 4.2.1.4.4 RI-List............................ 167 4.2.1.4.5 HQ/SIC List........................ 167 4.2.1.4.6 PLA┆
0x2bc00…2bd00 (43, 0, 12) Sector 2b0dff00102941 ┆+ )A List........................... 168 4.2.1.4.7 Operating Signals List............. 169 4.2.1.5 Interfaces............................. 169 4.2.1.5.1 Application Interface.............. 171 4.2.1.5.1.1 Interface MDP AAS to MDP┆
0x2bd00…2be00 (43, 0, 13) Sector 2b0eff00102941 ┆+ )A ........ 171 4.2.1.5.1.2 Interface TEP AAS to TEP ........ 171 4.2.1.5.1.3 Interface TRS AAS to TRS ........ 172 4.2.1.5.1.4 Interface ACS AAS to ACS ........ 173 4.2.1.5.1.5 Interface Log ................... 174 4.2.1┆
0x2be00…2bf00 (43, 0, 14) Sector 2b0fff00102941 ┆+ )A.5.1.6 Interface STP ................... 174 4.2.1.5.1.7 Interface SAR ................... 174 4.2.2 ACP127 Conversion Subpackage............... 175 4.2.2.1 Functional Specification............... 175 4.2.2.1.1 Routing Function┆
0x2bf00…2c000 (43, 0, 15) Sector 1d00ff00102941 ┆ )As.................. 175 4.2.2.1.2 ACP127 Formatting Functions........ 178 4.2.2.1.3 Traffic Separation Functions....... 179 4.2.2.2 Software Specification................. 185 4.2.2.2.1 ACP127 Conversion Module........... 185┆
0x2c000…2c100 (44, 0, 0) WangDocumentBody
[…0x14f…]
0x41000…41100 (65, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(65,0, 1), len=0xff, h3=41252041}, f00=»2520A «, f01=»GECO tilbud «, f02=»rt/pan «, f03=»PEH «, f04=»hele technical prop. «, f05=27-07-82 12:37, f06=» 1 «, f07=»11 «, f08=» 5359 «, f09=06-08-82 10:11, f10=» «, f11=»02 «, f12=» 70 «, f13=06-08-82 10:46, f14=06-08-82 11:07, f15=»0211A «, f16=» 68 «, f17=» 4 «, f18=»20 «, f19=» 1256 «, f20=» 14567 «, f21=» «, f22=» «, f99=920092000110056610110490aaca15050000000000000142035801df}
0x41100…41200 (65, 0, 1) WangDocumentBody
[…0x6…]
0x41800…41900 (65, 0, 8) Sector 4109ff00104641 ┆A FACS: a) Messages for re-routing (any case of channel close). It shall be indicated whether the message had been partly transmitted or not (if possible). 4.2.2.5.1.4 Interface AAS AAS to ACS: a) Complete outgoing messages for Routing and auto┆
0x41900…41a00 (65, 0, 9) Sector 410a8000104641 ┆A FAmatic release before transmission. b) Plaindress released messages from SCARS/CCIS for RI-assignment and conversion. directed after conversion. - NICS TARE circuit queue - TRC/Point-to-point circuit queues - SCARS circuit queue - CCIS ┆
0x41a00…41b00 (65, 0, 10) Sector 410bff00104641 ┆A FA 1 4.2.3 Incoming Transport Sub-Package 4.2.3.1 Functional Specification The incoming transport receives message lines from incoming channels via IOC, checks for reception errors,┆
0x41b00…41c00 (65, 0, 11) Sector 410cff00104641 ┆A FA extracts message characteristics, divides and stores message lines into several fields depending on the message type and condition (garbled characters). The incoming transport finally forwards the recieved message to the Analysis Queue. There ar┆
0x41c00…41d00 (65, 0, 12) Sector 410dff00104641 ┆A FAe four types of external channels which the incoming transport will serve. They are as follows: - TRC, Point-to-Point - NICS TARE - SCARS/CCIS - PTR For the external channel types listed above, the incoming transport is described in detail i┆
0x41d00…41e00 (65, 0, 13) Sector 410eff00104641 ┆A FAn the following and the functions which will be performed are depicted in figures 4.3.2-1 to 4.2.3-5. For further details see HIPO diagrams section 4.2.3.3. 4.2.3.1.1 Incoming Transport TRC, Point-to-Point The main functional components contain┆
0x41e00…41f00 (65, 0, 14) Sector 410fff00104641 ┆A FAed within the incoming transport, related to TRC, Point-to-Point connections are as follows: - Initial transport - Error control - Message characteristics - Message division The functions listed above are depicted in figure 4.2.3-2 and descri┆
0x41f00…42000 (65, 0, 15) Sector 41002900104641 ┆A ) FAbed in detail in the following. FIGURE 4.2.2.5-1 INTERFACES ACP127 CONVERSION SUB-PACKAGE ETWORK CIRCUIT Lengt┆
0x42000…42100 (66, 0, 0) Sector 4201ff00104641 ┆B FA 1 4.2.2.5.1.1 Interface MDP ACS to MDP: a) Plaindress or data messages for incoming message distribution (Local PLA - Format E1). 4.2.2.5.1.2 Interface TEP ACS to TEP: a) M┆
0x42100…42200 (66, 0, 1) Sector 4202ff00104641 ┆B FAessage service for RI-assignment. b) Security and warning Reports for printout at the supervisor position. TEP to ACS: a) User prepared plaindress and data messages for RI-assignment and conversion. b) Supervisor prepared ASM and service mes┆
0x42200…42300 (66, 0, 2) Sector 4203ff00104641 ┆B FAsages for RI-validation and conversion. (Return Completion-code). c) User prepared comments and VDU-pages in complete SCARS/CCIS E1-format that shall be forwarded to these systems. (Return status-code originator). d) Re-entering from outgoing me┆
0x42300…42400 (66, 0, 3) Sector 4204ff00104641 ┆B FAssage service after RI-assignment with a notation indicating whether the following subfunctions have been performed: - Relay assignment - Punch - Clear. (Return Completion Code) e) Supervisor initiated readdressal and rerun. (Return C┆
0x42400…42500 (66, 0, 4) Sector 42051900104641 ┆B FAompletion Code) RI 1 = NICS TARE RI 2 = TRC/Point-to-Point RI 3 = ? RI 4 = ? 1 4.2.2.4.2 Conversion Buffers Size: ┆
0x42500…42600 (66, 0, 5) Sector 4206ff00104641 ┆B FA 1 4.2.2.5.1.3 Interface TRS ACS to TRS: a) Messages for transmission to: - NICS TARE - TRC/Point-to-point - SCARS - CCIS The messages will be forwarded to the correspo┆
0x42600…42700 (66, 0, 6) Sector 4207ff00104641 ┆B FAnding circuit-queue. b) Re-routed messages for transmission and retransmission. The messages for retransmission shall be supplied with a suspected duplicate pilot (ACP127 or E1 in accordance with format-type). c) Messages to be punched at the de┆
0x42700…42800 (66, 0, 7) Sector 4108ff00104641 ┆A FAdicated PTP for off-line decryption. d) A command indicating that a message of precedence flash has been forwarded to a circuit or PTP-queue will be sent to the transmission control queue in order to initiate preemption (not NICS TARE). TRS to A┆
0x42800…42900 (66, 0, 8) Sector 4209ff00104641 ┆B FA 1 b) Lay-Out Circuit-List CIRCUIT ID NETWORK CODE COPIES Length: 4 Bytes Siz┆
0x42900…42a00 (66, 0, 9) Sector 420aff00104641 ┆B FAe: 33 records Total: 132 Bytes Circuit ID (Integer) A number representing the queue to which the message shall be directed after conversion. - NICS TARE circuit queue - TRC/Point-to-point circuit queues - SCARS circuit queue - CCIS ┆
0x42a00…42b00 (66, 0, 10) Sector 420bff00104641 ┆B FAcircuit queue - Message Distribution queue - PTP queue Network Code (Byte) A code indicating the network type, depending on which the message shall be formatted: A = CCIS C = CAMPS Local S = SCARS T = TRC/Point-to-Point N = NICS┆
0x42b00…42c00 (66, 0, 11) Sector 420cf500104641 ┆B u FA TARE COPY (Half Integer) The number of transmissions needed to include all RIs of FL2 using the associated View-Ref as basis. c) Conversion Counters Integers: Number of Sections Number of Routes Number of Networks ┆
0x42c00…42d00 (66, 0, 12) Sector 420dff00104641 ┆B FA 1 4.2.2.5 Interfaces The environment of this sub-package is as depicted in figure 4.2.2.5-1. This figure illustrates the other sub-packages of THP and packages that this sub-package┆
0x42d00…42e00 (66, 0, 13) Sector 420eff00104641 ┆B FA interfaces to. The interfaces to system-oriented packages are described in section 3.4 4.2.2.5.1 Application Interfaces The application sub-packages and packages that the ACP127-conversion sub-package interface to are: - Message Distribution┆
0x42e00…42f00 (66, 0, 14) Sector 420f8900104641 ┆B FA Package (MDP) - Terminal Package (TEP) - Transport Sub-package (TRS) - ACP127 Analysis Sub-Package (AAS) - Log Package (LOG) N = NICS TARE Circuit (Integer) A code indicating the circuit-ID to which the RI is assigned. `i6 {M)(sM &M7 ┆
0x42f00…43000 (66, 0, 15) Sector 4200b400104641 ┆B 4 FA 1 FIGURE 4.2.2.5-1 INTERFACES ACP127 CONVERSION SUB-PACKAGE ETWORK CIRCUIT Lengt┆
0x43000…43100 (67, 0, 0) Sector 4301ff00104641 ┆C FAh: 52 Bytes Size: 1 record Total: 52 Bytes Classification (Character) A character indicating the highest classification associated to the following route (RI) RI (9 Characters) The Routing Indicator available for select. Network a┆
0x43100…43200 (67, 0, 1) Sector 4302ff00104641 ┆C FAnd Circuit As for the RI-list. The up to 4 RIs available for select in accordance with classification, will be arranged with the lowest first, in order to establish the logical sequence of processing: The RI selected from the selective RI-l┆
0x43200…43300 (67, 0, 2) Sector 4303ff00104641 ┆C FAist will be assigned the RI-list. c) Lay-Out Originator RI-List RI 1 RI 2 RI 3 RI 4 Length: 36 Bytes RI 1 - RI 4 The fou┆
0x43300…43400 (67, 0, 3) Sector 43048400104641 ┆C FAr RIs associated to the originators HQ. The purpose of these RIs is to select one of them to be used when formatting FL3. VIEW LIST+(NETWORKS-1)+(SECTION-1)=VIEW-REF STORE TEXT-1 SECTIONS = 1? SELECT TEXT-PART TEXT-2 ┆
0x43400…43500 (67, 0, 4) Sector 4305ff00104641 ┆C FA 1 RI 1 = NICS TARE RI 2 = TRC/Point-to-Point RI 3 = ? RI 4 = ? 1 4.2.2.4.2 Conversion Buffers Size: ┆
0x43500…43600 (67, 0, 5) Sector 4306ff00104641 ┆C FA 1024 Bytes Buffer-1: Message parts for conversion Buffer-2: Formatted variable text TOTAL: 2048 Bytes The size of these buffers might be redefined during detailed design in accordance with available resources and performance. At this stage ┆
0x43600…43700 (67, 0, 6) Sector 4307ff00104641 ┆C FAthe buffers are estimated to contain 1 sector of data each. 4.2.2.4.3 Conversion Lists a) Lay-Out VIEW-LIST VIEW-REF Length: 2 bytes Size: 15 Total: 30 bytes VIEW-REF (Integer) View Identifica┆
0x43700…43800 (67, 0, 7) Sector 42085a00104641 ┆B Z FAtions of formatted and section separated message views for multiple transmissions. ┆
0x43800…43900 (67, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(67,0, 9), len=0xff, h3=41104641}, f00=»1046A «, f01=»CPS/SDS/010 «, f02=»vhn/sdv «, f03=»KNB «, f04=»fra 4.2.2.4 «, f05=15-06-81 11:47, f06=» 4 «, f07=»46 «, f08=» 37306 «, f09=27-07-81 12:50, f10=» «, f11=»18 «, f12=» 244 «, f13=27-07-81 13:55, f14=29-07-81 12:29, f15=»0060A «, f16=» 98 «, f17=» 11 «, f18=»06 «, f19=» 1164 «, f20=» 47655 «, f21=» «, f22=» p «, f99=070010000110066610110480aaca15050000000000000037036c01df}
0x43900…43a00 (67, 0, 9) Sector 430a6200104641 ┆C b FA C C C C B B B B B A A A @ @ @ ? ? > > > = = = = = = = < < < ; ; ; ; ; : : : 9 9 9 8 8 8 7 7 7 7 7 7 7 7 6 6 6 5 5 5 5 5 5 5 4 4 4 4 4 3 3 2 2 2 1 1 1 / / / / / / / / . . - - - - - , , , , , , , , , Dokumentnavn: Operat]r: Forfatter: ┆
0x43a00…43b00 (67, 0, 10) Sector 430b8b00104641 ┆C FA 1 CPS/SDS/010 KNB/810801 TRAFFIC HANDLING CAMPS -!/=6'C*-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x43b00…43c00 (67, 0, 11) Sector 430cff00104641 ┆C FA 1 4.2.2.4 Sub-Package Data This section defines the major dataitems used during routing and conversion. 4.2.2.4.1 Routing Lists a) Lay-out RI-LIST ┆
0x43c00…43d00 (67, 0, 12) Sector 430dff00104641 ┆C FA RI CODE RI NETWORK TYPE CIRCUIT Length: 14 Bytes Size: Max. 250 Records Total: 3500 Bytes RI-Code (Integer) 0 = Select ok 1 = No channels open this circu┆
0x43d00…43e00 (67, 0, 13) Sector 430eff00104641 ┆C FAit 2 = Classification mismatch RI 3 = Too low circuit classification 4 = Too many destinations (routes) 5 = X-PLA RI (9 Characters) The Routing Indicator selected under selective Routing Procedures, assigned under preparation (e.g. ASM┆
0x43e00…43f00 (67, 0, 14) Sector 430fee00104641 ┆C n FA) or assigned by Message Service. Network Type (Character) A = CCIS C = CAMPS Local S = SCARS T = TRC/Point-to-Point N = NICS TARE Circuit (Integer) A code indicating the circuit-ID to which the RI is assigned. `i6 {M)(sM &M7 ┆
0x43f00…44000 (67, 0, 15) Sector 4300ff00104641 ┆C FA 1 b) Lay-Out Selective RI-List: 4 * CLASSIFICATION RI NETWORK CIRCUIT Lengt┆
0x44000…44100 (68, 0, 0) Sector 4401ff00102941 ┆D )Aestart. 26 2.2.2.1.1 Initialization ...................... 27 2.2.2.1.2 Close Down .......................... 27 2.2.2.1.3 Restart ............................. 27 2.2.2.2 Check Pointing and Recovery............ 28 2.2┆
0x44100…44200 (68, 0, 1) Sector 4402ff00102941 ┆D )A.2.2.1 Checkpointing ...................... 28 2.2.2.2.2 Recovery ........................... 28 2.2.2.3 Error Detection and Error Handling..... 29 2.2.2.4 Integrity of Operation................. 30 2.2.2.5 Data Collection┆
0x44200…44300 (68, 0, 2) Sector 4403ff00102941 ┆D )A........................ 30 2.2.2.6 Security............................... 31 2.3 CHARACTERISTICS................................ 32 2.3.1 Timing..................................... 32 2.3.1.1 Throughput Time .................┆
0x44300…44400 (68, 0, 3) Sector 4404ff00102941 ┆D )A........ 32 2.3.1.2 Response Time ........................... 34 2.3.1.3 Priorities Imposed by Input ............. 34 2.3.2 Throughput................................. 35 2.3.3 Flexibility................................ 35 ┆
0x44400…44500 (68, 0, 4) Sector 44053e00102941 ┆D > )A2.3.4 Accuracy and Validity...................... 36 ktion annulleret Ukendt kommando JA eller ANNULLER Kun tal Kun mellemrum eller retur Under redigering nu Ukendt dokument Fundet I brug nu Allerede p> systemdiskette ┆
0x44500…44600 (68, 0, 5) Sector 4406ff00102941 ┆D )A 1 3 ENVIRONMENT........................................ 37 3.1 EQUIPMENT...................................... 37 3.2 SOFTWARE....................................... 37 ┆
0x44600…44700 (68, 0, 6) Sector 4407ff00102941 ┆D )A 3.2.1 System Software............................ 37 3.2.2 Development Support Software............... 37 3.3 INTERFACES..................................... 37 3.3.1 External Interfaces........................ 37 3.3.2 Package┆
0x44700…44800 (68, 0, 7) Sector 3008ff00102941 ┆0 )A Interfaces......................... 38 3.3.2.1 Interface MDP ........................... 38 3.3.2.2 Interface TEP ........................... 38 3.3.2.3 Interface SAR ........................... 39 3.3.2.4 Interface LOG ........┆
0x44800…44900 (68, 0, 8) Sector 4409ff41102941 ┆D A )A1029A CPS/SDS/010 rt KNB tAble of Contents 10 06 81 10 01 16 40 77786 12 10 81 10 58 01 39 31 07 81 13 43 20 10 81 08 34 0060A 100 23 22 1216 89467 f *J 7 _┆
0x44900…44a00 (68, 0, 9) Sector 440a6400102941 ┆D d )A D D D 0 + ┆
0x44a00…44b00 (68, 0, 10) Sector 440b8a00102941 ┆D )A 1 CPS/SDS/010 KNB/810801 TRAFFIC HANDLING CAMPS -!/=6'C*-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x44b00…44c00 (68, 0, 11) Sector 440cff00102941 ┆D )A 1 TABLE OF CONTENTS 1 GENERAL .......................................... 11 1.1 PURPOSE AND SCOPE.............................. 11 1.2 APPLICABLE DOCUMENTS AND PROJECT┆
0x44c00…44d00 (68, 0, 12) Sector 440dff00102941 ┆D )A REFERENCES.... 11 1.2.1 Applicable Documents....................... 12 1.2.2 Project References......................... 14 1.3 TERMS AND ABBREVIATIONS........................ 15 1.3.1 Terms......................................┆
0x44d00…44e00 (68, 0, 13) Sector 440eff00102941 ┆D )A 15 1.3.2 Abbreviations.............................. 18 2 SUMMARY OF REQUIREMENTS............................ 20 2.1 Package Description............................ 20 2.2 Package Functions.............................. 22 2.2┆
0x44e00…44f00 (68, 0, 14) Sector 440fff00102941 ┆D )A.1 Main Functions............................. 22 2.2.1.1 Reception Procedures................... 23 2.2.1.2 ACP 127 Analysis....................... 23 2.2.1.3 Routing................................ 24 2.2.1.4 ACP 127 Conve┆
0x44f00…45000 (68, 0, 15) Sector 4400ff00102941 ┆D )Arsion..................... 25 2.2.1.5 Transmission Procedures................ 25 2.2.1.6 Transmission Control Procedures........ 26 2.2.2 Functional Responsibilities................ 26 2.2.2.1 Initialization, Close Down and R┆
0x45000…45100 (69, 0, 0) Sector 4501ff00102941 ┆E )Aestart. 26 2.2.2.1.1 Initialization ...................... 27 2.2.2.1.2 Close Down .......................... 27 2.2.2.1.3 Restart ............................. 27 2.2.2.2 Check Pointing and Recovery............ 28 2.2┆
0x45100…45200 (69, 0, 1) Sector 4502ff00102941 ┆E )A.2.2.1 Checkpointing ...................... 28 2.2.2.2.2 Recovery ........................... 28 2.2.2.3 Error Detection and Error Handling..... 29 2.2.2.4 Integrity of Operation................. 30 2.2.2.5 Data Collection┆
0x45200…45300 (69, 0, 2) Sector 4503ff00102941 ┆E )A........................ 30 2.2.2.6 Security............................... 31 2.3 CHARACTERISTICS................................ 32 2.3.1 Timing..................................... 32 2.3.1.1 Throughput Time .................┆
0x45300…45400 (69, 0, 3) Sector 4504ff00102941 ┆E )A........ 32 2.3.1.2 Response Time ........................... 34 2.3.1.3 Priorities Imposed by Input ............. 34 2.3.2 Throughput................................. 35 2.3.3 Flexibility................................ 35 ┆
0x45400…45500 (69, 0, 4) Sector 45053e00102941 ┆E > )A2.3.4 Accuracy and Validity...................... 36 ktion annulleret Ukendt kommando JA eller ANNULLER Kun tal Kun mellemrum eller retur Under redigering nu Ukendt dokument Fundet I brug nu Allerede p> systemdiskette ┆
0x45500…45600 (69, 0, 5) Sector 4506ff00102941 ┆E )A 1 3 ENVIRONMENT........................................ 37 3.1 EQUIPMENT...................................... 37 3.2 SOFTWARE....................................... 37 ┆
0x45600…45700 (69, 0, 6) Sector 4507ff00102941 ┆E )A 3.2.1 System Software............................ 37 3.2.2 Development Support Software............... 37 3.3 INTERFACES..................................... 37 3.3.1 External Interfaces........................ 37 3.3.2 Package┆
0x45700…45800 (69, 0, 7) Sector 4408ff00102941 ┆D )A Interfaces......................... 38 3.3.2.1 Interface MDP ........................... 38 3.3.2.2 Interface TEP ........................... 38 3.3.2.3 Interface SAR ........................... 39 3.3.2.4 Interface LOG ........┆
0x45800…45900 (69, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(69,0, 9), len=0xff, h3=41102941}, f00=»1029A «, f01=»CPS/SDS/010 «, f02=»rt «, f03=»KNB «, f04=»tAble of Contents «, f05=10-06-81 10:01, f06=» 16 «, f07=»40 «, f08=» 77786 «, f09=29-07-81 13:22, f10=» «, f11=»40 «, f12=» 748 «, f13=31-07-81 13:43, f14=31-07-81 14:24, f15=»0060A «, f16=»100 «, f17=» 23 «, f18=»21 «, f19=» 1284 «, f20=» 89428 «, f21=» «, f22=»( «, f99=800010000110066610110480aaca15050000000000000037039601df}
0x45900…45a00 (69, 0, 9) Sector 450a6400102941 ┆E d )A E E E D 0 0 + ┆
0x45a00…45b00 (69, 0, 10) Sector 450b8a00102941 ┆E )A 1 CPS/SDS/010 KNB/810801 TRAFFIC HANDLING CAMPS -!/=6'C*-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x45b00…45c00 (69, 0, 11) Sector 450cff00102941 ┆E )A 1 TABLE OF CONTENTS 1 GENERAL .......................................... 11 1.1 PURPOSE AND SCOPE.............................. 11 1.2 APPLICABLE DOCUMENTS AND PROJECT┆
0x45c00…45d00 (69, 0, 12) Sector 450dff00102941 ┆E )A REFERENCES.... 11 1.2.1 Applicable Documents....................... 12 1.2.2 Project References......................... 14 1.3 TERMS AND ABBREVIATIONS........................ 15 1.3.1 Terms......................................┆
0x45d00…45e00 (69, 0, 13) Sector 450eff00102941 ┆E )A 15 1.3.2 Abbreviations.............................. 18 2 SUMMARY OF REQUIREMENTS............................ 20 2.1 Package Description............................ 20 2.2 Package Functions.............................. 22 2.2┆
0x45e00…45f00 (69, 0, 14) Sector 450fff00102941 ┆E )A.1 Main Functions............................. 22 2.2.1.1 Reception Procedures................... 23 2.2.1.2 ACP 127 Analysis....................... 23 2.2.1.3 Routing................................ 24 2.2.1.4 ACP 127 Conve┆
0x45f00…46000 (69, 0, 15) Sector 4500ff00102941 ┆E )Arsion..................... 25 2.2.1.5 Transmission Procedures................ 25 2.2.1.6 Transmission Control Procedures........ 26 2.2.2 Functional Responsibilities................ 26 2.2.2.1 Initialization, Close Down and R┆
0x46000…46100 (70, 0, 0) Sector 00000000000000 ┆ ┆
[…0x6f…]
