Presentation is loading. Please wait.

Presentation is loading. Please wait.

SPIES (Sensor/Platform Interface and Engineering Standards)

Similar presentations


Presentation on theme: "SPIES (Sensor/Platform Interface and Engineering Standards)"— Presentation transcript:

1 SPIES (Sensor/Platform Interface and Engineering Standards)
Overview for SAE Technical Assessment Panel Selection of Interfaces to Standardize May 2009 Many of the slides came from: 11 - Open Architecture by Walles.ppt

2 SPIES Program Goals Standardize EO-IR sensor/platform interfaces for future upgrades and acquisitions Enable reduced life-cycle costs on future upgrades/acquisitions Acquisition (simplify process, increase consistency) Integration (simplify, reuse of hdwe/sfwe) Maintenance (reduced spare sets, reduce training) Upgrades (reduce cost, increase competition, increase flexibility) Promotes Modular Open Systems Approach Promotes Open Architecture Maintains or increases warfighting capability IS supported by Industry and Navy organizations DOES NOT reduce system performance, reliability, maintainability or availability of critical sensor systems Develop a methodology and process for maintaining and revising the standardization Note: Standardization can include profiles, design guides, recommended engineering practices, standards, interoperability requirements, integration requirements, etc.

3 Purpose of This Meeting
Identify platform/sensor interfaces applicable to present and future aircraft and sensor subsystems Prioritize those platform/sensor interfaces that provide the most value THINK ………….FUTURE, FUTURE, FUTURE, FUTURE

4 EO/IR Systems Under Consideration
Gimbal-Turret Imaging and Targeting Sensors EO, MWIR, LWIR, SWIR, Multi-spectral Laser, Navigation, Targeting Pod Mounted Sensors Defensive Electro Optical Suite UV, IR, EO, Multi-spectral, IR threat tracking sensors, Laser CM Advanced Sensors Active Laser Imaging Systems, Hyperspectral Imaging, Synthetic Aperture Imaging, Active Hyperspectral Imaging Distributed Aperture Electro Optical Systems NEED TO CONSIDER ALL TYPES OF EO SYSTEMS TO DETERMINE INTERFACE BOUNDARIES TO ALLOW FOR MAXIMUM FLEXIBILITY FOR LEGACY UPGRADES AND FUTURE SYSTEMS 4

5 Definitions (from Dave Neel)
Interoperability: - The ability of two different systems (using "open" interfaces) to work together correctly. Interchangability: - The ability to replace one system with another

6 Definitions (SPIES) Interoperability: - The ability of two different systems, subsystems, or modules manufactured by different companies (using "open" interfaces) to work together correctly. Interchangability: - The ability to replace one system with another that is similar but not the same model or built by the same manufacturer.

7 Initial Platforms of Interest
Fixed Wing JSF, F-18, EA-6B, AV-8B, EP-3, P-3, P-8, C-130J Rotary Wing MH-60,H-53,V-22,AH-1W,AH-1Z,UH-1N,UH-1Y,VH-71 May be considered with STUAS if it becomes a program of record UAVs BAMS, Fire Scout, STUAS, N-UCAS Long Life to Influence Saving Opportunity to Influence Interfaces JSF P-8 V-22 STUAS H-53 Number of aircraft Major EO-IR Sensor Upgrades Distributed Sensor Architecture Initial Selection

8 Legacy System Architecture
Sensor manufacturer hardware/software Aircraft ECU ECU* Operator’s Station MWS Turret or Pod 8

9 Future System Architecture-1
Sensor manufacturer hardware/software Platform/integrator hardware/software Part of Aircraft Systems (Multifunction Displays) Aircraft ECU ECU* Operator’s Station MWS Turret or Pod 9

10 Future System Architecture-2
Sensor manufacturer “A” hardware/software Processor manufacturer hardware/software Sensor manufacturer “B” hardware/software Sensor manufacturer “C” hardware/software Platform/integrator hardware/software Part of Aircraft Systems (Distributed Processing) Platform or Integrator Software Part of Aircraft Systems (Multifunction Displays) MWS + LWS HFI Aircraft ECU ECU Operator’s Station Sensor Manufacturer Software Sensor Manufacturer Software Turret or Pod 10

11 Interface Type Commonality
Notional Example Interface Types JSF P-8 V-22 H-53 STUAS NUCAS 1. Imagery Data (a). x,y, intensity/radiance (video/still imagery) (b). x, y, range (Imaging LADAR, Flash LADAR) (c). x, y, spectral (HSI, MSI) (d). Future sensor technology 2. Metadata 3. Command and control 4. Elec. Power 5. Thermal 6. Software 7. Software Tools 8. Mechancal A. Connectors B. Physical mounting

12 Interface Hierarchy System (Aircraft) System (Test)
System (Ground Station) Components Subsystems Modules System (Aircraft)

13 Interface Hierarchy Sensor Subsystems System (Aircraft) System (Test)
System (Ground Station) Components Subsystems Modules System (Aircraft)

14 What is the Value in Standardizing a Specific Sensor/Platform Interface ?
Value Elements Importance bad good 1. Improve value to warfighter (better, faster, more) 2. Reduce cost of future upgrades (acquisition, integration) 3. Improved flexibility (missions, modularity, configuration) 4. Improved interoperability within aircraft avionics 5. Improved interoperability within system of systems 6. Simplify acquisition process 7. Reduce life-cycle maintenance costs 8. Reduce obsolescence (affordable upgrades, more often) 9. Reduce integration risks 10. Reduce training costs 11. Increase software and hardware reuse 12. Minimize proprietary software/hardware/interfaces

15 Tools That Might Help Increase Value
Technical Impact Business 1. Designate key Interfaces 2. Encourage competition and collaboration 3. Modular Open System Approach 4. Modular design and design disclosure 5. Open Architecture 6. Open interface standards 7. 8. 9. 10.

16 FACILITATE DISCUSSIONS
SLIDES TO FACILITATE DISCUSSIONS

17 System of Systems View Aircraft / Sensor Interface Air Vehicle Manned or unmanned Sensor Command & Control / Imagery & meta-data Information Grid Aircraft / Outside World Interface Data Link AV Command & Control Our task does not explicitly include interfaces to the rest of the world, however, we can utilize some of those interface standards and approaches in doing our standardization effort. i.e. why re-invent the wheel. Also, this would make it easier for the platform systems integrators to do their work and will promote interoperability. 17

18 Data: Sensors and Command & Control Details
(Notional) A/C skin Gimbal Status Data: Azimuth, Elevation, temperature, etc. Data Out: Imagery, Meta-data, Range, etc. Sensors Control IR Sensor(s) EO Sensor(s) INS Sensors LRF Position Sensors Zoom/Focus Motors Gimbal Motors Other Other Gimbal/Turret Sensor commands: zoom, focus, shutter, speed, gain, ping (range), etc. Gimbal Commands: Slew, tilt, etc.

19 Systems & Systems Integration Division
SPIES Organizational Relationships AIR 4.5 NGA EW Systems Comm. Systems NIAT Radar Systems Global Partners GWG Focus Groups Air Force Army Coast Guard NGA Other Other C O N T R A S SPIES EO-IR Sensors Interface Standards Overview Committee GWG MDR Strategic Partners DISA ITSC NAVSEA OPNAV NAVAIR (PEOs) NAVAIR (PMAs) Other DISR SAE From the Solar-system level, focusing in on the SPIES globe: GWG Geospatial Intelligence Standards Working Group NGA National Geospatial Intelligence Agency NITFS National Imagery Transmission Format Standard SAE Aerospace Council AIR Chair AIR Co-Chair AIR Sec GWG FG Rep SAE Rep S&T Rep (NRL, ??) AIR 5.0 (T&E ) rep AS-1 Aircraft Systems & Systems Integration Division Sub-committees


Download ppt "SPIES (Sensor/Platform Interface and Engineering Standards)"

Similar presentations


Ads by Google