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 executing on a computing system, and based on one or more first inputs received via a network from a first computing device, first design data for a project;
generating, by the computing system and using a first connector corresponding to the first DE software tool, first project data integration (PDI) input data corresponding to at least a portion of the first design data;
generating, using PDI software executing on the computing system and based on the first PDI input data, first project data for the project, wherein the first project data corresponds to a portion of the first design data;
generating, using a second DE software tool executing on the computing system and based on one or more second inputs received via the network from a second computing device, second design data for the project, wherein the second design data comprises at least one of:
modelling data for physical components for the project; or
simulation data for the project;
generating, by the computing system and using a second connector corresponding to the second DE software tool, second PDI input data corresponding to at least a portion of the second design data;
generating, by the PDI software and based on the second PDI input data, second project data for the project, wherein the second project data corresponds to a portion of the second design data; and
outputting, by the PDI software, via the network, an indication of a relation between a design feature associated with the second design data and a design feature associated with the first design data.
2. The method of claim 1 , further comprising:
receiving, by the computing system via the network and via a first web interface of the first computing device, the one or more first inputs; and
receiving, by the computing system via the network and via a second web interface of the second computing device, the one or more second inputs.
3. The method of claim 1 , wherein the first design data comprises requirements data for the project.
4. 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.
5. The method of claim 1 , further comprising outputting, by the computing system and via the first and second computing devices, an interface configured to:
receive input of a selection of the first DE software tool, the second DE software tool, or the PDI software; and
provide access, based on the selection, to the first DE software tool, the second DE software tool, or the PDI software.
6. The method of claim 1 , further comprising:
tracking, by the computing system, usage of the first DE software tool by the first computing device and usage of the second DE software tool by the second computing device.
7. The method of claim 1 , further comprising:
receiving, via the PDI software, one or more inputs linking at least a portion of the first design data and at least a portion of the second design data.
8. 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.
9. 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 and based on one or more first inputs received via a network from a first computing device, first design data for a project;
generate, using a first connector corresponding to the first DE software tool, first project data integration (PDI) input data corresponding to at least a portion of the first design data;
generate, using PDI software and based on the first PDI input data, first project data for the project, wherein the first project data corresponds to a portion of the first design data;
generate, using a second DE software tool and based on one or more second inputs received via the network from a second computing device, second design data for the project, wherein the second design data comprises at least one of:
modelling data for physical components for the project; or
simulation data for the project;
generate, using a second connector corresponding to the second DE software tool, second PDI input data corresponding to at least a portion of the second design data;
generate, using the PDI software and based on the second PDI input data, second project data for the project, wherein the second project data corresponds to a portion of the second design data; and
cause, using the PDI software, output of an indication of a relation between a design feature associated with the second design data and a design feature associated with the first design data.
10. The computing system of claim 9 , wherein the instructions, when executed by the one or more processors, cause the computing system to:
receive, via the network and via a first web interface of the first computing device, the one or more first inputs; and
receive, via the network and via a second web interface of the second computing device, the one or more second inputs.
11. The computing system of claim 9 , wherein the first design data comprises requirements data for the project.
12. The computing system of claim 9 , 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.
13. The computing system of claim 9 , wherein the instructions, when executed by the one or more processors, cause the computing system to output, via the first and second computing devices, an interface configured to:
receive input of a selection of the first DE software tool, the second DE software tool, or the PDI software; and
provide access, based on the selection, to the first DE software tool, the second DE software tool, or the PDI software.
14. The computing system of claim 9 , wherein the instructions, when executed by the one or more processors, cause the computing system to:
generate, using the first connector and based on output data from the PDI software, input data to the first DE software tool.
15. One or more non-transitory machine-readable media storing instructions that, when executed by one or more processors of a computing system, cause the computing system to:
generate, using a first digital engineering (DE) software tool and based on one or more first inputs received via a network from a first computing device, first design data for a project;
generate, using a first connector corresponding to the first DE software tool, first project data integration (PDI) input data corresponding to at least a portion of the first design data;
generate, using PDI software and based on the first PDI input data, first project data for the project, wherein the first project data corresponds to a portion of the first design data;
generate, using a second DE software tool and based on one or more second inputs received via the network from a second computing device, second design data for the project, wherein the second design data comprises at least one of:
modelling data for physical components for the project; or
simulation data for the project;
generate, using a second connector corresponding to the second DE software tool, second PDI input data corresponding to at least a portion of the second design data;
generate, using the PDI software and based on the second PDI input data, second project data for the project, wherein the second project data corresponds to a portion of the second design data; and
cause, using the PDI software, output of an indication of a relation between a design feature associated with the second design data and a design feature associated with the first design data.
16. The one or more non-transitory machine-readable media of claim 15 , wherein the instructions, when executed by the one or more processors of the computing system, cause the computing system to:
receive, via the network and via a first web interface of the first computing device, the one or more first inputs; and
receive, via the network and via a second web interface of the second computing device, the one or more second inputs.
17. The one or more non-transitory machine-readable media of claim 15 , wherein the first design data comprises requirements data for the project.
18. The one or more non-transitory machine-readable media of claim 15 , 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.
19. The one or more non-transitory machine-readable media of claim 15 , wherein the instructions, when executed by the one or more processors of the computing system, cause the computing system to:
receive input of a selection of the first DE software tool, the second DE software tool, or the PDI software; and
provide access, based on the selection, to the first DE software tool, the second DE software tool, or the PDI software.
20. The one or more non-transitory machine-readable media of claim 15 , wherein the instructions, when executed by the one or more processors of the computing system, cause the computing system to:
generate, using the first connector and based on output data from the PDI software, input data to the first DE software tool.