Whenever you evaluate the operational readiness of
your personnel, you should ensure that they are familiar
with the following topics:
Intended purpose of all switches, indicators,
controls, and the impact each has on other
subsystems or combat system equipments
Communication links available at the station and
with the other stations
Knowledge of and compliance with specified
communication disciplines
Knowledge that the lack of communication
discipline is an internal hazard to the combat
system or to the ship
TEST SELECTION AND SCHEDULING
With the coming of PMS, an integrated approach to
testing was developed. This approach is based on
defining all functional test requirements and subjecting
them to a critical examination. The examination
involves an engineering analysis in which each function,
parameter, and characteristic is examined for its (1)
importance to mission or mode performance, (2)
reliability based on the circuit elements that affect the
function and (3) expected mean time between failures.
This places a test periodicity (daily, weekly, monthly,
quarterly, semiannually, annually, and cyclically) on the
functions. Critical functions are assigned a high
periodicity, regardless of reliability; while less critical
functions may be assigned a lower periodicity based on
their reliability. Related functions are grouped by
periodicity and functional interdependency so that they
may be tested by appropriate periods. This integrated
testing concept results in a management problem that is
a SERT responsibility.
The tactical situation governs how and when
maintenance is scheduled. Scheduling is a critical
element of preventive maintenance management and
requires a thorough knowledge of the intent and
conditions of each maintenance requirement card
(MRC). Important conditions include in-port and at-sea
requirements, outside service requirements,
navigational support requirements, combat system
operational usage, ship control requirements, emission
control conditions, computer program requirements,
subsystem interdependency, impact on computer
program capability, adverse weather conditions, time
requirements, and manpower requirements. From these
conditions, the quarterly schedule can be developed
based on the ships employment schedule. Heavy
maintenance is usually scheduled during in-port periods
and independent ship exercises during nonthreat
conditions (particularly for those procedures requiring
long periods of operational equipment downtime). If the
employment schedule changes, the PMS schedule may
require modification. Daily and weekly schedules are
based on the ships readiness condition and operational
situation. Subsystem interdependence and manpower
usage are also critical in scheduling.
Preventive maintenance management includes the
following requirements:
1.
2.
3.
4.
5.
6.
7.
Ensuring that events take place as scheduled
Coordinating manning and equipment
availability for interdependent testing
Providing adequate safety measures
Ensuring the availability of required supporting
systems
Coordinating the actions of command and
tactical operation personnel
Ensuring fault isolation and corrective
maintenance follow-up
Ensuring the completion of required reports
The ships CSTOM contains readiness assessment
and fault isolation diagrams indicating the test that
requires the fewest ship resources, verifies each combat
system interface function, and aids the SERT in
preventive maintenance management.
READINESS ASSESSMENT REPORTING
After readiness assessment is completed, readiness
status must be reported in a form that is brief and easily
understood and that presents a clear picture of the
combat system effectiveness. This is done most
effectively by addressing the status of a major function
as it relates to a mission capability. Figure 4-7 shows a
sample method of presenting a mission summary report
of a four-state qualitative functional readiness
assessment. This summary report sample also provides
a brief description of the effect each subfunction fault
has on the major fictional. Supporting information on
specific subfunction faults related to the summary report
sample can be provided in a combat system daily fault
report form. Figure 4-8 shows a sample method of
presenting daily fault information. Report forms of this
type (or a similar type) should be developed by the SERT
to fit the ships requirements. The combat system daily
fault report is the responsibility of the SERT and should
4-18