Abstract: A total of 42 registered attendees participated in a program that included 28 briefings of current research in distributed instrumentation. The objective of the workshop was to explore critical issues associated with instrumentation of distributed computing systems, with the goal of understanding more clearly where further research is needed. Position papers were solicited to address topics such as instrumentation requirements, instrumentation standards, real-time instrumentation, special hardware requirements, and data reduction and analysis tools. Section 2 of this paper summarizes my interpretation of the content of the formal briefings presented at the workshop. Section 3 summarizes some of the main conclusions from the workshop. Interested readers may contact workshop presenters directly for further details. The quality of an experimentation environment for a distributed testbed is primarily determined by fidelity, versatility, and usability. One of the major tasks that constitutes the process of experimentation is experiment specification. Another important factor is the user interface to the testbed. The Distributed Computer Testhed (DCT) at Honeywell includes a tool named Experiment Specification Language (ESL) that facilitates experiment description and setup. The ESL provides a uniform linguistic framework for the experimenter to specify events, actions and event-action mappings. Users interact with DCT through an interactive, single-point user interface. Experience with F-16 avionics evolution from pure analog processing to distributed stored program control demonstrates that functional testing and fault isolation have become much more difficult. To address these concerns a Distributed Processing Testing System (DPTS) is proposed. Prototype implementations of a High-Level Test Language (HLTL) and an Automated Test Specification Generator (ATSG) have been developed as part of DPTS. With HLTL it will be possible to specify all necessary system interface information in problem-oriented terms. Formal system requirements are used to generate HLTL test scripts that are translated by the HLTL processor for direct execution by a distributed system component.