Non Volatile Technologies Pty Ltd

SYDNEY  AUSTRALIA   2227    (ABN 96 078 508 264)    Ph:+61 2 9016 4695 

"Helping others to have a future assures our own."

Automated and Simplified Tray Stores Ordering System

By Kevin Loughrey

Untidy state of 27 District Wksp

27 District Wksp Floor - 1988
Shelving & Tray Stores on Castors

Tray Store Ordering System

Example of barcode labels



1988-1989 In late 1987, I was seconded as an exchange officer to serve in the British Army.  My posting was to 27 District Workshop, located at Warminster, in the South West of England.  The workshop's location was most probably, to some extent the result of the British Army's School of Infantry being located at Warminster and the Salisbury Range training area being close by(as also was the famous Stone Henge).  I occupied the Production Manager's position and was also the second in charge of the workshop; the workshop being commanded by a Colonel (Colonel John Skinner) and my rank being Lieutenant Colonel.  27 District Workshop was the largest workshop in the British Army.  It not only supported local equipment but also performed 3rd and 4th line program rebuilds of fleet equipment operated throughout the British Forces. 

Having Colonel Skinner as my Commanding Officer was a happy coincidence because when I was the Officer Commanding of ACT Workshop Platoon, at Duntroon, in 1979, then Lieutenant Colonel Skinner was the Staff Officer Grade 1 (EME) at 2 EME Gp, HQ 2nd Military District, located in Sydney.  ACT Workshop Platoon was under the command of HQ 2 EME Gp and Lieutenant Colonel Skinner was effectively my Commanding Officer.

When I arrived at 27 District Workshop the state of the workshop floor was very untidy.  It was a dark and gloomy place because of inadequate lighting; something the unions were constantly (and rightly) railing against.  The lights were an orange argon type and this colour gave a depressing feeling to the workplace.  Staff were under considerable pressure because of the reforms, aimed at sheeting home financial accountability, introduced by the Thatcher Government.  In general, the staff at the workshop were highly motivated, well trained and of high quality in terms of their honesty, work-ethic and diligence.  The stress of coping with sudden change though had had an adverse effect on things such as workshop tidiness and basic organisation. 

27 District Workshop was the largest of all the district workshops in the UK Ministry of Defence.  It undertook some overflow programme repair and so verged on being a Base Workshop.  27 District Workshop tended to be loaded with equipment which the other Base Workshops did not wish to handle for a variety of reasons.  In some cases, the equipment was obsolete, the parts were always difficult to obtain and the equipment was often in a state of advanced decay.  27 District Workshops was smaller than most Base Workshops but larger than all the other District Workshops.  It was therefore a good testbed.  It it worked at 27 District, it would most likely be effective in all the other Base and District Workshops.

The Problem with Tray-stores

One aspect of workshop operations that was causing considerable disruption to efficient production was the matter of repair parts supply and, in particular, the supply of "ready-to-hand" parts positioned in trays on the production lines and work areas.  Normally, within a workshop, there is a sub-organisation responsible for repair parts supply.  When repairing an equipment, one normally attempts to perform an inspection in order to determine the parts that will be necessary to perform the repair.  It is often not possible to predict all of the parts that will be required.  Certain equipments also do not lend themselves to pre-inspection.  With these equipments, it is necessary instead to inspect and repair at the same time.  It is also not cost effective to have a totally centralised repair parts holding from which the parts are fetched every time there is an unexpected requirement.  For all of these reasons, it is normal practice in a workshop to have on hand, in trays, a variety of fast moving and generally inexpensive parts for the immediate use tradesmen.  These trays, for convenience of management, are generally located in groups, associated with workshop cost-centres, and spread throughout the workplace.  They are referred to as "Tray-stores". 

At 27 District Workshop, there were 177 tray-stores located throughout the workshop.  Each tray-store consisted of as many as 500 trays with a number of parts or an assemblies being held in each tray.  The average was around 50 trays per store; the total number of trays being held on the shop floor was at one time counted as being 8924 trays.  In all, at that time, there were 5,598 "line-items" being held on the floor with an estimated value of £132,000.00 Sterling. 

Tray-stores were a major source of production disruption.  The problems with their managment and upkeep being: A computer system, called ARROW and developed by the Royal Electrical and Mechanical Engineers (REME) Data Centre, was used to manage the stores and the production control in 27 District Workshop.  ARROW ran on an ITL mini computer.  It had a text and menu interface and, for its day, it was quite advanced.  ARROW connected to a large number of dumb terminals throughout the workshop using RS-232, an asynchronous serial system of communications.

The Good Fortune of Having Bob Willcox and Doug Bonner on My Team

The computers were administered by a small staff headed by Mr Bob Willcox.  Bob had two assistants, one of them being Doug Bonner who played a significant role in this and another project.  Bob and his team were excellent.  They were the powerhouse of the computer administration in 27 District Workshop, if not the entire REME.  Them being there was an incredible coincidence of good fortune for me as will become evident later in this story.

My Background Prepared Me Well

CO of 1 Base Workshop, Bulimba, Brisbane. Prior to coming to 27 District Workshop, from 1986 to 1987, I had been the Commanding Officer of 1 Base Workshop Battalion at Bulimba, a suburb of Brisbane the capital of the State of Queensland in Australia.  The Australian Army had a computer system similar to ARROW in its Base Workshops. This was called MAWD, standing for Machine Assisted Workshop Documentation.  MAWD purpose was twofold.  Firstly it provided the means by which workshops could record the process of repairing equipment, including the ordering, consumption and control of repair parts.  Secondly, it gathered data that was then inserted into a central database system called MODERNISE.

EME Systems.  In 1980 and 1981, I was put in charge of EME Systems development in the Australian Army.  In that capacity, I conceived and developed a new family of computer systems, EMEDATER and EMEMic, the emphasis of which was that of helping people perform their work in the workplace; the logic being that if the systems achieved that aim then the data that would be a by-product of this would be accurate and complete; something that the data in MODERNISE was not.  I saw microprocessors as they were called in those days as being the future.  I wanted the Australian Defence Force to adopt a microprocessor called the Onyx.  It ran a Motorola 48000 chip with a 64 bit Math Coprocessor and came equipped with a revolutionary storage device called a Winchester Drive, capable of storing a massive 40 Megabytes of data.  The Onyx could support up to 4 megabytes of dynamic RAM and ran the UNIX operating system.  The C programming language was commonly used to write applications on this computer but high level compilers for FORTRAN and COBOL were either available or under development.  The Onyx cost $4,000.00, imported from the US.  I drove to Sydney to see one just to make sure it was not a figment of a sales-executive's imagination.  Instead of buying the Onyx, Computing Services Division, then the centre of the Defence Computing Bureaucracy chose to purchase the newly arrived IBM PC.  It too cost around $4,000.00 (a friend of mine bought one of the first ones to come to Canberra!) but it was only a shadow of the Onyx.  Besides not having a true 16 bit architecture, unlike the Motorola chip, the IBM 8088 could not handle data and graphics at the same time.  The PC could only support 256 kilobytes of dynamic RAM and did not have a hard drive.  Importantly, even though IBM claimed the PC could be networked using RS-232, a bug in the BIOS meant that every time the PC wrote to the screen, the Programmable Interrupt Controller that handled the Universal Asynchronous Receiver Transmitter, essential for RS-232 communications, was disabled; thereby effectively preventing reliable RS-232 communications. 

Linking PCs to Mini-computers.  In EME Systems Development, my objective was to develop mobile systems that would help people in the workplace.  This meant using PCs.  For their own reasons, Computing Services Division and the Defence computing bureaucracy in general, did everything possible to slow down the introduction of these machines in the workplace.  As a part of this process, I wanted to interface PCs with the Defence Standard Mini-computer, then Perkin Elmers.  Like the IBM PC, the choice of the Perkin Elmer mini-computers by the Defence bureaucracy was a terrible one.  All programs in the Defence Computing Environment had to be written in Common Assembly Language.  This was because the cost of having sufficient magnetic core memory in a Perkin Elmer to allow programming in a high level language such as FORTRAN or even BASIC was prohibitive.  I saw PCs as a means of bridging the gap.  The PCs could be easily programmed in a new language called "Turbo Pascal" to do detailed tasks and the mini-computers could be relegated to being large storage devices and the means by which data was passed to central databases.  Over a period of time, the mini-computers could be phased out altogether.  I was told by CSD that it was impossible to interface an IBM PC with a Perkin Elmer mini-computer.

The Start of Terminal Emulation Software. When I became CO of 1 Base Workshop Battalion, with the approval of the Chief of Staff of the First Military District, Colonel Ford, I used local purchase funds to purchase an Amstrad 512 PC for a little over $1,000.  This was at a time when dumb terminals for Perkin Elmer Mini-computers cost around $4,000.00!  With the help of a friend Lieutenant Stevan
Vujovic, I learnt how to program in Turbo Pascal and Steve obtained for me a library of routines written by Blaise Computing in the US that enabled an IBM PC to communicate using RS-232.  With the help of my Electronics Instruments and Radio Platoon, I constructed a switchbox that allowed me to "listen" to all of the characters passing between a Perkin Elmer terminal and the Perkin Elmer mini-computer and it was not long before I had written the code necessary to allow an IBM PC to imitate a Perkin Elmer terminal; something CSD had claimed was impossible to do.  Using this facility, I quickly wrote an application that allowed me to raise jobs on the MAWD mini-computer for the purposes of achieving a comprehensive system of Time Accounting within 1 Base Workshop; something that had never been achieved anywhere in the Australian Army (and this remains so to this day!).  A life-long friend of mine, Graham Smith, was the CO of 3 Base Workshop Battalion in Broadmeadows, Melbourne, Victoria.  I shared my work with Graham and he installed the same system into 3 Base Workshop.

So when I came to 27 District Workshop, I brought all of this knowledge, my code and my switchbox.  When I saw the problems with repair parts I saw how it would be possible to largely automate the resupply of tray-stores in 27 District Workshop using barcodes as the means of facilitating accurate data capture.


The Management System Used for Tray-stores

The ARROW computer system had a special transaction for the purpose of ordering tray-stores.  It was an abbreviated indenting procedure, designed to save on the number keystrokes necessary to place an order.  As a part of this procedure the amount that could be ordered at any one time was fixed as was the total amount that can be ordered during any monthly period. 

At the time of my arrival, 3 Ordnance storemen use to patrol the workshop on a continual basis, taking note of which trays required replenishment.  They would then make their way to an ARROW terminal and, part by part, input an order to replenish each tray-store.  Besides being very time consuming there were a number of problems with this system of replenishment:

Terminal Emulation Software.

As mentioned, over the previous 4 years, I had been developing software for the purposes of allowing IBM Compatible Personal Computers to emulate various brands of minicomputer terminal.  I had already demonstrated this in 27 District Workshop and written a paper on the subject but it had attracted little interest from REME Data Centre who possibly resented my uninvited intrusion into their business.  I submitted another Staff Suggestion explaining how the emulation is achieved and pointed to the benefits that could be accrued from doing this.  The tray-store application was an object example of how this capability could be exploited with potent results in terms of reduction in labour and improvements in quality and productivity.

The Barcoding of Tray-stores

Hardware.  The hardware used in this project was as follows: Software.  The software that was used in this project was as follows: Outline of the Procedure Used.  The procedure used was as follows:


General.  The system performed beyond expectations.  A summary of the benefits is as follows: Direct Savings.  To set up the system took about 12 man-weeks of work.  Much of this involved the reorganization of existing tray-stores so that they complied with a newly introduced standard called "AQAP 4".  These reforms would have been necessary even if we had not decided to introduce the barcode system.   Reordering using barcodes required about 3 mandays per month of labour.  This figure takes into account not only the physical act of ordering stores but also the need to maintain the database of tray-store data that is used for generating the barcodes on the PC.  The saving is therefore, conservatively, in the order of 2 storeman-years per year.  On present capitation rates this equates to approximately £22,000.00 per year.  Once introduced into the 10 REME Base workshops a total saving of about £220,000.00 pa was achievable.  The initial hardware and software costs for the ten workshops was estimated to be about £30,000.  This money was easily within the Delegated Financial Powers budget allocated to each of these units.  From experience we knew that the maintenance costs of similar systems were about £60.00 per year per installation.  On the basis of an annual investment loss of 10% and add the maintenance costs, the total savings achieved by the system, in the 10 workshops, was estimated to be: £200,000 - £3,000 - £600 = £196,400 pa. (Note this does not in any way take into consideration the value of better productivity on the workshop floor nor better equipment availability in the fleets being maintained.)

Initial Setup Costs.  Initial setup costs were £30,000 in hardware and £25,000 in labour for the the 10 workshops.

Final Comment

The system was developed entirely in-house and largely in the private time of the persons involved.  It was intended to demonstrate and prove the benefits that could be achieved when PCs are interfaced to larger systems such as a mini-computer network and automated data capture devices are employed in combination with these PCs.  I believed then, and am even more convinced now, that the future rests with small, distributed systems capable of securely exchanging data on an opportunistic basis as communications allow.  What was, to some extent, an experiment, developed into a working, reliable and low-cost package that could be utilised to great effect in any workshop; even those without a mini-computer system like ARROW. 

Most importantly, this project, and a subsequent one related to Calibration Management, demonstrated how a small team of people, embedded in a workshop as part of the management team, could develop highly effective systems in a fraction of the time and at a fraction of the cost that would be incurred when a more conventional development approach, involving IT professionals and bureaucrats, is taken.  The Australian Defence Force, for example, has expended tens of millions of dollars over a period of greater than 8 years trying to harness barcodes to some productive advantage.  In this effort, they have employed large teams of consultants from firms like KPMG and utilised the highly structured, innovation-stifling procedures required by the Defence Materiel Organisation and the Chief Information Officer's Group.  All to no avail.


Copyright © NVTech 2005-2011