Cameron Reed Email and Phone Number

Began at GE as a developer working on the Precision Dispatch System (PDS). This is an extremely complex railway traffic monitoring and control system in active use by Norfolk Southern Railway, with additional customers, including CSX, Canadian National (CN) and BNSF in various phases of deployment. The work spans both linux and Desktop environments, with the lion’s share of my responsibilities being on the C++/linux side, but also working in Java Swing to do UI work. The communications between all of these components is a mixture of JMS, Tuxedo (SFT), RMI, SMI, Restful calls, as well as strict socket communication. Became Scrum Master when previous Scrum Master moved to a new position within the company. Participated in formal Scrum Alliance training and am a certified scrum master. As scrum master, the main focus was to guide the team to accomplish the goals set out for each sprint during sprint planing. Each 2-week sprint culminated in a demo to the entire program (several other scrum teams) followed thereafter by a retrospective discussion to address any issues or concerns and to accentuate the positive aspects that led to successes we had during the sprint.

JADOCS (Joint Automated Deep Operations Coordination System): Participated in high-pressure, short-term sprints preparing JADOCS for deliveries, actively keeping with the JADOCS Agile development methodology. Developed user interfaces for integration into the JADOCS client toolset. Also assisted with software and support issues pertaining to the JADOCS supported system: Korean Joint Command and Control System (KJCCS). CPM (Consolidated Product-Line Management):Software and system design and engineering support, including development, unit and system test, configuration-management, deployment, and site-support. Considered a subject matter expert on Combat Training Centers Objective Instrumentation System (CTC OIS) and CTIAProject Manager: CTIA (Common Training Instrumentation Architecture)Project Manager: CPM (Consolidated Product-Line Management)Project Manager: OneTESS (One Tactical Engagement Simulation System)Responsible for staffing, scheduling, Earned Value Management, EAC, cost reporting, interfacing with prime contractors and customers, and all other duties relating to Project Management. Worked with CAMs and customers on budgets and staffing. Fought for and procured workshare for Raytheon developers. Performed reviews and worked with engineers on their strengths and improvements. Oversaw the drawdown and contract end of both the CTIA and OneTESS contracts. Continued as PM of CPM until reduced staffing from loss of contracts led back to full-time engineering role.

Technical Lead of the System External Gateway (SEGW) project. In addition to a heavy focus on C++ development, responsibilities included interfacing with customers and prime contractor, design discussions and decisions, task assignment, prioritization, scheduling and tracking, personnel scheduling and coordination, milestone and deadline management, software deployment and documentation, and on-site support. During this time, the SEGW project expanded from a single DIS-CTIA gateway to six separate gateways and a GUI interface. These gateways allowed the core, classified system to interface with a wide range of external, unclassified systems, including the TCN (Tactical Central Node), TENA, A constructive simulation system (JCATS), and Green Flag (Air Warrior). The gateways also translated data through a Radiant Mercury Cross Domain Solution (CDS).

Sr. Developer on the System External Gateway (SEGW) Portion of the Battlefield Effects & Interfaces (BE&I) Contract for the Combat Training Centers Objective Instrumentation System (CTC-OIS) project. Designed the gateway architecture to translate Distributed Interactive Simulation (DIS) Protocol Data Units (PDUs) into the corresponding Common Training Instrumentation Architecture (CTIA) entity data and update a simulation environment with the appropriate state information. This entailed extensive knowledge of C++, the DIS protocol and CTIA.

FCS - SMART:Worked on the development of an architecture framework to ensure that the philosophies and guidelines set forth by the Army’s Simulation & Modeling for Acquisition, Requirements, and Training (SMART) initiative are followed across the entirety of the Future Combat Systems (FCS) program. OneTESS:Year-long Proposal effort competing against one other vendor for the OneTESS contract, a comprehensive next generation tactical engagement training and test system designed to enhance warfighter training and platform operational test. Duties included architectural design, concept development and design of UML models, research, and concept papers. Was an active member of the proposal team and contributed presentation slides, ideas, and expertise to the proposal effort.NASM (National Air and Space Model):Worked on integrating the NASM software into the Joint Simulation System (JSIMS) federation. Responsibilities included identifying problem areas and debugging code, performing code optimization on newly developed algorithms, writing scripts to assist with the integration effort (including automation of data collection and recording), and collecting and analyzing performance data.

Worked on a project which simulated an entire real-time networked environment on a single workstation, emulating the space shuttle telemetry collection and shuttle launch control system. Gained tremendous experience in UNIX shell scripting, including perl, ksh, csh, sed, awk, et.al. Developed a retrieval engine for archived space shuttle telemetry data. This engine was scheduled to replace the current one and was written to handle a new data format, taking advantage of technology advances in hardware and software performance. Developed software to retrieve data in real-time from the space-shuttle telemetry stream. This data was displayed on strip charts, which were created using the expert system SL-GMS.Developed a space shuttle tile status tracking application. This application was written in Java utilizing the Java 3D API. Taking the coordinates of the corners of each tile on the orbiter, it rendered the tiles in three dimensions. Each tile could then be individually selected and its status modified.