FEAT Description: Fuel Economy Federation Agreements

Status:
Subtitle: SISO-REF-068.1-2017
Acronym:
Document Number:
Taxonomy:
Security Classification:

metadata

identification

Title

VALUE: Fuel Economy Federation Agreements

SUBTITLE: SISO-REF-068.1-2017

Security

Releasability

VALUE: A: Unlimited distribution

Version

VALUE: 0.3

modification Date

2015-12-04T00:00:00

authors

point Of Contact

REFERENCED PERSON: Katherine L Morse

TYPE: person

ROLE: Author

point Of Contact

REFERENCED PERSON: Björn Möller

TYPE: person

ROLE: Author

point Of Contact

REFERENCED PERSON: David Drake

TYPE: person

ROLE: Author

point Of Contact

REFERENCED PERSON: Bobby Chawla

TYPE: person

ROLE: Author

rights

PRIVACY ACT: false

INTELLECTUAL PROPERTY: false

COPYRIGHT: false

notes

The Fuel Economy Federation is an analysis federation that is intended to study and compare the fuel consumption of vehicles under different conditions. This federation agreement is the design specification (or contract) for the federation. It provides requirements for the interoperability aspects of any participating federate.The Fuel Economy Federation is based, with permission, on "The HLA Tutorial," Copyright Pitch Technologies AB, Sweden, 2012. A full copy of the tutorial is available at http://www.pitch.se/hlatutorial.

referenced Docs

STATUS: TBD

remote Document

VERSION: v1.0

FORMAT: pdf

DATE: 2012-07-01T00:00:00

TYPE: simple

HREF: http://www.pitch.se/hlatutorial

Title

VALUE: The HLA Tutorial

SUBTITLE: A Practical Guide for Developing Distributed Simulations - Part I

Security

Releasability

VALUE: A: Unlimited distribution

description

This tutorial covers everything from an overview of what HLA is used for, to the practical design and development of HLA based systems. This tutorial is available as a stand-alone document or as part of the HLA Evolved Starter Kit. This kit contains software and samples with source code that you can run on your own computer, study, experiment with, extend or even use as a starting point for your own HLA development. This document contains instructions about practical labs that you can perform for many of the chapters.

remote Document

VERSION: 2010

DOC NUMBER: 1516

FORMAT: PDF

DATE: 2010-08-18T00:00:00

TYPE: simple

HREF: http://standards.ieee.org/findstds/standard/1516-2010.html

Title

VALUE: IEEE Standard for Modeling and Simulation (M&S) High Level Architecture (HLA)

SUBTITLE: IEEE 1516-2010

ACRONYM: HLA

DOCUMENT NUMBER: 1516

Security

Releasability

VALUE: A: Unlimited distribution

description

The High Level Architecture (HLA) provides a general framework within which simulation developers canstructure and describe their simulation applications. Flexibility is the aim of the HLA. In particular, the HLAaddresses two key issues: promoting interoperability between simulations and aiding the reuse of models indifferent contexts. Three main components are described within the set of products forming the HLA. Thefirst component, the HLA Framework and Rules Specification (i.e., this standard), provides a set of ten rules that together ensure the proper interaction of federates in a federation and define the responsibilities offederates and federations. The second component, the object model template (OMT), is a necessary basis forreuse and forms a documentation standard describing the data used by a particular model. The thirdcomponent, the federate interface specification, addresses interoperability and describes a genericcommunications interface that allows simulation models to be connected and coordinated. Although theHLA is an architecture, not software, use of runtime infrastructure (RTI) software is required to supportoperations of a federation execution. The RTI software provides a set of services, as defined by the federateinterface specification, used by federates to coordinate operations and data exchange during a runtimeexecution.

address Book

people

person

Title

Dr.

Name

FIRST: Katherine

MIDDLE: L

LAST: Morse

Position

VALUE: Principal Professional Staff

Org

REFERENCED ORGANIZATION: The Johns Hopkins University Applied Physics Laboratory

Name

The Johns Hopkins University Applied Physics Laboratory

person

Title

Mr.

Name

FIRST: Björn

LAST: Möller

Position

VALUE: Vice President

Org

REFERENCED ORGANIZATION: Pitch Technologies

Name

Pitch Technologies

person

Title

Mr.

Name

FIRST: David

LAST: Drake

person

Title

Mr.

Name

FIRST: Bobby

LAST: Chawla

organizations

organization

Name

The Johns Hopkins University Applied Physics Laboratory

Type

VALUE: academia

Address Info

Address Line1

11100 Johns Hopkins Road

City

Laurel

State

MD

Country

USA

Postal Code

20723-6099

Email

TYPE: work

URL

http://www.jhuapl.edu

organization

Name

Pitch Technologies

Type

VALUE: industry

Address Info

Address Line1

Repslagaregatan 25

City

Linköping

Country

Sweden

Postal Code

582 45

Phone

TYPE: work

NUMBER: +46 13 470 55 00

Email

TYPE: work

URL

http://www.pitch.se

organization

Name

Real-Time Engineering and Simulation Inc.

Type

VALUE: industry

Email

TYPE: work

glossary

definition

Federation Object Model

TERM: FOM

definition

High-Level Architecture as defined in IEEE 1516-2010

TERM: HLA

definition

The Institute of Electrical and Electronics Engineers, Inc.

TERM: IEEE

definition

Federation Engineering Agreement Template

TERM: FEAT

definition

Simulation Interoperability Standards Organization

TERM: SISO

changelog

version

VERSION NUMBER: 0.1

MODIFICATION DATE: 2015-03-03T04:58:39.292-08:00

changes

text

First draft

version

VERSION NUMBER: 0.3

MODIFICATION DATE: 2015-12-04T00:00:00.000-08:00

changes

text

Additional inputs from section 3 of Appendix A.

design

conceptual Model

remote Document Ref

REFERENCED DOCUMENT TITLE: The HLA Tutorial

SECTION: A.2

PAGE: 67

infosec

scenario

scenario Description

text

Information about car objects will be produced by the car simulators and consumed by analysis, visualization and data collection federates. Management interactions will be produced by the Master federate and responded to by the car simulators.

architecture

remote Document Ref

REFERENCED DOCUMENT TITLE: The HLA Tutorial

SECTION: 4.2

PAGE: 17

arch Model

TITLE: Fuel Economy Architecture
Fuel Economy Architecture

member Apps

member Application

TYPE: Master

cpe-item

NAME: cpe:/generatedID:262967500257

title

Master

instance

description

text

The Master federate is responsible for the management of the execution, for example assigning scenarios, starting and stopping. There shall be exactly one Master federate in each federation.

member Application

TYPE: Car

cpe-item

NAME: cpe:/generatedID:55716396378

title

Car

instance

SIM ID: A-Brand

description

text

Car Simulator federates are responsible for modeling car objects, their movements and fuel consumptions. There may be any number of car simulator federates. Each federate may model one or more car objects.

member Application

TYPE: Analysis

cpe-item

NAME: cpe:/generatedID:174410569275

title

Analysis

instance

description

text

These are used for analysis of the simulation results during and after the execution. They may only consume data. They may not affect the simulation. There may be any number of these federates.

member Application

TYPE: Visualization

cpe-item

NAME: cpe:/generatedID:1002173103997

title

Visualization

instance

description

text

These are used for analysis of the simulation results during and after the execution. They may only consume data. They may not affect the simulation. There may be any number of these federates.

member Application

TYPE: Data collection

cpe-item

NAME: cpe:/generatedID:674019417028

title

Data collection

instance

description

text

These are used for analysis of the simulation results during and after the execution. They may only consume data. They may not affect the simulation. There may be any number of these federates.

member Application

TYPE: Car

cpe-item

NAME: cpe:/generatedID:180719683089

title

Car

instance

SIM ID: B-Brank CarSim

description

text

Car Simulator federates are responsible for modeling car objects, their movements and fuel consumptions. There may be any number of car simulator federates. Each federate may model one or more car objects.

tools

tool

TYPE: operatingSystem

ID: 166933805206

cpe-item

NAME: cpe:/Windows 7

title

Windows 7

tool

TYPE: operatingSystem

ID: 1053210785922

cpe-item

NAME: cpe:/Ubuntu 14.04

title

Ubuntu 14.04

tool

TYPE: operatingSystem

ID: 295695426189

cpe-item

NAME: cpe:/Mac OS X 10.10.4

title

Mac OS X 10.10.4

tool

TYPE: middleware

ID: 672450721800

cpe-item

NAME: cpe:/Pitch RTI 4.4

title

Pitch RTI 4.4

tool

TYPE: operatingSystem

ID: 1091846856351

cpe-item

NAME: cpe:/Windows 10

title

Windows 10

execution

execution States

execution State

NAME: initialization

remote Document Ref

REFERENCED DOCUMENT TITLE: The HLA Tutorial

SECTION: A.5 Start-up and shutdown

PAGE: 70

execution State

NAME: running

remote Document Ref

REFERENCED DOCUMENT TITLE: The HLA Tutorial

SECTION: A.5 Error handling

PAGE: 72

TITLE: Scenario and execution management
Scenario and execution management

time Management

join And Resign

middleware Agreements

management

software CM

configuration Management

type

Software CM

description

Configuration management of all components of The HLA Tutorial will be performed by Pitch using standard corporate procedures.

vva

test Plan

data

data Exchange Models

dem

NAME: Fuel Economy Federation FOM (FEF FOM)

remote Document Ref

REFERENCED DOCUMENT TITLE: The HLA Tutorial

SECTION: B

PAGE: 74

sim Architecture

architecture

architecture

HLA

version

IEEE_1516-2010

pub Sub Responsibilities

app Entry

REFERENCED APPLICATION: Master

publications

publication

dem Target Entity

DEM NAME: LoadScenario

TYPE: simple

sim Architecture

architecture

architecture

HLA

version

IEEE_1516-2010

publication

dem Target Entity

DEM NAME: Start

TYPE: simple

sim Architecture

architecture

architecture

HLA

version

IEEE_1516-2010

publication

dem Target Entity

DEM NAME: Stop

TYPE: simple

sim Architecture

architecture

architecture

HLA

version

IEEE_1516-2010

subscriptions

subscription

dem Target Entity

DEM NAME: ScenarioLoadFailure

TYPE: simple

sim Architecture

architecture

architecture

HLA

version

IEEE_1516-2010

subscription

dem Target Entity

DEM NAME: ScenarioLoaded

TYPE: simple

sim Architecture

architecture

architecture

HLA

version

IEEE_1516-2010

app Entry

REFERENCED APPLICATION: Car

publications

publication

dem Target Entity

DEM NAME: ScenarioLoaded

TYPE: simple

sim Architecture

architecture

architecture

HLA

version

IEEE_1516-2010

publication

dem Target Entity

DEM NAME: ScenarioLoadFailure

TYPE: simple

sim Architecture

architecture

architecture

HLA

version

IEEE_1516-2010

publication

dem Target Entity

DEM NAME: Car

TYPE: simple

sim Architecture

architecture

architecture

HLA

version

IEEE_1516-2010

subscriptions

subscription

dem Target Entity

DEM NAME: LoadScenario

TYPE: simple

sim Architecture

architecture

architecture

HLA

version

IEEE_1516-2010

subscription

dem Target Entity

DEM NAME: Start

TYPE: simple

sim Architecture

architecture

architecture

HLA

version

IEEE_1516-2010

subscription

dem Target Entity

DEM NAME: Stop

TYPE: simple

sim Architecture

architecture

architecture

HLA

version

IEEE_1516-2010

app Entry

REFERENCED APPLICATION: Data collection

subscriptions

subscription

dem Target Entity

DEM NAME: Car

TYPE: simple

sim Architecture

architecture

architecture

HLA

version

IEEE_1516-2010

app Entry

REFERENCED APPLICATION: Visualization

subscriptions

subscription

dem Target Entity

DEM NAME: Car

TYPE: simple

sim Architecture

architecture

architecture

HLA

version

IEEE_1516-2010

data Dictionary

STATUS: TBD

infrastructure

networking

TITLE: Network layout
Network layout

network Segment

TYPE: LAN

bandwidth

VALUE: 1

UNITS: Gbps

protocol

NAME: TCP/IP

network Segment

TYPE: WAN

bandwidth

VALUE: 2

UNITS: Mbps

latency

180.0

middleware

middleware Instance

TOOL REF: 672450721800

supported Interop Standards

interop Standard

architecture

architecture

HLA

version

IEEE_1516-2010

hardware Configuration

hardware

NAME: JHU-1

DESCRIPTION: 64 bit Windows box: Intel I7 CPUs, 8 GB RAM, 240 GB SSD hard drives

ID: 567768676130

IP ADDRESS: 192.168.1.10

OS REF: 1091846856351

ASSET TYPE: Windows tower

hardware

NAME: Pitch-1

DESCRIPTION: MacBook Pro: 2.8 GHz Intel Core i7, 16 GB 1600 MHz DDR3

ID: 473224104195

IP ADDRESS: 192.168.3.21

OS REF: 295695426189

ASSET TYPE: Mac laptop

hardware

NAME: Firewall-1

DESCRIPTION: 1 Gbps router

ID: 777748275513

ASSET TYPE: Router

hardware

NAME: JHU-2

DESCRIPTION: Windows tower: Intel I7 CPUs, 8 GB RAM, 240 GB SSD hard drives

ID: 398096971288

IP ADDRESS: 192.168.1.11

OS REF: 166933805206

ASSET TYPE: Windows tower

hardware

NAME: Firewall-2

DESCRIPTION: 1 Gbps router

ID: 51977885861

ASSET TYPE: Router

hardware

NAME: Pitch-2

DESCRIPTION: Intel I7 CPUs, 8 GB RAM, 240 GB SSD hard drives

ID: 30457303433

IP ADDRESS: 192.168.3.22

OS REF: 1053210785922

ASSET TYPE: Linux tower

modeling

ddm

remote Document Ref

REFERENCED DOCUMENT TITLE: The HLA Tutorial

SECTION: A.2

PAGE: 68

misc

Federate Models
Master The Master federate is responsible for the management of the execution, for example assigning scenarios, starting and stopping. There shall be exactly one Master federate in each federation.
Car Car Simulator federates are responsible for modeling car objects, their movements and fuel consumptions. There may be any number of car simulator federates. Each federate may model one or more car objects.
Analysis, visualization and data collection These are used for analysis of the simulation results during and after the execution. They may only consume data. They may not affect the simulation. There may be any number of these federates.

variances

variance

Since the FEF was not executed, there are no variances to report.

REFERENCE: None