Realtime Roadmap and Architecture Diagram

							                   Realtime Roadmap and Architecture Diagram
                                             [ORBOS/97-05-21]

1. Introduction
The Realtime PSIG, in coordination with the ORBOS Task Force, plans to issue a series of RFPs for realtime and
closely related technologies. The roadmap is structured to fulfill the most urgent and best understood needs first,
while at the same time laying a foundation for CORBA solutions for a wide range of realtime application domains.
Over time, this set will be enhanced with a complete set of realtime and related technologies.

Two factors are relevant to this series of RFP submissions. Generic market needs and compatibility among realtime
technologies.

We recognize that some technologies that are critical to realtime systems, such as the need for user control over
ORB communication, are not unique to realtime systems. We expect that vendors who do not have substantial
realtime markets may choose to respond to these technology areas. For this reason, we will define such “generic”
technology areas separately from the more realtime technologies within our RFPs, allowing a vendor to implement a
generic capability without implementing the entire realtime technology suite.

On the other hand, it is critical that realtime technologies be compatible. For example, a realtime realtime system
must have compatibility between the time services and the scheduling service. This leads to the grouping of
technologies within the same RFP. Where timing considerations does not permit grouping, we have identified
dependencies in the roadmap.

The roadmap is provided so that other OMG groups, as well as RFP submitters, can understand the overall scope of
realtime CORBA. This will permit vendors to position their proposals for their markets, and will support
submitters in maintaining compatibility between initial submissions and the eventual goals of realtime CORBA.


2. Roadmap
The first set of technologies were selected based on the following factors:
          Urgency of user needs.
          Standardization of the current state of the practice.
          Technologies that are fundamental to or have board applicability for
                    realtime applications.

First set of RFPs: Release 3Q97, First Submission 4Q97.

         Realtime CORBA Foundations
                 Fixed priority scheduling support, including
                          end-to-end predictability
                 Enhanced time service
                 Flexible communications
         Minimum CORBA
                 Standardized minimum CORBA subset
                          with the capability to expand to full CORBA.

Second set of RFPs (extended realtime capabilities). Release 4Q97, First Submission 2Q98

         Fault Tolerance, including group communications and virtual synchrony.
         Dynamic Scheduling (this may be included in the first set of RFPs)
         Realtime Communication Protocols
Future RFPs. More specialized services. Release during 98, First Submission 4Q98-99. This is a working list,
and the final contents, structure, and ordering of these RFPs is not yet set.

        Resource Monitoring Service
        ORB Reliability
        Thread Management Service
        Flexible ORB Architectures
        Other types of scheduling services
        Resource Management Services
        Realtime extensions to other CORBAServices


3. Architecture Diagram
<<To be provided by June 9>>