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.

Status-quo

Target Architecture

Questions/Concerns

1. Cloud provider strategy: 
2. 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

Workload: tbd

Technical and Functional Assumptions

Sensitivity Points

Risks

Non Risks

Architectural Approaches

Trade-offs (alternatives)

Alternative 1 - ACD Lab Fetches files from LabPC disks to prepare and make reports available in the Cloud

In this solution ACD Lab remotely reaches LabPC discs so to fetch files captured from instruments.

For that, the set of LabPCs part of the site/technique must have a folder shared for external access with a minimum access control by granting only LabPC service account for read-only mode. 

Since this is such a Pull-data pattern, the intelligence to for scheduling, source mapping (LabPCs), new/old data tracking and authorization relies on the ACD Lab.

Alternative 2 - ACD Lab Fetches files from Local File Servers storage to prepare and make reports available in the Cloud

This solutions sticks to the regular data flow from LabPC to the Local File Server in the site, where Peer-sync observes files captured from instruments materialized in the LabPC discs and immediately promotes them to the Local File Server.

For that, ACD Labs points to Local File Server as the only source in a site for fetching files from a given technique.

Since this is such a Pull-data pattern, the intelligence to for scheduling, source mapping (Local File Server), new/old data tracking and authorization relies on the ACD Lab.

Alternative 3 - ACD Lab Fetches files from cloud storage to prepare and make reports available in the Cloud

TBD

Data Synchronizer Architecture - LabPC to the Cloud

• Evaluation Matrix

Conclusion

References

Meeting Notes