DCS AUTOMATED PROCESSING SYSTEM DAPS II

1
DCS AUTOMATED PROCESSING SYSTEM (DAPS) II

• KAY METCALF
• NOAA GOES DCS PROGRAM MANAGER
• DECEMBER 13,2001

2
BACKGROUND

• DAPS OPERATIONAL AT NESDIS SINCE 1989
• RUNNING ON DATA GENERAL COMPUTERS
• WRITTEN IN FORTRAN
• USES A COMMAND LINE INTERFACE
• USES A DG SPECIFIC DATA BASE MANAGEMENT SYSTEM
  (DBMS)
• RESULT
• NOT USER FRIENDLY
• NOT RELIABLE DUE TO AGING EQUIPMENT
• NO SUPPORT DUE TO LACK OF EXPERTISE IN
  HARDWARE/SOFTWARE

3
REPLACEMENT SCHEDULE

• CONTRACT AWARD SEPTEMBER 2000
• PLANNING AND DESIGN DURING 2001
• EXPECTED DELIVERY JULY 2002
• OPERATIONAL DECEMBER 2002
• PARALLEL TESTING FOR 6 MONTHS

4
USER FUNCTIONS

• Online Application for System Use Agreement
• Tracking of System Use Agreement Approval
• Online User Registration by Individual User
• Online Trouble Reports and Tracking
• Automated Address Generation and Channel/Time
  Slot selector (subject to NESDIS approval)
• Tracking of all User Requests
• Database Updates

5
USER FUNCTIONS(cont)

• Email Notification of Error Reports
• Online Mandatory Verification of Contact
  Information
• Online Query and Reports (predefined or ad hoc)
• Dissemination
• Web Interface
• FTP
• DCS Data Service (Client/Server dedicated
  delivery)
• Dial-In
• DOMSAT
• NWSTG

6
OPERATIONAL FUNCTIONS

• Centralized System Configuration Management and
  Control
• Real-Time Performance Monitoring
• Automated Failover to Backup
• Status Display of all System Components
• Channel Blocking
• Dissemination to User Interfaces
• Channel Testing and Test Transmitter Control
• Data Dissemination Blocking

7
FEATURES

• COMPLETE SYSTEM REDUNDANCY
• NO SINGLE POINT OF FAILURE
• 500 CONCURRENT USERS
• USER FRIENDLY
• GRAPHICAL USER INTERFACE (GUI)
• PULL DOWN MENUS WHENEVER POSSIBLE
• INTEGRATED FUNCTIONS FOR USERS AND OPERATORS
• SCRIPTING CAPABILITY FOR BATCH FILES
• OPEN MODULAR ARCHITECTURE
• EASILY UPGRADED/EXPANDED
• OFFICE AND SYSTEM AUTOMATION
• DATA AND USER VALIDATION

8
USER CONCERNS

• Database Transition
• Existing Records must be ported into new system
• Records need to be complete (PDTs)
• New fields need to be populated
• Training
• NESDIS will provide training
• Parallel Testing
• Keeping 2 dissimilar databases synchronized
• Which users will use which systems