NAME: STANLEY ADDESS
Contact Information: **** Northedge Drive
Springfield, VA 22153
(C) 703-***-****
*******.******@*****.***
Clearance Level: TS/SCI with Full Scope Polygraph
EDUCATION:
• B.S. (Chemical Engineering and Meteorology), City College, 1960
EXPERIENCE
L3 – Stratis 3/2012 to present
System Engineer/Architect
Mr. Addess is in the role of SETA contractor and is providing System Engineering support in the
area of Cyber Security technology development to the DoD Cyber Security Enterprise. Prior to
this assignment, Mr. Addess provided System Engineering and Architecture expertize to the
Secure Configuration Management and Audit Management projects being carried out on behalf
of the Department of Defense by the NSA. As team lead, he defined those DODAF products that
are necessary to satisfy the JCIDS process for a major IT system. He ensured that the SCM
architecture would be in compliance with the emerging Joint Information Environment (JIE). He
led the team in producing the required architectural views. Additionally, he coordinated and
participated in a major requirements traceability activity to map the architecture and new
initiatives against the functional requirements of the GIG 2.0. Further, Mr. Addess coordinated
and provided guidance and consulting to the Active Cyber Defense (ACD) architecture. For the
Technology Development Division of the NSA/CSS Threat Operations Center, provided
requirements management for a series of projects associated with information sharing and
situational awareness. Further for the same customer performed an analysis of alternatives
leading to a replacement for a legacy analyst tool.
Cloud Architecture
As part of the efforts associated with all three activities for this customer, Mr. Addess was
involved with ensuring that the designs would be compatible with the Enterprise Cloud
Architecture. This meant that applications would be built utilizing the Ozone Widget Framework
(OWF), that data would need to be normalized and follow a standard schema, that meta data
extraction could be automated to fit within bandwidth constrains. Further it is imperative that
workflow utilizing the cloud could be developed on a customized bases and be repeatable and
shareable. Additionally, to support IA audit requirements, Provenance Data needs to be collected
and provided to an automated audit process. Details of these activities are classified.
(b) SRA/RABA Technologies, Principal Consultant (c) 2007 to
2012
(d) Mr. Addess provides Architecture and Project Management expertise to major intelligence
community initiatives involving the full spectrum of Information Technology including Service
Oriented Architectures. He developed the Enterprise Architecture for a major intelligence
community component. He stood up and managed a verification and validation program for that
same agency. As this project used the agile methodology, he assumed the role of product owner
as well as created the requirements needed for test based on the customer user stories.He
provided Project Management to a DOD classified spacecraft program. The project provided
embedded software for autonomous spacecraft control. He provided Disaster recovery solution
support to a major intelligence agency as well as enterprise system engineering.
Cloud Architecture
As part of his CIO tasking, Mr. Addess was a member of a working group directing the
implementation of a multi – agency cloud pilot that sought to prove the feasibility of enabling
cross agency sharing of widgets and data of a cross-domain space. It further was to develop
performance measures for networks and platforms to determine scalability for utilization. In all
cases to was to determine feasibility of concurrently accessing and analyzing structured and
unstructured data sets. This work was performed under DNI funding.
(b) ITS Corporation, Vice President (c) 2006 to 2007
(d) Mr. Addess was responsible for growing, expanding and developing enterprise architecture
offerings to the federal sector. He served as Chief Enterprise Architect and is heavily involved in
up front project phases. He was responsible for managing and driving all high level design,
maintenance, assessment and optimization of architectural designs. He was responsible for
providing onsite SME support to federal clients responding to legislative and executive mandates
for enterprise architecture and IT transformation.
(b) Perot Systems Government Service, Principal Consultant (c) 2005 to 2006.
(d) Mr. Addess was the domain lead for the Applications Domain of the agency's Enterprise
Technical Architecture. He developed and documented a variety of Enterprise Architecture
Artifacts for determining gaps and redundancy in the existing architecture. He utilized agency,
developed strategic plans and objectives, and provided future architectures taking into account
new and emerging technologies. He ensured compliance with the Federal Enterprise
Architecture. He served as interface for the agency Application Domain to the Office of the
Director of National Intelligence Enterprise Architecture efforts. This included serving on the
Intelligence Community Service Oriented Architecture Working Group. He provided
consultation to the agency Chief Architect on matters concerning OMB and ODNI direction
(b) High Performance Technologies Inc., Director (c) 2004 to 2005
(d) Mr. Addess served as lead architect for developing the Federal Enterprise Architecture as well
as products to provide guidance to all Federal Agencies for their Enterprise Architecture
development and utilization. He evaluated agency submissions for compliance and quality.
Regularly met with agency CIO’s to discuss progress, provided architectural guidance and
promoted OMB direction. Additionally, he led an effort to create a central repository for FEA
compliant agency EA artifacts. Further, he created the model for Version 2.0 of the OMB
Enterprise Architecture Assessment Tool. This version places the emphasis on EA usability and
usage.
(b) Titan Corporation, Senior Enterprise Architect (c) 2003 to 2004
(d) Mr. Addess developed the Enterprise Architecture Assessment Plan and associated metrics for
the NSA/CSS Enterprise Architecture. This plan covers assessment with regard to compliance,
process, completeness and usability. He provided Enterprise Architecture Services for the
Corporate Business Services Segment of the NSA/CSS Enterprise Architecture. This
Architecture is being developed using the DoDAF/C4ISR methodology. He worked closely with
NSA/CSS Subject Matter Experts in developing architecture models of the “As Is’ architecture
for the Strategic Capabilities Sub–Segment. As senior architect on the NEADS CBS team, he
helped guide fellow teammates on necessary EA implementation principles and best practices.
NEADS key technical member responsible for engaging NSA/CSS CBS Trusted Agent, JHU-
APL, to ensure that all suggestions/recommendations are consistent with the expectations of the
NSA/CSS Enterprise Architecture.
(b) SGT INC., Director of Information Technology (c) 1998 to 2003.
(d) Mr. Addess developed all processes and procedures as well as managed the Program
Integration Board for the Internal Revenue Service Modernization Project. He provided
architectural guidance in developing the initial version of the enterprise architecture from a
systems implementation perspective. He provided technical leadership and management to the
Development, Test, and Production Environments as well as operational test, validation and
deployment of the Customer Account Data Engine the fundamental cornerstone of the
Modernization Project. Mr. Addess developed and implemented a program wide risk
management and control program based on the Carnegie Mellon Software Engineering Institute
Model (Continuous Risk Management). He worked at a source selection case for Enterprise
Architecture tools for Popkin’s System Architect vs. Rational Enterprise Suite, and developed
processes for conducting all life cycle reviews for development projects to enable cross project
integration as well as Enterprise Architecture compliance. He supported enterprise architectural
product development utilizing Enterprise Life Cycle Methodology (a tailored variant of CSC’s
Catalyst Methodology) based on the Zachman and Spewak models. Along with leading the
instantiation of an Enterprise Architecture for the IRS, he engaged in several “hands-on”
activities such as systems development, test, and deployment (project level) activity.
(b) RDC, Director. Systems Engineering (c) 1997 to 1998
(d) Mr. Addess managed the corporation’s largest division, and served as a key member on the
corporation’s management team (reporting to the President and CEO). He directed the technical
and business development efforts of mid-level managers. Mr. Addess worked with the Director
of Flight Systems at NASA’s Goddard Space Flight Center. He developed the EO-1 (A
Hyperspectral Imaging Spacecraft) technology demonstration spacecraft mission plan, the
Mission Operations Concept operations, and the EO-1 Data Processing flows and concepts. He
supported the Program and Project Managers on full life cycle implementation both space and
ground segments and provided technical consulting on imaging spacecraft.
(b) CSC, Senior Consulting Engineer. (c) 1986 to 1997
(d) Mr. Addess supported the NASA Project Manager for the ESDIS Project, a $2 billion
information system. He successfully turned around the project’s development after isolating and
resolving issues associated with requirements decomposition as it affects object oriented
development. Simultaneously, Mr. Addess directed systems engineering studies in the area of
tracking, telemetry and command frequency migration for the Block IIF GPS Satellite System.
He managed support for the International Space Station Communication System, and directed a
line organization that provided system engineering support to various NASA Low Earth Orbit
missions. He utilized an earned value reporting system developed for NASA, which tracked
resources against accomplishments for a variety of work efforts from level of effort to fixed price
activities, and developed a client-server based capabilities information system to be operated by
the Office of Space Communications at NASA Headquarters. He provided SE&I to the Landsat
Ground System Development at NASA, which involved utilizing packet communications
systems, image-processing technology, and information management systems.
(b) Spot Image Corporation, Technical Director (c) 1984 to 1986
(d) Mr. Addess was responsible for the total systems life cycle for all corporate assets necessary
to meet corporate mission. This activity involved cutting-edge technology (e.g., international
digital packetized communications systems, image processing, early versions of LANS and
WANS, Geographic Information Systems and IMS applications) and international diplomacy.
He utilized point of sale technology and was solely responsible for all technical contracts and
contract activity for the corporation. During the development of this system, he was responsible
for formulating and reviewing work standards, assigning contractor schedules, reviewing
discrepancies in work products, communicating policies, purposes, and goals to employees, and
supervising contractor personnel.
(b) NOAA and USGS, Deputy Division Chief and Program Engineer (c) 1970 to 1981
(d) Mr. Addess was responsible for the operation of the Landsat 4 flight and ground segments,
including spacecraft command and control, mission planning, telemetry and data processing and
distribution. He performed the first checkout of the Tracking and Data Relay Satellite and was
the primary interface for all US Government Agencies. Mr. Addess directed the implementation
of all system design enhancements and chaired the internal and interagency Configuration
Control Boards, and chaired other various failure review boards to determine causes, solution,
and workarounds to failures in the space and ground segments of the system. As the Deputy
Chief, Landsat Operations Division, NOAA, developed and implemented the transition of
activities from NASA to NOAA