<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="9675" 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/9675?output=omeka-xml" accessDate="2026-08-23T18:01:04-04:00">
  <fileContainer>
    <file fileId="6724">
      <src>https://declassified.library.utoronto.ca/files/original/77fb01065fbc0819f4db1123061f2c50.pdf</src>
      <authentication>c14a7053f08bef0e8e04c60ee9f1b697</authentication>
      <elementSetContainer>
        <elementSet elementSetId="31">
          <name>PDF Text</name>
          <description/>
          <elementContainer>
            <element elementId="131">
              <name>Text</name>
              <description/>
              <elementTextContainer>
                <elementText elementTextId="86152">
                  <text>Document disclosed under the Access to Information Act Document divulgue en vertu de la Loi sur faeces a {'information

ISlSRAKDUIi
$

2723-2 (DCRS)
L 2733^316/706
L 2?20-ii$QG/G0
DCK2«2

2 6 August^ 1966

SYSTEM CHANGES ~ ONTARIO AND HSDRA
J » I — upwiII •

i

i. mi t i mi • w f f i | T i - - r - i - " i i i i n

TITT

-—--[

• • -|

—

!«,
The following points should be followed up with HQ CFCS SJ&amp;
developing the detailed pl.sias to ftaples&amp;xt the decisions of the aieet^isg
botweoa Comd CFCS aisd staff ,4 DCRS and A/DCE oa 22 Aug 66 regarding proposed system change iavolvJag the Torcato-Tfsaton coarplet aad. tho
Rockcliffe TRC*
2D

i t M&amp;S agreed a t 17a nestings
a . that th® chafiysa Sa the ?Qreat&amp;*&gt;Trentc&amp; ceroid: (CFCS pro- pjsal ef 10 t.-m 66) ere agreed in principle, oubisct t© eea*
siderut'jca c./ certain pointsj
b« that t&amp;e c h / ^ e s 5ja tine Ottawa area will nefr have the p^Siaasy
a&amp;3 of reliovicg tho lead ea Rockcliffo aad the secondary aia
of 3xapre«ri;i t r a f f i c Htzu

3o
I t ie access?/,'/ to takQ Sato eeceaat certain proposals v&amp;ich HQ
CFCS i s developing r-tjardSEg tho KaatreaX area e You should offset l i a l o s a
tilth HQ CFCS to pax't.oipate in this pl£im$fig9
he
HQ CFCS-also i s caaaidor&amp;ag sense cfesages ia BritSfih Colw;baa&lt;»
Here ©gala you ehoall get Involved i a their plasaiag, oo that tre l e s s KO
time i a processing t i 3 project*
5»
Sfeese ore -Ms.': ©aly plsao for system changes Hhich EQ CFCS io eeaelder 5ng sm» . I t i s deaSrable that they a l l bo brought out for ©oamination
by DCH32, DCHS3, anc" DCE so that HQ CFCS doss not proceed too far /tfith plaaa
before c«aaulttT3g Gff 3,*
TORCMO-TRBKTOM FLAK
. g w w w c •%iiiiMia»M^m'i!»nm*iii»nwnwii»wwa«wpfci&gt;

6«
Th© l i e t of ' t i r e o l i s which n o s t b e t&amp;cluded oa t h e BORDER TRC i a a t
Aaaest A*
7«
The HQ CFCS jvopceal (CFR P&amp;gaa 7«*S) establishes a Kecd for thro©
circuits betsjeaa B O M 01 aad CAR?„ It proposes that tho ceisaeeted RTT
circuit be counted as one of theoe,. This is n#t agreed^ tse ohsald proride
a third leased circuit (leace period to b© adjusted if not seeded cs 2U/7
basis - Esybe 12/£ wcVJ.d d©)«, Our ctncqpt ef th8 use of cesaected RTf
circuits is that they r.upply iinasdiateXy available redendant capacity,, so
eoo.

�Document disclosed under the Access to
Document divulgue en vertu de la Loisur f

that in the event of loss of one of the leased c i r c u i t y there is
Insaediate capacity available on the connected RTT circuit to carry
the traffic of the tnlflsiag circuit nut51 yet another RTT circuit
can be patched onto the terminal equipment nonsally used on the
missing leased circuit a Thus on the mill trunk routes there i s
alt-iays one connected redundant RTT circuit available to carry the
traffic of any .faulty, leased c i r c u i t . In the former Army network
there are usually three RTT circuits t one of 'which ia connected t c
the TRC and the other two terminated a t circuit control ready for
patching&lt;» (Note? There i s no objection to using one or wore of the
RTT circuits for live t r a f f i c in order t o eajercise them, as long as
the concept of one spare circuit is maintained )&lt;,
GgggaftL P0BJT5
80
Routing Doctrine? The previous individual network routing
dcctria^"~ca21eQ "for transfer of traffic to a connected network a t
the point nearest the originator. This rule a i s e t i l l applicable^
could result ia overloading of a particular network if a amaber of
aew tributary responsibilities are sieved to i t from, another network,,.
I t has been intended to adept a universal routing systera fer the
CFCS' n^work to eliminate this© HQ CFCS were sot sure at the -meeting
whether the universal systssi was yet implemented,, because of lack ef
OLC on the fenaer Array network* but they believe the rule about transfer
e-f traffic has been lsaiveds This taust be followed up t o ensure that traffic* in the network i s normally routed on the optimum path, rather
than on an a r t i f i c i a l l y ^ ictated path* This must be confirmed before
any changes can be implemented,
9©
I'^aaingg The. application of tneas-ared scales to the elesseais
of the system involving oreargency government wast 'take account of
exceptions (additions) necessary.to handling the extra load of REGHQ,
FBRC, RDRC and ZEGHQ loads* There is no l i s t i n g ia the CFR of circuit
loading under emergency conditions© I t is necessary to include this
so that i t is not l o s t sight ef0
~Q*
Cirguit^Ut 51iaationi Page lli^ para 8 S 8 of t h e CFR assumes t h a t
an automatic TRG can achieve almost 100$ c i r c u i t u t i l i s a t i o n . The a c t u a l
f i g u r e , based on IB experience^ i s %%„ In t h i s p a r t i c u l a r case, the
proposed 3eale i s adequate even with t h i 3 lower assumed u t i l i z a t i o n *
'il»,
^ Spare TRC positional The available number ef-spare TRC c i r c u i t
positions t o provide for tape change and maintenance needs rechecking
because t h e r e a r e irore Emergency Government c i r c u i t s t o be considered
(see Annex A)., I t seems reasonable t o assume t h a t t h e "redundant
capacity RTT"-Circuit positions on t h e TRC can contribute t o t h e spares

available for this purpose on a practical basis,-as long as their'use
for this is. not of long duration (say 1-2 hours) aad as losag as not acre
than 1 or 2 are so 3CH&gt;sitted a t any one ttoe„ We need t o establish a
target figure for f u l l y spare positions for such planning^ t h i s
obviously depends on the also of the TRG* Spares are needed for each
speed of circuits

O.O.a,

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

•

12j,
Consultant*s Flan; It i s necessary to recognize that the
Consultant Etust prepare a phased iBtplejnentatioa plan,, This tneans he
i&amp;ust be kept informed of changes sade in the systeraa DCRS has directed
that our proposed changes be referred to the Consultant t o obtain cosfir.iaation that they will sot inhibit installation of new equipment
later under his Plan., and to ensure that his implementation plan takes
account of the current configuratioao This can be done by a simple"
diagram showing final arrangement, with brief notes of charges made* *
Do Toronto area one not? « do not wait u n t i l Rockcliffe plan finished 0
^o
FDX~HDX: The use of HDX circuits imposes difficulties in TRC
operation,. I t ^as agreed that DCRS2 Hill support FDX circuits in such
cases (eg CLINTOM &amp; CSNTRALIA)•
•~-k»
ISIlp".* ^ e u s e °% ^ E X £ ° r delivery and for ccssaercisl r e f i l e
is soimd"aSair. agreed in cases xrhere survivability is not necessary
(eg to serve tributaries or customers in a target area. However,
T3L3Z switching centres are usually in target areas, and therefore TELEX
is not satisfactory for delivery or ecisnsrcial r e f i l e service frora a
TRC THhich has an emergency r o l e .
10o
NOMENGIATURB; It has been agreed that Coma Sqn aarees or nuirihers
•will NOT be usexT^oTrefer to TRCs, isessage centres, telephone exchanges,
or stationso The geographic location will be used* Examples are BOKDEH
TRC| BORDUM COMCEH3 CARP* TRC* CFCS STATION CARP? CARP COKJEMj CARP
CRIPTOCENj OTTAWA TRC (CFHQ)* OTTAWA COHCEW (CFHQ)* e t c . Where the addition of the HQ nomenclature w i n clarify, i t isay be added 7 an
brackets« Our systeia diagrams are to be amended to confers %he&amp; next
issuedo References ia CFRs are to conforra.
16.
RCN Sequence^Selectors- The RCMf network employed.a sequence
sel eetor'oB the 'Otta^ia^saacouvar leased circuit, xfith the aiis of
exploiting this c i r c u i t ' t o serve Havgl Divisions 0 This.should be
reviewed to determine present status"(noting eiiraiaation of soae ITaval
Reserve-Divisions under the recent reorganisation of Reserves )„ I t assy be
that this sequence 'selector needs rearrangement * This should be i n vestigated and a reeowaandatioa included in the plan.

\-fjU Finch
Lt Col
DCRS 2
2~Oh70

000257

�Document disclosed under the Access to Information Acm
Document divulgue en vertu de la Loi sur /'acces a I'inforn&amp;ion

AKKEI A T O L 2723~-2(DCR3)
L 2733^316/708
L 2720»a500/00
DATED % August, 1966
BORDEN TBLSGRAi^ RELAY CENTRE
CIRCUIT COhgTMEHIB

•naiMK imcuns
la

C'IBP

(SMITHS FAJIS) TRC

2*

CARP (RENFREW) TRC

|,

CARP (RTT) TRC

/.

VADCARTIER (SF) TRC

5«

vAICARTISR (ES8) TRC

6„

VALCARTIER (RTT) TRC

To

SHILQ (SF) TRC;

8.

SHIM) (REN) TRC

9„

SHILO (RTT) TRC

10* FORT RILEY (Leased Circuit) TRC
11* FORT RILET (RTT) (Hote: Prefer TRC connection rath.\--jjan patch)
I2 a CCB BATTLE CREEK
13* DOT MJSKDKA (Confirmed as requirement with EH3/D0T on .'•« 4vg (-&amp;)
mszsmsa: GOVT TRIHS
Ik,,

ECMP OWEN SOUND

1$.

RDRC ORILLIA

16,,

ZEGEQ FT WILLIAM

17.

ZEGHQ SUDBURY

18 a

ZBGHQ BARRIS

19 0

ZEGHQ L0NDOJJ

so of£

000258

�£

mt

20»

ZEGHQ BELLEVILLE

21.3

ZEGHQ ROOTM/iJOHaMDA

22.

ZEGHQ GUSLEff

23&lt;,

ZEGHQ PETERBOROUGH

«*

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

DHD TRIBS
2Xu

CFEHQ (DM) 1 1 3 1 0 ) PETAUAvJA

2$e

CFEHQ (RTT) PETAVJA1JA

26&lt;&gt;

TRENTON ( L e a s e d C i r c u i t ) TRC ( v i c e KINGSTON)

27c

TH3NTON (RTT) TRC (vice KINGSTON)

28*

LONDON (leased Circuit) TRC

Z9o REGHQ Coacea
30» REGHQ CoEcen
31o

REGHQ Gryptocan

32 a

CAMP BORDEN Coacea

33*

0AK7ILLS TRC((Leased c c t )

3ho

OAKVILLE TRC (Leased e s t )

3$o STA DOWNSVJEW BASE COMCEN
36 e

1 SD DCvJHSVmr

37e

Spare position, (paper change and maintenance)

38&lt;, Spare p o s i t i o n (paper change and raaintenance)
39o Spare p o s i t i o n (paper change and naintcnance)
Notes

Io
2.

C a s e d RTT LONDON - BORDEN
Cancel RTT 0AK7ILL3 - BORDEN

000259

�</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="83892">
              <text>HY00332</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="83895">
              <text>System Changes - Ontario and Hydra </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="83898">
              <text>08/26/1966</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="83901">
              <text>Fixed Communications - Hydra Telegraph Relay System - Relocation of Hydra - Plans and Policy, RG24, S-2723-2, Vol. 2, 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="83904">
              <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="83907">
              <text>Canadian Crown</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="83910">
              <text>Rockcliffe, telegraph circuits, landlines, CFCS, Borden, Carp, emergency communications, radio communications </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="83913">
              <text>Memorandum from W.H. Finch to DCRS2-2 pertaining to proposed system changes to Toronto-Trenton complex, system changes due to a heavier traffic load at Rockcliffe, and changes to improve traffic flow at various army trunk and tributary stations. </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="83916">
              <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="83919">
              <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="83922">
              <text>PDF</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="83925">
              <text>en</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
