MBSE Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Production and Logistics Systems Modeling Challenge Team ======

===== Purpose ===== 
The production and logistics modeling team is advancing the practice and adoption of formal system modeling and model-based systems engineering methodologies in production and logistics systems development and operations. 
Specific challenges in providing a foundation to production and logistics [systems] engineering are the lack of:
  * Standard reference models
  * Well-structured engineering design methodologies
  * Integrated analysis models and tools available to support design and operational decision-making.

The purpose of this challenge team is to increase the availability of reference models, awareness of these models and methods, and successful use of MBSE in the production, logistics, and industrial engineering communities.

===== Scope =====
The systems of interest are discrete event logistics systems (DELS). They can be described as:
  * Structure: a network of //resources//, arranged in a //facility//; each resource has one or more processing capabilities that have a (maximum) capacity;
  * Behavior: //products// flow through the network and are transformed by //processes// executed by resources; a process may require  capabilities of multiple resources; a transformation can change location, age, or condition of a product.

These systems include, but are not limited to: 
  * supply chains, 
  * production & manufacturing systems, 
  * transportation networks, 
  * warehouses, 
  * and health care delivery systems.

The adjective “discrete” recognizes the nature of the products, flows, and processes. Products are discrete units, e.g., individual product units or components of product units, or batches of product units, flowing through the network separately. Processes have well-defined start and end times, e.g., the start of a machining or heat-treating process and completion of same, even though our knowledge of the well-defined time may be uncertain.

The scope of team activities is broad, covering almost all aspects of DELS. It might be narrowed and/or broken into smaller projects and outcomes based on the interest of team members. The scope can be defined along three axes:
  * System Lifecycle Integration: conceive, design, realize, service, retire (SeBoK)
  * Enterprise Integration: Process Control, SCADA, MOM, & ERP. (ISA-95 hierarchy).
  * Product Lifecycle: procurement, manufacture, sustainment, retirement. (SCOR: Source, Make, Deliver, Return)


===== Measure of Success ===== 
General measures of success of this working group include the number of members, joint activity partners, and activities successfully completed over the long term (years). The activities will be determined by our target stakeholders:
  * __Domain Experts__: Capture and operationalize knowledge about DELS design and operation; enable access to analysis methods through system-analysis integration (SAI) methods.
  * __Modeling End Users__: Increase availability of domain-specific reference models, model libraries, and patterns to support successful usage of system models and model-based methods.
  * __Analysis Experts__: Connect analysis requirements (from domain experts) to development and deployment of analysis methods. Capture analysis models and methods components of MBSE for DELS, advance analysis integration and interoperability/SAI.
  * __Tool Developers__: Connect analysis requirements (from domain experts) to development of better analysis tools, e.g. simulation, and to deployment of analysis tools  derived from and integrated with formal system models (industry-grade SAI tools).
  * __Standards Development Organizations__: Leverage DELS models to integrate related standards and identify requirements for DELS standardization.
  * __Enterprises__: Increase successful use of system models and MBSE; integrate production and logistics functions with product lifecycle modeling (PLM) to create richer use case demonstrations of MBSE value (ROI). 

===== Plan Overview / Description =====
Phase 1: (Time period to be established)
  * Expand membership, share and refine the charter, develop a long-term plan, and gain team buy-in to long term plan.
  * Bring membership up to a common level of DELS modeling, by developing and delivering DELS modeling tutorials.
  * Define and demonstrate capabilities for DELS modeling
  * Identify target products for near-term work by the team:
    * Common & domain-specific reference models and architectures (demonstrated using SysML)
    * Integrated MBSE / design methodologies for DELS
    * Integrated analysis tools (SAI for routine, common analysis models)
    * Suitable use cases, and test cases.

===== Schedule ===== 
^Date^Milestone^Status^Point of Contact^Materials^
| 2017-01 | Initial presentation at IW17 (Torrance, CA) | completed | Timothy Sprock | {{:mbse:prodlog:iw2017_-_presentation_-_2017jan26.pdf | Presentation}} |
| 2018-01 | Status presentation & Team Meeting at IW18 (Jacksonville, FL) | completed | Timothy Sprock | {{:mbse:prodlog:productionlogisticsmodeling_iw2018.pdf | Presentation}}|
| 2019-01 | Status presentation & Team Meeting at IW19 (Torrance, CA) | completed | Timothy Sprock | {{:mbse:prodlog:productionlogisticsmodeling_iw2019_v6.pdf | Presentation}}|
| 2020-01 | Status presentation & Team Meeting at IW20 (Torrance, CA) | completed | Timothy Sprock | {{:mbse:prodlog:productionlogisticsmodeling_iw2020.pdf | Presentation}}|
| 2021-01 | Status presentation & Team Meeting at IW21 (Virtual) | completed | Leon McGinnis | {{:mbse:incose_mbse_iw_2021:iw2021_production_logistics_challenge_team_.pdf | Presentation}}|



Challenge team weekly meeting at 11 am (Eastern) Fridays.
To join the Meeting: https://bluejeans.com/419553114


===== Team Members =====

Challenge Team Lead / POC: Tim Sprock, NIST: timothy.sprock@nist.gov

Co-Lead: Leon McGinnis, Georgia Tech

Co-Lead: Conrad Bock, NIST
MBSE Wiki

User Tools

Site Tools

Page Tools
