‹‹ Wed Afternoon Thu Morning Thu Afternoon Fri Morning Fri Afternoon Saturday ››


Thursday Afternoon Session Details

For October 12, 2017, afternoon session schedule click here.


Section Date Time October 12, 2017, 1:00 pm – 1:40 pm
Session Session 1a
Presenters Mohamed Elshal, Hazim El-Mounayri, and Rapeepan Promyoo
Title Application of MBSE and SysML in Patient Workflow Modeling
Summary Healthcare system in the United States has multiple issues regarding quality, rising cost and outcome of patient care process. Several initiatives have been led regarding the need for systems engineering methodologies and tools to address healthcare delivery challenges for patients and healthcare organizations; one of which is a collaboration between Eskenazi Health Hospital, Cientive Group Inc. and Indiana University to address resource allocation, cost and crowding inside Eskenazi Emergency Department (ED). A systems level approach is followed to model and predict ED patient flow and determine resource allocation and cost. The systems model provides a formal approach and inherent rigor to capture and communicate system behavior. ED domain model is constructed based on process documents, interviews and ED observation. Data requirements are identified, and data is collected and analyzed from various sources to build statistical models. Stakeholder requirements are gathered based on interviews with key stakeholders involved to capture human resource information and interactions. Model-based systems engineering framework is developed using OMG Systems Modeling Language (SysML); which enables model reuse, supports multiple system views, and enhance system’s verification and validation processes. Systems tools such as Cameo Systems Modeler from NoMAgic™ and Microsoft Visio are used to design multiple system views of the ED. Validation is conducted through continuous cycles; where requirements, system diagrams and outcome measures are validated directly with system’s stakeholders; as well as systems engineers and simulation experts. ED performance outcomes are evaluated by mapping those system views into an executable model using a powerful discrete-event simulation tool: Tecnomatix from Siemens™. This executable model is used to replicate ED system current “As-Is” state, and estimate ED’s measures of efficiency and effectiveness. In conclusion, systems level approach provides a deeper and clearer understanding of the internal and external entities that form the ED system. The comprehensive views allow us to focus and study the dynamics of patient flow across the ED. Results from simulation of the executable process models will be presented. The results will focus on the replication of the observed ED behavior.


Section Date Time October 12, 2017, 1:45 pm – 2:25 pm
Session Session 1b
Presenters Matthew Hause
Title Interface Management with MBSE – from Theory to Modeling
Summary Systems interoperate using interfaces. They exist between capabilities, organizations, people, systems, people and systems, systems and nature, systems of systems, and so forth. Interfaces are used to support both system to system communication as well as supporting the complete set of enterprise goals. Interfaces are where the most interesting things happen; and where most things go wrong. This presentation addresses system interface-management issues and the benefits of model-based approaches. An initial focus will be placed on interface information content that needs to be addressed at each level of system decomposition – from external stakeholders to system boundary to, eventually, system component- to-component. The focus will then shift to methods for reducing interface management theory to model-based and functional/logical design practice. We will also cover system interconnection and communications, how they change, operate and evolve over time to implement mission goals and to satisfy stakeholder needs. Key subject areas include: a) Defining stakeholder goals and required capabilities; b) Interface definition with MBSE; c) Logical Architecture Interfaces; d) Physical Architecture Interfaces; e) Allocation across cross cutting views; f) How behavior drives interfaces which drive behavior; g) Defining interaction requirements; h) Implementing effective and testable interface specifications; i) Traceability throughout the architecture; and j) Service Oriented Architectures.


Section Date Time October 12, 2017, 1:00 pm – 1:40 pm
Session Session 2a
Presenters Bobby Norton
Title Improving systems architecture with DSM, modularity, and a dash of network science
Summary If function A in a program makes a call to function B, then A depends on B. Replace "function" with other artifacts such as cloud server instances, database tables, message queues, and web services, and we have the start of a network model of an engineered system's structure...the architecture. The Dependency Structure Matrix, also known as the Design Structure Matrix or DSM, offers a scalable, automated visualization and analysis technique that represents the elements of a system in a scalable way and their interactions.
A DSM immediately provides a valuable visual reference to engineers and operations professionals managing and evolving a system. When combined with automated data collection through static analysis techniques, this documentation can continually evolve as the system changes. The data can then be used with community detection techniques to computationally discover modules or subsystems: Vertices that are highly connected amongst themselves and relatively weakly connected to vertices in other groups. Combined with a scoring model of modularity, we gain an objective means by which we can automatically describe, model, and optimize system architecture.
This talk will explore findings from applying this approach to mining architecture data from a collection of open-source projects. The tools used were built in Python and JavaScript and are also open-source, ensuring repeatable results for other researchers and practitioners. This talk will immediately benefit systems engineers that need to organize teams and reduce development or support cycle times in software-intensive systems. Attendees interested in applications of network science to systems engineering will also find useful takeaways.


Section Date Time October 12, 2017, 1:45 pm – 2:25 pm
Session Session 2b
Presenters David Quimby
Title Scaling the Creative Enterprise with Systematic Innovation
Summary Doug Engelbart didn’t invent the mouse, he discovered it. Identifying patterns of design and innovation that are common to various contexts and applying them within a product category, or even across product categories, is a cognitive strategy that enjoys an advantage over processing each creative opportunity in isolation from previous ideation. We’ll introduce the concept of systematic innovation and identify the various genres of systematic techniques. We’ll explore the history and the potential advantages and disadvantages of systematic approaches to innovation and we’ll compare the theory to our practical experiences. We'll ponder a rather extreme notion in which systematic innovation might amplify itself by applying itself to itself (invoking the mathematical, or computational, concept of recursion). We’ll review a practical application of a rather remarkable disruption in the user experience domain that resulted from a systematic approach.
This session will equip individual inventors/innovators, innovation/technical leaders, innovation groups, and technical organizations in the following ways: a) challenge conventional thinking about innovation/creativity; b) gain practical access to the broad field of systematic innovation with the ability to investigate/activate it more deeply; c) bridge gaps/eliminate barriers to previously undiscovered territory; d) differentiate opportunities and separate signal from noise in the opportunity landscape; e) focus resources/cognitive energy on fewer, more sustainable ideas; f) make innovation more repeatable across time for both individuals and groups; and g) make innovation more scalable across the organization.


Section Date Time October 12, 2017, 1:00 pm – 2:25 pm
Session Session 3
Presenters Steve Cantley
Title The Columbia Accident - Enduring Lessons From An Insider's Viewpoint
Summary This session is oriented toward Systems Engineers and about the loss of the space shuttle Columbia in 2003. It focuses on the event, how it came to be understood, and my takeaways: stakeholders that levy conflicting expectations, analytical model validation issues, an operational mindset for a still-experimental vehicle system, organizational entropy, and the way promotion within an organization, like the manned spaceflight community, does not happen unless one adopts the core beliefs of the organization -- so change is slow and painful.


Section Date Time October 12, 2017, 3:00 pm – 6:00 pm
Session Session 4a
Presenters Pawel Chadzynski
Title Convergence of MBSE and the Product Innovation Platform
Summary Vehicle complexity is increasing dramatically as technologies rapidly evolve and new modes of transportation emerge. This increase is being fueled by increased use of software, rapid advances in chip design and electrification of traditional mechanical systems. Vehicle design is now a complex systems challenge involving MBSE, design in multiple disciplines (mechanical, electrical, electronic and software) and simulation. Engineers are getting work done today by brute force – tracking via spreadsheets, valiant efforts by “people integrators” and lots of rework. IT systems are inadequate to manage the increasing volumes of models and designs being created (including version and revisions), BOMs and configurations, simulation results, changes, etc. This is limiting the rate at which progress can be made without compromising passenger safety. Legacy PDM is no help here, focused on “Science of Engineering” MCAD, and not flexible enough to deal with complex systems engineering challenges and real world company processes. The industry needs a new approach that supports systems engineering, manages designs, configurations and change across multiple disciplines. This presentation will discuss the combination of MBSE and a Product Innovation Platform that demonstrates design reuse and cross-discipline trade-off analysis. The example to be shown will illustrate the modification of an existing model and the optimal selection of existing parts to meet new requirements. The workflow will cover import into SysML (from the Platform) of the selected system architecture and requirements, modeling the trade study, linking parts parameters in the Platform to logical design characteristics, dynamic trade execution, and storing results back into the Platform. It is envisaged that adoption of the tools and methods to be shown will keep companies on track to meet aggressive connected/autonomous car goals while reducing the likelihood of costly recalls to resolve issues or, worse still, brand-destroying safety incidents while maintaining innovation by freeing engineers to focus on high value tasks.


Section Date Time October 12, 2017, 3:40 pm – 4:30 pm
Session Session 4b
Presenters Rajat Gupta, Hazim El-Mounayri, and Shuning Li
Title Validating MBSE-PLM integration through automatic generation of Systems Requirements Document
Summary Mass customization, small lot sizes, reduced cost, high variability of product types and changing product portfolio are characteristics of modern manufacturing systems during life cycle. A direct consequence of these characteristics is a more complex system and supply chain. Product lifecycle management (PLM) and model based system engineering (MBSE) are tools which have been proposed/implemented to address different aspects of this complexity and resulting challenges. Our previous work has successfully implemented a MBSE model into a PLM platform. More specifically, Pattern based system engineering (S* pattern) models of systems are integrated with TEAMCENTER® to link and interface system level with component level, and streamline the lifecycle across disciplines. The benefit of the implementation is two folded. On one side it helps system engineers using system engineering models enable a shift from learning how to model to implementing the model, which leads to more effective systems definition, design, integration and testing. On the other side the PLM platform provides a reliable database to store legacy data for future use also track changes during the entire process, including one of the most important tools that a systems engineer needs is an automatic report generation tool. In the current work, we have configured a PLM platform (TEAMCENTER®) to support automatic generation of reports and requirements tables using a generic Oil Filter system lifecycle.
There are three tables that have been configured for automatic generation which are Feature definitions table, Detail Requirements table and Stakeholder Feature Attributes table. These tables where specifically chosen as they describe all the requirements of the system and cover all the physical behaviors the oil filter system shall exhibit during its physical interactions with external systems. The tables and the diagram are core content for a typical systems engineering report. With the help of the automatic report generation tool, it is possible to prepare the entire report within one single system, the PLM system, to ensure a single reliable data source for an organization. Automatic generation of these contents can save the systems engineers time, avoid duplicated work and human errors in report preparation, and encourage standardized documents in an organization.


Section Date Time October 12, 2017, 3:00 pm – 4:00 pm
Session Panel Discussion 1
Moderator Sean McCoy
Panelists David Holst, Michele Zoromski, Bobby Norton, and James Hummel
Title Systems Engineering - The Key Elements of Success
Summary This panel-discussion will explore the elements that contribute to the successful adoption of Systems Engineering within an organization. The 4 key areas to be explored are: 1 - Culture makes it happen 2 - People make it happen 3 - Data makes it happen 4 - Management support makes it happen. Some other ideas worth exploring – process makes it happen, education makes it happen, and “living in the gaps” makes it happen.
We all know that it takes all of these ingredients, in some measure, for Systems Engineering to be successful. The panel will explore what happens if one, or more, are missing.


Section Date Time October 12, 2017, 3:00 pm – 3:40 pm
Session Session 5a
Presenters Angela Robinson, Gael Blondelle, and Ronald Houde
Title ISO/IEC 29110 Deployment Packages and Case Study for Systems Engineering: The "Not-So-Secret" Ingredients That Power the Standard
Summary Very small entities (VSEs) play an increasingly important role in the global economy. The products they develop are often integrated into products made by larger enterprises. Clients, furthermore, demand of the VSEs that they assume a much broader role, spanning the entire development life-cycle of the product instead of being limited to a “build-to-print” approach. The ISO/IEC 29110 systems engineering management and engineering guides were developed mainly from ISO/IEC/IEEE 15288 to address this new reality, to exploit the lean and efficient nature of VSEs and to adapt to their typical budget and resource constraints. By design, the management and engineering guide is supported by Deployment Packages (DP), the development of which was taken on by the INCOSE VSE Working Group. A DP is a set of artefacts designed to facilitate the implementation of the management and engineering guides of ISO/IEC 29110 by VSEs. In tune with the need for low cost and flexibility, Open Source software tools are emerging to support VSEs and provide a bridge with “Big League” development life-cycle toolsets. Finally, to make the deployment of ISO/IEC 29110 possible in VSEs, training packages, supported by relevant pilot projects help VSE personnel learn how to apply all of the above. This paper describes the Systems Engineering DP for Requirements Engineering (RE DP) and shows how it can be applied using the Rover Case Study developed under the Eclipse Foundation PolarSys Working Group.


Section Date Time October 12, 2017, 3:40 pm – 4:30 pm
Session Session 5b
Presenters Michael Vinarcik
Title 20 Million Leagues Under The Sea of Stars: The NeMO Orbiter Modeling Project
Summary System modeling is difficult to learn without hands-on exercises. The experience of translating real concepts, constraints, and capabilities into modeling elements is the most effective way to develop modeling competence. This paper will discuss the first-ever two-term modeling project at the University of Detroit Mercy. Student teams were given the science goals for NASA's Next Mars Orbiter (NeMO) as the foundation of a SysML model that spanned Systems Architecture and Systems Engineering courses. This presentation will discuss the practical aspects of leading multiple student teams as they learn SysML, tool user interfaces, and underlying systems engineering concepts.


Section Date Time October 12, 2017, 5:00 pm – 7:00 pm
Session Reception
Presenter STEM Demonstrations - Dan Stone


Section Date Time October 12, 2017, 7:00 pm – 9:30 pm
Session Banquet
Presenters Comedy Sportz Competition
Title Comedy Improv

‹‹ Wed Afternoon Thu Morning Thu Afternoon Fri Morning Fri Afternoon Saturday ››