Personal resource organisation
The virtual desktop provides a user-level starting point for files, folders, links, applications and CoSpace shortcuts.
THE ARCHITECTURE
A connected experience.
A considered foundation.
Understand the relationship between the user environment, collaborative services, CCOS and the infrastructure underneath.
CONNECTED AT EVERY LAYER
Explore the foundation.
Layer by layer.
Separate the model, rotate the view and select a layer to understand its part in the collaborative environment.
THE PLATFORM IN PERSPECTIVE
Drag to explore ↔Environment · Personal desktops and CoSpaces connect people around shared work.
Conceptual architecture model. Rotate and select a layer to explore.
A LAYERED VIEW
Everything has its place.
A conceptual view of the Picowork architecture, from the hosting foundation to the shared workspace.
04COLLABORATIVE ENVIRONMENTPeople & CoSpaces
Personal desktops, group spaces and invited collaboration.
03CONNECTED SERVICESCommunication & content
Messaging, shared files and supported collaborative applications.
02PLATFORMCCOS
A common software foundation for the collaborative environment.
01INFRASTRUCTUREYour hosting environment
Existing servers, data centres or suitable cloud infrastructure.
THE RESOURCE MODEL
Bring the useful things together.
Shared work context
A CoSpace groups participants and relevant resources around a purpose. It provides a common context for communication and content.
Application participation
The architecture incorporates third-party web resources. Each application may carry its own identity, access and integration constraints.
CROSS-CLOUD COLLABORATION
Separate environments.
A shared purpose.
The cross-cloud model connects participants from different environments through an invitation and a shared CoSpace. It is a way to think beyond a single organisational boundary.
Understand the access modelENVIRONMENT AYour organisation
People · Resources · Control
ENVIRONMENT BCollaborating organisation
People · Resources · Control
Architecture review matters.
For any cross-environment deployment, confirm authentication, network reachability, content transfer, storage location and the permissions enforced on both sides. A conceptual connection is not a substitute for an agreed data flow.
INTEGRATION IN PRACTICE
Start with the resource. Define the connection.
| Resource | What to establish | What to validate |
|---|---|---|
| Web application | Access URL, ownership and intended workflow | Authentication, embedding restrictions and session behaviour |
| Existing business system | Business owner and interface available | Network access, permissions and supported integration method |
| Shared document | Owner, format and permitted actions | Viewer or editor compatibility and synchronisation |
| External content | Source, audience and permitted use | Availability, provider access requirements and content rights |
| Cross-cloud workspace | Participating environments and responsibilities | Invitation flow, identity, storage and revocation |
DESIGN CONSIDERATIONS
The questions behind a dependable environment.
Identity and access+
Define who can authenticate, how identities map to roles and how external participants are approved. Determine the identity capabilities supported by the selected configuration rather than assuming a specific enterprise identity integration.
Storage and information lifecycle+
Identify where each resource resides, whether copies are created and who is responsible for retention, backup, recovery and deletion. Local storage is a deployment decision with corresponding operational responsibilities.
Application isolation+
The product design describes sandboxed web applications. Review the isolation boundary and supported behaviour for the deployment, including the limits imposed by browsers and the external application.
Capacity and resilience+
Plan for expected users, concurrent sessions, content volume and network conditions. Capacity, failover and recovery need workload-specific validation; historic stress-test figures should not be treated as a current service commitment.
YOUR NEXT CHAPTER
Make space for better work.
Start with the people, resources and infrastructure you already have. Build a clearer picture of what collaboration could become.
Build your collaboration brief