1. DCS Alternate Data Distribution System (DADDS) Database Development Status Presentation to the STIWG/TWG July 9, 2008

2. Introduction The DCS Alternate Data Distribution System (DADDS) was initially developed to disseminate DCS message data directly from the DAMS-NT DADDS is designed to act as emergency DAPS backup for DOMSAT and NWSTG data streams DADDS has been used operationally in place of DAPS and is available for backup DADDS forms the first incremental component to replace DAPS

3. Architecture

4. Availability DADDS includes redundant hardware with automatic failover switching capability The architecture design has dual processing paths for immediate re-routing of data Provides high-availability hardware configuration with rapid recovery in event of equipment failure –Hot-swappable hardware with redundant components and power supplies –Parallel blade servers/disks and SAN disk array –SQL server high-availability DBMS features

5. Operation DADDS uses daily PDT/UDT compressed files exported from DAPS as the database source The DADDS concept allowed users to update records via web application in event DAPS unavailable for extended period NOAA conducted Technical Interchange Meetings with Operators, Managers and Major Users to identify database requirements To replace DAPS, DADDS enhanced to support user web interfaces and legacy batch functions

6. Objectives Maintain all database records essential to operation and maintenance of DCS Provide database management software to fulfill real-time message handling requirements Incorporate general functionality of the present DAPS fields, records, tables, and databases Allow expansion/modification of the current fields, records, tables and databases Support web interface to allow user access for updates, queries, searches, reports and utilities

7. Requirements User login and authentication Access level and user privileges User agency affiliation with individual accounts Web database application and user interface Incorporate DAPS tables and records Update and expand database records and fields Support legacy database batch updates Message data access and retrieval Replication, redundancy and robustness System management and control

8. Authentication User application and registration process Account authorization and privilege level Password management functions –Emailing initial password instructions and changing passwords –Password expiration and warnings –Reminders and forgotten password features Current NOAA password policy and rules may apply –Minimum of twelve characters with at least one capital letter, one lower case letter, one special character and no characters repeated more than twice –Passwords expire every sixty days and cannot be re-used for two years –No names or words found in the dictionary

9. Access Browser-based GUI for Login with common look and feel for all user classes Secure access control for registered users NOAA password rules enforcement for user access to Government system Database controls for selective user access to authorized records

10. Schedule DBMS RequirementsApr – Jun 2008 Redundant HW/SANJul – Aug 2008 NSOF AcceptanceAug – Sep 2008 Web ApplicationJul – Dec 2008 DBMS DevelopmentJul – Jan 2009 DBMS AcceptanceFeb – Mar 2009