|
Headlines Getting the most out of Eclipse-fm® seems to be the theme for this newsletter.
Training, getting the best performance, How do I...?
We hope you find these useful
|
|
|
Version 4 - Late
Whoever said "never apologise, never explain" had it all wrong! Eclipse-fm® is later than we would have liked. Our apologies for that, and the explanation is that it has been a very ambitious task, with both the EBME work and the move to MS SQL Server affecting many existing areas of the system. As a result, we think this will be a very big step forward in the functionality of Eclipse-fm®, and one that you will find very important in extending the reach and excellence of your FM department. However, it is not our intention to repeat this level of complex change in a single release. For the future, we intend more frequent and more incremental releases. For example the next release will concentrate on the list of outstanding improvements, irritations and those things we are never supposed to speak of - bugs! Hopefully, our long suffering and much appreciated Feedback Group members will finally get to see the back of these, before we move ahead with more new functionality subsequently. In the meantime, as well as Version 4 itself, you have the new Trix Document Management facility as a new product integration, of particular interest to those for whom interactive access to AutoCAD drawings is a need, though Trix is much more than just an AutoCAD document manager of course.
So, as we look ahead to next year, we look forward to working with you to introduce Eclipse-fm® v4, - all part of your regular subscription of course - and to seeing many more of you at Training Sessions and Feedback Group meetings. |
|
Eclipse-fm® Version 4
As this newsletter goes out, Version 4 is now in final in house testing and will be going out to selected users in January. Two immediate impressions - it looks different, and it seems to be running much faster compared with V3. The appearance change is distinctive, though relatively minor. Gone is the beige, mildly 3d look, and in comes a more current blue theme and a "flatter" appearance. But this is only fashion, albeit one we have to keep up with! Much more importantly, particularly for those not yet using MS SQL Server as the data base, it feels much faster in operation. Even MS SQL Server users may notice some increase in speed, as with everyone now going to be using the server database, we have been able to take advantage of SQL optimisations. So - Whats new and Whats Changed? Overall, there are a lot of changes in this release, and from both a functional and visual point of view, we think you are going to find a lot to be happy with. The most significant areas of change and improvement are
Data Constraining by User Profile You may define a user to only see data for a particular Site, or Organisation,for a particular Store, or for particular types of tasks.
This will meet the needs of multi-site Trusts to provide for local level (site) management, while allowing higher level users to see and particularly to gain management information, from the whole Trust FM database. It ill also allow specialist staff to only gain access to tasks of a specific nature - EBME being a good example.
EBME We covered the EBME development in the last Eclipse-fm® Newsletter. As well as "just EBME", this brings in
The EBME module brings in the potential for handling many other "specialist needs" maintenance scenarios - covering a variety of classes of equipment that need different information to be associated with each maintenance task
MS SQL Server For those not already using MS SQL server for Eclipse-fm® data this will be a big change. This data-base migration was covered in the July Newsletter, along with the reasons and benefits of the move to this server database, so that you would have plenty of time to make any preparations. Now that we are getting close to the day, maybe you should refresh your memory as to whats involved - and start talking to us if you foresee any problems. A search engine is now included so that the user can search through the history to find information e.g. how did we fix this last time etc. Another SQL benefit, incidentally Task Search Engine
This means that instead of having to move around between multiple processes, and having to find your order for each one, you can stay within the "Order" and now see everything that relates to it - current status (requisition, order, processing, completion, etc.) and all of the current actions that can be carried out against it.
This could have lost the "process-centric" approach of the current system, but the new Purchase Order view lets you change to a different order without changing the currently active tab - just as with the current stage-based process in the separate views. So if you need to process "goods received" for a bunch of orders, just work on the first one in the Goods Received Tab, then you just stay on that tab as you find the others you need to process.The "best of both worlds" solution should make the job of those involved in Purchasing a lot easier. The Authorised Transactions tab acts as a control centre for progressing orders, and ensures that an order is properly progressed through the process, and that an audit trail record is created for every stage. This closely controlled progression provided by the Authorised Transactions Tab should both make the PO system easy to use, as it is difficult to do the wrong thing at the wrong time, and impossible to subvert. Look and Feel We think you will find Eclipse-fm® v4 looking distinctly updated and refreshed compared with the current version. Some of the functionality - and improved speed - behind this is Dependant on the MS SQL Server back end, just one indication of the tight interlocking of the various new features! Of course, there are a lot more changes, some in support of the above, and some as general improvements that would make this update note far too long to read!
Beta Test Sites We are now looking for Beta testers. No software developer can release software without user testing, and the definitive answer to the question "When will v4 release" now depends on user test results to augment our extensive in house testing.
Purchase Orders The current implementation of Purchase Orders was very much lifted from WIMS "as is" and does not do justice to how Windows can really improve application navigation. This is a complete rework, and, for example, brings the number of views involved down to only two. It also corrects a number of long standing WIMS "features" ! The new Purchase Orders view replaces 11 separate views (covering everything apart from the Change Finance Codes View) into one view with 5 Tabs. |
|
One of the many features of Eclipse-fm® that many people dont realise can assist them is the No Scheduled Work Dates option. This is a feature of Eclipse-fm® that those that have come from the legacy WIMS system will recognise as low weeks. What is this option? In the legacy product, low weeks allowed you to indicate in the system four working weeks that you do not want the system to produce any dockets for which would allow you to catch up with the current workload. As the legacy system worked in units of weeks, this would exclude just that, a week at a time. In Eclipse-fm®, as we have done away with the old way of working, you can now fine tune your scheduled workload down to a single unit of time being a day. This allows you to identify single days as days where you do not want any work to be planned for - No Scheduled Work Dates. Below is an example of this standard feature in Eclipse-fm®. (Click on image for a larger version)
You will see that we have populated the list with some typical dates for the current and next year. |
|
Tuning Eclipse-fm® performance
Some recent experiences of helping Trusts with performance issues have been very instructive, and we have put together a White paper on the whole issue. The key issues are MS SQL server performance.
Eclipse-fm® will work the server hard, so it needs to have plenty of processor speed and adequate memory. In particular, trying to operate MS SQL Server in less than 1 megabyte of memory on an older server, or worse, within a virtual server on a physical server already doing other things, will result in very slow performance.
If the Eclipse-fm® database is installed to the main Trust MS SQL Server, be sure to asses if there is enough capacity to take on the extra load. If performance is not adequate, particularly check that this central database server is actually providing the capacity and performance that you will need. Network Speed Hospital networks are big and overloaded. They may also be multi-site, and the FM department is often involved with usage at remote sites. You need the full bandwidth of a 100MBPS connection, and a Gigabit network backbone to run a busy database application, and longer distance connections typically implemented as 2MBPS leased lines will make the application unusable. In these cases. deployment via MS Terminal Services or Citrix will be needed, and will provide a very effective solution.
Look critically at the actual bandwidth available at busy times of day between database and the PCs running the Eclipse-fm® application. Poor Performance at particular times of the day If performance is a problem at certain times of day, but otherwise OK, this will be as a result of either an overloaded server, or an overloaded network, or both.
For a full paper on this subject, click here. |
|
|