[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 7.286::space

Title:Space Exploration
Notice:Shuttle launch schedules, see Note 6
Moderator:PRAGMA::GRIFFIN
Created:Mon Feb 17 1986
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:974
Total number of notes:18843

191.0. "DEC Computers on Space Shuttle" by ODIXIE::VICKERS (Don Vickers, Notes DIG member) Fri Jul 11 1986 00:00

    Today was truly a thrill.  I actually touched the Discovery orbiter.
    I visited KSC along with Marliyn Leon from the Orlando office to
    discuss how Lockheed is going to use two clustered 8200's and a
    MicroVAX-II to eliminate paperwork for orbiter flows.
    
    The computers are to make up a system called Process Engineering
    Computer System (PECS).  The current Process Engineering system
    is TOTALLY manual with an average of 5,000 Work Authorization Documents
    (WADS) per flow (turnaround).  Approximately half of these are
    unplanned flow activities.  Approximately 1,000 are tile related.
    Each WAD requires a minimum of four signatures and a maximum of
    nine depending upon the criticality or hazard of the work.  The
    signees are spread out over the base so physical paper movement
    is a problem.
    
    Lockheed hopes to eliminate all the paper in the flow of the orbiter.
    Not only does the paperwork slow the process but a fair portion
    is wrong due to being out of sync with the real work on the orbiters.
    Working in, on, and around the orbiter is not a place convenient
    for filling in a form so the technicans either 'remember' what they
    need to know or write it on scratch pads and then transcribe it
    onto the WAD forms.
    
    Lockheed plans to use voice input and output with the technicans
    and they already have a prototype using an IBM AT.  The VAXen have
    been sold with tons of software.  There is DEChealth, ALL-IN-1,
    RDB, DECgraph, Datatrieve, and Pascal.  Unfortunately, there is
    no functional specification or a whole lot of planning.  Nor was
    any consulting or real support from Digital.  The Lockheed people
    are fairly sharp but have no Digital experience.
    
    I hope to spend more time with them next week trying to help them
    learn how to use what they've bought as effectively as possible.
    They plan to start programming right away and I was unable to convince
    them to look before they leap.  Clearly, we all want this project
    to succeed for a lot of reasons.
    
    I'll provide more details here if the noting public would like.
    
    Today was a real thrill and it looks like Digital will play a positive
    role in helping the shuttle fly again.
    
    Don
T.RTitleUserPersonal
Name
DateLines
191.1Keep us postedGNUVAX::BKETTLERBrian P. KettlerFri Jul 11 1986 14:397
    
    Sounds likes you're going to enjoy that assignment :-)
    
    Keep us posted.
    
    /brian
    
191.2I'll goLATOUR::DZIEDZICFri Jul 11 1986 22:153
    Need any unpaid volunteers (well, with the exception of the
    mortgage payment!)?
    
191.3I want to know EVERYTHING, but not at all costSKYLAB::FISHERBurns Fisher 381-1466, ZKO1-1/D42Tue Jul 15 1986 16:5910
    re .0:  Zow! What an assignment!  But much as I would like to know
    everything, please make sure that your consience is clear before
    telling us about a customer's software.  I guess the standard SWS
    contract is "if we do it, we own it" or some such, but just a
    reminder...
    
    Go to it!  Maybe you can fix the SRBs while you are there, too?
    
    Burns
   
191.4A progress reportODIXIE::VICKERSDon Vickers, Notes DIG memberSun Jul 20 1986 12:3025
    Last week we installed a MicroVAX-II in the OPF.  It's conveniently
    located under the port wing of orbiter 102 (Columbia) in high bay
    2.  Quite a nice location for doing a software installation - the
    ceiling were the black tiles of the orbiter 10 feet above us.
    
    The machine is a demo machine that had VMS on it and some demo software
    for CIM.  We installed PASCAL for the LSOC people to run their voice
    software which they've developed on an IBM AT.  We copied their
    PASCAL code over to the uVAX and the sucker compiled correctly right
    away!!
    
    I go back on Monday to install ALL-IN-1 which they plan to use for the
    office automation aspects of the project.  I'm also going to install
    VAX Notes to show them how it could be used.  Given that this is
    a demo machine it seems like a demo is in order.
    
    There was a fair amount of interest on the part of the technicans
    in the high bay as to what the system was going to be doing.  Every
    one of them that talked to us indicated the need for some automation
    in the administrative areas.
    
    I'm excited as we should be able to provide them with the best tools
    to solve their problems.  I'll let you know here how it goes.
    
    Don
191.5VAX Notes is in KSCODIXIE::VICKERSDon Vickers, Notes DIG memberMon Jul 21 1986 22:0427
    Just got back from KSC after installing ALL-IN-1 and VAX Notes.
    I did a brief demo of VAX Notes and the senior manager indicated
    that he would approve purchase of it.  I'm not sure if they REALLY
    understand how valuable VAX Notes can be to them.  I certainly plan
    to keep pushing on it.
    
    They start a pilot project for step and gap quality control late
    this week.  This is where the step (difference in vertical height)
    and gap between all of the tiles is measured.  There are limits
    for each zone on the orbiter and also some overall score based on
    the weighting of each area.  Up until now, this job has been done
    completely by hand.  The technicans write down each measurement
    and then compute the individual values.  The clerical staff then
    take all the technican worksheets and compile the overall score.
    It takes several days of manual computations.
    
    The major point of the pilot these next few weeks is to determine
    whether the technicans can interface with the system through the
    voice input/output units.  The long term plan is to then automate
    all the paperwork required for the orbiter flows.
    
    In the mean time, they've just realized that they need a printer
    to print out the step/gap report.  (`:
    
    Still a thrill,
    
    Don
191.6Hope I Read .5 Wrong!LYMPH::DENSMOREMike DensmoreTue Jul 22 1986 08:565
    Ack!  By hand?  What no slide rules? :-)
    
    					Mike
    
    PS. Good to see DEC pitchin' in.
191.7I'm afraid notODIXIE::VICKERSDon Vickers, Notes DIG memberTue Jul 22 1986 10:268
    Actually, a few months ago they did add an HP programmable calculator.
    
    Prior to that, they CLAIM that it was really MANUAL.

    I know it's hard to believe but the orbiter processing is VERY manual
    in all respects.
    
    Don
191.8manual => inaccuracyDSSDEV::SAUTERJohn SauterWed Jul 23 1986 09:0110
    According to the Rodgers Commission report, there is (was) so much
    manualness in the work order system that some reports were 98%
    inaccurate.  It seems that the system is (was) so hard to use that
    it was avoided or ignored.  You have a considerable potential for
    improvement.  I only hope the voice I/O stuff works well.
    
    In case you didn't know, you have a whole bunch of envious engineers
    watching you through this notes file.  Please continue to keep us
    informed.
        John Sauter