NASA SBIR 2019-I Solicitation

Proposal Summary

 19-1- H6.04-4348
 Model Based Systems Engineering for Distributed Development
 Models as Microservices for Enabling Agile and Distributed MBSE
SMALL BUSINESS CONCERN (Firm Name, Mail Address, City/State/Zip, Phone)
2402 Lively Trail
Atlanta, GA 30345- 3847
(404) 329-0104

Principal Investigator (Name, E-mail, Mail Address, City/State/Zip, Phone)

Dr. Manas Bajaj
47 Perimeter Center East, Suite 410 Atlanta, GA 30346 - 2001
(404) 775-4287

Business Official (Name, E-mail, Mail Address, City/State/Zip, Phone)

Dirk Zwemer
2402 Lively Trail Atlanta, GA 30345 - 3847
(404) 592-6897
Estimated Technology Readiness Level (TRL) :
Begin: 1
End: 7
Technical Abstract (Limit 2000 characters, approximately 200 words)

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.  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.


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.


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).

Potential NASA Applications (Limit 1500 characters, approximately 150 words)

Technology developed in this project is applicable to all current and future NASA missions, both human exploration and robotic, that are actively deploying or investigating model-based systems engineering capabilities in a distributed and collaborative environment. Some notable examples are (1) Lunar Gateway, (2) Lunar Outpost, (3) Mars 2020, (4) Europa Clipper, (5) Europa Lander, and (6) Mars Sample Return. The Intercax team is actively working with several mission teams at NASA JPL that are adopting MBSE. 

Potential Non-NASA Applications (Limit 1500 characters, approximately 150 words)

Collaborative, distributed, and concurrent MBSE is taking a center stage in many industries, such as aerospace, defense, automotive, transportation, energy, healthcare, consumer goods, and electronics. Intercax has customers across these industries. The capability to integrate models originating within and outside the organization with automated information flows is crucial for these industries.

Duration: 6

Form Generated on 06/16/2019 23:39:20