Starting in the summer of 2007 the LAT configurations will be managed and tracked by the MOOT system which is documented elsewhere [3]. People working in the science operations aspect of the ISOC may need to understand the tools that exist to modify or make new configurations for the LAT. In this document we will describe only one part of the process of making LAT configurations: expressing the intent of the configuration and using the available tools to build LATC_XML and LCI_XML files and store those files in MOOT. From the point of view of science operations, LATC_XML and LCI_XML are the products delivered to flight operations to define the LAT configuration during LPA and LCI data taking. In fact, the MOOT system uses flight software tools to build the LATC_XML and LCI_XML into binary files which are managed by the flight-software file management system. All these processes are hidden from the point of view of data analysts and MOOT is the point of contact to get information about the LAT configuration.
First, in sec. 2 we will describe the context that ConfigSystem operate in and detail the functionality it must provide. The next two sections and will give overviews on the inputs (sec. 3) to and output products (sec. 4) of ConfigSystem. Then, in sec. 5 will provide extensive details about LPA configuration and in sec. 6 will do the same for LCI scripts. We will cover command line interfaces in sec. 7, graphical user interfaces in sec. 8 and give some examples in sec. 9. Finally, in the appendices we will provide complete syntax for all the input files types.