<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="9534" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://declassified.library.utoronto.ca/items/show/9534?output=omeka-xml" accessDate="2026-08-18T18:18:39-04:00">
  <fileContainer>
    <file fileId="6527">
      <src>https://declassified.library.utoronto.ca/files/original/75878e423ddb50b57f7176da3c59fbf5.pdf</src>
      <authentication>5650ba75342267cfcff02b8022e71f8b</authentication>
      <elementSetContainer>
        <elementSet elementSetId="31">
          <name>PDF Text</name>
          <description/>
          <elementContainer>
            <element elementId="131">
              <name>Text</name>
              <description/>
              <elementTextContainer>
                <elementText elementTextId="85958">
                  <text>Lt C o lWB* Finch, m.it cs f*C
P2, Canadian Forces 1
D

Document disclosed under the Access to Information Act Document divulgue en vertu de la Loi sur I'acces a /'information

ET

0 272&gt;t 1C $250 (B COM P)
Canadian farce*
Ottawa, nt.
Sap 6$

9

Leer //

1.
I barn seen your letter (GSPS 17u?/6$) dated 12 MX 6$ to Major
(now replaced by vajor 3haver whoa you have met). I head tho aoetlon i s
which tholr work l t dent*
2.
Share art certain problems associated with the operation of the U1LIU
^yatan which I will raise with you. If you art not the responsible authority,
I will be very sues obliged if you will redirect the queries and let ne knew
to whoa I should write in future*
ftjrMHHUi
• i iii

i iii ' »i

3*
The first prtblen is one of precedurea. the project to transfer the
telegraph relay operatioea of the Ottawa Traffic Centre from torn-tape
operation at UXTUM to the 3THAD at CARP raises some tiroeodura problems
w W W W P t

t"iw

g«aT^ptP^wsM8is awa* asMPss data asaiWa ^evav W s w

#aa*#»a^a SWjWPt^wwatat

asaa™^Mijp»a VeMRheitaffBBt

tWP

ACP procedures, art not identical and la particular require modification
to permit transit through aa automatic relay centre.
h.
Our methods and procedures people have made a detailed atudy of
this problast in aa attempt to adjust the HTDXA sreteisrs to the easential
atnlaaau However, we have concluded that the proper course i s to adept
ACP 127C procedure outright on this system. There are two reasons for this.
5.
tat first reason is tho necessity to ensure that traffic will
continue to flow even if the CARP relay centre ia out of action, tat only
alternative to the CAItr relay centre is one of the other military relay
centres ia Canada, tiniest ACP 127C procedure i» employed oa HTLRA, i t
will be quite impossible to pat* this traffic ia aa emergency through
teat other surviving relay centre. The second reason is that the diff&lt;
ia irooeduvea i t already causing significant difficulty in training tad
canning, and this i t aggravated when the mm relay operation occurs at
CAEP, which ia also tat Urinary Relay Centre In the Army network.
6.
I understand that It ia the long tarn plan ex osrs to
and rationalise jwaincci'it and Service* facilities. I
BfSaSJrtlSJtJ
that your future plans include automation of the relay
of Lcrjdon Traffic Centre aiid atslMBBJf analgia! Ion with
military operationa. aa doubt you art equally scustiuad to
alternate centre to handle thia traffic la the event that LTC ia put out
of service. Tou will therefore sacountar tils procedure problem In due
at your terminal, aad a change to ACP 127C prasaduru will be of
in tela. ACP 127C procedure la already la use by the
It ia designed for use with automatic relay

&lt;2:

; vv,

..•/2
1000036

�Document disclosed under the Access to Information Act Document divulgue en vertu de la Loi sur I'acces a /'information

r

7.
I will be grateful if yea will give me the British reaction to the
pi*ficcal to convert HtDRA to AC? 127c procedure.
1

• l i n n

W

I

M

I

I

H

I

point relates to traffic engineering aa the HJDHA
9m
B ceases no aa* authority hat direct Jurisdiction ever th* variout
message centres cr tributaries tad the relay centres, tnere caemt to bo
tedenoe*. there i t a procedure under which each relay centre lnfome'
th* ether if a message has been cr is expected to be delayed beyond c
apttificd time. I can find no agreement on overall handling timet how*
ever, aad we that Itch any basis for assessing system performance cr
determining the required number of circuits to matt apecifled speed of
1. Likewise we lack any quantitative survivability
10.
I am concerned at the high incidence of maatagat of rrasertawat
miOBXrr and above, which runs at about $0*. 1 think i t is apparent
that we cannot he giving true "priority** aarviee to half of the system's
traffic. I doubt that originator *a have a clear basis for allotting
iCMsdanaa in relation to th* desired time of delivery.
11.
If we ware able to agree oa overall apeed of handling throughout
th* system (cr at least between the tributaries directly connected to
OTC aad LTC) a* weald have a quantitative basic:
a. aa which to assess performance of the system)
b. with which to approach th* prcocrtsms ratio problamg
e. en which to calculate circuit scale}
d. with which to develop survivability standards.
12.
I attach at Annex A aa extract from car Canadian Army to«td of
service standard* which might serve aa a sample for farther discussion.
13.
I weald be glad to have th* British view on th* adoption of
of service standards for this cyster,

:r. v.J. Tiabberfleld
uwarnmsnt ttftal * leaning ...taff
Cabinet Office, London 8ml

, -•*--&lt;'

000
000037

�SBtaRET

•

•

Document disclosed under the Access to Information Act Document divulgue en vertu de la Loi sur faeces a {'information

V

AK&amp;3 A
TO 0 272&gt;2 TO $2$Q (L Comm P

m^Sm*
vtmam

9 If*....

or SJPVAL HOCTTCVL

.. .v. . -cc

- ;i i\l

..".

.

1 r: 11

iSL
1.
this chapter establishes t h * permitted handling times far wtttsgtt
on the CASS.
sjaaasassaai
III! I

MlT

2.
the overall handling time is the elapsed time from Time Handled &amp;t
at the aeeeag* centre of origin to the time th* neaeage ia ready la plain
page form for delivery to the indicated addrsesse(a).
the functional handling tlma it tht time occupied in a particular
processing area, such as the communication centre of origin, or a relay
or the siVhceaoe caneanlcaiien centre, the sue of the functional
handling times la the overall handling time* i* th* sua of the functlont
km
Par purposes of this chapter, a standard or average message ia
defined as having a leagtv of 120 groups 720 Hurray Code characters, or a
teletype U p e length of V inches (Including procedural and textual
On* group consists of six hurray Code characters including space. Tea
groupc occupies six inches of teletype tape.
' "-r-r , y-„"M/, •£]&lt;:...,:•*&gt; TP ,,
£•

Haaaagae shall be handled within the following overall handling times»
a. Abac* PUORxr? * as quickly as possible tad act more then JO mlnutcc)
b. PBIOSItT • 2 hours)
e. ROCTUiC - ©* hours.

6.

The permitted overall handling time will he extended i
a. by Lo aUaite* per 120 groupc when "off-line" encryption it involved
(this include* encryption tad decryption) |
b . by 12 minutes par 120 groupc above the standard massage leagthf
this sllowance ia divided into 6 minutes In tht originating
lieatlom centre aad 2 minutes per relay centre}
c by the permitted time par relay centre when
than three relay centres la required.

ET

*mw/*

000038

�Document disclosed under the Access to Information Act Document divulgue en vertu de la Loi sur I'acces a I'informati

§:
ate

a/
7.
To most the Shove permitted overall handling times, the following
that l i m i t s by functions shall he aott
TSatlXKaL

&lt;* mil i

a.

mmt

n

Ie

w!

. n i Yflfifmuih

i.. ••••.*;'»'•

Above
ID mine

b.

V^i

ftUOBXTT
"' "

5 mlns

2$ mlns

30

5*| hour©

60 miaa

3D nlat

5 alas

&lt; ajfji

2 hours

30 mlns

6 hou- s

8.
the permitted times include time awaiting iwatiattliif cr
aa wall aa th* actual processing and handling t i n e .
9M
j •

Bel j-rr^'tt-oc ftasajfl Baa Bad a M s j |a§aja. la | -xmt »... _« &gt; r aaajaj
eeaawm aroma•ee»»»^^m'

**w*w

wma w

eessFw mmw •

r

waenwe

a#a»w m a ^ m v

mp^

MSPS

es^w

mww a t

J

whether handled during peak or off-peak perioda.
10.
th* parmltted timet art maximua allowable times) every effort will be
to pass traffic in the Shortest peaslble time.
11.
^a*ess# «s

Delivery of sessegss should be affected ia the atms order of time §M
^wea*aipe^^m ms^m mw ^mmm v ^ ^ m vetfSwseMaai

Jr^s* aira^^me^aPeBteiBp

east

m

Mfmwmw ea^^msa. a^^s^a.^^ma

asa^iai^aasa^tepss^Baasaassts.

a^^asiast a t

unleaa t h t Headquarters Staff concerned rules otherwise (for example,
ragardlag Routine massages after office hours).
12.
atem six precedence system la encountered wmmmCi mtassgas w i l l be
subject t o the t i l i n g s for FLA i,
\L OtHBBim messages w i l l be
cab Jest t o the timings for ZJMSDXATS, sad BgfSPJttD naaaagea w i l l be subject
to tho timlnge for BOuTUtS*
ACT10B W PSFAUL,t
13*
If the permitted time for a particular message i a say of the functional
pros eases (eg cemeen of origin, relay centre) cannot be met, the o f f i c e r - i n w i l l enture test the following action Is taken in the order indicated t
a.

cheek whether trery pessihls mesne within the available amnpewer,
equipment aad circuit roaaurocs hat bean exploited)

b« notify tht originator or headquarters duty officer (where practicable) of the Bjasfsaassasd iafean asxi aoey saaaaapifea fee
w^wew/

te

w^

mmtmymw mm*m.mmf:ewa:^wrr«

^waaasagf

mmwm mrwmnsh W » J W J » J i " ^

Vis

ar upgrade the .rosadsmo aa appropriate t o the situation)
If c i r c u i t s are unavailable ar disrupted, follow the ^msadura
set out la para l &gt; . b lew.

S E h a f i E T

'

'

•

« *
1000039

�Document disclosed under the Access to Information Act Document divulgue en vertu de la Loi sur faeces a {'information

e&gt;
d.

:

:

i f i t i s considered probable that recurrences of the problem
are l i k e l y , report the matter with i nnrauainrtaUuiai through
acraal chaanalt t o D Sigs*
'-••-'•

:

qi

li.
Functional Processesi Officers la charge of message centres and
relay centres will he responsible for monitoring performance to ensure
that the permitted timings for each functional process taf met. If the
prescribed timings cannot he met la a particular rococo, the case will
be reported to D Sigs through normal channels with racasaeaaaticaa for
a solution.
15.
overall flandllnc timet in addition, officers In ehertre of
message centres will be responsible for monitoring the overall handling
timet of received masaagea. the fall owing action will be takem
a.

mio.'il?? aad Above - If overall permitted handling time is
exceeded, report through normal chanml* to 0 Sigt by Boutins
nseeeg*) Vitiate traaar action If the message orirlnsted at
a Caaadiaa Army messsge centre) and report result of tracer
action to D Sigs through norms! channels by Houtine ncesagC)

b. BOOTHS meaaagaa - if overall permitted handling time It
exceeded, record ssaaag* identity and office of origin,
tabulate for each originating message centre, sad submit
normal channels to D Sigs by 7th of the month for
MBSSAQL HABuLIBO WHS*
B08HAL AID ALtKHBATK KEAH5
16.
Waaaagss w i l l be heaaUsd as follows whea awaiting transmission
(Traaaaiaaica waiting Tin*) over a c i r c u i t or chswasl due t o the acraal ar
being unavailable, disrupted or unsuitable:
Wattsgtt ar prasartantt shove Priority w i l l be handled l a
with Annex *AR i o i h i e c t f p t s r .
b.

Priority me testes w i l l be referred hack i t th* Originator
or Duty Officer after 30 mlautee TraatmltsJca S i t i n g That
t o inform him of anticipated delay end seek confirmation of
assigned prs**n*nt* c r permission t o hold.

c.

Routine wastages w i l l be refonod back t o th* originator or
Duty Officer after li hours Transmission S i t i n g Tims t o lnfora
him of antlelfatcd delay aad seek eonflrmatlon of assignsil
c r permittioB t o hold.
Unless otherwise directed by th* Originator cr Duty Officer
w i l l he handled In accordance with Annex "A" t o t h i s

5S

••«*•*.
• 000040

�Document disclosed under the Access to Information Act Document divulgue en vertu de la Loi sur I'acces a I'informatic

SB&amp;R

jpo.

#

EUSTXNQ

cxac'fT

mmmam

Service circuit
dosed, but
available

service circuit
not available
due disruption
far beyond
leased hours,
Con^ercial
office at dec*
tlnation or
relay open.
Service circuit
not available
daa disruption
ar beyond
leased hours
commercial
office at dlatinatioR or
relay closed.

mmttum

MM
Telephone Duty
officer at dee*

Sgaa a* far FLASH

mmm
fame a t for FLASH

mmfttm
old until
aarviee circuit
....

supervisor, sat
pact uaCLAS cr
short crypto
mctaage verbally)
request service
circuit open for
long massage
Immediate connerclal ref l i e .

Same as for FLASH

Cosswareial ref U s
within 2 hours

In a l l sets* where messages are massed by telephone,
e copy is to be patted en tht service circuit, wham
i t re' erase, with a pilot shewing telephone action

Ref l i e after 12
hrs. (SAT. to
HO** morning
aad statutary
holidays
excepted).

feajajaja

Tslsphcne Duty
Officer at dee-

Same aa for FLASH

tinatlon or
supervisor at
the relay and
*eas all
messagea (CBCLA3
ana
crypto/
verbally.
M^^^jmu A B ^ « ^ A A ^

ruaaautlal ref l i e
within 2 hrs If
possible. If not
possible pass by
feaasj ag g*y

rum.

1

CaasBBntaal
ref l i e after
12 hre i f
poaclble,
(Sat. to Ken.
•aaiai ssaj
statutory holliaai |ajM| feBi]
or hold until
commercial or
service circuit
- *

«0T£t

dban s i x prsssrtsncc system encountered, t r e a t BWgajBaCI as for PL
OrgBATIOhAL imSilATZ aa for 2HH&amp;DIAT&amp;, aad DISFlSBJffiD aa for JIOUTIBV.

SE&amp;&amp;ET

1000041

�Document disclosed under the Access to Information Act \
Document divulgue en vertu de la Loi sur faeces a /'information

-ATLANTIC TBBXIBAL CABP
17*
stMn disturbed radio conditions are ai*wart area* on th* RTT t r a n s a t l a n t i c c i r c u i t , CARP Comcon w i l l eead the following aaalat priority
Idrasaed t o Coaeen Army Ottawa, Comcon SBP Ottawa, Coatan Caaa
Ccaaen
. once* Q3S00*- and Comcea SA3COH
TOTOSD RADIO COBDIT10BS SBCOufe, . .
?! I GSB OtAtl Oft DUTX OFfSBal HOI OOBFUaUtTOI OF lIstsT-teW Aft? ! BSS; G ..
FOR iCUJTb CUTSIDfi CABADA AMD USA PCISTWO OUT CCWgRCttL RSFILS SPSBSS
lWOW:. .
ILL AD»I35 *iISH RAL'IO COIDinoiB RET0R8 tD BBRHAL UB3BQTS.
1 .
After the •eeeage referred t o i n para 17. above baa been t e a t ,
the transatlantic terminal CABP w i l l automatically take action in
acrordanoa with th* trcaadare act out in Annex "A* t o t h l t Chapter, aad
rafarence back t o the Crlgiaatcr cr Duty Officer w i l l he the s o l e

responsibility of the Coseent notified.

af* K?i

T

000042

�</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </file>
  </fileContainer>
  <collection collectionId="72">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="71973">
                <text>Hydra</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="82203">
              <text>HY00285</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="82206">
              <text>[Hydra system problems] </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="82209">
              <text>09/09/1965</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="82212">
              <text>Fixed Communications - Hydra Telegraph Relay System - Relocation of Hydra - Plans and Policy, RG24, S-2723-2, Vol. 1, Library and Archives Canada (LAC) </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="82215">
              <text>Department of National Defence</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="82218">
              <text>Canadian Crown</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="82221">
              <text>Emergency planning, Emergency communications, EASE, STRAD, ACP 127, standards, procedures</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="82224">
              <text>Letter from W.H. Finch to V.J. Habberfield, Cabinet Office, London, pertaining to several issues with Hydra system for resolution. Issues include changes in procedure to meet ACP 127 requirements, lack of central authority for traffic engineering, and lack of agreement on handling times. Finch suggests Canadian standard for message handling times be implemented. </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="82227">
              <text>Canada Declassified</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="82230">
              <text>Text</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="82233">
              <text>PDF</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="82236">
              <text>en</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
