UF HCS

1
UF HCS Honeywell DSES Opportunities

• Presented by
• Advanced Processing Systems

2
Agenda

• Introduction - Honeywell
• UF HCS Capabilities Overview - UF
• Integrated Payload Overview - Honeywell
• Collaboration Plan - Honeywell
• Overview of Opportunities - Honeywell
• Working Group

3
UF HCS Overview
4
Integrated Payload
5
Market Need

• A market need has been established for an
  integrated payload processing system based on the
  Honeywell payload product line.
• To fulfill this need we must define a system
  hardware architecture based Honeywell payload
  processors and peripherals.
• A software system framework must also be defined
  to facilitate the integration of hardware
  components, horizontal services, and customer
  applications.
• The combined software and hardware must provide
  the capabilities desired by our customers.

Integrated payload systems make application
development easier.
6
Keys to Business Growth

• Modular and Integrated Systems
• Can assemble/architect system to meet mission
  needs with low NRE
• Pay only for missionization
• Inexpensive and readily available SDU system
• Provide a mechanism to evaluate and benchmark
  algorithms
• High Speed Interconnect to meet increasing
  bandwidth requirements
• Reconfigurable Computing has been recognized as
  key technology

We are listening to our customers and we will
deliver.
7
Get in the door early!
Study of Mission Algorithms on Integrated Payload
SDU
Continue refinement of algorithms on SDU and
demonstrations conducted with instrument
prototypes
Custom flight components are developed if
necessary
Custom components are integrated and tested on
flight Integrated Payload
Software migrates to flight unit for final
qualification
Flight unit complete
Integrated Payload Development Cycle
Integrated Payload Development Cycle
Program Life Cycle
Phase 2 Elaboration
Flight
Phase1 competition begins
Customer Internal Development
8
Overall IRAD Objectives

• Establish a substantive technical advantage in
  the area of complete satellite payload processing
  systems, enabling Honeywell to achieve
  significantly increased program roles.
• Deliver increasing system value to our Customers
  by pre-integrating the technologies of
  Honeywell and its Partners.
• Establish the system architecture for a
  heterogeneous system.

Honeywell Payload Systems will be the first
choice in the Integrated Payload Market
9
Proposed Product Offering

• Integrated Payload Processor
• Pre-integrated software components
• operating systems, device drivers, system
  monitors, runtime libraries, etc.
• Pre-integrated hardware components
• system controller, data processors,
  reconfigurable modules, IO, memory, etc.
• Pre-integrated development tools
• Development software and configware libraries,
  verification tools, compilers, etc.
• Scalable and Software Compatible
• System will be scalable to meet the particular
  requirements of the target application
• Software will not break if additional components
  are added to the system
• Provide support to quickly get customer up and
  running and resolve technical issues
• Provide a low cost SDU that is equivalent to
  flight system

The Integrated Payload will be a turnkey solution
ready for application development.
10
Integrated Payload System
Mission Application
Honeywell Integrated Payload System
Horizontal Services APIs, Interprocessor
Communication, Runtime Libraries etc.
System Software Components OS, Hardware
Abstraction, Device Drivers, etc.
Payload Interfaces
RHVP
SBC-PDP P/L Data Processor
SBC-PC Control Processor
MuSICA
Custom I/O Module (e.g. 1394)
HRSC
Mass Storage Module
Payload, S/C Comm System Interfaces
PMC
PMC
PMC
cPCI Backplane (control)
Point to Point High Speed Interconnects (data)
Honeywell DSES does payload processing systems
well and we will make the Integrated Payload a
reality.
11
Benefits of Product

• Reduce cycle time
• Eliminating the long integration phase
• Lowers integration risk
• Reduce amount of new development
• Ease migration from SDU to flight unit
• Reduce costs
• Reduce NRE
• Higher volume will yield lower production costs
• Increase overall product quality
• Product will have more time to mature

Higher quality and reduced costs can lead to
increased profit!
12
2003 IRAD Objective

• Primary Goal
• Integrate available subassemblies into a
  functional system model
• Develop system architecture to support the
  integration of heterogeneous payload systems
• Develop APIs to configure and manage available
  subassemblies
• Secondary Goal
• Develop a flight-like proof of concept
  application that can be utilized to support new
  program pursuits.
• Demonstrate ability to coordinate projects with
  other Honeywell sites

We are well on our way to achieving our goals
13
Proof of Concept System Integration
(PoCSI)Description
14
Demonstration goals

• To show the capabilities of the Integrated
  Payload by processing real-time video
• To show the reconfigurability of the system by
  implementing multiple modes of operation using
  reconfiguration
• To create an eye-catching demonstration that
  will draw customer interest
• To help develop standard interfaces and design
  flows for reuse by us and our customers

15
Design Considerations

• The HRSC has no microprocessor onboard. All
  functionality on the HRSC is implemented in
  hardware. Therefore, devices requiring software
  drivers to operate can not be used as PMC modules
  (for example webcams)
• Communication protocols such as IEEE 1394 and USB
  are complicated to implement in hardware (also
  costly)
• Most video formats such as composite video or
  S-video are analog
• Cameras that have digital video interfaces (such
  as CameraLink cameras) are cost prohibitive
  (price 4000)

16
System Block Diagram
17
Integrated Payload Software Architecture
18
Software Architecture - Goals

• Significantly reduce initial integration effort.
• Reduce dependencies on specific hardware,
  operating system, and BSP versions.
• Provide a modern COTS-like development experience
  for customers.
• Provide a system that can be extended by
  additional nodes and additional capabilities.
• Maintain a distinction between new product line
  technologies and demonstration software.

19
Software Architecture - Functional Capabilities
This is a functional model of the domain of
payload processing systems. It provides us a
tool for describing and understanding these
systems.
General services needed by most applications.
These represent value-add opportunities where a
customer typically invests effort, but does not
focus on their specific application.
These are basic computing environmental
conditions. They relate to the ability to
initialize a system, command peripherals, and
develop traditional software services.
20
Software Architecture - Architectural Elements
Current focus is on the Base Processing
Environment.
1
2
3
5
4
21
Next Steps
22
Future Next Steps

• Integrate additional hardware (e.g. RapidIO)
• Develop additional device drivers (e.g. MUSICA,
  1394).
• Investigate integrating with Glendales satellite
  structure lab
• Investigate additional horizontal services.
• Integrate payload system software with RTOS
  development tools.
• Continue to investigate additional RTOSs.
• Define development flows.

23
Collaboration Plan
24
Proposed Plan

• Communication
• Identify key representatives from each
  organization
• Establish recurring meetings
• Direction
• Define common goals and objectives for research
  and development
• Action
• Identify and pursue most promising opportunities

Together we are more productive and competitive.
25
Overview of Honeywell Opportunities
26

• Internships
• New Millennium ST-8
• Integrated Payload
• HRSC
• DARPA (RWI, others)
• SSPA
• Restricted (SCA, others)
• NASA