Wikipedia
OAMP, traditionally OAM&P, stands for operations, administration, maintenance, and provisioning. The addition of 'T' in recent years stands for troubleshooting, and reflects its use in network operations environments. The term is used to describe the collection of disciplines generally, as well as whatever specific software package(s) or functionality a given company uses to track these things.
Though the term, and the concept, originated in the wired telephony world, the discipline (if not the term) has expanded to other spheres in which the same sorts of work are done, including cable television and many aspects of Internet service and network operation. 'Ethernet OAM' is another recent concept in which the terminology is used.
Operations encompass automatic monitoring of environment, detecting and determining faults and alerting admins. Administration typically involves collecting performance stats, accounting data for the purpose of billing, capacity planning using Usage data and maintaining system reliability. It can also involve maintaining the service databases which are used to determine periodic billing. Maintenance involves upgrades, fixes, new feature enablement, backup and restore and monitoring the media health. The major task is Diagnostics and troubleshooting. Provisioning is the setting up of the user accounts, devices and services.
Although they both target the same set of market, OAMP covers much more than the five specific areas targeted by FCAPS (See FCAPS for more details; it is a terminology that has been more popular than OAMP in non-telecom environs in the past). In NOC environments, OAMP and OAMPT are used to describe problem management life cycle more and more - and especially with the dawn of Carrier-Grade Ethernet, telco terminology is becoming more and more embedded in traditionally IP termed worlds.
O - Operations A - Administration M - Maintenance P - Provisioning T - Troubleshooting