request for proposal (rfp) - FIND [PDF]

As one of 9 priority digital health concepts identified by the WHO Agenda for Action on Digital health ... 2 Andre, Isaa

40 downloads 39 Views 407KB Size

Recommend Stories


REQUEST FOR PROPOSAL (RFP)
We can't help everyone, but everyone can help someone. Ronald Reagan

Request for Proposal (RFP)
If you want to become full, let yourself be empty. Lao Tzu

Request For Proposal (RFP)
When you talk, you are only repeating what you already know. But if you listen, you may learn something

Request for Proposal (RFP)
Be grateful for whoever comes, because each has been sent as a guide from beyond. Rumi

Request For Proposal (RFP)
Your task is not to seek for love, but merely to seek and find all the barriers within yourself that

Request for Proposal (RFP)
If you want to go quickly, go alone. If you want to go far, go together. African proverb

Request for Proposal (RFP)
Respond to every call that excites your spirit. Rumi

Request for Proposal (RFP)
We can't help everyone, but everyone can help someone. Ronald Reagan

Request for Proposal (RFP)
No amount of guilt can solve the past, and no amount of anxiety can change the future. Anonymous

REQUEST FOR PROPOSAL (RfP)
In the end only three things matter: how much you loved, how gently you lived, and how gracefully you

Idea Transcript


REQUEST FOR PROPOSAL (RFP) CONNECTED DIAGNOSTICS PLATFORM (CDP)

1

Table of Contents 1.

SUMMARY AND BACKGROUND ............................................................................................................................................ 3

2.

CDP RFP ............................................................................................................................................................................. 4

3.

PROPOSAL GUIDELINES ....................................................................................................................................................... 5

4.

PROPOSAL EVALUATION CRITERIA ...................................................................................................................................... 5

5.

SCORING CRITERIA............................................................................................................................................................... 5

6.

ADMINISTRATIVE INFORMATION.......................................................................................................................................... 6

7.

TECHNICAL INFORMATION ................................................................................................................................................... 7

8.

PRODUCT DESCRIPTION ....................................................................................................................................................... 9

9.

TRANSFER SCOPE - WHAT WILL BE HANDED OVER ............................................................................................................... 9

10.

FIND AMBITIONS AND WISHES FOR CDP......................................................................................................................... 9

11.

TIMELINES ..................................................................................................................................................................... 10

12.

FIND SUPPORT.............................................................................................................................................................. 10

Appendix A - Product Description ............................................................................................................................................ 11 1.

CDP COMPONENTS ............................................................................................................................................................ 11

2.

KEY FEATURES OF CDP SERVER ........................................................................................................................................ 11

3.

KEY FEATURES OF CDP BRIDGE ........................................................................................................................................ 12

4.

HISTORY ............................................................................................................................................................................ 12

5.

TRIALS AND STUDIES ......................................................................................................................................................... 13

6.

DIFFERENTIATORS ............................................................................................................................................................. 13

7.

INTEGRATION WITH OTHER PLATFORMS............................................................................................................................ 14

8.

DEVICES SUPPORTED ......................................................................................................................................................... 14

9.

DISEASES SUPPORTED........................................................................................................................................................ 15

10.

LANGUAGES SUPPORTED ............................................................................................................................................... 15

11.

PLATFORM ARCHITECTURE ........................................................................................................................................... 15

12.

CDP DEPLOYMENT ....................................................................................................................................................... 16

13.

COMPONENT VERSIONS AND LICENCES ......................................................................................................................... 16

14.

CDP DOMAIN MODEL ................................................................................................................................................... 17

2

1. SUMMARY AND BACKGROUND FIND is an international non-profit organization that contributes to the development and delivery of much-needed diagnostic tests for poverty-related diseases, including Tuberculosis, Malaria, Sleeping sickness, Hepatitis C, HIV, Leishmaniasis, Buruli ulcer and Chagas disease. FIND acts as a bridge between experts in technology development, policy and clinical care, reducing barriers to innovation and effective implementation of diagnostic solutions in low- and middle-income countries. Over the last 12 years, FIND has supported the development of 11 new diagnostic tests that address diseases of poverty. FIND has also established critical resources for the development of many other tests, including specimen banks, integral reagents, product profiles and policy briefs that provide better visibility on pressing diagnostic needs. Reliable and timely diagnostic test information is of paramount importance for the proper functioning of several components of the diagnostic and treatment cascade including patient management, epidemiologic surveillance, quality assurance, laboratory operations, and technical product support.1 Archiving test data in an accessible standardized database and enabling integration with laboratory information systems, electronic health records, and health program databases are basic requirements that allow laboratory diagnostic equipment to meet these needs. Diagnostic ehealth solutions have the potential to help overcome these problems and maximize patient and public health impact. This requires device connectivity, wherein testing data and results are automatically and securely sent to repositories, translated into useful information and channelled to appropriate parties.2 Although device connectivity within other industries has been commonplace for some time, within the healthcare community it is still considered to be in its infancy (Ohno-Machado, 2012). As one of 9 priority digital health concepts identified by the WHO Agenda for Action on Digital health for the End TB Strategy for target product profiles, the adoption and use of diagnostics connectivity solutions are also monitored as core indicators for laboratory strengthening under the End TB Strategy3. According to the WHO Framework of indicators and targets for laboratory strengthening under the End TB Strategy, all sites that use WHO-recommended rapid diagnostics should be transmitting results electronically to clinicians and to information management systems using data connectivity solutions no later than 2020 (Indicator 4). Furthermore, remote monitoring via data connectivity solutions should be used to monitor key performance indicators at all sites that use WHO-recommended rapid diagnostics no later than 2020 (Indicator 9).4 The pace with which Information & Communications Technologies (ICT) has developed and diversified over the years can only be described as revolutionary. About 40% of the world’s population can access the Internet. As global connectivity expands, and hardware becomes more widely available and affordable, digital health products are destined to become increasingly present in the daily life of patients and practitioners.1 1 D Falzon et al. Digital health for the End TB Strategy: developing priority products and making them work. European Respiratory Journal 2016 2 Andre, Isaacs et al. Connectivity of diagnostic technologies: improving surveillance and accelerating tuberculosis elimination. The International Journal of Tuberculosis and Lung Disease 3 World Health Organization. Framework of indicators and targets for laboratory strengthening under the End TB Strategy (WHO/HTM/TB/2016.18). Geneva, World Health Organization; 2016. Available from: http://www.who.int/tb/publications/labindicators 4 Global Laboratory Initiative (GLI). GLI Quick Guide to TB Diagnostics Connectivity. 2016. Under publication. To be available from http://stoptb.org/wg/gli/

3

The steady transition in the management of medical records and surveillance systems, from paper-based methods, through electronic systems installed on isolated computer terminals, to systems on local area networks and, now, Internet-accessible databases with storage of data on the cloud, is an evolution that will reduce tedious and time-consuming paperwork and reduce errors.1 New opportunities are created for public health researchers, health system managers, patients and practitioners to explore how the innovative use of these tools can strengthen health systems. Field experience with digital health interventions is growing. The increased deployment of cutting-edge digital health concepts is destined to inject greater power, speed, flexibility and diversity into the same processes that have been helping public health practitioners, managers and clinicians to deliver better care to populations and patients for several decades.1 In reaction to this need FIND has developed the Connected Diagnostics Platform (CDP) for: 1) The centralized and secure aggregation and flexible visualization and management of clinical test and device performance data from diagnostics; and 2) The digitization of diagnostic test workflows and laboratory processes from patient registration, case history, examination and reporting of samples, as well reporting of quality metrics and key performance indicators. The CDP allows centralised and secure aggregation, and flexible management of data from multiple diagnostics, regardless of manufacturer, disease, or point of data generation. The platform allows users to manage all data coming from various connected diagnostic platforms, and data utilization through data analytics, presentation, informatics, and reporting capabilities. A comprehensive Application Programming Interface (API) enables the routing of data to existing health and management applications. The CDP reduces challenges associated with fragmented data sets, supporting a common standards approach to formats, storage, security, access, and sharing.

2. CDP RFP The opportunities for eHealth connectivity solutions are vast. The pace at which these interventions are being implemented has grown rapidly in the past few years and the potential for global adoption high. FIND developed CDP for other organisations to implement, and believes the platform has reached minimum viable product status. FIND is issuing this RFP to hear from parties interested in adopting CDP as a platform that can benefit their own eHealth strategies and global health needs.

4

3. PROPOSAL GUIDELINES Proposals must be received by 5pm CET on 17 March 2017. Proposals received after the stipulated date and time shall be invalid. All proposals must be signed by an official agent or representative of the organisation or company submitting the proposal. Proposals should be submitted in English to [email protected] and formatted in Microsoft Word or PDF. Selection of the applications will be based upon separate assessments of the proposals. FIND reserves the right to request further information throughout the RFP process. All email subject lines and document naming must be in the following format: a) Your organization name – Proposal – FIND – CDP-2017 Any questions or clarifications regarding this Request for Proposals (RFP) should be submitted in writing via e-mail to [email protected] prior to the closing date.

4. PROPOSAL EVALUATION CRITERIA To ensure consideration for this RFP, your proposal should be complete and include all of the following criteria: ● Organizational experience: Bidders will be evaluated on their organizational strategy, experience and capability as it pertains to diagnostic challenges in the global health domain ● Capability & capacity: Bidders will be evaluated on their capability and capacity, including history of their work pertaining to development and implementation of ICT solutions within the global health domain as well as client testimonials and references ● Quality & security: Bidders will be evaluated on their processes, practices and attitude towards product quality and data security ● Data use: Bidders will be evaluated on their intent of use of data that may be collected through CDP ● Geographical capacity: Bidders will be evaluated on their capacity to provide maximum exposure and support for CDP on a geographical basis ● Whilst it is FIND’s intent to transfer ownership of CDP entirely, based on responses, and in particular to geographical capacity, the right to select multiple applicants that are able to support and implement CDP on a regional basis is reserved. ● Where FIND judges more than one application to be complimentary, FIND reserves the right to suggest partnership within the RFP process.

5.

SCORING CRITERIA

The award criteria shall be based on a combination of technical capability, geographical capacity and intention. The total score comprises 60% of the technical score and 40% of the administrative score. Each question in the Proposal will be given a maximum score of 4 points where: 4 = Very Good, 3 = Good, 2 = Satisfactory, 1 = Poor 0 = Not satisfactory depending on the basis of assessment as specified for each section. 5

The scoring system is shown in the table below, which also provides an example to illustrate the calculations. Technical proposal 12 4 48

Number of questions Max score per question Total points

Administrative proposal 11 4 44

Example provided in highlighted cells below

12 4 60%

Administrative Information 11 4 40%

35%

25%

48 60 =48x60/48 60

22 20 =22x40/44 20

Technical Information Number of questions Max score per question Maximum Percentage Minimum Percentage (for eligibility) Scored Percentage obtained

6. ADMINISTRATIVE INFORMATION In addition to answering the questions below the bidder is required to provide the following information in their proposal. ● Copy of business registration documents, including proof of legal operation in their country of residence. ● Overview of company/organization history and statement of strategy. ● Copies of any certificates or standards qualifications as answered below. ● A statement as to why they wish to adopt CDP and perceived benefits.

#

Questions

Assessment based on

1

Please provide all office locations and operational points Capacity to provide maximum of presence. geographical support

2

Please provide number of full time employees, consultants and sub-contracted agents including percentage split by function.

Capability to provide all functions needed for product success

3

Please provide an overview of any quality standards achieved by your organization i.e. ISO 27001

Attitude and experience of quality standards

4

Please provide an overview of current and planned

Strategic fit

6

activities in global health including product development, implementation and support. 5

Please provide an overview of your financial status i.e., grant led or profit led. Please provide summaries of past three years’ accounts.

Organizational stability

6

Brief description of general arrangements to identify and Risk mitigation and operational mitigate against financial, legal, reputational and processes operational risks to clients (e.g., loss, damages, force majeure event, budget and cost overruns, quality assurance compliance and conflict of interests).

7

Please provide a description of your approach for achieving competitive and transparent pricing of products and solutions.

8

Please provide your experiences and track record of Track record and processes delivering projects on time and on budget. Please describe any general or specific project approaches used.

9

Please describe your experiences and capabilities of contracting and working with non-commercial entities such as Governments and NGOs.

Track record

10

Please provide an overview of your mandates, processes and practices to protect against corruption, fraud and bribery.

History and mandates

11

Please describe how your organization plans to use or share any data collected during studies and implementation of CDP.

Intended use

Organizational approach

7. TECHNICAL INFORMATION #

Questions

Assessment based on

1

Please describe experiences of developing products or Experience and diversity solutions including both hardware, e.g. diagnostic devices, and software, e.g. data management systems for global health needs, including supported use cases and challenges addressed.

2

Please describe experiences of developing or implementing products or solutions that contain the ability to send electronic data from hardware, e.g. 7

Experience and capability

diagnostic devices to remote repositories using fixed line or cellular technologies. 3

Please provide information for the volumes, locations, usage and impact of technical solutions that were developed.

Track record

4

Please provide information describing your capacity to develop, or modify software including an overview of the development team(s) and methodologies or standards followed.

Capacity and capability

5

Please provide information describing your capability to Capacity, capability and approach support deployed technical solutions including locations and hours of support teams, languages supported, service level agreements and escalation processes. In particular, please describe your approach to dealing with mission critical and emergency issues.

6

Please describe your experiences, capabilities and approach to supporting technical solutions in remote rural locations where site visits would be required.

Capability and approach

7

Please provide your experiences and capabilities in collecting and storing confidential electronic data. Please provide an overview of security policies and practices including any specific standards followed or accreditations achieved.

Knowledge, policies, approach, qualifications

8

Please provide your experiences and capabilities for complex data informatics, presentation and reporting.

Capability

9

Please provide an overview of any quality systems and standards that are used in product development, implementation and support

Number and relevance of systems

10

Please provide an overview of your capabilities for the management or monitoring of GSM cellular networks

Capabilities and systems used

11

Please provide an overview of products or solutions that you have provided training for. Please describe the training needs for each and the approach taken.

Number and approach

12

Please provide a copy of any non-confidential guides, Content and quality training materials or other user facing documentation that may have been developed for technical products and solutions

8

8. PRODUCT DESCRIPTION A condensed description of the CDP can be found in Appendix A. Detailed descriptions will be available to interested parties upon request.

9. TRANSFER SCOPE - WHAT WILL BE HANDED OVER 1.

Server code - All CDP code is currently held in a GitHub account. At the end of the RFP process all code constituting the CDP server components will be transferred to a nominated GitHub account. Each organisation will have an opportunity for code review and evaluation of CDP prior to proposal submission.

2.

Client code - code constituting the component called CDP Bridge will also be transferred on the understanding that this is already being used in selected FIND connectivity projects.

3.

Graphics and logos - The CDP platform and its components have had specific logos designed. All rights and original files associated with logos and graphics will be offered in the transfer.

4.

Domain names - The CDP platform currently uses the domain name www.thecdx.org - this will also be offered as part of the transfer.

5.

Development history - CDP has been developed using an AGILE development methodology. User stories, enhancements, change requests, bugs and other issues have been raised and categorised in the Redmine platform. These issues can easily be exported to CSV file for ingestion into preferred development management platforms.

6.

Documents & designs - All documents and designs that have been created during the CDP development and test processes will be available for transfer at the end of the RFP process. A full library of these documents is available for inspection during the CDP evaluation stage.

10. FIND AMBITIONS AND WISHES FOR CDP 1.

FIND consider the CDP code to have reached a status of Minimum Viable Product for the purposes of collecting and aggregating data from multiple diagnostic platforms and the digitalisation of diagnostic test workflows including patient case management. With the many challenges that can be overcome with ICT solutions for global health, FIND prefers applications where the continued development and enhancement of this core platform is prioritised e.g. to support additional diagnostic platforms and diseases.

2.

FIND supports diagnostic challenges in countries where the burden of disease is high. Implementation of CDP in priority countries would be preferred.

3.

FIND developed the CDP as a licence free platform for use to address global health challenges. It is the wish of FIND that CDP is used for its original intended purposes. FIND understands that 9

commercial interests may also need to be taken into account and will consider applications that incorporate other licensing approaches. 4.

FIND will use the outputs, expertise and lessons learned from the development of CDP to enhance and promote the evolution and successful roll-out of comprehensive connectivity solutions including CDP and others.

11. TIMELINES 1.

REQUEST FOR PROPOSAL TIMELINE All proposals in response to this RFP are due no later than 5pm CET March 17th 2017. Evaluation of proposals will be conducted from March 20, 2017 until March 31, 2017. If additional information or discussions are needed with any bidders during this window, the bidder(s) will be notified. The selection decision for the winning bidder(s) will be made no later than April 7, 2017. Notifications to bidders who were not selected will be completed by April 3, 2017. Upon notification, the transfer of assets with the winning bidder(s) will begin immediately. Transfer of assets will be completed by April 28, 2017.

2.

CODE REVIEW AND PRODUCT EVALUATION TIMELINE Each organisation will have an opportunity for code review and evaluation of CDP prior to proposal submission. Evaluations of the code that constitutes CDP v1.2.3, demonstrations of end to end data transfer from selected diagnostics and portal walkthroughs will be scheduled for interested parties during February and March 2017. Parties interested in evaluation and demonstration should contact [email protected]

3.

HANDOVER PROCESS AND TIMELINE Upon transfer of code and documentation FIND will offer a workshop to winning parties to include training for installation, maintenance and troubleshooting. These workshops will be completed by May 26, 2017.

12. FIND SUPPORT In order to ensure the maximum possible success for CDP, FIND will offer the RFP winner technical support to address questions relating to code for a period of 12 months following the transfer of assets. It is hoped that FIND are able to collaborate with the RFP winner, as it does with other platforms, providing programmatic support for future enhancements, implementation and guidance.

10

Appendix A - Product Description 1.

CDP COMPONENTS

CDP consists of following two major components: 1. CDP Server - web based connectivity platform 2. CDP Bridge - a client component used for capturing and transmitting results from diagnostic devices

2.

KEY FEATURES OF CDP SERVER ● Web application for the capture and representation of data collected from multiple remote diagnostics platforms regardless of manufacturing origin ● Web application for the capture of data for the management of multiple diseases ● Web application can be hosted in virtual servers a.k.a cloud hosting or on site within the customer’s own IT infrastructure ● Framework for the support for multiple languages (current implementation - English and Vietnamese) ● Patient Electronic Medical Record ● Fully digital diagnostic testing workflow including patient registration, case/episode registration, history of previous treatment, ordering of diagnostic tests, reporting of test results, upload of xray files, lab manager release of results ● Alerting functions to report notifiable events via email or SMS ● Ability to alert specific users when selected conditions are met (e.g. test result available) ● Configurable user permissions management system ● Ability to connect to multiple devices via configurable ‘device manifests’ ● Manual results entry for offline tests e.g. microscopy 11

● ● ● ● ● ● ● ●

3.

Test referral system to other sites Laboratory manager review and approval of results prior to release to clinical staff Finance approval for test order payment Ability to integrate approved results automatically into integrated systems Multiple CSV downloads of key data, for reporting purposes Ability to search for patients across the entire hierarchy Aggregated site and devices dashboards Application Programming Interface (API) for data extraction to other systems KEY FEATURES OF CDP BRIDGE

● ● ● ● ● ● ● ● ● ● ●

Interrogates the database of devices and extracts all available data Displays status of instruments connected Sends data to nominated servers according to schedules or requests by users Displays data queued and available to send Displays data previously sent Provides transmission reports to users and email recipients Caching of test and device data if internet is not available Able to generate dummy data for debug and testing purposes Provides user authentication and security Supports a one click installation method Has an automatic update mechanism allowing new versions, enhancements and bug fixes to be deployed without the need of site visits by IT staff ● Supports UTF-8 language characters and can be customised for each country of deployment ● Supports use with Windows XP computers and above

4.

HISTORY Version 1.0 – the original version of CDP focussed purely on providing a platform for connectivity and system integration. This version was command line driven. ● Version 1.1 – Introduced the UI, and supporting frameworks for core entities such as; sites Patients and test orders. Also included was ‘core’ test order workflows for TB, HIV and Ebola. ● Version 1.2 – This version established the concept of ‘core’ and ‘customised’ code, by introducing the first customisation, which was for the Vietnam NTP. This not only introduced essential elements such as multi-lingual support, but has also driven major refinements in the workflow and state model. ● Current Version V1.2.3-RC03 ●

12

5.

TRIALS AND STUDIES

CDP for Vietnam Study - v1.2.3 RC03 - 2016 This ongoing study project (due to complete in the 1Q17) seeks to understand the ‘feasibility and effectiveness of a fully digital; test order, examination and reporting, workflow’. This is being achieved via the following activities: ● ● ● ● ● ●

Customisation of the TB test order workflow to match the Vietnam NTP requirements Automatic collection of Xpert results via the CDP Bridge Manual collection of microscopy results via CDP Processing of patient testing alongside the ‘business as usual’ patient testing (shadow process) Integration of CDP into test versions of eTB manager and Vitmes. Capacity building within Vietnam, to run drive adoptions, manage operations and provide in country customer and technical support.

Data collection is ongoing with over 5000 patients registered and the study period completes 6th of Jan 2017 with a journal submission expected to be available by end of 1Q17. To date the project has been successful in modelling the patient testing processes and driving system integration according to the studies business rules. The CDP software has been well received and shown to be both stable and usable. Connectivity for Reducing Reporting Times - v1.1- 2015 ● Vietnam - Pham Ngoc Tach Hospital ● Peru - Universidad Peruana Cayetano Heredia ● Peru - Laboratorio de Micobacterias at the Instituto Nacional de Salud Report available upon request

6.

DIFFERENTIATORS

A number of other connectivity platforms have been developed by manufacturers and independent companies. All of these platforms have tended to support the data collection for either a single disease or a single or limited number of diagnostic tests. In addition to this they also omit the patient as part of the system entity model. The functionality of these systems focusses on the monitoring of the device and how many tests have been performed by devices and sites as well as associated metrics like error rates. The lack of a patient entity in these cases makes it difficult to associate test results with the patient and with a diagnostic pathway such as those seen with Tuberculosis a single patient can have multiple episodes of the disease in their lifetime, during any of one those episodes will have multiple encounters with a clinician and gives multiple samples. Simply counting tests performed on samples without the ability to trace this at a patient level does not provide the capability to accurately assess the disease burden of a country. In addition to displaying metrics regarding number of tests performed or indicators of error rates, the CDP has been designed to accommodate common laboratory testing workflows and offers the full digitization of the paper based forms that are used i.e. for patient registration, sample referral and result 13

reporting. The concept of the patient and the digitization of these forms ensures that the entire end to end process of the diagnostic pathway is captured in a single system, that data is easily stored, that these data are easily accessible for informatics purposes but above all that the results can be linked back to the patient being tested so that decisions on their care can be taken. Below is an example of the CDP workflow.

7.

INTEGRATION WITH OTHER PLATFORMS

The collection data from diagnostics may also be required to be used within other software applications i.e. DHIS2 for surveillance purposes. The CDP has been developed with a full API for the extraction of collected data into other systems. The CDP API is described at http://bfstaging.co.uk/cdpapi/ The CDP API has been used successfully to parse data from CDP to DHIS2, eTB Manager, OpenMRS and local hospital and laboratory systems used in Vietnam and India. Please see trials and studies section.

8.

DEVICES SUPPORTED

Today FIND have in various studies and proof of concept trials connected a number of different diagnostic platforms. CDP utilizes a concept called the CDP manifest in order to translate the output files from diagnostic platforms into formats that are understood by CDP for processing purposes. The CDP manifest system supports the mapping of any output file from a device using XML syntax. The manifest for each device only has to be written once before use. An example of a CDP manifest can be found at http://bfstaging.co.uk/cdpapi/ The following diagnostic platforms have been connected. ● Cepheid GeneXpert ● Alere PIMA 14

● Alere Q ● Hain Genoscan ● Qiagen ESEquant LR3 In addition to the above test platforms CDP also offers the results capture from diagnostic tests that are not connectable such as microscopy. FIND adopted this practice so that data from the full range of diagnostic platforms and test types could be captured and used and not just those platforms that produce results in a digital file. The majority of tests performed for TB for example are still performed using microscopy. The capture of results from these platform relies on the manual entry of the result into the digital forms as discussed earlier.

9.

DISEASES SUPPORTED

CDP was developed with the aim of supporting multiple diseases. Whilst various devices have been added and concepts tested the workflow and usability is most complete for the testing of TB. Minor amendments relating to the workflows and forms used would be required to additionally include HIV. Other disease states would need to be evaluated.

10. LANGUAGES SUPPORTED The code includes a multilingual framework allowing a default language to be set for the system and for the user to switch language at any time. CDP is currently available in English and Vietnamese. CDP uses language strings making it very easy for additional languages to be added by simply providing translation to the English fields.

11. PLATFORM ARCHITECTURE The CDP has been developed using the following technologies: ● Ruby On Rails - a web application framework written in under the MIT License provides default structures for a database, a web service, and web pages. It encourages and facilitates the use of web standards such as JSON or XML for data transfer, and HTML, CSS and JavaScript for display and user interfacing. As of January 2016, it is estimated that more than 1.2 million websites are running Ruby on Rails. Some of the largest sites include Airbnb, GitHub and Yammer ● MySQL - is an open-source relational database management system (RDBMS). In July 2013, it was the world's second most widely used RDBMS, and the most widely used open-source client– server model RDBMS. MySQL is used in many high-profile, large-scale websites, including Google, Facebook, Twitter and YouTube. ● HTML5 - is a markup language used for structuring and presenting content on the World Wide Web. It is the fifth and current version of the HTML standard. HTML5 includes detailed

15

processing models to encourage more interoperable implementations and includes features designed for low-powered devices such as smartphones and tablets. ● ReactJS - is an open-source JavaScript library providing a view for data rendered as HTML. React views are typically rendered using components that contain additional components specified as custom HTML tags. React offers a model in which subcomponents cannot directly affect enclosing components; efficient updating of the HTML document when data changes; and a clean separation between components on a modern single-page application. ReactJS is maintained by Facebook, Instagram and a community of individual developers and corporations and is currently being used on homepages such as Netflix and Airbnb.

12. CDP DEPLOYMENT The deployment of the CDP is easily managed by the utilisation of a ‘Container Management’ platform called Docker. A Docker container wraps up a piece of software in a complete file system that contains everything it needs to run: code, runtime, system tools and system libraries – everything that needs to be installed on the server. By encapsulating and isolating everything in a container, this guarantees that the container will always run the same, regardless of the environment it is running in - CDP can be run in any environment on any infrastructure. For years virtual machines (VMs) were seen as the status quo for packaging and running applications. Containers and VMs seem similar, but containers utilise a different architectural approach. VMs require a full operating system (OS) inside of each VM in order to run the service inside of it. Each virtual machine includes the application, the necessary binaries and libraries and an entire guest operating system - all of which may be tens of GBs in size. Containers have similar resource isolation and allocation benefits as virtual machines but their architectural approach allows them to be much more portable and efficient. Containers include the application and all of its dependencies, but share the kernel with other containers. They run as an isolated process in the user space on the host operating system. For more information on containers and Docker please visit https://www.docker.com/

13. COMPONENT VERSIONS AND LICENCES Component

Version

Licence

Docker

1.12.2

Apache 2.0

Ruby

2.3.1

BDSL copyrighted free software

Rails

4.2.7.1

MIT

Nginx

1.6.2

http://nginx.org/licence

MySQL

5.7

GPL

Redis

3.04

BSD

ReactJS

1.3.2

BSD 16

14. CDP DOMAIN MODEL A diagram of the CDP Domain model can be found in Appendix B as a separate document.

17

Smile Life

When life gives you a hundred reasons to cry, show life that you have a thousand reasons to smile

Get in touch

© Copyright 2015 - 2024 PDFFOX.COM - All rights reserved.