Title is 30 Pt Helvetica Bold

1
Software Enabled Control (SEC) Open Control
Platform (OCP) Requirements Specification
J. Pierre Wong December 14, 1999
2
Primitives for Geographic Location

• How do we find out where we are?
• How do we find out what we are a part of?
• How do we find out where another object is?
• Are maps available and, if so, from whom?

N
3
Primitives That Help Tell Time

• How do we find out what time it is?
• How do we synchronize clocks?
• How do we arrange for (nearly) simultaneous
  events?

N
4
Primitives To Introduce and Find Swarm Components

• How do objects join the system?
• How do we find an object?
• How does an object change its description/services
  ?
• How do we create new objects and allocate proper
  resources for them?

N
5
Primitives to Establish Communications (Streams)

• How do we find and choose among potential
  communications partners?
• How do we adjoin models to streams?
• How do we make streams robust?
• How do we layer protocols when some layers belong
  to OCP an others to applications? What is the
  division of responsibilities?
• How do we provide resource consumption
  projections?

N
6
Primitives That Control Controllers (Meta-Control)

• How do the OCP and the applications jointly
  coordinate reconfigurations of equipment and
  control?
• How do we change self-preservation instincts,
  control limits, and computational priorities
  throughout an entire vehicle, sub-swarm, or swarm?

N
7
Vehicle-Level OCP Goals

• Allow separate executable images to be installed
  and removed from a single processor card.
• Have all applications request and receive data in
  a manure so they dont know if the data is local
  or external.
• Provide for complete software portability between
  applications and operating systems.
• Automatically resolve data communication routes
  to previous and newly added applications.
• Use as much POSIX as possible to remove
  dependence on operating system.
• 100ms warm start from the time power is reapplied
  to when the highest rate application is ready to
  execute.
• Highly deterministic, low-latency processing.

N
8
OCP Hardware Requirements

• Considerations for processor performance.
• Thermal heat dissipation.
• Board space requirements.
• Meet resource requirements with and without
  cache.
• Memory management unit for partitioning of
  software.
• Error detection/correction.

N
9
OCP Software Requirements

• Time and timer services.
• Event, error and exception management services.
• Inter-partition communication and synchronization
  management services.
• Thread management services.
• Memory management services.

• The operating system task scheduler must support
  Rate Monotonic Scheduling for processes.
• Brickwall Partitioning of safety critical
  applications
• Less-critical partitions will be unable to
  adversely affect the memory, the processor
  execution time, or input/output resources and
  data associated with more critical partitions.

N