|
|
| (42 intermediate revisions by 2 users 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 .... ==
| + | |} |
| − | <gallery>
| |
| − | https://wiki.gccollab.ca/images/0/00/HomePage.png|Caption1
| |
| − | </gallery>
| |
| − | === Data management framework and platform ===
| |
| − | It will support data governance and provide tools needed to support the entire data management lifecycle, including data acquisition, cataloguing, transformation, integration, storage and archiving, search and discovery, and collaboration and publishing.
| |
| − | | |
| − | === 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
| |
