|
Can we host Bika LIMS on our own computers?
Do we have to pay?
What do I get?
Where's the catch?
They say with Open Source my lab gets better SEO visibility?
Installation
Most Bika and Senaite professionals do server installations at discounted prices
Configuration
Big configurations can be done from spreadsheets for savings, Import setup data
Instrument Interfacing
Not recommended on the long term, massage results into table format used by Bika's generic results importer
|
Why are Support hours so expensive? What do I get?
What is the thing with LIMS Support buckets?
Contracts based on fixed retaining fees, don't reward hard working labs that use less support
With buying Support buckets, they only consume support credits when really needed. Win Win
So is it any good?
Open systems undergo comprehensive quality control, inherently so being managed in open repositories
New code gets picked apart by devs intending to use it themselves. Community users nail bugs in beta releases
Good release masters only accept well documented standardised code that include unit tests
Professional Open Source, POS, has become better than closed systems, for all its inherent benefits unmatched in proprietary environments
Not. Tips and Tricks
Servers, Barcode printers and scanning, benchtop PCs
Where is my password?
Good question
|
Why are more labs not using Open Source LIMS?
Labs don't consider Professional Open Source (POS) LIMS,
Unfamiliarity
Labs an financial managers do not realise they can have, more affordably, on tailor made LIMS delivery,
FULL OWNERSHIP
UNLIMITED USERS on unlimited servers
ACCESS to the lims program code
FREE UPGRADE PATH
FREEDOM to MODIFY their lims, using their own resources
NO LICENSE FEES
NO VENDOR LOCK-IN
NO FIXED MAINTENANCE CYCLES
Widespread FUD
Fear, uncertainty and doubt - a disinformation strategy used in sales, marketing, public relations and politics. ... to influence perception by disseminating negative, dubious or false information in an appeal to fear'. Wikipedia
For an example, see Free LIMS an Oxymoron, where all the OS attributions originate from the authors' uncertainty facing a delivery model providing true value. Comprehensively taken down at Really?
|
The difference between Bika and Senaite
Bika 1,2 and 3, 2002 to 2017, established the foundation Senaite rests on, its initial design analysis went under the Bika 4 moniker, with an emphasis on performance and maintainability
In 2018 it manifested under new title Senaite to resolve the project's nagging naming issue at the same time. The project and Cape Town founding company were both using Bika in their titles, unfair to other contributors
|
Bika Lab Systems contributes her code to Senaite, but the bulk is coming from Europe nowadays, some of the best, and via strict release management and quality control
The code has been transformed, and both project goals achieved with aplomb, and you'll still find the original Bika bits at its heart
With near 20 years invested, we maintain the Bika brand independently from Cape Town, providing add-ons to extend the generic Senaite base with functions outside its lean performance driven scope
|
These are often requirements in distinctly differentiated lab disciplines collected in Bika branches, e.g Bika Cannabis vs Bika Covid
Bika also distributes complete typical configurations, fine tuned over years.
In the spirit of Ubuntu, Bika strives for a more holistic delivery model than that pursued in the Northern hemisphere
We value directness as in 'Tell it as it is' translated from isiZulu 'to report'. Not always politically correct, but more professional
|
