Weather, Air Quality, and Climate Study

1. Air Quality, Climate, and Weather Study Brief M. Adamovic, R. Cooney, C. McLinden, R. Nassar, R. Wu June 15, 2015 Protected B PROTECTED B Page 1G. Séguin, Présentation au Président, 8 Jan., 2008

2. Summary • Scope and Objectives for a Study on a Weather (TBC), Air Quality, and Climate mission are presented to ensure all aspects of the activity have been properly discussed with the team and the client. • Next step is to prepare SOW and initiate procurement activities.

3. Context • Environment Canada (Air Quality Research Division and Climate Research Division) has requested the development of a mission concept that would build from past work for the Weather, Climate and Air quality (WCA) instrument suite under the Polar Highly Elliptical Orbit Science (PHEOS) program. • WCA was considered a secondary science payload on PCW and is currently not baselined for the PCW mission. EC has requested a study to explore the possibility of moving the WCA instruments away from PCW to a standalone small satellite(s). • The mission would monitor weather (TBC), air pollutants (e.g. CO, NO2, SO2,O3, HNO3 and others) and GHG (CO2 and CH4) from space over Canada and the Arctic regions with a focus on the troposphere. • The mission concept goals fall under several priority areas of the EC science strategy 2014-2019

4. Scope • Review the PHEOS-WCA user requirements to focus on EC needs • Industry to revisit the instrument and mission design to fill the user needs. • Trade study to determine viable mission concept(s). • Develop viable mission concept(s) and respective development plans based on Canadian capacity. • Prepare the Initiator Business Case. • If work is successful next steps would be: – Prepare Technology Development Request for STDP – Initiate a Phase 0;

5. Needs • Environment Canada needs to update the WCA instrument concept proposed as a secondary payload on PCW to support a standalone mission providing Weather (TBC), Climate and Air Quality data over the Arctic.

6. Proposed Activities EC. CSA/contract support • Define Mission Objective (Athabasca oil sands, arctic-boreal, revisit?) • Collect, review, clarify, and validate the User Requirements. • Prepare User Requirements for contract input. • Review User Requirements • Review current data sources and identify relevant gaps. • Identify options to provide the data; • Examine collaborative options (International partnership, PPP) • Perform initial trade off to determine viable options; • Prepare Initiator Business Case • Translate Mission Objectives and User Requirements into preliminary instrument requirements (FOV, spectral bands, spectral resolution, etc.) and mission requirements where appropriate. • Develop payload concept • Develop mission concept(s) for viable option(s). • Assess feasibility/performance/budgets and cost of option(s) • Identify critical technology elements for inclusion into technology roadmaps. Contract, EC/CSA Support CSA. EC/contract support Contract

7. Points for Consideration • Weather? • Approach to collect and validate the requirements (EC lead the preliminary User Requirements based on PHEOS input). Timeline? • Interest in a threshold/goal approach? • Preference on consultation with Users/EC? Regular TIMs? • Mechanisms/interest to contact and involve academia in User team? • Is there a template for an “initiator business case” or “investment proposal” (i.e. phase 0 gate)? Need this to feed contract activities in the SoW. • Develop single preferred concept or all viable concepts? Do we need to cap the number of viable concepts to be developed? • RFP • One RFP for one contract + option • Budget: 500k + 100k option (TBC) • Managed by CSA contract, no need for PWGSC • Duration • 5 months in 15\16 + 7 months in 16\17(TBC)

8. Preliminary Options • Preliminary options that will be minimally included in the option analysis: • Hosted payload on commercial or international satellites • Hosted payload on a Canadian mission (PCW) • Purchase data from commercial source(s) • Orbit: • HEO, LEO, MEO • Stand alone Canadian small-satellite • Constellation of Canadian small-satellites • On a high level each option must be assessed for: • feasibility to meet User Requirements (threshold/goal) • cost • Retained option(s) will be further developed: • mission concepts • performance assessment • feasibility • cost Protected B

9. Timeline • Preparation of SoW: July 2015 • Documents to contract officer: Aug 1, 2015 • Posting of RFP: Sept 1, 2015 • Proposal Evaluation: Sept 24, 2015 • Contract negotiation: Oct 1, 2015 • Contracts Start: Nov 1, 2015 • Contracts End: Oct 31, 2016 • 1st User Meeting : • Initial List of Reqt., needed for RFP? • etc. Protected B

10. Study Team • CSA • Ryan Cooney , Marko Adamovic • EC • Ray Nassar, Rosa Wu, Chris McLinden • Academia • (?) Protected B

11. Consultation Process • Many studies involve a ‘consultation’ process. Make sure that you capture how this will be done.

12. Deliverables • Instrument and Mission Requirements Document • Options Analysis Report • Mission Conceptual Design Document Protected B

13. Work Description • Identify and list in bullet forms your main tasks. State what you want at the end and do not spend time explaining how you would like it to be done. • See a couple of examples in the background section. • Make sure to discuss with the client especially if there are work packages under their responsibility. Protected B

14. Notes • Capture here small items you may want to clarify (in needed) • Possibility of a follow up work or option could be put here. Protected B

15. The last slide! • Use your judgement if you deem you need to add (or delete) slides to define your study. • The aim of the Study Brief is to provide a light-weight low-maintenance tool to capture the main elements of your activity before spending time is SOWs, MOUs, consultation, etc. • Do not transform it in a paper mill… Protected B

16. Back-Up Slides Protected B

17. Phase Definitions Extracted from CSA's Systems Engineering Technical Reviews Standard Protected B

18. Definitions (for SOW) • Operational System • System delivering data to support ongoing operations of a Canadian department. Data availability is guaranteed. • Proto-Operational Mission • Shorter term, lower cost Mission to prepare for an Operational System. Mission and satellite are of shorter duration, operational system not fully developed. • Microsatellite • Small platform having a mass less than 150 kg, which can support a short duration mission. Meet specifications of MMSMB. • Small Satellite • Small platform having a mass less than 1000 kg, which can support missions of medium lifetime (<7 years). Protected B

19. Work Description (example 1) • Collecting User Requirements • CSA will prepare a list of current applications • CSA and GLO will prepare a list of OGDs to be contacted. • Questionnaire will be sent to OGDs via GLO. • Info will be collected and consolidated by Technical Authorities. • Rest of the process for validating and refining the requirements will be performed with the contractor(s). Protected B

20. Work Description (example 2) • Review Requirements • Review inputs provided by users. • Assess how much is covered by existing or planned missions. • Clarify assumptions and obtain more detailed specifications from users where needed. • Establish initial list of system capabilities (payload and ground segment) to satisfy the needs expressed by users. • Hold one Users Teams Meeting to provide the feedback. • Finalize initial list of requirements. Protected B

21. Work Description (example 3) • Options Analysis • Group requirements in domain areas for which groups of users with common interests can be formed. • Identify user priorities within each group. • Identify high-level satellites requirements for one or several satellites to satisfy the requirements for each group. • Formulate high-level concepts for payloads to meet the requirements for each group, with a possibility of meeting the requirement of more than one group. • Perform high-level Complexity/Benefit Analysis to rank payload options. • Present options to Users/Groups (TBC) • Work with users to select prefered option(s) in each group. Protected B

22. Work Description (example 4) • Mission Concepts • For each priority payload identified by the users, prepare a list of mission, system and payload specifications to meet the requirements. • Consider possibility of meeting requirements for different groups and combining requirements for EO and SatCom with a reduced number of missions. • Prepare preliminary Mission Conceptual Design documents to describe the proposed concepts. • Identify required developments for short and long term. • Present the concepts. • Identify Bus capacity if different from MMMSB. Protected B