Biomedical Engineering Reference
In-Depth Information
the different partners access to subsets of compounds and/or assays in the
projects as relevant.
Although assay registration was implemented fairly early in LSP, it was
not deployed as a general tool. Assay registration functionality existed in
the old systems, although it was not as effective and the new LSP version
therefore did not initially give the users signifi cant new functionality. The
LSP version of assay registration would introduce a major, but necessary
data cleanup. Unfortunately, an assay information cleanup introduces
more work, not functionality, to the scientists, so 'an award' was needed
that would show the user benefi ts of this exercise. The award was a new
assay query tool that enabled searches across parameters from all global
research assays and therefore made it easier for the scientists to fi nd all
assays working against a certain target, species, etc.
This started the move towards using LSP for assay registration and
retrieval. Another important push came with external (partner) upload of
data and collaboration on project grids/SAR tables. In order to make sure
the external partners can understand and use the Lundbeck data, the
scientists need to clean up the assay information.
The last part of existing legacy functionality to be moved into LSP and
then improved, is our project overview/SAR table grids, displaying the
combined view of compounds and results in our projects. This should be
the centre/starting point for all data retrieval and analysis as well as
transactions in the form of new assay or compound ordering. Currently,
the project overview with the ability to see all history data on a single
compound has been ported to LSP (Figure 1.5), while ordering is in
the plans.
￿ ￿ ￿ ￿ ￿
1.10 Organisation
IT/Informatics departments normally consist of managers, business
analysts, project managers, applications specialists, etc. as well as
developers (if still available in-house). The departments therefore tend to
become large and costly while most of the individuals do not develop or
maintain applications but rather manage resources. However, the biggest
issue with these types of organisations are the translations, where valuable
information gets lost. There are translations from scientists to business
analysts, from analysts to project managers, from project managers to
developers - or more likely from project managers to the outsourcing
partner project managers and then to the developers. The handovers
between all these individuals are normally performed via a User
 
Search WWH ::




Custom Search