•Solve problem of integrating other control systems•Solve problem of extending our control system•Minimize the latency for data•Minimize the implementation mapping•Make it look acceptable to native support•Create an achievable growth path

DDD(Database Distributed DAS)

UMBRELLA

• Tiered Data Base • Top Tier • IRMIS++• Facilitates

– Protocol Type– Name extension– Data structure description– Global facilities - bypass, save/restore, alarms– Hardware Description– Hierarchial Devices

DCDCDatabase Centric Distributed Controls

D3

• Second Tier DBACNET DBEnforced EPICS DBDOOCS DBCORBA SCADA

Interface Extensions

• Classes to provide Protocol Interface• Classes to provide Protocol dependent

displays• Support Multiple Display GUIs

– EDM– CLIB– LABVIEW– JAVA– MATLAB

Cons

• Heavy Client• 3 Front Implementation

– DB– DAS Interface– Display Interface

• Potentially many protocols• Requires an alarm server• No automatic support for FTP/SNP• Acquisition on client FTD (events, etc.)

Pros• Native DAS• Reduce Latency• Extensible to other Protocols• Isolates Native Data Base• Transparent Client UTI • Global DB• Extends Native Protocols including ACNET• Works for all IOCs: embedded, soft,

open(JavaIOC,vxWorks)• Implement once for EPICS

Steps

• Create a team• Implement at FNAL for FNAL• Receive Approval as an Umbrella for all

Control Systems• Integration for NML/HINS• Utilize a “free” DB• Start with IRMIS relationships• Implement Protocol-based Interface Classes