Utilizing MBSE to Modularly Architect the NESDIS Ground Enterprise

The power of Model-Based Systems Engineering (MBSE) lies in the relationships built between the systems, activities, and functions in the model. Flat diagrams and spreadsheets can only tell a two-dimensional story and do not have the interweaving relationships and live architecture sense that using MBSE provides when architecting a system of systems. The JPSS Common Ground System is currently modeled in such a way as to completely define all operational activities and systems (including backup and testing). The rigorous modeling effort has expedited and ensured accuracy down through the test and verification phase. Working closely with the system vendor as well as JPSS ground project management, the model is able to maintain a high level of accuracy true-to-form for the system being built. Any changes to the system during design reviews, from additional/changing requirements or otherwise, are documented and adjusted in the model immediately to keep the model always current and accurate. The NESDIS Ground System was also modeled using MBSE to document and visualize the as-is state of the current ground system. The model was crafted with a variety of input from existing architecture schematics, engineering personnel, system databases, and subject matter experts in each of the respective “stovepipe” subsystems. Each mission that NOAA operates was added to the model as well as missions which are partnered with NOAA. External entities, end users, international organizations, and universities were also incorporated. The JPSS mission is a small subset of what the NOAA ground system comprises. In order to maximize reusability, traceability, robustness, and accuracy, the JPSS model can be linked to the NESDIS ground architecture model. It would act as a plug-in-play piece to NOAA’s ground architecture. This would create an updated view of the NESDIS enterprise and lead the way for plugging in other missions, partners, and external entities in a similar fashion. Creating this enterprise level model for NESDIS and its partners would also greatly enhance NOAA capabilities to understand their enterprise upgrade needs. Metadata can be stored for all systems in the model such as processing capacity of systems, cost of operations/hardware, lifecycle milestones, etc. This metadata can then be sorted or filtered to produce lists of systems ready to be refreshed, those which can be consolidated, and those at end of lifecycle. The NESDIS Ground System consists of segregated systems, operations, networks, and facilities. This amalgamation of systems and system of systems is often referred to as the NOAA “stovepipes.” With the transition of GOES-16 and JPSS-1 operations to NOAA, we will see an increase in the complexity of the overall NESDIS Ground System. The addition of hundreds of systems, servers, and network nodes make understanding the system as a whole a daunting task. Modern architecture tools and disciplines, such as Model-Based Systems Engineering, can be used to clearly define the as-is state of a ground system regardless of complexity.