1. DoD Acquisition Domain (Sourcing) (DADS) Analysis of Alternatives (AoA)
Good Morning
Today I am going to give you an overview and update on the Analysis of Alternatives process currently underway.
E-Business/SPS Joint Users’ Conference November 15-19, 2004 Houston, TX

2. Agenda AoA Background AoA Process Team Accomplishments Next Steps
JROC / JCIDs
Functional Area Analysis
Functional Needs Analysis
Functional Solution Analysis
Team Accomplishments
Next Steps
I will give a little background, talk about the AoA process, explain what JCIDs and JROC mean
Highlight the Functional Area Analysis and Functional Solutions Analysis
Team Accomplishment, and the Next Steps to reaching a solution for future sourcing capabilities.

3. AoA Background
The AoA is being conducted by Office of the Under Secretary of Defense (Acquisition Technology & Logistics)
AoA Direction pursuant 26 Nov 03 AT&L Memo
The AoA for future joint Acquisition Domain capabilities conducted DPAP
Tasks include:
Obtain JROC validation / approval of ICD
Obtain Milestone Decision Authority Approval of AoA Results
Develop Technical Development Strategy
All DOD Components represented
Air Force is AoA Study Director
Includes discussions with Federal and Industry partners
The AoA was directed in Nov 2003 and is being led by OSD, AT&L
The focus is on identifying alternatives for sourcing capabilities in the future
All DOD Components participate in the workgroup and the analysis includes discussion with Federal and Industry partners.
The rest of the presentation will discuss the AoA process more formally.

4. AoA Defined What is the AoA?
Analysis of the sourcing capabilities needed by DoD
End-to-End Procurement
Moves beyond procurement to include capturing requirement document, pre and post contract management, purchase card, and assistance agreements
Sourcing is done at many levels
Requirements Definition
Full and Open Competition
Task/Delivery Order contracting
Purchase Card Transactions
And
Assistance Agreements

5. Digitizing the Sourcing Functions
Start
Start with Identifying Needs
Then, evaluate alternatives, determine requirements (this may take a few iterations), then proceed to
Design and development of the program, test, build the system, inherently testing will occur repeatly, field the system,
Then there is system support
Through the configuration management process, reengineering, and infusing best practices, there will be continued enhancements, which get tested and fielded

6. AoA Purpose Why are we doing an AoA?
Currently, no visibility into Enterprise-level buying activity
No means of providing auditable financial accounting across DoD
Cannot respond to Total Cost of Ownership requirements
Need to evaluate the best alternatives to meet our sourcing capabilities
Who is the Enterprise? DOD
No means of providing auditable financial accounting – GOAL is achieve a clean audit from GAO
And we can’t capture our total cost of ownership
As part of the AoA we consider the full scope of concerns that effect
considers these factors as part of the

7. Operational Concepts
Joint, seamless, end-to-end procurement process for DoD
Open to all operational environments
Interface and interoperability aspects
Data sharing with allied, coalition, multi-national partners
Support synchronization of databases
Information flow among multiple information formats
Identify associated information/data element levels
Intelligent push-pull of data
Interface with contractors using commercial standard formats
Open means Open System - a system that implements specifications for interfaces, services, and support formats, to enable properly engineered components to be utilized across a wide range of systems with minimal change, to interoperate with other components on local and remote systems, and to interact with users in a manner that facilitates portability.
Interface with contractors to support electronic transaction processing using commercial standard formats

8. AoA Process Joint Requirements Oversight Council (JROC)
Validates and approves the Joint Capabilities Integration and Development Systems (JCIDS) documents
Initial Capabilities Document (ICD) is prepared by the user to articulate a capability gap that requires a system solution
Procurement is the first business system to go through the weapons systems JCIDS process
Joint – means all of us
JROC and JCIDS are program oriented efforts – needed before procurement is executed -- part of the Acq Domain and Procurement is the first business system to go through the weapon systems JCIDs process

9. AoA Process
The focus of the AoA is to refine the selected concept documented in the approved ICD. The AF is the lead Service for this process.
Per the Nov 2003 ATL Under Secretary memo the AoA started
This slide shows the timeline and activities completed and planned –
Jan 04 FAA Began, the Functional Needs Analysis was done
By Mar04 the ICD (Stage I) was done concurrently with the Functional Solutions Analysis
In June 04 the AF level approval was completed
Oct 04 MDA approval was received
The hot-pink letters shows we are currently at the FSA Execution phase
Future activities include the Concept Decision approval in Aug05, the JROC Validation in Nov05 and the MS Authority decision in Dec05
KEY ACTIVITIES ARE EXPLAINED NEXT FEW SLIDES.
The AoA shall assess the critical technologies associated with these concepts, including technology maturity, technical risk, and, if necessary, technology maturation and demonstration needs.
To achieve the best possible system solution, emphasis shall be placed on innovation and competition. Existing commercial-off-the-shelf (COTS) functionality and solutions drawn from a diversified range of large and small businesses shall be considered.

10. Functional Area Analysis (FAA) Required Capabilities
Timely, cost effective sourcing
Leveraged-enterprise buying power
Timely & accurate data to support accounting & finance processes
Requirement initiation through closeout/final disposition
Supports FAR/DFARS & other sourcing guidance for contracts, commercial capabilities and assistance agreements
Flexible, adaptable, secure interoperable w/other communities
Solution will reside within Global Information Grid
Multiple operational environments
Available anywhere US Forces operate
Classified and non-classified
The FAA identifies the operational tasks, conditions and standards needed to achieve our objectives.
We need to reach the source to get what we need timely and in a cost effective manner
Leverage our buying power, DOD spends over $219B a year in contracting dollars – that is a lot of leverage
Track our requirements anywhere in the world, from end-to-end, within policy and regulation, for classified and non classified requirements.
Be flexible for different systems, commodities and service
Be compliant with the global information grid (GIG interconnected, E2E set of information, capabilities, and associated processes and personnel for collecting processing, storing, disseminating, and managing information.

11. Functional Needs Analysis (FNA)
The Functional Area capabilities are assessed to identify capability gaps and preliminary requirements
Laws
Chief Financial Officer Act
Clinger-Cohen Act
Government Performance and Results Act (GPRA)
Federal Information Security Management Act (FISMA)
Business Process Re-engineering Workshops
Government Purchase Card IPT
PD2 299 Functional Requirements
Defense Logistics Agency Business System Modernization (BSM)
Technical Influences
Business Enterprise Architecture
Global Information Grid CRD
Network Core Enterprise Services Initial Capability Document
Global Combat Support System
The Functional Needs Analysis assesses the FAA to identify capability gaps framed by -
Framed by laws such as Chief Fin Ofcr Act, 2002
clinger-Cohen Clinger-Cohen Act of 1996 , and the
GPRA - Government Performance and Results Act (1993) annual perf plans required after submission of annual budget
AND other initiatives such as BSM - This "Business Systems Modernization" (BSM) strategy will result in a new COTS, enterprise Information Technology (IT) environment which will enable reengineering, outsourcing and partnering with customers and suppliers at all DLA echelons.
Business process reengineering – not just automating the status quo
Capture the BI associated with the purchase card
We have to consider the 200 requirements in PD2 which is over 59,000 data elements.
There are also technical influences such as…Business Enterprise Architecture
Global Information Grid CRD, Network Core Enterprise Services ICD
Global Combat Support System

12. Functional Solutions Analysis (FSA)
Provides direction for acquiring capabilities to fulfill shortfalls in the Functional Needs Analysis
Recommend preferred alternative for AoA Study
FSA has two parts
Non-material solution: Satisfy by changing doctrine, operations, training, leadership, personnel and/or facilities
Material solutions: possible “types” of viable solutions to fill the gaps, which are the most cost-effective
Resulting AoA and Technology Development Strategy (TDS) taken to “Milestone A” Decision
Functional Solutions Analysis - Operationally based assessment of all potential doctrine, organization, training, materiel, leadership, personnel and facilities (ORG CULTURE) approaches to solving (or mitigating) one or more of the capability gaps (needs) previously identified.

13. FSA Alternatives Priorities for alternatives include
Leverage existing capabilities (keep the status quo)
Make product improvements to the existing system (re-engineer the status quo)
Use existing solutions currently in Federal Sector
Initiate a new system solution
COTS
Proprietary System
The alternatives are listed here
Keep our baseline
Tweak the baseline (to keep up w/ the FAR/DFARS)
Modify the status quo (upgrade what we have)
Develop a customized system from scratch
Have an Interoperable a family of solutions
Outsource
New COTS solution – from scratch
Keep the legacy systems

14. AoA Team Accomplishments
Trained multiple work groups
Joint Representatives
Achieved a mature process
Developed effectiveness measures
Completed Market Survey
RFI done, Industry responses received
Developed alternative approaches
Completed initial approach comparison
Global Information Grid – a globally connected, end-to-end set of information capabilities, associated processes and personnel for collecting, processing, storing, disseminating and managing information on demand to warfighters, policy makers and support personnel. The GIG includes all owned and leased communications and computing systems and services, software (including applications), data, security, services, and other associated services necessary to achieve information superiority. The GIG Integrated Architecture underpins all joint mission area capability architectures. The GIG was formerly known as the Defense Information Infrastructure (DII). See also Joint Integrated Architecture.

15. Next Steps Take remaining approaches into further study
Apply cost factors to viable alternatives
Complete Initial Capabilities Document (ICD) Stage 2
Present ICD to Air Force Requirements Oversight Coordinating Council (AFROCC)
Forward requirement to Joint Requirements Oversight Council (JROC)
Functional Needs Analysis – Assesses the ability of the current and programmed joint capabilities to accomplish the tasks that the FAA identified under the full range of operating conditions and to the designated standards.

16. Our Vision... An innovative and strategic Acquisition enterprise focused on efficient and cost-effective delivery of the best possible capabilities that enable the Warfighter to succeed.
Our Mission... Lead the transformation to strategic acquisition by integrating the people, processes, technologies, and policies required to implement a modern acquisition environment that supports the Warfighter's needs.