In many organisations and agencies, the teams developing the ground segment system software (be it the mission data systems, flight dynamics or ground station software) are distinct from the teams provisioning and maintaining the physical or virtual IT infrastructure, including the baseline operating system and packages/dependencies, on which the software runs. As a result, information such as which physical or virtual resources are supporting which mission on which infrastructure baseline version and with which version of infrastructure or mission-specific software is loosely coupled and not easily queried. As the ground segment moves to a service-oriented and multi-mission architecture, multiple missions may rely on the same physical or virtual IT resources The idea is to provide a digital link between ground segment system and software models and the systems used for monitoring, maintenance and provisioning of the infrastructure on which the software is deployed for a particular mission. This shall be achieved through mapping of functional models to associated physical IT and network architecture and integration of the respective tools (i.e. of the system/software modelling tools and the IT enterprise management such as configuration management databases, ticketing systems and monitoring tools). Provided with such a link, queries and also impact analyses during phases D/E (e.g. of planned or unexpected downtime or of security incident occurrence on infrastructure verses mission/functional impact) and trade-off analyses (e.g. for resource allocation, provisioning or procurement needs) shall be enabled and associated efficiency gains realised. Benefits of developing new physical architecture modelling capabilities in addition to existing functional modelling tools shall also be assessed (for more efficient and direct mapping with IT enterprise management/ticketing tools).
