| Status | WIP |
|---|---|
| Stakeholders | |
| Outcome | |
| Due Date | |
| Owner | |
| Solution/Domain/Data Architect |
Background
In the new ACD Labs Harmonization strategy, tbd
ACD Labs offers an opportunity to assess a license for deploying the solution in the cloud, where new features capabilities would be also available.
Today there are several deployments across sites globally in the company.
Goals: Rationalization of apps, centralize ACD Lab deployments...
Laboratory Architecture - Building Blocks
NMR workflow & application context
WiP
Questions/Concerns
- Cloud provider strategy:
- China/Shanghai: In case of Azure being the best fit as cloud provider for this deployment, Shanghai site can be also covered by leveraging Azure 21Vianet local partner.
Scenarios/Use Case
- Instrument-application dependency on Windows 10 OS
- Instrument-application dependency on Linux OS and Synology storage (instead Local File Server)
- Large file generation to manage for specific purposes: immediate usage, long term storage, complex analytics at scale, global NMR database
Technical and Functional Assumptions
Sensitivity Points
Risks
Non Risks
Architectural Approaches
Target Architecture
Trade-offs (alternatives)
Alternative 1 - ACD Lab
Alternative 2 -
Alternative 3 -
TBD
Data Synchronizer Architecture - LabPC to the Cloud
- Evaluation Matrix
| Architectural Approach | |||||
|---|---|---|---|---|---|
| 1 | Alternative/Evaluation Vector | Alternative 1 - | Alternative 2 - | Alternative 3 - | |
| 2 | Technical Debts | Paid | |||
| Added | |||||
| 3 | Major Work Block | ||||
| 4 | Performance | ||||
| 5 | Scalability | ||||
| 6 | Consistency | ||||
| 7 | Deployability | ||||
| 8 | Interoperability | ||||
| 9 | Resource - Cost Efficiency | ||||


