1 | CSIRO ASKAP Science Data Archive (CASDA) – Stage 0 Project Intent Statement Confirm the necessary requirements, use cases, workflows, business processes, architecture and designs of CASDA to enable valid estimation and progression into Stage 1 build. Overview The CSIRO Australian Square Kilometre Array (ASKAP) project requires a Science Data Archive to store, manage, and make available for discovery & access the data that is generated by ASKAP operations. CSIRO ASKAP is, in many ways, a data driven facility where the data rates are extremely high. The data rates arriving at the Pawsey Centre, ASKAP’s key processing facility, are approximately 2.5 Gigabytes (GB) per second, equivalent to 75 Petabytes (PB) per year. This is beyond the current ability to archive data and so the majority will be processed in quasi real time with only a sub-set to be archived. The total volume of archive data is expected to reach 5 PB per year. Given the scale of data that is in context in this project, new uncertainties will exist beyond those applicable to a standard data management project. Explicit time upfront to work through these uncertainties will support a more considered framework/approach during system construction. Having a clear plan and architecture are key to enabling agile delivery in this particular context. Stage 0 described here is focused on requirements, use cases, workflows, business processes architecture and design of the forthcoming CASDA system. What are the project target outcomes? Increased understanding of the CASDA requirements, use cases and workflows; Increased understanding of the overall architecture that will support and guide development of CASDA ; Increased understanding of the high level designs of key system components, operations business processes, and user support services of CASDA.. What are the project deliverables? v1.0 Requirements and use-case specification; v1.0 Workflow/activity model specification; v1.0 System architecture + design description; DRAFT CASDA standard operating procedures specification; DRAFT CASDA support service model specification; Who is involved? David Toll: CSIRO Chief Information Officer, Project Co-sponsor Douglas Bock: CASS Assistant Director, Project Co-sponsor CASS Project Review Board: Chaired by Phil Crosby Jessica Chapman: CASS Data Management Leader, Project Leader Ian Heywood: CASS Project Scientist Euan Sangster: IM&T Exec. Manager, Primary Supplier-Software Angus Vickery: IM&T Exec. Manager, Primary Supplier-Infrastructure IM&T Software & Infrastructure Services: Provision of technical team members for production of deliverables User Reference Group: Champions and early adopters of CASDA selected to have scientific expertise using astronomy data archives ASKAP Program: Key input in terms of ASKAP science & operations CASS Software and Computing Group: Responsible for delivery of all ASKAP related software including telescope operations, data processing and data management iVEC: Integration partner, provision of ASKAP computing facilities and associated data archive infrastructure ICRAR: Sharing of knowledge between MWA and ASKAP data archive groups. What is the approach? This stage of the CASDA program will follow a Kanban approach to the production of project deliverables. Output scope has been established and the team will work towards delivery in priority order. Milestones and review points will be set along the way to gauge progress, review risks and issues and to demonstrate the key information and knowledge gained. When will the project be carried out? Start: August 2013; Estimated End: Early What technologies and expertise will be used? Key members of CASS and ASKAP in particular will provide critical knowledge in regards to requirements and integration of CASDA into the broader ASKAP program; Elicitation and verification of requirements, uses cases, workflows and business processes will be led by the project analysis team; Consultation will be undertaken with ASKAP Survey Science Teams, Guest Science Projects and members of the general astronomy community to gather requirements and define usage scenarios; Architecture and design of the proposed CASDA system will be undertaken by key members of the project technical team; Consultation with leading external architecture specialists will be undertaken to validate and support proposed solutions; Members of ICRAR will be approached to share knowledge in relation to the experiences managing data for the MWA project; Members of iVEC will guide on integration with the Pawsey Centre; Broader input will be sought across CSIRO to identify suggestions and ideas that could contribute to the overall solution; Formal review of final project outputs will be carried out by IM&T and the CASS Project Review Board. v3 15/10/2013, Dan Miller