Engineer or senior engineer or systems engineer
Content
Senior Engineer - 30+ years of military aircraft, ground vehicle, and electronic s development experience, specifically: * * * * * * * * * Aircraft Stability and Control Electronic Warfare Mission Planning Software - IV&V and development Avionics - navigation, weapon delivery, sensors Net-Centric Warfare - system of systems Intelligence - Combat operations center, Europe Systems Engineering - UML, Sysml C4ISR
Education: o BS Aeronautical & Astronautical Engineering Purdue University - W. Lafayett e, IN o MS Aeronautical Engineering University of Washington - Seattle, WA o MBA Coursework University of Dayton - Dayton, OH Clearance: o Active Secret - Former TS/SCI Employment History: Reverse Chronological order
L-3COM GSES - Systems Engineer/Operational Architect 04/2009 - 09/2009 o Sole L-3COM representative to the Special Forces Command at Ft Bragg, NC. o Was assigned to develop C4ISR Architectures per DoDAF instructions for propos ed Special Force unique equipment and weapons. Emphasis was on DoDAF OV-1s used to brief command staff. GDLS (General Dynamics Land Systems) - Requirements Manager 10/2008 - 01/2009 o Was hired in the midst of the STRYKER Upgrade program requirements developmen t phase. o My assignment was to improve the development process and ensure requirements quality (e.g., complete, feasible, unambiguous, testable). I failed to effect s ignificant change because the primary objectives of the upgrade were never compl etely defined and because of organizational bias. SAIC - Senior Systems Engineer 02/2008 - 10/2008 o Assigned to the Army Tank Command (TACOM) in Warren, Michiga o Mentored junior Systems Engineers. o Developed System Engineering Plan (SEPs) for R&D projects. Lockheed Martin - Requirements Manager 11/2006 - 11/2007 o Assigned to Coast Guard Deepwater system-of-systems program. o Responsible for the team maintaining the DOORs database. o Proposed DOORs enhancements to facilitate data access and correlation. Proto types were well received but further development responsibility was assumed by L ockheed management. GDLS (General Dynamics Land Systems) - Systems Engineer 06/2003 - 11/2006
o Requirements UML Analyst for FCS (Future Combat System) o Led a team whose responsibility was to certify requirement validity. Non-industry Related work 10/2000 - 03/2003
Northrop Grumman / Logicon 01/1977 -10/2000 o Tech Lead for B-1 EW software IV&V team
o Tech Lead of LANTIRN Pods (Navigation & Weapon Delivery) software IV&V team o Tech lead of IV&V team overseeing Intelligence Analysis Tool development for the Combat Operations Intelligence Center (COIC) at Ramstein Air Base, Germany. o Senior EW Engineer on EW Directorate at Point Mugu NAS, Malibu, Ca. o Lead Engineer for the B-2 Mission Planning System program development. o Lead Engineer for JMPS (Joint Mission Planning System). Boeing Commercial Airplane Company -- Stability and Controls Engineer 01/19 75- 01/1977 o Conducted wind tunnel testing, analyzed test data and authored the Flying Qua lities Prediction Doc.
Education: o BS Aeronautical & Astronautical Engineering Purdue University - W. Lafayett e, IN o MS Aeronautical Engineering University of Washington - Seattle, WA o MBA Coursework University of Dayton - Dayton, OH Clearance: o Active Secret - Former TS/SCI Employment History: Reverse Chronological order
L-3COM GSES - Systems Engineer/Operational Architect 04/2009 - 09/2009 o Sole L-3COM representative to the Special Forces Command at Ft Bragg, NC. o Was assigned to develop C4ISR Architectures per DoDAF instructions for propos ed Special Force unique equipment and weapons. Emphasis was on DoDAF OV-1s used to brief command staff. GDLS (General Dynamics Land Systems) - Requirements Manager 10/2008 - 01/2009 o Was hired in the midst of the STRYKER Upgrade program requirements developmen t phase. o My assignment was to improve the development process and ensure requirements quality (e.g., complete, feasible, unambiguous, testable). I failed to effect s ignificant change because the primary objectives of the upgrade were never compl etely defined and because of organizational bias. SAIC - Senior Systems Engineer 02/2008 - 10/2008 o Assigned to the Army Tank Command (TACOM) in Warren, Michiga o Mentored junior Systems Engineers. o Developed System Engineering Plan (SEPs) for R&D projects. Lockheed Martin - Requirements Manager 11/2006 - 11/2007 o Assigned to Coast Guard Deepwater system-of-systems program. o Responsible for the team maintaining the DOORs database. o Proposed DOORs enhancements to facilitate data access and correlation. Proto types were well received but further development responsibility was assumed by L ockheed management. GDLS (General Dynamics Land Systems) - Systems Engineer 06/2003 - 11/2006
o Requirements UML Analyst for FCS (Future Combat System) o Led a team whose responsibility was to certify requirement validity. Non-industry Related work 10/2000 - 03/2003
Northrop Grumman / Logicon 01/1977 -10/2000 o Tech Lead for B-1 EW software IV&V team
o Tech Lead of LANTIRN Pods (Navigation & Weapon Delivery) software IV&V team o Tech lead of IV&V team overseeing Intelligence Analysis Tool development for the Combat Operations Intelligence Center (COIC) at Ramstein Air Base, Germany. o Senior EW Engineer on EW Directorate at Point Mugu NAS, Malibu, Ca. o Lead Engineer for the B-2 Mission Planning System program development. o Lead Engineer for JMPS (Joint Mission Planning System). Boeing Commercial Airplane Company -- Stability and Controls Engineer 01/19 75- 01/1977 o Conducted wind tunnel testing, analyzed test data and authored the Flying Qua lities Prediction Doc.
