The Disaster Response Network Enabled Platform (DRNEP) is a system that integrates a set of independently developed infrastructure and disaster simulators. This paper describes some of the architectural choices that we made for DRNEP. The overall system uses a master-slave pattern, with one master simulator orchestrating all of the others, based on a central system clock. As the various simulators are developed by different organizations, they each have their own data models, with data elements not matching one for one, or with different representations, or not useful for collaboration. To integrate them in DRNEP, and to avoid developing n2 distinct translators, we devised a single common data model, akin to the mediator pattern, and we therefore need only one data translator per simulator. Developing this common data model poses many challenges: on one hand it must contain the right abstractions to communicate with a variety of existing and future simulators, in particular the topology of their underlying models, yet reduce the overall complexity of the system, and also minimize the likelihood of too many drastic changes when the system will evolve. We used principles from system theory to develop this common data model, and will be used with 2 simulators connected to UBC's Infrastructure Interdependency Simulator (I2Sim) serving as master.