Digital Engineering Ecosystem
A digital engineering ecosystem may comprise a plurality of digital engineering software tools, a plurality of connectors corresponding to the digital engineering software tools, and project data integration software that may execute on, and be hosted by, a computing system. Users may access the digital engineering software tools to generate design data for a project. The project data integration software may generate and store project data that may be used to track links between design data generated by the software tools.
1 . A method comprising:
generating, using a first digital engineering (DE) software tool, first design data;
generating, using a first connector and based on the first design data, first project data integration (PDI) input data;
generating, using a second DE software tool, second design data;
generating, using a second connector and based on the second design data, second PDI input data; and
generating, using PDI software and based on the first PDI input data and the second PDI input data, project data, wherein the project data:
links to the first design data and to the second design data; and
associates a first design feature, associated with the first design data, with a second design feature associated with the second design data.
2 . The method of claim 1 , further comprising:
storing each of the first design data and the second design data in a database, wherein the project data links to the first design data as stored in the database and to the second design data as stored in the database.
3 . The method of claim 1 , further comprising:
receiving, via a network from a first computing device, one or more first inputs; and
receiving, via the network and from a second computing device, one or more second inputs,
wherein the generating the first design data comprises generating the first design data based on the one or more first inputs, and
wherein the generating the second design data comprises generating the second design data based on the one or more second inputs.
4 . The method of claim 1 , wherein the first design data comprises requirements data.
5 . The method of claim 1 , wherein the first DE software tool is not an extension of, and is not native to, the PDI software, and wherein the second DE software tool is not an extension of, and is not native to, the PDI software.
6 . The method of claim 1 , wherein the first design data comprises one or both of:
modelling data for physical components; or
simulation data.
7 . The method of claim 1 , further comprising generating a user interface configured to:
receive input of a selection of one or more of: the first DE software tool, the second DE software tool, or the PDI software; and
provide access, based on the selection, to one or more of: the first DE software tool, the second DE software tool, or the PDI software.
8 . The method of claim 1 , further comprising:
receiving, via the PDI software, one or more inputs associating at least a portion of the first design data with at least a portion of the second design data.
9 . The method of claim 1 , further comprising:
generating, using the first connector and based on output data from the PDI software, input data to the first DE software tool.
10 . A computing system comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processors, cause the computing system to:
generate, using a first digital engineering (DE) software tool, first design data;
generate, using a first connector and based on the first design data, first project data integration (PDI) input data;
generate, using a second DE software tool, second design data;
generate, using a second connector and based on the second design data, second PDI input data; and
generate, using PDI software and based on the first PDI input data and the second PDI input data, project data, wherein the project data:
links to the first design data and to the second design data; and
associates a first design feature, associated with the first design data, with a second design feature associated with the second design data.
11 . The computing system of claim 10 , wherein the instructions, when executed by the one or more processors, further cause the computing system to:
store each of the first design data and the second design data in a database, wherein the project data links to the first design data as stored in the database and to the second design data as stored in the database.
12 . The computing system of claim 10 , wherein the instructions, when executed by the one or more processors, further cause the computing system to:
receive, via a network from a first computing device, one or more first inputs; and
receive, via the network and from a second computing device, one or more second inputs,
generate the first design data by generating the first design data based on the one or more first inputs, and
generate the second design data by generating the second design data based on the one or more second inputs.
13 . The computing system of claim 10 , wherein the first design data comprises requirements data.
14 . The computing system of claim 10 , wherein the first DE software tool is not an extension of, and is not native to, the PDI software, and wherein the second DE software tool is not an extension of, and is not native to, the PDI software.
15 . The computing system of claim 10 , wherein the first design data comprises one or both of:
modelling data for physical components; or
simulation data.
16 . One or more non-transitory machine-readable media storing instructions that, when executed, configure a computing system to:
generate, using a first digital engineering (DE) software tool, first design data;
generate, using a first connector and based on the first design data, first project data integration (PDI) input data;
generate, using a second DE software tool, second design data;
generate, using a second connector and based on the second design data, second PDI input data; and
generate, using PDI software and based on the first PDI input data and the second PDI input data, project data, wherein the project data:
links to the first design data and to the second design data; and
associates a first design feature, associated with the first design data, with a second design feature associated with the second design data.
17 . The one or more non-transitory machine-readable media of claim 16 , wherein the instructions, when executed, further configure the computing system to:
store each of the first design data and the second design data in a database, wherein the project data links to the first design data as stored in the database and to the second design data as stored in the database.
18 . The one or more non-transitory machine-readable media of claim 16 , wherein the instructions, when executed, further configure the computing system to:
receive, via a network from a first computing device, one or more first inputs; and
receive, via the network and from a second computing device, one or more second inputs,
generate the first design data by generating the first design data based on the one or more first inputs, and
generate the second design data by generating the second design data based on the one or more second inputs.
19 . The one or more non-transitory machine-readable media of claim 16 , wherein the first DE software tool is not an extension of, and is not native to, the PDI software, and wherein the second DE software tool is not an extension of, and is not native to, the PDI software.
20 . The one or more non-transitory machine-readable media of claim 16 , wherein the first design data comprises one or both of:
modelling data for physical components; or
simulation data.