Section 6. Section 7. Section 8. Section 9. Navy   manning   plan   (NMP),   and members on board the activity. NEC  Summary.  A  summary  of  an activity’s authorized NEC billets and the members on board or expected on board who  possess  those  NECs. CNO  Billets  Authorized  Revision Number XXXXX dated yr/mo/da. The information contained in this section is identical  to  the  Summary  of  Organ- izational   Billets   appearing   in   the activity’s   Manpower   Authorization (MPA) OPNAV Form 1000/2. NEC Billet/Personnel Inventory. Lists NECs  for  which  the  activity  has authorized  billets  and  members  who hold  these  billets. NEC  Management  Section.  Lists  the names of the activity’s personnel who hold NECs, and lists up to five NECs per individual. As  a  supervisor,  you  should  learn  to  read  and  use the  EDVR.  It  will  provide  you  valuable  information  to use in providing proper manning for your ship. The format and procedures for validating the EDVR are shown in NAVMILPERSCOMINST 1080.1. MAINTENANCE MATERIAL MANAGEMENT  (3-M) RESPONSIBILITIES By this point in your career, you should have an extensive knowledge of the 3-M Systems and should follow their requirements automatically. As an ET1 or ETC, you should know the full use of the 3-M Systems and  must  ensure  that  your  personnel  comply  with  the 3-M Systems requirements. To review the mechanics of the 3-M Systems, we recommend that you read the “Ships 3-M Systems” chapter of the Military Requirement for Petty Officer Third Class  once again. This particular chapter of the Military  Requirements  for  Petty  Officer  Third  Class provides  an  excellent  description  of  the  3-M  Systems; however, the official reference for the 3-M Systems is OPNAVINST  4790.4.  You  may  also  wish  to  read lntroduction to 3-M Systems,  NAVEDTRA  13092.  This text  gives  a  short,  but  very  informative  explanation  of 3-M Systems and procedures. SHIP CONFIGURATION AND LOGISTIC SUPPORT  INFORMATION  SYSTEM (SCLSIS) The structure of a ship, defined in terms of onboard systems and equipment, is referred to as the ship’s configuration.   The   ability   to   define   a   ship’s configuration  accurately  is  critical  in  maintaining proper  shipboard  support.  Navy  managers  responsible for  the  operation,  maintenance,  modification,  and logistics  support  of  both  ships  and  equipment  need  to receive  accurate  configuration  data  in  a  timely  manner. To  ensure  the  availability  of  this  data,  many  Navy managers in the past developed their own information systems  for  gathering  and  processing  configuration data.  While  those  systems  satisfied  specific requirements,   each   required   maintenance   and organizational  support.  The  multiple  systems  also imposed redundant reporting responsibilities on the fleet. Managers who lacked the resources to develop their  own  configuration  information  system  were  forced to  collect  data  from  the  several  existing  systems.  This produced inconsistent results and interface problems because  of  different  program  languages  or  equipment incompatibilities. The need to provide all managers with a single, standard source of accurate ship configuration data and to reduce fleet reporting to a single requirement led  to  the  development  of  the  Ship  Configuration  and Logistics  Support  Information  System  (SCLSIS). SCLSIS  replaced  the  CNO-sponsored  program, Ship  Equipment  Configuration  Accounting  System (SECAS), in 1989. SCLSIS applies to all ships of the active and reserve fleets, except for fleet ballistic missile submarines  (SSBNS)  and  nuclear  propulsion  systems.  It covers  the  life  cycle  of  the  ship,  starting  during  its construction. Department   of   the   Navy   Configuration Management  Policy,  SECNAVINST  4130.2,  assigns  to the  Naval  Sea  Systems  Command  (NAVSEA)  the responsibility  for  maintenance  and  control  of  ships configuration  data,  including  related  platforms, systems, and equipments. It also requires that a single activity be designated as the ship class control authority for configuration data input and changes to the Weapon Systems  File/Ship  Configuration  and  Logistic  Support Information  (WSF/SCLSI)  Database.  The  WSF/SCLSI Database is maintained by the Ship’s Parts Control Center  (SPCC)  in  Mechanicsburg,  Pennsylvania. The term weapon systems file refers to the parts level,  parts  inventory  portions,  and  related  secondary ship component level configuration data files of the 2-16