GP45126001

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

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. HealthSoS PrivacySoS Top Candidates from Summit I Earth DecisionsSoS (e.g., GEOSS+) New Markets + Societal Benefits TransportationSoS DefenseSoS Somewhat Country Unique InfrastructureSoS What’s New = Better Interoperability Emerging Systems-of-Systems (SoS) Markets Some Major Societal Functions Assure Human Health Assure Human Privacy (& Security?) Observe & Predict Earth Transport People and Cargo Defend Country…Internal/External Provide Roads, Ports, Power, etc.

6. Global Healthcare System Interoperability = GROWTH Market. (e.g., Elliot Sloane = Co-chair Healthcare Enterprise & Chair, SoS Tech Committee, Healthcare Norway Germany Holland Canada Taiwan France Japan Korea China Spain USA Italy UK Year 7 (2005) Year 8 (2006) Year 1 (1999) Year 2 (2000) Year 3 (2001) Year 4 (2002) Year 5 (2003) Year 6 (2004)

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 • 1st 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 • 1st 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. Find a “Working Together” Model Why are We Here?Basic Premise of Presidents’ Summits • If Systems C Succeeds Alone it’s a Win • If Systems C “Works Together” w/Member S/Cs, We Can create a Win/Win • If We All Work w/IEEE Vision & Leadership on Societal Challenges, We can Create a Win/Win/Win

13. Systems Council Scope (FoI) As Modified from 1st Meeting, September 2005, Montreal • “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 - We are an OU of “Practice”

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

15. Technologies & Systems SoS EndBeneficiaries CASS IMSS TransportationSoS Humans CIS ITSS Computer MTT Infrastructure SoS HumanHealthcareSoS Earth ComSoc OES Control Systems P&ES Corpora-tions Earth Decisions SoS Human Privacy & Security SoS Education ProductSafety EM&B Reliability Govern-ments Defense SoS EMC SignalProcessing GRSS SMC Emerging Systems-of-Systems (SoS) Markets

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. Emerging Systems-of-Systems (SoS) Markets Health Privacy GEOSS Trans-portation Defense Infra-structure Functions Needed Communications Computing Reliability Sensors Info Fusion Robotics Systems Eng Data Security Power Safety/Availability Test & Verification

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”