IBM Smart Vision Suite 4.0 Plan Update

1. IBM Smart Vision Suite 4.0 Plan Update April 11th, 2012 IBM Confidential

2. SVS Analytic 4.0 Major Scopes • Near-Field People Search (Including Facial Recognition) • Mid-Field People Search • Detection Enhanced Tracking • Railway Monitoring • Mid-Field Vehicle Search • License Plate Recognition (Device/Elsag) • Abandoned Object Detection

3. Near Field People Search • Provide single attribute and combined attribute search capability on people features: Baldness, Eyeglasses, Sunglasses, Head Color, Skin Tone, and texture and multiple-color search on torso clothing area with 13 color selection • Provide additional user interface to rank ordering search results based on attribute(s) confidence • Provide user interface to display confidence values of attributes of a search result • Potentially provide user interface to weigh the prominence of attributes • Provide complementary capability integration with Facial Recognition Engine for real-time identity alerting • Provide a People Search Framework to add new person attribute • Provide Color Calibration Tool to manually calibration color using artificial object colors and existing scene objects or automatically correcting colors

4. Targeted Cameras Requirements: Near-frontal faces with at least 30x30 pixels and +/- 15 degrees

5. Mid-Field People Search • Provide capability to detect and track people in a very crowded environment • Provide multiple-color search capability on upper and lower body areas with 13 clothing color selection for a people • Provide search capability to measure actual person height and moving speed • Provide Color Calibration Tool to manually calibrate color using artificial object colors and existing scene objects or automatically correcting colors if desired • Provide World Metric Calibration tool to manually calibrate real world metric using artificial objects and existing scene objects • Provide Size-map Calibration tool to automatically learn pedestrian size distribution in a scene and perform manual adjustment if needed (improve CPU performance and analytics accuracy)

6. Targeted Cameras Requirements: Both upper and lower body visible with minimal person resolution:12x26 pixels

7. Detection Enhanced Tracking • Provide better alerting and searching capability through improving detection and tracking of pedestrians and vehicles within periods of crowded activity • Provide search capability for actual person height and moving speed, and actual vehicle width/height, and speed • Provide Color Calibration Tool to manually calibrate color using artificial object colors and existing scene objects or automatically correcting colors if desired • Provide World Metric Calibration tool to manually calibrate real world metric using artificial objects and existing scene objects • Provide Size-map and Pose-map Calibration tool to automatically learn pedestrian size and vehicle size and pose distribution in a scene and perform manual adjustment if needed (improve CPU performance and analytic accuracy) • Provide better object recognition based on detection results

8. Targeted Cameras Requirements: Pedestrian Resolution:12x26 pixels; Vehicle Resolution: width 30 pixels

9. Railway Monitoring • Provide Real-Time alerting for Rail Crossing • Provide Real-Time alerting for Tunnel Entering • Provide Real-Time alerting for Level Crossing Blocking • Provide Real-Time alerting for Person Nearing Edges of Platform • Provide Real-Time alerting for Object (like People) Falling onto tracks • Provide Real-Time alerting for live crowd level detection • Provide real-time alerting for abandoned objects on platform, stations, and tracks • Provide real-time alerting for moving object presence after hours

10. Targeted Cameras

11. Mid-Field Vehicle Search • Provide better alerting and searching capability through improving detection of vehicles within periods of crowded activity • Provide search capability for actual vehicle width/height and speed • Provide Color Calibration Tool to manually calibrate color using artificial object colors and existing scene objects or automatically correcting colors if desired • Provide World Metric Calibration tool to manually calibrate real world metric using artificial objects and existing scene objects • Provide Size-map and Pose-map Calibration tool to automatically learn vehicle size and pose distribution in a scene and perform manual adjustment if needed (improve CPU performance and analytic accuracy)

12. Targeted Cameras Requirements: Vehicle min Resolution: width 30 pixels

13. Improving Abandoned Object Detection Rate (focusing on solving key causes of failures)

14. MILS V4.0 – Supporting the new V4.0 Analytics • The changes necessary to MILS are significant. The user interface, the java server side framework, and data model are all impacted. • The required volume, performance and functionality testing will also be considerable. • In order to provide support for the new 4.0 metadata being produced by the SSE, major underlying framework and data model changes are necessary. • The new attribute and color metadata force significant changes in MILS processing. • These changes are necessary primarily to reduce scarcity and to insure performance • The new 4.0 metadata formats also force a re-design of the MILS User UI. • The current User UI is tightly bound to the V3.x metadata format. It was never designed to handle heterogeneous metadata formats. • Realize they’ll be a much greater customer focus on the User UI and event search given the new 4.0 analytics • Note: The existing MILS admin UI will not be ported to the new UI framework do to time constraints.

15. IBM Security Services 2012 – MILS 4.0 (Framework modifications) In order to support the new SVS 4.0 competitive analytic features, significant changes to the backend MILS framework are required. These changes are required to productize and integrate the advancements made in analytic capabilities brought about by 2011/2012 research investments. • The current MILS framework doesn’t support parent-child relationships. New 4.0 metadata such as multi-color support and multi-attribute detection require this support. • Significant changes to framework and underlying DB model are needed to implement this change • Benefits include less scarcity, critical given SVS data volumes (TB’s not MB’s), and better overall system performance • Overstuffed/Overloaded definition of existing content types • Existing content type serves multiple purposes and serves the wrong purpose at the same time. • Inefficient creation/definition of database indexes - hefty price for storage/performance.

16. IBM Security Services 2012 – MILS 4.0 (UI modifications) • Currently the MILS UI cannot respond to new vertical specific, or analytic specific, content types (from search or data rendition perspectives). • UI-Driver XML lacking vocabulary to drive configuration. • MILS UI code too “static” and hard-coded. It recognizes only 2 content types. • As a result, efforts like the Retail UI are required. • Going forward, all registered CTD’s will be rendered and be searchable from the UI. • The current MILS UI is very difficult to make ‘international-ized’ (I18N) • Hardcoded references, graphical content, no use of resource bundles • Going forward, NLS will be ‘designed-in’ from the start, the new 4.0 User UI will be internationalized. • The new UI framework will be better positioned to be utilized in a 3rd party interface, such as the IOC by leveraging strategic user interface SDKs and alignment with emerging IBM design standards. The plan is to re-write the User UI portion (not the Admin UI) of the user interface. The new User UI will support the new metadata formats, be internationalized, replace the existing Federation UI, and be designed to operate in 3rd party presentation layers.

17. MILS V4.0 – The MILS UI, more details… • Extensibility – The support of heterogeneous metadata formats • Required given the uniqueness of the 4.0 analytic profiles • Enables any defined content type (ie., badge reader, LPR) to be rendered and searched within the default UI (this is not possible today) • I18N – Designing for this now is critical… • The new User UI portion of the MILS UI will be internationalized. • 4.0 Roles – Designing for this now is critical… • Current UI – supports two ‘roles’, Admin (only pvadmin!) and User • 4.0 UI – Surveillance, forensics, adjudicator, alert admin, admin (future) • These are being designed and will be reviewed • Mockups – This is the next deliverable in the 4.0 UI design phase • Role experiences • Search complexities • NYPD • Note on the existing Admin UI • This role will be formally added to the new UI in a subsequent release • But we’ll be making small improvements to the existing interface. • Both Rick and Cathee have given input, these need to be prioritized

19. Release 4.0 - Code and Testing Impacts • The release 4.0 backend work is more significant than expected. The core DB model, framework and UI are all impacted**. • Additional volume and performance work is necessary to insure query response times meet expectation • Need to evaluate the uptick in metadata traffic do to new detection based algorythms • Need to ensure volume-metrics do not cause issue with current production hardware, both SAN storage. • The frontend analytic changes are significant • The new algorithms will undergo a lengthy accuracy testing period • Given the new algorithms, additional resiliency/long-run testing is necessary. • Performance testing will also be done to measure the uptick in CPU utilization. ** We have looked into minimizing these impacts, but given the new types of video metadata, these changes are necessary.

20. Backup

21. Status Of Abandoned Object Detection

22. Key Remaining Tasks for Production 4.0 and 4.1 Releases • Function and Code Complete • Usability Evaluation • Remaining Analytics Component Integration • Integration with MILS • Quantitative Accuracy Evaluation • Reliability • Scalability and Performance Optimization • Beta Testing at Key Customer Sites (NYPD) • Packaging • Quality Assurance • Documentation • Close the Research and Release Planning for 2012

23. Status on other NYPD tasks, outside the Release 4.0 Scope • SCOM integration • Agreement with SCOM tech-team on Linux interface • SVS code changes near complete • Need to firm up deployment plan with customer and SCOM team • Virtualization analysis • Delivered spec’s for a test environment to the TSS team. • There are complications with IBM middleware and MS Hyper-V, workarounds are being discussed. We have also contacted IBM SWG. • Reviewed production SSE performance logs. Recommend holding off on production SSE virtualization until 4.0 performance metrics are obtained. • Genetec Security Center • Currently working with Genetec to understand the interface changes in this new release. These look to be significant. We’ll work with Genetecand the customer to plan any req’d development changes. • Scalable Analytics Deployment Process (including Camera and View Categorization) • Deployment Certification • Weekly FP and FN Analysis and Resolution