DAW3
DAW3
BI-AS-CPI IT RDM
DE-AS-AMES-STUDY-MANAGER IT RDM
DE-AS-COMETASSAY IT RDM
DE-AS-COLUMBUS IT RDM
DE-AS-INCELL-ANALYZER IT RDM
BI-CS-NBEINFOPEDIA IT RDM
DE-AS-CRN IT RDM
BI-AS-UNICORN IT RDM
BI-AS-UNICORN-NGXP IT RDM
BI-CS-XYBION IT RDM
BI-AS-QUATTRO-CM IT RDM
BI-AS-TRACEQ IT RDM
RDG-AS-TRP IT RDM
BI-AS-KNIME IT RDM
BI-AS-ISSA IT RDM
DE-CS-TCEP IT RDM
BI-AS-CSCS IT RDM
BI-AS-PIPELINE-PILOT IT RDM
BI-CS-DRUGDEV IT RDM
DE-AS-DRYLAB IT RDM
BI-AS-FUSION IT RDM
BI-AS-MOSAIC IT RDM
BI-AS-MATERIALSTUDIO IT RDM
BI-AS-BI-D360 IT RDM
BI-AS-MYSTUDYWINDOW IT RDM
BI-AS-CPD3 IT RDM
BI-AS-CTA IT RDM
BI-AS-EVMPD IT RDM
DE-AS-WATSON-LIMS IT RDM
DE-AS-LEGACY-DATA-BIO2100 IT RDM
BI-AS-VENUS IT RDM
DE-AS-DNA-BANK IT RDM
DE-AS-ILCAS IT RDM
DE-AS-RAVER IT RDM
DE-AS-LABWARE-BP-NGXP IT RDM
BI-AS-DAHLIA IT RDM
RCV-AS-AREST IT RDM
BI-AS-BICHROM3 IT RDM
RDG-AS-APERIO IT RDM
DE-AS-DSC-TGA IT RDM
DE-AS-SYMPATEC IT RDM
BI-CS-CT-INTERACTIVE-ENGAGEMENT IT RDM
RDG-AS-ELYSE-DATA-ARCHIVE IT RDM
BI-AS-SENSE IT RDM
BI-IS-SCIENCE37-DCT IT RDM
L3 Organization CMDB: Managed by
IT RDM Research Andrea Pinkney
IT RDM Development Andreas Koch
IT RDM Development Andreas Koch
Bemus, Allen
German*
German*
English*
English*;#German*
English*;#German*
English*;#German*
English*;#German*
English*;#German*
English*
English*
English*
English*;#German*
English*
English*;#German*
English*;#German*
English*
German*;#English*
English*
English*
English*
German*;#English*
English*
English*
English*
English*
English*
English*
English*;#German*
German*
English*
English*
English*
English*
English*
German*
German*
English*
English*
English*
English*
Support Level Internal Support Effort (FTE)
2nd Level 0.20
Application Monitoring 0.01
Application Monitoring 0.03
3.00
2nd Level;#3rd Level 0.20
2nd Level;#Application Monitoring
2nd Level;#3rd Level 0.05
2nd Level;#3rd Level;#Application Monitoring 0.20
2nd Level;#3rd Level;#Application Monitoring 0.20
2nd Level 0.00
2nd Level 0.01
0.10
2nd Level 0.00
Internal Support Location CAPRY: EOC Support Type Application Type
Full System Support Application Service Provider
Germany Full System Support Commercial Software Package
Germany Full System Support Commercial Software Package
Others Server-based
Server-based
Others Server-based
Others Server-based
Laboratory Information Management System (LIMS) Server-based
Others Cloud
Others Server-based
Others Server-based
Others Server-based
Cloud
Others Server-based
Others Server-based
Others Server-based
Server-based
Others Server-based
Others Server-based
Others Server-based
Others Server-based
Laboratory Information Management System (LIMS) Server-based
GE Healthcare
Inveni AI
Xybion
Instem
KNIME AG
Scitegrity Limited
Titian Software
inhouse
inhouse
inhouse
LabWare
Waters
Definiens
Medaptive Health Inc. TCS, India
inhouse built - Oracle/MSAccess
Instem
TCS, India
External Support Level External Support Effort (FTE)
3rd Level
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Skills Required for Support
SQL, Linux
Not applicable. This will become a SaaS solution hosted and supported by the vendor.
SL
SQL, Excel, Windows Server
90%
100%
0% 0
0
0
Level 2 Tickets Per Month Level 3 Tickets Per Month ServiceNow Usage
2 20
1 3 Yes
Yes
Yes
0 10 No
10 10 Yes
0 0
0 0 No
0 0 Yes
0 0 Yes
Support Window Onsite Support Total External Spend Variable
10 x 5 (EMEA)
10 x 5 (EMEA)
24 x 7 (APAC/EMEA/AM)
24 x 5 (APAC/EMEA/AM)
5,000.00 €
Comments
KH Pfeifer: Likely to move to EOC. Waiting for business approval - July 2020
on site support; neede from time to time/Transfer to TCS planned (see document "Service
Description BI-TCS: IT RDM Engagement Run Services - Extension")
on site support; neede from time to time/Transfer to TCS planned (see document "Service
Description BI-TCS: IT RDM Engagement Run Services - Extension")
August 20202: Christina Paradis: The project is still in scoping phase, so the timeline is not finalized.
The high-level estimate at this point is approximately July 2021
Transfer to TCS planned (see document "Service Description BI-TCS: IT RDM Engagement Run
Services - Extension"). Application System is currently prepared to be deployed to the global user
community -> QuattroCM Rollout (62705). There is no available data/experience to tell more about
the required effort and number of tickets.
KH Pfeifer: System currently under development - July 2020.
Michael Osswald: To be discussed. Might become a cloud solution
This will become a SaaS cloud solution.
Transfer to TCS planned (see document "Service Description BI-TCS: IT RDM Engagement Run
Services - Extension")
In house developed application and Chemaxon software used additionally
Clinical System. Application is under development; production est. 2022. Transfer to TCS planned
(see document "Service Description BI-TCS: IT RDM Engagement Run Services - Extension")
Development delayed. Expected delivery for productive validated version of TCEP in 2023.
Transfer to TCS planned (see document "Service Description BI-TCS: IT RDM Engagement Run
Services - Extension")
Transfer to TCS planned (see document "Service Description BI-TCS: IT RDM Engagement Run
Services - Extension")
August 2020: Lars Bergander (RDM Architect): System still in PLAN status in CAPRY. Hence, moved
to RDM_X Bundle.
Transfer to TCS planned (see document "Service Description BI-TCS: IT RDM Engagement Run
Services - Extension")
Business critical yes, but due to the simple and small IT footprint (client based, only licenses on
servers), IT risk: low
March 2021: Jose Carlos Escribano: RDM would like to transfer the system in 2022 with a Full
System Support
2020: Transfer to TCS planned (see document "Service Description BI-TCS: IT RDM Engagement Run
Services - Extension")
Application is currently business owned. Discussing possibility to move to EOC with Function.
Transition not planned for the next 2 years. System's future not finally clarified yet. Maybe system
will cease as own system and move to an umbrella system. System does not need much support,has
no user interface. Trans.effort maybe higher than savings.
One component of the system is a vendor supplied software and handheld scanner. Transfer to EOC
planned (see document "Service Description BI-TCS: IT RDM Engagement Run Services - Exten
Osswald,Michael (IT RDM): suggests to move the transition date to a later timepoint. Late 2021.
It is planned to re-implement the system based on a new technical platform in order to replace the
outdated technology and to move away from ORACLE. Project is supposed to start in Q4/2020
It was already agreed with EOC, that EOC cannot support the system, because the user interface
and all documentation is completely in German
August 2020: Olga Moehlinger: System will be in production by the end of this year.
The system is in implementation phase right now and will go into production in September. There
are no experiences about support efforts, ticket count, ... At the beginning the efforts will be hire
and decrease with more experineces
KH Dreher: It is ok if the support language for the above system is just English
August 2020: Added according to Tim Skinsky
System will go live earlierst in Oct 2021
Transfer to TCS planned (see document "Service Description BI-TCS: IT RDM Engagement Run
Services - Extension")
System will go live earlierst in Oct 2021
Item Type
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Item
Path
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning
sites/z365itenterpriseoperationscenter/eochome/planning/repository/transition/Lists/TransitionPlanning