T. Le Flour

1

• Brick
• Manipulation
• Management

2
Outline

• Main software characteristics
• General Architecture
• Communication
• Development status
• Milestones
• Demonstration

3
Main software characteristics

• Wide distribution of the software components
• Graphical User Interface (GUI) , Databases, ...
• BMM only manipulates its database
• BMM should react when new data are available
• BMM should have the possibility to notify
  external systems
• If Possible
• External components will access BMMs data
  through service calls.
• Based on CORBA standard
• Inter-operable (Soft and Hard.)
• Implementation OMNIORB4.X

4
BMM A Three Tiers architecture

• Distributed, Reactive and Secured System

BMS Server
Data Tiers
Client Tiers
A P I
DAQ Manager
Client
A P I
Business Tiers
BMM
Central Repository
Local Repository
OCCI
BMM Server
Oracle
Oracle
A P I
Operator Work Station
Data Monitoring
5
BMM Communication Scenario
Event Service
Naming Service
Programmable Logical Controler
LINUX
Window
Platform independent
6
Development Status(1)

• Initial Loading Mechanism
• Full specification of the initial loading phase
• Software component map (Description
  Relationships)
• Prototype
• Some specific software components under
  development
• Configuration Manager
• Description of the BMM environment
• CORBA services
• Name Service , Event Service,
• BMM Clients
• BMM as client
• Message description
• Detector configuration
• Initial loading
• Row inhibition
• Setup Manager
• Depending on the configuration, controls the
  availability of the software components.

7
Development Status(2)
General View
8
Development Status(2)
Servers description
9
Development Status(2)
Event Channel description (Client Server Side)
10
Development Status(3)

• Logbook Manager
• Goals
• Tracking and saving events coming from external
  systems
• Based on the configuration database
• Provide a way of accessing the event history per
  sub-systems,
• A tool for debugging and controlling
• I.e. BMS
• Debugging automate operations
• Maintenance
• Remark such a tool can be used in a more
  general context
• Configuration
• Only one master responsible for the message
  saving
• The message saving should be configured to
  authorize or not the message saving
• Several slave logbook managers could be launched
• Each logbook manager is individually configurable
• To subscribe/unsubscribe to the event channels

11
Logbook Manager Behavior
Event Service
Name Service
Messages DB
Configuration DB
12
Milestones

• Prototype ready
• Communication process fully tested (GUI ? BMM ?
  BMS)
• Initial loading
• Based mainly on simulated components from the PLC
  side.
• From now to Autumn 2004
• Integration on the BMS side of all the new
  automate objects.
• Integration checked with the full implementation
  and the manipulator
• From now to end of 2004
• BMM Software Analysis
• Extraction scenarios under study
• Extraction prototype ready for end of 2004
• Relation with the others external sub-systems
• Discussions will take place during this period.
  (I.e. Cosmic Bench, Dev. Lab, Storage Area, )

13
Demonstration Initial Loading

• CORBA Services
• GUI ? BMM Load(SM,Side)
• BMM ? BMS
• Load_Bricks(SM, side) From loading basket to
  Carousel(20 )
• Insert_Bricks(SM, Wall, Row) From carousel
  into the wall(20 )
• Events on the Event Service
• Brick and CS Bar Codes
• Insertion phase starting

Local Repository
BMS
BMM
BMM Corba Server
A P I
BMS Corba Server
Oracle
Event service
For data output
14
DemonstrationInitial Loading - Setup
LAPP Setup
LINUX CC Lyon
Windows2000 LAPP
LINUX/VMWare LAPP
Windows2000 LAPP
GUI (Java)
Event Service
Name Service
BMS
Oracle
BMM
LabView Simul.
Data Saving
Demonstration Setup
LINUX VMWare
Windows2000
GUI (Java)
Event Service
Name Service
Data Saving
BMS
BMM
Oracle
Windows 2000