1 / 7

Enterprise Systems Engineering One Systems Engineer's View

Enterprise Systems Engineering One Systems Engineer's View. Stephen J. Sutton, P.E. Enterprise Systems Engineering (ESE) Panel Presentation & Discussion INCOSE Chesapeake Chapter 15 March 2007.

zwi
Download Presentation

Enterprise Systems Engineering One Systems Engineer's View

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enterprise Systems EngineeringOne Systems Engineer's View Stephen J. Sutton, P.E. Enterprise Systems Engineering (ESE) Panel Presentation & Discussion INCOSE Chesapeake Chapter 15 March 2007 The opinions presented tonight represent my personal views and are not those of my employer or INCOSE

  2. Topics • Definition • Challenges • Skills and Tools

  3. ESE Definition • Engineering for the lifecycle of a complex entity • An organization (company, agency, a government) • A multi-national project (GEOSS) • This is not engineering of a well defined system with all the constraints are clear and bounded

  4. Challenges • Recognize that ESE corresponds to activities for re-engineering, strategic planning – not all technology-focused engineering • Following a process and method • Doing the hard work so that subordinate activities will be successful • Finding the right people

  5. Skills and Tools • An ESE’s Characteristics • Knows what questions to ask and information to capture • Look at the system in its environment • Work with people • Can identify or elicit needs (goals, missions, capabilities, MOEs, metrics….) • Addresses multiple levels of abstraction • Uses tools effectively • Willing to live with not getting to the gory details of technology and implementation – but having to understand the technology and implications for implementation: Concentration on activities, information, products and not on the physicality of the enterprise • Willing to live with uncertainty

  6. Strata of EnterpriseTransformations • External Environmental Constraints Transformation 1 • Lines of Business/Business Functions/Products and Services • Top Level Organization Structure/Business Geopgraphy • Strategic Plans/Measures & Metrics/Timelines • General Business Rules Transformation 2 • Operational View (capabilities, information/flows, products, services, processes) • Expanded Organization Structure/Locations & Relationships • Business Master Plan/Master Schedules • Expanded Business Rules Transformation 3 • Systems View (Master Transition Plan, Segment Definition) • Capabilities Roadmaps • Roles and Responsibilities • Detailed Business Rules Transformation 4 • Material (Systems) and Non-material (e.g., doctrine) solutions

  7. Summary • Enterprise engineering poses interesting challenges for an SE • SE is SE but the enterprise context presents differences • Certain skills take forefront

More Related