# 2026-02-03

- Adner style preference: avoid dashes in prose (e.g., do not write "Hi Jennifer - hope you are well."). Use commas/periods instead. Keep this in mind for future drafting.

- Blue Prism RPA POC (BINC) context captured:
  - IT lead: Adner. Hosting/infrastructure: Arvato Systems GmbH. RPA vendor: Arvato Connect.
  - POC scope is non production only: 1 Blue Prism app server, 1 SQL server, 2 desktops (robot runtime + control/monitor), UI automation only, no API integrations, no direct DB access to business systems, fictitious users, MFA required, auth can be native BP or AD.
  - No separate dev/test/prod environments.
  - Desktop constraints: VDI not feasible. W365 discussed but deemed unsupported due to Entra ID and SCCM changes; Dominik: Blue Prism not supported on Entra ID managed devices; SCCM being dismantled.
  - Only remaining desktop option discussed: self-hosted clients with compliance responsibility on customer.
  - Critical clarification: self-hosted does not necessarily mean unmanaged or non domain joined.
  - Proposed acceptable model to confirm: BINC-owned physical endpoints, joined to BGROUP domain, managed/updated by Arvato Systems (similar to BincBluestar). Vendor accesses via controlled technical accounts.
  - Status: feasibility mode. No infra provisioned. Awaiting written response from Dominik on endpoint model.
  - Comms style: concise, direct, factual; no over-thanking; avoid dashes/bullet characters in emails; written confirmation preferred; avoid implying readiness to build; governance/feasibility first.