search.noResults

search.searching

note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
Building a Smart Laboratory 2017


from the potential user community, and then engaging in a prioritisation exercise to reduce the list to a specific set of requirements that form the basis of a request for proposal (RPF) to be presented to vendors. It is important that the business requirements


are fully clarified first of all; this ensures that the scope of the project is defined and can therefore help exclude some of the more exotic ‘needs’ that might arise. Any single item on the requirements list should justify itself not only financially, but also in terms of its usefulness and ease of use. Anecdotal experience suggests that some


requirements specifications could be shrunk by between 25 and 50 per cent by the removal of ‘wish list’ items – bringing cost-savings and lower cost of ownership, as well as easier user adoption. It is important for the project team and sponsors to be able to define what business problem the electronic laboratory notebook (ELN) will solve, and to ensure that user requirements are kept simple and are focused on solving the problem. Te formal RFI and RFP approaches can


only go so far, and it is essential that candidate systems be demonstrated and assessed with some preliminary configuration to establish and evaluate not only whether the system meets the functional requirements, but also whether it provides an acceptable user experience. In some respects, it makes sense to consider functional requirements and user requirements as separate criteria.


Business case development and project management


Building a good business case requires a thorough and systematic approach to understanding current limitations as well as future requirements for the business. It is important to see laboratory informatics as a component in a laboratory ecosystem (technology, processes and people), rather than ‘just another laboratory application’. Te following points should all be considered in formulating the case for a new informatics system.


Why do we need a new system? l What is the problem that needs to be solved? l Is there any quantitative data that illustrates the problem?


l Which laboratory areas will be involved in the project?


l Who makes the go/no-go decision? l What are the issues relating to IP (internal/ legal/patent)? and


www.scientific-computing.com/BASL2017


l Are there any regulatory compliance requirements?


Clarify why the organisation thinks it needs a new system. Tis is best achieved by developing a problem statement that quantifies a specific problem, or set of problems, about the laboratory’s productivity and/or knowledge management performance. Te scope and scale of the problem (and hence, the solution) should be identified. Te key decision-makers/budget- holders should also be identified, plus any other interested party who may have influence over a go/no-go decision. It is important to know what business level constraints may apply in terms of internal, legal or regulatory compliance.


“ Building a good business case requires a thorough and systematic approach to understanding current limitations as well as future requirements for the business”


Laboratory/company background l Use organisation charts to clarify roles


and responsibilities and organisational relationships;


l Identify the nature and scientific disciplines of the laboratory work and how they relate to each other; and


l Establish whether outsourced agencies (contract labs) are involved?


Establish the way in which the laboratory is organised, the nature of the work it undertakes and how it relates to internal and external organisations with whom it collaborates.


Current laboratory processes and systems l Which laboratory systems are already in use? (Are there SOPs?)


l Which data acquisition systems are already in use?


l Which teamwork/collaboration systems are already in use?


l Which document management systems are already in use?


l Who is responsible for the management and support of these systems?


l Is there a (electronic) records management policy? and


l Are there any specific policies and restraints relating to the introduction of IT systems?


Establish how the laboratory is currently working, paying specific attention to the use and effectiveness of manual systems such as


Practical considerations


worksheets, paper lab notebooks, and data management. Also identify major ‘electronic’ systems used for the acquisition, processing and management of data, and ask what happens to this data – where is it stored and for how long? Is it communicated or transferred elsewhere – if so, how? Is it backed up and/or archived? Can it be found? Is laboratory data the responsibility of the


laboratory, or does IT have any involvement? What level of involvement does IT have in the purchase and implementation of laboratory systems?


Future laboratory processes and systems l Based on interviews with laboratory


managers and laboratory staff, a model should be developed to illustrate the major relationships between laboratory data and information;


l Construct data workflow and laboratory process diagrams;


l Identify any conflicts in nomenclature and establish an agreed taxonomy;


l Identify the role (scope and scale) of existing laboratory systems in the model and diagrams; and


l Test the model and diagrams against each of the laboratory areas and other interested parties (IT, legal, QA, records management).


A high-level plan, showing the relationships, processes and data flows that describe a future state for the laboratory, should be developed. Tis should include an identified role for each of the laboratory systems and should clarify the specific functions of each. Any problems with laboratory terminology should be resolved. Te plan should be tested by presentation and discussion with the interested parties.


Business plan development l Quantify the benefits of the proposal, in


particular productivity gains, ROI and knowledge management, and support these estimates with case studies;


l Undertake a risk assessment, paying attention to process, technology and people- related risks. Align the risk assessment to the set of user requirements; and


l Prepare, and include in the business case, a high-level implementation plan that addresses any specific requirements and/or risks that have been identified.


Quantitative benefits should be identified, along with all risks. An implementation plan should address known risks and/or potential problems, in particular the strategic approach to roll out, e.g. a progressive deployment,


37


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44