160 likes | 289 Views
Tool for Installation. How can we store in a unique repository all information related to Control hardware Installation. PUBLIC ETHERNET NETWORK. OPERATOR CONSOLES. FIXED DISPLAYS. OPERATOR CONSOLES. TCP/IP communication services. SCADA SERVERS. FILE SERVERS. APPLICATION SERVERS.
E N D
Tool for Installation How can we store in a unique repository all information related to Control hardware Installation
PUBLIC ETHERNET NETWORK OPERATOR CONSOLES FIXED DISPLAYS OPERATOR CONSOLES TCP/IP communication services SCADA SERVERS FILE SERVERS APPLICATION SERVERS CERN GIGABIT ETHERNET TECHNICAL NETWORK TCP/IP communication services TIMING GENERATION RT Lynx/OS VME Front Ends WORLDFIP Front Ends T T T T PLCs TCP/IP communication services T WorldFIP SEGMENT (1, 2.5 MBits/sec) T T T OPTICAL FIBERS T PROFIBUS FIP/IO T BEAM POSITION MONITORS, BEAM LOSS MONITORS, BEAM INTERLOCKS, RF SYSTEMS, ETC… QUENCH PROTECTION AGENTS, POWER CONVERTERS FUNCTIONS GENERATORS, … ACTUATORS AND SENSORS CRYOGENICS, VACUUM, ETC… LHC MACHINE LHC control system architecture
Then…..So • We need to have a unique tool to store this data • We propose to use the ABCAM Portal ( AB Controls Asset Management), because: • It is based on MTF as LHC standard Asset management system • It will use the Rack wizard for logical connections • It is based on ABCAM DB • Data will be shared with the LHC CO Controls DB • Data will be correlated with the following databases in order to avoid duplication of information: • TS-EL (Cablotheque) • IT-CS (Netops) • …
Control hardware Data model • The control hardware can be described by the following elements • It is constituted of “Systems” • Instantiation of a VME crate, PLC,… for a particular task in a precise location • Each “System” is made of “Components” • Hardware elements which are grouped together to build a system • Connections • Electrical connection arriving/leaving a component in a system • Electrical connection between two components in a system.
Systems • Attributes describing a system • Type • Name (conform to naming convention) • Location, Rack or electrical cabinet • Ethernet Host name • This information link ABCAM DB to IT_CS DB • Powering origin • This information link ABCAM DB to TS_EL DB
Components • Crates hardware, CPU, I/O board, Timing cards, repeaters,… • Attributes describing the component nature • Type (according to AB-CO equipment type) • Names • Barcode, CO Code, MTF Code • Serial number • Firmware type & version • DL Number (option) • … • Attributes describing the component status • Status (installed, on repair, in stores, Other) • State (working, faulty, unrepairable) • Associated “System” if installed • Location, rack/electrical cabinet if different from “system” ones • …
Connections • Attributes Describing a connections • name of the Cable connected to it : • TS EL Name : name Coming for the “cablotheque” of TS EL if it is acble they hev installed this name may not exist for local cables ( cable installed by us in a rack for instance) • AB_CO for local Cables • System : the name of the system holding the connection • Slot : the name of the slot of the system holding the connection • Connector type • Status (connected; not connected) • Comment • …
ABCAM delivery • DB structure using the proper DB tables ( MTF, ABCAM, rack wizard,…) • Almost ready. still some decision to be taken for connection. • Forms to create/update component & systems Connections • Reports to extract information based on location, systems, components etc • Excel spreadsheet templates to upload large amount of data • Viewing of rack layout by rack wizard
ABCAM Planning • Consolidation of DB structure to be implemented before end of the year. • Tools to import data from EXCEL files OR DB to be created by AB-CO DM for january • First prototype ready for the end of this year • ABCAM Portal V1 Operational in production end of January
Acknowledgements • Thanks to : • Zory Zaharieva • Michel Bornand • Josi Schinzel • Ronny Billen