As a part of Army's annual experimental campaign plan, an event named Talon Strike was planned for the spring of 2010 involving several of the US Army's Battle Labs and the United Kingdom (UK) as a coalition partner. It was not the specific intention to conduct Talon Strike as a homogeneous simulation experiment. In 2010, ARCIC, in an effort to conserve resources, combined both a Battle Command experiment with a pre-deployment training event using a single simulation driver. Talon Strike requires special security classification management. In order to comply with these security requirements and to reduce the complexity of the experiment, it was decided to use only OneSAF as the entity driver and the experiment's only constructive simulation. Talon Strike culminates a five year US/UK Future Land Operations Interoperability Study (FLOIS) staff effort for interoperability of coalition forces in battle command systems and staff operations. The experiment's architectural approach evolved into a model that supports the Common Interface level (High Level Architecture), the Common Data Level, the Common Architecture Level and the Common Application Level which together classify it as a Homogeneous Simulation Experiment, based on the Homogeneity Model proposed by Paul Hanover at I/ITSEC 2009. The Army's Omni Fusion series of heterogeneous experiments have traditionally been a collection of different battle labs each with their own proponent simulation and has required up to six months of detailed technical planning and integration to provide ten unique experiment runs. This paper compares the pros and cons of heterogeneous versus homogenous simulation federations, and presents the reduced effort need for integration compared with previous federations, while retaining entity model fidelity. This paper also contrasts and provides resource and workload insights into conducting both a homogeneous and heterogeneous experiment using empirical cost and manpower data.