Busine Business ss and Enter and Enterprise Sys prise Systems tems WE run the Systems that run the AIR FORCE…moving MONEY , MANPOWER and MA MATERIE RIEL Giving the Business to Business IT Rich Aldridge, Air Force Program Executive Officer Business & Enterprise Systems AFCEA Logistics Officers’ Association 4 Jun 20
B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7 2
The Strategic Context ◼ Russian fighter patrols over the Arctic for the first time in 30 years and Russian AA missiles from Syria to Siberia ◼ Chinese live fire exercises in the South China Sea ◼ “We have returned to an era of great power competition” – SecAF Wilson ◼ The AF has 75% of the combat power it needs (312 vs 386 ops sqdns) ◼ Innovation is in the DNA of the Air Force ◼ Multiple bomber models in WWII – iteration ◼ Nuclear, stealth, satellites ◼ Isn’t about removing bureaucracy or up’ing research ◼ What, how and who we buy solutions from is drastically changing Delivering at speed is the new normal, not saving money B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7 3
What policies of today will be seen like this in the future? B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7
What is the AF doing? ◼ Chess vs Speed Chess ◼ China is patient; plans for our predictability ◼ Time to market matters ◼ He who dies with the most money doesn’t win ◼ Transforming the Acquisition enterprise ◼ Section 804 authorities for prototyping – Goal: 100 yrs savings (MET) ◼ Section 873/874 Agile pilot programs ◼ Radical empowerment and delegation ◼ Innovation: Sparq Tank, AFWERX, Agile DevSecOps ◼ Operational Test reset ◼ Collaborating with OSD on Digital Technology appropriation ◼ Shifting from product to service-oriented IT B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7 5
What is the AF doing? ◼ AF Pitch Day, NYC, 7 Mar 2019 ◼ 51 contracts, shortest was 3 min pitch-to- pay; AF can be ‘first choice’ for start ups ◼ $660M/yr for Small Business Innovative Research; access to another $400M ◼ All PEOs cleared to do their own pitch day ◼ Reverse the Industry Base consolidation ◼ Software Factories ◼ Kessel Run Kobayashi Maru (Level Up) Space Camp ◼ BES Product Innovation (BESPIN) B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7 6
What is AFPEO BES doing? ◼ Catching our stride with Agile ◼ From 6 pilots in Feb 2017 to 30+ programs as of Dec 2018…and growing ◼ Making good use of Intel’s DI2E Atlassian Suite (Jira) and Microsoft TFS/Visual Studio Team Services ◼ 350 employees trained on Agile methodologies; Scrum Master growth – 13 to 44 ◼ Successes ◼ CON-IT: On-boarded 4,400 operational contracting users; Migrated 41,212 contracts at 98% success rate; shutdown 109 Standard Procurement System (SPS) instances across the USAF ◼ PBES: Delivered POTUS budget capability in mere 6 mo. from dev start-- 15 mo. earlier than scheduled; Trained 15 AF MAJCOM’s/Orgs & 350+ users, 4.7/5 satisfaction rating ◼ NEXGEN CE: 10 Sprints yielded 4 major releases in 6 months, fielded 500+ requirements (2010-2016: 350 requirements) B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7 7
Finally going mobile Inventory Check Part Request B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7 8
Partnering with CDO to tackle AF Data Challenges ◼ Large number of legacy systems with numerous point-to-point interfaces that are expensive to implement and maintain ◼ Antiquated, brittle architectures inhibit legacy system enhancements required to make data accessible ◼ Many legacy systems employ “data jails” that prevent timely data access that supports the analytics needs of Functional communities and senior leaders ◼ The time is now to employ new, commercially available data services that will change the landscape of how data enables mission effectiveness ◼ BES Data Pilot now an operational platform being used by two major orgs; signed out by USecAF as the AF Reference Architecture, DoD CDO reviewing as possible joint solution B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7 9
Challenging Existing Organizational Structures ◼ Air Force IT delivery is segmented ◼ The primary issues are organizational and cultural, not technical ◼ No single authority is responsible for end-to end IT service delivery ◼ Multiple orgs chasing unique IT solutions to common problems ◼ Warfighters need integrated IT solutions to deliver mission effects ◼ End-to-end services, designed to support enterprise outcomes ◼ Standard approaches to infrastructure, cybersecurity, and data ◼ Smarter business deals through enterprise integration ◼ AFPEO BES shifting to Product delivery not program management Army attempting to solve this on a broader scale with Futures Command, AF through governance structure and processes B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7 10
Sometimes we ended up with this B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7 11
Often we ended up with this B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7 12
Today’s Air Force IT Operational Context • Every Mission Area an island: • Pursuing unique solutions to common problems • Decreasing IT spend value • Designing IT independent of supported missions (IT for IT’s sake) • Increasing cybersecurity risk • Losing data visibility & intel • Creating operational risk through gaps and seams between systems • Decreasing Cloud migration velocity • Wasted energy on products, no synergy in delivering services Readiness impacted by stove-piped budgets, priorities, & technical disparity 2 Not architected; not governed; performance neither measured nor measurable B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7
How Do We Execute the AF Bus Ops Plan? End User Business Outcomes Modernized Microservices Custom Dev Contained # of APaaS offerings APaaS EBS as a technical standard Foundational; Resources and capacity to flow • Enterprise (vice backlog) Decisions requests for • Centrralized service Control • Decentralized Execution B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7
How Do We Execute the AF Bus Ops Plan? End User Business Outcomes Modernized Microservices A deliberately architected, Custom tightly integrated Dev Contained # of APaaS technology baseline that offerings must be managed as a APaaS “thing” - Who is the architect? EBS as a technical Who is the manager? - standard Foundational; Resources and capacity to flow • Enterprise (vice backlog) Decisions requests for • Centrralized service Control • Decentralized Execution B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7
How Do We Execute the AF Bus Ops Plan? End User Business Outcomes Modernized Microservices A deliberately architected, Custom tightly integrated Dev Contained # of APaaS technology baseline that No resources + no offerings must be managed as a APaaS “thing” - Who is the architect? architecture + no manager = EBS as a technical Who is the manager? - standard Foundational; no plan Resources and capacity to flow • Enterprise (vice backlog) Decisions requests for • Centrralized service Control • Decentralize d Execution B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7
AF Integrated Business Operations Environment (IBOE) How We’ll Enable the Air Force Business Operations Plan DCIO | DCMO CDO B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7 Our Organization and Operations are Part of the IBOE Architecture
Air Force Digital Business Transformation • 442 Systems • X Systems • 331 Business • 331 Business Outcomes Outcomes • Deliberate, managed and • Ad hoc comprehensive architecture CCE/Shared Services FM A1 CCE A4 AQ 2019 202X B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7
B r e a k i n g B a r r i e r s … S i n c e 1 9 4 7 19
Recommend
More recommend