Integrated Resource Supply-Demand-Routing
Abstract not provided.
Abstract not provided.
Abstract not provided.
In March and April of 2020 there was widespread concern about availability of medical resources required to treat Covid-19 patients who become seriously ill. A simulation model of supply management was developed to aid understanding of how to best manage available supplies and channel new production. Forecasted demands for critical therapeutic resources have tremendous uncertainty, largely due to uncertainties about the number and timing of patient arrivals. It is therefore essential to evaluate any process for managing supplies in view of this uncertainty. To support such evaluations, we developed a modeling framework that would allow an integrated assessment in the context of uncertainty quantification. At the time of writing there has been no need to execute this framework because adaptations of the medical system have been able to respond effectively to the outbreak. This report documents the framework and its implemented components should need later arise for its application.
Abstract not provided.
As part of the Department of Energy response to the novel coronavirus disease (COVID-19) pandemic of 2020, a modeling effort was sponsored by the DOE Office of Science. Through this effort, an integrated planning framework was developed whose capabilities were demonstrated with the combination of a treatment resource demand model and an optimization model for routing supplies. This report documents this framework and models, and an application involving ventilator demands and supplies in the continental United States. The goal of this application is to test the feasibility of implementing nationwide ventilator sharing in response to the COVID-19 crisis. Multiple scenarios were run using different combinations of forecasted and observed patient streams, and it is demonstrated that using a "worst-case forecast for planning may be preferable to best mitigate supply-demand risks in an uncertain future. There is also a brief discussion of model uncertainty and its implications for the results.
Sandia National Laboratories is part of the government test and evaluation team for the Defense Advanced Research Projects Agency Collection and Monitoring via Planning for Active Situational Scenarios program. The program is designed to better understand competition in the area between peace and conventional conflict when adversary actions are subtle and difficult to detect. For the purposes of test and evaluation, Sandia conducted a range of activities for the program: creation of the Grey Zone Test Range; design of the data stream for a user experiment conducted with U.S. Indo-Pacific Command; design, implementation, and execution of the formal evaluation; and analysis and summary of the evaluation results. This report details Sandia's activities and provides additional information on the Grey Zone Test Range urban simulation environment developed to evaluate the performer technologies.
Abstract not provided.
Abstract not provided.
Abstract not provided.
Abstract not provided.
This document provides implementation guidance for implementing personnel group FTE costs by JCA Tier 1 or 2 categories in the Contingency Contractor Optimization Tool – Engineering Prototype (CCOT-P). CCOT-P currently only allows FTE costs by personnel group to differ by mission. Changes will need to be made to the user interface inputs pages and the database
Abstract not provided.
This document provides background and instructions for developing and building the Contingency Contractor Optimization Tool - Prototype (CCOT-P) application.
Sandia National Laboratories (Sandia) is in Phase 3 Sustainment of development of a prototype tool, currently referred to as the Contingency Contractor Optimization Tool - Prototype (CCOTP), under the direction of OSD Program Support. CCOT-P is intended to help provide senior Department of Defense (DoD) leaders with comprehensive insight into the global availability, readiness and capabilities of the Total Force Mix. The CCOT-P will allow senior decision makers to quickly and accurately assess the impacts, risks and mitigating strategies for proposed changes to force/capabilities assignments, apportionments and allocations options, focusing specifically on contingency contractor planning. During Phase 2 of the program, conducted during fiscal year 2012, Sandia developed an electronic storyboard prototype of the Contingency Contractor Optimization Tool that can be used for communication with senior decision makers and other Operational Contract Support (OCS) stakeholders. Phase 3 used feedback from demonstrations of the electronic storyboard prototype to develop an engineering prototype for planners to evaluate. Sandia worked with the DoD and Joint Chiefs of Staff strategic planning community to get feedback and input to ensure that the engineering prototype was developed to closely align with future planning needs. The intended deployment environment was also a key consideration as this prototype was developed. Initial release of the engineering prototype was done on servers at Sandia in the middle of Phase 3. In 2013, the tool was installed on a production pilot server managed by the OUSD(AT&L) eBusiness Center. The purpose of this document is to specify the CCOT-P engineering prototype platform requirements as of May 2016. Sandia developed the CCOT-P engineering prototype using common technologies to minimize the likelihood of deployment issues. CCOT-P engineering prototype was architected and designed to be as independent as possible of the major deployment components such as the server hardware, the server operating system, the database, and the web server. This document describes the platform requirements, the architecture, and the implementation details of the CCOT-P engineering prototype.
The Contingency Contractor Optimization Tool – Prototype (CCOT-P) database is used to store input and output data for the linear program model described in [1]. The database allows queries to retrieve this data and updating and inserting new input data.
This document describes the final software design of the Contingency Contractor Optimization Tool - Prototype. Its purpose is to provide the overall architecture of the software and the logic behind this architecture. Documentation for the individual classes is provided in the application Javadoc. The Contingency Contractor Optimization project is intended to address Department of Defense mandates by delivering a centralized strategic planning tool that allows senior decision makers to quickly and accurately assess the impacts, risks, and mitigation strategies associated with utilizing contract support. The Contingency Contractor Optimization Tool - Prototype was developed in Phase 3 of the OSD ATL Contingency Contractor Optimization project to support strategic planning for contingency contractors. The planning tool uses a model to optimize the Total Force mix by minimizing the combined total costs for selected mission scenarios. The model optimizes the match of personnel types (military, DoD civilian, and contractors) and capabilities to meet mission requirements as effectively as possible, based on risk, cost, and other requirements.
The Contingency Contractor Optimization Tool - Prototype (CCOT-P) requires several third-party software packages. These are documented below for each of the CCOT-P elements: client, web server, database server, solver, web application and polling application.
This requirements document serves as an addendum to the Contingency Contractor Optimization Phase 2, Requirements Document [1] and Phase 3 Requirements Document [2]. The Phase 2 Requirements document focused on the high-level requirements for the tool. The Phase 3 Requirements document provided more detailed requirements to which the engineering prototype was built in Phase 3. This document will provide detailed requirements for features and enhancements being added to the production pilot in the Phase 3 Sustainment.
The reports and test plans contained within this document serve as supporting materials to the activities listed within the “Contingency Contractor Optimization Tool – Prototype (CCOT-P) Verification & Validation Plan” [1]. The activities included test development, testing, peer reviews, and expert reviews. The engineering prototype reviews were done for both the software and the mathematical model used in CCOT-P. Section 2 includes the peer and expert review reports, which summarize the findings from each of the reviews and document the resolution of any issues. Section 3 details the test plans that were followed for functional testing of the application through the interface. Section 4 describes the unit tests that were run on the code.
This document provides training examples to provide users practice in using the tool. Detailed instructions on how to use the tool can be found in the User Manual (SAND2015-6028).The Contingency Contractor Optimization project is intended to address former Secretary Gates’ mandate in a January 2011 memo and DoDI 3020.41 by delivering a centralized strategic planning tool that allows senior decision makers to quickly and accurately assess the impacts, risks, and mitigation strategies associated with utilizing contract support. Based on an electronic storyboard prototype developed in Phase 2, the CCOT-P engineering prototype was refined in Phase 3 of the OSD ATL Contingency Contractor Optimization project to support strategic planning for contingency contractors. CCOT-P uses a model to optimize the total workforce mix by minimizing the combined total costs for the selected mission scenarios. The model will optimize the match of personnel groups (military, DoD civilian, and contractors) and capabilities to meet the mission requirements as effectively as possible, based on risk, cost, and other requirements.
This tutorial walks the user through analysis examples using the Contingency Contractor Optimization Tool Prototype. The examples are designed to showcase key capabilities of the tool. The main goal of this tutorial is to provide examples of how to use the tool to perform analyses to those users acting in the analyst role. All examples and locations used in the prototype are fictional, but are intended to be realistic. Users reading this manual are expected to have a basic understanding and familiarity with the Contingency Contractor Optimization Tool Prototype. This tutorial includes scenarios for the occurrence of two wars, Prussia and New Granada.
Abstract not provided.
Transportation Research Record
This paper presents a probabilistic origin-destination table for waterborne containerized imports. The analysis makes use of 2012 Port Import/Export Reporting Service data, 2012 Surface Transportation Board waybill data, a gravity model, and information on the landside transportation mode split associated with specifc ports. This analysis suggests that about 70% of the origin-destination table entries have a coeffcient of variation of less than 20%. This 70% of entries is associated with about 78% of the total volume. This analysis also makes evident the importance of rail interchange points in Chicago, Illinois; Memphis, Tennessee; Dallas, Texas; and Kansas City, Missouri, in supporting the transportation of containerized goods from Asia through West Coast ports to the eastern United States.
This User Manual provides step-by-step instructions on the Contingency Contractor Optimization Tool's major features. Activities are organized by user role. The Contingency Contractor Optimization project is intended to address former Secretary Gates' mandate in a January 2011 memo and DoDI 3020.41 by delivering a centralized strategic planning tool that allows senior decision makers to quickly and accurately assess the impacts, risks, and mitigation strategies associated with utilizing contract support. Based on an electronic storyboard prototype developed in Phase 2, the Contingency Contractor Optimization Tool engineering prototype was refined in Phase 3 of the OSD ATL Contingency Contractor Optimization project to support strategic planning for contingency contractors. The planning tool uses a model to optimize the Total Force mix by minimizing the combined total costs for the selected mission scenarios. The model will optimize the match of personnel groups (military, DoD civilian, and contractors) and capabilities to meet the mission requirements as effectively as possible, based on risk, cost, and other requirements.