Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision |
about:which_one_for_you [2023/02/01 04:19] – [Synchronised Single-user (Single-user sync)] Mark Glover | about:which_one_for_you [2023/11/15 20:49] – [Comparison table] Mark Glover |
---|
{{indexmenu_n>40}} | {{indexmenu_n>40}} |
| |
====== 1.04. Which mSupply package best suits your organisation? ====== | ====== 1.04. Which combination of mSupply products best suits your organisation? ====== |
| |
Since its creation in 1998, mSupply has grown and multiplied as it has been applied to different challenges. The original [[about:which_one_for_you#free-user|Free-user]] (Windows or Mac based) application continues to be downloaded and used regularly. In fact, it comes packed with (almost) all the bells and whistles of some of our most sophisticated installations, but is only suitable for a small, single concurrent user facility. | Since its creation in 1998, mSupply has grown and multiplied as it has been applied to different challenges. The original [[about:which_one_for_you#free-user|Free-user]] (Windows or Mac based) application continues to be downloaded and used regularly. In fact, it comes packed with (almost) all the bells and whistles of some of our most sophisticated installations, but is only suitable for a small, 'single concurrent user' facility. |
| |
| |
===== Comparison of the mSupply packages ===== | ===== Comparison of the mSupply products ===== |
| |
So which is the right mSupply package for your organisation? | So which are the right mSupply products for your organisation? |
| |
==== Free-user ==== | ==== Free-user ==== |
* Lower cost than conventional synchronised multi-user as the single-user client license is less costly than multi-user client licenses. The [[synchronisation:introduction#synchronisation_server|Synchronisation server Module]] and [[web_interface:using_the_web_server|Web Server Module]] are required on the central server. | * Lower cost than conventional synchronised multi-user as the single-user client license is less costly than multi-user client licenses. The [[synchronisation:introduction#synchronisation_server|Synchronisation server Module]] and [[web_interface:using_the_web_server|Web Server Module]] are required on the central server. |
| |
| ==== mSupply Mobile (Android) ==== |
| * [[mobile:|mSupply Mobile]] is similar to [[about:which_one_for_you#synchronised_single-user_single-user_sync|Synchronised Single-user (Single-user sync)]], but the users operate with mSupply Mobile (client) software on Android tablets. This app has a reduced feature set, but is more than adequate for most Last-Mile needs. Local stock details are synchronised back to the Central server, and can be monitored and reported on there. |
| * Being [[https://en.wikipedia.org/wiki/Open-source_software|Open Source software]], mSupply Mobile has zero license fees. The [[synchronisation:introduction#synchronisation_server|Synchronisation server Module]] and [[web_interface:using_the_web_server|Web Server Module]] are required on the central server. |
| |
| ==== Open mSupply ==== |
| |
| * [[https://docs.msupply.foundation/docs/introduction/introduction/|Open mSupply]] is the multi-platform mSupply software that has been under development by [[https://msupply.foundation/|the mSupply Foundation]] since 2020. Open mSupply has all of the flexibility of all of the other versions of mSupply with the benefit of being Open source. |
| * Being [[https://en.wikipedia.org/wiki/Open-source_software|Open Source software]], mSupply Mobile has zero license fees. The [[synchronisation:introduction#synchronisation_server|Synchronisation server Module]] and [[web_interface:using_the_web_server|Web Server Module]] are required on the central server. |
==== Comparison table ==== | ==== Comparison table ==== |
| |
^ [[about:which_one_for_you#synchronised_multi-user|Synchronised Multi-user]] | If the internet connection to remote users in a Multi-user configuration is inadequate, then [[synchronisation:introduction|synchronisation]] allows a Primary - Satellite configuration to be deployed. 'Satellite' multi-user servers are installed at remote sites where users operate mSupply on their local store without worrying about the internet connection. In the background, these 'satellite' servers will synchronise their local store data with a 'Primary' server when the internet connection becomes adequate. | A software license needs to be procured for each concurrent client for each server. The [[synchronisation:introduction#synchronisation_server|Synchronisation server Module]] and [[web_interface:using_the_web_server|Web Server Module]] are required on the central server. | | ^ [[about:which_one_for_you#synchronised_multi-user|Synchronised Multi-user]] | If the internet connection to remote users in a Multi-user configuration is inadequate, then [[synchronisation:introduction|synchronisation]] allows a Primary - Satellite configuration to be deployed. 'Satellite' multi-user servers are installed at remote sites where users operate mSupply on their local store without worrying about the internet connection. In the background, these 'satellite' servers will synchronise their local store data with a 'Primary' server when the internet connection becomes adequate. | A software license needs to be procured for each concurrent client for each server. The [[synchronisation:introduction#synchronisation_server|Synchronisation server Module]] and [[web_interface:using_the_web_server|Web Server Module]] are required on the central server. | |
^ [[about:which_one_for_you#synchronised_single-user_single-user_sync|Synchronised Single-user\\ (Single-user sync)]] | There are situations where the remote sites (with poor internet access) are just single-operator stores needing to manage and report their stock using the fully featured mSupply client. Procuring the minimum multi-user satellite server configuration for each of these sites would be expensive. A solution has been developed that entails installing single-user clients machines (normally laptops) at these remote locations and then synchronising them to the primary server much like the Synchronised Multi-user configuration. | Lower cost than conventional synchronised multi-user as the single-user client license is less costly than multi-user client licenses. The [[synchronisation:introduction#synchronisation_server|Synchronisation server Module]] and [[web_interface:using_the_web_server|Web Server Module]] are required on the central server.| | ^ [[about:which_one_for_you#synchronised_single-user_single-user_sync|Synchronised Single-user\\ (Single-user sync)]] | There are situations where the remote sites (with poor internet access) are just single-operator stores needing to manage and report their stock using the fully featured mSupply client. Procuring the minimum multi-user satellite server configuration for each of these sites would be expensive. A solution has been developed that entails installing single-user clients machines (normally laptops) at these remote locations and then synchronising them to the primary server much like the Synchronised Multi-user configuration. | Lower cost than conventional synchronised multi-user as the single-user client license is less costly than multi-user client licenses. The [[synchronisation:introduction#synchronisation_server|Synchronisation server Module]] and [[web_interface:using_the_web_server|Web Server Module]] are required on the central server.| |
^ [[https://docs.msupply.foundation/en:mobile:user_guide|Mobile]] | This is a Synchronised Single-user configuration, but the users operate with mSupply Mobile (client) software on Android tablets. This apps has a reduced feature set, but is more than adequate for most Last-Mile needs. Local stock details are synchronised back to the Primary server, and can be monitored and reported on there. | Pricing is even lower than for Synchronised Single-User. We see this as the way forward for the medical supply chain in small and remote facilities. The [[synchronisation:introduction#synchronisation_server|Synchronisation server Module]] and [[web_interface:using_the_web_server|Web Server Module]] are required on the central server. | | ^ [[mobile:|mSupply Mobile]] | [[mobile:|mSupply Mobile]] is [[https://en.wikipedia.org/wiki/Open-source_software|Open Source software]] that is similar to the synchronised Single-user configuration, but the users operates the software app on an Android tablets. This app has a reduced feature set, but is more than adequate for most Last-Mile needs. Local stock details are synchronised back to the Central server, and can be monitored and reported on there. | Pricing is even lower than for Synchronised Single-User. This //was// the way forward for the medical supply chain in small and remote facilities - until [[https://docs.msupply.foundation/docs/introduction/introduction/|Open mSupply]] (see below) took that honour! The [[synchronisation:introduction#synchronisation_server|Synchronisation server Module]] and [[web_interface:using_the_web_server|Web Server Module]] are required on the central server. | |
| ^ [[about:which_one_for_you#open_msupply/|Open mSupply]] | [[about:which_one_for_you#open_msupply/|Open mSupply]] is the [[https://en.wikipedia.org/wiki/Open-source_software|Open Source software]] multi-platform mSupply software that has been under development by [[https://msupply.foundation/|the mSupply Foundation]] since 2020. Open mSupply has all of the flexibility of all of the other versions of mSupply with the benefit of being Open source. Local stock details are synchronised back to the Central server, and can be monitored and reported on there. | Pricing for smaller facilities (single-user stores) is the same as [[mobile:|mSupply Mobile]]. We see this as the way forward for the medical supply chain in both small and remote facilities and in large multi-user facilities. The [[synchronisation:introduction#synchronisation_server|Synchronisation server Module]] and [[web_interface:using_the_web_server|Web Server Module]] are required on the central server. | |
^ [[web_interface:msupply_customer_setup|mSupply Customer | ^ [[web_interface:msupply_customer_setup|mSupply Customer |
Web Interface]] | Allows staff of Customers in your mSupply system order stock on-line. It runs on a browser on any device: tablet, smartphone, net-book, desktop computer etc. | Depends on your situation - contact us. The [[web_interface:using_the_web_server|Web Server Module]] is required on the central server.| | Web Interface]] | Allows staff of Customers in your mSupply system order stock on-line. It runs on a browser on any device: tablet, smartphone, net-book, desktop computer etc. It's a little hard to see why this should be chosen over [[about:which_one_for_you#open_msupply/|Open mSupply]], as the costs are very similar, without the benefit of being able to operate a store... | Depends on your situation - contact us. The [[web_interface:using_the_web_server|Web Server Module]] is required on the central server.| |
^ [[integration:frontlinesms_integration|FrontlineSMS]] integration | mSupply has the ability to integrate with a FrontlineSMS installation. This allows a customer to send their current stock levels to mSupply using an SMS (text) message from any mobile phone. This is particularly useful if, for example, you are a mobile or remote health post or dispensary which doesn't have internet access and only needs to send in information about a few items at a time. | SMS module is required on the central server. | | ^ [[integration:frontlinesms_integration|FrontlineSMS]] integration | mSupply has the ability to integrate with a FrontlineSMS installation. This allows a customer to send their current stock levels to mSupply using an SMS (text) message from any mobile phone. This is particularly useful if, for example, you are a mobile or remote health post or dispensary which doesn't have internet access and only needs to send in information about a few items at a time. | SMS module is required on the central server. | |
| |
\\ | \\ |
\\ | \\ |
| |
| ===== A note about costs... ===== |
| ==== Software costs ==== |
| |
| When procuring software, an obvious question is what does it cost. We try to be as up-front as possible about what mSupply software costs. Even so, it's complicated. As you can see above, the mSupply ecosystem is complex and each component has different costs. For a start, we've tried to document the software costs on our [[https://msupply.org.nz/pricing/|pricing page]]. The amounts that you might pay for mSupply software can be divided into three components: |
| |
| * **License costs** Thanks to the generous support of many donor agencies over the decades of mSupply's existence, only the mSupply products built on the (very good!) [[https://us.4d.com/|4D database engine]] incur a license fee, up-front, lasting forever - refer [[https://msupply.org.nz/pricing/|Pricing]]. Not all of the 4D based mSupply products have a license fee; [[about:which_one_for_you#free-user|Free-user]] is ... free ;-).\\ [[about:which_one_for_you#msupply_mobile_android|mSupply Mobile]] and [[about:which_one_for_you#open_msupply|Open mSupply]] are both [[https://en.wikipedia.org/wiki/Open-source_software|Open Source software]], and so are <wrap em>FREE</wrap> of licence fees. |
| * **Installation costs** mSupply systems need to be configured to the needs of the supply chain system. In principle, software and hardware configuration can be done by system administrators in the host organisation. However, in most cases, [[https://msupply.foundation/|the mSupply Foundation]] is engaged to assist with software and hardware configuration. This is often done initially by one or more consultants travelling to the country for a number of weeks. The costs of this will normally be in the tens of thousands of dollars. Once a country has an mSupply system up and running, additional stores and sites can normally be added at much lower costs, with indicative prices below. For large implementations, local configuration capacity needs to be developed, and [[https://msupply.foundation/|the mSupply Foundation]] is very keen to train local system administrative configuration capacity. |
| * Configure a store, not including storage locations and complex user profiles: USD 100 |
| * Configure hardware: |
| * Tablet: USD 25 |
| * Single-user PC: USD 100 |
| * Server: USD 200 |
| * **Maintenance costs** As with any technology systems, there are ongoing maintenance costs including keeping software up-to-date((only applicable for mSupply products that have a license fee)) and providing support. This support could be provided by system administrators in the host organisation. However, in most cases, it has been found to be more effective to engage [[https://msupply.foundation/|the mSupply Foundation]] to provide support, at least in part. For large implementations, local support capacity needs to be developed, and [[https://msupply.foundation/|the mSupply Foundation]] is very keen to train local system administrative support capacity. |
| * For mSupply products that have a license fee, Up-to-date and support is charged as detailed [[https://msupply.org.nz/pricing/#316|here]]. |
| * For Open source products, support is charged as detailed [[https://msupply.org.nz/pricing/#317|here]]. |
| |
| ==== And all the other costs ==== |
| |
| Software is //never// the largest component of deployment and operational costs. Local circumstances can vary dramatically, but in one a typical developing country with in excess of 500 mSuppy stores, the experience has been that //after// the expensive initial deployment, deployment and operational costs have been: |
| |
| ^ Cost type ^ Deployment ^ Annual operation ^ |
| | License | 0% (Open source) | 0% (Open source) | |
| | Configuration / Support | 5.6% | 7.6% | |
| | Hardware | 37.3% | 9.1% | |
| | Internet | 0% | 36.6% | |
| | Training | 57.1% | 46.6% | |
| |
| {{ :about:pasted:20231115-070909.png }} |
| |
| Note that in this particular country, the annual costs of a the cheapest commercially available cellular internet connection //exceeded// the capital cost of the 10" Android tablets. |
| |
| Key conclusions: |
| * Training is the highest cost (rightly so!) |
| * Provision should be made for hardware depreciation (devices do break, get stolen, etc.) |
| * <wrap em>Software costs are normally < 10% of the costs (capital and operational)</wrap> |
| |
===== Referring to the server machine vs. server software ===== | ===== Referring to the server machine vs. server software ===== |