1 / 20

Gary L. Smith NAVAIR V-22 IETM IPT Lead 10 February 2004

V-22 IETM Overview The Evolution of the V-22 IETM. Gary L. Smith NAVAIR V-22 IETM IPT Lead 10 February 2004. V-22 IETM Overview. The Evolution of the V-22 IETM Portable Electronic Display Device (PEDD) Data Authoring Environment Presentation Software Lessons Learned The Way Forward.

elroy
Download Presentation

Gary L. Smith NAVAIR V-22 IETM IPT Lead 10 February 2004

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. V-22 IETM Overview The Evolution of the V-22 IETM Gary L. Smith NAVAIR V-22 IETM IPT Lead 10 February 2004

  2. V-22 IETM Overview • The Evolution of the V-22 IETM • Portable Electronic Display Device (PEDD) • Data Authoring Environment • Presentation Software • Lessons Learned • The Way Forward

  3. Portable Electronic Display Device • 1st Generation PEDD (1996-1999) • ART SPARC 5-based device running Unix • Issues: cost ($25K), UNIX based, noisy, large and weight (35 lbs) • 2nd Generation PEDDs (1998-2001) • Honeywell (formerly Allied Signal) “tablet” running WinNT 4.0 • Issues: cost ($15K), speed, sunlight visibility, and trackball • GETAC A740 ruggedized laptop running WinNT 4.0 • Issues: speed, sunlight visibility, and battery life • 3rd Generation PEDDs (2002- ) • GETAC A760 ruggedized laptop running Win2000 • Issues: no major ones with upgraded processor and transflective screen

  4. Portable Electronic Display Device GETAC A760 Ruggedized Laptop

  5. Data Authoring Environment1st Generation • JIMIS Authoring Environment (1994-1999) • SGML-based authoring environment introduced in 1994 • Initial product baseline available to V-22 authors in June 1995 as GFE • Did not include electronic interface to LSA database • Continued in use on V-22 through 1999 and still being used by JSTARS program

  6. Data Authoring Environment2nd Generation • PDAT Authoring Environment (1999- ) • Oracle-based Publications Data Authoring Tool (PDAT) developed by Boeing Helicopter, using V-22 program funds • Incorporated direct interface to LSA database • Real-time presentation functionality • Eliminated time consuming parse activity • Still in use by V-22 authors today

  7. Data Authoring EnvironmentPublications Data Authoring Tool

  8. Presentation Software1st Generation • JIMIS Presentation Software (1995- ) • Developed in early 90’s for JSTARS (E8C) Program • First Class IV IETM delivered to the USAF for operational use in March 1995 • Adopted for use by V-22 in 1995 • Unix-based ANSI C application ported to run under WinNT in 1998 • Version 6.X being used by JSTARS and V-22 today

  9. Presentation Software2nd Generation • Phoenix Presentation Software (2004 on) • Web-based Class IV presentation system • Minimum data migration issues involved in using currently authored data • Data integrity testing currently being conducted by JSTARS and V-22 personnel • Version 1.0 to be released to V-22 in May 2004 representing fully ported JIMIS functionality (and more)

  10. Presentation SoftwarePhoenix

  11. Lessons Learned • Lesson #1- Adhere to open standards to the maximum extent possible • Open standards foster cost effective development • Avoid proprietary non-standard hardware and software solutions, if at all possible

  12. Lessons Learned • Lesson #2- Allow for technology growth path • Don’t get locked into a specific technology or standard • Look to the future • Establish a sensible upgrade strategy

  13. Lessons Learned • Lesson #3- Hardware is cheap • Do not let hardware costs adversely dictate your technology decisions • Be forward thinking • Don’t be “penny wise and pound foolish”

  14. Lessons Learned • Lesson #4- Don’t let data development environment dictate the final product • The deployed product should be independent of the data development methodology • Publications data need only reflect the requirements of the supportability data

  15. Lessons Learned • Lesson #5- Use COTS wisely • Just because it’s COTS doesn’t mean it’s good • COTS does not necessarily mean open • Avoid COTS products with no readily available alternatives

  16. Lessons Learned • Lesson #6- Spec compliance does not guarantee an acceptable product • Being 100% spec compliant does not ensure the end-user will accept the delivered product • Proper interpretation of the implementation of the spec requirements is the key

  17. Lessons Learned • Lesson #7- Involve the end-user • The user is the key to interpreting the spec • User involvement fosters buy-in of the delivered product • Manage the user expectations

  18. The Way Forward • Near-term Initiatives • Complete the upgrade to web-based Phoenix • Support the execution of a successful V-22 OPEVAL • Evaluate and procure a 4th generation PEDD • Establish the framework for a V-22 Automated Maintenance Environment • Define the requirements and technology path for improved IETM graphics

  19. The Way Forward • Mid to Long-term Initiatives • Evaluate alternate hardware technologies for the deployed IETM, to include: • Wearable devices • Hand-held devices • Wireless capabilities • Evaluate the benefits and cost of migrating to an XML environment • Examine the benefits and cost of achieving S1000D spec-compliance

  20. The Way Forward On the V-22 program, we will continually strive to provide the end-user with the best possible IETM product we can.

More Related