Current integration of Microsoft Project 4.0 is accomplished by exporting the data from a Teamware activity network into a file format that MS Project understands. This translation is automated, and after creating the file, MS Project is started under a Windows emulator (WABI). At any time during execution of the network, you can export the Teamware network into MS Project and perform the analysis of the tasks accomplished to date.

One of the disadvantages of MS Project is that loops, conditionals, and branching aren't handled very well (if at all). In order to leverage off of this commercial tool, decisions need to be made about these control points. We give the user an option of choosing between three different analysis methods: assume a single pass through all loops, estimate a probability for each control point and statistically model it, or assign the number of iterations for each loop based on the manager's expert opinion.

Eventually Teamware will accomplish all of its analysis internal to the system, but for now, the simpler analysis capabilities of MS Project are being used as a placeholder. The integration of Teamware with MS Project has been one of the most popular features.