Spacecraft on-board autonomy is becoming more and more prevalent and On-Board Control Procedures (OBCPs) have had a significant place in this process for many years. This lead to an enforced embedding of the OBCP management process into the overall space system engineering process and an additional categorization in so called On-board Operations Procedures (OBOP) and so called Onboard Application Programs (OPAP). This approach principally extends the perimeter of OBCPs, but clarifies the position of the OBCP's in between ground based operations procedures and on-board software. Despite that "OBCP" remains the widely used term but the nature and complexity of the OBCP execution environments as well as of the procedures itself differ considerably between missions. Some OBCP are deliberately simple and limited in scope; others rely on a high level programming language and are actually compiled or interpreted programs. Unfortunately, simplicity does not necessarily imply readability! This paper will report on experiences with various types of OBCPs and will explain the decisions that have been made to provide an appropriate development environment for them.