Technology Give-Away in the 80s

       SAMPLE OF 800,000 BYTES TRAVELING BITNET TO EUROPE       
 COLLECTED BY SOBCZAK TO WARN OF UNANTICIPATED TECHNOLOGY LOSS
            COPIES SUPPLIED TO NAVAIR 411, CNO AND NIC

The following was captured from a BBS system in the midwest which
advertises its BITNET connection to the European continent.  The
compressed file was being transferred to a BBS in WARSAW Poland.
It was for that reason we copied the file to see what information
was moving off shore.  This BBS is frequented by emigres from
Eastern Europe.  Some users possess an apparent high tech bent as
validated by the topics discussed.  Some transmissions seem to be
based in slavic or cyrillic.  The capture, less its BBS message
heading, appears:

DISCLAIMER: Sobczak cannot verify or validate the accuracy or
how current the following text might be.  To the best of our
knowledge any transmission from a public domain BBS is harmless.
Every attempt has been made to notify proper authorities
concerning the appearance of this text and/or software.

*****************************************************************
 Morzy byc?
 
             MICROMPUTER Version of NAVAIR Level of Repair Models
                        USER INSTRUCTIONS FOR PC
 
_______________________________________________________________|
                                                                                                               |
|TO EXECUTE MODEL AFTER INSTALLATION:                                          |
|                   ENTER "LOR" AT THE PROMPT                                           |
|_______________________________________________________________|
 
The following two NAVAIR Level of Repair (LOR) models have been
translated from SIMSCRIPT and combined into a single model
written in FORTRAN-77 (ASCII X3.9-1978 standard):
 
     Avionics Level of Repair Model MOD III Release 6
     Avionics Support Equipment Level of Repair Model MOD II    
        Release 4
 
Specifications and descriptions of these models are given in
MIL-STD-1390B, Level of Repair, Appendices A and B.  User Manuals
(dated September, 1988) are available from Naval Air Systems
Command (AIR 411, Attn: Capt J. Hall).
 
Although the MICROCOMPUTER version required extensive changes in
the program LOGIC, all of the inputs and outputs are the same as
the former versions.  An IBM PC/XT/AT (or compatible) with at
least 640K RAM and a hard disk is required.  A math chip (8087 or
80287) is optional; the model will run more than twice as fast if
one is installed.
 
This version of the model is designed to run in "batch" mode
similar to the previous models.  Input data is prepared in a
single data set.  The model generates all outputs in a single
output data set which may then be edited and/or printed.  At the
beginning of a session, the user is asked to identify the model
type (Avionics or Support Equipment) and the name of the input
file.  The model generates an output file with the same prefix as
the input file but with a ".OUT" suffix.  As the model executes,
the user is informed of progress on the console screen.
 
PROBLEM SIZE
 
The MICROCOMPUTER version of the model is limited in the size of
problem that can be run.  These limits are as follows:
 
                                                                Maximum Number
       Items                                                           80
       Sites                                                           30
       Manpower Types                                          50
       Support Equipment Types                             50
       Documentation Types                                   50
       Space Types                                                50
       User-defined Maintenance Alternatives             3
       Sensitivity Analysis Groups                            5
       Number of Resources per Maintenance Task  12
       Number of Distant Repair Sites per User Site   5
 
If any of these limits are exceeded in a model run, error
messages are produced and the input data must be appropriately
revised.
 
The program requires about 534K bytes of RAM to run.  If you have
a 640K RAM computer but with other programs in residence at the
same time, the model may not run (an "insufficient memory"
message will be given).  You must then remove some of the
resident programs if you want to run the model.
 
COMPATIBILITY WITH MAINFRAME MODELS
 
Although the MICROCOMPUTER model is designed to operate with the
same inputs as the MAINFRAME versions and produce the same
outputs, there are several minor differences of which the user
should be aware.
 
1.  Several minor input data format changes have been
implemented.  These are as follows:
 
     a. Format I - Part Number
          This field has been expanded from 12 columns to 16
columns to allow entry of NSNs.  The field is now in columns
19-34 (formerly, columns 19-30).
 
     b. Format I - Item Nomenclature
          This field has been shifted 4 columns to the right to
accomodate change #1.  The field is now in columns 36-75
(formerly, columns 32-71). 

     c. Format L - Unit Cost

          In order to allow values of Unit Cost that exceed the
field width, entries may now be made in thousands of dollars,
with a "K" in the last position.  For example, an entry of
"146.5K" would be interpreted as $146,500.  If a "K" is not
entered, the given value is used.  For example, an entry of
"146.5" is interpreted as $146.50.  If a "K" is entered and is
not in the last position of the field, an error message will
result.
 
     d. Format T - Support Equipment Name
          This field has been expanded from 6 columns to 8
columns.  The field is now in columns 13-20 (formerly, 15-20).
 
        Format T - Documentation Cost
           In order to allow values of Documentation Cost that
exceed the field width, entries may now be made in thousands of
dollars, with a "K" in the last position (column 64).  See change
"c." above for instructions on entering values in this field.
 
The model will run with datasets in the old formats,i.e., Release
5 or below.   The only noticeable difference in outputs is in the
Equipment Breakdown report  (one of the input data listings).
Here, entries under the headings "MFG PART  NO." and
"NOMENCLATURE" will appear split up but will be readable. (look
for GAC for F-14C, GEAC is F-14A/B, all MACAIR are F-18A) 
                                                                      
2.  Input Data Sequence.  The MICROCOMPUTER model imposes
restrictions on the order in which the various input records are
arranged:
 
     a.  The A and P format records must be first in file (in
either order).
 
     b.  The T format records (Task Data) must follow the I and M
formats.
 
     c.  The N format records (Alternatives) must follow the I
format records.
 
     d.  The Q format records (Sensitivity Analysis) must be last
in file.
 
To avoid any problem in this regard, it is recommended that the
input data always be prepared in the following order:
 
     Format A - Analysis Identification
     Format P - Option Selections
     Format Y - Parameters
     Format Z - Parameters
     Format S - Site Data
     Format I - Item Identification
     Format L - Item Characteristics
     Format M - Manpower Data
     Format T - Task Data
     Format N - Maintenance Alternatives
     Format Q - Sensitivity Analysis Specifications
 
3.  Site Data.  Site data (Format S) should be in sequence
according to site type (CV,NAS,PIMA,DEPOT).  If a distant repair
site is referenced with a lower sequence number than the given
site, a run error message will be produced.
 
4.  Item Data.  Item identification data (Format I) must be in
sequence according to a top-down breakdown of the equipment.  The
model cannot detect errors of this kind and may run but with
incorrect or strange results.
 
5.  Additional Standard Maintenance Alternative.  An additional
standard maintenance alternative has been provided in the FORTRAN
version.  In this alternative, all WRA's are repaired at the
depot and optimal LOR codes are assigned to all lower indentured
items.  This alternative is defined as Standard Alternative #6
and the pure optimization alternative (formerly #6) is now #7.
All output reports have been revised to accomodate this
additional alternative.
 
6.  Format Changes.  A variety of minor changes in the output
report formats have been made to enhance their readability and to
reduce the number of pages of printout.
 
7.  Sensitivity Analysis Specifications.  A significant change
has been made in the way specifications for sensitivity analyses
are entered on the Q format.  For many of the input parameters
that can be sensitized, several conditions controlling the scope
of sensitization are defined.  Previously, only one type of
condition for a given parameter could be selected in each run.
Now, combinations of conditions may be selected.
 
This change may be illustrated by considering Parameter #10, GSE
Cost, in the MOD III Avionics model.  For this parameter, five
different sensitizing conditions are defined:
 
     a.  Site Type (CV,LB,PIMA,Depot)
     b.  Item Indenture (WRA,SRA,Sub-SRA)
     c.  Task Type (Verify,Repair)
     d.  Resource Type (Shared,Dedicated)
     e.  Specific Items
 
Previously, only one of the five possible conditions could be
selected by entering an "X" in appropriate columns of the input
form, with entry fields for the other conditions being left
blank.  Now, however, combinations of conditions may be
specified.  For example, you may specify that only
DEDICATED GSE resources used in REPAIR tasks for WRAs at DEPOTs
may be sensitized.  This is accomplished by entering an "X" in
the indicated columns of the Q Format.
 
For this additional flexibility to work, however, entries must be
made for all conditions to be operative during the run.  For the
GSE Cost example, this means that specific entries must be made
in each of the first 4 condition fields listed above; if any one
of the fields is left blank, an error message will result.  To
sensitize on GSE Cost under all conditions, therefor, an "X"
must be entered in each column of the first 4 fields (Site Type,
Item Indenture, Task Type, and Resource Type).  For the last
field (Specific Items), entries are optional.  The sensitization
will be operative for all listed items not covered by
specifications in the Item Indenture field.
 
8.  Error Checking.  The MICROCOMPUTER version checks input data
more rigorously than the MAINFRAME models.  As a result, error
messages may be produced for data which would previously be
accepted.  This is particularly true for Format Q entries due to
the model change described above for specifying sensitivity
conditions.
 
9.  Model Errors.  Several minor errors in the MAINFRAME versions
of the model have been corrected.  As a result, slightly
different results may be expected when the MICROCOMPUTER model is
run with the same data.
 
DISK CONTENTS
 
In addition to files used to install the model on your computer
according to procedures given below, this disk contains the
following data sets:
 
    TABLE.DAT  - Data used by inventory policies of the model
    AV.DAT     - Example data for the Avionics model
    SE.DAT     - Example data for the Support Equipment model
 
The two example data files contain input data for the LOR
problems used in the User Manuals mentioned above.  You may use
this data to see how the model runs.  When running the model, you
will be asked to input the name of your input data file.  If,
instead, you press ENTER, the appropriate example data file will
be used.
 
MODEL INSTALLATION AND OPERATION
 
The model is provided on three floppy diskettes.  First, copy all
diskettes and save the originals.  Using the copies, the model
may then be installed on your computer with the following
one-time procedure (Note - you must have a hard disk plus a
floppy drive that can read DSDD diskettes):
 
STEP 1:  Make a new directory on your hard disk.
 
                  Example:  C:>MD LORA
STEP 2:  Copy the contents of the three diskettes into the new
directory.
 
                  Example:  C:/LORA> COPY A:*.*
                  (This examples assumes that you are in the new
directory, LORA, and the diskette is in drive A.  This command is
applied for each of the three diskettes.)
 
STEP 3:  Enter the command, INSTALL.
 
                  Example:  C:/LORA> INSTALL
 
The INSTALL procedure will create a file, LOR.EXE, and will
delete all files used to install the model, including the INSTALL
procedure itself.

After the model is installed, it may be run by entering LOR atthe
DOS prompt.
 
                  Example:  C:/LORA> LOR
 
Input data for the run must be in the same directory as the model
(if the data is in some other directory, copy it over before
running the model). The file containing outputs of the run will
be written in the model directory.
 
HELP
 
The point of contact when problems arise with any of the NAVAIR
LOR models is R T Golenblowski ILS POLICY MANAGER, NAVAIR-41112,
(202) 692-2644 or Tom Pope LOR Program Manager, NAVAIR-41112A,
(202) 692-0028.
 
Czy ty morzesaromiec?  Ja nie wierze jedne gosttnwka.  To jest
niemorzebny. Ja rzarce nato. Dobra noc.  Ja musze isc.

                         .................PODROZNY

     The names and telephone numbers are real. Should you call and
ask for a copy of the Level of Repair models, they will probably
refuse.  As a taxpayer you can write a freedom of information
request asking for a copy.  Send along a blank formatted floppy
disk.