The Battle Lab Collaborative Simulation Environment federation is replacing its primary entity driver OneSAF Testbed Baseline (OTB) with One Semi-Automated Force (OneSAF). OTB is at the core of the Army Capabilities Integration Center's (ARCIC) Battle Lab Collaborative Simulation Environment (BLCSE) federation. Currently, the BLCSE federation has OTB at the core with about 14 other federates that depend on the entities and interactions provided by OTB. The ARCIC Simulations Division envisions that OneSAF will not only replace OTB but will over time replace the functions provided by many of the other federates to create a more homogenous federation. As OneSAF is introduced into a mature federation such as BLCSE, there are federation considerations and site considerations that must be managed. This paper will address the BLCSE enterprise culture changes associated with procedures and challenges involved in community adoption. Economies are gained by replacing OTB and eventually one or more other federates with OneSAF. Configuration management procedures will have to be adopted to address users that are now able to compose behaviors of a simulation that are at the core of the federation. This paper will also address how a BLCSE site such as the Future Force Integration Directorate (FFID) in Ft. Bliss, TX is conducting OneSAF training for users and technicians, modifying/introducing infrastructure, participating in integration and stress testing of ONESAF, and performing configuration management. These activities and more are being synchronized and conducted to ensure a successful introduction and adoption of the primary entity driver, OneSAF, in the BLCSE federation.