top - download
⟦a007a893a⟧ Wang Wps File
Length: 5068 (0x13cc)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN75.00«
Derivation
└─⟦d10d3ed68⟧ Bits:30006014 8" Wang WCS floppy, CR 0055A
└─ ⟦this⟧ »~ORPHAN75.00«
WangText
1981-05-08 gj/rt
to: shnmo division
att.: mr. paul f. shey, contracting officer
cc.: lt. col. manfred stoltz, camps program manager
fm: christan rovsing a/s, denmark
gert jensen
our ref: cps/101/tlx/0245
subject: cr's response to dn's on the integrated training plan.
-----------------------------------------------------------------
references (a) integrated training plan, CPS/PLN010,issue
1
(b) shapes dn's to integrated training plan
(camps log 184)
(c) camps log 191
in the following references are made to dn's as listed
in ref (b) and (c) msg.
1.a. installation dates:
original installation and integraton schedule is not
changed due to the integrated training plan. cr suggests
a revised plan for the training of the resident site
technicians and regular technicians which will cut
to a minimum the period between completion of the course
and psa of he respective sites.
1.b. rst - training:
replacing the integration and test part of the rst-training,
refer to table 4.3.4, page 31, cr suggests the following:
the length is reduced to 7 weeks, following the original
planned 7 plus 3 weeks, frming a total rst course of
17 weeks, equal to 4 months. The last 7 weeks are then
based on extended hands-on training, using a preliminary
OJT-package and intensive system trouble-shooting.
to obtain better coordination of psa and rst training,
he 3 courses are held during 1983, 3 x 4 months, according
to the table below:
rst 1: jan.3 - apr.30
rst 2: may 2 - aug.26
rst 3: aug.29 - dec. 22
holidays will cut into this schedule, but lost lessons
will be added through the courses to qualize the training
for all students.
this schedule may conflict with scars training of instructors,
so cr would like an evaluation.
it is cr's belief, that the change in the rst training
will meet the requirements, and that started goals
can e reached within the schedule now outlined, using
intensified training methods during the last period
of the training.
furthermore, cr would like to stress, that the technician
training has been expanded from 5 to 7 weeks as presented
in ref. a dcument.
it is our opinion that the changes proposed in the
technician and rst training programs will meet the
stated objective i.e. giving sufficient training in
maintenance of the camps equipment at site.
1.c. initial technician training:
cr uggests, that the first 7 courses are held during
1983, according to the table below:
course 1: jan. 3 - feb.18
- 2: feb.21 - apr.1
- 3: apr.4 - may 27
- 4: may 30 - jul. 15
- 5: jul.25 - sep. 9
- 6: sep.12 - kt.28
- 7: okt.31 - dec.16
the last course is as suggested by shape held 1984,
week 2 through 8,
cr accepts to conduct course no. 8 in latina at an
additional price of 93.000 dkr (one instructor).
2. the software course is optional, butthe training plan
for this course will be delivered according to contract.
fig. 2.1 will be clarified accordingly.
3. cr will comply
4. by "a.o." is meant "and other". the abbreviation will
be spelled out or deleted as applicable.
7. it is cr's pinion that software maintenance is the
job of a software specialist, i.e. software analyst,
designer or programmer. training of the software specialists
is done at the optional software maintenance course
(not yet exercised).
the capability of te rst's on software problems is
to report problems with the necessary level of detail,
insert patches according to stated procedures, but
not to debug software problems. the training will reflect
this point of view.
8.1 "introductory programming taining" will not help solving
the problems, the technicians are expected to meet.
the training in use of maintenance and diagnostic software
will substitute this.
8.2 paragraph 4.1.7 is an overview of the following text
only (in ref. doc. a) i.e. ara 4.2 through 4.5., and
not a decription of a single type of course.
12. please refer to point 7.
13. cr agrees without cost impact
15. please refer to point 7 and 8.1
16. please refer to point 7.
17. please refer to point 7.
18. cr agrees ithout cost impact.
all points not directly answered above will be complied
by cr.
r̲e̲f̲.̲:̲ ̲c̲a̲m̲p̲s̲ ̲l̲o̲g̲ ̲1̲9̲1̲
addition to para 4.1.1 in ref. doc. a:
the term "module level" is in the integrated training
plan defined as the level of repair, wherean integrated,
physical unit can be isolated and replaced. examples
of such units are: a printed circuit board, a power
supply and a cable with plugs.
table 3.3 (ref. doc. a):
cr will include "change in data bases" and "change
of software" meanig insert of patches or replacement
of the software unit.
Kind regards,
CHRISTIAN ROVSING A/S
Gert Jense
postscript:
cr hopes that this message satisfies shape's requirements and
that shape will confirm this by return msg. shortly. cr will
then initiate update of ref. (a) document
