LEO editor

Roy Irons, one of Ilford Ltd LEO 2/9 computer operator:
The British Oxygen LEO 2/8 was in Edmonton, North London where they had a factory,
distribution and offices. There was also a LEO 2 in the Slough area, I remember going over
there once, at night!
Another thought occurred to me, modern day ‘computer experts’ would not realise that
in the ‘old days’ the programmes were kept on punched cards, not preloaded as now.
Each time you ran a programme you fed the programme in front of the data. As the
programmes were regularly updated, sometimes daily for new programmes, it was the
operator’s worst fear that a card jam would happen while feeding the programme in.
You always hoped that the programmer had updated the spare programme pack! I and
my shift colleague spent many a time reconstituting ripped punch cards after piecing
the bits of the jigsaw together. Problems always occurred at night, rarely when the
programmer was about with his or her notes! Computer operators had to know how to
take the various bits of equipment apart to retrieve ripped cards, etc. The knowledge of
card readers, punches and sorters became a vital part of our job. We also had to help
the engineers locate faults on the main frame. It was a tough life, it was another world!
See http://www.glias.org.uk/news/256news.html


Bill Jack

Roy Irons: Read More »

Bill Jack, English Electric Engineer (team leader) Ravenscraig LEO III, recollection.
The Leo III was acquired by the Colvilles Group Engineering Department on behalf of the
Ravenscraig Works. They had already installed the KDN2 on the Slab Mill. I was a young
engineer in the department and was sent to Kidsgrove to learn about the KDN2. When the
Leo III arrived I was put in charge of the implementation team because I knew about
computers! The LEO III was applied to production control/tracking throughout the
steelworks complex and also to the production of the weekly payroll for 4,000 employees.
The LEO III continued in both roles from 1965 till around 1972 when it was replaced by an
IBM 360.
The most interesting feature of the installation was the extensive use made of Lector
documents to record information directly from the operatives at the various processing points
throughout the plant. These documents were collected at the end of each shift and processed
in time for the production meetings at 9.00am the following morning.
You do correctly identify the tussle between the Finance and Engineering Directorates but
this was resolved by the Finance Director purchasing an ICL 1900, installing it in another of
Colvilles steelworks at Clydebridge and proceeding independently. This did not impinge
upon the installation at Ravenscraig.
As a result of our conversations I have been in contact with members of the original LEO III
32 team and will put together a short record of the installation and the applications. This I
can forward to you if of interest.
Bill Jack

Bill Jack: Read More »

Helen Jackson (nee Clark)
Born June 1936 in Wigan, I was the youngest of 3 daughters to a manager at the local coal
mine.
At the age of five I was sent to a private preparatory school, to which even at that age I went
by myself on two buses each way. From this school I passed the 11 plus and went to Wigan
High School for Girls.
That same year my father died from heart attack; my mother never re-married.
In my penultimate school year, on a school trip to France I had to make a speech in French to
the Mayor of Paris, thanking them for their hospitality, which I can recite to this day. In my
final year I was appointed Head Girl
After my A levels in 1954, I went to Manchester University, and graduated in Maths in 1957.
I went for job interviews to English Electric, Vickers Aircraft and LEO. I liked LEO best,
particularly the job Appreciation Course, which in those days was a one day elementary
programming course and tests on it, with the interview coming after the test results were
known. I thought ‘I can do this’, and joined Leo in September 1957.
My sisters were by then living near London, and my mother had decided to move South
anyway, and did this soon after I joined LEO.
After my programming course I was put into the programming section managed by Jim
Smith, which had about 15 programmers working mainly in technical and insurance
applications. I worked on several of these, on both LEO I and LEO II, and was rapidly
promoted to be a Senior Programmer.
In 1959 LEO moved from Elms House, adjacent to Lyons head office at Cadby Hall, to
Hartree House in Bayswater. LEO needed much more space for growth, for both
programming work and computer operations for service bureau and computer customers.
In 1961 I was given responsibility for all service bureau application programming, and raised
to management level. At 24, I was told that I was both the youngest person and the first
woman ever to achieve this in the whole Lyons organisation.
Also in 1961 I married Mike Jackson. We had first met when Mike, also one of Jim
Smith’s programmers, was giving some of the lectures on my initial programming course on
joining LEO. After that, we had had very little contact until the autumn of 1958 when all
London Transport bus drivers went on strike, which lasted a few weeks. One lunch time a
group of us were chatting about the effects of this on them, and I told them that I had to walk
over 3 miles each way to and from the station to get to work, unless I could thumb a lift from
a passing motorist. Mike offered to take me home that day on his motorbike, and this led to
him taking me regularly to and from work for the duration of the strike. A strong
relationship soon formed, which has lasted ever since. We will be celebrating our Diamond
Wedding this year.
Mike was a keen racing dinghy sailor, and from early 1959 I crewed him regularly, in boats
he had designed and built himself. We won many races, including regatta trophies, and
were 3 times National Champions in the Class.
Following my promotion in 1961, the work for service bureau programming steadily
increased. Initially, Hartree House had LEO II/5, with a drum, magnetic tape, and very fast
printers. These latter items made it much more capable than LEO II/1 at Elms House, and
much more service bureau work could be taken on. Later, LEO III/1 was installed there,
many times more powerful than the LEO II, and my department was steadily expanded to
meet the customer workload that the greatly extra computing power enabled. Eventually I
had 53 programmers working for me.
Service bureau programming was where most new trainee programmers were placed, some
proving to be of high calibre, and I was delighted that they came through my department on
their way to better things. Noteworthy were Mike Daniels, Jim Feeney, Dick Peters.
However, all good things come to an end. I this case, it was with the arrival of our first
child in 1965, after over 4 years as Service Bureau Programming Manager. I did not return
to LEO, although after the birth, Mike asked me to write the programme for the largest and
most complex job he was planning for the LEO 326 installation he was managing. This was
written in CLEO for the handling of the accounts for a very large mail order company, which
came to be handling over 300,00 agents and individual accounts of over a million credit
customers. (Editor: that was the London Mail Order Company which Mike later joined. See
Mike Jackson’s own oral history). It was very successful. We had two more children, in
1967 and 1969.
By 1978, I decided that I would like a part time job, and started as bookkeeper for a small
nearby firm in the building industry. When there, having told the boss about my time at
LEO, he got me to use Atkins Computing, a service bureau in Epsom, to do structural
calculations for some design work. This was followed with his purchase of an Apple II in
1980, my first introduction to personal computers. I was pleasantly surprised at how
powerful it was, and after machine code on LEO II, what a flexible language Basic is. I
stopped working for him in 1981, when I started teaching.
We had sent our daughters to an independent grammar school. At a parents evening, in a
chat with the headmistress I told her of my time at LEO. This resulted in being asked to
introduce computer studies into the curriculum, and I taught it for 5 years. Some parents
came for word processing lessons. During this time I put the staff payroll on to a PC,
paying them direct into their banks, using a BACS file sent over a normal phone line. This
was very early days for using a PC for that kind of work. But when the school accountant
was due to retire, I was asked to take on that job, where I put the school accounts on to a PC,
including parent billing. I was in this position for several years, only retiring in 1995.
After that, I did various stints of unpaid voluntary work, including for a local Citizens Advice
Bureau, a toy library, and as a classroom assistant at a local primary school

https://www.dropbox.com/scl/fi/7wxh6koaq45ankayv3b4g/Helen-Jacksonhistory.docx?dl=0&rlkey=289bn2bg4bsqw2jd0czs2ydrh

Helen Jackson (nee Clark): Read More »

Paul Kelley
I worked in the Engineering Training Department July 64-August 68 – first at Minerva
Road and then at Radley House in South Ealing. I began on LEO III (never worked on the
326 or 360) until switching to System 4 in early 65.
I have in my possession a complete set of LEO III logic diagrams and microprograms. In
2013 I began documenting, in extreme detail, how the various subsystems within LEO III
operated. I had available to me the original text of my 1964 notes (and those of others) to
assist me. I was intrigued as to whether or not, after 39 years, I could still do it. By way
of illustration, attached is a Word doc of my efforts on the Coordinator which I ran by
Tony Morgan in December 2013. It won’t be too meaningful as there are extensive
hyperlinked references to the logic diagrams and other documents.
Also attached is an image of my folder structure. I include this in order to point out that
EVERYTHING I have has been scanned (1.5gb total) and to draw attention to the Orig
Text folder which contains all my notes of 1964 vintage for all the LEO III subsystems.
In sum, I think it would be appropriate to have a discussion with someone as to how best
to dispose of all the above so as to ensure that it is not lost. Some of it may be redundant
as it may already exist in the ‘archive’. Given that I am now 80 and the sole carer for my
wife, time to indulge oneself in this project is at something of a premium and whether I
will be able to finish the project problematical at best. In light of these circumstances I
would be happy to send a memory stick with everything on it and take advice on how best
to proceed with the hard copy versions

Paul Kelley: Read More »

Mike Josephs: Beginnings
This is in the nature of a bit of self – indulgence. I want to talk about my early days in the
fledgling computer industry back in 1957 and thereabouts. Before doing so I want to
welcome a new recruit to our circulation list: David Caminer, who must surely be the most
senior of us all, as he was a warrior in the Desert Rats back in 1942. His name, you can be
sure, will appear in what follows.
While the rest of you will probably have been doing something conventional, like medicine
accountancy or ordinary business, I joined a new subsidiary of J Lyons & co which had gone
into the trade of making and selling business computers. I will now admit that with my
freshly minted maths degree, I had hoped to join IBM but they quickly spotted that I lacked
the necessary skills in dissimulation to suit their style of operation.
To me the whole thing was like a job and a hobby and a high pressure trade school all
wrapped into one intriguing parcel, made all the more so by David Caminer’s role as king of
the systems and marketing areas. The business was so young, but he and his managers
seemed to know so much about everything. They were an incredible gang of people, full of
unexpected talents.
I never really understood how the whole thing had come about. We were given some briefs
on the company’s short history, and various names were mentioned in tones of awe, but we
were too busy worrying about where we were going, to concern ourselves with what was
already long past. Anyway I left LEO Computers after 8 years, during which it had been
merged with English Electric and Marconi, and effective control had passed out of the hands
of the original senior team.
So why am I suddenly rambling on like some old codger reflecting on the errors of his youth,
when as everyone knows I am supposed to be writing a deconstruction of the Financial
Ombudsman Service to submit to the Commons Treasury Committee? The fault lies entirely
with an authoress, Georgina Ferry, whose field is the history of various significant
enterprises. She recently published her latest entitled “A Computer Called LEO”, and to my
surprise it is very good indeed.
It is not just a picture of the exciting days of a new technology which in the space of 50 years
we have all come to take for granted, but simultaneously it charts the decline of a massively
successful family owned food business which could not adapt itself to the demands of that
new era. Although I encountered some of Lyons’ strange ways, I knew too little about
business elsewhere to put them into an overall context, but the book makes clear just how
feudal and paternalistic the whole operation was. When push came to shove, the youngest
family spriglet ranked above the most senior ‘employee’ director. And those senior
employees wanted it that way. They saw themselves as squires to the family knights, not
ambitious for themselves and devoted entirely to the family interest.
As a result, a degree of real humility percolated down through the ranks of the management
and was imbibed by the fractious juniors like myself. If John Simmons, hyper-competent
administrator and famed initiator of the whole Lyons computing enterprise, saw himself as no
more than a capable family servant, who was anyone else to put on airs and arrogance? The
contrast with executive culture and self promotion at the start of the 21st century could not be
greater. I suspect that many of those old Lyons managers (though not us LEO people) would
have fitted into Ancient Egypt without a ripple.
The Lyons company’s self-image was of an immensely competent enterprise which had
forgotten more about running food businesses than anyone else had ever learned. At its heart
was an administrative machine that kept rigorous track of every bit of raw material and every
hour of labour, and reported profit margins on a weekly basis. They, like the Marks and
Spencer of the same era, were always looking for better, cheaper, more effective ways of
doing things, so they found room for men of imagination and energy who would challenge
established practices and propose better ones.
Unfortunately, marketing, finance and business strategy were not subject to the same types of
intellectual discipline, but they were the fiefs of family members who reigned like Dukes
over major parts of the whole empire and whose word could not be gainsaid.
As I read the book, I came to understand the strange conjunction of circumstances that led
this food company into pioneering the application of digital computers to the operation of
major businesses, both their own and other businesses with forward looking management.
Simmons (also a Cambridge maths graduate) had come to realise that the process of
administrative improvement was blocked by the lack of suitable office equipment:
everything available up to 1950 was just too damned dumb, and needed the work broken up
into excruciatingly small stages. He realised that the new-fangled computers, just emerging
from the labs of leading universities, could offer the solution to his problems.
His solution was simplicity itself: offer some funding to the Cambridge computer wizards,
and in return get their advice and co-operation in designing and building Lyons own machine
which would be tuned to business work the way the academic machines were tuned to
scientific computations. Lyons and Simmons were even more ‘can-do’ than the American
Marines.
As I think about this unlikely set-up into which I so innocently plunged, I realise that even
today, after all the vicissitudes, some of my good friends date from that era: Frank and Ralph
Land, Alan Jacobs, and perhaps one or two more whose origins I have forgotten. I might
even include Robin Fairlie who made a huge success at Remington Rand/ Univac after David
Caminer refused to be persuaded by my recommendation that Robin be taken onboard.
Now the engine of this unlikely subsidiary was not Research or Production, but was indeed
the Systems Department run by David Caminer, who had learned his trade under Simmons in
Lyons own Systems Department. That is where I started as a humble programmer, learning
at the feet of people like Frank and Alan. These strange but clever people cared about only
one thing: ‘Did it work?’, by which they meant ‘Did it do the job we had promised the
customer?’ This was a very strange idea in the computing world of the day, where it was
taken for granted that nothing would ever work first time, and certainly nowhere near the
original budget.
But this was the philosophy of the Lyons people and we imbibed it from them like mother’s
milk. Neither intricate requirements nor unreliable equipment could be allowed to stand in
the way of doing the job properly. They were just obstacles to be surmounted. If you didn’t
know how, then ask. If no one knew how, then work it out for yourself. The product of all
this was a remarkable type of person, not so different from what you might find in a
university engineering department. LEO people were unassuming but intimidating in their
confidence that they could solve any problem that was capable of solution. And they proved
again and again that the confidence was justified.
Looking back, it is easy to see that what was really special about LEO was the systems knowhow, and that ‘attitude’. It today’s parlance we would say that they were without equal as
systems and project engineers, and however good the youngsters were David Caminer was
even better. Of course, he had the advantage of the right sort of basic training, which we all
skipped because there wasn’t time for that old fashioned ‘organisation & methods’ stuff.
That was the business that LEO should really have tried to be, but the directors had got the
computer building bug and could never throw off the habit. Other people picked up the idea
of systems consultancy and made fortunes doing badly what LEO could do well, but LEO
wanted to be in the production business as well, which is something that burns real capital.
Of course the mergers went badly, because the paternalist Lyons Board had cut their losses
and cut their ties with LEO with the ruthlessness that would make a 21st century capitalist
quite proud. None of the LEO directors even knew what was going down – they were sold
out without warning!
I always seemed to be dragged into the strategic errors that senior management insisted on
making, like setting up an operation in Johannesburg when we didn’t have enough of ‘the
right stuff’ to cope with the UK market. It was only when I read the book that I realised that
DC and I thought the same about that little jaunt, even if it did give me a year in the RSA.
Reverting back, to when I returned from South Africa, I had to serve a two year stint as
Caminer’s technical fixer, which was sometimes a non-job because he was his own best fixer
as all the rest will gladly testify. It also meant that I was under his feet a bit too often, which
was widely regarded as something to be avoided if at all possible. Anyway, as a reward for
sticking it out, and helping to get some advanced computers into production (something
which Georgina talks about while neglecting to mention me by name for some reason) I was
promoted into product planning in the Research Division, which I now learn from Georgina
was a bit of merger politics that was not expected to produce anything.
There I turned myself into a pale copy of David C. and ran around like a demented bluebottle
making enemies in all directions, but coming up with a credible scheme that unfortunately
was just a bit before its time. Meanwhile the real version saw which way the corporate
politics were going and espoused the proposal that the English Electric brigade wanted to
hear. Our work in Research wasn’t entirely wasted, because ten years later after yet more
mergers, it was incorporated into a line of machines under the ICL label.
That was about as close as I got to corporate glory, but as they say, it was a great learning
experience and helped prepare me for the rough and tumble of management consultancy. But
what I didn’t realise was how much of British industrial history in the 20th century was
encapsulated in the strange case of Lyons and its LEO computers. Do read Georgina Ferry’s
book if these things interest you at all.

Mike Josephs: Read More »

Professor Alan Kay
From Professor Alan Kay distinguished American Computer Scientist known for his work on Object
oriented coding and winner of the Turing Award in 2003.
I knew Maurice Wilkes slightly many years ago, Roger Needham years ago, and most
recently have met Andrew Herbert. The latter two had spent some time at Xerox Parc, and it
was Andrew who told me about your society after I mentioned LEO as a good follow-on
exhibit/story to TNMOC’s recreation of EDSAC. He also explained about the society’s
museum presence in Cambridge.
Still, I think having at least “a wall” at TNMOC about LEO would greatly add important
context to the larger story of computing, and especially British computing.
To me, there is more of an interesting parallel to Whirlwind development than to the IAS
machine (especially with regard to scope and software). I think the LEO software schemes
for the Lyons’ businesses were both landmarks and early, and deserve to be more told in some
kind of museum exhibit.
The ARPA and then PARC computer work was very inspired by both the big ideas of the
past and especially the amazing amount of work under difficult and primitive conditions to
not just think about software uses, but to include both the design and making of software and
hardware part of an integrated working practical whole system.
Still, it’s hard to beat the LEO story in this regard (I love it!)
I do know Dag Spicer, and others at CHM, and have donated various artifacts to CHM,
including a couple of Altos, and a copy of the original Dynabook cardboard model. In
addition, CHM is planning a “50th Anniversary of Smalltalk” for this Fall, which will
probably partially feature the “Smalltalk Zoo” (working versions/recreations of all the
Smalltalks going back to 1972).
A huge challenge (for a computer museum especially) is to provide actual explanations and
context beyond just exhibiting artifacts as static objects. Visitors are supposed to “keep
moving”, and there is little time or place to learn more (a partial exception used to be the Met
in New York, which had a great store next to a large cafeteria, so a visitor could buy more
context and spend an hour in the cafeteria learning more).
Still, for computers, what’s really important to understand about them is not actually shown in
a learnable way, especially with regard to software. And the shops are often very lacking in
this regard also. For example, a terrific little project at TNMOC is a valve flip-flop kit, which
requires one to put together and solder, etc. But there is no explanation of flip flops, their
history, and especially no explanation about how the kit itself actually works, or how flip
flops are an essential part of computers, etc.
I started to talk to Andrew Herbert because I found that I had one Alto left in storage, and that
the TNMOC had some interest in doing an Alto related exhibit. This got me to revisit
“context” in general, and to think about “more” in general. And this led back to thoughts
about earlier heroic computer projects, like Whirlwind, and especially LEO.
One of the nice and important properties of LEO is the wealth of documentation and detail —
although I gather that this doesn’t extend to the actual software that otherwise could be
resurrected via emulation. However, the wealth of early system planning and ambition is
priceless. Parc was almost the opposite in that, though the planning was pretty crisp, there
were not a lot of planning documents, but there are readable tapes of large parts of the SW,
and working Altos (also very detailed emulations including the microcode etc), with the
result that quite a bit of what actually got done can be demoed today. Very useful partial
exceptions are CSL’s minutes of the weekly “Dealer” meetings in which progress and
discussion were shared, and also the 6 month and 2 year reports (I wonder if these got
preserved somewhere, I didn’t take mine from Parc, and now wish I had). (LEOPEDIA
editor’s correction: All the manuals (except volume 2 CLEO) are digitised
at http://settle.ddns.net/LeoMan/Manuals.htm and there is a working emulation of the Master
Routine and Intercode Translator. Intercode programs may be written, translated and run either
freestanding or under the Master Routine. In addition we have listings of several customer
programs, mainly from London Boroughs, as well as a few CLEO programs.}
In any case, though I am mostly thinking about how more context could be shown about the
Alto, I can’t help thinking about what could be done with LEO’s history to make it more
understandable by the public (and I’m sure the LEO Society has thought about this much
more than I have). I’m certainly willing to donate funds to help make the LEO story more
widely known. https://en.wikipedia.org/wiki/Alan_Kay

Professor Alan Kay: Read More »

Frank Land (with Hilary Caminer) – Reminder of a celebration. On the 30th
November 2021 The partnership between the Centre for Computer History (CCH) and
the LEO Computers Society (LCS) with funding from the National Lottery Heritage
Fund celebrated the 70th anniversary of the world’s first live business application –
Bakery Valuations – by J Lyons & Co on their LEO computer at their HQ at Cadby Hall.
The celebration included the launch of the LEO Film made by Boffin Media with lottery
funding and available for viewing at …, , presentations by Peter Byford, Dame Steve
Shirley and Frank Land ….
The Film is intended for younger view to get an appreciation of the early days of
business computing and the pioneering work of the LEO team. To view the Film and
respond to a feedback survey please click on the following ….and send your own
comments to Frank Land for posting to LEOPEDIA.

Frank Land (with Hilary Caminer): Read More »

Ernest Lenaerts: Extract from his diaries on the occasion of Princess Elizabeth’s visit to
Cadby Hall on 15 February 1951, including a demonstration of LEO I performing test
calculations.
▪ HRH was no more and no less impressed than I had expected. The information “printed at
the bottom which provided some light relief. Fortunately LEO made few mistakes –
obviously not subject to stage fright and the Demo went off smoothly. A little more
interest was shown I think in the interior of the machine when she saw the complexity of
the circuits – how many of this machines like these in existence?
Only one other in working condition – No others on commercial clerical problems. This
auspicious occasion called for an enormous improve in general tidyness of the lab and I
must make an effort to preserve this. My own desk was clear for the occasion – the first
time in months. Work on the machine can go ahead again and I have been given a more or
less free hand to proceed on which problem I deem the best tackled first. The object will
be to bring the machine to full operating condition as soon as possible so that Caminer &
Co can get [[weaving]] on some of the programmes that they have kept up their sleeves for
so long. The first and most obvious fault to be cleared is the corruption in the Teleprinter
which I Think are due to breakthro in the output Unit. Other troubles to be cleared are
occasional “1”s being added into the store. These have the effect of spoiling all of the test
programmes received from Cambridge ” View the post here.

Ernest Lenaerts: Read More »

Stewart Logan, LEO III at Ravenscraig
Colvilles Ltd., Ravenscraig Steelworks
A Short Description of the Leo3/32 Production Planning & Control System
Introduction
Colvilles Ltd. Steelmakers installed a Leo 3 (No.32) in their Ravenscraig Works
in Motherwell in 1963. In 2021, Dr. William (Bill) Jack, leader of the systems
development team described in a paper to the Leo Computers Society the systems
developed and run on this computer. I was the lead analyst on the Production
Planning and Control system and was asked by the Society if I could provide
further detail on how Lector OMR techniques were used. I was not involved in
the concurrent development of the payroll system so my recollections are only of
the PPC system. This request was made nearly 60 years after we had acquired the
Leo and all documentation had long since been destroyed. We clearly did not
have the foresight to realise that what we were developing could be regarded as
pioneering.
Locating some lost information
Perhaps a word is in order as to how I managed to get a little more detail. In 1967
I had just got married and was working on draft drawings of a house I planned to
build. By pure chance, I recently found that one of these drawings had, on the
back of it, most of a flow chart of the Production Planning & Control system that
we had implemented. I think it is probably just missing 1 or 2 operations down
one edge so it gives a very good picture of the scope of the system. It is
unfortunately very faded and not really suitable for adding to the Leo archives. I
was able to pick up much detail of the use of Lector documents from it but,
regretfully, have not managed to trace any of the actual documents. This flowchart, however, enabled me to extract further information about the system.
Why optical mark reading?
The primary requirement of the system was to provide information as at 6am for
day staff who started work at 8.30am and for production meetings at 9am. This
was not possible to achieve using conventional data preparation.
Collection of order details
Lector documents were used to collect data on new orders, order amendments,
order cancellations and order completions. These documents were completed by
sales personnel in an office environment. This information was input to the
system run at 6am daily thus providing an updated order file.
Collection of steel movements and change of status
As Dr. Jack explained in his paper, for process scheduling reasons, it was not
possible, unless an order was very small, to move all of the material for it through
the plant together. However, by tracking the movement of every piece of material,
whether or not allocated to an order, the system could provide the requirements
of every order and the present progress towards order completion including
whether there was a shortfall of material for it.
Lector documents collected information on the creation of steel slabs, their
dimensions and allocation to orders and the coil of steel produced from each slab.
Thereafter, Lector documents were used to record every movement and change
of status of a coil. In later processing, a coil could be cut along its length into 2
or more narrower ones. Coils could also be cut into bundles of sheets and further
processed. Lector documents were also used to track material through these
processes. Where a coil was despatched to Gartcosh Works finishing processes
the tracking continued until despatch from there as either coils or bundles of
sheets. The data recorded on each coil or bundle as it passed through the processes
included a code for the process, any change to dimensions, any change to weight
and any change to grade (which resulted in it being removed from its allocated
order). A lector document was also used to collect information on surplus stock
being allocated to suitable orders. The tracking of coil and sheet bundles
movement thus covered all processes until the material was despatched.
The Lector documents were completed by recorders on the shop floor (see
appendix 1). The data was collected through a 24 hour period and input to the
Lector machines at Ravenscraig and Gartcosh. Trials showed that time was
probably insufficient to get the Gartcosh Lector paper-tape output driven over to
Ravenscraig after 6am. add it to the Ravenscraig data, complete the system run
and get the Gartcosh print-outs delivered all before 8.30am. A paper-tape reader
to paper-tape punch link was thus commissioned between Gartcosh and
Ravenscraig.
The system produced production reports for morning progress and planning
meetings at 9am. Additionally, order file reports were produced showing the
present status of each order so that remedial action could be taken if it was
running late or short of material. Lists were produced of the stock ahead of each
production unit to assist schedulers with their work and to greatly simplify
periodic stock checks. Subsequent stock-checks showed the system to be highly
accurate.
Analysis of the recovered flow chart indicates that there were 52 Cleo routines
providing vetting and files updating together with about 50 printed reports. There
were upwards of 30 sort routines. I do not have actual figures but there must have
been many hundreds of order and stock changes every 24 hours.
Development team
Initially, the team comprised about 9 personnel who worked on systems analysis
and the early stages of systems design. As work progressed, 6 of the team then
programmed the analytical work. It seems remarkable that the system design and
implementation was done by only about 3 systems analysts and 6 analystprogrammers using Cleo, which speaks highly of that language. The basic
tracking and reporting system was implemented in late 1965 by the team that had
only been trained early that year. However, continuous enhancements followed
in the use of all the data that was being collected.
Further development
Round about 1970, under a British Steel reorganisation, the Leo 3 was to be
replaced by an IBM 360/40. It indicates how highly the Leo system was regarded
that the suite of programs was rewritten almost unchanged in PL1 to run on the
IBM machine. This rewritten system which was implemented in 1973 still used
Lector documents for several years until replaced by on-line terminals.
Stewart Logan
November 2021

Appendix 1 – Design of Lector forms
Trial OMR documents were printed and tested out on shop-floor production
recorders. Most of the data to be collected was numeric; items such as material
identity, any changes to dimensions, weight, grade or anything else that could
change at any specific production unit. Alpha data was very limited and normally
restricted to one of several characters. The test documents had the particular
processing unit identity pre-printed on them. As most of the date to be collected
was numeric, each character of a particular parameter to be input was represented
by four, what we called, soup-bowls labelled 1, 2, 3 and 6. Thus, by filling in no
more than 2 of these soup-bowls by pencil, any digit from 0 to 9 could be
represented. Thus recording a material identity of 5 numeric characters would be
represented on the pre-printed form by 5 groups of these 4 soup-bowls. The
choices of the limited acceptable alpha characters were all represented by
individual soup-bowls. We were advised that shop-floor personnel would not
understand this. We argued that anyone who knew how to fill in a pools coupon
would soon master it. Trials showed that we were right. Subsequently, once the
system was implemented, we only had one failure – a person who was dyslexic.

Stewart Logan: Read More »