With increased proliferation of the Unmanned Aerial Systems (UAS), there is now a need to develop UAS training standards for flight and payload operations. Unfortunately within training systems today there is an acute lack of UAS standards for Operational Flight Program (OFP) training interface functionality when it comes to the Weapon System Training (WST) simulators. Currently, there is an Aeronautical Radio Inc. (ARINC) 610B standard that identifies the requirements needed for the simulator OFP interfaces and functionality. The ARINC standard as it is designed does not address training needs of the UAS community and is primarily human in the loop Pilot centric. This is because UAS OFPs are separated into two pieces: Air Frame and Ground Segment (GS). Thus the Payload Operator requirements and standards for the WST do not exist and are not addressed by ARINC 610B. The UAS operations crew requirements are different from the traditional Pilot centric trainer's approaches as the crew is often composed of the Pilot, Payload Operator, Maintainer and a Tactical Coordinators. The UAS systems have a different CONOPS for air vehicles and hence require a new approach to WST interface development for the OFP. One possible way forward that will be presented here is to propose a modification of ARINC 610B standard and develop equivalent requirements to address the needs of the Payload Operators, Maintainers, and Tactical Coordinators to properly interface with the OFP for WST trainers. Although the HLA, DIS, and other standards are designed to interface with the WST, the interface challenges described in this paper are at a lower level (software development core framework) of implementation and impact the WST form, fit, and function as a training device, rather than communication issues and standards between WST devices.