Master/Slave Mode allows Systemwide subscribers to share calculations and employee data across multiple devices in real-time. This is perfect for union boards, pension committees, and negotiation teams working together.
Important Requirements:
- All users must sign in using the same account
- The account must be a Systemwide level account
- The first user to log in automatically becomes the master device
- Other users can request to become the master (requires current master approval)
- Each user should click on the badge and set a nickname so it's known who is requesting when interacting
How It Works
- Master Device: The first device to log in becomes the master device. The master device can perform calculations and share them with all slave devices.
- Slave Devices: Additional devices that log in become slave devices. They receive notifications when the master shares calculations or employee data.
- User Identification: Each user should click on their badge/device indicator and set a nickname. This helps identify who is making requests and interacting in the system.
- Employee Data Sharing: When the master device uploads a CSV file, it's automatically shared with all slave devices. This ensures all devices have access to the same employee data.
- Calculation Sharing: When the master performs a calculation, it's automatically shared with all slave devices. Slaves receive a notification and can choose to accept and auto-calculate, or dismiss.
Master Device Features
- Perform calculations normally
- Upload employee CSV files (automatically shared with slaves)
- Calculations are automatically shared with all slave devices
- See count of connected slave devices
Slave Device Features
- Receive notifications when master shares calculations
- Accept shared calculations to auto-populate and calculate
- Dismiss shared calculations if not needed
- Automatically receive employee data when master uploads files
- Request to become master (requires current master approval)
Data Security
Employee data shared between devices is stored temporarily in the database and is automatically deleted when the last slave device logs out. This ensures sensitive information is not permanently stored.
Master Transfer
If a slave device needs to become the master, it can request master control. The current master device will receive a notification showing the requesting user's nickname (if set) and can accept or deny the request. This allows for flexible collaboration while maintaining control. Remember to set your nickname by clicking on your badge so the master knows who is making the request.
Use Cases: Negotiations and Collaborative Work
Master/Slave Mode is particularly powerful for pension plan negotiations, allowing negotiation teams to work collaboratively and efficiently during critical discussions.
Negotiation Workflow
During pension negotiations, the master/slave mode enables a streamlined workflow:
- Master Device Setup: The lead negotiator or actuary logs in first using the Systemwide account, becoming the master device. They upload the employee CSV file with all relevant data.
- Slave Device Connection: Team members (union representatives, committee members, advisors) log in on their devices using the same Systemwide account, automatically becoming slave devices. Each member should set their nickname by clicking on their badge.
- Real-Time Data Sharing: When the master uploads or updates employee data, all slave devices automatically receive the updated information. This ensures everyone is working with the same data set.
- Scenario Testing: The master device can quickly test different pension scenarios (changing multipliers, COLA settings, retirement ages, etc.) and share calculations instantly with all team members.
- Collaborative Analysis: Slave devices receive notifications of new calculations, allowing team members to review scenarios in real-time during negotiations.
Benefits for Negotiations
- Rapid Scenario Modeling: Test multiple pension plan configurations quickly without waiting for expensive actuarial calculations
- Synchronized Team: All team members see the same calculations and data simultaneously, ensuring everyone is on the same page
- Strategic Planning: Quickly identify the most advantageous pension configurations to present to actuaries for formal analysis
- Cost Efficiency: Avoid costly and time-consuming traditional actuarial calculations for initial scenario testing
- Real-Time Collaboration: Team members can review and discuss calculations as they're generated, even during active negotiations
- Data Consistency: Eliminates confusion from different team members working with different data sets or outdated information
Best Practices
- Designate a Master: Choose one person (typically the lead negotiator or actuary) to be the master device for the duration of negotiations
- Set Nicknames: Each team member should click on their badge and set a nickname immediately after logging in. This helps identify who is making requests and interacting during negotiations
- Pre-Negotiation Setup: Upload and verify employee data before negotiations begin to ensure accuracy
- Test Scenarios in Advance: Run various pension configurations before negotiations to identify optimal options
- Keep Devices Connected: Ensure all team members remain logged in during negotiations to receive real-time updates
- Use Calculation Sharing: When the master tests a new scenario, share it immediately so all team members can review it
- Document Key Scenarios: Save or note the most promising calculations for formal actuarial review
Typical Negotiation Scenario
During a pension negotiation session:
- Master device uploads the complete employee roster via CSV
- All slave devices automatically receive the employee data
- Master tests a pension proposal (e.g., 2.5% multiplier, 7% COLA every 5 years)
- Calculation is automatically shared with all slave devices
- Team members review the results on their devices
- If adjustments are needed, master modifies parameters and shares new calculations
- Process repeats until optimal configuration is identified
- Final numbers are provided to actuaries for formal analysis
Note: This tool provides rapid scenario modeling and estimation. Final pension plan changes should always be verified through formal actuarial analysis before implementation.