B737-700 REPORTS RECEIVING DATA-LINK MAINTENANCE TESTING REQUESTS GENERATED BY ACFT SOFTWARE ABOUT WHICH MAINTENANCE WAS UNAWARE. POST EVENT DOCUMENTATION WAS NECESSARY TO PAIR THE PERFORMANCE WITH A VALID REQUEST.

Narrative

AT TOP OF DSCNT; WE RECEIVED AN ACARS MESSAGE 'PLEASE PERFORM AUTOLAND ON NEXT OCCASION.' DURING REVIEW OF THE LOGBOOK EARLIER; IT WAS NOTED THAT AN AUTOLAND HAD BEEN PERFORMED ON A RECENT FLT AND THAT THE ACFT HAD RECENTLY RETURNED FROM 'C' CHK OUT OF THE COUNTRY. DISPATCH RELEASE NOTED CAT I STATUS BUT WX AND CONDITIONS IN ZZZ ALLOWED FOR US TO PERFORM THE AUTOLAND PER GUIDANCE IN THE FIELD AND FACILITIES NOTICES OF THE FLT PAPERWORK. WE PERFORMED A SATISFACTORY AUTOLAND AND DOCUMENTED THE RESULTS IN THE LOGBOOK. DURING OUR TURNAROUND I WAS NOTIFIED BY THE AVIONICS LEAD THAT CERTAIN MAINT CHKS HAD NOT YET BEEN COMPLETED AND THAT MAINT DID NOT YET DESIRE AUTOLAND PERFORMANCE CHKS. FURTHER INQUIRY TO DISPATCH/MAINT CTL REVEALED THAT NO HUMAN WAS MAKING THESE REQUESTS AND THAT A COMPUTER ON THE AIRPLANE WAS THE SOURCE OF THE REQUEST. THE AVIONICS LEAD SAID THAT HE WOULD ENTER THE AUTOLAND DATA AND THAT WOULD SOLVE THE PROB. ON THE NEXT LEG WE RECEIVED THE EXACT SAME REQUEST JUST AT THE TOP OF DSCNT. PLTS COULD CALL DISPATCH VIA RADIO TO CONFIRM/VERIFY THAT REQUESTS VIA ACARS WERE ACTUALLY VALID.