Access the self-contained, scalable and secure cloud data analysis service. Find out about costs, features and how to register your interest
The Australian Bureau of Statistics (ABS) developed SEAD to address demand for secure cloud-based data access services across the Australian government. It aims to support government agencies to incorporate the Office of the National Data Commissioner (ONDC) Data Sharing Principles into regular operations, safely manage data sharing and access modern data science tools by leveraging ABS investment and expertise.
The SEAD service is an innovative solution providing a series of secure, self-contained environments known as “SEADpods” within the ABS DataLab’s cloud-based infrastructure. SEADpods operate independently from the DataLab but adhere to the same Safe Settings risk management controls, in line with the Five Safes framework.
The SEAD service enables government agencies engaging this service, referred to as “SEAD partners”, to adopt a SEADpod and inherit exclusive administration of that self-contained environment via self-service features. This allows them to retain full control and management of their data, users, projects and outputs in accordance with their legislative, policy and risk requirements, while the ABS continues to maintain the system's Safe Settings protections.
The SEAD service does not permit SEAD partners to access ABS data held in the DataLab. To enquire about access to ABS data, please see our other data service offerings.
Distinguishing itself from the DataLab which services end-users from government and academic sectors, SEAD is designed for use by individual government departments. SEAD enables areas within departments to service their own end-users who may be internal or external to that department and have contemporary analysis requirements.
SEAD is currently offered to:
The SEAD service can be applied to a variety of use cases. Some of our most common SEAD partner use cases include:
Since its release in June 2022, growing demand and positive feedback from existing SEAD partners demonstrates its position as a valuable addition to the Australian data landscape. Notable mentions of SEAD have occurred in the:
The ABS has extensive experience in keeping data secure as Australia’s national statistical organisation and as an Accredited Data Service Provider (formally Accredited Integrating Authority).
The SEAD system is hosted in Microsoft Azure and meets 'PROTECTED' level security standards as prescribed in the Australian Government Information Security Manual (ISM). It is subject to Independent Security Registered Assessors Program (IRAP) certification, ongoing security audits and robust IT security testing and patching.
The technology underpinning the SEAD system includes:
The ABS employs the above with a focus on industry standard security posture management to provide a safe and secure platform for policy and program delivery work.
For more information about SEAD system security or compliance with IRAP, please Contact us.
The SEAD service enables partners to leverage the existing Safe Settings protections maintained by the ABS.
Responsibility for upholding the remaining Five Safes controls moves to the SEAD partner, with each element in this context as follows:
SEAD partners retain the responsibility for the security of their data within their SEADpod, by managing data ingress and egress within their data governance safeguards. SEAD partners must also ensure that appropriate confidentialisation and treatments are applied to any form of data, code or packages before being made accessible to their users.
SEAD partners oversee user access to their SEADpod, ensuring that only authorised researchers can utilise and interact with their data. SEAD partners are responsible for providing the appropriate people vetting and onboarding processes for access to their SEADpod.
SEAD partners have the autonomy to approve and manage projects within their SEADpod, streamlining their workflow and data analysis. It is the SEAD partner's responsibility to ensure appropriate project governance.
SEAD partners are responsible for ensuring all outputs are validated prior to release from the system against organisational tolerances, to ensure appropriate governance and legal obligations are adhered to (e.g., preventing the re-identification of an individual or organisation).
Note: ABS system administrators hold an overarching administrator role but will not view or interact with SEAD partner data or activities unless requested.
SEAD leverages the underlying systems and resources that support the operation of the DataLab. This ensures that both SEAD and DataLab users have access to the same software and virtual machine offerings outlined below.
SEAD runs on the Windows operating system and is equipped with the following standard tools:
SEAD can also accommodate the following non-standard tools upon request:
All software is licensed, maintained and administered by the ABS through the SEAD service. All data is hosted onshore by Microsoft Azure cloud computing services and accessed through a virtual desktop.
Note: Microsoft Word and Excel are not currently available, as these applications require an internet connection which is not supported in a secure system like SEAD. Libreoffice is the alternative offered in the system, with similar capabilities to Microsoft Office. Firefox and Edge are available to support access for Databricks and Jupyter notebooks to use Python/R. These browsers cannot be used to browse the internet.
| Name | Windows server | CPU | RAM |
|---|---|---|---|
| Small | Small Windows 10 DSVM | CPU Cores 2 | 8GB |
| Medium | Standard Windows 10 DSVM | CPU Cores 2 | 16GB |
| Large | Standard Windows 10 DSVM | CPU Cores 2-8 | 64GB |
| Name | Windows server | CPU | RAM |
|---|---|---|---|
| X-Large | Standard Windows 10 DSVM | CPU Cores 16 | 128GB |
| XX-Large | Standard Windows 10 DSVM | CPU Cores 32 | 256GB |
| XXX-Large | Standard Windows 10 DSVM | CPU Cores 64 | 504GB |
Larger machines than those outlined above are available on request at an additional cost.
As of July 2023, potential SEAD partners can request a quote to adopt a SEADpod based on the following cost recovered components charged up front:
Starting from approximately $65,000 per annum, these charges cover information technology and administration support, system development, maintenance and licensing involved in subscribing to the SEAD service.
These charges will vary based on marginal cost of service levels agreed to in a Memorandum of Understanding (MoU).
Inclusions:
Additional charges apply for customised SEAD services. These services may include additional administrative support, data confidentialisation and output clearance, all in accordance with SEAD partner tolerances and instructions.
Starting from approximately $2,000 per annum, per active Virtual Machine (VM), inclusive of standard software licensing.
An annual cost projection is produced in negotiation with the SEAD partner, based on estimated use. All charges reflect actual data and system usage passed on from Microsoft Azure to the ABS.
Inclusions:
Additional charges apply for non-standard software, such as SAS, Databricks, or other requested software.
Note: The above charges apply to the SEAD service only; costs cannot be transferred or negotiated with the DataLab service. All charges adhere to the ABS user charging policy, exclude GST and may be subject to periodic review. Inactive VM (unused for over 30 days) and administrator accounts will incur minimal maintenance fees.
For criteria, refer to Who can access SEAD.
Potential SEAD partners should ensure that their use case aligns with the SEAD services provided, for more information and a summary on how the ABS handle privacy as part of the SEAD service please refer to the SEAD Privacy Impact Assessment.
To register your interest and an initial consultation, please Contact us to discuss your requirements. We encourage potential SEAD partners to have an initial discussion with the ABS to determine if SEAD is the right service for you.
After an initial consultation, once the ABS receives confirmation to proceed, SEAD partners are requested to complete a system usage and software requirements form which is used to provide a tailored quote.
The MoU drafting and requirement gathering process will continue, and relevant system specification sharing will also commence. The MoU will outline the terms, conditions and responsibilities for both parties, providing a clear framework for the partnership.
Following the completion of a networking specifications form and confirmation to proceed has been received, the ABS will facilitate setup of the partner SEADpod and initiate a complimentary 30-day trial period. Partner organisations will be required to setup Azure Storage Explorer, via their IT department at this point.
The ABS will assist in initial account setup and provide instruction guides and relevant training on how to use the system. The ABS will also present a live demonstration of SEAD administrator functions to address any outstanding knowledge gaps.
Note: ABS does not provide any training for users on conducting analysis or modelling within the system itself.
If the SEAD partner's requirements are met following the completion of the trial, the MoU will be finalised. The SEAD partner service will formally commence upon agreement by both parties, and invoicing is paid.
The ABS will continue to provide ongoing account and system support, licensing and development services as outlined. The SEAD partner takes on the responsibility of administering their SEADpod in accordance with their governance and legislative requirements.
The ABS will provide a service usage report every 6 months to assist the SEAD partner in managing their costs and usage.
The ABS privacy policy and SEAD privacy notice outline how the ABS handles any personal information that you provide to us.
The SEAD Privacy Impact Assessment considers the potential privacy impacts on people whose personal information may be used as part of the SEAD service.
Understand the expected behaviours that govern your access and use of SEAD
SEAD can be administered by the Australian Bureau of Statistics (ABS) or another Australian government organisation engaging the ABS to provide the SEAD service.
By accessing and using SEAD, you agree to abide by the administering organisation's relevant requirements and obligations, including the conditions outlined below. If you cannot abide by these conditions, your use of the system is to cease immediately.
Unless specified, each condition pertains to either organisation administering SEAD.
Remote access within Australia is permitted under the following conditions:
The SEAD privacy notice and SEAD Privacy Impact Assessment outline how the ABS handles any personal information that you provide to us.
The ABS Privacy Policy for Managing and Operating Our Business outlines how we handle personal information that is collected for managing and operating within the ABS.
Understand the functions undertaken by SEAD partner administrators
SEAD offers various roles within the system, each with its distinct set of functionalities as outlined below.
SEAD partner administrators will be provided with an extensive instruction guide, containing all the information provided here as well as additional content.
An overview of administrator roles and hierarchy of access provisioning:
| Role | Associated tasks |
|---|---|
| Pod Owner |
|
| Pod Administrator |
|
| Read-Only Administrator | This is a type of administrator provisioning that enables viewing access to all administrator information (e.g., Cost Summary, Projects, Users) while disabling the ability to access edit functions. |
| Pod User |
|
The administrator portal enables access to various operational objects (Users, Projects, Products etc,) in the SEADpod.
Depending on the level of administrative access given to a person (i.e., Pod Owner, Pod Administrator, Read-Only Administrator), the number of operational objects available will be slightly different.
The Pod Owner portal, immediately below, showcases the maximum number of operational objects available as it is the highest level of administrative provisioning.
| Operational object | Functionality |
|---|---|
| Projects | Shows a list of all projects ever created in the SEADpod. Clicking on a project ID enables adminsitrators to view the information about it in more detail and make various amends, including close, reopen, clone, remove or add users to the project. |
| Virtual Machines | Shows a list of all VMs in the SEADpod, both active and closed, as well as their power state, status, type, who they are assigned to and the name of the project they are associated with. Administrators can make various amends to the VMs, including updating the VM size, type and version. |
| Users | Shows all users ever registered in the SEADpod. From this page, administrators can register new users, as well as evict users, reset their password and MFA, or edit their basic attributes (i.e., name, organisation, contact number). |
| Products | Shows a list of all products available for linking to projects in the SEADpod. |
| Desktop Sessions | Shows all VM desktop session occurring in the SEADpod by detailing the session start and end time, duration, user and the VM name. |
| Packages | Shows all R and Python packages available to users in the SEADpod. |
| Organisations | Shows a list of all organisations created in the SEADpod. From this page, administrators can create new organisations or edit and delete existing organisations. |
| Tags | Tagging allows administrators to create searchable tags and link them to objects from within each object interface (User, Project, Product, Organisation). This page showcases all tags ever created in the SEADpod and the number of objects they are attached to. |
| Banner Messages (Pod Owners only) | From this page, Pod Owners can publish a banner message displays across all user and administrator portals in the partner SEADpod. Banner messages are often used to communicate urgent or important messages and can be amended or published as frequently as necessary. |
| Administrators (Pod Owners only) | Like the Users page, Pod Owners can view all Administrators ever registered in the SEADpod. From this page, Pod Owners can register new Pod and Read-Only Administrators, as well as evict them, reset their password and MFA, or edit their basic attributes. |
| Action Log | The Action Log keeps a real-time record of all administrative and user functions occurring in the SEADpod. |
Users are not able to load code or packages themselves, this responsibility sits with partner administrators and the ABS. To ensure system security and integrity, SEAD partner administrators should refer to their SEAD Administrators Instruction Guide provided by the ABS for information on trusted sources.
In addition, software is not to be provided, or attempted to be loaded to a SEADpod by partner administrators. Any request for new software must be submitted to the ABS, accompanied by a business justification.
For more information, please visit the Contact us page.
To ensure the security of our data and systems, access to our services from overseas locations is only permitted upon request and approval by the ABS.
Access will be considered on a case-by case basis and is limited to endorsed countries.
If you have any questions or require further assistance regarding overseas access, please Contact us.
How to access SEAD, navigate the portal, launch your remote workspace and manage your account
By accessing SEAD, you are confirming you are authorised to do so, and acknowledge you have read and agree to comply with the conditions of use.
SEAD uses multi-factor authentication to provide a secure login environment.
You will need to download the Microsoft Authenticator application to your smart phone from the App Store (for iOS) or Google Play (for Android) to fulfil the login sequence.
Make sure that the authenticator is published by Microsoft, as SEAD only supports Microsoft Authenticator.
The first time you log in, you will be required to enter the username and password provided to you by your SEAD administrator.
Note: all SEAD accounts use the @mydata.abs.gov.au domain format.
The SEAD portal is where you will find information about your SEAD Account, Projects and Virtual Machines (VMs). This interface allows you to self-manage functions of your account, like changing between VMs.
The SEAD portal displays information across three tabs:
From this tab you can activate, start and launch the VM associated with your project.
Use this tab to view your personal contact information and basic account settings.
Keeps a record of your portal actions. This can help you manage your sessions and provides useful information if you encounter problems with the system. It includes:
The left navigator menu contains shortcuts that can be used to navigate between pages. Click the arrow to collapse or expand the navigator menu.
The links at the top right are available from all pages of the portal:
This acts as a global information centre for the DataLab and SEAD, showcasing information about new features and updates.
To access your virtual desktop. You must activate your VM before you can use this shortcut.
Directs you to the SEAD web content.
Directs you to the SEAD privacy notice.
Displays your details, including your name, user name and user role. This is also where you log out of the SEAD portal.
The SEAD conditions of use will help you understand your obligations and management responsibilities to handle microdata safely. It is important that this page is read carefully.
This banner appears at the top of your SEAD portal window when your SEAD administrators have an important message for your consideration or action.
The 'My Projects' page of the SEAD user portal makes it easy to launch and switch between your project VMs.
The Project ID - Your project identifier commonly comprising of a series of numbers and letters.
The Project name - This is your active Project, you can launch the Virtual Machine (VM) straight away.
The "Launch" button - Clicking this button ion your active VM machine will take you straight to the Citrix workspace.
Power state - Click this button to start or stop the VM.
Manage - This button enables you to perform other actions from the detailed view.
Auto-shutdown - This tells you the time of your auto-shutdown.
Scheduled rebuild - Shows the days until your next scheduled rebuild.
Activate - In order to switch between approved Projects, click "Activate". Note: If you try to launch locked VMs from the Citrix Workspace you will receive the error "The requested workstation is in maintenance mode and cannot be used".
Click the ‘Manage’ button on the upper corner of your VM tile to see a detailed management view.
On the VM management page, you will be presented with details about your project, project members and machine.
The VM management page also showcases your VM power state which allows you to start, stop, or restart the VM. This can be helpful if swapping between VMs or having difficulties seeing your machine in the Citrix or Azure Desktop workspace.
You can also view the scheduled shutdown for your VM. VMs are automatically shutdown every night at 10pm AEST. If you have a program running that you expect to run past 10pm, you can choose to extend your session for up to 3 days by selecting 'Bypass shutdown'.
You can also view the date of your next scheduled rebuild. A date and numbered count down is displayed on the coloured bar, with time adjusted to your local area. The coloured bar changes, starting with green, moving to orange and finally red as you get closer to the rebuild date.
VMs are automatically destroyed and rebuilt every 30 days for security and maintenance purposes. You cannot extend this time, however, you can choose to rebuild before the scheduled time by selecting ‘Rebuild Now’. After rebuilding, the countdown resets to 30 days and allows you to bypass the nightly shutdown.
Note: If you try to bypass a shutdown when your machine is scheduled for a rebuild, the system will deny the action and will instead offer to ‘Rebuild Now’.
You can update your desktop version annually as new desktop versions become available. Generally a new VM version is provided once annually, with updated versions of software. Click on 'Change VM Version' to view or update your desktop version.
To compare the software of your current version to the latest version, click on 'Versions'.
The 'My Account' page of the SEAD user portal allows you to view your basic user attributes, such as your name and email address. If your details require updating, contact your SEAD administrator.
From this page you can also self-service account settings related to receiving email reminders. These reminders let you know when your VM will shut down. Notifications are sent at 5pm AEST/AEDT, prior to the 10pm scheduled shut down if you have started your VM that day. It will also remind you before your 30 day VM rebuild. You can change this option at any time by clicking ‘Edit’.
Each project you are a member of will have a separate VM. You can only access one project VM at a time. If your VM is already available to launch, skip to the next step of launching your workspace.
If not, click the ‘Activate’ button on your VM tile and wait until the ‘Launch’ button appears. This may take a few minutes.
Note: If your VM shows a status other than ‘Launch’ or ‘Activate’, it means you must rebuild your VM by navigating to 'Manage'.
If you have a VM for another project that is currently active, this logs you out of your other session. If you have a program running in your workspace using another VM, this will stop the program. You can only run multiple VMs if you have requested to use offline local disk space.
SEAD currently has two different Virtual Desktop Connection options. You can move between versions using instructions in the VM management options section. Citrix Virtual Desktops will be phased out from May 2024.
To launch your SEAD virtual desktop, refer to the relevant system instructions below.
Launch the VM by clicking the ‘Connect’ button on the active VM tile.
Prior to launch, you will be asked to choose the type of connection you wish to utilise from the drop-down menu, as shown in the image below. AVD provides the option to select between a web browser user experience OR downloaded application if required (via the 'Remote Desktop Client').
Note: If you want to use multi-screen functionality, we advise you connect via the 'Remote Desktop Client' for Windows version. This version may also improve connection stability and VM screen resolution.
This image shows three options from the drop-down menu when selecting ‘connect’ to launch your AVD VM. The first option is “Connect (web client)”, the second is “Connect (Remote Desktop Client for Window)”, and the third option is for “Other ways to connect”, which will bring up another menu to show other launch options.
If you are connecting to the 'web client' version of AVD, a new browser page will launch showing the settings screen. This window may have slightly different options for each device. There is no need to change any of these settings. Press ‘Connect’ to continue.
You will then be asked to log into your VM using your SEAD credentials. Once you have entered your credentials, click 'Sign In'.
After a successful login, you will see the below loading screen.
Your VM will then prepare Windows for you.
You should now have access to your VM within a browser window. Click here for more information on using the workspace.
Note: You may see an upload button in the toolbar which, intentionally, does not work. You may encounter a success message after uploading but you will not be able to retrieve any files that you have uploaded. If you wish to upload data or packages to SEAD, please Contact us.
If you are connecting to the 'Remote Desktop Client' version of AVD, ensure that your IT department has enabled the correct networking addresses available here under 'Azure Virtual Desktop configuration'.
Note: If you intend to use the 'Remote Desktop Client' on your organisation's workspace, you will need to contact your internal IT department to make it available to you.
The latest version of 'Remote Desktop Client' for Windows is available here and for Macintosh is available here.
Once you have access and have started the application, click ‘Subscribe’ as shown below.
You will then be shown a new window that allows you to log into your SEAD account using your SEAD credentials
Upon a successful login, you will be shown all your available VMs. If you can’t see the VM that you want, it may be dormant and requires a rebuild.
If you have access to multiple projects you may be shown multiple tabs, one for each project as shown in the image below.
Note: If you wish to use multi-display, right click on your VM icon, click ‘Settings’, and turn off ‘Use default settings’. You should now see options for how you would like to display you VM.
Click into one of the computer icons and you will be taken to a login screen to reconfirm your identity, before access is granted to enter your VM. This may not appear if you have recently logged in, through a similar window.
The below loading bar should briefly appear.
If, instead of the second login prompt, you receive a message as shown in the below image, then either your machine is not the active machine or it is not using the AVD version ‘2024avd’. If your desktop session does not start, repeat Step 1 Activate your VM and check that the version at the bottom of your VM says ‘2024avd’.
You will then be presented with another login screen for the VM itself.
You should then have a new window open on your computer with your VM desktop open.
For more information on using the workspace see Using your workspace.
Launch the VM using the ‘Launch’ button from the active VM tile. This opens your Workspace application after a few moments.
If your VM version uses the Citrix Workspace Application, you will be redirected to the Citrix dashboard where you can view all your recently used desktops. 'Desktop' is the Citrix term for VM.
If your VM version uses Azure Virtual Desktop (AVD), your workspace will open in a new window.
Click the VM/Desktop (this is your project number) to open your project in the SEAD environment.
You will then begin connecting to your SEAD desktop, this may take a few minutes. A notification in the bottom right hand corner of your screen will show you the connection progress. If your desktop session does not start, repeat the above steps to activate your VM.
If your VM operates on the Citrix based version, you will be prompted to open the Citrix Workspace Launcher. If you do not have the Citrix receiver application, you will need to download it to your device. The latest version of Citrix Workspace is available here. You can ignore this step or potentially attempt a workaround, by migrating to the new Azure Virtual Desktop VM version.
If your VM version runs on AVD, your workspace will automatically open in a new window.
At this point you can select the ‘Always allow’ checkbox, if you do not wish to receive this alert each time you launch your workspace.
Log in using the same credentials you used to log into the SEAD Portal. Once logged in, the system may take a few minutes to load as it prepares Windows.
By logging in you agree to these conditions:
Important Notice
If you are not authorised to access this system, exit immediately. Unauthorised users may be subject to criminal and civil penalties.
This is an Australian Government computer system. Part 10.7 of the Criminal Code Act 1995 outlines the penalties that may apply for unlawful use of Government systems including unauthorised access, modification or impairment of computer systems, data or electronic communications. The Act provides penalties of up to 10 years imprisonment for such offences. By proceeding, you are representing yourself as an authorised user and acknowledge you have read and agree to comply with the Responsible Use of ABS Microdata User Guide. Your activity will be logged, monitored and investigated should any misuse be suspected.
Sanctions ranging from a reprimand to revocation of access or termination of employment may be imposed if misuse is determined.
You will then be signed into your project desktop.
You can use your SEAD workspace in a similar way to using other secure networked systems, where you can securely see, use and share data files, analysis and output with the other members of your project team.
Open File Explorer and click on This PC to see the network drives you have access to.
All researchers can see all files in the Library drive. This drive is managed by the ABS and contains support information, such as statistical language documentation, ANZSIC classification and general access guides for non-standard products. Files cannot be saved to this drive.
Any output you want your SEAD administrators to clear should be saved to this drive. Only members of your team can see this drive. Information is backed up nightly and retained for 14 days. Information in this folder remains unaffected by a rebuild.
A shared space for your team to work in and store all their project files, as well as set up and run Python and R scripts. Only members of your team can see this drive. Information is backed up nightly and retained for 14 days. Information in this folder remains unaffected by a rebuild. The default storage is 1TB. You will need to review and delete unnecessary files as your project files grow over time. If necessary, an increase to this storage can be requested via your administrators. There may be a cost for additional storage.
Access data files that have been approved for your project. However, it is best to use the 'My Data Products' shortcut on your desktop as this shows you only the datasets you have been approved to access, rather than all dataset short names. Files cannot be saved to this drive.
If you have been granted local disk space, this can be used to run jobs on offline virtual machines (desktops). You may want to request this option if you have multiple projects that you are actively involved in. There may be a cost associated with attaching local disk space to your VM. The local disk will only be present if it has been allocated to your VM. To request local disk space contact your SEAD administrator.
Can be utilised to run scripts and create new Python package virtual environments, not facilitated through either Jupyter Notebook, JupyterLab or Spyder. Noting the C drive is also destroyed with each 30 day rebuild. Note: Avoid using this drive for saving files - there is limited space and no ability to increase the storage capacity. If more storage is required a local disk can be requested for your VM.
Are not to be used. Information saved here is either destroyed with each nightly shutdown and 30 day rebuild, or has restricted access. Attempting to read or write from Drives A or D will invoke a group policy error due to access controls. In this case please use the C drive or consult your project lead to request local disk space.
Do not store files in any other folders: Other members of your project cannot see files if you store them in other drives. Files stored outside of the Project and Output drives are destroyed every 30 days as part of SEAD security protocols.
Refreshing your network drives: If your network drives do not appear in File Explorer, you can click the 'Refresh Network' shortcut on the desktop. A confirmation message appears when this has been successfully refreshed.
To access the data files for your project, use the 'My Data Products' shortcut on your desktop.
The My Data Products folder displays only the products approved for your project.
Selecting the 'Products' drive shows you the short name of all data loaded to the SEADpod. However, if you try to open a file that is not approved for your project you are denied access and receive an error.
When you walk away from your computer or have finished with your desktop session, you must either lock your workspace or sign out to ensure nobody else accesses your SEAD workspace.
To lock or sign out of your workspace, click the menu button at the top of your window to expand the toolbar, then select 'Ctrl+Alt+Del' to be presented with the options to lock or sign out of your workspace.
If you need to leave your computer for a short time or you have analysis running, lock your workspace. You can then close your virtual desktop window by clicking the X in the top right-hand corner. This closes your session but does not end any programs you have running. Your programs will continue to run until 10pm that night, or longer if you have selected the Bypass option in the portal.
Sign out to leave your workspace session. This closes your session and will end any programs you have running.
If you are using Citrix workspace portal, you may still be logged into the browser. You can either close this window or Log Out of the portal using the icon in the top right corner (with your initial).
If you are an analyst who works across multiple projects, you can request local disk space. This will enable your VM to run jobs offline, noting the 30 day rebuild still applies.
Datasets are stored on a remote file share. Only the active machine has network access to this location. Your locked VMs do not. To run offline jobs, you need to request local disk space via your administrators to be attached to your machine. There may be a cost associated with this.
When running jobs offline, the inactive machine can continue to run your program as it still has access to the data since it is no longer using the remote file share. However, working like this does not allow your project team to see your analysis or output. You should always move your output back to your Project or Output drives where your project team can access and review the output.
To use local disk space:
There are various recommended means for you to access, request or move code, code libraries and packages to your project in order to undertake your analysis in SEAD. You can access code through the following:
If you are working with a specific set of R and/or Python packages, you can now manage these using the Package Manager shortcut on your desktop.
In the Package Manager, click 'Get Started' to navigate to the available packages. You can use this tool to search for packages (in the left column) and install the packages you want to use for your project. If the packages you need are not listed, you can request them using the Contact us page.
The SEAD portal and workspace is presented in a web browser. The latest version of the following web browsers are recommended:
Internet Explorer is not recommended.
Note: Mobile devices are not supported/enabled for SEAD.
If you have forgotten your password, click the 'Forgotten my password' link on the username entry screen.
On the following screen, you will be asked to enter the characters in the picture. You have the option to hear the characters in the picture if you click on the speaker icon (circled). Your user ID is populated for you.
The next screen takes you to Step One of verifying your account. Choose from the options in the left-hand column.
Enter the verification code you received via email, text, or call, then click 'Next' to reset your password.
Enter your new password, ensuring it has a minimum of 8 characters and contains at least three of the following:
The following screen is displayed once your password has been reset. Select the ‘click here’ link to sign in with your new password.
Basic troubleshooting for issues with logging in, virtual machines, errors and running out of space, code and software
There are many different authentication applications, ensure the one you have downloaded is published by Microsoft (not Google or otherwise) as SEAD only supports Microsoft Authenticator.
If you have verified you are utilising the correct application, but you are not receiving prompts to authenticate on your mobile device. You should check your battery optimisation is turned OFF by following these steps (applicable to Android phones only):
You can also try to switch from Wi-Fi to mobile data through your phone, to ensure a good connection to your PC/laptop.
SEAD is enabled by cloud infrastructure, which may be blocked by some organisations’ firewall settings.
ABS cannot make changes to external organisations' infrastructure. Your organisation’s Network/IT Security section will need to review and make changes to authenticate access.
Ensure your organisation has whitelisted the appropriate IP, URL and domain information. If you are using Citrix, ensure you have the latest version of Citrix, click here to view the Citrix Workspace download page.
The temporary password issued to you by your SEAD administrator lasts for 90 days.
If you have forgotten your temporary password, you can self-service a password reset by following these instructions.
Your session will continue to run until a shutdown is required (either nightly shutdown or 30 day rebuild). However, you can still reset your password while your session is running.
Save your work to your Project or Output drives to ensure that your analysis is not lost, this also ensures other team members on your project have access to your work. Information saved outside of these drives is destroyed when your machine is rebuilt every 30 days.
Try logging out of and stopping your VM, then begin the Start VM process again. If that does not work, rebuild your VM by navigating to your VM management options, refresh your session or clear your cache/browser history. If issues persist, contact your SEAD administrator.
System performance issues can occur for many different reasons and every issue requires a unique approach to troubleshoot. Many issues can be resolved by attempting one of the following:
If you cannot see the Library, Project and Output network drives in File Explorer, go to the desktop and double-click the 'Refresh Network Drives' icon.
Stata error example:
"op. sys. refuses to provide memory: Stata's data-storage memory manager has already allocated 77792m bytes and it just attempted to allocate another 32m bytes. The operating system said no. Perhaps you are running another memory-consuming task and the command will work later when the task completes. Perhaps you are on a multiuser system that is especially busy and the command will work later when activity quiets down. Perhaps a system administrator has put a limit on what you can allocate; see help memory. Or perhaps that's all the memory your computer can allocate to Stata. Apart from Stata, only a bunch of files on adobe were open while the append was being run and am not using a multi-user system."
If you encounter the above image, this means you have exceeded the memory for your VM.
If you are receiving an error when attempting to unzip a file using 7zip, this may be because the default is set to ‘7zG’ and not ‘7zFM’. To confirm whether this is the case, attempt the following steps:
Clean up the drive contents, review and delete redundant files to free up space. Additional space can be requested of your organisations SEAD administrators.
Users with SAS installed now have the ability to edit the SAS configuration file located at “C:\Program Files\SASHome\SASFoundation\9.4\nls\en\sasv9.cfg”. This file governs various software settings and parameters, enhancing customisation options. Noting any changes will need to be repeated following machine rebuilds, as the C drive is destroyed on rebuild. To modify the SAS config file, follow these steps:
You can request input clearance for data, code or files to be loaded to your project, from either another project, or other sources that you hold. To do this contact your organisation's SEAD administrators.
You can extend your session to bypass the nightly shutdown, by one, two or three nights.
SAS configuration inside SEAD is tied to the size of your VM. Alternatively, the addition of local disk space (see Running jobs offline using local disk space) can improve run times. Users can also work more on a local disk and then write to the Projects drive when finished, but beware of the costs involved with attaching a local disk space. A 1TB disk can cost between a minimum of $116 to $299 a month depending on usage transactions that would be cost recovered.
Following recent enhancements, PostgreSQL's data directory relocation is now automated to X:\psql\data when a local disk is attached, facilitating expanded storage capacity for data. This feature streamlines the process of accommodating larger datasets. To enable local disc please contact your SEAD administrator.
Use the R Studio Package Manager shortcut on the SEAD virtual machine desktop to check the range of R packages available to you. See Requesting code and packages for more information.
Due to a default setting in Microsoft, the system automatically uses Microsoft Edge to open any PDF file. You can open the PDF file by right-clicking on the file, selecting Open with > Adobe Reader. This launches the file using Adobe Acrobat Reader.
Find answers to common questions about the SEAD service and how it operates
SEADpods are exclusively available to government entities, encompassing federal, state, and local organisations.
SEADpods are designed to be versatile, allowing interactions with various organisations as intended by the SEAD partner. However, certain restrictions may apply based on project specifications and security considerations as specified by the adopting agency.
Yes, projects can be linked to only the products defined by the administrator, subsequently enabling access to data by a select group of users. Much like the model seen in the shared infrastructure of the DataLab. Noting, administrators however do have access to all data loaded to the environment.
No, there is no limit to how long a SEADpod can exist. The SEADpod will remain in use by the SEAD partner until an explicit termination date is provided.
Users are not able to load code or packages themselves, this responsibility sits with partner data administrators and the ABS. To ensure system security and integrity, SEAD partner administrators should refer to their SEAD Administrators Instruction Guide provided by the ABS for information on trusted sources. In addition, software is not to be provided, or attempted to be loaded to a SEADpod by partner administrators. Any request for new software must be submitted to the ABS, accompanied by a business justification.
Project and Output folders within each workspace are backed up every night and retained for 14 days. These backup snapshots are accessible to SEAD administrators.
Closed projects will also be archived after 180 days since their closed date. Data from P: (Project) and O: (Output) file shares will be moved from the Project storage account to a dedicated archive storage account. The ability to restore a project will no longer be available after the 180 days grace period and requests to restore an archived project will incur a cost.
Data input and output is managed through Azure Storage Explorer by uploading and downloading files from Azure Files Storage Accounts. Azure Storage Accounts are configured with a firewall to restrict access to an administrator's nominated network.
SEAD facilitates collaborative engagement on shared projects. SEAD partner administrators have the capability to create user accounts and strategically assign them to specific projects. It is up to the SEAD partner to determine and manage data access policies.
There are alternative options available, but this is up to the SEAD partner to manage. The choice depends on specific project requirements.
VMs are the virtual workspaces analysts use to undertake their work in SEAD. An analyst will have one VM for each project they are a member of and can only work in one of these (the ‘Active’ VM) at any given time. This is a security measure to prevent analysts from accessing data for multiple projects simultaneously. The VMs are also called ‘Desktops’ if you are using Citrix Workspace or Azure Virtual Desktop. Only SEAD administrators can increase/decrease or assign VMs to users.
The appropriate VM size will depend on the size, complexity, and needs of the analysts working on a given project. Larger and more complex files and analytical tasks may require larger machines. We advise users to use small, medium or large machines in the first instances. There are cost implications on VM use. See Available features for more information about VM sizes and performance. Users have the ability to manage their VMs power state in SEAD.
Yes, VM GPU units are available at an additional cost.
VM Project and Output drives are backed up every night and kept for 14 days. Files outside of these drives are not recoverable.
Yes, it takes about 5 minutes to process the connection. You also need to log out of your VM to allow the system to refresh your session with the new data.
VMs are destroyed approximately every 30 days for security purposes. If the 30 day timing will interfere with the timing of your project, you can choose to destroy and rebuild earlier than 30 days at a time that suits you.
Yes, users are reminded about a rebuild three days ahead of their rebuild and again 24 hours prior.
No, there is no predetermined limit to the amount of data that can be stored in a SEADpod. By design, SEAD is a scalable environment. However, by default each project workspace is provisioned 1TB, which can be increased by administrators to 10TB of storage. Additional storage can be provided upon request to the ABS, to a maximum of 100TB per project imposed by the Azure platform. Cost management should be considered when thinking about storage applications.
Yes, system usage charges will vary depending on the forecasted usage profile, including, but not limited to, storage, number of accounts, license use and VM use.
Like DataLab, SEAD is already equipped with various software for SEAD partners to utilise at no additional cost, including R, Python, STATA, Winmerge, QGIS, and 7ZIP (for the full list of software, see Available features). However, new software or software that requires paid licensing will incur additional charges. For example, Databricks is available but will incur a cost. Other non-standard software tooling can be requested by SEAD partners for implementation in the system, and will be considered on a case by case basis.
Yes, SEAD administrators have the ability to assign/move SAS licenses as required due to our concurrent SAS license pool arrangement. This means that if you pay for 20 concurrent licenses, the system will limit your users if over 20 try to use a SAS enabled machine at the same time. Since the licenses are pooled, up to 30, 40 or 50 users in your SEADpod can be assigned a SAS enabled machine at any given time, they just cannot be accessed concurrently. SEAD administrators can monitor this by exporting reports from the Virtual Machines page on the SEAD portal.
Yes, once confirmation to proceed with the SEAD service is provided, we can facilitate a free 30-day trial period. See Applying for the SEAD service for further information about the application process.
Register your interest or general enquiries and support for existing SEAD partners
To register interest or general enquiries in adopting a new SEAD environment:
To: sead.support@abs.gov.au
Subject: New SEAD environment query
Dear SEAD team,
I have reviewed the eligibility criteria on the website, and would like to enquire about setting up a new SEAD environment for my organisation or department.
Key contact name and details:
Organisation:
Project Title:
Brief use case:
For existing SEAD partners to report technical issues or request general system support:
✉ Existing SEAD partner system support request
To: sead.support@abs.gov.au
Subject: Existing SEAD partner system support request
Dear SEAD team,
I would like to report a system issue, or request general system support for either users or administrators of the SEADpod I work in.
For existing SEAD partners to request code, code packages or software be implemented in the system:
✉ Existing SEAD partner code or software request
To: sead.support@abs.gov.au
Subject: Existing SEAD partner code or software request
Dear SEAD team,
I would like to request a code/code package, or software be added to the SEADpod I work in.
If you are a researcher using an existing SEADpod and want to enquire about data access, account resets, input or output clearance, training or general enquiries, please contact your organisation's SEAD administrators.
For all other enquiries, please contact the ABS via email at sead.support@abs.gov.au. This email account is monitored and we will respond to your query during standard business hours (AEST), Monday to Friday.