I probably should be clearer. I don't think 9lv will feature on Japanese ships. But I think there could be some joint collaboration on integration of sensors and systems to ensure the localisations and externally integrated aspects aren't left behind in the future direction of networked warfare and can achieve the same outcomes. It is entirely possible the two forces will fight together, so coherency on things outside of the US stuff still happens.
Still not sure what you mean specifically. Not saying collaboration on integration isn't good...just that the specific desired endstate from "localisations and externally integrated aspects" is a bit unclear.
Interoperability of allied forces comes from being able to communicate and exchange data/information. Setting aside the TTP's and focusing on the technical aspects, for the most part, we're probably already there.
Between all the Allied exercises in the Pacific theater, I would expect any technical interop issues to have already come to light. We've done joint US, Japan, and ROK exercises where all 3 nations were up in the same Link network to support a BMD firing event. Same in Europe with most recently a non-AEGIS NATO ship using a Thales radar which successfully passed to a USN AEGIS ship.
A CMS doesn't particularly care whose network control box is talking to it...if the "magic Link box" tells it that Link box from Unit #4 in the network list is reporting Track #12345, the CMS is going to process it.
In other words, across navies at least, Allied interoperability is actually already pretty good.
As long as everybody is using the same LINK/IFF standards (which is why those LINK 11/16/higher standards exist), you should be OK...and all the major Pacific partners for any Coalition are already probably on board with the existing legacy Links at least.
Same goes for any other "secret squirrel" data sources. This is where I really can't say anything specific, but the overall concept is the same. The interoperability resides in the subsystem that will actually talk to the other players in whatever network you want. If I can enter in a partnership to share data and successfully establish this network, then using the data at the unit level is just an internal problem in how your CMS of choice will receive and process the new data source.
CEC is a different story, because it wasn't build with the requirement for Allied interoperability...which is why it's a rather big deal that Australia received it, while no other AEGIS customer has even been approved for sale to date.
I do think it is interesting that Australia is going the Aegis/9lv route. And about rolling that back onto the AWD's.
Gotta agree with spoz on this one regarding the roll back to AWD's.
For initial design on SEA 5000 it's an interesting solution to what was going to be a challenging problem, and probably the most elegant given the advances in flexibility of modern CMS. Open architecture and virtualization, in theory, make integration between interfaces much easier, so it was probably the most cost-effective option to provide this capability.