DSAS REPLACEMENT STEP 1 CRITICAL DESIGN REVIEW 81004

DS/AS REPLACEMENT STEP 1 CRITICAL DESIGN REVIEW 8/10/04 Tim Hopkins NWS SYSTEMS ENGINEERING CENTER

Deirdre Jones l Opening Remarks 2

Objectives l Critical Design Review for Step 1 l Preliminary Design Review for entire plan l Will follow up with PDR and CDR for Step 2, etc. - Each Design Review will include an overview of entire plan with progress and milestones. l 30 -50 field sites deployed per Step 2, by Feb. 15, 2005 l Schedule accelerated at direction of Corporate Board, to enhance system performance b/4 next severe weather season. 3

Team Organization and Responsibilities l Tim Hopkins (OST 31) – Project Lead l Chuck Piercy (OST 11) – Program Management and Budget l Walter Scott (OST 11) – COTR l Dave Holloran (NGIT) – Project Manager l Leigh Dominy (NGIT) – Project Engineer l Franz Zichy/Karthik Srinivasan (OST 31/OPS 12) – Maintenance and Logistics l Mary Buckingham (OPS 24) – Operational Assessment Test Director l Carl Mc. Calla/Ed Mandell (OST 31) – Software Development and Integration Coordinator 4

Chuck Piercy l Program Management and Budget 5

AWIPS System Architecture AWIPS GOES Firewall NEXRAD Terrestrial and Satellite Communications Systems ASOS Buoys, River Gauges, Lightning, etc. Workstations Retrieval, Processing & Storage Servers Workstations Network Control Facility Workstations LAN NCEP Weather Models 6

Legacy Architecture WAN NEXRAD RPG HP DS HP AS 100 Mbps FDDI HP WS SIMPACT PLAINTREE SWITCH HP-RT CP ROUTER 10 Mbps Ethernet LINUX WS LDAD Server FIREWALL 10 Mbps Ethernet Total Processing Capacity: Approx. 900 MFLOPS 7

Linux Phase I Architecture NEXRAD RPG HP DS HP AS HP WS SIMPACT Phase I Enhancements LINUX CP 100 Mbps FDDI PLAINTREE SWITCH LINUX PX LINUX WS WAN ROUTER LDAD Server 100 10/1000 Mbps Ethernet Switch FIREWALL 10 Mbps Ethernet Total Processing Capacity: Approx. 3750 MFLOPS 8

Linux Phase II Target Architecture WAN LINUX CLUSTER(s) ROUTER LINUX WS LINUX CP LINUX PX AS REPLACEMENT LDAD SERVER DB SERVER LDAD FW NEXRAD RPG Ethernet 1000/10 Mbps SWITCH “Local Apps” Server CLUSTER WFO/RFC Archive AHPS NEXRAD Equip RPG SBN IP Multicast Total Processing Capacity: Approx. 16, 000+ MFLOPS 9

Expected WFO/RFC Hardware Architecture ~July ’ 05 WAN AWIPS WAN LINUX LX Router Network Attached Storage (NAS) LINUX XT Linux CP Linux AX Nexrad RPG Ethernet 1000/10 Mbps SWITCH Serial MUX Plaintree Switch LINUX PX 1 LINUX SX 1 LINUX DX 2 RFC REP LDAD Firewall PV 100 Mbps FDDI LDAD SERVER Legend DS 1 HP-UX 10. 2 DS 2 HP-UX 10. 2 < 1 yr old 1 -2 yr old 2 -3 yr old 3+ yr old 10

Operational Concept l Same operational concept, with enhanced computing resources additional storage space and centralized, shared mass storage using Network Attached Storage device. 11

DS/AS Replacement Roadmap l Leigh Dominy (NGIT) 12

Overview l An analysis of technology and development of a “to-be” architecture was initially briefed to the AWIPS Systems Engineering Team (SET) on 2/3/04. l To-be architecture provides the framework to complete individual product improvement tasks while maintaining a common goal. X-terminals Redundant LDAD firewalls DS/AS replacement Redundant LDAD servers Serial mux upgrade Full DVB deployment l To-be architecture facilitates development of a roadmap for schedule, budget and deployment planning. l Roadmap assists in issue and dependency identification and resource planning for risk reduction. 13

AWIPS To-Be Architecture l Hardware - Utilize Network Attached Storage (NAS) technology - Deploy commodity servers on Gb. E LAN - Incrementally deployed and activated - Promote reuse of select hardware - Remove limitations of direct attached storage l Software - For availability, move from COTS solution to use of public domain utilities • Some experience with NCF and REP • Can be decoupled from operating system upgrades • Supports NAS environments • Can be augmented for load balancing if required - Deploy low cost Linux database engine 14

AWIPS To-Be Architecture l Methodology - Stage hardware, move software when ready - Reuse hardware to ease transition and allow planned decommissioning - Deploy flexible availability framework l Goals - Decommission AS, Advanced. Server, DS and FDDI - Support universal deployment of single Linux distribution (currently RHE 3. 0 with OB 6) - Provide dedicated resource for local applications - Expandable within framework (easy to add servers) - Deploy to subset of sites prior to February 2005 15

Step 1 – Initial Hardware Deployment l Release OB 4 is a prerequisite l Initial staging of hardware - New rack - NAS w/LTO-2 tape (~400 GB storage and backup) - 2 commodity servers – DX 1/DX 2 - 2 Gb. E switches and associated cables, etc - 2 8 -port serial mux replacements (installed in PX 1/2) l NAS key to incremental deployment and activation l Serial mux replacements installed but not activated l LTO-2 drive for site backup l New hardware and PX 1/PX 2 on Gb. E LAN l LDAD firewall upgrade deployed independently 16

Step 1 and Release OB 4 Hardware Architecture WAN AWIPS WAN Router LINUX LX Network Attached Storage (NAS) LINUX XT Linux AX Linux CP Nexrad RPG Ethernet 1000/10 Mbps SWITCH plaintree Serial MUX 100 Mbps FDDI PX 1 PX 2 DX 1 DX 2 LDAD Firewall PV DS 1 DS 2 AS 1 AS 2 LS 1 Mass. Storage Benefits • Solves Active/Active PX problem • DS Mass Storage and Auto. Loader can be decommissioned Light Blue or Clear boxes indicates new hardware component Issues • Will plaintree swtch handle nfs traffic from DS/AS to NAS? • Does site have footprint for another rack before any old ones are decommissioned? • What is the file structure of the NAS? • Do most decoders use internal storage for temp files? 7/30/04 • What kind of NCF monitoring will be available for the NAS? 17

Step 1 and Release OB 4 Software and Data Architecture WAN DS 1 • Decoders • Radar Processing • Dial Radar • wfo. API • RMRserver • Radar Server • Radar Text Decoder • WWA Processes • Database Engine • Tex. DB read/write • OH cron/apps • Shef decoder • MTA/MHS processes • LDAD server • LDAD routers • Listener • Local ldad applications • NWWS Product • LAMP DS 2 • Netmetrix • Trap Interceptor (ITO) AS 1 • asynch. Scheduler • Decoders • Metar • Synioptic • RAMOS • Redbook • Radar. Storage • DNS • NIS • NTP • Jet. Admin • SNMP Agent • NWWS Scheduler • Notification. Server • Dam. Cat(OH) AS 2 • LAPS NAS PX 1 • Data Storage • Site Backup PX 2 LINUX DX 1 • DNS Phase I LINUX DX 2 • DNS Phase I PV • IFP • GFE • Decoders • Satellite • Grib • Bin. Lightinig • Maritime • Profiler • Web Server • Safe. Seas • Comms. Router • FFMP/SCAN • MSAS • Decoders • Buf. Mos. Decoder • Warn. DB • Std. DB • Collective • Raob • Aircraft • ACARS • Bufr Drivers • text. Notificationserver Bold Underlined text indicates newly ported or moved processes or data Light Blue or Clear boxes indicate new hardware component Processes and/or data are listed underneath corresponding hardware component 7/30/04 18

Step 1 - Incremental Activation l Activate NAS - Point DS to NAS • Allows DS 1/DS 2 to be used as active/active pair using existing MC/Service. Guard infrastructure • Decommission DS mass storage and autoloader - Point PX 1/PX 2 to NAS • Maintain active/active pair • Deliver new availability mechanism • De-activate cluster management portion of AS 2. 1 • Power. Vault (PV) deactivated for near-term l Connect PX 1/PX 2 to Gb. E LAN and install PCI-X cards as future AS serial mux replacement once APS port is complete l Most data to the NAS, temporary files continue to be written to local disk l Planning early October OAT to verify DS 1/DS 2 and PX 1/PX 2 failover and NAS data availability l Require a full deployment decision in mid-October to complete deployment of initial 64 sites by 1 Feb 05 19

Step 1 - Considerations l Current plan is to move data from DS mass storage and PX Power. Vault to NAS - Limited to 2 GB tar files - Some sites will need to clean up px 1 data and px 2 data prior to NAS installation l Rack placement at WFOs - Early sites will have “extra” rack longer than sites deployed later in 2005 20

Step 2 - Decommission AS 1/AS 2 l Release OB 4 maintenance release (OB 4. X) of stable OB 5 software required for AS decommissioning l Activate DX 1/DX 2 - Infrastructure/decoders move to DX 1 - IFP/GFE to DX 2 - Newly ported functionality to DX 1 l Reuse PX 1 and PX 2 as PX 1 and SX 1 - PX 1 for applications/processes using processed data - SX 1 for Web Server, local applications and eventually LDAD - Activate serial mux replacement and ported APS l Non-ported software from AS 1 to DS 2 l DX 1/DX 2 deployed with RH 7. 2 as risk reduction 21

Step 2 and OB 4. AS/OB 5 (w/RH 7. 2) Hardware Architecture WAN AWIPS WAN Router LINUX LX Network Attached Storage (NAS) LINUX XT Linux AX Linux CP Nexrad RPG Ethernet 1000/10 Mbps SWITCH plaintree Serial MUX 100 Mbps FDDI DS 1 DS 2 PX 1 SX 1 PV Benefits • Could stop maintenance on AS’s • Could eliminate 1 rack of equipment • Could decommission FDDI at this point if 100 MB boards were cheaper than maintenance. • Start migration of MHS Light Blue or Clear boxes indicates new hardware component DX 1 LDAD Firewall DX 2 LS 1 Issues • Start running X. 400 and SMTP in parallel. • Should PX and SX be retrofitted with extra disks? 7/30/04 22

Step 2 and OB 4. AS/OB 5 (w/RH 7. 2) Software and Data Architecture WAN DS 1 DS 2 • Radar Processing • Dial Radar • wfo. API • RMRserver • Radar Server • WWA Processes • Database Engine • Tex. DB read/write • OH cron/apps • Shef decoder • MTA/MHS processes • LDAD server • LDAD routers • Listener • Local ldad applications • NWWS Product • LAMP • Decoders • Metar • Synoptic • RAMOS • Netmetrix • Trap Interceptor (ITO) DX 1 • Decoders • Bin. Lightning • Satellite • Grib • Maritime • Warn. DB • Std. DB • Collective • Buf. Most. Decoder • Raob • Aircraft • ACARS • Profiler • Redbook • Radar. Storage • Radar. Msg. Handler • Radar. Text. Decoder • Handle. Generic • Bufr Drivers • Comms. Router • DNS • NIS • NTP • Jet. Admin replacement • SNMP Agent • SMTP MTA/MHS • Xyplex hosting DX 2 • IFPServer • GFE NAS PX 1 • Data Storage • Site Backup SX 1 PV • FFMP/SCAN • Safe. Seas • LAPS • MSAS • Text • Web Server • router. Store. Netcdf** notificationserver • asynch. Scheduler • NWWS Scheduler • Notification server • Dam. Crest(OH)** *Serial MUX is an AS Decommissioning dependency **Requires prototype testing Light Blue or Clear boxes indicate new hardware component Processes and/or data are listed underneath corresponding hardware component 7/30/04 Bold Italicized text indicates moved processes Bold and underline indicates newly ported processes 23

Step 2 - Incremental Activation l Failover scheme - DX 1 to DX 2 - DX 2 to DX 1 - PX 1 applications and servers to DX 2 - PX 1 processes APS and NWWSProduct to SX 1 (require PCI-X card access) - SX 1 baseline software to PX 1 l Decommission AS 1/AS 2 and excess rack l Linux SMTP MTA deployed as start of migration from x. 400 (required for DS decommission) l Provide sites with some level of performance improvement as early as software readiness allows 24

Step 3 – Deploy Data Base and OS l Deploy Linux Postgre. SQL data base engine to DX 1 - Move existing PV to new rack and connect to DX 1/2 - Reconfigure PV (possibly into 2 separate direct attached disk farms, one for each DX) - Database availability via mirrored or replicated databases is TBD at this time - May be accelerated to OB 5 for fxatext database l Migrate ported databases l Upgrade operating system (currently RHE 3. 0) on all applicable hosts LX/XT CP (if full DVB deployment complete) DX PX/SX AX RP (RFCs only) 25

Step 3 and OB 6 (w/RHE 3. 0) Hardware Architecture WAN AWIPS WAN Router LINUX LX Network Attached Storage (NAS) LINUX XT Linux AX Linux CP Nexrad RPG Ethernet 1000/10 Mbps SWITCH plaintree Serial MUX 100 Mbps FDDI DS 1 PX 1 SX 1 DS 2 Benefits • Start Migration of Databases Light Blue or Clear boxes indicates new hardware component DX 1 PV LDAD Firewall DX 2 PV LS 1 Issues • When will apps be ready to use Postgre. SQL? • Data reliability with Postgre. SQL • Will there be issues with running Informix and Postgre. SQL in parallel? • What is the performance of Postgre. SQL? 7/30/04 26

WAN DS 1 Step 3 and OB 6 (w/RHE 3. 0) Software and Data Architecture DS 2 DX 1 DX 2 NAS PX 1 SX 1 • Postgre. SQL • Radar Processing • Dial Radar • wfo. API • RMRserver • Radar Server • WWA Processes • Informix Database Engine • LDAD server • LDAD routers • Listener • Local ldad applications • NWWS Product • Decoders • Metar • Synoptic • RAMOS • Netmetrix • Trap Interceptor (ITO) • IFPServer Database Engine • GFE • FFMP/SCAN • Data Storage • OH cron/apps PV PV • Safe. Seas • Site Backup • Shef decoder • LAPS • Text. DB read/write • Postgre. SQL Database • MSAS • Decoders • Text • Bin. Lightning notificationserver • Satellite • asynch. Scheduler • Grib • NWWS Scheduler • Maritime • Notification server • Warn. DB • Dam. Crest(OH)** • Std. DB • LAMP • Collective • Buf. Most. Decoder • Raob • Aircraft • ACARS • Profiler • Redbook • Radar. Storage • Radar. Msg. Handler • Radar. Text. Decoder • Handle. Generic • Bufr Drivers • Comms. Router • DNS • NIS • NTP • Jet. Admin Bold and underline indicates newly ported processes replacement • SNMP Agent Light Blue or Clear boxes indicate new hardware component • SMTP MTA/MHS • Xyplex hosting Processes and/or data are listed underneath corresponding hardware • MHS Processes • Web Server • router. Store. Netcdf** • ldad. Mon 7/30/04 component 27

Step 3 – Incremental Activation l l Decommission AS 2. 1 and HP Informix engine can remain on DS for site use Transition to SMTP and decommission x. 400 Consideration - Can/should Postgre. SQL be delivered early to RH 7. 2 DXs? - Most sites run software against GFS databases, not their own databases. - Database and software will be tested with RHE 3 only as part of OB 6. - If databases delivered early how/when does parallel ingest get developed and tested? - Should RFCs be handled differently? 28

Step 4 – Deploy LDAD Upgrade l Deploy LS 1 and LS 2 - Deploy redundant server pair (requirements still tbd) - Could reuse PX 1/SX 1 as LS 1/LS 2 and use new generation hardware for PX 1/SX 1 l Activate LS 1/LS 2 - Migrate internal LDAD processing to SX 1 - Some internal and external LDAD processing must transition at same time l Reuse existing HP LS on internal LAN - Existing 10/100 MB LAN card 29

Step 4 and OBx Hardware Architecture WAN AWIPS WAN Router LINUX LX Network Attached Storage (NAS) LINUX XT Linux CP Linux AX Nexrad RPG Ethernet 1000/10 Mbps SWITCH plaintree Serial MUX 100 Mbps FDDI DS 1 PX 1 LS 1 SX 1 DS 2 Benefits • Move old LS 1 to internal LAN PV DX 2 PV LDAD Firewall LSx 1 Issues • Transition from LS to LSx needs to consider how/when local ldad apps will be done. • Do we run old LS and new LSx in parallel while sites convert their local software? • Int/Ext Ldad software must be ready to transition at the same time. • Could reuse PX 1 and SX 1 for LSx 1/2 and buy higher end machines for PX 1 and SX 1 Light Blue or Clear boxes indicates new hardware component 7/30/04 30

WAN DS 1 Step 4 and OBx Software and Data Architecture DS 2 DX 1 DX 2 NAS PX 1 SX 1 LSx 1 • Postgre. SQL • Radar Processing • Dial Radar • wfo. API • RMRserver • Radar Server • WWA Processes • NWWS Product • Decoders • Metar • Synoptic • RAMOS • Netmetrix • Trap Interceptor (ITO) • IFPServer Database Engine • GFE • FFMP/SCAN • Data Storage • Web Server • LDAD • OH cron/apps PV PV • Safe. Seas • Site Backup • router. Store. Netcdf** Server • Shef decoder • LAPS • ldad. Mon Applications • Text. DB read/write • Postgre. SQL Database • MSAS • LDAD Server • Decoders • Text • LDAD routers • Bin. Lightning notificationserver • Listener • Satellite • asynch. Scheduler • Local ldad applications • Grib • NWWS Scheduler • Maritime • Notification server • Warn. DB • LAMP • Std. DB • Dam. Crest(OH)** • Collective • Buf. Most. Decoder • Raob • Aircraft • ACARS • Profiler • Redbook • Radar. Storage • Radar. Msg. Handler • Radar. Text. Decoder • Handle. Generic • Bufr Drivers • Comms. Router • DNS • NIS • NTP • SNMP Agent Bold and underline indicates newly ported processes • SMTP MTA/MHS 7/30/04 • MHS Processes Light Blue or Clear boxes indicate new hardware component • Jet. Admin replacement Processes and/or data are listed underneath corresponding hardware component • Xyplex hosting 31

Step 5 – Decommission DS 1/DS 2 l Continue to move ported software/databases to Linux servers - Combine with step 6 if additional DXs are required - DX 1 for database server and infrastructure - DX 2 for IFP/GFE - DXn for decoders l All Linux devices on Gb. E LAN l Remaining functionality on LS on 100 MB LAN - Dial. Radar/wfo. API (tied to FAA/Do. D requirements) may be OBE at this point. If so, Simpacts and LS can be decommissioned at all non-hub sites. - Netmetrix (required at hub sites only) 32

Step 5 and OBx Hardware Architecture WAN AWIPS WAN LINUX LX Router LINUX XT Network Attached Storage (NAS) Linux AX Linux CP Nexrad RPG Ethernet 1000/10 Mbps SWITCH Serial MUX LS 1 PX 1 SX 1 Not Upgraded • Printers • Xyplex • Modems • VIR’s • Simpacts Benefits • FDDI and DS decommissioned. • Reuse of LS for SW that isn’t proted yet. (non-redundant) • Rack consolidation DX 1 DX 2 PV PV LDAD Firewall DX 3 (optional) LSx 1 Issues • Dialup and wfo. API may still be needed on an HP-UX machine • Netmetrix at HUB sites needs to be on HP-UX Light Blue or Clear boxes indicates new hardware component 7/30/04 33

WAN LS 1 Step 5 and OBx Software and Data Architecture DX 3 (optional) DX 1 DX 2 NAS PX 1 SX 1 LSx 1 • Postgre. SQL • Dial. Radar • Netmetrix • IFPServer Database Engine • GFE • FFMP/SCAN • Data Storage • Web Server • LDAD • OH cron/apps PV PV • Safe. Seas • Site Backup • router. Store. Netcdf** Server • Shef decoder • Trap Interceptor (ITO) • LAPS • ldad. Mon Applications • Text. DB read/write • Postgre. SQL Database • MSAS • LDAD Server • Decoders • Text • LDAD routers • Bin. Lightning notificationserver • Listener • Satellite • asynch. Scheduler • Local ldad applications • Grib • NWWS Scheduler • Decoders • Maritime • Notification server • Metar • Warn. DB • LAMP • Synoptic • Std. DB • Dam. Crest(OH)** • RAMOS • Collective • Buf. Most. Decoder • Radar Processing • Raob • wfo. API • Aircraft • RMRserver • ACARS • Radar Server • Profiler • WWA Processes • Redbook • NWWS Product • Radar. Storage • Radar. Msg. Handler • Radar. Text. Decoder • Handle. Generic • Bufr Drivers • Comms. Router • DNS • NIS • NTP • SNMP Agent Bold and underline indicates newly ported processes • SMTP MTA/MHS 7/30/04 • MHS Processes Light Blue or Clear boxes indicate new hardware component • Jet. Admin replacement Processes and/or data are listed underneath corresponding hardware component • Xyplex hosting 34

Step 6 – Process Loading l. Incrementally add DX hosts for load balancing for new functionality and data sets. - DX 1 for database server and infrastructure - DX 2 for IFP/GFE - DXn for decoders 35

Step 6 and OBx Hardware Architecture WAN AWIPS WAN LINUX LX Router LINUX XT Network Attached Storage (NAS) Linux AX Linux CP Nexrad RPG Ethernet 1000/10 Mbps SWITCH Serial MUX LS 1 PX 1 Not Upgraded • Printers • Xyplex • Modems • VIR’s • Simpacts SX 1 DX 1 PV Light Blue or Clear boxes indicates new hardware component DX 2 PV LDAD Firewall DX 3 (optional) LSx 1 7/30/04 36

WAN LS 1 • Dial. Radar • Netmetrix Step 6 and OBx Software and Data Architecture DX 3 (optional) • Decoders • Bin. Lightning • Satellite • Grib • Maritime • Warn. DB • Std. DB • Collective • Buf. Most. Decoder • Raob • Aircraft • ACARS • Profiler • Metar • Synoptic • Redbook • RAMOS • Bufr Drivers • Comms. Router DX 1 DX 2 NAS PX 1 SX 1 LSx 1 • Postgre. SQL • IFPServer Database Engine • GFE • OH cron/apps PV PV • Shef decoder • Text. DB read/write • Postgre. SQL Database • Radar. Storage • Radar. Msg. Handler • Radar. Text. Decoder • Handle. Generic • DNS • NIS • NTP • SNMP Agent • SMTP MTA/MHS • MHS Processes • Jet. Admin replacement • Xyplex hosting • Radar Processing • wfo. API • RMRserver • Radar Server • WWA Processes • NWWS Product • FFMP/SCAN • Data Storage • Safe. Seas • Site Backup • Trap Interceptor (ITO) • LAPS • MSAS • Text notificationserver • asynch. Scheduler • NWWS Scheduler • Notification server • LAMP • Dam. Crest(OH)** • Web Server • LDAD • router. Store. Netcdf** Server • ldad. Mon Applications • LDAD Server • LDAD routers • Listener • Local ldad applications Bold and italicized indicates newly ported processes 7/30/04 Light Blue or Clear boxes indicate new hardware component Processes and/or data are listed underneath corresponding hardware component 37

High Level Schedule l Key dates - Step 1 Deployment Decision by 21 October -necessary to complete initial deployment by 1 Feb - Step 2 OB 4. X – will provide performance improvements to Step 1 sites - OB 6 check-in 38

DX/NAS OAT Mary Buckingham OPS 24 8/10/04 39

DX/NAS OAT l OAT begins about 9/30 l Need for early hardware deployment decision (by mid Oct) - Risk hardware issues might not surface in so short a time - Can’t stress hardware much within these constraints - Possible a severe problem surfaces in operations - would affect entire schedule l Will take 60 days to finish OAT to ensure installation or software issues are found and fixed l Combine with Serial MUX Replacement OAT 40

DX/NAS OAT l l l l l Preliminary Mod Note proof on NMTW 12 Test sites 1 RH (1 st site, safest) 1 RFC 1 NCEP 9 WFO OB 4 Prerequisite (Begin 9/23) - Will affect pace of installations Conflicts with VTEC and Watch by County ORDs (8/30 -10/13) Sites selected based on: - History of poor performance and risk in severe wx - Cover the spectrum of site types - Space for new rack 41

DX/NAS OAT l Risk Factors - Expect similar installation issues as encountered in PX install Repointing all databases to new location (NAS) Unknown local mounts Rush on decisions and limited sites mean risk of not finding install or operational issues until deployment l Unknown how much relief step 1 will give sites - Faster I/O should help but more problems might lurk l OCONUS sites: unknown whether standard system will help their severe problems - Additional engineering might be required OAT will give info on whether more is needed 42

DS/AS Replacement Project Step 1 Software Development and Integration l No software development needed for Step 1 43

DS/AS Replacement Project Step 1 Maintenance and Logistics l Franz Zichy/Karthik Srinivasan (OST 31/OPS 12) – Maintenance and Logistics 44

Maintenance and Logistics Concept l Integrated logistic support l Maintenance and logistics concept l Maintenance policy and procedure l Disposal Procedure l M&C of NAS, DX 1 and DX 2 45

Integrated Logistics Support l Supply Support l Determine LRU • • DX 1, DX 2 cpu’s NAS Ge Switch Miscellaneous (cables, manuals, etc) - Assign Agency Stock Numbers (ASN) - Catalog [(p/n, price, manufacturer)] 46

Integrated Logistics Support l OPS 12 provides TIP (Technical Information Package) - Inform field • Schedule • Technical specifications • Maintenance concept • Logistic concept l NGIT will provide NRC with DX 1/2 Checkout procedures l NRC receives spare DX 1/2 servers 47

Integrated Logistics Support l failed component tested. - Vendor notified of failed component l Components divided into LRUs and placed into stock at NLSC. - servers - switches 48

Maintenance Concept 49

Maintenance Concept l Linux device fails - Open trouble ticket with NCF • • • - Hardware failure • - Hardware Network Software Order new from CLS Network failure • • If external, use NGIT resources to repair If internal, order new from CLS 50

Maintenance Concept l Software failure - Open DR and/or provide work around until next MR - OS only in step 1 l Linux hardware failure - Order new LRU from CLS Once received, ship defective unit back in same container Call NCF Install new device Site works with NCF to recover/configure device 51

Disposal of Existing Equipment l No disposal in Step 1 52

Monitor and Control l M&C of DX 1 and DX 2 will be through Xyplex l M&C of NAS will be through Xyplex 53

Security l Complying or will comply with all existing pertinent security policies, directives and rules l No known issues with Step 1 54

Installation Coordination Issues l Direct Ship from staging site in Chantilly to sites l New Rack Requires Space and Power - Similar to REP l Maintenance & Logistics issues - Spares for infant failures Deployment support 55

AWIPS DS/AS Replacment Step 1 Major Schedule Milestones Feb 04 Initial SET Brief PECP delivered Task Authorized Critical Design Review(CDR) FMK Development Mod Note Complete Operational Assessment Test Full Deployment 2/3 Apr 04 Jun 04 Aug 04 Sep 04 Oct 04 -Feb 05 4/26 6/23 8/10 8/30 9/28 9/29 10/29 1/6/05 2/16/05 10/6 56

Risks l NAS Single point of failure l Old HP’s and FDDI to new GE and NAS l Re-engineer of failover 57

Action Item Review l 58

Deirdre Jones l Closing Remarks 59