Difference between revisions of "TADAP"

From wiki
Jump to navigation Jump to search
 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
== '''Target Architecture for Data and Application Platform (TADAP)''' ==
+
== '''This page was deleted as TADAP has changed to EDH''' ==
 
+
{| class="wikitable"
== What is TADAP ==
 
=== TADAP is a Data management framework and platform ===
 
It will support data governance and provide tools needed to support the entire data management life cycle, including data acquisition, cataloging, transformation, integration, storage and archiving, search and discovery, and collaboration and publishing. The outcome of TADAP is the DFO Data Management Platform.
 
 
 
=== Application framework and platform  ===
 
It will support the deployment of applications built using commonly used frameworks based primarily on Java and .NET (i.e. MODIP, EFMSI). Support will also be provided for LAMP (Linux, Apache, MySQL, PHP) and Python. The platform will be designed to isolate data assets from computing, making data assets more secure and shareable by multiple applications.
 
 
 
=== Corresponding infrastructure in the Cloud ===
 
DFO will be able to meet the current and anticipated computing needs of the department in a reliable, timely, efficient, and cost-effective manner. The capabilities will exist to scale up or down depending on needs and will be able to accommodate DFO’s data storage and computing needs.
 
 
 
== Why TADAP  ==
 
===== Internal to DFO =====
 
* DFO’s legacy of silo applications and fragmented data makes information not discoverable; difficult to find quality information
 
* SSC challenges and limitations in setting up the DFO required end-state data centres
 
* Need to change culture around data governance and stewardship (additional parallel project)
 
* Meet demand of OPP, Internet of things, continuous increase needs of acquired data volume
 
 
 
===== External to DFO =====
 
* Demand of new capabilities for Big Data, Artificial Intelligence, Digital Government, Collaboration
 
* New opportunity – new delivery options in the Cloud
 
* New momentum from TBS for GC data strategy and governance
 
 
 
== Stakeholders ==
 
'''This is an initial list.'''
 
 
 
'''Please feel free to contact us if you think there's room for improvements.'''
 
{| class="wikitable mw-collapsible"
 
|+
 
|'''Sector'''
 
|'''Contact Person'''
 
|'''Project / Program'''
 
|'''Meeting date'''
 
|'''Relation to TADAP'''
 
|'''Other Comments'''
 
|-
 
|Conservation and Protection
 
|Lise Melanson
 
|Department  Violation System (DVS)
 
|Augut 24th,  2018
 
|These projects  have to be supported by TADAP
 
|We  are contacting  André Bélanger to get  more info about data sources
 
|-
 
|
 
|Pauline Lalonde
 
|C-STAT
 
|September 25th, 2018
 
|This project has to be supported by TADAP
 
|
 
|-
 
|Canada Coast Guard
 
|Shawn Legault  and Nicholas O’Hara
 
|SIPA
 
|September 11th,  2018
 
|CCG has its own  opertional network. However, we need to at least catalouge their data
 
|
 
|-
 
|
 
|Jean-François Coutu
 
|INNAV
 
|September 24th, 2018
 
|CCG has its own opertional network. However, we need to at  least catalouge their data
 
|
 
|-
 
|
 
|Chris  Burnie-Gardiner and Patrick Marion
 
|SISAR
 
|September 13th,  2018
 
|CCG has its own  opertional network. However, we need to at least catalouge their data
 
|The  goal of this meeting was to explore how AI can be applied in Search and  rescue. However, we may at least want to catalouge their SISAR database
 
|-
 
|
 
|Bert Paulin
 
|Reporting for CCG programs
 
|To be determined
 
|Further discussion required
 
|
 
|-
 
|Canadian Hydrographic Services
 
|Terry Fanning  and Matthew McGowan
 
|Main work is to  move science, ocean, and species data to the Government of Canada Open Portal
 
|August 27th,  2018
 
|This program  needs to be supported by TADAP
 
|George  is contacting David Bradley, new manager of science data sub-committee, to  arrange for future meetings
 
|-
 
|
 
|Claude Guay
 
|Metadata management and data management for whole science  sector
 
|To be determined
 
|
 
|
 
|-
 
|SRS, Science Branch
 
|Theraesa Coyle  and Johannie Duhaime
 
|Aquaculture  Monitoring Program
 
|August 27th and  September 4th, 2018
 
|This program  needs to be supported by TADAP
 
|
 
 
|-
 
|-
|Stock Assessment and Research Division, Science Branch
 
|[http://www.geds.gc.ca/en/GEDS?pgid=015&dn=cn%3DPatten%5C%2C+Bruce%2Cou%3DFAD-FAD%2Cou%3DSTAR-STAR%2COU%3DSCI-SCI%2COU%3DRDG-DGR%2COU%3DREGPAC-REGPAC%2COU%3DDM-SM%2COU%3DDFO-MPO%2CO%3DGC%2CC%3DCA Bruce Patten]
 
|Scientific survey documentation for fish population  assessment, fish harvest tracking and reporting
 
|August 31st, 2018
 
|Stakeholders are very interested in collaboration. Their  programs need to be supported by TADAP
 
 
|
 
|
|-
 
|Ocean Science Division, Science Branch
 
|Di Wan
 
|Scientific oceanographic survey documentation for Pacific and Arctic
 
|August 31st, 2018
 
|Stakeholders are very interested in collaboration. Their  programs need to be supported by TADAP
 
|
 
|-
 
|Aquaculture Management Directorate, Aquatic  Ecosystems Sector
 
|Tyree Lush and  Arsenault Shane
 
|Canadian  Shellfish Sanitation Program (CSSP) mapping system
 
|September 7th,  2018
 
|This program  needs to be supported by TADAP
 
|
 
|-
 
|Fisheries  & Licence Policy / Fisheries and Harbour Management
 
|Mark Ledwell
 
|FHM
 
|To be determined.
 
|Further discussion required
 
|
 
|-
 
|Ecosystems and Fisheries Management: System  Integration
 
|Aaron Gillis  and Andrew Frost
 
|EFM-SI
 
|To be  determined
 
|This program  has to be supported by TADAP
 
|
 
|-
 
|Information  Management and Policy Strategies
 
|Lyn Warner
 
|Open Data Portal
 
|To be determined
 
|Has to be supported by TADAP
 
|
 
|-
 
|Ocean Data and Information Section
 
|Tobias Spears
 
|To be  determined
 
|To be  determined
 
|
 
|
 
|}
 
 
== Architecture ==
 
<gallery>
 
File:TADAP Architecture.png|TADAP Logical Architecture
 
File:TADAP ConceptArchitecture.png|TADAP Conceptual Architecture
 
File:TADAP HighLevelArchitect.png|TADAP High Level Architecture
 
</gallery>
 
 
== The Prototype ==
 
The roadmap for TADAP: DFO Data Management Platform starts with the idea of TADAP, a Proof of Concept (using one COTS tool), prototype, Pilot and the going to Production.<br>
 
 
A '''Proof''' of Concept is a small exercise to test a design of the TADAP idea . The primary objective is to prove that a solution is viable.<br>
 
 
A '''prototype''' simulates the relevant part of Data Management Platform. While a POC shows that a functionality can be done, a prototype explains how it will be done. A prototype may provide some re-usable components that can be re-used in a pilot or even in production.<br>
 
 
 
The  '''pilot'''  is a subset of the whole audience.  A pilot will help us getting a better understanding of how the product will be used across DFO. This will be our Minimum Viable Product (MVP).<br>
 
 
 
[[File:PoCPrototypeProd.png|center|frameless|600x600px]]
 
 
== Team ==
 
Please feel free to contact us to discuss the project and how you can participate
 
{| class="wikitable"
 
|'''Name'''
 
|-
 
|George  Esper
 
|-
 
|Jane Moore
 
|-
 
|Ian Allen
 
|-
 
|Bill Yuan
 
|-
 
|Jimmy Novak
 
|-
 
|Riham  Elhabyan
 
|-
 
|Benedict Okudolo
 
|-
 
|Yask  Shelat
 
|-
 
|Marc Pollett
 
|-
 
|John Bao
 
|-
 
|Abdul  K Hamdo
 
  
 
|}
 
|}

Latest revision as of 06:28, 5 February 2024

This page was deleted as TADAP has changed to EDH