Data Processing The MDS data processing facilities collect, store, and  analyze  maintenance  information  inputs  into  the system   to   yield   data   concerning   equipment maintainability   and   reliability,   manhours   usage, equipment alteration status, material usage and costs, and  fleet  materiel  condition.  Various  automated  reports are produced periodically for the ship, repair activities, unit  commanders,  and  type  commanders.  These automated  reports  include  a  current  ship’s  maintenance project file, work requests, and preinspection and survey deficiency  listings. INTEGRATED MAINTENANCE Combat   system   maintenance   is   based   on   a comprehensive schedule of tests performed at three mutually supporting levels: (1)  combat system,  (2) subsystem, and (3) equipment. These  integrated  tests are  designed  to  test  all  combat  system  functions, parameters,  and  characteristics  periodically  against specified  tolerances.    Successful    equipment performance during the tests usually indicates that the system is combat ready. Integrated  maintenance  requirements  are  developed through engineering analysis, based on a study of all factors  that  significantly  affect  maintenance.  The analysis  defines  system  and  equipment  functions,  and sets tolerances (in terms of system parameters) that allow operators and technicians to determine whether or not  the  system  is  operating  properly. Integrated   maintenance   procedures   provide minimum  preventive  maintenance  coverage  of  the combat  system  and  are  designed  to  test  specific functions   under   specific   conditions.   Sometimes equipment   operators   and   technicians   may   not understand the purposes of the tests. However, they must still follow the procedural sequence explicitly. Improvising or shortcutting procedural sequences often leads to incorrect troubleshooting or masking of actual faults. The  integrated  maintenance  concept  follows  PMS principles and is the most effective way to achieve PMS goals. Adhering to this concept enables the SERT to manage the combat system maintenance effort and achieve an optimum level of readiness with the most effective  use  of  available  manpower. COMBAT SYSTEM TESTING Combat  system  testing  is  conducted  at  three  levels: (1)  combat  system,  (2)  subsystem,  and  (3)  equipment. Integrated maintenance tests must be scheduled to reduce redundancy wherever possible. The three levels of testing are described in the following paragraphs. SYSTEM  TESTING Combat system testing exercises the entire combat system. It is the highest level of testing that can be done on  board  ship.  Combat  system  tests  are  usually automated  and  monitored  in  the  combat  direction system  (CDS)  subsystem. While these tests provide an overview of system performance,  they  usually  do  not  test  the  full  capability of  the  combat  system.  It  is  impractical,  from  an instrumentation  and  manpower  standpoint,  to  test  all  of the  functional  requirements  at  the  system  level. Therefore,  confidence  in  operability  or  materiel readiness is mainly dependent on integrated testing at the subsystem or equipment level. System-level  tests  provide  a  verification  of  the alignment  between  sensors;  on-line,  real-time monitoring of combat system interfaces; and an overall test of the 3-D search radar and its interface with the CDS. These tests are described in the synoptic test descriptions in the CSTOM. SUBSYSTEM  TESTING Subsystem  testing  exercises  two  or  more  pieces  of equipment  functionally  contained  within  the  same subsystem. The intent of subsystem testing is to test intrasubsystem (within the subsystem); but with the need  for  integrated  testing,  some  functions  are  tested intersubsystem  (outside of the subsystem). The subsystem  operability/readiness  test  is the keystone   of   integrated   subsystem   testing.   The subsystem  operability/readiness  test  consists  of  a  rigidly controlled sequence of steps designed to test all critical functions  during  a  primary  mode  of  operation.  The subsystem  operability/readiness  test  and  a  supporting family of system tests use the concept of end-point testing  in  which  functions  are  stimulated  at  their terminal  point,  thereby  verifying  all  operations  within the function. Subsystem tests are functionally grouped and  mode-oriented  so  related  functions  may  be  tested using  the  same  setup,  procedures,  and  stimuli. 4-22