Loren Data's SAM Daily™

SAMDAILY.US - ISSUE OF SEPTEMBER 05, 2020 SAM #6855
SPECIAL NOTICE

99 -- MBSE Interface Connector

Notice Date

9/3/2020 6:41:55 AM
 

Notice Type

Special Notice
 

NAICS

541512 — Computer Systems Design Services
 

Contracting Office

NTESS, LLC - DOE CONTRACTOR Albuquerque NM 87185 USA
 

ZIP Code

87185
 

Solicitation Number

20_15
 

Response Due

9/16/2020 10:59:00 PM
 

Archive Date

10/01/2020
 

Point of Contact

Edward Carrol
 

E-Mail Address

ercarro@sandia.gov
(ercarro@sandia.gov)
 

Description

Background Information: National Technology & Engineering Solutions of Sandia (NTESS) has been using the Model-based Systems Engineering (MBSE) application GENESYS (by ViTech Corp.) on its projects for several years and has a substantial amount of data relevant to systems already modeled. NTESS�s customers and development partners utilize a variety of other MBSE applications, in particular, MagicDraw/Cameo (by No Magic, Corp.). Therefore, the ability for NTESS and our engineering partners to exchange relevant MBSE data with our customers is recognized as an important capability to establish early in the transition to �model-based.� This announcement outlines a set of use cases and acceptance criteria for automated interface Connectors in accordance with an approach that pilots the automated exchange between the GENESYS and MagicDraw MBSE applications.� Demonstrations will be scheduled quarterly and designed collaboratively as incremental acceptance tests to show that the integration software developed accurately transforms the content of the MBSE models. The objective of this Announcement is To develop prototype MBSE API/Connectors Demonstration Target Date: December 2020, demonstration of prototype capability What is the expected result for this specific proposal? API/Connectors (software) capable of exchanging systems engineering model data bidirectionally between the GENESYS and MagicDraw software applications. NOTE1: Collaborator may provide either the GENESYS or the MagicDraw API/Connector, or both. Please specify in your response. NOTE2: Collaborator of the MagicDraw API/Connector may provide a Connector that is compatible with both MagicDraw and Cameo, or MagicDraw only. Please specify in your response. Administrative: Target start date: October 1, 2020 Expected duration?� October 1, 2020 to September 30, 2021. The work to be divided into quarterly phases. NTESS Principal Investigator Edward R. Carroll (02831) Is access to classified information required? ?Yes ?No Is unescorted access required (Q/L badge)? ?Yes ?No�� Meeting with NTESS: What, When, & Where? Occasional trips to Sandia facilities will be negotiated and coordinated on an as need basis (as COVID-19 pandemic permits) for collaboration, deliverable installation, testing, and acceptance. Initial expectations for meetings are: Kickoff: at start of contract; at Sandia National Laboratories facilities; team Progress demonstrations; at Sandia National Laboratories facilities; select key team members only. These meetings will be scheduled only as needed. Phase demonstrations; at Sandia National Laboratories facilities; team (as needed). Phase demonstrations will be scheduled quarterly, as COVID-19 restrictions allow. Expect most interactions to be via Microsoft/TEAMS or Skype meetings (no on-site-SANDIA software code development Is funding available to cover the CRADA? ?Yes ?No; only Phase 1 is funded, at present. SCOPE: What NTESS Brings to the Collaboration A NTESS research team has developed an approach for Systems Engineering model interoperability and completed a proof-of-concept for model transformation between GENESYS and MagicDraw models. NTESS will provide the results of this research to the collaboration. The team�s approach involves the following steps: Create an Application Program Interface (API)/Connector for both applications (GENESYS and MagicDraw) that maps the model data structure for both MBSE applications to a Resource Definition Framework (RDF) data structure. This step preserves the underlying ontological structure of the model. Transfer and transform the model data into an RDF file Transfer and transform the RDF file to the receiving API/Connector This Announcement lays out a potential collaboration between the NTESS research team and a Collaborator, building on the approach NTESS demonstrated in our proof-of-concept. Following the above approach, initial success has already been demonstrated that a GENESYS model can be successfully transformed into a MagicDraw model.� The proof-of-concept was only one-direction, the reverse direction from MagicDraw to GENESYS has not yet been demonstrated.� Additionally, the automatic diagram generation (activity/EFFBD, PBD, hierarchy, IBD, etc.) was not included in the proof-of-concept. Reverse direction model transfer and automated diagram generation are a set of Use Cases in this Announcement. SCOPE: Nature of Collaboration Exploratory Research � Experiment on options and evolve direction and results Finalized and detailed acceptance criteria not currently available. Detailed specification for deliverable(s) will evolve over the course of the work based on research findings Objective is to collaborate to develop approach and necessary features of the translator NTESS will not fund a product exploitable for full commercial market by a Collaborator. ,� Any IP ownership will be detailed in a Cooperative Research & Development Agreement (CRADA) which will be the contractual mechanism that will facilitate the collaboration between NTESS and a successful respondent. Willingness to explore the following contracting/funding concerns/options with selected Collaborator: Joint development effort A successful Respondent will be required to provide an in-kind contribution under a CRADA. NTESS will fund its portion of the work. Collaborator retains ownership of any Background Intellectual Property it brings to the effort Successful respondent should be able to enter into a CRADA and comply with Export Control regulations, be registered in Sam.gov and comply with all applicable laws associated with working under a CRADA with a DOE National Laboratory. SCOPE: Standards and Supporting Documentation The Collaborator shall develop the API/Connectors in accordance with the following standards RDF, OWL 2.0, OSLC, RESTful standards SCOPE: Site Requirements Where will the work be performed?�onsite and offsite Development team shall be US citizens; clearance not required Ability to deliver within the SANDIA IT environment (a closed network with no general public access). Supervised access to the Sandia Restricted Network will be provide only when necessary. Expect most interactions to be via Microsoft/TEAMS or Skype meetings (no on-site-SANDIA software code development) Possible GITHub for software collaboration, file and data sharing, and source code management ���Is overtime allowed? ��?Yes ?No SCOPE: Personnel Qualifications & Training Willingness to work starting conceptually from Sandia�s Proof-of-Concept (SANDIA will provide knowledge transfer of the above-mentioned approach and research results) Understanding of how to map and extract data to/from an ontology Knowledgeable of and experienced with RDF, OWL 2.0, OSLC, RESTful standards Final deliverable shall be developed in accordance with the above standards Familiarity with the incremental release of the SysML 2.0 specification draft GENESYS API/Connector: Expert knowledge of and experience with GENESYS API development: Access to and understanding of GENESYS schema, functionality, objects, and relationships Expert experience with model creation in GENESYS as an user and as an API developer Expert experience with creation of GENESYS diagrams and their correlation to SysML diagram counterparts as a user and as an API developer Collaborator shall provide their own GENESYS licensing and documentation access. Sandia will not reimburse the Collaborator for license fees related to the GENESYS software MagicDraw/Cameo API/Connector: Expert knowledge of and experience with MagicDraw Plug-in development and Profile development Access to and understanding of MagicDraw Domain specific language (extend user interface for user customization) Access to and understanding of MagicDraw Stereotyping Access to and understanding of MagicDraw implementation of SysML (currently version 1.6 SysML specification),� MOF, and functionality Collaborator shall provide their own MagicDraw licensing and documentation access. Sandia will not reimburse the Collaborator for license fees related to the MagicDraw software. Expert experience with model creation in MD SysML Expert experience with creation of diagrams (BDD, IBD, activity, sequence, etc.) and their correlation to GENESYS diagram counterparts SCOPE: Provisions Collaborator shall have an established software engineering capability (owned employees, equipment, and methodology): If Collaborator has existing licensed software relevant to API/Connectors (GENESYS and MagicDraw) such as existing connectors, plugins, etc., then please demonstrate the licensed software to Sandia evaluation team prior to contract award Agile development process Continuous integration, effective release planning; feature prioritization; concept of test first and test exploration; effective testing and evaluation Source Code control practices (CM techniques) - to assure errors are not introduced when incorporating changes Final deliverables shall be high quality API/Connectors with associated user and administrator documentation. Occasional trips to Sandia facilities will be coordinated on an as needed basis (if pandemic permits) for collaboration, deliverable installation, testing, and final acceptance. Establishing the possible GITHub repository will be the responsibility of NTESS SCOPE: Test Models NTESS will provide a set of Systems Engineering models for testing early in the course of the Collaboration. NTESS encourages the Collaborator to provide additional test models. The models to be provided include: The Fast Food model from the Vitech training model library The Rocket_MI model from NTESS�s model library A comparable simple MagicDraw model A publicly distributed Satellite model A Generic Rocket Interface model (representative of the structure and complexity in typical NTESS projects) SCOPE: Quality Issues API/Connectors shall function in accordance with Use Case descriptions, without degradation of any data selected for transfer, with all the defined model constructs included, and without the need for human redevelopment / reinterpretation of model constructs after transformation. NTESS recognizes that the collaborative nature of this agreement could potentially mean that the Collaborator is unable to demonstrate as completed some of the Use Cases specified. NTESS accepts partial responsibility for this risk, as natural to a collaborative research engagement. NTESS expects the Collaborator to accept its share of the responsibility toward demonstrating Use Cases as complete. SCOPE: Deliverables GENESYS USE CASES: GUC_001/GEN-UIX: A graphical user interface (GUI) for the API/Connector shall be provided that functions within the GENESYS application, selectable from a menu or executable icon, that allows the Systems Engineer/end-user to select all, partial, or individual data elements, as well as command appropriate items (such as file name, file location, etc.) to be exported/imported. GUC_002/GEN-RDF(nd): Transform a simple SE system model (see attached sample models) from GENESYS to RDF file format (no diagrams) Transform a defined set of GENESYS objects and all associated information and relationships into an RDF file format. GUC_003/GEN-RDF(wd): Transform a simple SE system model from GENESYS to RDF file format (including diagrams) Adding to the transformations in GUC_001. Transform a defined set of GENESYS diagram method calls (to the RDF file) and all associated information and relationships for a defined set of GENESYS diagrams. GUC_004/GEN-RDF-GEN(wd): Transform a simple SE system model from GENESYS to RDF file format (including diagrams). Then reverse the direction and import the same model RDF file into a new GENESYS project. Map the defined set of GENESYS objects (in the RDF file) and all associated information and relationships to the appropriate objects and information locations in GENESYS and auto-populate a new GENESYS model project. GUC_005/RDF-GEN(nd): Transform a simple SE system model (see attached sample models) from MagicDraw (in RDF file format - no diagrams) Map the defined set of MagicDraw objects (in an RDF file) and all associated information and relationships to the appropriate objects and information locations in GENESYS and auto-populate a new GENESYS model project. GUC_006/RDF-GEN(wd): Transform a simple SE system model from MagicDraw (in RDF file format) to GENESYS (including diagrams) Adding to the transformations as in GUC-003. Transform a defined set of MagicDraw diagram method calls (from the RDF file) and all associated information and relationships to the appropriate GENESYS diagrams. Execute auto-diagram generation in the target model GUC_007 � GUC_010: Repeat GUC_002 � GUC_006 with a medium complexity systems model MagicDraw USE CASES: MUC_001/MD-UIX: A graphical user interface (GUI) for the API/Connector shall be provided that functions within the MagicDraw application, selectable from a menu or executable icon, that allows the Systems Engineer/end-user to select all, partial, or individual data elements, as well as command appropriate items (such as file name, file location, etc.) to be exported/imported. MUC_002/MD-RDF(nd): Transform a simple SE system model (see attached sample models) from MagicDraw to RDF file format (no diagrams) Transform a defined set of MagicDraw objects and all associated information and relationships into an RDF file format. MUC_003/MD-RDF(wd): Transform a simple SE system model from MagicDraw to RDF file format (including diagrams) Adding to the transformations in MUC_001. Transform a defined set of MagicDraw diagram method calls (to the RDF file) and all associated information and relationships for a defined set of GENESYS diagrams. MUC_004/MD-RDF-MD(wd): Transform a simple SE system model from MagicDraw to RDF file format (including diagrams). Then reverse the direction and import the same model RDF file into a new MagicDraw project. Map the defined set of MagicDraw objects (in the RDF file) and all associated information and relationships to the appropriate objects and information locations in MagicDraw and auto-populate a new MagicDraw model project. MUC_005/RDF-MD(nd): Transform a simple SE system model (see attached sample models) from GENESYS (in RDF file format - no diagrams) Map the defined set of GENESYS objects (in an RDF file) and all associated information and relationships to the appropriate objects and information locations in MagicDraw and auto-populate a new MagicDraw model project. MUC_006/RDF-MD(wd): Transform a simple SE system model from GENESYS (in RDF file format) to MagicDraw (including diagrams) Adding to the transformations as in MUC-003. Transform a defined set of GENESYS diagram method calls (from the RDF file) and all associated information and relationships to the appropriate MagicDraw diagrams. Execute auto-diagram generation in the target model MUC_007 � MUC_010: Repeat MUC_002 � MUC_006 with a medium complexity systems model Final deliverables shall be high quality API/Connectors with associated user and administrator documentation. SCOPE: Proposed Schedule Milestone schedule: Demonstration milestones:� December 2020, March 2021, June 2021, September 2021.
 

Web Link

SAM.gov Permalink
(https://beta.sam.gov/opp/3207e637f0d54a9fad5777b3deb10cb1/view)
 

Place of Performance

Address: Albuquerque, NM 87185, USA

Zip Code: 87185

Country: USA
 

Record

SN05785843-F 20200905/200903230154 (samdaily.us)
 

Source

SAM.gov Link to This Notice
(may not be valid after Archive Date)

---

| FSG Index  |  This Issue's Index  |  Today's SAM Daily Index Page |