1 / 18

DEW(RF) Database Overview (U) 14 October 2009

UNCLASSIFIED. DEW(RF) Database Overview (U) 14 October 2009. Scott F. Griffiths Naval Surface Warfare Center, Dahlgren Division Directed Energy Technology Office, Code Q22 18444 Frontage Road, Suite 328 Dahlgren, Virginia 22448-5161 (540) 653-8059 (703) 432-0909 scott.griffiths@navy.mil

plato
Download Presentation

DEW(RF) Database Overview (U) 14 October 2009

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. UNCLASSIFIED DEW(RF) Database Overview (U)14 October 2009 Scott F. Griffiths Naval Surface Warfare Center, Dahlgren Division Directed Energy Technology Office, Code Q22 18444 Frontage Road, Suite 328 Dahlgren, Virginia 22448-5161 (540) 653-8059 (703) 432-0909 scott.griffiths@navy.mil scott.griffiths@usmc.mil UNCLASSIFIED

  2. Background • Originally developed under the Joint Program Office for Special Technology Countermeasures (JPO-STC) Counter RF-Attack program • July 1997 – Database proposed to community at first ever tri-service HPM program review • Aug. - Oct. 1997 – Scoping study performed to define requirements (14 DoD organizations) • Database objectives: • Facilitate JPO-STC RF countermeasures development • Share (leverage) HPM data across Services / Agencies • Database requirements documented in “Software Requirements for DEW(RF) Database”, Rev. 4, 24 July 1998 (FOUO) • Four major releases have occurred (1999, 2002, 2005, 2007) • OSD/HPMSG database charter signed (March 2002)

  3. OUSD Database Charter • Charter signed March 2002 • JPO-STC designated as HPM/CHPM Database Manager • Establishes/promulgates procedures and roles to: • “Standardize the reporting of captured empirical, system or subsystem level, parametric data” • “Define common data formats” • “Establish a single repository for all DoD HPM/CHPM effects data (regardless of program, executing organization, security classification, or end use)” • “Consolidate DoD funded, sponsored, or supported HPM/CHPM effects data within that repository” • Funding to be arranged by OSD

  4. Characteristics/Development Team • Characteristics: • DVD-ROM, Windows 95/98/NT/2000/XP, PC Requirements: Min. (P3, 64 MB Ram), Rec. (P4 3GHz, 1 GB Ram) • Software - Sybase SQL Anywhere 7.0.00, PowerBuilder 8.0.00 • 2 Versions - Read Only, and Read-Write (Field Version) • Database Classification is SECRET • Development Team • JPO-STC/NSWCDD - Scott Griffiths, David Stoudt • AFRL - Capt. John Allison, Hildy Hogate • ARL - John Tatum • Booz, Allen and Hamilton - Vincent DePrenger, Don Blake, Bob Hart, Steve Eng

  5. Benefits • Resource Multiplier • Reduces Duplication of Effort by Sharing Info • Facilitates Joint Testing (Shared Costs) • Helps Identify Knowledge Gaps and Directs Testing • Facilitates Sharing of RF Sources / Test Facilities etc. • Identifies Information Sources • Provides an Archive for Information

  6. DEW(RF) DatabaseInformation Areas (U) Formally Chartered in FY02 by OUSD(AT&L) to be the DoD repository for all offensive & defensive HPM effects data.

  7. Database Organizationby Screen (U) • Subject Areas: # Screens# Records • Programs 6 46 • RF Sources (Transmitters / Antennas) 14 188 • Target Assets 9 4,046 • Test Facilities 5 50 • Test Information 10 185 • Test Results 4 59,798 • Analysis / Simulations 2 6 • Personnel / Organizations 9 743 • Documents 4 626 • Pictures 1 455

  8. Features – User (U) • Organized hierarchy • Easy to comprehend • Easy to move around database • View linked pictures (JPEG, BMP, many other formats) • Export data • Many formats (Excel, text, PDF, HTML, XML, DBase, …) • With or without headers • Printing (Overview screen data) • User assistance • 500 page User-Guide • "Help" button • Technical support

  9. Features – Sort/Search (U) • Deluxe searches • Search by field in table (numeric or text) • Search by user-defined parameters • Search by key words (searches ALL fields in table) • Ability to build complex queries • AND, OR, parentheses • =, >, <, ≥, ≤, "LIKE" • Wildcards ("%") • Built query available for user editing • Cumulative • Sorting (multiple tiers) • Filters (similar to searches) • Search linked documents (DT Search: PDF, Word, PPT)

  10. Basic Search Types (U) • Relational • System Type - “List all tests on IR air-to-air missiles.” • Hierarchical - “List all tests on subsystems of F-16” • Logical - “List all tests on system XYZ at 2GHz that produced damage.”

  11. Hierarchical AssetDescriptions (U) Avionics Weapons Systems Avionics Propulsion Propulsion Weapons Systems LRU A LRU B LRU C Data Bus • Asset Descriptions - Infinite Level of Detail  System, Subsystem, …, Component • Asset Relationships - Infinite Links Common Components

  12. Features - Data Entry (U) • Flexible data entry options (e.g., enter test only, test summary data, or shot-by-shot data) depending on availability of data • Default values • Duplicate records • Ability to link multi-level targets to Tests • User-Defined parameters • Excel Export-to-Import (VERY useful) • Responsible for huge increase in populating Test Results • Database-to-Database import • Allows collecting data from multiple copies

  13. ACTD Data Log LOG 1 LOG 2 LOG 3 LOG 4 San Clemente Test Questions Answers Data Collection Process (U) On Site Scanning Identify Documents High Priority Scanned Document Files Database Population Laboratory Personnel Data Lower Priority DETO Document Scanning DETO Master Database Server Scanned Document Files For Official Use Only

  14. • • • Database Distribution (U) DEWO Data Collection Team Archive (Read-Only) Database Field Version (Read-Write) Database Approved Organization #1 Approved Organization #2 DEWO Approved Organization #3 Data Approved Organization #M Laboratory Test Personnel Field Version (Read-Write) Database Plans for Migration to SIPRNET For Official Use Only

  15. Distribution Policy • Distribution authority resides with HPMSG chairman and HPMSG member orgs. • The Database may be distributed to: • All HPMSG member orgs. • Other DoD orgs., Gov’t orgs., and contractors by formal request from HPMSG orgs. sent to DEWO • Distribution conditions • Foreign govt’s/contractors are not allowed access • Distribution statements/classifications may further limit distribution • Distribution reviewed by HPMSG prior to release • Done through email with 1 week for comment • Active participation is required of all recipients • Contribution of test data and reports

  16. User Organizations Version 3.0 Distribution • Other recipients of versions 1.0 and 2.0 • Lockheed Martin, ARL-SLAD, NASIC, AAMCOM, JAYCOR/TITAN, JPO-STC, TACOM-ARDEC AFRL AFRL/RWAL AMRDEC ARL ATK DIA DOE(HQ) DTRA JHU/APL JIEDDO JNLWD JWAC LANL L3-JAYCOR MCIA MIT MSIC NAWCWPNS NGIC NRL NSWCDD OUSD(AT&L) RDECOM (Picatinny) RDECOM (Redstone) SNL USSOCOM Initial Version 2.0 Distribution

  17. Funding Overview Fiscal Year Agency 97 98 99 00 01 02 03 04 05 USA(CECOM) 30 55 JPO-STC1 125 386 395 250 235 205 166 240 DTRA 25 15 USAF2 100 75 USN(NSWC) 12 13 Totals 30 280 498 423 250 235 205 166 240 Dollars in $K 1 Does not include Government Cost (98-$200K, 99-$125K, 00-$75K, 01-$50K, 02-$45K, 03-$35K, 04-$35K, 05-$60K) 2 Funding is for Data Collection in Specific Topic Areas

  18. Recommendations • Secure stable funding • Ensure tri-Service participation • Migrate database to SIPRNET • Provides real-time access • Simplified data collection/distribution processes • DVD distribution may still be required • Perform a new scoping study to validate/update database requirements • Improve the data collection process • Train community to enter data as it is collected/analyzed • Determine enticement for entering data– hammer or carrot • Transfer database management/support functions to DTIC for execution • Requires a transition period while community is spun up to enter data

More Related