I am very pleased to announce the latest release of Maros and Taro.
This version features great additions like an alternative flow optimisation solver and rate operations for Maros, transient yields and flow triggering events for Taro plus a Result Comparison View for both tools to help when comparing results. Maros and Taro also comes with improvements to the interface, usability, reporting and our maintenance strategy implementation. These are designed to help you build better, faster, and more usable models. 🙂
You can download the versions in our Customer Portal:
Alternative Flow Optimisation method
The new flow solver is part of the initial implementation of optimisation methods in Maros. The solver is a Mixed Integer Linear Programming (MILP) type of a solver based on the revised simplex method. This method focuses on setting up an objective function which represents the target to be optimised. The objective function would typically refer to an export node which will be used as a reference for the flow calculation.
Taro has now the ability to define transient yields for the different process units. In previous versions, the implementation of transient yields included defining multiple units with phase-in and phase-out – this approach increases the size of models and it makes it difficult to perform quality checks. With this new feature, the definition of transient yields is directly performed at the Node property window inside the Products tab.
Flow Triggering Events
The “Trigger” option initiates an independent event rather than managing a stream flow. The independent event is triggered once the threshold level and direction are breached; it is important to note that, by default, the event will be repeated sequentially for as long as the threshold is breached.
The new version of Maros and Taro also comes with a Comparison View. This provides the ability to compare the results between different models. Typically, a base case and its sensitivity scenarios. The main key performance indicators are displayed in graphical and tabular format. In addition, the delta button can be easily displayed:
We have also launched more videos in our e-learning centre: Maros and Taro e-learning centre
Meet the team!
The super star team developing Maros and Taro include:
- John Gilmour, Head of Software Development for Maros and Taro- John has over 25 years experience managing and developing software for a range of different industries. For the last 21 years John has been managing the user interface and simulation development for Maros and Taro. He has the vision and is always available to assist clients. John is the technology champion of the new Plant Ecosystem project which combines RAM analysis to Integrity Management.
- Stephen Bates, Principal Software Developer – Steve has been working with Maros, Taro and Trail for over 20 years now. He has a PhD in Applied Maths and is the brain behind most of what our Simulation Engine is today. He was the one integrating Maros and Taro simulation engine. Most recently, he implemented Transient Yields, Flow Triggering Events and he is also continuously extending the flaring operations and criticality algorithm to accommodate the increasing demand to model complex scenarios.
- Shafack Njoze, Principal Software Developer. Shafack has been working with Maros and Taro for the past 3 years. He has a degree in Mathematics, masters in Control Systems, and a PhD in Computing which is a combination that fits well with our needs. Shafack is the one behind the new flow optimisation method is key to this new version of Maros. His work is the foundation for the next flow-related features we are adding to Maros and Taro.
- Michael McCoy: Principal Software Developer. Michael is responsible for a lot of neat features in Maros and Taro. Sensitivity Manager, Results Viewer, the new Comparison View and all grids are work of Michael. Furthermore, Michael is the lead architect in the Process Safety, Risk and Reliability Product Centre. He is also responsible for developing our Cloud solutions and has been implementing the code to make the Plant Ecosystem work for Maros and Taro.
- David McLelland, Principal Software Developer. Dave has been working with Maros and Taro for 14 years. Among other stuff, all the nice user-interface (i.e. Ribbon Tab, Animation Mode etc.) implementation that you see in Maros and Taro is developed by Dave. He is the one implementing all the validation to make sure we are not breaking models. Dave was part of a quick-wins project that we run for this release, implementing small changes but valuable changes to the interface.
- Lois Moore, Senior Support and Test Engineer. If you have been in touch with support, you probably heard from Lois. Apart from responding to your support questions, Lois takes care of the quality of the applications and make sure that everything is running as described in the scope document. She runs test extensively to break the applications so this can be reported and corrected by the developers before is send out to clients. Lois has been working with Maros, Taro and Trail for over 16 years.
This team is what makes Maros and Taro the best RAM tools available in the market and I am very proud of being part of it.
A big thanks to Jessica Pertolaw, Marketing & Communications Manager. She makes sure you get our news! She manages the entire release process and makes sure that I am not forgetting anything important (e.g. the installer :))
We obviously have around 50 consultants working with Maros and Taro around the globe and they are constantly contributing to the development of Maros and Taro. Thanks!
Maros and Taro offers great new and unrivalled features. We’re always looking for new ways to improve our products, and some of our best ideas come from our users. If you have ideas for new features, important issues we need to address or new features you’d like to see, please let us know!
If you have any questions, comments or feedback, please feel free to drop me an email at firstname.lastname@example.org.