1 / 7

RAI Information Brief

RAI Information Brief. Prospective from the RAI Working Group. What is Resource Adapter Interface (RAI) ?. What does DOD need for RAI. A standard(s) that can fulfill the definition. Practical enough for today

kirby-cardenas
Download Presentation

RAI Information Brief

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. RAI Information Brief Prospective from the RAI Working Group

  2. What is Resource Adapter Interface (RAI) ?

  3. What does DOD need for RAI • A standard(s) that can fulfill the definition. • Practical enough for today • Flexible enough to represent more robust implementations that further maximize platform independence in the future.

  4. DOD Goal for RAI • Allow for maximized independence of the test program software. • Allow for advanced test instrument interchangeability. • Provide a reduced total cost of ownership and improved ATE capability & flexibility. • Enhance support for synthetic instruments.

  5. DOD Desired RAI Requirements • Support for a Test Requirement abstraction where: • A test requirement is a concert of time related signals and locations. • Support for the existing procedural representation. • Support for a non-procedural (data only) representation.

  6. DOD Intent • Recommend a standard or standards for RAI to be used in DOD acquisition policy. • Support a wide array of architectures. • Provide a path to future capability and robustness. • Incorporation into future DOD ATE.

  7. Bottom Line • We think IEEE-1641 can be enhanced to accomplish these objectives. • We want to work with the committee to induct our requirements. • Once accomplished we want to use IEEE-1641 as the Signal based Requirement abstraction candidate for DOD interface mandate.

More Related