The short answer is: "No, the Workstation must be linked to a specific Target platform, before any development is possible".
To expand on this let us review a few Telestra fundamentals. A Target platform runs a simulation model utilizing the processing capability of the CPU, and can be configured to operate in an embedded mode, such that the platform powers up, loads, and runs a pre-selected model. In this operating mode, no external platform is needed to operate. This allows optimization of the core software on the Target to the runtime task, which after all, is the intended operating mode for any platform deployed to a training device or simulator. In the typical life of an ASTi system, we might see the system used in development mode for perhaps 6 months or so, followed by 10-15-20 years of operational service.
In order to support the development task, ASTi has opted to off-load this functionality to a remote machine, the Studio Development Workstation. This platform in its current form does not support stand-alone development (but more of this later), and must be linked to one or more Target platforms for model development. There are a number of reasons why this configuration is preferred:
Optimization of the Target runtime framework to support the embedded mode of operation is preferred, versus a hybrid development-runtime platform which introduces overhead and complexities.
A single development workstation may be employed to service multiple Target platforms in a distributed environment, allowing centralized management of many machines perhaps running cooperatively to support one or more concurrent exercises, or perhaps to support multiple simulators during development.
A single development workstation may be employed to develop a model that spans multiple Target platforms to form a single tightly-coupled "layout." The development workstation is suited to address the needs of the increasingly common combined-mode, coupled front and back-end training devices (commonly using an OFT or FFS cockpit simulator, and an RCT rear crew trainer, that can be linked to form a single platform), or individual models for each device to support split-mode operation.