Trans-Atlantic Modelling
and Simulation for
Cyber-Physical Systems

TAMS4CPS Theme 4 US Workshop

TAMS4CPS will hold its next US workshop on 17th and 18th March 2016 at University of Texas, San Antonio, US.

The workshop will be the fourth in a series that aims to identify collaboration opportunities between the US and EU.  Each workshop focuses on a theme in the area of modelling and simulation for CPS, and will consist of activities to:

  • Introduce EU and US perspectives on the state of the art, strengths and weaknesses, and vision;
  • Identify and prioritize trends and drivers, markets, technologies and enablers in the field;
  • Elicit “test cases” (instances of CPSs and CPS design challenges) that can be used to benchmark modelling and simulation products (methods, tools, etc.) against the state of the art and against each other;
  • Identify research collaboration priorities and implementation plans.

 

This workshop focuses on Theme 4 of TAMS4CPS “MBSE applied to computing platforms and energy management for Cyber-Physical Systems”. This theme is concerned with energy efficient computing and includes the improved management of large distributed network devices. The emphasis of this theme will be on the user of MBSE to describe, and hence manage large networks that dynamically reconfigure. Environmental modeling will also be important in this theme.

Agenda

The workshop will consist of 4 half-day sessions:

  • Mutual introduction: EU and US perspectives on the state of the art, EU and US strengths & opportunities, EU and US vision. (The purpose is to get to know more about each other, but the session also provides the participants with the opportunity to introduce a particular topic that the participant feels it is important for the workshop)
  • Roadmapping exercise (all): trends &drivers; needs/markets; opportunities; technologies (either current or needed); research directions; enablers/barriers.
  • Elicitation of test cases (group activity): test case specification will be developed. A description of what a “test case” may consist of can be found in the accompanying document.
  • Identification of research collaboration priorities and planning the way forward. (As part of this session we will address the topic of “funding mechanisms and priorities”, as such we will invite the US point of contact to say a few words on US funding plans/priorities for CPS and US mechanisms available for funding)

 

A more detailed agenda and joining instructions are provided to participants via e-mail. Preparational materials are available under resources.

 

What is a test case?

Within the workshop, we aim to identify and work up one or more “test cases”. Test cases act like exemplars that will serve as demonstrators for stretching the capabilities of CPS modelling tools and techniques. The role of test cases is to provide M&S developers with a means to evaluate their product against the state of the art and other products. The format of a test case may vary depending on the M&S research area: some may require an accompanying data set, whereas others may just be a description of the use case. The minimal requirement for a test case is a detailed enough description to provide an unambiguous specification of a cyber-physical system. Ideally a test case should contain specifications for three different competency levels to provide a form of benchmark for an M&S product. These competency levels are:

  • Basic (now): this would provide “entry level” requirements for an M&S product; such a test case should be achievable by the current state of the art
  • Moderate (3-5 years in the future): this would stretch the M&S product in an incremental way, expanding the state of the art in some significant, but tractable direction
  • Advanced (7-10 years in the future): this would be a futuristic vision of what an M&S product should be able to achieve

 

Promoting a test case can potentially bring the attention of researchers, tool developers or funding bodies onto key modeling and simulation challenges to address in a particular domain.