SaaS Data Mirroring Across Isolated Accounts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Construction management SaaS applications face inefficiencies in collaboration and data sharing between parties due to the isolation of accounts in multi-tenant architecture, leading to access issues and inability to record confidential information across connected parties.
Innovation Solution
Implementing a 'Connections' tool that allows parties to connect their accounts, enabling data records to be mirrored across connected accounts, with separate instances in each account and propagation of updates, while allowing access to shared data even after disconnection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If accounts are isolated in multi-tenant architecture, then data security and privacy are improved, but collaboration efficiency and data sharing capability deteriorate
Solution Approach 1:
The patent segments data access rights by creating connections between accounts, allowing selective sharing of data records while maintaining account isolation. Each connection defines specific access permissions between accounts, enabling controlled collaboration without compromising overall security.
Solution Approach 2:
The system introduces connections as intermediaries between isolated accounts, mediating data sharing while preserving account boundaries. Connections act as controlled channels that allow specific data to flow between accounts under defined permission rules.
2Reliability
If data records are stored only under individual accounts, then data privacy is improved, but access to shared information and collaboration capability deteriorate
Solution Approach 1:
The patent adds a new dimension to data storage by creating mirrored copies of data records in connected accounts. Instead of storing data in a single location, the system creates multiple accessible copies across connected accounts, enabling shared access while maintaining privacy through controlled mirroring.
Solution Approach 2:
The system creates copies of data records in connected accounts, allowing parties to access shared information without copying physical documents. The mirroring mechanism creates virtual copies that can be accessed by connected accounts while the original remains in the source account.
3Device complexity
If accounts remain disconnected, then system simplicity is maintained, but ability to share information and collaborate deteriorates
Solution Approach 1:
The connection system is dynamic, allowing accounts to be connected or disconnected based on collaboration needs. Connections can be established when information sharing is required and terminated when collaboration ends, providing flexibility without permanent complexity.
Solution Approach 2:
The system performs preliminary actions by automatically mirroring data records when connections are established, so that information is ready for access before needed. The system proactively sets up data availability in connected accounts rather than requiring manual data transfer.
4Manufacturing precision
If RFIs are answered manually and reviewed by general contractors, then accuracy of information can be maintained, but time consumption and inefficiency increase
Solution Approach 1:
The system implements feedback mechanisms where RFIs and related information are automatically propagated between connected accounts. This enables faster response cycles where information flows bidirectionally between parties, reducing the time needed for manual review and response while maintaining accuracy through structured data exchange.
Data Source
AI summary
Disclosed herein is software technology that enables different accounts to be mirrored. In one aspect, the disclosed process may involve determining that an origin data record created under a first account of a first party is to be mirrored to a second account of a second party, generating a thread identification that is mapped to the data record created under the first account of the first party, and generating a first message that comprises data from the origin data record and the thread identifier that is mapped to the origin data record. Based on the first message, the disclosed process may further involve creating a target data record under a second account of a second party that corresponds to the origin data record created under the first account of the first party and storing the target data record under the second account of the second party.