Phoenix PK/PD Modeling and Simulation Software Phoenix extends the winning formula of WinNonlin by combining its trusted algorithms with an easy-to-use graphical user interface and the additional tools needed to support more advanced analysis, such as population PK/PD modeling with Phoenix NLME and in vitro-in vivo correlation with the IVIVC Toolkit. The Phoenix Workbench leverages visual workflows to vastly increase the efficiency of analysis and reporting. Once a Phoenix workflow is developed and customized, it can easily be reused. Phoenix also includes tools for sophisticated data management, high quality table and figure generation, and a project-centric design to easily store, share and reuse completed Phoenix projects. Phoenix is the leading PK/PD modeling and simulation software used worldwide by 6,000 researchers at biopharmaceutical companies, academic institutions, and global regulatory agencies, including eleven divisions of the US FDA.

Dear all, since many people still (why?) use older versions of WinNonlin and may not visit Pharsight’s support site regularly, below a copy of the “WinNonlin end of support notice”. Audience: All Customers using a WinNonlin version earlier than 5.3 As previously announced, and consistent with Pharsight’s Maintenance and Support Policy, WinNonlin versions prior to 5.2.1 are no longer officially supported. In addition to our customary policy, the license key generator for WinNonlin versions older than 5.1 is no longer supported by the manufacturer and has been decommissioned, meaning that Pharsight will be unable to provide licenses for versions prior to WinNonlin 5.1 after the end of 2011. We are letting you know about this now, so that you can plan to upgrade to a supported product version by the end of 2011. Moving to a supported version of WinNonlin requires migration to either WinNonlin 5.3 or the Phoenix platform.

An important factor driving the development of our Phoenix platform was that WinNonlin 4.x/5.x was developed with Visual Basic, which is no longer supported by Microsoft – so we developed Phoenix using the.NET framework for long-term support. Discontinuing support for Visual Basic and the license key generator was outside of our environment and could not be avoided, so moving to a new infrastructure was required. Clients will be able to run both Phoenix and non-Phoenix WinNonlin product versions (e.g., WinNonlin 5.3 when maintained on a compatible operating system) on the same machine for the foreseeable future with an active license to ease the transition to Phoenix WinNonlin. The upgrade to Phoenix WinNonlin is free for current/active WinNonlin license holders. We strongly recommend that all of our clients start thinking about their migration plans sooner rather than later. Pharsight can work with your teams to understand any challenges and help develop a Phoenix migration plan with you.

Validation tools and services are available to assist along with a number of public training courses to help users make the migration to Phoenix smoother. Let us know how we can assist. Version Support End Date 1 License Renewal End Date 2 WinNonlin 3.x No longer supported No longer available WinNonlin 4.x No longer supported December 2011 WinNonlin 5.0.1 No longer supported December 2011 WinNonlin 5.1.1 No longer supported December 2011 WinNonlin 5.2.1 June 2011 June 2012 WinNonlin 5.3 September 2012 September 2012 • This point version of the software will no longer be available for download, and no further patches will be developed or released. Upgrade assistance is always available. • Pharsight will no longer be able to process license renewal requests for the associated point version after the date listed in the ‘License Renewal End Date’ column.

Winnonlin.software.informer. Bartender Ultralite 9 2 Cracked more. com at KeyOptimize. Latest comments. Downloaded 1366 times. E-mail address. Register now.

Didn’t know that WinNonlin was programmed in Visual Basic. Must have been great fun to port Carl Metzler’s original FORTRAN code. Thanks Helmut for reminding the BE community of this, as a rule our official support period for a version is 18 months AFTER the release of the REPLACEMENT version. PS - Those of you who use Trial Simualtor and have been frustrated by Fortan compiler difficulties will be pleased to know that the current release 2.2.2 now comes with the same distributed compiler as that used by Phoenix as well as supporting Windows 7 etc. I hope to give an indication of TS 3.0's release date in the Phoenix architecture soon. Happy New Year all, Simon.