Find a Security Clearance Job!

Military


 DOT&E

Director, Operational Test & Evaluation
  
FY97 Annual Report

FY97 Annual Report

NAVAL TACTICAL COMMAND SUPPORT SYSTEM (NTCSS)

Navy ACAT IAM Program
377 systems
Total program cost (TY$) $772M
Average unit cost (TY$) $2.1M
Full-rate production 3QFY98

Prime Contractor
Navy Management Systems Support Office (NAVMASSO)

SYSTEM DESCRIPTION & CONTRIBUTION TO JOINT VISION 2010

NTCSS is a tactical command support information system for management of ships, submarines, aviation squadrons, and intermediate maintenance activities (afloat and ashore). NTCSS provides the unit commanding officer and crew with the ability to manage maintenance of the ship/aircraft, parts inventory, finances, automated technical manuals and drawings, personnel information, medical, crews mess, ships store, and unit administrative information. NTCSS also provides the intermediate level maintenance activities with the ability to manage workload and resources involved in repair actions for aviation repairables and ships repair work packages.

NTCSS is an open architecture client/server system using a common server and operating environment with tactical systems (TAC series computers and the JMCIS Common Operating Environment). PCs and peripherals have been added for greater access and functionality while future versions will shift more computing workload to the client as new operating system and application software technologies allow.

NTCSS is a roll-up of several independent legacy systems including the Shipboard Non-Tactical ADP Program (SNAP) and Naval Aviation Logistics Command Information System (NALCOMIS). It is the support side of the Joint Maritime Command Information System (JMCIS), with the Naval Tactical Command System - Afloat (NTCS-A) as the tactical side. JMCIS is the Navy input to the Global Command and Control System (GCCS).

NTCSS supports JV2010 in the area of focused logistics. The improved asset visibility and timely logistics and maintenance information flow to tactical decision makers will allow better use of available forces.


BACKGROUND INFORMATION

As part of the Navy's Copernicus architecture and the evolution towards the JMCIS strategy, an NTCSS Program Transition Plan and Program Manager's Charter was released in May 1993. The SNAP III program manager was moved up into the role of NTCSS program manager after successful fielding of SNAP III in 1994.

Development work by NAVMASSO commenced in 1995 on the NTCSS Software Optimization. This step is essentially a software technology insertion phase following in the footsteps of the successful hardware technology insertion phase which was SNAP III and the successful automation of a manual process which was NALCOMIS OMA. Optimization will bring reengineered/ported code and minor procedural changes, including improved interfaces between the legacy systems, to NTCSS.

The follow-on step will be a Business Process Improvement phase which will result in reengineered processes and code and integration of the existing systems.


TEST & EVALUATION ACTIVITY

An Optimized SNAP DT, followed by an OT period, will take place 1-3QFY98. The Test and Evaluation Master Plan and test plan are approved.


TEST & EVALUATION ASSESSMENT

Testing is currently being done aboard an Arleigh Burke class ship and the USS Enterprise. The optimized SNAP III OT testing conducted to date has revealed no major deficiencies. Test results are still being analyzed and emerging results will be available in February 1998. The maintenance application within SNAP III performed well during testing. This application provides for organizational level maintenance and material management support aboard ship. Optimization consists of a technical update to the existing system software and the testing focused on functionality, interoperability and responsiveness. Adequate training has proven vital in using the optimized system.


LESSONS LEARNED

Early and long involvement of DOT&E action officers and/or support personnel allowed smooth procession of test planning and program documentation despite differences over extent of testing and documentation requirements.



NEWSLETTER
Join the GlobalSecurity.org mailing list