Transcript M4 Alpha Release August 9 2006 th

M4 Alpha Release
August 9th 2006
M4 Alpha Release Modified Agenda
•
•
•
•
•
Review M4 Objectives, General Concepts and Design
Review M4 Development Schedule
Alpha Release Scope and Objectives
Demo M4 Alpha
Discuss High-Availability Platform Alternatives
February 8th, 2006
Project Objectives and Validation
Objectives
Validation
All data collected 100% valid.
Throughput analysis.
Data provided in ‘near-real’ time.
M4 Automated Upload features with
existing PTAGIS verification reports.
99.9% system uptime.
Significant alpha field test with
Marathon Platform.
Support B2CC and legacy readers.
PTAGIS lab testing.
Interface with PTAGIS systems.
M4 Committee approval of alpha/beta
release.
Ease of use.
““
Standard Platform
Test Plan and Virtual PC.
Meet or exceed current SxC efficiency. (next slide)…
February 8th, 2006
Separation-by-Code Performance Evaluation
To ensure that M4 ‘meets or exceeds’ the performance of Separation-byCode in MultiMon:
1. Measure the performance of MultiMon and compare with M4 in the same
laboratory conditions. This requires:
– Custom hardware and software to measure latency from transceiver to
gate over several iterations
– Custom software to emulate the activity of a large site with 40 or more
transceivers
2. Perform a live fish test with a production release candidate of M4.
3. Monitor existing PTAGIS efficiency reports when M4 is deployed to the field.
February 8th, 2006
M4 Performance Evaluation Design
Wheel
Readers
M4/MultiMon
PLC computes the delta in
milliseconds between these
two points over several
revolutions of the wheel.
PLC
February 8th, 2006
M4 Conceptual System Architecture
Physical Devices
Reader
Gate
Reader
PLC
Ethernet
Serial/Ethernet
System
Device.dll
Device
Commands
Messages
M4 Site Monitor
Service
Messages
SxC.dll
PTAGIS
Topology/Configuration
M4System.dll
Messages
SiteTopology
Message
Remotable
DataAccess
SQLExpress
Messages and
Topology
via
HTTP
Gateway SQL
Server
Data
Transformation
Services
IPC
Remoting
Messages
User Session
Toplogy
ServiceStatePublisher.dll
Int.
Files
M4 Topology
Manager
M4 Dashboard
PTTP/IDL
M4 SxC Manager
PTAGIS3
Ingres
Reports
February 8th, 2006
Exported
XML
Data
Export
Import
XML
Web Application
New Concepts: Data is Stored in a Database
DeviceMessage
MessageKey
TopologyKey
SiteCode
AntennaGroupID
DeviceID
AntennaID
Buffered
Message
MessageKey
MessageType
MessageKey
LocalTimeStamp
LineNumber
PSTTimeStamp
MessageText
Processed
MessageTypes
MessageType
MessageTypeDescription
February 8th, 2006
MessageText
New Concepts: Topology and Site Configuration
1. M4 Topology Manager creates and manages topology versions (site
configurations).
2. Only one topology version is active when M4 Site Monitor Service is
started.
3. M4 Dashboard allows user to designate a topology version as
“active”.
– User must restart M4 Site Monitor Service to change a topology
version.
– A topology version cannot be modified if it has been “activated” or
“expired”.
4. A topology version and the data collected during it’s “active” period
have a direct relationship.
5. A topology version must be “Registered with PTAGIS” before
associated data can be uploaded to PTAGIS.
February 8th, 2006
New Concepts: Flexible Topology
•
M4 provides a flexible topology to scale with current and future
PTAGIS interrogation sites.
•
M4 can monitor multiple sites from one computer.
Traditional Site
February 8th, 2006
Small-Stream Site
Dual Site
M4 Project Milestones
•
•
•
•
•
•
•
•
Draft of Project Plan and Functional Specification
Evaluation and Approval of high-availability platform
Develop and Approval of Performance Evaluation Criteria and Tools for Lab
Regression Testing
Development of M4 prototypes for evaluation and to drive functional
requirements.
Alpha release of M4 “Monitor Only” for performance evaluation.
Alpha release of M4 for performance evaluation and committee approval
Field test of M4 beta release
Field deployment of M4 production release candidate.
February 8th, 2006
Alpha Release Scope
•
Topology Manager Alpha
–
–
–
–
•
Create topology configuration for all basic components
Limited validation
Versioning w/ Activation
Associated with interrogation data
To do:
–
–
–
–
February 8th, 2006
Needs group input for any additional configuration settings
Integration with ALRS/ATS
Extended validation with physical devices w/ auto-discovery
Data management features (save as, export/import)
Alpha Release Scope
•
M4 SiteMonitor Alpha
–
–
–
–
–
–
•
Performs essential monitoring functionality (start/pause/stop)
Robust messaging
Collects and manages interrogation data from all device types
Integrates with basic SxC features with feedback
Error handling
Remote server communication
To Do:
– Perform scheduled activities (pulse, uploads, etc.)
– Complete writing of additional message types (diagnostics, SxC, GPS)
February 8th, 2006
Alpha Release Scope
•
M4 Dashboard Alpha
–
–
–
–
–
–
•
SiteMonitor controller and state publisher
Provides drill-down topology display of interrogation data (manual refresh)
Topology Version Display
Task icon notification
Remote device commands
Client remoting
To Do:
–
–
–
–
–
–
–
–
February 8th, 2006
Tighten display feature w/ advanced error reporting/notification
Reporting
Data management (import/export/purge/downloads/MobileMonitor)
Integrate Event Log and System Viewers
Custom remote commands
User interface for application settings
Manual upload (push)
PTAGIS integration (identify processed messages)
Alpha Release Scope
•
PTAGIS Gateway (IDL Interface) Alpha To Do:
–
–
–
–
–
–
February 8th, 2006
Procure SQL Server System
Create Push/Pull Data Transform Service w/ Scheduler
Provide Dashboard Interface w/ reporting
Provide DTS transform of topology data to PTAGIS3 site config.
Provide DTS/XSL file transform of message data to IDL data loader
Provide any reporting to PTAGIS web.
Alpha Release Objectives
•
•
•
•
Integration of all major system components w/ limited SxC and user
interface features
Initial Performance Evaluation
Drive additional feature requirements.
M4 Committee Approval of M4 Alpha Release.
February 8th, 2006