1. PROJECT MANAGEMENT TRAINING FOR THE GCCS M SOFTWARE PROJECT XCELLENCE IN BUSINESS & ENGINEERING SOLUTIONS X FEDS, INC CAMINO DEL RIO NORTH, Suite SAN DIEGO, CA

2. GCCS M Software Maintenance and Fleet Support Engineering Services N00178-05-D-4664-NS03

3. Agenda: I. Introduction II. Project Processes III. Notes IV. Questions

4. I. Introduction  Purpose  Five Minutes  1 Slide  Project Summary  Ten Minutes  2 Slides  Products  5 minutes  3 Slides

5. Purpose To provide training on the GCCS-M software maintenance program to X-Fed employees. It was created using the Project Management Training Template and the GCCS-M Project Management Plan (PMP). This training slideshow includes all planning activities, either directly or by reference.

6. ;l Project Processes The Command and Control Program Office under the Program Executive Office Command, Control, Communications, Computers and Intelligence (C4I) has acquired software maintenance engineering, fleet support, and training support services for Global Command and Control System-Maritime (GCCS-M). GCCS-M is the maritime component of the GCCS Family of Systems (FoS) and is designated as a Mission Critical, Acquisition Category (ACAT) IAC - Major Automated Information System, National Security System. FOS GCCS-M (ACAT)(IAC) C4I

7. Project Processes (Cont.’d)  Global Command and Control-Maritime (GCCS-M) software has been developed using an evolutionary software acquisition strategy to fulfill Navy Command and Control (C2) requirements.  GCCS-M software is built on a foundation of core services provided by the DISA-managed Common Operating Environment (COE). GCCS-M software is currently fielded worldwide in over 320 shore sites and afloat platforms.  Requirements are described in a Navy-approved Operational Requirements Document (ORD) dated 12 February 1999 and Capability Production Document (CPD) dated 18 October 2006.  GCCS-M software must be periodically updated and maintenance builds and patches developed to support life cycle maintenance of fielded software builds

8. Project Processes (Cont.’d)  Distance and on-site Fleet support for GCCS-M software must be provided ashore and afloat.  Training documentation must be developed and updated, and training must be provided, based on new builds and gap analyses.  GCCS-M Increment 1 software consists of integrated, tested, certified, and accredited GCCS-M builds scaled to meet Navy platform requirements with additional software modules that provide maritime-unique C2 services.  This increment is comprised of the 4.0.x family of GCCS-M builds and is fielded ashore and afloat.

9. Project Processes (Cont.’d)  GCCS-M 4.1 (Increment 2) software is under development and will be composed of the GCCS-J product and Navy-unique Government-Off-The-Shelf (GOTS) software modules, which use Commercial-Off-The-Shelf (COTS) operating systems and databases.  These maritime-unique C2 services will be tested and evaluated by the Navy to ensure that they function properly with the GCCS-J product, without impact to the certification and operation of either product.  After the Full Rate Production (FRP) decision, GCCS-M 4.1 software will be fielded ashore and afloat, and life cycle maintenance will be required.

10. Products