CALSIDE Program - PowerPoint PPT Presentation

Title: CALSIDE Program


1
CALS/IDE Program
CECOM
AFMC
July 22, 1998
Washington, DC
LakeHurst
Indian Head
Type Designation Automated System (TDAS)
2
Our Purpose Today

• Section 1 Focus on the TDAS Background
• Section 2 Highlight the Works Accomplished
• Section 3 Discuss Current Future TDAS
  Issues
• Section 4 Introduce Proposed TDAS
  Architecture
• Section 5 TDAS Web Client Demo

3
Section 1

• TDAS BACKGROUND

4
TDAS Means Going From
The Ledger
5
The Concept
TDAS Processing

• Contractor(s)
• DoD Control
• Points
• Gov. Agencies

• CECOM/AFMC
• Super-client
• Processing and
• Data Manipulation
• Privileges

TDAS Extensive Capabilities
6
The Concept
U.S. Army
Information Hub Processing
U.S. Air Force
AFMC
CECOM
FLIS Federal Logistics Information System
U.S. Navy
Initial Query Path
User Community
External
U.S. Marines
7
Concept Of Operation A Non-CDRL
To Serve as a Means of Understanding and
Agreement on the Functionality and Operational
Process of TDAS
8
Concept Of Operations

• TDAS Will
• Enable electronic submittal of DD Form 61
• Allow MSTDS personnel to directly retrieve and
  update
• DD Form 61 data.
• Allow clients to directly query CECOMs type
  designation
• data.
• Facilitate client entry of appropriate data on
  DD Form
• 61 data.
• Facilitate verification of appropriate data on
  DD Form 61.
• Develop database of relevant DD Form 61 and
  previous
• type designation data. (1943 up to the
  present)
• Enable retrieval of legacy DD form 61s VIA key
  data fields in
• database.
• Enable connectivity to DLSC Information Hub for
  external
• users.
• Provide security to control access to DD Form
  61 data.
• Enable production of search scenarios (i.e.,
  duplications)
• and generation of custom reports.

Create Revise Close-out
9
Conceptual View / To-Be
CECOM AFMC
SuperClient
SuperClient
U.S. Army
U.S. Air Force
AFMC
CECOM
S E R V E R
FLIS
U.S. Navy
Remote/External
DD61 Submission
U.S. Marines
Type Designation Data Base(s)
Client VIA Internet
Type Designation Automated System Extensive
Capability
10
TDAS Architecture

• Super-Client (CECOM, AFMC)
• Clients
• Manufacturing. Admin. Contractors
• Government Agencies
• Department Control points

11
Computer Selection/Acquisition
Windows NT

• Competitive Acquisition Process Completed
• 5 Proposals received
• Bid Rating Assessment Model (BRAM)
• Performance Warranty/Service
• Technical Conformance Price
• Equipment Delivery to ManTech, WV by
• September 31, 1997
• EDA/SQL Installation Late October 1997
• Acquired Both CECOM and AFMC Initial
• Configuration

12
Windows NT Configuration

• Pentium Pro SMP Server
• Oracle Database Server 7.3
• Oracle Web Server
• EDA/SQL Server 3.2.3

External Users
Internet

• DD 61 Ref. Repository
• Type Desig Active File
• MIL-STD-196/1812

Internet

• Super Clients
• Intel Pentium Processor
• 32 MB RAM
• 2.0 GB HD
• 8X CD-ROM

DLSC Hub
NOTE Scanner Per Configuration
13
Legacy Data Issue
CECOM / DD61(s)
AFMC / DD61(s)

• Paper Based
• Microfiche
• Microfilm
• Magnetic Tape (9/S2K Format)
• Canonfile 250 Format

Canonfile 250

• Canonfile 250 System
• Multiple Disks Containing
• DD61(s)

Standard
ASCII Format
GOAL Capture All DD61(s) Processes So
We Can Eliminate The Ledger Books
14
Preliminary TDAS Database Design
Fische II
Paper Cannonfile (1987 - 1996)
Microfiche (1943 - 1969)
S2K (1970 - 1986)
SRN
SRN
SRN
SRN
Key Fields
Key fields
65 fields
90 fields
SRN
SRN
Block 14.7
Block 22
SRN
Note The unique SRN will be used as the primary
key across all tables.
Block 21
15
Our Approach

• Paper First, gt 82,500 Pages of DD61 Format
• Key data fields full form image
• Initial process set-up
• Scanning process/full image in
• TIFF4 format
• Key data fields by double entry for
• 99 confidence factor
• Note Data clean-up process is costly
• Process analysis and review
• Coordinated batch process with daily
• production currently at 500-600 documents
• Microfiche System 2K Data Tapes and Canonfile
• 250 (AF) Next

Five Pages of Detailed Rules Governing Data
Entry Process (EM)
16
Legacy Data Conversion
1st Conversion Process 1970 Today
17
SECTION 2

• WORK ACCOMPLISHED TO DATE

18
JETDAS Releases

• JETDAS 1.0
• Initial version
• JETDAS 1.1
• Interim release
• Gave users the ability to change the
  automatically-generated SRN
• JETDAS 2.0
• Fixed several bugs in 1.0 and 1.1
• Made several revisions to the field validation
  algorithms for submitting a DD Form 61 Added 4th
  tier to JETDAS (addition of government agency
  in block 2)
• Added ability to view a form based upon the type
  designation
• Updated the drop-down menus on all screens
• Updated privileges of the different user types
• Added ability to query the reports based upon
  more search criteria
• Replaced Top Secret in block 7 with CCI

19
JETDAS Releases (Cont)

• JETDAS 2.1
• Fixed bugs in 2.0
• Changed the SRN concept behind a package (the
  sequence number remains static for items within
  a single package)
• Gave DCP users the ability to change the
  originator (block 1)
• Added ability to generate a report of the JETDAS
  users
• JETDAS Administrator 2.1
• No changes since version 2.0
• JETDAS Thin Web Client 2.0
• Initial version of a thin web client
• Functionality consistent with JETDAS 2.0

20
JETDAS Releases (Cont)

• JETDAS Thin Web Client 2.1
• Fixed several bugs in 2.0 web client
• Functionality consistent with JETDAS 2.1
• JETDAS Administrator 1.0
• Initial version
• JETDAS Administrator 2.0
• Fixed bugs
• Added ability to generate a report of the JETDAS
  users
• JETDAS Administrator 2.1
• No changes since version 2.0

21
What Comes With TDAS Installations?

• TDAS Software - Oracle, Cold Fusion, TDAS
  Standalone, TDAS Web Client, TDAS Admin, Backup
  Exec, Anti-virus, TDAS Web page
• TDAS Hardware - Server, PC(s), Scanner
• HELP systems for both systems
• Software Change Request Reporting software
• Users Guide
• Administrators Guide
• On-site training
• Help-desk type support from WV

22
Current TDAS Architecture

• ALR Quad 6 Revolution
• Pentium Pro SMP Server
• Added 9.0 GB HD/30 GB Total
• Added 128MB RAM/256 MB Total
• Oracle Database Server 8.0
• IIS Web Server
• EDA/SQL Server 3.3.1

• External Users
• Web Browser
• only

Internet

• DD 61 Ref. Repository
• Type Desig Active File
• MIL-STD-196/1812

Internet

• Super Clients
• Intel 233 MHz Pentium
• 64 MB RAM
• 4.3 GB HD
• 16X CD-ROM
• Win95
• EDA/SQL Client 3.2.3

DLSC Hub
EDA/SQL 3.2.3
NOTE Scanner Per Configuration
23
JETDAS Deployment

• Stand Alone JETDAS
• CECOM (2 systems)
• CASC/AFMC (2 systems)
• Indian Head (using Web client -- firewall)
• Lakehurst (3 systems)
• Web Client ( Users Registered)
• Canada
• Hanscom

24
JETDAS Processing Statistics

• STATUS OF NON-LEGACY FORMS AS OF FRIDAY, 1100 ON
  July 17, 1998
• APPROVED (FINAL APPROVAL) 76
• APPROVED BY A DOD CONTROL POINT 26
• APPROVED BY A DEP'T CONTROL POINT 48
• APPROVED BY A GOVERNMENT AGENCY 1
• REJECTED (PERMANENT) 1
• RESERVED BY A DEP'T CONTROL POINT 14
• RESERVED BY A GOVERNMENT AGENCY 1
• RETURNED TO A DEP'T CONTROL POINT 2
• RETURNED TO A GOVERNMENT AGENCY 2
• OTHER (UNKNOWN STATUS) 2
• TOTAL FORMS SUBMITTED 173

25
Legacy Data Conversion

• STATUS OF LEGACY FORMS CONVERTED AS OF July 10,
  1998
• Total Microfiche keyed 75,613
• Total Paper keyed 39,240
• Total Canonfile 250 keyed 3858
• TOTAL FORMS CONVERTED 117,124

26
AFMC TDAS

• ASETDS (Aeronautical Support Equipment Type
  Designation System)
• Ready for Deployment July 10th (after quick
  release of JETDAS 2.1 on July 1st.
• Installation Scheduled July 27th - Canceled
• Current Installation Date Aug. 10th.
• AFMC/CASC Contact John Bauer

27
SECTION 3

• TDAS CURRENT and FUTURE ISSUES

28
High-Level Project Plans

• Transfer/Install/Orientation of TDAS at CECOM
  --------------------------Completed
• Install CECOM Beta Web Clients
  (3/4)----------------------------------------Compl
  eted
• Develop AFMC TDAS System -----------------------
  -----------------------------Completed
• Test AFMC TDAS System --------------------------
  -------------------------------In progress
• Release TDAS Version 2 (2.1) to CECOM
  ------------------------------------Complete
• Transfer/Install/Orientation of TDAS at AFMC
  -----------------------------August 10th Note
  AFMC TDAS delivery has been rescheduled twice.
• Continue with future TDAS Systems
  Planning-----------------------------In progress
• Complete Legacy Data Conversion
  Process--------------------------------Nov. 1998
  Note
  Projected date that could vary dependent on the
  quality/format of data back to 1943.

29
Issues/Problems Encountered

• CECOM Internet Connection Performance
• Frequent connection problems
• Slow response to problems
• Approx. 50 TDAS reported failures due to
  internet connectivity problems
• On-site System Administration and Support
• MT remains the administrator for the system
• Backups performs by operations personnel
• No formally assigned systems administrator
• Computer Literacy Issues
• Approx. 25 TDAS reported failures due to
  misunderstanding of TDAS system and/or computer
  literacy problems.

30
Issues/Problems Encountered

• Requirements Changes Relates to Lifecycle Issues
• Numerous changes introduced long after Beta
  testing
• Changes insisted upon throughout JETDAS
• Lack of Planning and Implementation to the Field
  Users
• Coordination problems with field users
• Enforcement tough if support is not available to
  users
• Multiple TDAS System Users
• Some users will need to submit to JETDAS and
  ASETDS both.
• How do these people determine which system to log
  into?
• Ex. Ray Santee (Lakehurst) submits to both CECOM
  AFMC

31
Multiple System User Problem
Ray Santee/Lakehurst
External Users
Internet
Internet
Internet
ASETDS/AFMC
JETDAS/CECOM
32
Information Builders EDA/SQL

• Upgrade to Oracle 8.0 to handle DD61 images
  (.tiff)
• Problem encountered with EDA/SQL 3.2.3
• Upgrade EDA/SQL 3.3.1
• Works with older NT client software 3.2.3
• Testing w/ PRC for connection with HP 3.2.3 EDA
  for HP UNIX
• 20K per site for EDA/SQL
• All abilities of EDA/SQL can be done with current
  technologies more cost and performance
  effectively

33
SECTION 4

• INTRODUCE PROPOSED TDAS ARCHITECTURE

34
Proposed Architecture
JETDAS/ CECOM
ASETDS/ AFMC
Additional site??
Additional site??
TDAS Operation Server (WV)

EDA/SQL Oracle 8.0 Data Backup Internet Access
FLIS
Type Designation Data Base(s)
Cold Fusion/Oracle Transparent Gateway
DLSC HUB
EDA/SQL Internet
35
Advantages To This Architecture

• Eliminates additional cost of EDA/SQL for each
  site (yearly maintenance included)
• Direct integration of DLSC Hub to TDAS for all
  TDAS users if authorized
• Eliminates Multiple TDAS User Problem
• Easy Ability to Make the DLSC Hub Internet
  accessible
• Avoid purchasing additional HW for new sites
• Could eliminate Stand-Alone version and release
  Web client only -- to control CM and allow for
  immediate upgrade response
• Technical support and HelpDesk activity could be
  better performed from WV with proper support and
  resources

36
SECTION 5

• TDAS WEB CLIENT DEMO