Models as Microservices for Enabling Agile and Distributed MBSE

Award Information
Agency: National Aeronautics and Space Administration
Branch: N/A
Contract: 80NSSC19C0325
Agency Tracking Number: 194348
Amount: $124,565.00
Phase: Phase I
Program: SBIR
Solicitation Topic Code: H6
Solicitation Number: SBIR_19_P1
Timeline
Solicitation Year: 2019
Award Year: 2019
Award Start Date (Proposal Award Date): 2019-08-19
Award End Date (Contract End Date): 2020-02-18
Small Business Information
2402 Lively Trail, Atlanta, GA, 30345-3847
DUNS: 128606188
HUBZone Owned: N
Woman Owned: N
Socially and Economically Disadvantaged: N
Principal Investigator
 Manas Bajaj
 (404) 775-4287
 manas.bajaj@intercax.com
Business Contact
 Dirk Zwemer
Phone: (404) 592-6897
Email: dirk.zwemer@intercax.com
Research Institution
N/A
Abstract
Models-as-Microservices (MamS) is a paradigm shift for agile and concurrent MBSE with globally distributed stakeholders. Model authors can publish models and data, in any format or database, as web-based microservices that can be dynamically composed and orchestrated to realize different engineering workflows for a given project or mission.nbsp; Model authors can configure the subset of model information, level of access control, and update frequency, e.g. publish only major revisions and not each iteration, when models are published as microservices. Once published, these microservices are accessible to all stakeholders via standard REST/HTTP APIs using open standards-based concepts.nbsp;Although each model/dataset is based on authoring tool-specific schema, the microservices published from those models are based on an extensible set of concepts in open standards, such as SysML 2.0, STEP (ISO 10303), and OSLC specifications. Engineering workflows can be configured by parametrically linking the endpoints (inputs/outputs) of the microservices using standard notation, such as SysML activity/parametric models, or BPMN process models. Once configured, the workflows can be executed automatically on a scheduled basis to run verification and validation campaigns and generate nightly builds of the system, such as technical data packages and corresponding reports.nbsp;The breadth of models includes, but is not limited to, systems engineering (e.g. SysML and UAF/UPDM), requirements (e.g. spreadsheets, ReqIF, DOORS, Jama), mechanical and electrical design (MCAD/ECAD, e.g. NX and Creo), engineering and manufacturing bills-of-materials (PLM eBOM/mBOM, e.g. in Windchill and Teamcenter), software modules (e.g. in Git repositories), project management (e.g. JIRA and MS Project), simulation (e.g. Simulink, Modelica, FEA/CFD models), models originating from home-grown tools, and data in common formats (e.g. CSV, Excel, XML, JSON, RDF).

* Information listed above is at the time of submission. *

US Flag An Official Website of the United States Government