Charge for the L1cal Technical Readiness Review

-----------------------------------------------



    All of the individual boards which make up the upgrade of the

L1Cal have been shown to work on the test bench and meet their

design specifications. The purpose of this review is to verify that

all of the parts work in concert as a system so that there are no

reservations about installing the system from the technical point of

view. The scope of this review includes the online software as well

as the hardware.



Particular points which should be covered include:



- Communication paths

    -Have the transmission of data and control signals been verified

across all of the relevant communication paths (BLS/ADF,ADF/TAB,

TAB/GAB, TAB-GAB/L2-L3, GAB/TFW, SCL/L1cal, ...). Are the bit error

rates low enough for long-term operation? Have new cables been

tested?

    - Has the connection to the Cal Track Match system been tested?



- Timing

    - Are there demonstrated procedures for properly adjusting the

    timing of each element of the system?

    - Is the overall latency understood and within specifications?



- System scaling:

    -Has it been demonstrated that multiple ADF's in a crate (a

full crate, ideally) operate without interference?

    -Has it shown that multiple TABs operate without interference when

    all of their inputs and outputs are used?

    - Has it been shown that multiple TABs in a crate (a full crate,

    ideally) communicate with the GAB without interference?

    - Is the measured power consumption compatible with specification?



- Parallel readout tests:  The sidewalk system can be read out through

the standard DZero data path in coincidence the entire DZero detector.

>From these data, have the following been demonstrated:

    - acceptable TT noise performance

    - ability to read pulser data

    - mechanism for calibrating TT's against precision readout



- Software tools: Has software (expert tools, at least) been written

and exercised which

    - download the hardware

    - verifies the download

    - monitors the operation for errors

    - compares hardware output with emulation

    - unpacks the L1cal data which is written to the raw data chunk

    - archives/tracks history of installed firmware

    - monitors the system online

    - interfaces with COOR for configuration



- Documentation: Is there adequate documentation for

    - configuring and initializing the system

    - interpreting errors flagged by the monitoring utilities

    - specifying the data formats

    - documentation for each piece of hardware in the system



- Installation plans:



    - have all the required safety approvals for installation been

obtained, or are in the works?

    - is the installation infrastructure planned out, for example

power, real estate, cabling, etc.?

    - what is the installation plan and who is going to do it?

    - is a method in place for identifying bad BLS trigger outputs so

    that they can be fixed during the shutdown?



- Maintenance: While this will be reviewed as part of the

collaboration review, we would appreciate hearing about the following:

    - how are boards going to be repaired in the long run? Are there

adequate spares and test stands?

    - is it conceivable that changes might be required to hardware

and/or firmware after installation and technical commissioning? How

will the facilities and expertise for making these changes be

available?