gnas maintenance control center (gmcc) design

134
SAD-A254 409 GNAS Maintenance Control Center (GMCC) Design Qualification Test and Evaluation (DQT&E) Test Report C% RichardVan Suetendael '~A UG 13.1992 , , July 1992 DOT/FAA/CT-TN91 /39 Document is on file at the Technical Center Library, Atlantic City International Airport, N.J. 08405 Approeid kw ukr.em U.S Dep rmn of Transportahn Federa Avltion AdniOstraton Technical Center 9-29 Atlantic City International Airport, N.J. 08405 9 - 2 9 q6)92 8 O 2IlI111ll :

Upload: others

Post on 05-Jan-2022

3 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: GNAS Maintenance Control Center (GMCC) Design

SAD-A254 409

GNAS Maintenance ControlCenter (GMCC) DesignQualification Test andEvaluation (DQT&E)Test Report C%

RichardVan Suetendael '~A UG 13.1992 , ,

July 1992

DOT/FAA/CT-TN91 /39

Document is on file at the Technical CenterLibrary, Atlantic City International Airport, N.J. 08405

Approeid kw ukr.em

U.S Dep rmn of TransportahnFedera Avltion AdniOstraton

Technical Center 9-29Atlantic City International Airport, N.J. 08405 9 - 2 9

q6)92 8 O 2IlI111ll :

Page 2: GNAS Maintenance Control Center (GMCC) Design

NOTICE

This document is disseminated under the sponsorshipof the U.S. Department of Transportation in the interest ofInformation exchange. The United States Governmentassumes no liability for the contents or use thereof.

The United States Government does not endorseproducts or manufacturers. Trade or manufacturers'names appear herein solely because they are consideredessential to the objective of this report.

Page 3: GNAS Maintenance Control Center (GMCC) Design

Technical Report Documentation Page1. Report No. 2. Government Accession No. 3. Recipsent's Catalog No.

DOT/FAA/CT-TN91/39

4. Title and Subt,,e 5. Report Oate

GNAS MAINTENANCE CONTROL CENTER (GMCC) July 1992DESIGN QUALIFICATION TEST AND EVALUATION 6. Performing Organization Code(DQT&E) TEST REPORT ACN-250

8. Performing O,gonization Report No.7. Author' s

Richard Van Suetendael DOT/FAA/CT-TN91/399. Performing Organzation Name and Address 10. Work Unit No. (TRAIS)

Federal Aviation AdministrationTechnical Center 11. Contract or Grant No.Atlantic City International Airport, NJ 08405

13. Tpe of Report and Perird Covered

12 Sonsoing Agency Name dAddressUj epartment oT Transportation Technical NoteFederal Aviation AdministrationMaintenance Automation Program 14. Snsoring Agency CodeWashington, DC 20591

15. Supplementary Notes

16. Abstract

This report presents the results of Design Qualification Test and Evaluation(DQT&E) testing of the General National Airspace System (GNAS) MaintenanceControl Center (GMCC).

As Test Director, ACN-250 conducted testing at the Federal Aviation Administration(FAA) Technical Center, Atlantic City International Airport, New Jersey.

The purpose of DQT&E testing is to verify that the phase I and phase II GMCC designrequirements are met. The requirements were successfully demonstrated with someminor problems. However, due to an incomplete test configuration, ACN-250recommended retesting the system with a four GMCC network.

17. Key Words 18. Distrinutlon Stetement

General National Airspace System (GNAS) Document is on file at the TechnicalMaintenance Control Center (MCC) Center Library, Atlantic CityRemote Maintenance Monitoring International Airport, NJ 08405

System (RMMS)Maintenance Management System (MMS)

19. Security Classif. (of this report) 20. curity Clos . (of this page 21. Me. of Pages 22. Price

Unclassified Unclassified 131

Form DOT F 1700.7 (8-72) Reproduction of completed page authorized

Page 4: GNAS Maintenance Control Center (GMCC) Design

TABLE OF CONTENTS

Page

EXECUTIVE SUMMARY v

1. INTRODUCTION I

1.1 Background 11.2 Purpose 11.3 Test Time and Location 11.4 Test Participants 21.5 Related Documentation 2

2. TEST CONFIGURATIONS 3

3. TEST RESULTS AND RECOMMENDATIONS 7

3.1 DQT1 Component Inspection, Initialization, Integration, 7and Checkout Test

3.2 DQT2 Local Area Network Functional Checkout Test 73.3 DQT3 Full Service System State Verification 10

4. CONCLUSIONS AND RECOMMENDATIONS 14

4.1 Conclusions 144.2 Recommendations 14

APPENDICES

A - Test Verification Requirements Traceability Matrix (TVRTM)

B - Phase II GMCC Configuration (AT&T Federal Systems Document)

C - Program Trouble Reports (PTRs)

LIST OF ILLUSTRATIONS

Figure Pagel~rIC QDALrTY rNSPECTED 5

2-1 Phase I GMCC Configuration 4

2-2 Phase II GMCC Configuration #1 Acoess'on For 5NTTS - &I

2-3 Phase II GMCC Configuration #2 DT!- Ti 6U1t ai:'i-c n ced ElJuz t , t'!etio

Avnl1 bility Codes'Avail and/or

Dist Special

Page 5: GNAS Maintenance Control Center (GMCC) Design

EXECUTIVE SUMMARY

This test report describes the results of the Design Qualification Test andEvaluation (DQT&E) of the General National Airspace System (GNAS) MaintenanceControl Center (GMCC). The testing was conducted from April 22, 1991, throughMay 1, 1991, at the Federal Aviation Administration (FAA) Technical Center,Atlantic City International Airport, NJ.

The purpose of DQT&E was to perform phase I and phase II testing of the GMCC.Phase I consisted of verifying that Office Automation Technology and Services(OATS) contractual requirements were met. Phase II consisted of testing the LocalArea Network (LAN) interface to the Maintenance Processor Subsystem (MPS), as wellas testing the MPS, LAN, and GMCC workstation software functions. Two additionaltests were conducted to test network reliability and the effects of loading on thenetwork.

ACN-250, as Test Director, performed testing in accordance with the draft GMCCDQT&E test procedures, dated April 1991. Testing utilized version PCB0702 of theInterim Monitor and Control Software (IMCS) to monitor and send commands to thesynchronous Remote Monitoring Subsystem (RMS) simulator. The IMCS software used isresident on the ACN-250 Testbed MPS located at the Federal Aviation Administration(FAA) Technical Center. Testing also utilized commercial off-the-shelf (COTS)software packages resident on the GMCC workstations.

All phase I DQT&E requirements were successfully demonstrated during the OATS MDTevaluation prior to DQT&E testing. The phase I GMCC design is acceptable.

The phase II DQT&E requirements were successfully verified on the GMCC testconfigurations. (See the Test Verification Requirements Traceability Matrix(TVRTM) in appendix A). The network reliability test proved that allmessages/alarms from the synchronous RMS simulator were sent to the GMCCworkstations via the MPS with no data loss. The network loading test indicatedthat eight Maintenance Monitoring Software (MMS)/IMCS sessions and four TandemAdvanced Command Language (TACL) sessions could run simultaneously without systemdegradation or data loss. Test results also indicated that a GMCC workstationconnected to the MPS via a StarLAN network could run the MMS/IMCS software withonly minor problems. The only possible major problem is a lack of security,allowing unauthorized access to the StarLAN server.

Only one complete GMCC (with modems and Brouters) and two direct-connect kMultiLANAdapter to StarLAN Hub) configurations were tested. A configuration w'th fourcomplete GMCC networks must be tested before ACN-250 will recommend accepting thesystem.

At the start of testing, the GMCC network and software configurations were unclear.Datronics/American Telephone and Telegraph (AT&T) and TANDEM representativesgenerated draft configuration documentation (appendix B) during testing. Anychanges to the configuration will necessitate additional DQT&E testing.

Problems discovered during testing did not significantly impact system operation.Each problem was recorded as a Program Trouble Report (PTR). A complete set ofPTRs for GMCC DQT&E can be found in appendix C of this test report. The followinglist briefly describes the problems encountered during testing and theircorresponding PTRs:

v

Page 6: GNAS Maintenance Control Center (GMCC) Design

a. The GMCC workstation could not access UNIX on the server because theKermit application was not functional (PTR-01).

b. A keyboard lockup sometimes occurred when a screen update was received at

the same time a key entry was made (PTR-02).

c. The PackRat application was not available (PTR-03).

d. The Back-It application did not work as expected (PTR-04, PTR-05).

e. The IMCS reports could not be printed from the network printer (PTR-06).

f. Printing MMS reports from the shared printer could only be accomplished ifthe MMS session was exited from after requesting a report (PTR-07).

g. A random error was generated when multiple data points were monitored orunmonitored (PTR-08).

h. An invalid password entry on the GMCC workstations did not prevent theuser from gaining access to the network and its applications. Although MMS/IMCShas adequate security protection, unauthorized access to the StarLAN server andnetwork, which allows access to the MPS, is not desirable. This could beconsidered a major problem (PTR-09).

i. A continuous beep occurred at workstations running two simultaneous IMCSConstant Monitor sessions (PTR-lO).

j. A 25th line message was not displayed on the GMCC workstation (PTR-ll).

k. The StarLAN server tape backup unit was not tested. Documentation on thetape backup unit was not available.

1. Failure mode testing and the useability of GMCC software applicationsshould be evaluated before a design acceptance decision is made.

ACN-250 recommends that DQT&E be repeated when a complete GMCC configuration (fourGMCC LANs connected to a single MPS) and all phase II application functions(including status board and weather) are available.

vi

Page 7: GNAS Maintenance Control Center (GMCC) Design

1. INTRODUCTION.

This test report details the results of the Design Qualification Test andEvaluation (DQT&E) of the General National Airspace System (GNAS) MaintenanceControl Center (CMCC). As Test Director, ACN-250 performed testing in accordancewith the draft GMCC DQT&E test procedures, dated April 1991. The testing utilizedversion PCC0702 of the Interim Monitor and Control Software (IMCS) to remotelymonitor and send commands to the synchronous Remote Monitoring Subsystem (RMS)simulators. The IMCS software used is resident on the ACN-250 testbed MaintenanceProcessor Subsystem (MPS) located at the Federal Aviation Administration (FAA)Technical Center. Testing also utilized commercial off-the-shelf (COTS) softwarepackages resident on the GMCC workstations.

At the start of testing, the GMCC network and software configurations were unclear.Datronics/American Telephone and Telegraph (AT&T) and TANDEM representativesgenerated draft configuration documentation (appendix B) during testing. Anychanges to the configuration will necessitate additional DQT&E testing.

1.1 BACKGROUND.

The GMCC will provide continuous real-time automation support to FAA maintenancepersonnel for the monitoring, control, and maintenance of FAA facilities, systems,and equipment. The CMCC will centralize the management and control of maintenanceoperations for all National Airspace System (NAS) facilities under GMCCjurisdiction. In addition, the GMCC will automate maintenance operations includingcertification and preventative maintenance.

1.2 PURPOSE.

The purpose of GMCC DQT&E was to verify the following:

a. The phase I functionality requirements of the GMCC are satisfied by thesoftware and hardware elements procured under the FAA Office Automation Technologyand Services (OATS) contract.

b. The GMCC meets the phase II requirements defined in the GMCC Type A SystemSpecification, FAA-E-2875, and NAS System Specifications, NAS-SS-1O00 (Volumes Iand V), as outlined in the Test Verification Requirements Traceability Matrix(TVRTM) found in appendix A.

1.3 TEST TIME AND LOCATION.

The GMCC was tested from April 22 through May 1, 1991, at the FAA Technical Centerin Atlantic City, NJ.

Page 8: GNAS Maintenance Control Center (GMCC) Design

1.4 TEST PARTICIPANTS.

The participants in the GMCC DQT&E were as follows:

a. Bill Gibbons Tandemb. Andy Howard Datronics/AT&Tc. Alan Jarvis Datronics/AT&Td. Mike Jones ACN-250/CTAe. Danny Rasdall ASM-450f. Julie Riches ACN-250/CTAg. Craig Stewart ACN-250/CTAh. Richard Van Suetendael ACN-250

1.5 RELATED DOCUMENTATION.

1.5.1 GMCC Program Documentation.

a. GMCC Type A System Specification, FAA-E-2875, December 5, 1990, DOT/FAA.b. GMCC Type Bl Prime Item Specification, FAA-XX-XXX, June 22, 1990, DOT/FAA.c. Draft GMCC DQT&E Test Procedures, April 1991, ACN-250/FAA.

1.5.2 RMMS Program Documentation.

a. NAS System Specification, Functional and Performance Requirements for theNational Airspace System General, NAS-SS-1000, Volume I, December 1986, DOT/FAA.

b. NAS System Specification, Functional and Performance Requirements for theNational Airspace System Maintenance and Operations Support Element, NAS-SS-1000,Volume V, December 1986, DOT/FAA.

c. Remote Maintenance Monitoring System Interface Control Document,Maintenance Processor Subsystem to Remote Monitoring Subsystems and RemoteMonitoring Subsystem Concentrator, NAS-MD-790, June 10, 1986, DOT/FAA.

d. Functions and Operational Requirements of the NAS Maintenance ControlCenter, NAS-MD-794, March 15, 1986, DOT/FAA.

1.5.3 Other Documentation.

a. Draft Design Qualification Test Plan for the GNAS MCC, June 18, 1990.

b. NAS Operational Test and Evaluation/Integration of the Interim Monitor andControl Subsystem Test Procedures, October 1990.

c. MDT OATS Procurement Evaluation Test Report, August 1990, ACN-230/FAA.

d. GMCC Integration Document (DRAFT), April 1991, Datronics/AT&T FederalSystems.

e. Documentation for Testing of MULTILAN/STARLAN (DRAFT), April 1991, TANDEMComputers, Inc.

2

Page 9: GNAS Maintenance Control Center (GMCC) Design

2. TEST CONFIGURATIONS.

The phase I Design Qualification Test (DQT) configuration is presented infigure 2-1. Most Phase I requirements were successfully tested during theMaintenance Data Terminal (MDT) evaluation of the OATS equipment. (See theMDT OATS Procurement Evaluation Test Report, dated August 1990.)

The phase II DQT configurations are shown in figures 2-2 and 2-3. The DQTsequences were performed twice; once for the configuration depicted in figure 2-2and once for the configuration depicted in figure 2-3. The GMCC Loading Test,DQT3.11, and GMCC Network Reliability Test, DQT3.12, were conducted only for theconfiguration depicted in figure 2-3. Note that the FAA-E-2875 (GMCC Type A SystemSpecification) phase II requirement is for up to four GMCCs connected to a singleMPS. This configuration was not available for testing. Appendix B, which wasprepared by Datronics/AT&T and TANDEM representatives, presents the DQT&E phase IIGMCC configuration with network attributes.

The following hardware and/or software was used to perform the DQTs:

a. OATS GMCC workstation hardware consisting of an 80386 25 megahertz (MHz)processor, 4 megabyte (Mb) of Random Access Memory (RAM), 90 Mb hard disk,3.5"/1.44 Mb and 5.25"/1.22 Mb floppy disk drives, Video Gate Array (VGA) colormonitor, 10 Mb StarLAN Network Adapter Unit (NAU) card, keyboard, Microsoft mouse,and 2400 bits per second (bps) modem.

b. OATS GMCC graphics workstation hardware consisting of an 80386 25 MHzprocessor, 4 Mb of RAM, 90 Mb hard disk, 3.5"/1.44 Mb and 5.25"/1.22 Mb floppy diskdrives, video graphics card and 19" Mitsubishi HL6915STK color monitor, 10 MbStarLAN Network Adapter Unit (NAU) card, keyboard, and Microsoft mouse.

c. OATS server hardware consisting of an 80386 25 MHz processor 8 Mb of RAM,150 Mb hard disk, 3.5"/1.44 Mb and 5.25"/1.22 Mb floppy disk drives, VGA colormonitor, 10 Mb StarLAN NAU card, Hi-Capacity Internal Tape Cartridge, and keyboard.

d. Multi-LAN Adapter Device (MLAD) Unit consisting of an 80286 processor, 20Mb hard disk, 5.25"/1.2 Mb floppy disk drive, monochrome monitor, 10 Mb StarLAN NAUcard, 3-COM adapter card, and keyboard.

e. AT&T StarLAN 10 Network Hub Unit (NHU).

f. StarWAN 200 Brouters with X.25 and bridging software.

g. Codex 3600 modems.

h. AT&T StarLAN 10 Network Auxiliary Unit Interface (AUI) Adapters.

i. Accel-500 dot matrix printer.

J. OATS workstation resident software including: AT&T StarGROUP Client(Version 3.3), AT&T MS-DOS (Version 3.3), Microsoft Windows (Version 3.0),Microsoft Word for Windows (Version 1.1), Microsoft Excel (Version 3.0), PrecisionSoftware Ltd. Superbase 4 (Version 1.21), TANDEM PC6530 Terminal Emulation software(Version G21), Gazelle Systems Back-It (Version 3.1), Polaris Software PackRat(Version 3.0), and Columbia University Kermit (Version 2.32), used to access AT&TUNIX System V/386 Release 3.2.2 on server.

3

Page 10: GNAS Maintenance Control Center (GMCC) Design

k. OATS server resident software including: AT&T StarGROUP Server(Version 3.3 for eight users), UNIX System V/386 Release 3.2.2.

1. Two synchronous RMS simulators configured as Air Traffic Control BeaconInterrogation (ATCBI)-5 sites.

m. MPS running IMCS software (Version PCC0702) married to the MMS software;used to monitor/control the synchronous RMS simulator operations.

n. Protocol Analyzer (LM-1 Version 7.0) software resident on a Compaq IIportable computer; used to monitor/record RS-232 message transmission between theMPS and RMS simulator.

MPS

MODEM

TELCO Line

MODEM

OATS MDT

FIGURE 2-1. PHASE I GMCC CONFIGURATION

4

Page 11: GNAS Maintenance Control Center (GMCC) Design

Tandem 5 MAN

10 0 __ _ A10 Transceiver M U

DirectConnection

STARLAN TRA TRA TRA ALN

OATSOASOTOASOS

Graphics Sre

FIGURE 2-2. PHASE II GMCC CONFIGURATION #1

5

Page 12: GNAS Maintenance Control Center (GMCC) Design

Tandem 5 3HMPS 6 C MLAD N - U

o 0 ABO M TJ

FBrouter

AI Adapte

STARLAN STARLAN STARLAN STARLANSTR

OATS OATS OT ASOT

Graphics Sre

FIGURE 2-3 -PHASE II GMCC CONFIGURATION #2

6

Page 13: GNAS Maintenance Control Center (GMCC) Design

3. TEST RESULTS AND RECOMMENDATIONS.

The results from each of the DQT sequences for phase II are presented in thissection. The test purpose, results, and corresponding recommendations (ifapplicable) are provided for each test sequence. Program Trouble Reports (PTRs)are provided in appendix C.

3.1 DOTI COMPONENT INSPECTION, INITIALIZATION, INTEGRATION, AND CHECKOUT TEST.

The DQTI verified that each GMCC component was undamaged and operational. Eachcomponent was examined for external physical damage prior to power up or connectionto any other component. This test was performed by AT&T as part of Phase Itesting.

The DQT1 was performed in accordance with the GMCC DQT&E test procedures and wassuccessfully completed for each workstation. However, due to hardware limitations,only one complete GMCC network could be configured (see figure 2-3).

3.2 DOT2 LOCAL AREA NETWORK FUNCTIONAL CHECKOUT TEST.

The DOT2 verified that all communications connections/interfaces were operational.The DQT2 also verified that COTS software installed on the Local Area Network (LAN)operated in a manner prescribed by the manufacturer's documentation.

The DQT2 consisted of 11 test sequences: DQT2.1 Network Administration Test,DQT2.2 LAN Checkout, DQT2.3 MS-DOS Software Checkout, DQT2.4 AT&T UNIX V SoftwareCheckout, DQT2.5 Microsoft Excel Software Checkout, DQT2.6 PC6530 EmulationSoftware Checkout, DQT2.7 Superbase 4 Software Checkout, DQT2.8 PackRat SoftwareCheckout, DQT2.9 Back-It Software Checkout, DQT2.10 Word for Windows Checkout, andDQT2.11 Microsoft Windows Software Checkout.

3.2.1 DOT2.1 Network Administration Test.

3.2.1.1 DOT2.1 Network Administration Test Purpose.

The DQT2.1 verified that system administration functions could be performed fromthe network server.

3.2.1.2 DOT2.1 Network Administration Test Results.

The DQT2.1 was performed in accordance with the GMCC DQT&E test procedures and wassuccessfully completed on the network server. One problem was identified duringthis test:

a. An incorrect password was accepted by the StarLAN network. Unauthorizedaccess to the StarLAN server is undesirable. This could be considered a majorproblem (PTR-09).

7

Page 14: GNAS Maintenance Control Center (GMCC) Design

3.2.2 DOT2.2 LAN Checkout Test.

3.2.2.1 DOT2.2 LAN Checkout Test Purpose.

The DQT2.2 verified that general StarLAN network commands could be performed ateach GMCC workstation. Links to the server were established and verified.Terminal messages were sent and received at each workstation. Existing links andservers in use were displayed upon request. This test sequence also verified thatthe NAU Statistics program and the Reconfiguration program were accessible andfunctional.

3.2.2.2 DOT2.2 LAN Checkout Test Results.

The DQT2.2 was performed in accordance with the GMCC DQT&E test procedures and wassuccessfully completed on each GMCC workstation. No problems were observed duringthe conduct of this test sequence.

3,2.3 DOT2.3 MS-DOS Software Checkout Test.

3.2.3.1 DOT2.3 MS-DOS Software Checkout Test Purpose.

The DQT2.3 verified that MS-DOS Version 3.3 was resident and functional on eachGMCC workstation. The basic MS-DOS commands were issued and the results recorded.

3.2.3.2 DOT2.3 MS-DOS Software Checkout Test Results.

The DQT2.3 was performed in accordance with the GMCC DQT&E test procedures and wassuccessfully completed on each GMCC workstation. No problems were observed duringthe conduct of this test sequence.

3.2.4 DOT2.4 UNIX V Software Checkout Test.

3.2.4.1 DOT2.4 UNIX V Software Checkout Test Purpose.

The DQT2.4 verified that the UNIX V Operating System (OS), resident on the server,was accessible through the KERMIT communication application on each GMCCworkstation.

3.2.4.2 DOT2.4 UNIX V Software Checkout Test Results.

Because the KERMIT application was not functional, DQT2.4 could not be completed(PTR-Ol). It is believed that KERMIT is not compatible with the version of LANsoftware being used.

3.2.5 DOT2.5 Microsoft Excel Software Checkout Test.

3.2.5.1 DOT2.5 Microsoft Excel Software Checkout Test Purpose.

The DQT2.5 verified that Microsoft Excel (Version 3.0) software was resident andfunctional on each GMCC workstation.

8

Page 15: GNAS Maintenance Control Center (GMCC) Design

3.2.5.2 DOT2.5 Microsoft Excel Software Checkout Test Results.

The DQT2.5 was performed in accordance with the GMCC DQT&E test procedures and wassuccessfully completed on each GMCC workstation. No problems were observed duringthe conduct of this test sequence.

3.2.6 DOT2.6 Tandem PC6530 Software Checkout Test.

3.2.6.1 DOT2.6 Tandem PC6530 Software Checkout Test Purpose.

The DQT2.6 verified that Tandem PC6530 (Version G21) software was resident andfunctional on each GMCC workstation and that access to Maintenance MonitoringSoftware (MMS)/IMCS is permitted via the PC6530 application.

3.2.6.2 DOT2.6 Tandem PC6530 Software Checkout Test Results.

The DQT2.6 was performed in accordance with the GMCC DQT&E test procedures and wassuccessfully completed on each GMCC workstation. No problems were observed duringthe conduct of this test sequence.

3.2.7 DOT2.7 Superbase 4 Software Checkout Test.

3.2.7.1 DOT2.7 Superbase 4 Software Checkout Test Purpose.

The DQT2.7 verified that Superbase 4 software (Version 1.21) was resident andfunctional on each GMCC workstation.

3.2.7.2 DOT2.7 Superbase 4 Software Checkout Test Results.

The DQT2.7 was performed in accordance with the GMCC DQT&E test procedures and wassuccessfully completed on each GMCC workstation. No problems were observed duringthe conduct of this test sequence.

3.2,8 DOT2.8 PackRat Software Checkout Test.

3.2.8,1 DOT2.8 PackRat Software Checkout Test Purpose.

The DQT2.8 verified that PackRat software was resident and functional on each GMCCworkstation.

3.2.8.2 DOT2.8 PackRat Software Checkout Test Results.

Because the PackRat application was not resident on the network, DQT2.8 could not

be completed (PTR-03).

3.2.9 DOT2.9 Back-It Software Checkout Test.

3.2.9.1 DOT2.9 Back-It Software Checkout Test Purpose.

The DQT2.9 verified that the Back-It (Version 3.1) software was resident andfunctional on each GMCC workstation.

9

Page 16: GNAS Maintenance Control Center (GMCC) Design

3.2.9.2 DOT2.9 Back-It Software Checkout Test Results.

The DQT2.9 was performed in accordance with the GMCC DQT&E test procedures. TheDQT2.9 test sequences were completed on each GMCC workstation. Testing revealedthe following problems:

a. The floppy diskette format worked inconsistently (PTR-04).

b. The disk backup procedure defaults to the A: drive when the user specifiesthe backup for the B: drive. This occurred only on the first attempt. The secondattempt at backing up was successful (PTR-05).

3.2.10 DOT2.10 Microsoft Word Software Checkout Test.

3.2,10.1 DOT2.10 Microsoft Word Software Checkout Test Purpose.

The DQT2.10 verified that Microsoft Word for Windows (Version i.1) software wasresident and functional on each GMCC workstation.

3.2.10.2 DOT2.10 Microsoft Word Software Checkout Test Results.

The DQT2.10 was performed in accordance with the GMCC DQT&E test procedures and wassuccessfully completed on each GMCC workstation. No problems were observed duringthe conduct of this test sequence.

3.2.11 DOT2.11 Microsoft Windows Software Checkout Test.

3.2.11.1 DOT2,11 Microsoft Windows Software Checkout Test Purpose.

The DQT2.11 verified that Microsoft Windows (Version 3.0) software was resident andfunctional on each GMCC workstation. TheDQT2.11 also verified that simultaneousoperations could be performed using Windows on one GMCC workstation.

3.2,11.2 DOT2.11 Microsoft Windows Software Checkout Test Results.

The DQT2.11 was performed in accordance with the GMCC DQT&E test procedures and wassuccessfully completed on each GMCC workstation. Each GMCC workstation was capableof running three Tandem sessions two MMS/IMCS sessions and one Tandem AdvancedCommand Language (TACL) session simultaneously. One problem was observed:

a. A constant beep occurs at workstations that are running multiple IMCSsessions. This does not cause data loss or system degradation (PTR-10).

3.3 DOT3 FULL SERVICE SYSTEM STATE VERIFICATION.

The DQT3 verified full service system state requirements. The GMCC full servicesystem state is defined as all workstations, processors, and communications linesbeing fully operational.

The DQT3 consisted of 12 test sequences: DQT3.1 Full Service System StateInitialization, DQT3.2 MPS Software Compatibility, DQT3.3 Simultaneous WorkstationOperations, DQT3.4 GMCC Operational Control, DQT3.5 GMCC Real-time Monitoring,DQT3.6 GMCC Certification, DQT3.7 Status and Alarm Handling, DQT3.8 NonfacilityInformation Monitoring, DQT3.9 Full Service System State Response Time, DQT3.10GMCC Reporting, DQT3.11 GMCC Loading Test, and DQT3.12 GMCC Network ReliabilityTest.

10

Page 17: GNAS Maintenance Control Center (GMCC) Design

3.3.1 DOT3.1 Full Service System State Initialization Test.

3.3.1.1 DOT3.I Full Service System State Initialization Test Purpose.

The DQT3.1 verified that GMCC equipment was configured and initialized as required

to test the GMCC full service system state.

3.3.1.2 DOT3.1 Full Service System State Initialization Test Results.

The DQT3.1 was performed in accordance with the GMCC DQT&E test proceduresand was successfully completed. Powering up the GMCC network took approximately10 minutes.

3.3.2 DOT3.2 MPS Software Compatibility Test.

3.3.2.1 DOT3.2 MPS Software Compatibility Test Purpose.

The DQT3.2 verified that the GMCC was capable of accessing MMS/IMCS software on theMPS by utilizing the Tandem PC6530 Terminal Emulation software package on the GMCCworkstation.

3.3.2.2 DOT3.2 MPS Software Compatibility Test Results.

The requirements for this test sequence were verified during DQT3.3 through

DQT3.12.

3.3.3 DOT3.3 Simultaneous Workstation Operation Test.

3.3.3.1 DOT3.3 Simultaneous Workstation Operation Test Purpose.

The DQT3.3 verified that all GMCC workstations could operate simultaneously. TheMMS/IMCS operations were performed on each of the workstations at the same time.Operations included site monitoring, alarm acknowledgement, command issuance, andreport generation.

3.3.3.2 DOT3.3 Simultaneous Workstation Operation Test Results.

The DQT3.3 was performed in accordance with the GMCC DQT&E test procedures.Testing revealed the following two printing problems:

a. The IMCS reports could not be printed to the network printer (PTR-06).

b. The MMS reports could only be printed on the network printer if the MMSsession requesting the report was exited (PTR-07).

3.3.4 DOT3.4 GMCC Operational Control Test.

3.3.4.1 DOT3.4 GMCC Operational Control Test Purpose.

The DQT3.4 verified that the GMCC had operational control of its monitoredfacilities by sending commands, acknowledging alarms, and monitoring/unmonitoringspecific sites and/or data points via MMS/IMCS.

11

Page 18: GNAS Maintenance Control Center (GMCC) Design

3.3.4.2 DOT3.4 GMCC Operational Control Test Results.

The DQT3.4 was performed in accordance with the GMCC DQT&E test procedures. One

problem was observed:

a. After a group of data points was selected for unmonitoring, IMCS indicated

that not all the selected data points were unmonitored (PTR-08).

3.3.5 DOT3.5 GMCC Real-time Monitoring Test.

3.3.5.1 DOT3.5 GMCC Real-time Monitoring Test Purpose.

The DQT3.5 verified the capability of the GMCC to perform real-time monitoring of

its monitored facilities via IMCS/MMS.

3.3.5.2 DOT3.5 GMCC Real-time Monitoring Test Results.

This test requires access to all facility logs, alarm and certification history

data, and other facility information. This information was not available and so

this test was deferred.

3.3.6 DOT3.6 GMCC Certification Test.

3.3.6.1 DOT3.6 GMCC Certification Test Purpose.

The DQT3.6 verified the capability of the GMCC to send RMS commands via MMS/IMCS to

specific certification data points within an RMS.

3.3.6.2 DOT3.6 GMCC Certification Test Results.

The DQT3.6 was performed in accordance with the GMCC DQT&E test procedures and was

successfully completed on each GMCC workstation. No problems were observed during

the conduct of this test.

3.3.7 DOT3.7 Status and Alarm Handling Test.

3.3.7.1 DOT3.7 Status and Alarm Handling Test Purpose.

The DQT3.7 verified the capability of the GMCC to process status and alarm messages

via MMS/IMCS.

3.3.7.2 DOT3.7 Status and Alarm Handling Test Results.

The DQT3.7 was performed in accordance with the GMCC DQT&E test procedures and wassuccessfully completed on each GMCC workstation. No problems were observed duringthe conduct of this test.

3.3.8 DOT3.8 Non-Facility Information Monitoring Test.

3.3.8.1 DOT3.8 Non-Facility Information Monitoring Test Purpose.

The DQT3.8 verified the capability of the GMCC to monitor nonfacility information,

such as weather data and air traffic restrictions, via MMS/IMCS.

12

Page 19: GNAS Maintenance Control Center (GMCC) Design

3.3.8.2 DOT3.8 Non-Facility Information Monitoring Test Results.

Nonfacility information was not available for testing and so DQT3.8 was deferred.

3.3.9 DOT 3.9 Full Service System State Response Time Test.

3,3.9.1 DOT 3.9 Full Service System State Response Time Test Purpose.

The DQT3.9 verified that command execution and alarm presentation times were withinthe ranges specified in NAS-SS-1000.

3.3.9.2 DOT 3.9 Full Service System State Response Time Test Results.

The DQT3.9 was performed in accordance with the GMCC DQT&E test procedures and wassuccessfully completed. The GMCC workstation command execution times observed wereunder 3 seconds. The alarm presentation times were under 6 seconds.

3.3.10 DQT3,10 GMCC Reporting Test.

3.3.10.1 DOT3.0 GMCC Reporting Test Purpose.

The DQT3.10 verified GMCC reporting functions by utilizing MMS/IMCS functions.

3.3.10.2 DOT3.10 GMCC Reporting Test Results.

The DQT3.10 was performed in accordance with the GMCC DQT&E test procedures and wassuccessfully completed on each GMCC workstation. No problems were observed duringthe conduct of this test.

3.3.11 DOT3,11 GMCC Loading Test.

3.3,11.1 DOT3.11 GMCC Loading Test Purpose.

The DQT3.11 verified that all GMCC workstations were capable of running independentMMS/IMCS sessions simultaneously. All workstations ran two IMCS sessions and oneTACL session. The loading effects on the network were recorded.

3.3,11.2 DOT3,11 GMCC Loading Test Results.

Test results indicate, for the configuration shown in figure 2-3, that nosignificant system degradation occurred under the loaded conditions. The GMCCperformed as expected.

3.3.12 DOT3,12 GMCC Network Reliability Test.

3.3.12.1 DOT3,12 GMCC Network Reliability Test Purpose.

The DQT3.12 verified that the GMCC network could reliably process alarms that weresent continuously from the monitored facilities. Two RMS simulators alternatelysent streams of alarm and return to normal messages to the GMCC network.

13

Page 20: GNAS Maintenance Control Center (GMCC) Design

3.3,12.2 DOT3,12 GMCC Network Reliability Test Results.

Test results indicate that no data loss was experienced when using a networkconfiguration (figure 2-3). All alarm and corresponding return to normal messages(generated every 20 seconds) from the RMS simulators were received and displayed oneach GMCC workstation.

4. CONCLUSIONS AND RECOMMENDATIONS.

4.1 CONCLUSIONS.

All phase I Design Qualification Test and Evaluation (DQT&E) requirements wereeither successfully completed prior to DQT&E testing or satisfactorily demonstratedduring DQT&E testing. The phase I General National Airspace System (GNAS)Maintenance Control Center (GMCC) design is acceptable.

The phase II GMCC test configurations satisfactorily demonstrated the capability tointerface with the Maintenance Processor Subsystem (MPS) via the StarLAN network.The GMCC workstation software applications functioned satisfactorily. A potentialmajor problem is the lack of security on the StarLAN server that allowsunauthorized access to the StarLAN network.

The FAA-E-2875 (GMCC Type A System Specification) phase II requirement states thatup to four GMCCs may be connected to one MPS. This configuration was not availablefor testing. There are major impacts to the network configuration when expandingto the required four GMCCs. This configuration must be evaluated before designacceptance can be decided.

Failure mode testing was not formally conducted during DQT&E. Also, useability ofGMCC software was not addressed. Both of these should be considered before adesign acceptance decision is made.

Furthermore, some applications (i.e., status board, weather) required for phase IIare not yet available. These applications must also be evaluated prior to designacceptance.

At the start of testing, the configuration of the GMCC network and OfficeAutomation Technology and Services (OATS) commercial off-the-shelf (COTS) softwarewas unclear. Any changes to the network and/or COTS software that were tested willnecessitate additional DQT&E testing.

4.2 RECOMMENDATIONS.

ACN-250 submits the following recommendations:

a. Conduct General National Airspace System (CNAS) Maintenance Control Center(GMCC) failure mode testing.

b. Conduct a useability evaluation of GMCC software.

c. Repeat some or all of Design Qualification Test and Evaluation (DQT&E)when a complete configuration (four CMCC Local Area Network (LANs) connected to asingle Maintenance Processor Subsystem (MPS)) and when all software applicationsare available.

d. Conduct all recommended testing (a through c) before a designqualification decision is made.

14

Page 21: GNAS Maintenance Control Center (GMCC) Design

APPENDIX A

TEST VERIFICATION REQUIREMENTS TRACEABILITY MATRIX (TVRTM)

Page 22: GNAS Maintenance Control Center (GMCC) Design

0z

co)

u w I 0 0.. -

0 V 01 41 a4) M c w. 4.o 4 4, )

4) 4 a w Ow A 4 4 Cu0 E- or. Mr. OWNY

c w ~0. 0 0. 0 > 4

4.4 03a)4)

Cd'

911

00 4)

od (6

w4104) 4)Z

0-4 0. )74.4 In.. ) )

.PL.4 Z 141 1 w 4...u .00 to U-4 0) bO4 91 cn 4) 2 m. A0 .. 3t M 4. to r.z A uLn-. "4O .. 4 Auba... 0)4- 00. -4 > 1C W. Uo4 l o.4 ed U -4 C 0 0 r " "= . rE- ca C4 .-. 4 -6 V M - U '4.4 W 93 wu .4M CV 4'-'~ 4U u4

x0 cc4) 4) 0 4)1 cc4 A.0 .04 0U r cj4C ciu C4r ow -40 44dw CO~ 9 U: to(4. -4 *.J4 .4

N -4) cc~2 cc 41 *.4 W) ) .' 4 C:.4) Aj 4 CA4 J.O3 m.E. 11g .. 4 .L 'A ( A co t I

".4C 0. W c -* A 4) ". 4) 40 %..- 4

w us O M 0 0.4w4 0.-.C 0.) 0 W-4 E-ca ~ 4C' a~l 0c 1: 0 3-4 .a .CO

-4 . 41 w 41 . . -4>__ _ _ 0 cc a 0C l 4) 0 02 ato W U 4-

4

4-4

Ca~ .. 4 j~

4.4 4)1fj .4 U2 Cu

o 04) .0214.44Do 340:4

00 -400 cc44 *I&"W

-P4

t4).0

4)4

0 4(4 V4)

40 u 0 -40

A-i

Page 23: GNAS Maintenance Control Center (GMCC) Design

00

u 1 0 E-4 Wr

w -0.4- m4

44. w . .441a 41 14 00 .

0 E 41. -4

E-4I E-14

41 0 -0 C-4 -,

) 1 &j441

41 414 4

.= -4w LW"4C r 44

-- .4 ~ 0 .r A) )0 14 4 c 4m c1

4.1 41 0 u4oa14 140 " z CUW d 41 W 4- d4 4 44 0 C

4 00 41 41 u mV 4 4 -1v1 41 4. u O 0 w0

0 c 4 WW44l 0. C 0 4 o00w P 410.inC -$.zU04114 44~4 a) w0m 6 A r 1

u 41.1 414 ca0c C a0 9 4 4w4 1 41 w r u4L 9: $ .4 1 " u 4-1 = mad .4 1

12 m to 41 0z u 0 0 i 9 Z4 41 0 . 0 014 u.41a 0C$ " .Aj0 00)0 if 0 ,MAW0 $.44 '00$

01 00u 414w104-co 41 41x 41$. 41$.> CL 44 Ai 4)41 w4.P44 0 41 u. 4 0 . J Aiw" .40

z 0-40.14 4 ca" )0caw z1 4. r4 0 ) :0 C- 4

0 i 9 LCX0 4 > -44 41 CL4 0>0.4 "41-a

441UE w

ad4 004

(-d

el 44

E-4 41 4 0-4~

C.,; c ..

41 41 CL.

0 4.414

41 4 g

0 41 to -

4.. * 4 0 r

0C- c"

A--4

Page 24: GNAS Maintenance Control Center (GMCC) Design

0041

o 4.4z 0

41 -141 JJ.41 w.

U4 1 e 44 V3(n Qj-4

4 0 41 41uO0 E-4 to w

w >% 41 041~ 41)

4a) Aou

4-00

41 4 41

w O04 cc .-4 '04 00u "is 0 w0 :

-4-4. 41> 4 - cm 4

".4. >% 0& 4 0

CL4 ) i 4 M4 - 0 t0 .0 w .

.44 . .41 4 m1 4.. .o-" a0 41 0 c -

0 j0 0 0 0 1L . r4.o0

"-4 -4 Cd C.0 4. M4. ) 4) 9 u 4 41.4 0404 00 410 d .

z 4 w 4 C cc 9:bo -4.W 0 0 0 ma A

w1 L, 9:Q . % d . 1 0 0 4 u w >%O>% .4 -iI 4 .4.5441 a 41 0 0- a - 0) 14) 41 a

41 0 41 4W' -i4~ a V w w 0 0 Vu - -

.1 . r-4.) 1 > 0-444ro. 4 >C 44i10 1 0 hi GC 0 i > )"4 t41 z 0 ca Ud 0 04. I 4 U .. 1. u uz 8 4 0 au 10

0 Urmc=W ww0m00t 0 . 0 U$ ( 043t

ad > h-

r .w 0 0 411.4 10

-4 > w-0 ca1

hi ~.41 00) c

-4 414-

0 c~J0 cc w (1&J41~ cc 00

w 0n

0 hi 41-4 0 r.0>1 41 -4 Vi U

00 ~ 0 04 h0 -Id m

441 -. 4 0-00

414

A- 3

Page 25: GNAS Maintenance Control Center (GMCC) Design

-4 C.4

z

0~ 04

0 ).4 4

m0 w --.

035 -- s

r.2 I 14)04a 01- JJ cz cn0) 414

4 - 1 f

4)4

o4 E--4

4) m V4

041 0)..4 .4 4Z

,a2 04) 0 s 1cc 4 >O r. 4)4 J c 0 -44

0. cc 4) 4 0W 4w 00 - bO 0 U;)0 4).4~.O -4) M 4 44(1)U

). W I. 4) 4 1.4 0 ) ~J-.4 '4c Cis C6 w cc -4 .. 4LJ w 0. -4 > .a0-4

CL c0 r.0 41 JJLJ 0 >)"4 04c 04 4.4 0U0 w0 $0044 0

4)JJ u 4)0u0 QW 0 0 r- 0 w)4 4r-4 4) u 41 0&J U4.4Uri41 6 -1 a Q) ri .. A

41) 0. u~4J 0 i 0u 0 w'. u 04) 4)cc 0 0 00 V4~~0. 'a* C. - 4 e

04132~~ s44~)4'.0U. O 4)00oA. 9: 0 W W 4

4 9 .0W V40 us0)c

m . 04-4 " W 0 - M 1 44 0 "4-4-b 0.wuO 0. > -4 O0W 4-4 0 0 >Vr

o r $ O .4 Jw~4 w 0 1-4...444w.4) 1.4w 0 PC-4 4) >4 4 CL.0 u w d toc CLu 41cc0. 04 4-10(

cc 4 .

>--

411444 cm4 4) 4

w .0 00

Z- LI to w

co- *Zu 0 0 4 10 0 : 0)41

.0 E1.4 *~r'4 0.

to~4) 0Q 01

44 U 4

A-4)

Page 26: GNAS Maintenance Control Center (GMCC) Design

0z

z) 0 ~0 :10 14 :10a) U 0- 0 -4 0 0 -V*4 0 444.4 4) 444 (U4&j

~~ 4.) 11 4) 3t)4.44)0.44) U) -40.6 0 -4 L40. 400 .- ICL

4) 4) zO 000 E- a a 4

4.)0 41

o)z 4-4 e -

-E 1

40 0 )... c.

04 ce 0 (U .

,a. O 41 -- 4W4 0~go - .4 ul C ) b) "J)4 0 M4 041

a ~ 4 44 4)4)W 4 .0 44- " .o 01 40 U,44 0 C 0 4.4 Cct 4'4. ..a.Iu00 r.

4 .04) , -4) V . U 00 0w41 %64 U 114. 4) 0 40 4 . '44~ - ZM 0 4 0 . 0 J-). t 44 14 t v & 0 4

, -4 4 4 000 4U) W 40~ -4 0cn wM0L 0414 c c.. E W M.4 1I- 4 uJ w4

4)u>%4 u~ -4 a 41 U).44$4 CL- - 4) -4

w )rI-4 V .-44*4 (U 1 4. 0 > C )44. = ?A 0 co 0Q Lz c l4 4)J. ca~ > 0 0 0 0 4 4 tb-4 r. tocol 4 ".44 Q C ) 0- -. -400 sr

-4 41 "4 w) cc 0) U C l w 0 " 0 t.4 .4 U) 4 >

4 '0 4. Z U0 0d-. 4 b :. . o4 4

0 4n. (34u)4.4 m- 1- 4 b r ( i- : c 1

4) 4. C4) 1 CL 4 1 d 0

"04 >4)>0" r 4 - 4 I u 0 k0.I W -4 -4 w4) 4 w

4 0 04a 4144C- M

:> 4)

4)4)Z -4

41 C4 4

4.) CL i 41

4)'

'4)

44

A-5

Page 27: GNAS Maintenance Control Center (GMCC) Design

u 4 rc .4 to C

4,40 -. 4 fl~ -

44 In 041

UC 1-4 0 0-4 a JJ >.104

1.4 0-l 4 u 1

44. u i 0 4 : ) 4c

w N~ wJ >%-41

1.4 4_ 4__ _ _toMCAcc_1_ _ _ _

0 0~40 .0: 4c'cw a r- dar

-4, -4 4 4 1.1r- J2 44

c41 1-4 10- "4 m4..u 3 4 *z r-4i 4 .~ 44 a 44 44 (j. -

-, .02 40W M .> C " a 40 40 c 0 4) 0 0) "1 ca0 0. t 4 4 0 0

0 r "4b . 4 0 r4 W w u0 4)4 W 4Q)B Adc C-4 . 04c 44 r . 41

>- ca W~. 4).~ 0 9141.a 1.4 0'd C.40 C.~ c. a

~~6 0) W40 A4j4 0 4.0

441 - 3-4W4. .. , 4 0 51-41 IOf 45

w I0o w 4)0 0

.14 .~* 4 0 th 1

E1 404 4.1410 c

'I. ____s 41 0i t0 0 042-w4 11 40 &

cd~ -4r4 w OE

toi C1 u C a 4

Z. -410.41~ 04

I-.0 .0 4

Ai' > > A 4 u

0.1- 4 .4 C 44 5.

4.4 * ) . 00~ ~~~~ NO. ez54~ .

in* 0 5,4.

A-6~Zfl b0

Page 28: GNAS Maintenance Control Center (GMCC) Design

064)4

u . -) m b-4 4

2: V -4

4) 0 (D

~4) 0 CA4. 3 c

4) W . 0

(aU -a 0a C E .41 r- e

44 4.4

E4 -4 4)c4) co 0

,a z 44

cc 0I 4.) 4044 t - 441) e.: 41C0 1 4 A 40

C: 4 ca a 0 . f- 41 u Q 4)

H 4 c w4)m c - 44z 4 00 0 44Q r.a-4t

x ". 1t oX -4 Q0ww0b 4)

l4 - 4 4) a C U 0 -

- 4 b4) 4)4 ~44 84) 4 41 )~.4 -.4

,4 4) %. >%t 1> -44) 44z 4 4)41 I (f C$ 4J 0 U W 4 91 4)

0 -4 -0 "4 4 - l- 00000 --- 4 -4 - 400 -4 M0 U 014. 4 44 31 W0. 4)

> 0 >v W44 0 0> 4)0 0 3 "4 c0 3u a 0-b 441 u54.4 4.uU -40

040 Ui 0. 0 4)4 ;ON .0 m .- 0 ).-4 B .0

Z ))) 44.4 96ul czCLa *ad tou 4 . UI" co.4 4)

-> 41

1 0.4-041)

41 01 4.).0 .-4 0 1 44e C4 1

4-4 4 . 0. 0 tR 4)I' "-4 CU 41EV 1. 4 *0 .0

V4.)icn A ' U - cc 4 4 4J "4 U-4 Qb* . -4 * 0 b0 *01 4 0: . jwCw4

0.E- 41 .0 -4M 4 -4 N4.) = 0 >..

Z. . 44 . * -,4 U 44 . " 44 44 00c C4. 4u .0 C4 C CAu 4) .0 04u "0.0 .

cc r.~ 4) z . 0 0 C.0M * C Z0CA.E rUCA e Z a. cn ul.4

4.)

-4 0 00 4-40 ~ ~ ~ ~ ~ ~ 4 -4" 4 0"44 4m0

u41 41 > X 41 >4.. 41 >4- 04) ua

40 W 5 U I~) uJ U 3 ~U 0C4.44.14441 4C4a

__ _ CaUu CL. 0. 6 .C

A-7

Page 29: GNAS Maintenance Control Center (GMCC) Design

0 6

43 0

CA 4

92 a 1-

3 CA

4 0 43A

43041

44 0 043 V 0

to 01an

go

41 U04 43

'-4 bo1 4U 0 - 0A .V - oC 43

V.0 0 0 1-w.43. 9543$ 1 1w 0-

u u 4 u$40aa CJW-44 .0

41 u 4 0 l U ri a 44ou a s 00 0 4 O 40 cc

104 a0 V4 443. 4 1043 ~ 434 04.U)1 ha 4.3J "J4CIS 4.~ a4 "4- 490 J4

>A AJ0434 -4 > is 4.4 0U 4 a3 4"43f C~O. 0.cJ OC $40 0(i4 CwbO c 43

04 4*44 C l. M 3 WP.W 43.4- .4 04 434 U .

43 ~ a.~ .. 1 O1W 04 "44. 400U 43

t4 9:. -4

.cc 0

43

0 v4

> 41

.4 "4. 0~04 043

wO U . A 1 -a

A-84

Page 30: GNAS Maintenance Control Center (GMCC) Design

Cu6

0)4

CACal

Us U 4

o H 41 U)

w 41 41

w10.1'.4 - 4 -41

4.4 Cu a 4 .t C 0(41) 4WW0 4W. 4" M

Z 0-.4 0 4Z r. 0"0"=.Jww""4 0 j 1C t)C

04 iiU4- A 40 44JU- 4Q 00-4"

a440 "4 0". 4 .4. 44 4 -4) '.V00 X) 4Vw 4 4 1 :4

-4 - M 0 0 J -4 -. r- al 4 -4 -4 -.40 '0 -4 . V

0 . W 44 =4 CM W4 . W4

4)

U3 4)Cu 4

- 4 *.. ... 41 C(-4 4l -4 4 ~ 4 '~CC

0 ~~~~~t 41 Cu4144U4'-~co C -i U 0). A..C- C '0 u ~ '

CuI..0..C4

U1-C-C 41 >140.. &14 0. 00

4.4 U-4uV SC4 . u

CLC

- A-9

Page 31: GNAS Maintenance Control Center (GMCC) Design

z

4) -dc wc

u4 4)ul&J4w). Z 0 m0

4.-4 to-

40 4)4)) .4

b- 0 -. 4 r V440 0.0

-4 -4c

Z~~ 0104).

CL4 4)-k t $ r

r.. C4C. c

-4 CL44 ,4 0 &

0)04 w A c 4 0 U.

)i * jC A40 A a44)04 4 0-4 1 4.4 a 4

rr 0c0 0619

.,I Aci-4d 4. W O. 0 -ea > 4) r.0 41~ V 0 v 0

4) CU . U. CL -44

4 -4W -4)> r.- 4) A JN (044 A1 U

4)0 00 c" 0U 4)0

ZC -4WC4 0Ud 01

4 )- 4) 00 u) -1w 0-4E- C4 CO 4) 'O4 00 . -.4 ~ -en0-enw - "4U Q4.'0 .. 4 AJ0 * 4..

04.4b c4- _;~ " 0.f C .- 4 . . or?A $ j M-4- i r4-

-- 0 4)4r . -4 r) ."

4oC)to44 0 C 4) . 0 C-4 uU =rO -M Zo 0 0-4ib

-4 4)-4cr4 CU. co

1-4 Z~ CU-4

.) 0 0-0 U

00 *CCLU* WO4u.E (nJ 916... uN bO44- 4'. Q6. E 44

CU ~ ~ ~ ~ ~ A 10.44 .. 04) ~ *. 4

Page 32: GNAS Maintenance Control Center (GMCC) Design

4)cc4

w 0

e 4) $4 - 0v ) 0 r. 4

w4 0 Ia.a 6

0.4 J.3 4J 404)0 4) WJ ) v.00 I -. 4)

0.0n 0.0 )

cc 4)

U 4 W 4 .0 h

4 SE- J0 w 040U

U.0 m4.4c .4 >>$z lM lZ 40c0 -4 X U4)-4MQ 44

x 1 0 0 .) to0 u .4& - 4 4

m~~ ~ ~ ri 0 0 % a a go" v54 "A. 4 mUISj 4 J ) 0 - 0 C 4 4) 0

-4 U44 r- w 0 -.4 V- 0 ca*a4)-J4)C)& )CLCA 4 0 4 ) 0 00 W J -4 -4)...4 0 14 - 0 ul4

"4 > ri U J0~ 0 4-1 4 4 -. >-a4 -41 4) Zz04)~ 0) 6-4 w Oc 0C 0-4 0 .o 4J M $.4.0 4 . ) 4))dJ 0 .cco~ wo >1 . urn u4040 00 0 CL 01-4 ad 4).'- 4 cctc0 CL 0 44

co -4U) U0 0 -O0c 0 U

04)44

13) 84)

.0 0 0, m.00 4)

to 4 4j .a 1r

to J to i .4 cc .9 0. 2 -4 4) >

w U44w *01-.4 .4 gcc '0 .. .0 C4-40 u 0 C4 M 0

m0 *0- n .40 *O0. 0l

-4 4)

-44w4- -. 4

-440 444 .4 "4)4 40)0 r40 6 X )

C60

A-li

Page 33: GNAS Maintenance Control Center (GMCC) Design

u w

0i

44 1(

40 41

W A 4

V 41554.1 41 A

-a C - 4.-441-

I- 4.0 w4 u X 40u3 0r

-P 0 4 C r 0 0 1-cccr.2 C: 10 1 0 -4 41 45 CD.4 -4 - *4 W V -L 4 0 b

ula40 4 110 Aj m 0 to0 . 41r4)a - A.U ~4~ 4-1 Cu c -4uw s0.9z ~ 4 (A~ 41 0iu 3 A 0 )c 0 a1

0- C414C. to.4 -6 4 u 0 C 0 Do E-M 31 41 *"4 41 Uzi 41

4) u .0 4 -4~~ U JJ W-- ~ 0 ~ 8 0 *

4) C01- z.OJ 0. 0 0 0 00 AOA -. 4.4 0 J -4J. 05.4 - 4 4100 '0 41 -40 > 4 r 0 > A0 cc 0 > u -4 -4

z w 0E.0 0 04.- .0 4 z 0 0 -4. ina ~ 0 C w 0 $41 0 .0w0 441 0 0 w4 w 0 C0 0P 41 NO Cu4. : 4.4 A0 0 A 0 .a CL A.>>b

La~~~~~~U -4 '.. 4 4 d-. 1

Z 5a.1 0.0 C 044 0 >4

0 -. 00 0 C

w IV" 4 0l- a -4

b .4 "4 -4 c _ ( -4

.444

46J1

5.4d .- 40 :10

Ai 1

4w u0) 0 0-

u rA

A- 12

Page 34: GNAS Maintenance Control Center (GMCC) Design

z

= ' 0U4) ul

u Z

4) U)

C 0 E-4

4)1

1.4 -

4)441

>4.4 U)41)4)

cc 0i- 4.4 0-

V~2 :1 : vr

0 0 41 0 -4 131 to -, -iw a44140 a 1 .4 a0 -4O i

4.) C 0.)o. 0 4 cc '4.4a . 4) (

wl4 0 c A ". -U r4)w.4 W.) w :P%. w *..4&4)0 fto 0 )0 0 a 40-a44 0

0)t r r.& 41 Nj. . r- OU -4 *UC O .0 4r4

-' V 40c 0 0 4 4 1.iC 0U) 04.4.4c)

$4 CS ,-, .0 "4 W0 -4 C )-4 U 4 U.41 0 u) 4) =

co 0 4 U4 4 JV u) 41 >%. 11..4 .4C Or L 4d goaU) to~. 0 aUE 4 1 o

4) 0 "4 Ui4) u0 cc.'U44U4 u Uia 4)..4 0 -414 )- U > )- 4).4 u) 4)

o ~u fZto00O4H 4 )4 )U 4-1 04 U a q*0 >

4

C.4

4) 4ul

4.) 4

0 0

.j

40

4)-4 Uo

E-4

'4.4 a04)0

A- 13

Page 35: GNAS Maintenance Control Center (GMCC) Design

41

44 tVI 0

(0 H .

0-4 41

VIA..

41 41

ccr d , c

>0- -4 - . 1 A

to(t . s 4 - 4go>XUr - ,-> Vac

co 4 4C S.

414 0 - VI VI4 41 .4w u

C j us C a C a 1LIZ C 04 41 C 4

boa A 0 VI..q.. ij u~ 41 U1

-4 I 4J C 4 IQ 41 U -96 n 0 0 4) 0 IU I U 4) r2 J J t96 UvI 40V4-4 0 0 .00COdUCC U..m4 w 4441 41 .4 U 44

C 0 .. CIVIL .JC4 U...

0, 0U V c 4.' 4 4 a c 1 I a

0 C >VV i m CL. u 0 41 u 4V014A

0-44

4 ) VZ IZ

.c

.C

Cd-. 0

VI -4bO C 4I

U

0 VICC

A- 14

Page 36: GNAS Maintenance Control Center (GMCC) Design

J.J~ 4 ~ .4 -4

z

u) z

4)G 04

ca U

U0 E-.

mb X U)0cc-

0 . 0w0

r. -4 C

40 - , 0 -1 r 0 -

0- " 0 U, U 0 u i w a 0 " 0 " *a 0G Gac 0s 0 a O 00G

U.jJ .0 g4)'- U4.) 444W 0 J

,1 . w W go Q -4~ ' -.4 0-V . 0.- V- 0 w- VG r v-. 4 z U 0. 0- 4-,4 1 . U 0 -J. :SJ tO

"4> 0 W > -.4 > > .

z 4.0Ga-4 "-fO a CJ 0 mJ'U0 w0 C"4 W Z00O 0 0

GaUGC4. 0dM 4)'

C6 E).1..W. aU-.4 a4 G 0Gw4~U W a V*~U

Ga-'U cU ~C. - 0 4 ~ .4- U ~ ~

*0

A-15

Page 37: GNAS Maintenance Control Center (GMCC) Design

41

z

41

a 41

ul40

uw -

414.14-1 0 0

Z 3-.4 ,1c

to 41

r. 211 C -

u 4A 4 ( 4w Z1 -4 04

V31 w 0 4j 0 ): 41 -u .4( -4m M -4 w ( as w 41 -4

1w cn t0 43 .ca r.

4 0 .0 44 0 .2. 24c c .Ca] &Jo >.0 00 -40 41 M ci0~~~ 4j 0 >0. . 43.3 b 4

m $ 041 V ~ X cc. w. u oc-cCL (0 4 4 4,O41 -40 0-0o 0 u a C.

ad-~ W 0 4) C c I -D 0 0, 0 4 4 0 -441 00 0-A V0 0.4 V 0 0. -4 >4

0L w-.-' 41fl 0 -~ ~ -W0 dz c 0 w z - 4 4z . 0JJ 0-t 1 C4 0 4.3 )0 0 4 1&Ju.>.Jw

1 V0 ~ ~ ~ 40w 0 m0 ) 4x0a l= 010O & -o(

Ow ad41 0.4 - (D u 0 -4.0 0 w .- u4.4 c

P-41

-3 0

to Ca.

z 0 0-I-'Z -0

.0o .- J0 00.-.-. 04 00

0t .- 4 4..

4)-~ 4.40

0 043

0 0>

A- 16

Page 38: GNAS Maintenance Control Center (GMCC) Design

0z

4) cw z

t.4) 0

0 041 41

1-4 -

1-44

31 wE- 4.w 0 0 .- 1lA

U O -4 .14 0 V - 4-d4 4r

54 . >t> 4 aI"r 4 4 4 0 ra

r 4 to .~41 w -40 a 0 r. 9 B- 00 4)4 >%4 1 1 4$ 4 1 C44 04 0 r. 4.1

to.. UL 1 0 0 .1 0 )0 14.4 9: 0 04W -4 cc )ImA-CC4 4.0 4 I4)0 -'44 0 . 4W 14)0CJ 04.14 OJ 44CC 4

U ( CA r4 0 41 C: . o " c . 41 co(d 40 -4) r.

U0 )-444 r- lB 0)B . 04 44 a0 ca.u44m 0 0 "4).1 C: 0.O0001 4J 0 M C4 4 0 "4$40J.)4104 r .1 3 -40 " J c 0 IV C CL u wU0 z 0 4.B 0 4B ult .U4C . . 000 1o4) 41> o.t 4)..w44.4 in ' Q0 01u0 >~ I w 410 w -r

04 O $4 4).4 B0 a .. 1 0Bz1 0-4CL4a4.J V0 w a 0) L0 W -1 0 B $4)BCO0.4O0 4

1.40.u r 1 0 -4 U4 in 0 -- 0-I

$4

414

4)

140 -4

4.1 0

.B-4

010

14 0

A-17

Page 39: GNAS Maintenance Control Center (GMCC) Design

z

Ci 41

u34 0

1

4 1 0100 E- .

E4-

Cd 4 04 41 4

E- Cr. 41'

P-4 (

w -4 co r-4 c 4. 0) 01u - &

0.0 "4 0 04 b0cm 0 4 01)41P0 1. 0 0Cwm C 0 40 " 4 0) to 4.1-4

u 4 Mr. 4 0 A 4 uA0a." w> 41u0.4 1,0 a 04- C4 V 0)-> C0 4 Aj t 1.4. o 4141

0 C " >. 0. "4J "4 >.0 WE 4 0 a Cd W 0441iA. PI 100 C m4 1u >M I. >. 9 c ~ 03 . 0 1)~ cnm. 0 0 C 0 4 . AV09: 0 CL C 0' 3c

u4 4.j 4 6 4.4 "4 A 4 r. = 4 " 1. 1 V 4d~ w4FE-0(40r C 1co4 041 a1. w 0 2 4174.

01 m 01-0 4 u14. 01 41C .>m 0 Afn" i440X 1C0) C. .JJCIS 0 lc 1- 4 4) 1Cr. 4 c J 410 u 0101II ~. 41 4 1 8 00 .4 0 .4 41 0 A

co 4 0 -A 4.14 0 - 41 " 0- 0 - o=4 ) c 4 1 r

C14 4 0 0 0 01000Nw 4 0 C140 C o 0 1 w-o 0 14r - wCC- 14 0400 _ 10 041 '.0 M0 011

-6 -.4 > I Q 0 0- 0..U>-1 CJ.J4-4 > I4J .4~ >450L0oz z 4C 3 . 0 u.4 a LW

c- w1 04 w0- 4 w00wa0 w0 0 w0 4140

14 V1*.14 0. 4)

41 0. 4

.0 9 4-34

Z- 24C' .9 -4

'L E-- .41.4 r.-.

w0 W W 01cco .144.4 CO

0 z% 0.L

0 01

zCL-C.

41~A 181'

Page 40: GNAS Maintenance Control Center (GMCC) Design

WI0)

u 0

z

c.4) 4 )

0) 41E- o E-

0.4 U44

-.4

4

(4400

4) 4 (4)

4 44) 0) uI.0 r. Dt -. .

V3 44) -4 UlW 4-4 1 A .4)-I co .d W > t4 .4 - '.0 C

m L) j cc l 10 a ol0 -.C6 -. 4 .. C-4 U 4) U'.V4)mJ(a > .4) -4)ZC

1-4 0 r(U 4 C 044 -. 4)- V CIC; 8U)4).4 4-4) 0 - 44) 01 c&

1- 4)-.4 4)(U .CCO U)C.4

Z4 " 9: 44 4 0 4)J.U 0 -4 4J w c 4o0 co 0 ).j vX I : C 4 w )wC.1 1- - )4 -4 ji -.O1 .- 4 0 O~0 04

z 0 0. U$

0 $4al "0 -4C > c W44 M-1 M w44 a 44)1-4 0 4 4 0 0 0 - . 14 C

(.4

4)- 19

Page 41: GNAS Maintenance Control Center (GMCC) Design

0z

C.71

4) U

40 E )

E..

-.4 - =4)

4)44114. -. 0 -

r)4 4).-44 " c0j. ci1. Z 0 00 w w f -4 - = a C

E- OE- M1. 1 0 t 41a~ 4) 0- c- Lr 1 04 )t

W 4 1 4 r % )c 1 co4 . A

z U, 4) 1 S 0 r )CI

In- C 44 4.) 4 4 4)-4= X . CD

cd -.1 u) > 4) 'u) 0 aw4)

4) 0 - l 0I- ~ ) m -4 .14U0 04.4-4 i A" 4 ~4 0~ A4 4.4 W 4

9L. V 0.0 . z 414 wJ.J1.44)

ad, "4 W 0) 00 4). Z 4)-4 > 44 4) B 0v >4 4J0 J 4

04):1 0 0 0 ." 4 0O. w)44 o 0 4)comAi 40r $4 .0 u)4.) . w 140 .4 l W "4 =J4) = c

Ad -).4 CO) Q 0-r4 A. W c4)4-44 O U) CC 3. -,4 0

-.. 4 u.4).4. 4).J. &j4.. )~4 ~0to to -4 0 0 U.4.4 a 0 >

sw .b04U)-4 ci 4).- ccU4). 0.go 0U4 40041 4)4.4 ... ...0C6 :1..4 U ).4.4 44 4)4. ) 41. ... .~ 4) ~ 00~ J.J1' ' ~ 4)4 '~0 )01. 0~4) ~ U)

44 4)

A-2

Page 42: GNAS Maintenance Control Center (GMCC) Design

4. j -4 10z

U) U 0. 0-44cc U 4) Aj 4)4. .

c., w o

4)0 4) 000 0 1-'U

0 414.4 m)

.0

0 F1-4 4.1

4.1 0

"4 c I

41 4)

0-4)

44.4 4 ) -o cc-4 toU 0 w w 0 0> 0C c

CA-, 4 C 4"4 4 4 -44 410 O -4).W 4)0 .0 4 ,4U)

4) w ") w *.4141 4.4(.1 .4-1 Z -P4 o 4 0 "49:

... 0 U.1. 0 "4 04J , 14 U i 0cn .1 41 04 r..4 4 44 ) 41 4 04 -4 0 >

I 40 4) 04t) c -44)U 0.4 -4z U) w c.a tbo 60 % c W o0 U 44 C: -4 C z

to U) cc~ U).404 V. 0)0 c) .44) 1-4) 4)..4 41 w. 4)

1- 00-4 0U a V -4 w U 4) 1 ad)4)In g U41 P-4 U0)4) 41 4 004acc)0 oz CO W W -4 4o $4 U 3.0 4)1'- wJ >) U) (w) 4)U0. " 0 4)1 4J ccA 0

0' )4 .c )0vw9 t U 4. a4 . -44) "O4 w0 ') O-4 0c0 4)4) 0 w I 4) . w -H

"4a a im v '4) -4 -4 w 0 w. 1.4Mo .. Q)4 4> 1 w C > 1.0 w C) 10) r0 4) "..4 0 C 4 04 m 0 a .4 0 414) to 0C) 0 4)

0- M, r4U4.14 40403 CL 1c L 0 a o

Ez- 4)

0)0C

1-4 -. 4).

UU A0

4.14* 0 0 4.1

0.14 4 0

1.. tj 4.1 4

4-44.1 -'-x

0 0 14 u) 0

4A)21

Page 43: GNAS Maintenance Control Center (GMCC) Design

4)0C1 a0

A3 41 4)414

4). u 4) 0 00.4 CA-44

4.4 to3 4.

00 E-4 0 .0

-2 cIa PCo4 414

4343

43

-444 0~- 0. A4 4

-4 4 c 0.

.41.0P 4 .0

- 0- 0 4..-3w40 V :-dt 4 t

-444. X 4 u4 9 44jW4 0 a m r

40 wr 0:4 ) r )C 0a W- a-0 0 4uw 4 )- 0 01w

V2 14 34-In 0 u 0 60 1-4

0 04. -4 -4 0 00i 41 ZJ0 41 4.3 40-

01 "4 w1. go1'0. 0 -44.3~~ ~ .04 >.0 434J4J 41 ~ .

06c.. 4;1. 0444 0. 0 4.3! c41 u4 4 u 40 -0 0. 1.0.4 0 ="4 u1.4c c U.4.. >0~ 0 41 bfl 0 A. J4o.4 J0 4)

ps* to. w0' 43.0 41 u 4 40 C w. 4.43& " 0 V4 0>sO 0. 02Jr 4 0 0 43-0 43.40.0 40-.4 V oW 4 r. i -4 V Vwa 1 0W - 3--1 4 J A - 4 J.3C" A-4 0tvo -1 4v ".440.

> uW. .4-.4 U to a .4 3 0.0 a 1.uu34>41ra4 Ai 30 0 u 0 u w 0j 130 10 w 0F4. .04 W0o0 r

w4m 4 0. w3 w 3 w4r 3 1440 w 00w14 0 0 to 0u* 4 CL. .Cd co-4. 00 0 0 w 60. 344-

1..0 .4 0 . 04.43 43 3..44 43"4.3 li. 01 4r_043 0)d 0Z -4 0~4 43 44.44 3 0 44343

.13..4 .. 4-- 03 0- 04 0 .J r.- 4 4

w V - w 1-4 -0. 4. .4~ >404 W A .043 0m1. .. bO3 A. 043 0 zb (A -4ca -4 = ~ ~ 0 u0 3 4 . -4 3 1.440 W t 3Lo

____ __ 4- 0 4~..- 0 . 0.4 0 a. 0- 041. 4 0..4. U

ciccE-.4 434 4 ).4.3 u0. -4 1...4 -4. C4C .4

904 u0.0 0 4a u39LE. 0.~ = If6b 0L.0

1.4 *b0 ~ 0 0 .-4 0 Un Q0-4

A-224

Page 44: GNAS Maintenance Control Center (GMCC) Design

0) c

w 4 4

u0 E- 9 mw., ;P%

4) E- 4J M

*u 4)440

0 ) 4 w-V4

0 W94 4

w4.4C 0 0

E-CL 0 4j .4 .. 4lwcs 0 0 0 0 w to0

CLCf W i 0 ulr.. 00C-

4) 0o U6) o.4 W to Ow.0 -4 C2 Ja.00CC "4 - -. oC-a

C U) 0. 0 In~ 0 4 cc a-I 0 0

" ad 4 Q ..- w r. 0 AW C.inu .) 1 4 c 004. 0 0 M0 cc0 -40 .

z wcc ? 4 4) r.

0 w.4- 04 41a 1 1 0 4 CJJ W4-)

cz 44.4 ~0 4iu . . 4) 4 0 CCL* 414J. >ICf ~.04 4 (1 w C -4 4 .04

> 4 ti4)0 -4 4) 44-

>.04 0

-4

4)400 4)

A 4 '. .

u 04

4- cc- 41 C36Cto ' C 4) W .0. a

. i0 0 w)

0 0 -4 00

00 -44J '-IC1.' *0 . - 4C0 0 N.. C'0

99nu r a)C6 CL

V1.

A-23

Page 45: GNAS Maintenance Control Center (GMCC) Design

z

14

-1 4)

440 0-

LW 4J 4

> -4

4J 01- 44.1

-. 4 co

an0 1.4 r u -4

2' w l-M*-4 -

0 ~E U 0AC

0 4 4 V 0 44

j 4 0a 4 00

&j0Ul 54- - C0 -r. V 0 r. 4J 0 -4

bo 0 l A 0 J1. 44Um4r 40 0LU4L" -4 0

n"4041 r-4 CC 4LU44 44

vo 0o r-4 O. cJ E 41 C >41W 4J0 MC J~. 0 a2

1.41

cn .~4.1

Z4 0

14

4Ccc

EULLU 0

04 -4

0 0.

A-24

Page 46: GNAS Maintenance Control Center (GMCC) Design

0z

=1 v

0 Z

41U 41

w . P--c

411- ..an 4ad4144c1114 4 c

-. 41 1 -4is 0 4 1.1)c -. 01-4- 4 )4 Z 0 4 - 4 0 4

.1-4 -4 44a'i4 s 40 w .44. 0 0 4 c 1 4 0 - 4 C

co41 0. 4.1 -4 t j 4 c

.0 r0 0. t1 0 a cisI:14 io c . 4.1 w14 u .4 41 : 4 -000 41 r.0 .cc V G : L 4-4 4100

4.1,y -4 w14 In c ~140 4 ~ 41 mri.0 -4 .- 4 4. 0 0 = w41

0. V.~ 44. V W.41C1.141 4)044 SUI. 2.. 00 02.0.4-.

Cfl § '0 0 U)W- 444 0.04 0 1.4U 2a 1 444 . 0.4 1 4 . 4

P-40 1.0 0 *4 U UW ~ .44

>4~ 1 O 1 1 W~ 4~ 1 41 .~

-- 4

0.

CaCL

-4

0 .0.0 In1

A-25

Page 47: GNAS Maintenance Control Center (GMCC) Design

02

41

0 H

U44 0 04

4) U)4)( Ps6u : 3r

ao 41' .4 a M4)410 -4. '44 4 3

W 4 0 -4c

0 L r 4 .4 0

cc0w41-0-464 00A

1. 0 bw"a9a 4 4 a 4 g V " 0 aej

u.4.4 w 0 0 j 4- 4.

0 CL = .0 _00 4- 04.) - *0 Wr 4 .0 41u0-4 0 z 40 4

-44)4) W 0 II w4 to 1-0 a0-

004-40 "4J 06 41 4 40. ".4 J0-. U 01Q-0 Ia hi0h W 66 a L - o 9 0 an in0.

444 C. x C

06.0 0 '~ u) O.

~UW .).)o4

41 0

goo 60 . n

w~.0 V C4 -4

o0 as 0 00 0A4

-4-

4-. 0.

0 u) l-Cal6 .. 0

04 . C11

A-26

Page 48: GNAS Maintenance Control Center (GMCC) Design

c. w z

0)

00 E--

000

~~E-.

u -

a~0 0 .V 4bx 0 0 .4 X -4 u X"4 =0 :

0) w Elw0- 0 . At

8 ,r 4-4 r. r 4 4 . U Uw a .- 4 WO 4 r_ a (2 z

-4140 0-4 to w ~ w o 4 -1. *4 4)z

zc 0 w .0- 0J- ) c.- v r_41 tra u ~ 4) X 04a 0

us V 4)k u t. w u 4 -. 4 co44L ) .004>4). 4) 54 - I.J m a 0 4 c 4 4rau -0) 0 - U &j X 0.0 cc4 V a a0 V a4 a c .- ow Q 'i 0 tm CO u 0 14

0 = 4 .4 = 0 > 40 a4 w.- 0 m .VCU..- E Q 0m~ 0 4ca f& C u

.MOUO~~ - .. 'o-4

P-4 m>.4 U . 0 . 4 ~ ~ ~ ~ *

-4

la4 c 41

DO r ai

(6 4

> V6

-0 mu

006

4-4- u

4-4-4 (60 0 U* -CA) in.J v 0

A- 27

Page 49: GNAS Maintenance Control Center (GMCC) Design

2:

0V 41

c1 w

a4( 4

U0 F4 -.

.4 -

.4 41 4

01 -4-M

cc 41.

w -4 t*4 0 bO 0) c bO0u0A--44. 0 Cn *C 4 3

41 0 .U4. = 9 $ 41 (944

0) 020 4 O J c "0 -4 41JC u cc 2:x 3.-' 1 3 "~ 0 .l0 -

".4 A0C 0 0 A V 0 toC, 41ina6. re w4 *-.44 bo. U3I 411 0

4. lcn 4 43 QJ- .~4 C . 2: -4 9

W r-4 "Ca.JJ"440W41"J,14U -O41m 4.1.4 1-1 441 co = 9: .1 v- a

00J 414 41" V 11" o$ 41 4

.I1.1

u.4 .C6>a JX1U) 0w :0 w 04 41.

41 ~ ~ ~ 4 a0 ,01-41 0'-4) 0.4-4O41041 4 4W.0- 0.4 > 0. u o 6 6 444O. (A 0 4 4 .4.141.-6 . mu " -

1. 46.4 cc4. -4114. a4o1441a

C1. *0. C1 14 4 04 w MO "4 41-4 41~4 1.44S.4J3 0 W Q.4J M 0a 2 4 41

1.4 m (4JJJ.41.4 C 1 .44.

1.1 0 .0 .0> W " 4 41

41 04 .0 1. 4 0-4 -4

"4 1 1 "

Z1 -.4

4~ .10) 0

1.o 4 1 4 11410 41C.

U2 6. 1.

04

$4. -1 z.6

'4.4 -' 4 -4 0 6 va1 'SJ u 99

A-28

Page 50: GNAS Maintenance Control Center (GMCC) Design

J..- --0

Puz

w .1 Z-,a 0

~~41a)00

0 1 c )>0j U - 4W4 1xu 1 nC 4 4

ci g h- .4Wwgo G a0 4

414 -41AuP 0r L c

clE C v r . d 4004

In 14.4= 0 'a .40 4.I-4 .4Ca 0 14Zr-4 r 0044J0 14Li c -4.b '.4 J.

'.41co4 W ci r-0E' 4n '4 00 4'I. CA. 0 40w 1 4.6 00 is S.4~4 16 O.0 Q O

0a 0 .0 0 0 "4 c rA .w.4 0 .- 4. 0 0 4 4j. 444- 4jA

ar 0 Ai 0, IA -4 C US.A .4 0 0 0 c 014 0J.JO 14 J.5 "04 " 0. 141 u 0 >

z U1 44.Jcr 4 0 0 to "f c ".0 0 ) 0 0 -~'4 c m $ QaC Ai.- '-4 41 (&

W 444f4.4J 41 40

00 CL 4)30

14

00

C. I 4.

0 00

00 4.

444.

gm4cu0rn0

0 0"A-29

Page 51: GNAS Maintenance Control Center (GMCC) Design

4) z4

(A0

w ) (D4a taa

a 41

41 41

4J 4J C.M.4.

Ci 4 en

04 - -

'e. -44146

WO r. a 114 u c3tLz 04 0. .% w04%1 4 6

414 r-41 '4.4 0

0 0hi 0 441 s a10 A

z 4) 4. 4) 044 . 4 1 .9 4- 04

x 4)ca 0ta . 2 4J 9 -

*.-.4) .40 = 0 o 1 -w1 4J ca c 0C Ai414 u0jco

; , ul 41 t F

-mco4 4 44 CL .1)4 4 .4z 4 0 IFA.44 hi m' a- 4)43 0 0 -0 '1 00 .cr u 0 U 0 -1 w .0 4 C ) .

uhic 444. 041. II4 0U J

0 a -4 4 14 4.0 41444 to 4.

4)41041 ~ 41gw

4)4 U .a J~ U 4 4) h 4) 4

..4 41 41 &, w.J4 4 .i 4 4)

cco -4 4 ' 00 . -.-. A

03 cu C40. 0U 04)4hi4)4.44. .. 4

_ _ _ U 04) 0h 1 41 .o> si > 441

to of1.1

".4 4 4 41~4) 44 w4

441 --4 4J ~ 4

A-.4 .) ~ A .30

Page 52: GNAS Maintenance Control Center (GMCC) Design

u 4 c

u 4z

4)

4) aw-nC

0 4)t44 ul

4) a 4 4)C e I- .

1.4E-

4) 4 4

4441 '-

zl 0k- cc0% -

'4. w. ho4 1 1t c 1 4 L0 )4

ca 31 440 4 1 %4 ) .

f-4. 0 Oc>a s 0a , w0 1r4444 -. 4 44444) 4) z 0 41 .0

x mt 4 l C 4 4) u : 4444) r).. &J JZAj4 444 9 0 .0 4.4 4 Q -

4)41 0 4 to

04 -, 4 1. 1-0 t 4 4)4 1 -. .u1u 4 cn -4 FA m4c 14x r- .04)i 41)a >)44 .. 4.4 .0 4

4) 14 cc 0 0 C44 *.4)0 4)144 '41J (A : -4)z c4 m 0 u 04 M4 U 4) 4 ~ ca -14 4 m 444

a r 4 3 4) 4 W 4 34) w 1 C 4 4 c .4 40- 0'-~44 in4) caa t ) C6 A 0 ) a t b 4) -1E-4 4J.4 4 olCN 4 4 I. -4 44) 4) = ~ 4 C )

cc4. X ~ 4) . ") 4) 3 :4E 4 4)4. c0)P-4 -4i~4 0% 4 ~cn W V34)- 4.4. 41~*.

0>)- 4 ) 44. ) . t 2 4 10 1-14 )

$44 *4.

1.-44) ...to41

Z' .0 4) >4-)'A a > tA 4 W 114 41 4 -' 4 Ai (1)

"I - c4) C4 cn 4) en 0-4 4)c4)3.0

L.- .44) e CV 4) e 4) 4444 .0 u 0 4444 r.1 w1 -h4)I C 0

cc4 -4'. . 0 -4 4 r0 4 C4) 4 *-4 w

44c C4 v 0 ' N4 0 v 44 (a 4 CA Ai0. * 4) 4)4)a4) *4)4)4) . > * 4 1 44 u

m~~~~~~~~~4 u0"0 4C ic ea 3W a4) >U- V

-4 0 .- 40 .- 4 0 -4 0 z

64 X -0 ~4) . 0-1 0X.-4 o

4 - "4-4 rA z0

40 043 *43 '43 u

A-31

Page 53: GNAS Maintenance Control Center (GMCC) Design

4C)

00

4))) 41 ~ 4) 41 4) .1

si J A 4) 41 (1O

14 4 1- L 4CLn

wb

00

1.40 4 c.J

S-4>C

4)4) 0.. u.

gow 4 4 6 4 OCr Z 414)0 -4 0 4) 4C3 u r

u2.In~ u. OX 4.1 4) w 0 = Mxr. & C -4 J

41 M.) 4.4 r.0r "..4 4 31 toJ M 4(a 0

w 4 . ,4 4)CD JU 4 ) 0. (.4U 0 uM .0w 0 -.. 4I4.C0J A falZu w4 4) u 0 4)

6 0 0-0 t4o 0 4.) .0U) co U0" 0o0 V&-4Vi :s d '4.4 c I .0

X5 in r. CWC 04) 1

.4A~ Q. -4 ).0 Mr.C U 0 " . 4) 0.0 4 ) 4) O4 w InC "

c-4 r r04 4) CL 4-4 4 4. as a 4.4 . b $

zC 5 " 4d0Oc 4)4J ) -4 W 0O4) r.gCaI 4) oCd u ) riI 0). c4. 4) a wM 0 4ado C: "4v 41 C6 0-4 C4 r. 4) 44 m0 C $4

4)- 4) I44) 0E W 0 a oa . oV0 0-44) V

C o0 ' 4.4.-44m- "4) U =0 4 4 4

z c -4 0) In 0.a W "44

C14 0 w...4u

W - .4 >.

U 0U040 0 . 14)

04 4) -4

1...0-

54

C13 4 0 4)3144H4 z .U( u

4.)41 q j-. 0

0.4

4-4 4

C 4. C 4.4u

-4 0Iw '4 40

C4 C-

4) 4)~ .- ~.- 0A-324

Page 54: GNAS Maintenance Control Center (GMCC) Design

0

C

U!n r- 0.l

40 4) z 0 .J

00 ~r E- aAj CI4

41A0- u

0 0)4 4 ~ '

w 41W

,a " C00 "

U - 1.) > u0 N W 64)-41414144 A go= UA % 414

441 ~ l C4 4 w)1 u t 0.t$4 co 41 ) w .0 l.4U w ...0 C * ~441 0 U0441 C 1-a1.4 Cc 4j " 4c444 0- ba .C 4)4.- -0 01. 0- 4)V44U> 4-

u 4~1aa1-4 C 0.u C -4JJ - &10 n 41CW 1.4.. 0 c1 104)

OM W 4) %M C41 Q1ao b 40 Q W Q-a 4-a C41 -,I to 4 -. a -4 a w -a1-4- 0) W 44W 0 b4 W -P4 0.4) 44 -Y 8 "-4 .a) '1 .4 J 0 414141C-.a& -4141 Q U! 0J.j > C = r. -4 4 aU 4 11-ICCj.) W 4 4.414 C4 4 ~-J0 Ai -,4 u4

$4 c 0 '4 4 M 0 a 4C 0 - C 4J -4Mo..-a21-j-c. 0C4 u! )t c4-1-4 o 1 C-4 W-4' - J 4a4i-4-

z z 0

a-a

Q0

aA-3

ME

Page 55: GNAS Maintenance Control Center (GMCC) Design

00zr-4

4 0 w c C41 (D 0- 1 0' u

91) 4) . ).

4) U .40 0 .

1.4 4)mmt .41.

4.4 ama)4) 4

W

U2C3 -4 x 4

411

-I 2 4)

0 1 ed r.4)4r 4 $4c n 0 4

41 .0 91 r.4) ) rV r 1 t

-4)-4 a 0 t 0 0 .U jA

us4) C 0 U 4)C 4) r .0 C.: w .IC

4) C1..0 Ow uUI A 04i .4 " c c

0. &j :O -040.J ~ ) ) ad. as4 4.4 cc I-4.44.J 0 4 )4 O-.4.4 -4.U 44

0 04) 0 1 '0 0)0&J W I.4 6044 M. mm44 E U"Iv96 :3$4 .0.0J . 0U 4 -4 W 4 41 4 Z0 -00 1 944) 0m -4 >.14 0 %41 m 4 4 CL)1

00 44o) 4;s:1t ca 0 a ,- 0 -. ) 0 LI C J. "4u .0 k4.) W -U L44)U 0 - )2 4)4 L 044 .

P- JJ.ZOU4) .- 4~)4)J*.4bO44 U 1~L 01cis-

4)' U* 1i~ . ) 40 4

4-I

ba r.4 ca

I. 4 4l

0 I-4

4)4)

100 u.- .D

A-34

Page 56: GNAS Maintenance Control Center (GMCC) Design

0 3)A.() .

Q 41 A0 4) 41 4)." .WI l -4 Q-4 M W0 -u 4 1 0 414. 41 -0

4. ul :1 ca :1 u0W

041 41 O

41 0C.4 t-

InIW

4141 a

--

go 4.4 0l 0

41041

4.) 4 441 41 4 a A 41-4 W

0~~ 44 .04 ...-CL x 41 u C4. 4040 v 0 . 41 -4.

w u 4 0 4 0 JJ1(A 4. 4 41 0u

39 -.4 " 3 w ul- 410 C- A - )-4 C: CO $4wn . 0 u % in . 0 P 0 0 bo..4- 0J Ai "0

U 'm aC =1O.- 0 4 4.1 4 ;N 4 Zu2. 4 414a4 . 4J41 to ul0 w4 U V4J . 4 44041l -4 0 4)$4 4 cc

41 I.0 Z41 0 - -4 r. 1 0 0-4 ) -4 4

.=1A V11..W -4 l. 4. w~J 0 4 cc Z Cd -44 404 0.41 .04). a -I44 * 01. 0410 0U Wwb *-4 a~l01d1 14~

-4 0 u-403c10CJ. ad40. E-4 z0 u w I0o.0 0 >

0 c o 0 0.0-4 U00 a 0t4-

) .0 44-

z -4

Q1.4

.0

$4.

044

0 0ad. i

A-3

Page 57: GNAS Maintenance Control Center (GMCC) Design

z

000

= 0 U 4 0 4 04 -10 go 0 0 0 -W4341

U- 0w. 414.1 E- 4) .0I1 .4

43 0 CL. 034 .000 4 3.4.4 344.4~41

3.o -d 0

440

0

x C -

44.1.

0. -4 c Q3 .. 0

000oJ~ 43

.34 0 to 0 1 cc.'0 -4 :1. co "

44AJ A .. 444b004 -.4 0 s 0 >4~ .01 U0 im E 3. 40 .0 .41 0 4-44 o ( L i 4

a a 00,.4-- " *b " C.-s 3Cho 0 04 , 43 .0C*U 0 u .0U .43.34340 4.1C c C:U .0ug "4 00 3. Ai 4.) -40.4 -4343o 0i 4 tz 41 4 l 3 >% E0.m0. to 4 co a cd. -I0 m4.- -4

Z. - 4r 14 ZM4 V U 4 4 00 43.1 00 V 4

I . 4 4-1C3C4 4 40 44,0 0u0 u4 .c% 040 c 04 4

" oda4o3 1Aj r 1 0 3 )4

a4 0Imr 40 JQ04 n-43 0040 4 b o oa u w4 i o a .

u w43004 a o 4C 4 *0 ( A >-

E-4 u 440 0'44C " n 04 w _tz0 to "00 0 4 0

1-4- to4

$4.

E 04 Z3

-,410. E0

41 43-0 C0

~4.4 0

.- 4

A-36

Page 58: GNAS Maintenance Control Center (GMCC) Design

0zC

41

-. 4

41 0 -1004 41 1.4

'a ~ 44412

an 4. :144.4 4 0 ( .

fj -4 -.4 r. % -4 = =0 0 t 1 O 9 4. .04

w 4 ( 4 Ow00ri 4 .0 4-4~~~.- u 4.. C 1

" . >% cc x >. 4 0

>. 41 4 41Zb MC~ 41 414.0 " .0 .

-.4 Uj W 4 ZU-,. C = AU " aw 0 0 -. 41 4)W 4 - 0b

-4 c r.9:4 -4 -.U44 .4 0 to9: . t 0- 0400J -4.0 4) m w ad 0X 0 (0 4.1 " C CA

tzv o- -.4 :1~C ). 1 0j v C 31 41 u .. 41-4 0 - 04w1j 0 bo1. u41 c 0 " -4 W0 4 r 3I- >0mu u 0 > A 41dc cocom". 0".44 u41Q2W40 -4 C a. ca Z

0 4 .~ 4.O ~ 0 0 0.4 41 co 4-4.01.4 ii 0

0-.4 ca4u -4

z to 41Z1 q-4 UU

41 WU4 1

-4s. .41 00 rcc 4 44 -4 c~

w0- V un 4 & .4 C .

0o m ~ - -4 C)0a

0(1 04j 4.44M)4" 0410 4 . 0 0 Z LW

4.4104

-. 4. ...4e>Cj>4 C. -4

-40 cc 041 ~ 4 -4 4 -4

tCw41 p440 44 0 4

A-37

Page 59: GNAS Maintenance Control Center (GMCC) Design

0

4.2>

-4

1-44.4 U

Ajz -. 4 4 k i

-1rC. .40 rr

u 4.0 0 4 43 . 40-4-4"41-4 .4 4 .4 41 Ol 9141CO

0 a 41 4 0 a 0 r -41 2 .4 64 w 4.2. Q b2.54U 4 m1 4" 90h-.4 Aj 0 *a2 41 w -

go. a mC j4 06 4 .41&4 41 0.nli D10 40.4 W 4O .4 06 . 0 CmI .44.2>

4.21 00 042 w ~ 44.4U 41U42 -. Ud CL m~ w 4 126~4 .).o .-.- 4

UO woo -44 cdI~. .4 421- r .4 .0 -4J 000 -40 .- d4 0 0 - .us4

010 Q.~. 6. 4.4 m20 ~4 . J. 4U 44aw~ soCLz3 U~ .4U A 0 0w. 1 coJ U co 90 d4.241 U1 40 a 0 4 0 rA 0w 2.a

044rI4 ca 4 w 06 .0 93 Q 4 EVzU>2 caI rU6 4 w4 U 1 -. w04 U44 1-6": 0 44.-42 ~ U bb

w4 U 0 0 . z.0 U4J 2~ - 4J 0

P.~0 UA 67 -4 w m 0 c 4.4 4

00 .1U4.r.2w0-4r. 0 .0.

r-4 0 4) -4 .4

4- 2 4242UI-a A 0 UC 4

002 r24. UU c U 424w04enCL 2 0 e 30z0 -4 cr

u zU 96 U t*A~2' *0 .'U EU

004 C~ 0 0 44003 %I4 0U 0A.' 60 2 (~4>

UU-

.10 .4 .4042.U 4 I! 4

in u' 060 C. (A ~

A- 38

Page 60: GNAS Maintenance Control Center (GMCC) Design

0

CD -4 -

4) cc0 K 0 0

4) (a0

0~ 2i 0 u

4-4 W4 ~ 4

4) 0 )00.

4) ca 4

0 0

E. 0j 0 w

so- 4 - o .4 C

4'0 0 . )u 0r c4

Q )4) 0r 411 a.14 4

E- .u r4c - , - 0

KO CO- Z) '0)04) gu

6 4 A A- - UU1 404)u> - cc C 4 r 4010 4.K-

41 4.1 4 1.4 0 m 4)U0 4) to 4 0'CL N . K

r A0. -4Z -40 .D 46N -4 044r.3 4) n 0. .0 04) 0 * 4.

-, .- ) ad4 -40 bo -iC 64) V A0 0 as c c - 1 >a

40 4) t-4 $4 C ~ 0 7 0 a c 0 0

ce 4 4 4 4 r, -4 4I 4)40 -1 CL 4) -~ 4). 4) 4.4

4)4

.0 41)4.S0 .11 -44

Z 4 u ..4 >% wAj-4 &j 0

44) Aj .0 -4 0l.-4 -4 do *- V)

w -44 - 4 mf .0ho~ r. *. Q . t .0 U00 4 t4) Lf n U41 %n - -44 cc

0a 0N C4 (C.4 ( O Cm ca en 9

w 4) . a . > >%41

4

00 0 0 0* 4 -0.4 "4.. ~ 4 -4 .1

>4. X Aj. > >~. ii > 41)

0 4) u"U ~U U 'I

4 ri - 4 4 44)0 I=.~ 4)~ *U 4) uU *.u a

A-39

Page 61: GNAS Maintenance Control Center (GMCC) Design

In

0z

0 a 0ccz 04 0 0

U1. V 0 0

)., " $0 414J41 E 0 . 4). 01-

041

0 0~

x~40 a

4J' -4=

4.1.U

0 . ~ .4 00

41 Co 0 b0414 -6 A.

0. 1.k0 .00 4.1 4.4"4 >% 0~ 0 c -4 400 02 .- 4 0 CIuu 0. C.1 0 W U4.6 W -4 to CL 0

U4160Q r. 0 "A 0U41 10 -. 00 a 0 U ~ 0

slow. 1.4 w4100 0n 0ow 4~~4W ~ 1 4 Psa 0 MN .- 601 j44 CL0.V A4Ju

c0 > 0 -4 us 1041 0 -4 0C6 V4.4 c 4 as0041 w 44414.1 a -i~ 4

A. 03 0 cwin- p .40 0.40 049 %

-4~OU 41 44.1w

> > 1 -V

0-4

ad

1.i-aAi

0

4.44

0 4.1>A 41

A-440

Page 62: GNAS Maintenance Control Center (GMCC) Design

4)A .0

4)

4 0 43

43 -4 - M4.0l

- 14 0 4 HA i1

z A- '-4 CL cn 0 -,.V 4

.. )4L3o : .43a0UA 41 fn c :(a9 o 1c

Ji z4 .044g 41 -441 s 4 4 41XC:4)r 4 40 C-4 4 43 to

0-4 u r Q 0 0 a 1in4. ~ 4 340. 4) C'J w C r

z i C-0 .04 1 0 8 C 41 Cl 4w.4) 041u J 46) r. r6 ari04 ur 3.

4W4 to 4 414 r.44w .O

0 o $ 0C 1 I.4 Q IV "

43 0 w14 - 41 *O0Z ar C: 541.u0LJ go. I443 ~ 0.a c cw r 41 c

Lr u3 $.Z40 . WO Ia w -4 a3041 4CL3cc

o -.4 0 0 u0 14 0 W.1. A .4gQu& Z 0)0 V U (a M U ~00.9L44 In JU

-P C 0 r6 0oZ0o.41 - u

z 0 4 toc ao 4p____ __ .U ~ -4'~l-4..4cc

>4

1 .4

41Q4"44

44 w

A-4

Page 63: GNAS Maintenance Control Center (GMCC) Design

0z

1~ 0

0 . .

0 f A r

4 U .4 41

a 0I

a 44 WI

41 0 r.

02 to_____r_. r 0.

ul~~ 000ce

Z - 0 z 0 a0 0..C. - - E

4IO 40 V .0 0 z

0 00 0 4 4 U 44w w M 4)-

Urn w4 WIJ4U 0 . -4 0.in d -40 0%r 00 4 r. 0 -4 41b 00e

A. .10 *4JA .a ub5dIa 00113 ". WI.I4 0 0 4 .s 4w -

r 4 -.6 It. 6-4 0 .0 84.4 0 C 0. &j

0b66 a0 0 05.. $ w00 '0 IW4bJ '06

U C6-0 0 84 6Ut0I CL w r.a L 0. AU

co 'A ;~W

'-4 ~A-42

Page 64: GNAS Maintenance Control Center (GMCC) Design

0100 a

0

CA 01

01 E-4 C

I- E- E-4 H01

00 0

01 cc 0

cc01? o o - .- 4 -0ra1 -

0 01 01 w 0 01n 41010 - -48t01U 01 4 a > 0 0 4 w iU

(4-4 >., >% to0 -4c V wa 0 0 0 0(n~~~. w 1 40 0 A 4 mu b1>

.4 -0 h4

4.4 01a -44 4 4 0

01 4. :.4 M

r. Cl- MJ M' 4. C %10d ' dW- c.a 0' 01c 1t - a a a>

C6 01 319 jAja 0 c

x~0 >1 1- 0b 0r-4 0 CV r.a A 01 r_ 1

z C - C 01 - 4 0 .4

01 c 0 v 410 0 41

0 0 13 " 00 .0 0 C3 0 UUiI 0ad>41wc >J. 4J00 11 AJ1 0 o0 0 41

a-4r.~ o 41 w-4 0 010)-E$4 40 01 c QU .4 -O0 $ C) 4

1.1 01 .o A.101 9 41U 0 01 vC 4 AWX*

41 (d 1.- 0 0 *ZV C14 01 1 10 1

r1 r. 010

-4E ~ 0 -~00A-430.

Page 65: GNAS Maintenance Control Center (GMCC) Design

U,

0

zh 0 0 0-6~ .4 w4 -4 -04,..

4 4 Ohi 0 Q a 4114t0 w4 4- w1 (a0 w

0.0 CL 00

a41

(44a41E-41

EW -4

0 01' 41

0.41

14-, CO141

01 cn-.~ w 1 0 0 0

-A .0 ac 4'!E-1 0I0

to~ 00 $a1 044.Z u.a10 0 CO ". s s0 .

01 asmu4 4104 -P4 0 41-41 cc W0 to 441~i m04 u C ce- . .4 -4 :1 u

wn 41 cd 9 0 jaL .41 ccdo a.41cc 0.toV3 0 u a al - M1. wJ. 444 01-'1 0 4

U 0 0 4W CU. so4(. >, L 141 mU riw. CA0 u -04 CL = 1U 44-0 -4 .4. M-0 u 11 4. 1 CL -4

41b1-41 -4 0 7'444 410 0- c .2 04 cd 4104 w 4 0. -4 41-.- -44 -41w

r.0 V U 4 0 U 'ba I0 U4o ~4J 014"M .1 a0 00A41r 414 i -4 U0 c a 4 0 * A 1. 4 j Va - .0

1.uoOO 4 14 CiJ 4.4 to Ud-4 0HO 4jr4 UA0 >go >10 Z~ h -O 041 O

w U 0 . $41 044 CLa. 0C4s v 0.4 c awoa* 04

W .

E- -4 Z

41 E-4

tic0 c411-ca 4-

h a ,99 i . t.f

41 000000U4. 0 0 >

4104

Page 66: GNAS Maintenance Control Center (GMCC) Design

00

0 u 0

'041 41 4~W tiu

:9 - u

-4 0. -4 >-4. "4 41 0~-

0W0rI2 1

I- .- 4. 4) 4 0 W o.0Q r.0r

ta w.4 W3' w WI n 4 C414 4o - IL$ 1 WI -

0 r05 aW c4U c 404 .0 4

41 vs~. CL (1 41 4 44 Id4 1.0 NI. m~4 z.44 .4 ~ .4

= 1c 01 4 ... c .4 41.04 u 0" 4 0 M-6 4 04 WUa .440.4)41 41 3 0 41. o &1 41Q 0

I=wI 0t WO! u 4141 %41 ZJ1 4-J0a1 w0 41 a 0 0 -4 ~ O 411.

-4 a~ IN 0~ a1

z ~ 0P.% -441 0 W .- 4 u a 0 u0 4 ua* to 1 (A- '4. 4) v ww v 0w * 41 .

a~ OW W.-4 0 41 % a - c0 444 -~0 zOWcIc

2 d9 * 14' 4 14.440 c >0 ;p"0 ae 04.491 r. r.w ) .. 444 01~ 0 a m 0 w 41U.

- 4 01 4) w 0 v0 1.4 &J44 w W>.41 0 $W00 uIn- 3t UW4 Ul c ad a C 041c 0 00.WIWu 04-14-1 ca

3-4

1.4u a0. U .0U3 1 . . ; 4E-4 z- 4 4.- -

41. .

aOaa

4 .d C%;

U4 0 0 0 0 00

go 0-00C 0 0o

__ _ _z. >~ P~ z. z >

A-45

Page 67: GNAS Maintenance Control Center (GMCC) Design

41

00

1 .4 bo bo 0 -C

L~ 41 W ~ -4 0 aa u

w ~ ~ ~ -- :114 w0001a41 4 1 iI 01J Q 41.4C "

01 w 1 ".1 CaJ 41 c :60 % 0" C t

041

U141

44. 0o0-4u -. 4oa

.2 41 0a Co10 41).

0 1: 4 > i. -.44 1 0 4. Co1 .-. 4li I -441fad 4104. 418 410

U 0.~ V1OJ ul 0 1

g$i -. r. 0 4 4 UW. -4 a V

S4 44 A4 14.44 4 -4 -4 -4 1- 41

U,4 4 .~4 w 441 -441J. " 1 CO -4

0. 04.4 .4.4 m41 Nz 4.

0. .41 IV 03 94 0. 0.4- w m r

04 C . i14 i u

1- 0 0 "P . -4 W . 1

-4.Ai C:-4 -4 -4 "4 4 - 4 c

4141 - 4W 4 -4 2 .4 A .-4 JU -

*0 444$4o 0 40 A 0 FAa 0 aV 0 cwj. 0 r. 0 4 wC0> 4-4- 0 0 w41

4141 -4 CoCo O -4~ -4 - 4 Ad c

I.,1

I-4

Page 68: GNAS Maintenance Control Center (GMCC) Design

-4 -4

0 0

0 o ca

c~ ~4.4 4.4

u30 43E.-43 4

434 U U

4. 0

0 E-4

3.C4

?-4 c:.

0- Cd 0

~0z

0.3 as u 4 04 -4o 0. 00 4)0- -4

430 4) w. 0 -1w 0 a.J- ca 0 " 1... 0 r.

0.04. U m 01 40 0. 0 40413 cc -4 CA 4.14 1.,) m .4 (4

V3f 3j .u) 43 9: .. 4 4 41) Ai3 U,; I-.rI u 0O .- i> W C Z 0 ~-1 C10C

4).44 ) -4 - 4 0 0 0.C -43 .0 4.1.at0 0. .441 pa- 4 4 0 0. 00C

imis 4) "34.3 . 4.043 cc)1w4X0w.cc..4 0&4CL041) m) 9:C u.J 4) 0 43. w4)

440 C: 44. U14J 44 41.4. 3.z4 wAi w00 m13w'1 60 cOU)w 044 "444 0 * l 01

0)4)0 -4 43 44 43 -4&~1 .000 40~ 0 0 40 %4 PC 00.3 U)

43U-4 4.44 W. U)J ... r C)1:1.4 C- J4 O C PC C: m4 >34 -4 -4 430

0 w 3 Ai cc 3.4 U) .. 4 1.4.. .41 4)4J43 -.4 31 A .. 44.z ) 0 3- Q34 -U4 C ~ 4 >% -43)

V 41.444 C *04441 004 0434.) A 010.- 104 4.1Ad 3443-1 W.C "40 1.43.4 0 -3.d w .4 r44) 14

0 -.4 W4 4 0 44.4 04010. 044) 4J0 WC 0 4 4J

1-4 43& - o 4d

E-44W . 5l14c

Z* .0 4A .-4 .-4 4

$43cc 3 0 -4 -4 -4 44-4.

4)fl el .. 4

P.* 4 P4 >4 >4~ -4

4.4 U CA z . .

-C 04 C 0 ~ (' 0

A-47

Page 69: GNAS Maintenance Control Center (GMCC) Design

0

to a C13C.)u Q u (a r

w.s. z 0 0

00s ud - d

44 (a

uu

Cujz 41

r. 4)- r. 91 -4 CE- 4je 0 4) $ " c -

-4)1 - - -41 341w

E- u- l UC A oU A 4 l 1 C Mu cc 41 0-n0 0 L 0 a r u r.06u "4 ul t

Cu w )a 4 ze W - 4 0 (a ~ 0 v 0 >in as~~0.u-- : 1 M . n 0 d Q C uhw0

CL0 W -c 44J -C Cu Cu to 0ua u

4.J4uNl -4 Cu4 390 cc4~ 0) co C.Y Cu.- Lne44. 10 c 24 C0)4 cU)e

wC4 r.J cc >1 C ?AS A -4 -4 a] M ) FA000O.J 4.1. -u 0 A.4) > 10 % u Cu > uU.-4 >

z " Q a.J Q 4u4 s ) usI. u 4)r. ul CuJ O.0c 3a cu 0 "4 44 u .4 coU u~-C Z 8 3 4 l'0M 0

9 ' -4A Cu'- w C a 055 0 Cu VCu4Ai(

> M 41u " 4)W 4 1 4) u Cur.u CL r_0 4) r. r.0 4 >, u~ 4.4 cn 0 0 u m u'En .0-Cw z -0 0M X :1- >4~ AJw. -. ~ ci 41 -~C ) ca r0. V* - to ~ -Cu~ Z . IU ac 40 au 0u c

Z-4

41 -

m cc

(DJ -4 > -

I-.Cu -4 CA.-

Cu < 0 0

45W .. ~ .e~A-48 -

Page 70: GNAS Maintenance Control Center (GMCC) Design

U)

0z

u w z0 u 9 0 - a ti -CtU)7 Uv 041 ) 44 AU)495- U3 U) ;

4) U) 4 CL.4 w. :1 4 Z 4 :34)C 4) 41.J 10 - 41 1 4

4) 4A n3 d U

ME-.

1-4 E- 1-4 1- -4 i-4f

'44 0 0

4) ou 4

>S 4) 0

-4 -4 0 V r. v P bo~ .-

U)i 004. - 4 4 A '4.4 0-4 -4). ww 0~ PC cc ) 0 w1.44.4 .. 4 -4 4 U)

4)J0 IsU)uw 00 4"0 .14 WU) C60c .4) % .4 in Q. 4)w. w 1.0

U)U) 14u -4 ~U 4J A44bo C W )44 cc ia zo1. 41 - ~ 4) .- ~ r. 0.U~ :3 r.

41 -i. -) -40w r 0 .- ' 4) V t bo cU) ul 0 4440 U) .4 -4J " j u 01-4 r.4) c r

w j01 0 P4 0 4.4 w A A 0 *el3 U) r.~)U -4faIn m 414 4 w o a o 0 Cc 4) a

=) U)) 4b 0 m444. 4 >, 41UU) 4.,.to)9~ce. a).4 "044 4 .4 v ~ .4 "4.44) u r C: 1 g- 4404 ,-4U = wco ) ) "q 60.

W. = ) a ) U) o U) 1 U) 4. 41 U 0 . U) to co .40aw( 4 4 -4 4) -..4 0 "4 0 a4) 4 14 4. 4)

-4WCO Q-44 M) 4*4J- = ~ U b r*-4c4.4U" CO. 4 a 4 z )CL

0 ) 04 0C>%.4. u-UU 0>4 bo .a>0 0.4

14 = 4) 4r- "-4 -4)U)4) to 140-aa4 144)-4 0 .40c 4

UW 44 03 w0 0 0 0~ $4 0 c= $ 0 w 0b4. 0 0 w.404m

-4 C

14)

AA-4

Page 71: GNAS Maintenance Control Center (GMCC) Design

z

u ) c )jc

z

41 41A 0' 4. 4.)

C. 4) 0 zO 0). 0i A~14 0 -. 4 U

414. J4 44 .

414 - 4C

44 a

0% 4)

41 ci4 44 D-O DO0

C:. 0) 0 . 09

0 P -0u w o9

41 co 0 '0 9: 4 .14.. 4 V .. I 4.)Cd rZ .1 4W 00.4.1 0 4) .4.4

.4 41 - 0 *a )to $4 - -4 D4

.4 . 4 4J W 4 .4 J 0 40 - 1.4 - .0r).4vCi a ,. 4a). -A 4 04'44 4 -4 0 0 Q P4 0 4CO(

0 .'0 z -4 '41wCU . 03 44 9 0 4 j. "4.0 1:4) .0) r. - 4 Cal Q a . 4 1 41* 0 0 .4 A - 0 0

041 0 I 4J 4).4 L WJ' W 0.c'.o4 0J 4"0&41 . J o 0 .4 4 4 W 0 8 0 -4 u C:4r. 4 04 u 0 4J4J".4) u44 w. w ,wr .- 4r

4) cc0o0 44 Cco w L9 0 4.)*a000 00 Cd0a a i C r t 4 ul w) ) 4 .4 44 4434) -4 ) u -1 4J -)4 C: 4 a V1.4 4iJU44 W o Z 0 . cc 4. 0 -.40 w v

r. 4)).4. )J.4 0 4 44,.) )4 UJJ 0 w 4 4.4.

0 r 10 C w '0 -4 W CO 4 C: m w 0 0 0 1 4

4 -P4 4 U.0 4) .40L4I41 4.4

1.4 0 dC P

144

X 4.)

0c

w. 0 -4

-4 C4.

4) Q

4. 4(44

od 0 ALz z z z

A-5O

Page 72: GNAS Maintenance Control Center (GMCC) Design

44 ) CM ~0 4

04 E0

40 0 0

4) 444)

4)1- 50 '4 )4400 0 )o 4-0 0mvw 0004 41 1.4 - j 0 4" 0

$44 0 1a r , 1 1 cs- 04(A 4 c ) w4 44 Arr-C 1-4) boC )- )L 4 49-41 : 4(

w 4. 0o 0j 0 $ . a 6 0 0 -4 Q t

0-4 cc-4 4 4 0' 4 9 .4 t 4 :

W . C 41 . 4 d

4.. W '0 -1 440 F - 4 a-0 40 W 0 .4 3 w 0 .4 -,4 r 4'.4 1 0 44 J

* . 4) 0 "a .J'0 0 '0 4C 1414 V 1.4. X :1 VU. Wa -41. CL .4 31-.4 -4 3t0 -4 0 I

-4 >. > 400 0'4. 4) >'. w " 4 )-C 0 0 ) $ a0 0 410 w 0 C0 QQ -144C.40w = A a u 'W40 4) - w'440 > 14JJ0 -D- 0. 41 6 ) 1440U 4 1 '40 41 0.4 0 0.u00

o r0.1. ) J444J 4 444 ~ -1j.

>~.4 ~ 0 '~ 4- 0).

1.0 cn. .. 0- .14 3 .

41 A 444 0 m o '4 0

e4 C4" 140.414 ~ 4'0 JJ- 0'0 1.10 0 1.)J.0 0cc

'.4 .141 0'.4.40 00'O J 0. 091Z 0114. 0'.4 14,4 0.4'~0~ .4 44) 4.4.) w

o ) 0' '0 0 0 0l404.4~'0- 410. 4~0 .0 f.~ 4~'4 00 '

In4 4)

v0In c C n n0

< c -C-C <)z z z4)

1.A-51

Page 73: GNAS Maintenance Control Center (GMCC) Design

4)44 C40

U41 0 4.u3 $4 z 0 0

:1 .4 4 r-6 c*a 012& 0 0. "-0 41 cc w 14CL

u~. 0 w0. E-

.43

o E . . 44

'.44

4.4 0 0

410A14.4. 4.1 4.

1- C-41 41 414-

0 ~ 0 * -4 04o 4~4. O 4). 414 p *41

w ~ 'I o 4 rw .i' 000 -4V ca F- c 00 1 .

0 4 r*. 4 .40 43LJ 0 . O > w -4 v 1U, 4.41 444.44. 1 4.1 r '404 4 000

c v. .4.- 000 X 0 a w 41X 1 . 6 ~..4 3'01. 041 41 4)44 4 . >b w 03-iJ

Q 00 - CL0 4J. .4 4 0 4~ 04.4 -.41 4 %0 .94 -4a 4 . a 4w

0 41 4.4 Q 41 60 w.0 coa c c

2 41.3 4 C1.-4. -141 14 044oo 0 -443. >U.. a *a~ 0W000V- 4w m 0 0 0 (a *.031i- bo 4 - 0.. ;N -4J r0-4

OC4 -4U cc$ 0 r A a C 04- C 04 3' .0 .__Iw__.__C A4 0! -aJ-O~. P-34. 0~ O.4 13'0 - >

w~~ ~ ~ ~ ~ ~ 4 cc-4. 4 uM4$ j-

a- '4v c ) 4.4 1 3

2-4

4.1

.141.

0 r.0ca

1- 01-4 Ac

4141

(j41 4

44 4 00 0

-C

A- 52

Page 74: GNAS Maintenance Control Center (GMCC) Design

(A a -

a 0

P4.

E0 -' I-

0.0 0

= 02

Of- cc ' 4

'-44 w4 '3F.u 0 0 4 04

@20g 4 "041 0 4

<' A4.r0 4) "_ -4 r 04)44 o4

41 cc ~ 0 40& 0-4. 0 r-I 0 c 1.44.) m .)

414. CL &0 0- c4 0 &-C-40 *4 U'.4 -4 -4

.0 .4 9 C A A4'41 .0 1In4 '.o V 9: .. 4) 0 0 0

4 .- 4 4) 0 O .- 4 4 co .2u2 :1 4J''. so 4 u 4 .- 40U

*j 4O- a~U , 1@214IJ .0'0 -0 44 1--4 0

0. 0 b . >44 m0041O www, wm.' 4 0-4

10V-4 V C tho -4~ o . m4o 1-. . -40 . 4 cu-c @4 4 4 j 1.4>2 > > 0w4u- > Li -4 - 4.>

0 .0 u $wZ c a244. @214 $@4 J. c .Ic

CL @2'- 4 96 cc 0.m a .ad ,.44 I 0.4M

Z .4

D .0

AiI

410.I-0

-4 z

A-53

Page 75: GNAS Maintenance Control Center (GMCC) Design

APPENDIX B

PHASE II GMCC CONFIGURATION

(AT&T FEDERAL SYSTEMS DOCUMENT)

Page 76: GNAS Maintenance Control Center (GMCC) Design

GMCC Integration Document

FAA Technical Center

April 1991

Prepared by: AT&T Federal Systems

Date: April 1991

Version: Draft 1.0

B-1

Page 77: GNAS Maintenance Control Center (GMCC) Design

Contents Page

1. Introduction

2. System Architecture

2.1 System Overview2.2 System Components

3. Detailed Hardware Configuration

3.1 OATS Workstation3.2 10 MB StarLAN NAU Card3.3 Brouter Configuration3.4 Cabling3.5 Modems

4. Detailed Software Configuration

4.1 Workstation Software4.2 Server Software4.3 Loading Procedures4.4 Parameter Adjustments4.5 PCT Set up4.6 Batch Files4.7 Windows Environment4.8 Memory Management4.9 Machine Names/Addresses

5. Non Standard Configurations

6. Application Procedures

B-2

Page 78: GNAS Maintenance Control Center (GMCC) Design

Appendices

A System Configuration - Direct ConnectB System Configuration - Through BroutersC Workstation config.sys ExampleD Workstation autoexec.bat ExampleE Workstation lanman.ini ExampleF Workstation protocol.ini ExampleG Batch Control FileH Modem configuration

B-3

Page 79: GNAS Maintenance Control Center (GMCC) Design

1. Introduction

This document was produced to detail the procedures carried out in setting up theGeneral Maintenance Control Center (GMCC) system. The document includes hardware andsoftware configuration procedures and modifications, application procedures, systemdiagrams and a complete CLIN listing. The project was carried out over a six weekperiod from March 18th to April 26th 1991, at the FAA Technical Center near AtlanticCity. Assistance during the project was provided by the following individuals:

Richard Van Suetentael (FAA)Dennis Steelman (FAA)Bill Gibbons (Tandem)Tom Miller (Tandem)Phillip Hoang (FAA)Samer Salty (Martin Marietta)Julie Riches (CTA/ACN-250)Mike Jones (CTA/ACN-250)Craig Stewart (CTA/ACN-250)

B-4

Page 80: GNAS Maintenance Control Center (GMCC) Design

2. System Architecture

2.1 System Overview

Two system configurations were set up and tested during the project. The firstconfiguration connected the OATS network directly to the MLAD computer through theNHU (Network Hub Unit). The second configuration included the Brouter hardware whichprovided a bridge between the MLAD and the OATS network. System diagrams for bothconfigurations are provided in appendices A and B.

2.2 System Components

2.2.1 OATS Workstation

80386 25 Mhz processor / 4 MB RAM84 MB SCSI hard disk3.5"/1.44 MB and 5.25"/1.2 MB floppy disk drivesVGA Color Monitor CRT 329D10 MB StarLAN NAU card305 KeyboardMicrosoft Mouse

2.2.2 OATS Server

80386 25 Mhz processor / 8 MB RAM300 MB SCSI hard disk3.5"/1.44 MB and 5.25"/1.2 MB floppy disk drivesVGA Color Monitor CRT 329D10 MB StarLAN NAU card305 KeyboardHi-Cap Internal Tape CartridgeMicrosoft Mouse

2.2.3 MLAD Unit

Tandem 8028620 MB SCSI hard disk5.25"/1.2 MB floppy disk driveMDA Monochrome Monitor10 MB StarLAN NAU card3-COM adapter cardKeyboard

2.2.4 Hub Unit

AT&T StarLAN 10 Network Hub Unit (NHU)

B-5

Page 81: GNAS Maintenance Control Center (GMCC) Design

2.2.5 Brouter

StarWAN 200 BrouterMCI Controller card2 Serial Network Interface Cards2 Ethernet IEEE 802-3 Interface cardsGS2 BFX Version 8.1 (2.5)X.25 SoftwareBridging Software

2.2.6 AUI Adapter

StarLAN 10 Network AUI Adapter

2.2.7 Printer

Accel-500 dot matrix printer

2.2.8 Cables

RJ45 StarLAN Ethernet CablesRS 232 Serial CablesAUI

2.2.9 Modems

Codex 3600

B-6

Page 82: GNAS Maintenance Control Center (GMCC) Design

3. Detailed Hardware Configuration

3.1 OATS Workstation

Main Processor : Intel 80386 25 Mhz Serial Ports: 2Co-Processor : None Parallel Ports: 3Video Display Adapter: Video Graphics Array (VGA)

Available Floppy Disk Drives: A: 3.5"/1.44 MBB: 5.25"/1.2 MB

Available Fixed Disk Drive: 84 MB SCSIPartitioned as:

C: 32 MBD: 32 MBE: 20 MB

Memory:640 K-bytes main memory64 K-bytes display memory156 K-bytes extra memory2,272 K-bytes expanded memory

Included in one of the workstations is a Video Graphics card, which drives a 19"Misubishi HL6915STK color monitor.

3.2 10 MB StarLAN NAU Card

The following settings were used for all NAU cards, (irrespective of Server,

Workstation or MLAD).

IRQ: 2I/O Address: 368RAM Address: DOOO

B-7

Page 83: GNAS Maintenance Control Center (GMCC) Design

3.3 Brouter Configuration

The Brouters were configured to act as a bridge between the Tandem MLAD and theStarLAN 10 network. This was achieved with the following configuration:

Brouter A (The Tandem side)

1. Enter "enable" at the Brouter prompt to enter privileged user mode.2 Enter "memory erase". This makes sure that any previous entries are cleared.3. Enter "configure" at the Brouter prompt to edit the configuration details.4. Enter "bridge I protocol ieee".5. Enter interface ethernet 0".6. Enter "bridge-group 1".7. Enter "interface serial 0".8. Enter "bridge-group 1".9. Enter "^Z" (control Z). This exits configure file.10. Enter "write memory".11. Enter exit.

Brouter A is then configured.

Brouter B (The Starlan 10 side)

1. Enter "enable" at the Brouter prompt to enter privileged user mode.2. Enter "memory erase". This clears any previous entries.3. Enter "configure" at the Brouter prompt to edit the configuration details.4. Enter "bridge 1 protocol ieee".5. Enter interface ethernet 0".6. Enter "bridge-group 1".7. Enter "interface serial 1".8. Enter "bridge-group 1".9. Enter " Z" (control Z). This exits configure file.10. Enter "write memory".11. Enter exit.

Brouter B is then configured.

B-8

Page 84: GNAS Maintenance Control Center (GMCC) Design

3.4 Cabling

Workstation - Hub RJ45 Max Length ?????Brouter - Hub RJ45 Max Length ?????Brouter - AUI adapter 15 pin AUI cableAUI Adapter - Hub RJ45 Max Length ?????

3,4.1 DB-25 Pin Configuration

The cable should be connected with one female end (DTE) and one male end (DCE).Only the following pins were connected:

Pin 2 (Transmitted Data)Pin 3 (Received Data)Pin 4 (Request To Send)Pin 5 (Clear To Send)Pin 6 (Data Set Ready)Pin 7 (Signal Ground)Pin 8 (Data Carrier Detect)Pin 15 (Transmit Signal Element Timing)Pin 17 (Receiver Signal Element Timing)Pin 20 (Data Terminal Ready)Pin 24 (External Transmit Signal Element Timing)Pin 25 (Test Indicator)

3.5 Modems

Codex 3600, synchronous, 19.2 K Bits/sec. For modem configuration see appendix H.

B-9

Page 85: GNAS Maintenance Control Center (GMCC) Design

4. Detailed Software Configuration

4.1 Workstation Software

AT&T StarGROUP Client version 3.3 (8 user)AT&T MS-DOS 3.30a Version 1.01Microsoft Windows Version 3.06530 Terminal Emulation

4.2 Server Software

AT&T StarGROUP Server version 3.3 (8 user)Unix System V/386 Release 3.2.2

4.3 Loading Procedures

It is assumed that all of the OATS software will have been pre-loaded before delivery,including the installation of the server and client StarLAN software. The followingis the sequence of tasks that should be carried out to connect and configure the GMCCsystem.

- Connect the components of the GNAS section of the system.

- Connect and configure the Brouters and AUI adapters.

- Install the StarLAN NAU card into the MLAD computer, setting the IRQ, I/OAddress and RAM address as outlined.

- Connect the MLAD to the Hub unit.

- Install the StarLAN client software on the MLAD. The procedure for this can befound in the StarGROUP document "StarGROUP Software - Installing LAN Manager". Thefollowing options should be selected during the installation:

Choose the install rather than the upgrade.Select Basic DOS client form the "Select a Configuration" menu.All software should be loaded on drive C:Accept the default directory location.Enter "WKSIO" as the computer name.Enter the primary server name as specified, including the .serve extension.Do not enable the message receiver.Do not load the network driver in expanded memory.Do not load the DOS redirector in high memory.Enter "Yes" to "Prompt to start network software on boot".Enter the NAU interface board type as AT&T Starlan 10 Network PC NAU.Enter the strap setting as they have been set up on the NAU board. Theyshould be:

IRQ - 2I/O Address - 368RAM Address - DOOOOTest the configuration.

B-10

Page 86: GNAS Maintenance Control Center (GMCC) Design

Once installed, and with the server running and Brouters in place, reboot the MLAD.The MLAD will try to make a connection to the server. If the connection issuccessful, the message "SOFTWARE LOADING COMPLETED" should appear. The network canthen be further tested by linking to the server disk.

4.4 Parameter Adjustments

These amendments need to be made to the following files:

4.4.1 OATS Workstation

Config.sys

Add the following lines:

device-c:\tandem\kernel.sysdevice-c:\tandem\rmpcdrvr.sysdevice-c:\tandem\lan6530.sys /S4 /B4096

These files should be supplied by Tandem. The file sizes and creation dates areshown for reference.

LAN6530 SYS 15514 12-06-90 ll:10aRMPCDRVR SYS 10030 12-06-90 ll:llaKERNEL SYS 2819 12-06-90 ll:07a

Autoexec.bat

Add the following lines:

D : \lanman. dos\netprog\ql N: \\servname. serve\uD : \lanman. dos\netprog\ql LPTI: \\servname. serve\accell02

Replace 'servname' with the name of your server.

Protocol.ini

Amend the following parameter:

nsess - 7

This will allow the workstation to open three 6530 sessions and access the TandemDos partition.

4.4.2 MLAD

Config.sys

Add the following lines:

device-c:\tandem\kernel.sys

These files should be supplied by Tandem. The file sizes and creation dates are

shown for reference.

B-11

Page 87: GNAS Maintenance Control Center (GMCC) Design

KERNEL SYS 2819 12-06-90 11:07a

Protocol.ini

Amend the following parameters:

nsess - 32

ncmds - 64

B- 12

Page 88: GNAS Maintenance Control Center (GMCC) Design

4.5 PCT Setup

The 6530 terminal emulation program is called PCT.EXE, and should be installed on eachworkstation. The Oks 1989 version should be used. The configuration program used toset up the emulation parameters is PCTC.EXE. To allow Windows 3.0 to open threecopies of the same program with different parameter files, three directories had tobe created under the TANDEM directory on drive C: These should be called TACL, MMS1and MMS2. The PCT.EXE file was copied to each of these directories and renamedPCTTACL.EXE, PCTMMS1.EXE and PCTMMS2.EXE, respectively. The configuration programshould then be run in each of these directories to create the PCT.INI files. Thefollowing fields should be amended in the configurations:

On page 3 of 9:

HOST NAME '\acta'WINDOW NAME '\acta.$lanl.#bdl2tcl'

NB. The fields in quotes are examples only. Consult with the TANDEM engineer tofind out the local names that should be used. The window names should be differentfor each PCT session.

On page 5 of 9:

AUXI DEVICE 'LPTI'AUX2 DEVICE 'AUX2TACL'DEVICE NAME 'LANDRVR'

The AUX1_DEVICE field should be set to the shared printer (if this is not set up ora non-shared printer is entered, a 'DOS ERROR: BAD STRUCTURE LENGTH' error will occuron starting the second and subsequent windows on the workstation). The AUX2_DEVICEcan be set to a shared printer or to a file name. If set to a file name, this shouldbe different in each PCT.INI set up. The DEVICE NAME must be set to LANDRVR.

The setup can be tested outside of Windows by typing in the PCT program name in thedirectory containing the PCT.INI file. If the network is connected correctly andfunctioning, it will be possible to connect to the TANDEM machine. To end theTANDEM session, type CTRL-END.

4.6 Batch files

A batch file has to be included in each of the TANDEM directories to stop multiplecopies of the same program running. An example of the control batch file is shownin appendix G. This requires that the directory C:\LOCKS exists. The three batchfiles should be called C:\TANDEM\TACL\BATTACL.BAT, C:\TANDEM\MMSI\BAT_MMSl.BAT andC: \TANDEM\MMS2\BAT_MMS2.BAT.

4.7 Windows Environment

4.7.1 Program Groups

A program group should be created with the description "Tandem Applications" withinthe Program Manager.

B-13

Page 89: GNAS Maintenance Control Center (GMCC) Design

4.7.2 Program Items

Three program items need to be created within the program group "Tandem Applications",one for each of the programs in the TANDEM sub directories created (ie. TACL, MMS1and MMS2). The descriptions and command lines should be:"Tandem TACL Window" - "C:\TANDEM\TACL\BATTACL.BAT""Tandem MMSl Window 1" - "C:\TANDEM\MMSI\BAT MMS1.BAT""Tandem MMS2 Window 2" - "C:\TANDEM\MMS2\BATMMS2.BAT"

4.7.3 PIF Files

PIF files need to be created to control the running of programs inside Windows,including the batch files. These PIF files are created and modified using the PIFeditor found within the Windows environment. A total of six PIF files will need tobe created. Example are shown for the TACL batch file PIF and the TACL PCT PIF:

TACL batch file PIF: BATTACL.PIF

Program Filename: C:\TANDEM\TACL\BATTACL.BATWindow Title: TACL WindowStart Up Directory: C:\TANDEM\TACLMemory Requirements: KB Required 128 KB Desired 640Display Usage: WindowedExecution: BackgroundClose Window on Exit: YesBackground Priority: 25Foreground Priority: 50EMS Memory: KB Required 0 KB Desired 1024XMS Memory: KB Required 0 KB Desired 1024Uses High Memory Area: YesVideo Memory: TextMonitor Ports: High GraphicsEmulate Text Mode: YesAllow Fast Paste: Yes

TACL PCT PIF: PCTTACL.PIF

Program Filename: C:\TANDEM\TACL\PCTTACL.EXE

All other parameters should be the same as above. For the MMSI and MMS2 PIF set up,amend the First three fields as appropriate. If the network and TANDEM applicationsare connected, it should now be possible to run the 6530 emulation from within theWindows environment.

4.8 Memory Management

This section is still to be completed.

4.9 Machine Names/Addresses

The following workstation names were used:

GMCC21, GMCC22, GMCC2G, GMCC23, WKSIO

B-14

Page 90: GNAS Maintenance Control Center (GMCC) Design

4.10 Printer Configuration

The printer used was the Accel-500. StarLAN 3.3 contains a printer driver for thisprinter. The printer should be set up from within Control Panel. The AMT ACCEL-500on LPTl: should be selected and made active. The Network option should then beselected. Select the device LPTl: and type in the name of the shared printer nameon the server in the PATH field eg. \\04800368.serve\accellO2, and select connect.This will then redirect any output sent the port LPTl: to the server, which shouldthen ne printed out on the printer attached to the server.

B-15

Page 91: GNAS Maintenance Control Center (GMCC) Design

5. Non Standard Configurations

All components and configurations should be agreed before document release.

6. Aplication procedures

6.1 System Start Up

The system should be brought up in the following order:

- Make sure that The Tandem machine is fully operational.

- Start the OATS server and switch on the printer. The machine will automaticallyboot itself intu UNIX when powered up. This will take t a few minutes. When the'Login:' prompt appears, proceed to the next step.

- Start the MLAD computer. The machine will automatically load the network softwareand start the MLAD software.

- Start the windows and applications on the Tandem. The MLAD will display all openwindows and sessions.

- Start the OATS workstations. These will load the network software and startMicrosoft Windows.

The system should now be ready for use.

6.2 Tandem Applications

The Tandem applications (MMS and TACL) are available through Microsoft Windows onthe OATS workstations. They can be accessed through the 'Tandem Applications' Iconwithin the 'Program Manager". By double-clicking on this Icon , the contents willbe displayed. There are two MMS windows available and one TACL windcw. To run oneof the options, point to it with the mouse and double-click on the option. Thiswill open a window into the selected application. To close these applications,press Ctrl-End. If the same option is selected before the window is closed amessage will appear in a window saying the application is already running. It isnot possible to exit Windows while any of the Tandem applications are running.

B-16

Page 92: GNAS Maintenance Control Center (GMCC) Design

Appendices

Appendix A - System Configuration - Direct Connect

1 15 1 :3 M ISt II Tandem 16 . C: L ILAN II MMS 10 1 :0: A INAU II 10 1 :M : D I I

I I I

I R145

I HUB I

• R.145 : 1

I .- R 45 *- : :I +--RJ45---+ H

I I I +- J45I I I I RJ45 I

+ +- -4 + -+ +-#

I StarLAN I I Stad.AN I I StarLAN I I StarLAN I I StarLAN I

I I I I I I I I II

I OATS I I OATS I I OATS I I OATS I I OATS I-I Acceil-500 Primer II W/S I I W/S I I W/S I I W/S I I Server I --4.I I I I I I I I II

B- 17

Page 93: GNAS Maintenance Control Center (GMCC) Design

ARoendix B - System Configuration - Through Brouters

1 15 1 :31 M IStw II Tandem 16 - !C: L ILAN II MMS 101 O: A INAU I1 101 :M : D I I

I PJ45

I HUB I

I R.14

I AU! Adapur I

I AU! AdapterCable

I Bmowr I

I DB-25 serial

I Codex 3600 1

I TelepboneI Nenwotk

I Codex 3600 I

I DB-25 serial

I Brour I

I AUX Adqer Cable

I AU! Adape iI I

I R.J45

I HUB I

RJ45--RI- R45-R. 5- :

II I ---- .3---RJ4---

I I IR 45

I Sud.AN I I StaL,N I I SILAN I I StULAN I I Smd.AN I

II I I I I I I II

I OATS I I OATS I I OATS I I OATS I I OATS I- Acc=4-500 Priner ISW/S I I W/S I I W I I W/S I I Screr I4

I I I I I I I I I

B-18

Page 94: GNAS Maintenance Control Center (GMCC) Design

ADgendix C - Workstation Config.sys example

device-c:\tandem\kernel.sysdevice-c:\tandem\rmpcdrvr.sysdevice-c:\tandem\lan6530.sys /S4 /B4096device-c:\dev\sstbio.sys /wedevice-c:\dev\sstdrive.sysdevice-c:\dev\fixmem.sysdevice-c:\dev\386max.sys pro-c:\dev\max.prodevice-d:\lanman.dos\drivers\protman.dos /i:d: \lanman.dos\drivers\starlOdevice-d:\lanman.dos\drivers\attload.dos /ndevice-d:\lanman.dos\drivers.\attiso\attiso.dosdevice-c:\dev\3861oad.sys prgreg-1 prog-d:\lanman.dos\drivers\attcsma\attcsma.dosshell-C:\command.com /e:384 /pstacks-O,0 # WARNING: MODIFICATION TO ANY PARAMETERS, THEIR orlastdrive-N # LOADING ORDER MAY RESULT IN UNWANTEDbuffers-20 # INCLUDING BOOT TIME ERRORS, SYSTEM HANGS and.files-40 # OATS BOOT CONFIG @(#)CPP File config.cpp 2.3@(#) - 7/18/90 VJC

APendix D - Workstation Autoexec.bat example

@echo offrem ##########################################################rem # RESTRICTED RIGHTS NOTICErem #rem # Use, reproduction, or disclosure of software is subject torem # restrictions set forth in Contract No. DTFAO1-90-D-00009rem # with American Telephone and Telegraph Company.rem #rem # Unpublished--rights reserved under the Copyright Lawsrem # of the United Statesrem ############################################################rem # For support, please do not remove the following block of lines.rem # AUTOEXEC.BAT: ID: @(#) CPP File autoexec.cpp 2.4 @(#)rem # LD: 2/24/91 16:16:02rem # LG: 2/24/91 16:16:59rem # BUILD: Thu Mar 21 13:27:54 EST 1991rem # DOSS: 124rem # WKST: danrem # HASSLE: 3.0rem # Thank you from your AT&T OATS Team.rem ##########################################################set attlanroot-D:\lanman.dosset path-%attlanroot%\netprog;attstartC:\utl\3861oad prgreg-2 envsave prog-C:\DOS\share.exeC:\utl\3861oad prgreg-2 envreg-3 flexframe prog-C:\utl\mouse.comC:\utl\3861oad prgreg-4 envsave prog-D:\lanman.dos\netprog\prtsc.exerem #rem # Standard Environmentrem #set comspec-C:\command.comprompt-$p$g

B-19

Page 95: GNAS Maintenance Control Center (GMCC) Design

set helpdirpath-C:\DOS\helpdirset path-C:\DOS;C:\;C:\utlrem #rem # Include MS-Windows in the Pathrem #set path-C:\win;%path%set temp-C:\tmprem #rem # Include Micrz~oft Excel in the pathrem #set path-C:\win\excel;%path%rem #rem # Include Microsoft Word for Windows in the pathrem #set path-C:\win\winword;%path%rem #rem # Place your own PATH entries in here with statements likerem # set path-%path%;YOUR-PATH-ADDITIONrem # Remember, the length of the PATH is limited. Refer to yourrem # MS-DOS documentation for more information.rem #rem #rem # You have installed LAN Manager Client software or Remoterem # PC Client software.rem # In order to access the LAN file server, a Quick Link to LAN Serverrem # must be made.rem #rem # Replace the Lan SeRvE place holderrem # with the name of the server that acts as your File Server.rem #D:\lanman.dos\netprog\ql N: \\04800368.serve\uD:\lanman.dos\netprog\ql LPTl: \\04800368.serve\accel1O2rem #rem # Put the Network Drive at the Endrem #set path-%path%;N:rem #rem #rem # Packrat (Networked) Link-Up to Serverrem # In order to use networked Packrat, a Quick Linkrem # to your Packrat server must be made. Replace therem # PaCkRaTSeRvE placeholder with the name of yourrem # Packrat server. Refer to the Packrat documentationrem # for more information and ask your local networkrem # administrator for help.rem #set path-%path%;K:\D:\lanman.dos\netprog\ql K: \\04800368.serve\packratrem #rem # Standard Environmentrem #set path-%path%;rem #rem # Clear old lock files

B-20

Page 96: GNAS Maintenance Control Center (GMCC) Design

rem #C:cd C:\locksfc- %%X in (\locks\*.*) d . del %%Xcd C:\clsecho.echo.echo RESTRICTED RIGHTS NOTICEecho.echo Use, reproduction, or disclosure of software is subject toecho restrictions set forth in Contract No. DTFAO1-90-D-00009echo with American Telephone and Telegraph Company.echo.echo Unpublished--rights reserved under the Copyright Lawsecho of the United Statesecho.pauserem #rem # Automagically jump into MS-Windowsrem #win

B-21

Page 97: GNAS Maintenance Control Center (GMCC) Design

ARDendix E - Workstation lanman~ini exgMtle

;AT&T StarGROUP(TM) NETWORK CONFIGURATION FILE;This file is used by the ENHANCED CLIENT

;Release 3.3 1989

;NOTE: Comments begin with a ';' and MUST begin in the first column.

[networks]netservices - minses, vertbl

(workstation]wrkservices -

charcount - 16chartime - 250charwait - 128computer name - gmcc22himem - yeskeepapis - yeslangroup - langrouplanroot - D:\lanman.doslogonserver -

mailslots - yesnumcharbuf - 2nummailslots - 2numresources - 8numservers - 10numviewbuffers - 2numviewedservers - 50numworkbuf - 3optimizations - 3prlbuffsize -256pr2buffsize - 128pr3buffsize - 128singlercvbuf - 0sizcharbuf - 128sizworkbuf - 2048

(netshell]username - GUEST

BaIHiIGrIEnIDiIAlIDBIPBIBDILBISBIElIM1BIMeIMsIMhlmhI ihIDAIShIcolors -070170702030031430030030713710710712030030300431401670431002

colors[att]ATTRIBUTES-0,15,7,0,0,15,112,0,0,112,112

attutils - setbit, nps, netmsg17'tpref - nconfigname - ENHANCEDlogonpref - yesmaxmsgsz - 128redirver - 3.3primaryserver - servname.servepublic - U

B-22

Page 98: GNAS Maintenance Control Center (GMCC) Design

release -R3.3

(attservices]netmsg - services\loadmsg.exenetstart - \netstart.batnps - netprog\nps.exeprtsc - netprog\prtsc.exesetbit - netprog\setblt.exeqi - netprog\ql.com

[services]Iminses - netprog\loadmin.exenetbind - drivers\netbind.exevertbl - netprog\loadtbl.exeworkstation - netprog\loadrdr.exe

ADDendix F - Workstation Drotocol.ini exaMple

[protocol manager]drivername - PROTMAN$

(attiso]drivername - ATTISO$bindings - attcsma

nsess - 7ncmds -12

useem - y[attcsma]

drivernaie - attcsma$board-type - Iirq - 2ioaddr - 0x368darani - OxDOOO

B-23

Page 99: GNAS Maintenance Control Center (GMCC) Design

ADDendix G - Batch control file

@echo offrem ############################################################rem # RESTRICTED RIGHTS NOTICErem #rem # Use, reproduction, or disclosure of software is subject torem # restrictions set forth in Contract No. DTFAO-90-D-00009rem # with American Telephone and Telegraph Company.rem #rem # Unpublished--rights reserved under the Copyright Lawsrem # of the United States.rem #rem ############################################################

rem # PCT MMS1 Window Batch File April 30 1991rem ##########################################################

rem CHECK IF LOCK ALREADY EXISTSIF exist C:\LOCKS\PCTTACL GOTO :LOCKED

rem CREATE LOCKECHO PCT MMS1 > C:\LOCKS\PCTMMS1

rem RUN PROGRAMC:CD \TANDEM\MMS1PCT MMSl.PIFERASE C:\LOCKS\PCTMMSlGOTO :END: LOCKED

rem ALREADY LOCKED - PUT OUT MESSAGE AND RETURN: LOCKEDECHO IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIECHO

ECHO PCT MMS1 Window is already running.

ECHO EIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIID:\NU\BE ASK "" TIMEOUT-2GOTO :END:END

B-24

Page 100: GNAS Maintenance Control Center (GMCC) Design

ApDendix H - Modem Config.uration

The following configuration parameters were set on the modems. One modem wasdefined as the master and the other as a slave. Any differences in theconfiguration have been noted.

a) DEVICEMode 3600Max Rte 19.2Port 1

b) ANALOG1) LS ANG

Op Mode TURBO PPRate 19.2Tx Lvl -15DBMCD/THR -26/-31LS STP 0000000

2) SW ANGSW CNFG UNIQUEOp Mode TURBO PPRate 19.2TELCO PERMISIVCD/THR -43/-48SW STP 0000000

3) DTE+MUX MOD AV33 MUX LOC PROGTIMING INTERNAL (MASTER) LOOPBACK (SLAVE)SPD CTL NORMALDTE STP 0000

c) PORTS1) Port I

DATA/CL SYNC INTP1 STP1 00000000P1 STP2 00000010

d) NWK CTLADDRESS 01 (MASTFR.) 02 (SLAVE)NC RTE 75BPSDCE RTE 75BPSNC STPl 00000000

e) RESTORL1) DIAL+

MODE ANSWERDL TYPE AUTODTR REQ NO

B-25

Page 101: GNAS Maintenance Control Center (GMCC) Design

SECURE DISABLE1STCALL REM TXQK CONN ENABLEPAUSE D 4 SECABT FRQ 2100HZ

2) INIT+AUTO RST DISABLELL DCD 15 SECLL UI ENABLEDTR RST DISABLESL STBY DISABLE

3) TERM+AUTOTRM ENABLERST DCD 15 SECRST UI ENABLEHC LOSS SHORTTRM TNN DISABLE

4) PHONE#REM TX1 9REM TX2 4

REM RX3 ?REM TX4 ?REM TX5 ?

ii) Remote

a) CONNECTREM ADD 00SEND

b) ASSIGNREM ADD 00S/N 0SLOT NO 0SEND

c) SEARCHS/N 0SLOT NO 0SEND

d) MISCOVERIDE ENABLEPROTECT DISABLETIMEOUT ENABLELOGOUT

e) MESSAGEADDRESS 00NUMBER 00SEND

B-26

Page 102: GNAS Maintenance Control Center (GMCC) Design

Documentation for testingof MULTILAN/STARLAN

conducted at the F.A.A.Technical Center

During the weeks starting on March 18,1991 and ending onApril 17,1991 , testing was conducted at the Technical Center todetermine the viability of utilizing the A.T.& T. OfficeAutomation Technology Systems (OATS) equipment to access TANDEMbased applications via the MULTILAN NETBIOS gateway product.

The purpose of this testing was to determine if this'off-the-shelf' hardware/software could be utilized to providethe required connectivity for the MCC GNAS project. The intentof this document is to provide sufficient detail of the TANDEMhardware/software configuration to enable the reader to replicatethe tested configuration.

This document will only briefly describe the STARTLANcomponent of the hardware/software LAN environment. The STARTLANLAN environment will be described in a separate document preparedby the A.T.&T. sub-contractor, DATRONICS.

This document assumes that the user is familiar with theTANDEM host application, PATHWAY, PATHCOM, SCF, and otherutilities. If further information is required in these areas,please reference the appropriate application manual.

B-27

Page 103: GNAS Maintenance Control Center (GMCC) Design

HARDWARB

Overviev

During the first three weeks of our testing, we weregiven only one A.T.& T. STARTLAN 10 PC LAN adapter forthe two MLADS. Although other PCs, with STARTLAN 10adapters installed were available, we were not permitted touse them. This severely limited the scope of our testduring that period.

Limited to one STARTLAN 10 PC adapter card, we wereable to test connectivity to the TANDEM in only the singleMLAD configuration. Using the single MLAD, we testedconnectivity in two configurations:

1. Configuration #1 (pg. 3) consisted of a local LAN setupwith the MLAD gateway attached directly to the HUB of theSTARLAN.

2. Configuration #2 (pg. 4) included two A.T.&T.communication routers, called BROUTERs. The two BROUTERs'-ere connected via modems to an analog circuit configured tosimulate a leased circiut in a Wide Area Network (WAN). TheBROUTERS were employed to provide a LAN communication bridgefrom the LAN (remote) to the MLAD gateway (local).

B-28

Page 104: GNAS Maintenance Control Center (GMCC) Design

Configuration #1 - Direct Connect (local LAN)

5 3 M STAR-Tandem 1 6 C 5 L LAN

MIPS 0 o o A INAUI I0 i I 43 D II _ _ _ _ I I I I I__ _ _

I_ _1 -- 1 _ I - _ _ _ _ _

STRIN STARLAN STARAN rSTARAN STARLAN

OATS 'OATS OATS OATS OATS

WS W/S I/ I/ ServerB-29B BI29

Page 105: GNAS Maintenance Control Center (GMCC) Design

Confiquration #2 - Through BROUTERS

1*5 ___ 3 M TSTAR- T-Tandem 6 ___ C L LAN 'H

MPS 0 o' A NAU -- u'0' 'M D 'B'

_ _ _I I--I I _ _ _ I _ _ I I I

Brouter

AUI dapter

I -

Modem

I dapter

ISTARLANI STARLANI STARLANI STARLAN

I II I I

OATS" OATS OATS OATS OATSW/S W/S I/SW/S 1 Server

I II I

B- 30

Page 106: GNAS Maintenance Control Center (GMCC) Design

ovezviev (cont.)

Later, we were supplied with five additionalworkstations. We extracted the STARLAN 10 adapter from oneof the five workstations and placed the card into the secondMLAD. This limited our second GNAS configuration to three(3) CLIENTs and one (1) DISK SERVER.

The anticipated GNAS LAN configuration is expected toconsist of four (4) CLIENT workstations and one (1) DISCSERVER. Each Air Route Traffic Control Center (ARTCC) wouldsupport a maximum of four remotely located GNAS MCC LANsetups. Additionally, the possibility exists for a localLAN setup, know as the AMCC, to require access to theTANDEM.

We recomended that the FAA perform testing with aconfiguration containing the full range of devices expectedto be supported by the maximum configuration. Due to lackof available equipment, the FAA decided to process with thetesting using the available equipment.

TANDEM Connectivity Components

The 5600 Ethernet controller, the controller cablewhich runs from the controller to the EMI patch panel, thetranceiver cable which runs from the EMI patch panel to theTRANSCEIVER, the transceiver, and the ETHERNET coaxial cableto the 3COM 503 cards inside the two MLADs had already beeninstalled by the TANDEM CE proir to our arrival.

In both MLADs, the 3COM 503 card was jumperedaccording to the factory settings. The factory setting forthe I/O base address is 300h. The factory setting for thememory base address is 'disable'. All software options wereallowed to assume the default settings.

All STARLAN 10 adapter cards were installed with an I/Obase address of 368h. The memory base address was set toDOOO.

The 3COM adapter assumed IRQ 4 and the STARTLAN 10adapter was set to assume IRQ 2.

B-31

Page 107: GNAS Maintenance Control Center (GMCC) Design

HARDWARE

LIMITATIONS

We were eventually supplied with the following hardwarecomponents:

1. Nine A.T.&T. 386 workstations. Two (2) were designatedas the LAN DISK SERVERs, and the other seven (7) were set upas LAN CLIENTS. We were informed that each GNAS MCC wouldcontain one SERVER and four CLIENTs, so we would only beable to configure one complete GNAS MCC site.

2. Two A.T.&T. BROUTERs.

3. Two STARLAN HUBs.

4. Two sets of cables for connecting the BROUTERs to theHUBs.

5. One STARLAN 10 LAN adapter card for each of the nineworkstations.

6. Two MLADs each eqiuped with a 3COM 503 adapter forconnection to the TANDEM based 5600 LAN controller.

7. Two STARTLAN 10 LAN adapter card for the MLADS. EachMLAD should be able to support two NETBIOS LAN adaptercards. In the case of the STARTLAN cards, this would limiteach gateway (MLAD) to supporting 32 names and 64 sessions.We tested with only one STARLAN 10 adapter per MLAD,limiting each MLAD to 16 names and 32 sessions.

Since we were testing with a limited subset of thedevices expected in the maximum configuration, the FAA wasreluctant to pass the system without specifying that theDesign Qualification Test and Evaluation (DQT&E) washampered by lack of equipment.

However, given the results of our testing, we do notanticipate problems as more GNAS MCC sites are added. Thecommunications circuit bandwidth (@19,200bps) shouldthrottle the activity for each GNAS MCC LAN added.

B-32

Page 108: GNAS Maintenance Control Center (GMCC) Design

SOFTWARE

Software Versions

MLAD T9377C20 16FEB90

PC6530 G21

MultiLan Host Software C20

MSDOS Version 3.30a

MS Dos LAN Manager Protocol Manager V1.1

MS Dos LAN Manager Netbind V1.1

AT&T StarGROUP (TM) 82586 CSMA Driver Version 3.30a

AT&T StarGROUP (TM) OSI Netbios Driver Version 3.30a

SMB Compatible : Yes

Netbios Names : 16 per Adapter

Netbios Sessions : 32 per Adapter

Adapter per MLAD : 1

Host Adapter Type: 3Com 503 or 501

B-33

Page 109: GNAS Maintenance Control Center (GMCC) Design

CONFIGURATION for the MLAD Gateway

After the STARTLAN software was loaded on the MLAD, theconfig.sys and autoexec.bat were set as follows:

C: CONFIG.SYS

files=2 0buffers=20DEVICE-c: \tandem\KERNEL. SYSLASTDRIVE=NSHELL=-C:\COMMUAND.COk! /e:384 /pdevice-c: \lannlan.dos\Qrivers\protman.dos/i: c: \l~nman. dos

\drivers\starlOdevice-c: \lanman. dos\drivers\attload. dos /Ydevice=c: \lanman. dos\drivers\attcsma\attcsma. dosdevice-c: \lanman. dos\drivers\attiso\attiso. dos

C: AUTOEXEC.BAT

@echo offbreak-onpath-c: \;c: \dos;c: \mlad;c: \utils;prompt $p$gverpath=%attlanroot%\netprog; %path%:REM ***** AT&T StarGROUP(TM) Software - Do Not Modify **

SET ATTLANROOT-c: \lanman. dosPATH-%ATTLANROOT%\netprog; %PATH% ;\\04800368.SERVE\UATTSTARTcd \cd \mladpause

miads, -al -g#PITaO -S32 -C64 For the Pittsburg GNAS.or

:miads -al -g#ACYaO -S32 -C64 For the Atlantic City GNAS.

B-34

Page 110: GNAS Maintenance Control Center (GMCC) Design

NLAD Configuration Notes

The gateway name in the MLADS command must match thename specified in the TANDEM SCF 'ADD GATEWAY' commanddiscussed later (i.e. -g#PITaO or -g#ACYaO in our exampl3s).

The -S32 and the -C64 must match the 'nsess' and the'ncmds' entries in the \LANMAN.DOS\DRIVERS\STAR10\PROTOCOL.INI file installed on the MLAD as part of the AT&TSTARTLAN configuration. Note that the 'nsess' entry (numberof sessions) in the PROTOCOL.INI file will effect the numberof sessions which can be established via the MLAD. Each PCuses some of these sessions for LAN based functions.

At one point, we were receiving 'CSS error 4' from theemulator (PCT) while attempting to start a third window viathe WINDOW 3.0 manager. Increasing the number of sessionson the workstation adapter by incrementing 'nsess' solvedthe problem.

The C:\TANDEM subdirectory contains the G21 release ofthe EM6530 product. The diskette containing this release ofEM6530 should be delivered with the MULTILAN product.

Be sure to use the KERNEL.SYS contained with the G21release (not the old KERNEL.SYS contained on the MULTILAdiskette). The older release of KERNEL.SYS included on theMULTILAN diskette is not compatible with the G21LAN6530.SYS. This is important when installing the driverson the LAN workstation.

The MLADS.EXE was taken from the SUT delivered with the5600 controller. The version we used contained a version ofT9377C2OA16feb9OA16feb90. This version number will alsoappear as the banner on the MLAD once started.

B-35

Page 111: GNAS Maintenance Control Center (GMCC) Design

LAN Based Workstations

After the installation of the AT&T STARLAN networksoftware on the workstation, the CONFIG.SYS contained thefollowing:

device-c:\tandem\kernel.sys # TANDEM G21 kerneldriverdevice-c:\tandem\rmpcdrvr.sys # TANDEM G21 resourcemanager defaultsdevice-c:\tandem\1an6530.sys /S4 /B4096 # TANDEM G21 lan driver

4 sessionsdevice-c: \dev\sstbio. sys /wedevice-c: \dev\sstdrive. sysdevice-c: \dev\fixmem. sysdevice-c: \dev\386max. sys pro-c: \dev\max. prodevice-d: \lanman. dos\drivers\protman. dos/ i :d: \lanman. dos\drivers\starlOdevice-d: \lanman. dos\drivers\attload. dos /ndevice-d: \lanman. dos\drivers. \attiso\attiso. dosdevice-c: \dev\3B61oad.sys prgreg-lprog-d: \laznan. dos\drivers\attcsma\attcsma .dosshell=C:\command.com /e:384 /pstacks=O,0 # WARNING: MODIFICATION To ANY PARAMETERS, THEIRVALUES, orlastdrive-N # LOADING ORDER MAY RESULT IN UNWANTED

SYSTEM BEHAVIOR,buffers-20 # INCLUDING BOOT TIME ERRORS, SYSTEM HANGS

and CRASHES.files-40 # OATS BOOT CONFIG @(#)CPP File config-cpp 2.3@(#)-

7/18/90

The first three entries represent the TANDEM driversrequired for MULTILAN connectivity.

B-36

Page 112: GNAS Maintenance Control Center (GMCC) Design

TANDZM device drivers

The KERNEL.SYS device driver creates a multitaskingenvironment for the PC based software. KERNEL.SYS must beloaded before RMPCDRVR.SYS and LAN653O.SYS.

The RMPCCOM.SYS device driver establishes a sessionbetween the PC and the TANDEM based MultiLan ResourceManager (MLRM) via the session associated with the ZHME1application name.

The session is used by RMPCCOM for logging onto thesystem. LAN6530 also uses this session to establish dynamicand static windows (note: addition of each window results inaddition of an application name to the MLAD resident LANadapter card.

The session is established when the named resource isutilized i.e.- an application is run against the addedwindow).

The LAN6530.SYS device driver establishes multipleterminal emulation (PCT) sessions (depending on the /Sxparameter) via dynamic or static windows.

B-37

Page 113: GNAS Maintenance Control Center (GMCC) Design

SOYTWARI ON the TINDEN (host)

8SSON

The MACRO:

MLMUX^MACRO MLAI4 TYPE 56,SUBTYPE 0,RSIZE 32000,PROGRAM C9376P00,MAXEQUESTSIZE 32000,LINEBUFFERSIZE 32,BURSTSIZE 16,INTERRUPT IOPA INTERRUPT A HANDLER .4;

In the CONTROLLER section:

LAMA 5600 2,3 %350; !MULTILANCONTROLLER

In the PERIPHERAL section:

SLAM1 LANA. 0,LANA. 1ML.MUXAMACRO,NAME #LANOOO1; !HULTILANLINE

B-38

Page 114: GNAS Maintenance Control Center (GMCC) Design

8O1TWBW ON the TINDEX (host)

STARTUP

You should have a Subsystem Control Process (SCP)running to support your SCF interface. If one has not beencreated, you can start one as follows :

stop SZNETSCP/NAME $ZNET,PRI 150,NOWAIT,CPU l/2;autostop -1

Start the TLAM Manager. This NonStop process pairprovides the internal programmatic interface forconfiguration and network management of TANDEM LAN accesssoftware communications subsystems. There is only one MLMANprocess pair per TANDEM system and it's PPD name shouldalways be SZLMG.

stop SZLMG

MLMAN/NAME $ZLMG,PRI 198, CPU 3,NOWAIT/2

Start a Multilan Resource Manager (MLRM).

stop SZMRMMLRM/NAME $ZMRM,PRI 197,CPU

Use Subsystem Control Facility (SCF) to add andinitiate the subsystem objects.

SCF/IN SSYSTEM.MULTILAN.DOMAIN/

Where the file DOMAIN would contain commands toaccomplish the following for each GNAS. For exact filecontents see:

\ACTA.$system.Multilan.domain which is secured fornetwork access ).

allow all errors ! allow for error conditions

start line $laml ! insure line is started

B-39

Page 115: GNAS Maintenance Control Center (GMCC) Design

STARTUP (continued)

During our testing we assumed that each GNAS would beconsidered one domain, so we named the DOMAIN after thePittsburg GNAS (PIT).

add domain $laml.#PIT,default

We were only supplied one LAN adapter card, so we named

the gateway after adapter zero in that gateway.

add gateway $laml.#PITAO,type mlad,domain #PIT

We assumed the wokstations would be named accordingthe GNAS in which they were contained.

add WS $laml.#PITl,domain #PIT

Then we added three window for each workstation. Onefor TACL, one for MMS, and one for MMS.

add window $laml.#PITIMCs,WSname #PIT1delay 2add window $laml.#PITIMMs,WSname #PIT1delay 2add window $laml.#PITiTCl,WSname #PIT1delay 2

Note : Once we added the BROUTER we noticed that theNethbios Add Name requests were not being handled

quickly enough, so we added a 2 second delaybetween each add. This seemed to be sufficient.

\new

SOFTWARE ON the TANDEM (host)

DOMAIN commands (continued) :

We then added the remaining windows with the followinSCF

commands:

add WS $laml.#PIT2, domain #PIT

B-40

Page 116: GNAS Maintenance Control Center (GMCC) Design

add window $laml.#PIT2MCs,WSname #PIT2delay 2add window $laml.#PIT2MMs,WSname #PIT2delay 2add window $laml.#PIT2TCl,WSname #PIT2add WS $laml.#PIT3, domain #PITdelay 2add window $laml.#PIT3MCs,WSname #PIT3delay 2add window $laml.#PIT3MMs,VSname #PIT3delay 2add window $laml.#PIT3TCl,WSname #PIT3delay 2add WS $1aml.#PIT4, domain #PITadd window $laml.#PIT4MCs,WSname #PIT4delay 2add window $laml.#PIT4MMs,WSname #PIT4delay 2add window $laml.#PIT4TCl,WSname #PIT4delay 2

Now that objects were added, and the application names

weresuccessfully added to the MLAD adapter, we initialized the

objects by isssuing the start command.

start line $laml,sub all

\new

SOFTWARE ON the TANDEM (host) :

Adding the application windows :

We wanted to have applications running against thewindows, so we added the application items using PATHCOM.

Since the application code we were using supported onlya four TCP configuration, we added the each 'terminal'to the TCP with the same number as the workstationnumber. This was done intentionally so that a problemimpacting a particular TCP (i.e.-CPU crash) would onlydiable one workstation at the GNAS. A given workstation

number at each GNAS would be associated with the Mn-TCPon the MPS (where n is the terminal number).

PATHCOM /in \ACTA.$system.mmslan.LANCONF/ $MMS

B-41

Page 117: GNAS Maintenance Control Center (GMCC) Design

Where the file LANCONF would contain the followingentries for each GNAS MCC :

Set up the default values to be used for both MMS and MCS

applications.

SET TERM DISPLAY-PAGES 5SET TERM INITIAL MMSINITSET TERM TMF ONSET TERM AUTORESTART 0SET TERM TYPE T16-6530

Declare the individual terminals to support the MMSapplication.

SET TERM FILE $laml.#PITlmmsSET TERM TCP Ml-TCPSET TERM PRINTER $S.#PITlADD TERM PIT1MMS

SET TERM FILE $laml.#PIT2mmsSET TERM TCP M2-TCPSET TERM PRINTER $S.#PIT2ADD TERM PIT2MMS

SET TERM FILE $1aml.#PIT3mmsSET TERM TCP M3-TCPSET TERM PRINTER $S.#PIT3ADD TERM PIT3MMS

SET TERM FILE $laml.#PIT4mmsSET TERM TCP M4-TCPSET TERM PRINTER $S.#PIT4ADD TERM PIT4MMS

\new

SOFTWARE ON the TANDEM (host) :

Adding the application windows (continued) :---------------------------------------------

Declare the individual terminals to support the MMSapplication.

SET TERM FILE $laml.#PITlmCsSET TERM TCP Ml-TCPSET TERM PRINTER $S.#PITlADD TERM PITIMcS

SET TERM FILE $laml.#PIT2mCs

B-42

Page 118: GNAS Maintenance Control Center (GMCC) Design

SET TERM TCP M2-TCPSET TERM PRINTER $S.#PIT2MADD TERM PIT2McS

SET TERM FILE $1aml.#PIT3mCsSET TERM TCP M3-TCPSET TERM PRINTER $S.#PIT3MADD TERM PIT3McS

SET TERM FILE $laml.#PIT4mCsSET TERM TCP M4-TCPSET TERM PRINTER $S.#PIT4MADD TERM PIT4McS

B-43

Page 119: GNAS Maintenance Control Center (GMCC) Design

SOFTWARE ON the TANDEM (host) :

Adding the application windows (continued)------------------------------------------

Then we started the sessions with the following command.

PATHCOM/ in STARTWIN/ SMMS

Where STARTWIN would contain the following commands foreach GNAS MCC :

start term PITlmmsstart term PIT2mmsstart term PIT3mmsstart term PIT4mmsstart term PITlmcsstart term PIT2mcsstart term PIT3mcsstart term PIT4mcs

A TACL process was then started as follows for each GNASMCC:

tacl/in $laml. #PITltcl,out $laml. #PITltcl,name$PITtl,nowait,pri 150,cpu 3/2

tacl/in $laml. #PIT2tcl, out $laml. #PIT2tcl,name$PITt2,nowait,pri 150,cpu 2/3

tacl/in $laml. #PIT3tcl,out $laml. #PIT3tcl,name$PITt3,nowait,pri 150,cpu 0/1

tacl/in $laml. #PIT4tcl,out $laml. #PIT4tcl, nameSPITt4,nowait,pri 150,cpu 1/0

We found that it was extremely useful to use the namingconvention shown in the above examples. Each nameidentified the domain, window, workstation, and applicationwhenever a problem occured.

The actual startup files we used in our testing can befound on \ACTA.$SYSTEM in the MULTILAN and MMSLANsubvolumes. The MNSLAN subvolume contains the startup andconfiguration used for the PATHWAY application. TheMULTILAN subvolume contains the remaining files (includingthis file).

B-44

Page 120: GNAS Maintenance Control Center (GMCC) Design

SOFTWARE ON the TANDEM (host):

Adding the TANDEM SERVER environment:

The TANDEM system administrator created a user id underthe MMS user group called IMMS.GMCC' and gave it a passwordof 'GMCCUSER'.

The TANDEM server environemnt was to be located in\ACTA.$DATA2.DOSDISK subvolume. Logged on as 'MMS.GMCC' andin the $data2.dosdisk subvolume, we created the twonecessary files by entering the following FUP command:

FUP/in Saystem. sysl7.MLSRVFUP/

This created the DOSENT and DOSACC files needed to managethe DOSDISK.

The STARTSRV file contains the startup info we used for theMultiLan Server (MLSRV).

The STARTSRV file contained the following:

MLSRV/name Smsrv,in CMDS,cpu 2,pri 160/

where CMDS contains:

backupcpu 3memory 2500000lan adapter $laml.#PITa0.0 1share dosdisk - \ PWD /rwcshare PITIdos - \PIT1 pswdPl /rwcshare PIT2dos - \PIT2 pswdP2 /rwcshare PIT3dos = \PIT3 pswdP3 /rwcshare PIT4dos - \PIT4 pswdP4 /rwcshare guard - GUARDIAN /1800share sread - SPOOLERREAD Sspls /US7share swrite - SPOOLERWRITE $s.#lp /us7 /$splscache files 10 read

B-45

Page 121: GNAS Maintenance Control Center (GMCC) Design

SOFTWARE ON the TANDEM (host):

Adding the TANDEM SERVER environment:

At the workstation we added the following commands tothe AUTOEXEC.BAT file:

RMPCCOM SET HOST \ACTARMPCCOM LOGON @\ACTA MMS. GMCC, GMCCUSER

net use f: \\acta msrv0l\dosPIT pswdPlnet use g: \\actajmsrvol\guardnet use h: \\acta msrv0l\sreadnet use lpt2: \\acta msrv0l\swrite

On the first workstation we did a 'net use' on the'dosdisk'sharename. We then created the subdirectories tobe assigned to each workstation i.e.-\PIT1,\PIT2,\PIT3,\PIT4) using the MKDIR command.

We assumed that each workstation would have a uniqueand separately secured DOS partition. If you decided toallow all workstations to share a single DOS partition, youcould specify the 'net use' as follows:

net use f: \\acta-msrv0l\dosdisk PWD

B -46

Page 122: GNAS Maintenance Control Center (GMCC) Design

Missing Software:

During the Memphis GNAS MCC testing, an addition wasmade to the I.M.C.S. software to allow for a WSPTPconnection to a BORLAND Turbo C program running on one ofthe workstations. This software combination is refered toas the 'status board'.

I requested this software from the FAA people at thetechnical center. Joe Salvatore, of the FAA, supplied mewith some of the P.C. source code. The diskette containingthe software was unreadable in certain sectors, and , as aconsequence, the TANDEM TAL WSPTP application could only bepartially restored.

I then requested that Jay Jones send me a copy of thissoftware from Memphis. Jay agreed to do so. I have not yetreceived the tape.

The 'status board' software will have to be tested atlater date.

B-47

Page 123: GNAS Maintenance Control Center (GMCC) Design

APPENDIX C

PROGRAM TROUBLE REPORTS (PTRS)

Page 124: GNAS Maintenance Control Center (GMCC) Design

Report No. Project Subsystem Test Date Create Date

PTR-01 GMCC 04/22/91 05/10/91

Report By: Test Sequence IDC.Stewart DQT2.4 - UNIX V Software Checkout

Test Step Description:Run KERMIT software.

Category of Failure I II III IV V(circle one) critical major minor annoyance other

Brief Description:KERMIT SOFTWARE NOT OPERATIONAL.

Detailed Description:

Although an icon for the KERMIT communications softwareprogram existed in the directory, the application wouldnot run. This prevented the user from accessing UNIX onserver.

Test Engineer _

Disposition Instructions:

Follow-up Status

Date:1.2. _j

Closure Description:

_ _ __ _ __ _ __ _ ___I/ -_ _

Approved:

Test Director

ACN-250/CTA/051091

C-1

Page 125: GNAS Maintenance Control Center (GMCC) Design

Report No. Project Subsystem Test Date Create Date

PTR-02 GMCC 04/23/91 05/10/91

Report By: Test Sequence IDC.Stewart DQT2.6 - MicroGate Emulator Checkout

Test Step Description:In MMS2 environment.

Category of Failure I II III IV V(circle one) critical major minor annoyance other

Brief Description:KEYBOARD LOCKUP OCCURRED.

Detailed Description:

A keyboard lockup occurred when the screen updated at thesame time that a key entry was made. The application hadto be exited and restarted. The key entry was lost. Thissituation occurs on the Tandem terminal as well.

Test Engineerne r_ _ __ _ __ _

Disposition Instructions:

Follow-up Status

Date:1. _ jj2. _

Closure Description:

_ _ _ _ _ _ _ _ _ _ _ _ _ __ / -_

Approved:

Test Director

ACN-250/CTA/051091

C-2

Page 126: GNAS Maintenance Control Center (GMCC) Design

Report No. Project Subsystem Test Date Create Date

PTR-03 GMCC 04/22/91 05/10/91

Report By: Test Sequence IDC.Stewart DQT2.8 - PackRat Software Checkout

Test Step Description:Run PackRat software.

Category of Failure I II III IV V(circle one) critical major minor annoyance other

Brief Description:PACKRAT SOFTWARE NOT INSTALLED.

Detailed Description:

No icon exists for the PackRat software program.

Test Engineer

Disposition Instructions:

Follow-up Status

Date:1. __J _2. . _J _

Closure Description:

Approved:

Test Director

ACN-2SO/CTA/051091

C-3

Page 127: GNAS Maintenance Control Center (GMCC) Design

Report No. Project Subsystem Test Date Create Date

PTR-04 GMCC 04/22/91 05/10/91

Report By: Test Sequence IDC.Stewart DQT2.9 - Back-It Software Checkout

Test Step Description:Format 1.2MB floppy disk in A: drive.

Category of Failure I II III IV V(circle one) critical major minor annoyance other

Brief Description:FORMAT ERROR OCCURRED.

Detailed Description:

When formatting a high-density floppy disk in the A:drive, the message "ESC PRESSED OR TIME-OUT ERROR" keptappearing and stopping the format process. The disk wouldeventually format after repeating the format attempt.

Test Engineer

Disposition Instructions:

Follow-up Status

Date:1. ._JJ

2. _ JJ

Closure Description:

_____ ____ ____ _ -_-_-

Approved:

Test Director

ACN-250/CTA/OS1091

C-4

Page 128: GNAS Maintenance Control Center (GMCC) Design

Report No. Project Subsystem Test Date Create Date

PTR-05 GMCC 04/22/91 05/L0/91

Report By: Test Sequence IDC.Stewart DQT2.9 - Back-It Software Checkout

Test Step Description:Backup files to B: drive.

Category of Failure I II III IV V(circle one) critical major minor annoyance other

Brief Description:BACKUP LOOKS AT WRONG DRIVE.

Detailed Description:

With a floppy disk in the B: drive, a backup attempt to

the B: drive attempts to copy files to the empty A: drive.The backup is successful on the second attempt.

Test Engineer

Disposition Instructions:

Follow-up Status

Date:1. . JJ/2. . JJ

Closure Description:

_ _ _ _ _ _ _ _ _ _ _ _ _ ____'- __

Approved:

Test Director

ACN-250/CTA/051091

C-5

Page 129: GNAS Maintenance Control Center (GMCC) Design

Report No. Project Subsystem Test Date Create Date

PTR-06 GMCC 04/23/91 05/10/91

Report By: Test Sequence IDC.Stewart DQT3.3 - Simultaneous WS Operations

Test Step Description:Print IMCS reports.

Category of Failure I II III IV V(circle one) critical major minor annoyance other

Brief Description:IMCS REPORTS CANNOT BE PRINTED.

Detailed Description:

IMCS reports cannot be printed to the network printer.

Test Engineer AgeKI'd

Disposition Instructions:

Follow-up Status

Date:1. _/_/2. _

Closure Description:

Approved:

Test Director

ACN-250/CTA/O51091

C-6

Page 130: GNAS Maintenance Control Center (GMCC) Design

Report No. Project Subsystem Test Date Create Date

PTR-07 GMCC 04/23/91 05/10/91

Report By: Test Sequence IDC.Stewart DQT3.3 - Simultaneous WS Operations

Test Step Description:Print MMS reports.

Category of Failure I II III IV V(circle one) critical major minor annoyance other

Brief Description:MMS REPORT PRINTING PROBLEM.

Detailed Description:

MMS reports can only be printed by the network printerwhen the MMS window or session from which the print isissued is exited.

Test En g n e __ _

Disposition Instructions:

Follow-up Status

Date:1. _/JJ2. _AJJ

Closure Description:

_ _ _ _ _ _ _ _ _ _ _ _ _ _ __-I _/

Approved:

Test Director

ACN-25nCTA/O51091

C-7

Page 131: GNAS Maintenance Control Center (GMCC) Design

Report No. Project Subsystem Test Date Create Date

PTR-08 GMCC 04/23/91 05/10/91

Report By: Test Sequence IDC.Stewart DQT3.4 - GMCC Operational Control

Test Step Description:Monitoring/Unmonitoring data points.

Category of Failure I II III IV V(circle one) critical major minor annoyance other

Brief Description:IMCS PROBLEM - RANDOM ERROR.

Detailed Description:

When monitoring or unmonitoring more than one data point,a random error occurred advising the user to notify theMPS Supervisor.

Test Engineer

Disposition Instructions:

Follow-up Status

Date:1. _. _.J

2. _JJ

Closure Description:

_ _ _ _ _ _ _ _ _ _ _ _ _ _ __-I __

Approved:

Test Director

ACN-250/CTA/051091

C-8

Page 132: GNAS Maintenance Control Center (GMCC) Design

Report No. Project Subsystem Test Date Create Date

PTR-09 GMCC 04/22/91 05/10/91

Report By: Test Sequence IDC.Stewart DQT2.1 - Local Area Network Checkout

Test Step Description:Enter an invalid password.

Category of Failure I II III IV V(circle one) critical major minor annoyance other

Brief Description:INVALID PASSWORD SECURITY.

Detailed Description:

Even though an incorrect password was entered, the message"DQE was logged on successfully" was displayed and networkaccess was allowed.

Test Eng ir__ _

Disposition Instructions:

Follow-up Status

Date:

2. . JJ

Closure Description:

Approved:

Test Director

ACN-250/CTA/051091

C-9

Page 133: GNAS Maintenance Control Center (GMCC) Design

Report No. Project Subsystem Test Date Create Date

PTR-10 GMCC 04/22/91 05/10/91

Report By: Test Sequence IDC.Stewart DQT3.3 - Simultaneous WS Operations

Test Step Description:Run second Constant Monitor.

Category of Failure I II III IV V(circle one) critical major minor annoyance other

Brief Description:CONSTANT BEEP OCCURRED WITH TWO CONSTANT

MONITORS RUNNING AT ONCE.

Detailed Description:

Opening two IMCS windows and running simultaneous ConstantMonitors caused the workstation to issue a constant beep.The beep was loud enough to cause aggravation.

Test Engineer n r __ _

Disposition Instructions:

Follow-up Status

Date:1. _2. JJ

Closure Description:

_ _ _ _ _ _ _ _ _ __ _ _ _ __'- __

Approved:

Test Director

ACN-2S0/CTA/O51091

C-10

Page 134: GNAS Maintenance Control Center (GMCC) Design

Report No. Project Subsystem Test Date Create Date

PTR-11 GMCC 04/22/91 05/10/91

Report By: Test Sequence IDC.Stewart DQT2.6 - MicroGate Emulator Checkout

Test Step Description:Running an IMCS session.

Category of Failure I II III IV V(circle one) critical major minor annoyance other

Brief Description:25TH LINE NOT DISPLAYED.

Detailed Description:

Within an IMCS session, there is no display of 25th linereal-time alerts.

Test Engineer n e _ ___ _

Disposition Instructions:

Follow-up Status

Date:1. . JJ2. . _JJ

Closure Description:

_____ ____ _____ _-I/-

Approved:

Test Director

ACN-250/CTA/OS1091

C-11