One attribute of the FPOS data model is that new data types can be defined easily and through independently deployed updates to the various microservices, these new data types can be rolled out without breaking changes even in regulated environments (not making a claim of any compliance here, just part of the design considerations). The JSON schema here are the bodies of each [Labware Map] and [Labware Transfer] data type I have identified as mechanisms to describe repeatable scientific workflows. They can be used as the data object freely by anyone who is developing commercial or DIY software tools to improve the efficiency of lab execution.

Following several meetings related to the core FPOS architecture which enables a "digital mirror" of any physical world environment, starting with a biopharma example, these slides have been created to provide an introduction to how the architecture enables user applications to support laboratory execution and data consumers access to curated data.

If you believe in the idea of industry taking charge of its own R&D lab productivity challenge by building its own better solution to R&D laboratory software, it will take investment. The DSDC needs roughly 10-15% of the R&D IT Opex budget for three years to solve this problem and reduce costs permanently. After some feedback on the consortium, here are three quick ways in which you can find that money in your existing budget.

Another feedback question from an interested industry peer who wonders if the intention of the DSDC is to push the existing commercial solution providers to improve their products and services. The DSDC is being formed because commercial solutions have failed to meet the needs of R&D labs for 30 years running with no real improvement on the horizon. The DSDC intends to solve this problem as a by industry - for industry approach and there is no intent with commercial solution providers. However, the the answer is yes, this is a way to push industry to improve because it will free them from their own technical debt...

A question posed by a trusted peer in the industry of lab informatics who asks this hard question on behalf of ANY potential DSDC investing member or user. The three key reasons why this solution will succeed where hundreds have failed are summarized here: The Commercial Model, The Product Design, The Consortium approach where we (industry) are solving our own problem the way it needs to be solved. Prioritizing the laboratory needs over the product time to market or profit.

An appropriate question to ask! Given all of the ways in which we need to fix the Rx industry, is the DSDC an appropriate thing to focus on right now? The backdrop is that we know if we make the choice NOT to act we will get the same decline in performance (more cost and more time per new drug), so the choice to act is clear. The nuance is that of many things to fix, what can we do for low effort and high impact? This decision is explored and the DSDC perspective on where to start is with streamlining laboratory orchestration and data management globally.

The commercial model of the DSDC is described in this article. The decoupling of product development from commercial delivery and support are components of a flywheel which will create a commercially sustainable software solution. Beginning with industry investment in a pre-competitive platform solution to laboratory efficiency and data management, the financial model for how this flywheel will enable a not-for-profit market leading solution to enable companies to focus their resources on new scientific innovation rather than spending tens of millions per year on the laboratory version of "basic productivity tools".

Today, laboratory workers spend a great deal of time and effort navigating their complex and ineffective landscape of commercial or bespoke DIY labware solutions each and every day. This detracts from the time they spend performing important research experiments or executing critical laboratory processes. One major contributing reason for this is due to what is described as a over-solved problem. The problem and the novel approach to solving this problem through system simplicity and technical innovation is described in this article.

A question from industry stakeholders about what standards, if any, the DSDC product will implement. Will the DSDC approach focus on industry alignment and implementation of standard ontologies? Part of the reason why the DSDC approach will be sustainable is because the product will focus on translators rather than standards. The concept of Dynamic Ontology Integration is described here in response to industry feedback.

Prompted by an immediate question from industry peers after the DSDC announcement, the question of how an industry consortium can create a sustainable commercial product. This first dive into the commercial model explains the early concept for a novel approach to not-for-profit software in the laboratory informatics market space.

The official first overview of the Digital Science Development Consortium. This overview article precedes this website and the DSDC will undoubtedly have evolved since this first version of the "complete picture" was shared but it will remain here for transparency and historical context of the evolution of the DSDC.