Engineering topics
Jacobson, J.
Publications and source records attributed to Jacobson, J..
Feedstock and Conversion Supply System Design and Analysis
The success of the earlier logistic pathway designs (Biochemical and Thermochemical) from a feedstock perspective was that it demonstrated that through proper equipment selection and best management practices, conventional supply systems (referred to in this report as “conventional designs,” or specifically the 2012 Conventional Design) can be successfully implemented to address dry matter loss, quality issues, and enable feedstock cost reductions that help to reduce feedstock risk of variable supply and quality and enable industry to commercialize biomass feedstock supply chains. The caveat of this success is that conventional designs depend on high density, low-cost biomass with no disruption from incremental weather. In this respect, the success of conventional designs is tied to specific, highly productive regions such as the southeastern U.S. which has traditionally supported numerous pulp and paper industries or the Midwest U.S for corn stover.
Registered file support for critical operations files at SIRTF
Explore the source record for details and available documents.
Registered File Support for Critical Operations Files at (Space Infrared Telescope Facility) SIRTF
The SIRTF Science Center's (SSC) Science Operations System (SOS) has to contend with nearly one hundred critical operations files via comprehensive file management services. The management is accomplished via the registered file system (otherwise known as TFS) which manages these files in a registered file repository composed of a virtual file system accessible via a TFS server and a file registration database. The TFS server provides controlled, reliable, and secure file transfer and storage by registering all file transactions and meta-data in the file registration database. An API is provided for application programs to communicate with TFS servers and the repository. A command line client implementing this API has been developed as a client tool. This paper describes the architecture, current implementation, but more importantly, the evolution of these services based on evolving community use cases and emerging information system technology.