Model Inspection Server Release Notes

1. MIS 5.0.0

1.1. Changes

1.1.1. Dependencies

  • Updated Model version from 7.1.0 to 8.0.0.

  • Updated Tooling Core version from 7.3.1 to 7.5.1, which contains Model version 8.0.0.

  • Updated hgk version from 6.0.0 to 7.0.0.

1.2. Bug Fixes

1.2.1. Service Objects

  • ReferenceInfo full names are now updated correctly after a rename, both when merging missions and within Model Service Objects.

1.3. Notes

  • BREAKING: hgk 7.0.0 changes the name and location of the deployment jar to use the deployment instance name. Workflows that take the jar directly from the output/ directory must be updated. The jar exported to the package registry is unchanged, and is still named ModelInspectionServer.jar.

2. MIS 4.3.0

2.1. Changes

2.1.1. Mission Merging

  • MIS now tracks which missions have been merged.

3. MIS 4.2.2

3.1. Changes

3.1.1. Dependencies

  • Updated Tooling Core version to 7.3.1.

  • Updated Model version to 7.1.0.

3.1.2. Mission Merging

  • The TargetRouteConnection validator in the mission merger now checks route services leniently.

4. MIS 4.2.1

4.1. Bug Fixes

4.1.1. Mission Merging

  • Route signature matching now matches services by full name only, ignoring the service version. Mission databases generally contain artefacts of several versions — some of them from bundles — so a service such as component.PAS would otherwise fail to match between target routes even though the services are the same.

5. MIS 4.2.0

5.1. Changes

5.1.1. Mission Merging

  • Extra targets from both the base mission and the merging mission are now included in the merged mission, so that targets whose IDs are not present in the base mission are merged in intact.

  • Instances merged into the base mission now have their full names updated to reflect the change of mission.

  • Placeholder target connections are no longer combined with those of a real target.

  • A placeholder target that has any initiator route connections is now reported as an error before merging begins.

5.2. Notes

  • Two mission merging rules changed with this release: placeholder target connections are never added to a real target, and a placeholder target cannot hold initiator route connections, though it can still be the target of another target’s initiator route connection.

6. MIS 4.1.0

6.1. Changes

6.1.1. Mission Merging

  • Added mission merging, integrated into the Model handling. Several mission databases can be loaded into a single Model and merged into one mission, so that the Model information for the ground or flight software, its proxies and its ground station networks — each of which is normally held in its own mission database — can be accessed together as a single Model.

  • Added a reset operation to the ModelLoaderService, which clears all mission database and Model contents from MIS.

6.2. Notes

  • To merge mission databases, load the base mission database with the ModelLoader component’s LoadMissionDb operation, then call the same operation for each further mission database to merge it into the base mission. Call reset to start again from scratch.

  • The mission being merged in replaces the base mission’s targets whose IDs it shares, so the base mission must contain placeholder targets for them: a target can only be replaced if its name is prefixed with Placeholder, which is not case sensitive. Targets with IDs not present in the base mission are merged in intact, and target order by target ID is preserved.

  • Missions may not contain duplicate instances. Two missions that each hold an asset of the same name and version cannot be merged, since it would be ambiguous which of the two to use. Library elements shared between the models — a Component Type, for example — are loaded once and shared, and are identified by full name, version and type.

7. MIS 4.0.0

7.1. Changes

7.1.1. Dependencies

  • Updated hgk version to 6.0.0.

  • Updated Model version to 7.0.0.

8. MIS 3.1.0

8.1. Changes

8.1.1. Dependencies

  • Updated Tooling Core version from 5.0.0 to 6.1.0.

  • Updated Model version from 6.0.0 to 6.1.0.

  • Updated hgk version from 5.0.3 to 5.1.0.

8.2. Bug Fixes

8.2.1. Mission Database

  • Fixed an issue with loading MissionDB via a blob.

8.2.2. Service Objects

  • Ensured ModelUtility and ModelLoader return copies of Service Object outputs.

  • Fixed an issue where Service Objects were not using ordered maps when copied.

8.2.3. Target Resolution

  • Fixed an issue where the getTargetsOnHost method did not match any targets.

8.3. Notes

  • Generated using hgk CLI 5.1.0.

9. MIS 3.0.0

9.1. Changes

9.1.1. Summary

  • MIS now provides Model data using the new Service Object structure.

  • MIS bundle now contains compiled code.

  • Updated service names and locations for Model Inspection services.

  • Includes various Model changes and Tooling Model loading fixes as described in their respective release notes.

9.2. Version Updates

  • Updated Tooling Core from 1.1.3 to 5.0.0.

  • Updated hgk from 2.1.2 to 5.0.0.

  • Updated htk from 2.3.1 to 4.2.0.

  • Updated Model version from 1.0.1 to 6.0.0.

9.3. MIS Changes

9.3.1. Core Implementation

  • Updated MIS core implementation to use Tooling Core with Service Objects.

  • Removed the mis.modelreferencemapping module.

  • Removed ModelReferenceMap logic.

  • Added a new MIS selection ID assigner class.

  • Updated ModelHandler to set the Model Selection ID assigner.

9.3.2. Model Inspection Services

  • Updated MIS to use Model Inspection services from the Model Bundle.

  • Model Inspection services are now provided by the Model Bundle rather than the MIS.

9.3.3. Component and Service Regeneration

  • Regenerated all MIS component implementations.

  • Removed old generated MIS Service XMLs.

  • Updated MIS component types to use Model services.

  • Added a new MIS failure module containing exceptions.

  • Added ReferenceInfoIdAssigner.

  • Added ReferenceHandler and associated exception.

  • Regenerated Model Inspection components with updated getter methods.

9.3.4. Packaging

  • Renamed MIS executable from: deployments-modelinspectionserverdeployment-0.0.0.jar to: ModelInspectionServer-${version}.jar

9.4. Downstream Effects

9.4.1. Workspace Dependencies

  • GenOne workspaces using MIS must depend on the GenOneModel bundle.

9.4.2. Service Name Changes

  • Model Inspection services were renamed:

    • mis.model → genone.model

    • mis.CoreModel → genone.modelinspection.CoreModel

    • mis.FunctionalModel → genone.modelinspection.FunctionalModel

    • mis.PhysicalModel → genone.modelinspection.PhysicalModel

    • mis.MissionModel → genone.modelinspection.MissionModel

9.4.3. Service Object Structure

  • ReferenceInfo classes now use a typed Service Object Reference structure.

  • ReferenceInfo classes include optional embedded Service Objects.

  • ReferenceInfo class names changed from *Info to *ReferenceInfo.

9.4.4. Impacts

  • Code using ReferenceInfo int-based references requires updates.

  • Protobuf definitions reflect the updated Service Object structure.

  • Code using ParameterBlockDefinition must be updated according to Model release notes.

  • Standalone MIS executable name has changed.

9.5. Notes

  • Generated using Groundkit 2026.3.0 with hgk 5.0.0.