A.3 Workspaces and Data Management

1. What does it mean to create a new workspace?

   Creating a new workspace in STSA means setting up an isolated environment where you can perform stress testing and scenario analysis without affecting the production data. This workspace includes a sandbox, metadata, and configurations that allow users to experiment with different financial risk models safely.

2. What does it mean to create a new workspace?

   Creating a new workspace in STSA means setting up an isolated environment where you can perform stress testing and scenario analysis without affecting the production data. This workspace includes a sandbox, metadata, and configurations that allow users to experiment with different financial risk models safely.

3. Does it mean I have to create another equivalent to production?

   Not necessarily. While a workspace is based on production data, it is not a full replica of the production environment. You can migrate selected data and metadata to the workspace, ensuring it contains only the necessary components for testing. This process helps maintain efficiency while avoiding the complexities of duplicating everything from production.

4. I have taken a lot of time to set this up and perfect this over the year, so how simple is the new creation going to be?
   Because you have already perfected your setup, creating a new workspace should be relatively simple. You can:

   • Use templates from previous setups to quickly configure a new workspace.
   • Migrate metadata and configurations instead of manually recreating them.
   • Leverage automation features within STSA to speed up the setup process.
5. What is the time taken for me to create a workspace?
   The time required depends on the complexity of your environment, but typically:

   • Basic workspace setup – A few minutes if using templates or cloning from an existing workspace.
   • Data migration and sandbox population – Can take a few hours if large datasets are involved.
   • Custom configurations and validation – Depends on specific requirements but can take additional time.
6. Why can't we handle stress testing and scenario analytics in the production environment itself?
   Running stress tests in production is not recommended because:

   • Performance Impact – Stress testing can consume high computational resources, slowing down production systems.
   • Data Integrity Risks – Scenario shocks and stress tests modify data, which could lead to unintended changes in live production data.
   • Regulatory Compliance – Most financial institutions require a controlled environment for risk simulations separate from live operations.
   • Flexibility for Testing – A sandbox allows multiple iterations of stress tests without impacting real transactions.
7. How do I know if the sandbox is ready for me to perform stress testing?
   You can check the Execution History and Workspace Status in STSA:

   • If the data population status is complete, your sandbox is ready.
   • Ensure that all required models, variables, and portfolios are available in the sandbox.
   • Run a small test scenario to verify that everything is functioning correctly.
8. How easy and how often do I have to sync it up?
   • Ease of Syncing – Syncing is relatively straightforward using automated object migration and sandbox updates in STSA.
   • Frequency of Syncing – The best practice is to sync:
     • Whenever new models or changes are introduced in production
     • Before major stress testing cycles (quarterly or annually)
     • Before regulatory reporting deadlines
9. How do I create a new workspace?

   Navigate to the Workspace Summary page, click Add Workspace, and follow the setup wizard to configure a new workspace.

10. What is a sandbox, and why is it needed?

    A sandbox is a testing environment where users can work with cloned data from production without affecting live operations.

11. How do I migrate production data to a sandbox?

    Use the Object Migration feature to copy production metadata into a sandbox for stress testing.

12. What is the difference between a sandbox and production data?

    The sandbox contains test data and configurations, while the production environment holds live, operational data.

13. Can I create multiple sandboxes for different tests?

    Yes, STSA allows multiple sandboxes to be created for separate testing scenarios.

14. How do I add and manage data in a sandbox?

    Use the Populate Workspace feature to add data from production to your sandbox.

15. What happens if I delete a sandbox?

    All associated data, configurations, and test results will be permanently removed.

16. How do I check the status of data population in a sandbox?

    In the Workspace Summary section, go to Execution History to view the population progress.

17. What types of data can I add to a sandbox?

    You can add dimensions, portfolios, risk models, scenario variables, and financial data.

18. Does the creation of a workspace entail movement of data?
    Yes, creating a workspace involves migrating metadata and selected datasets from production. However, the movement of data depends on your setup:

    • For historical data, you may choose to move large datasets.
    • If only metadata (models, variables, and configurations) is required, data movement can be minimal.
19. How much data is required for us to perform stress testing?
    • Minimum Data – Only key financial metrics, risk factors, and necessary variables are required.
    • Full-Scale Testing – If you're running detailed portfolio-level stress tests, you may need complete transaction-level data.
    • Regulatory Compliance – Depending on compliance requirements, you may need at least several years' worth of data.
20. How and when is data moved into the workspace for stress testing?
    • Data Movement Process:
      1. During workspace creation, select the production datasets to migrate.
      2. The data is copied into the sandbox through the Populate Workspace process.
      3. The system might apply filters and transformations to select relevant data.
    • When Data Moves:
      1. Initially when the workspace is created
      2. Whenever the sandbox is refreshed with updated production data
21. What is the level of user engagement required in this process?
    • Initial Setup – Requires manual selection of data sources and configuration.
    • Data Syncing – Can be scheduled or automated, requiring minimal user intervention.
    • Monitoring – Users should validate that the correct data has been migrated before running tests.
22. Because I have already performed executions in the data in production and may have already used this for reporting, I would like to ensure that the same base data is used for stress testing. How do I ensure that the data in the ST workspace is consistent with the data in production?

    To ensure data consistency:

    • Use the same source tables from production.
    • Enable automated data syncs before each stress test execution.
    • Perform validation checks by comparing sample records from production and ST workspace.
23. Is there a possibility that the data doesn’t match or there will be inconsistencies?

    Yes, possible inconsistencies can occur due to:

    • Timing differences – If production data updates after migration, there may be differences.
    • Partial data movement – If not all relevant tables are copied, results may vary.
    • Incorrect filters applied – Ensure that the filters used during migration match those used in production reporting.
24. How can I ensure that all data required for stress testing is available before commencing the stress test?

    To ensure that all data required for stress testing is available before commencing the stress test:

    • Use the Data Validation Reports in STSA to confirm the presence of all necessary data.
    • Run a sample execution before the full stress test to check for missing data.
    • Compare sandbox data with reference production datasets.
25. How many times does the data move from production to the sandbox?
    • Data movement depends on your setup:
      • Initial migration during workspace creation
      • Periodic updates when syncing with production
      • Before each major stress test cycle, if required
    • Few institutions refresh their sandbox monthly, quarterly, or yearly, depending on regulatory and internal needs.