1. IEEE Systems Council Presidents’ Summits Conclusions “Planning Our Future…Together” Systems Council AdCom 2008-10-04 GP45126001.ppt Paul E. Gartz & Elliot Sloane Past President, IEEE Systems Council; Chair, EMBS Healthcare SoS 2008-10-03

2. Systems Council Presidents Summits Goal: Start Next Phase in Sys C Growth Propose New Model for an IEEE Council to “Work Together” w/S-Cs on Products & Services Create a Team w/Member S/Cs & Share Resources Achieve Highest Goal of Systems C to work “…systems of national and global significance…” Stabilize and Grow Sys C Business Plan

3. Systems Council Societies w/Interest = Member, Systems Council= Potential Member, Systems Council

4. What Was Decided at Presidents’ Summit I? 2008-02-16, 17; Louisville KY, USA Engaged Dialog & Ideas Presidents Liked Win/Win/Win Sys C Should Focus on a Specific SoS…not Generic Start a Joint SoS Conference in 2010 Properly Manage Risk Presidents Will Decide in June…then Act

5. Infrastructure SoS Defense SoS Earth Decisions SoS (e.g., GEOSS+) Transportation SoS Provide Roads, Ports, Power, etc. Emerging Systems-of-Systems (SoS) Markets Defend Country…Internal/External New Markets + Societal Benefits Observe & Predict Earth Transport People and Cargo Some Major Societal Functions Health SoS Assure Human Health What’s New = Better Interoperability Privacy SoS Assure Human Privacy (& Security?) Somewhat Country Unique Top Candidates from Summit I

6. Global Healthcare System Interoperability = GROWTH Market. (e.g., Elliot Sloane = Co-chair Healthcare Enterprise & Chair, SoS Tech Committee, Healthcare FranceUSAGermanyItalyJapanUKCanadaKoreaTaiwan Norway HollandSpainChina Year 1 (1999) Year 2 (2000) Year 3 (2001) Year 4 (2002) Year 5 (2003) Year 6 (2004) Year 7 (2005) Year 8 (2006)

7. Goals for Presidents’ Summit II Choose One SoS for Joint Conference Presidents Will Choose…Not Systems Council Understand Member S/Cs’ Value Needs and Address Presentations on Key SoSs Develop Conference Roll-out Plan Funding and Sponsorship Plan; MOUs/MOAs Venue: Where, When? Conference Scope: How? Conference Program Committee Team Oversight Plan Explore Other Joint Opportunities…Later

8. Presidents’ at Summits Chose… Start w/HealthCare SoS Market Start w/2010 Conference in N. Am. Joint Conference Also includes GEOSS Health and Privacy Foci 1-2 Reps from each Society Set up and Run Tracks in FoI of Society EMBS = Key 1 st Meeting of Conference Committee ~Mid November

9. Systems Council Societies w/Interest = Member, Systems Council= Potential Member, Systems Council

10. Post-Summit Sys C Decisions & Actions Systems C 2010 Conference Team Conference Co-Chairs = Paul Gartz/Elliot Sloane; Reps from Each Participating S/C Member + ICEO Operates Like Any Conference…Bottom Lines to AdCom Reports to Sys C and also Member S/Cs S/C Commitments & Reps EMBS Board Review + Commitment; 8/20/08 AESS Board Review + Commitment; 9/29/08 Others Coming on Board in Oct 10/xx/08 Next Step Planning & Meetings 1 st Joint Conference Committee Meeting 11/xx/08 Plan Likely to Proactively Structure Conf & Invite Papers

11. Sys C Decisions Needed Agree on Overall Direction Scope: Joint Conference on Healthcare SoS in N Am. Timeline: Feb – Jun, 2008 = S/C Presidents Support Jul – Oct, 2008 Conference Committee Formation ~Mar, 2009 Plan/Finances Review w/Sys C + S/Cs ~Jun, 2009 Venue Committed; CFP ~Jul, 2009 – May, 2010 Pre-implement in S/C Conferences ~Nov, 2010 Conference Approve Finances…if Any Needed No Funds Needed Now…Likely No Operating $ Needed Likely No S/C Funding, but “Contributions” Funds = Non-operating Budget (Standard IEEE Process)

12. Why are We Here? Basic Premise of Presidents’ Summits If Systems C “Works Together” w/Member S/Cs, We Can create a Win/Win If Systems C Succeeds Alone it’s a Win If We All Work w/IEEE Vision & Leadership on Societal Challenges, We can Create a Win/Win/Win Find a “Working Together” Model

13. - “Systems of Global and National Significance” Implies Systems-of-Systems, Nations and Transnational “Practitioner Focused” Includes All System Aspects for Holistic Look “Living Systems” & HMI (Human-Machine Interface) Business, Economics, Politics, Marketing Industry, Academia, Government, Lay Public Management and Technical Bottom Line Performance Line RAA Systems Council Scope (FoI) As Modified from 1st Meeting, September 2005, Montreal We are an OU of “Practice”

14. How are SoS “Glued” Together? With Common IEEE Systems, Technologies, Theory, Methods Customized to Each Specific SoS Infrastructure Transportation Security Earth (GEOSS) Healthcare SoSs SoSs Need IEEE’s Breadth & Depth and Vice Versa Sensors Signal Processing Common- ication tbd Navigation Geo- Spatial Data Power Networks & Theory Data Mining & Info Fusion Systems Engineering Computing, Software Control EM&B ITSS AESS OES P&ES PES GRSS MTT CASS Computer Society ComSoc EMC Control Society CIS SMC RS PSES SPS IEEE Societies

15. Emerging Systems-of-Systems (SoS) Markets Humans Corpora- tions Earth Govern- ments End Beneficiaries Infrastructure SoS Human Privacy & Security SoS Defense SoS Transportation SoS Earth Decisions SoS Human Healthcare SoS SoS Computer IMSS GRSS EMC EM&B Control Systems CASS CIS ComSoc Signal Processing Education OES MTT ITSS Product Safety Reliability P&ES SMC Technologies & Systems

16. Why Should You Care about SoSs? Where Money Flows Will Change!!! Global “Earth” Issues Recognized & GEOSS Formed Global Healthcare Crisis Recognized Affecting Humans & Business Global Defense/Security Investments are Already Changing Defense & Security will Link & Embrace “Dual Use” & Civil Sector Macro Transportation Issues: Land, Sea, Air New Research Grants and Business Growth Opportunities SoSs will Emerge as Macro-Integrators SoSs will Specify Architecture Frameworks & New Requirements Telecomm/Nav/Computing/etc all used by SoSs in New Ways Earth Predictions are Key to Most

17. Infra- structure DefenseGEOSSTrans- portation Emerging Systems-of-Systems (SoS) Markets HealthPrivacy Communications Computing Reliability Sensors Info Fusion Robotics Systems Eng Data Security Power Safety/Availability Test & Verification Functions Needed

18. Market Scope Implications Sys C May Want a Sub-market for Each SoS GEOSS, Healthcare, Security, Infrastructure, Transportation, etc. Separate Conference, Pubs, Outreach, etc. for Each Sys C May Want Variants by Region Special “Events”/Outreach by Regional Interests/Concerns E.g., “Security” is a National Concern and may want differences by region So “Transnational” Becomes Super Important Need Ways to Organize and Partner for Each None of these needs can be well met without S/C teaming

19. Observations…Issues & Opportunities Major Societal Issues are Escalating & Need Technical Help & Holistic Systems Thinking Industry says to IEEE: “Do More Integration” IEEE Organizes by Independent OUs S/Cs and Sections Largely Work Separately But Major Businesses and Issues Cross IEEE Societies Good IEEE Vision, But Few Work Together Seize Opportunity & Lead Bottom Up

20. How Do Sys C Societies Benefit? Systems Council Creates a New Context for S/C’s SoS Are Larger, More Complex at National/Global Levels Generates New Research Topics, Curricula, Grants for Academia Brings Business Opportunities and Outreach to Industry Brings Integrated Technical Help to Government Problems Works Pressing and Interesting Societal Issues for S/C Members Re-brands IEEE to a One-stop “Systems Solution House” Conferences, Pubs, Technical, Education Run Parts of New Conferences and New/Special Publications Market and Income Growth; NextGen Service to Members/Society New/Expanded Committees, Technical Opportunities Lots of Technical Outreach Needed…DLs, Expert Now/Tutorials Standards…New Anticipated…in “Layers”