ACR X HAD LTSS FROM ACR Y. SYS ERROR.

Narrative

ACR X SAN DEP AS PER LETTER OF AGREEMENT WAS ASSIGNED HDG 020 FROM SECTOR 9 WITH SECTOR 40 CTL FOR TURNS. PROC AND PRACTICE IS SECTOR 40 POINTOUT TO SECTOR 31 FOR CLB. SECTOR 31 REFED POINTOUT WITH ACR X ARR TO LAX FROM MEXICAN AIRSPACE VIA JLI2 ARR DSNDING TO FL240. I RECOORDINATED ASKING FOR AT LEAST FL240 TO PUT ACR X INTO HIGH ALT STRUCTURE. SECTOR 31 CTLR COUNTERED WITH FL250 APPROVED AND HIGHER REF ACR Y WENT CLR. ACR X CHKED ON FREQ DATA BLOCK ON ACR Y STILL REFLECTED DSND TO FL240; SO IN TURN I WAITED UNTIL DATA BLOCK OF ACR Y WAS UPDATED TO SHOW WHAT HAD BEEN COORDINATED. ONCE ASA'S DATA BLOCK SHOWED FL260; I THEN CLBED ARR X TO FL250. CONFLICT ALERT FLASHED; ALL DATA BLOCKS REFLECTED WHAT WAS COORDINATED. A LOSS OF MODE C OCCURRED; WHEN DATA BLOCK MODE C RETURNED ACR X SHOWED FL250 ACR Y SHOWED FL247 DSNDING; TARGETS HAD PASSED AND WAS 3 MI. I WAS INFORMED FIRST THAT IT WAS A PLTDEV; THEN LATER THAT THE R31 CTLR HAD MARKED STRIPS SHOWING FL260 ENTERED INTO DATA BLOCK FL260 BUT HAD FAILED TO ISSUE ALT TO ACR Y. ADDITIONALLY OEP NEVER ACTIVATED NOR WAS THERE A TCASII ALERT EITHER. INITIALLY WAS RPTED AS AN OPERROR; BUT AFTER XCHKING WITH DARK THIS ERROR NEVER OCCURRED AND WAS BEING RECLASSIFIED WITH R.O. I DISAGREE; THERE WAS AN ERROR. SECTOR 31 CTLR NEEDED TO ISSUE ALT RESTRICTION TO ACR Y. 80 PERCENT OF ACFT THAT DEPART SAN ON THIS DEP SHOULD BE HANDED OFF TO SECTOR 31 TO ELIMINATE THE POINTOUT. WHY DID OEP NEVER GO OFF? SO FAR AS OEP PROGRAM IS CONCERNED IT IS IN SERIOUS NEED OF BEING REEVALUATED. MANY TIMES IT WILL NOT ACTIVATE; ALSO WITH THE CHANGING OF LEADER LINES YOU CAN PREVENT OEP FROM ACTIVATING. THIS PRACTICE I HAVE SEEN OVER AND OVER AGAIN WITH SUPERVISION STANDING BEHIND AND OBSERVING THIS COVER UP.