To date, disinformation research has focused largely on the production of false information ignoring the suppression of select information. We term this alternative form of disinformation information suppression. Information suppression occurs when facts are withheld with the intent to mislead. In order to detect information suppression, we focus on understanding the actors who withhold information. In this research, we use knowledge of human behavior to find signatures of different gatekeeping behaviors found in text. Specifically, we build a model to classify the different types of edits on Wikipedia using the added text alone and compare a human-informed feature engineering approach to a featureless algorithm. Being able to computationally distinguish gatekeeping behaviors is a first step towards identifying when information suppression is occurring.
This simple Microgrid Design Toolkit (MDT) use case will provide you an example of a basic microgrid design. It will introduce basic principles of using the MDT islanded mode optimization by modifying a baseline microgrid design and performing an analysis of the results. Please reference the MDT User Guide (SAND2020-4550) for detailed instructions on how to use the tool.
This simple Microgrid Design Toolkit (MDT) use case will provide you an example of performing microgrid sizing by identifying the types and quantities of technology to be purchased for use in a microgrid. It will introduce basic principles of using the MDT microgrid sizing capability by comparing the results of two microgrids in two different markets. Please reference the MDT User Guide (SAND2020-4550) for detailed instructions on how to use the tool.
This report describes the results of a seven day effort to assist subject matter experts address a problem related to COVID-19. In the course of this effort, we analyzed the 29K documents provided as part of the White House's call to action. This involved applying a variety of natural language processing techniques and compression-based analytics in combination with visualization techniques and assessment with subject matter experts to pursue answers to a specific question. In this paper, we will describe the algorithms, the software, the study performed, and availability of the software developed during the effort.
This document represents the results of deliverable D05.02 (Identify relevant efforts at SNL and other institutions) under the activity area Relevant Efforts Review. The goal of the Relevant Efforts Review activity is to identify relevant data integration efforts at SNL and possibly other institutions and compile lessons learned that are relevant to the development of a framework for data integration efforts in support of analysts and decision makers. The intent of this activity is to provide, by examples, context of how the requirements-gathering process has already been implemented in other instances and to guide the development of such a process for OCIA's needs. Information for this report was gathered through SNL staff interviews and the team members' knowledge and project experiences.
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
In July 2012, protestors cut through security fences and gained access to the Y-12 National Security Complex. This was believed to be a highly reliable, multi-layered security system. This report documents the results of a Laboratory Directed Research and Development (LDRD) project that created a consistent, robust mathematical framework using complex systems analysis algorithms and techniques to better understand the emergent behavior, vulnerabilities and resiliency of multi-layered security systems subject to budget constraints and competing security priorities. Because there are several dimensions to security system performance and a range of attacks that might occur, the framework is multi-objective for a performance frontier to be estimated. This research explicitly uses probability of intruder interruption given detection (PI) as the primary resilience metric. We demonstrate the utility of this framework with both notional as well as real-world examples of Physical Protection Systems (PPSs) and validate using a well-established force-on-force simulation tool, Umbra.
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.
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 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.
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.
The goal is to make software developers aware of common issues that can impede the adoption of analytic tools. This paper provides a summary of guidelines, lessons learned and existing research to explain what is currently known about what analysts want and how to better understand what tools they do and don't need.
This Quick Start Guide is an abbreviated version of the Contingency Contractor Optimization Phase 3, User Manual for the Contingency Contractor Optimization Tool engineering prototype. It focuses on providing quick access instructions to the core activities of the two main user roles: Planning Manager and Analyst. 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 to support strategic planning for contingency contractors. The tool 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 types (military, DoD civilian, and contractors) and capabilities to meet the mission requirements as effectively as possible, based on risk, cost, and other requirements.
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 [1] and DoDI 3020.41 [2] 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.
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 [1] and DoDI 3020.41 [2] 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.
This Quick Start Guide is an abbreviated version of the Contingency Contractor Optimization Phase 3, User Manual for the Contingency Contractor Optimization Tool engineering prototype. It focuses on providing quick access instructions to the core activities of the two main user roles: Planning Manager and Analyst. 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 to support strategic planning for contingency contractors. The tool 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 types (military, DoD civilian, and contractors) and capabilities to meet the mission requirements as effectively as possible, based on risk, cost, and other requirements.
The goal of Phase 3 the OSD ATL Contingency Contractor Optimization (CCO) project is to create an engineering prototype of a tool for the contingency contractor element of total force planning during the Support for Strategic Analysis (SSA). An optimization model was developed to determine the optimal mix of military, Department of Defense (DoD) civilians, and contractors that accomplishes a set of user defined mission requirements at the lowest possible cost while honoring resource limitations and manpower use rules. An additional feature allows the model to understand the variability of the Total Force Mix when there is uncertainty in mission requirements.
Infectious diseases can spread rapidly through healthcare facilities, resulting in widespread illness among vulnerable patients. Computational models of disease spread are useful for evaluating mitigation strategies under different scenarios. This report describes two infectious disease models built for the US Department of Veteran Affairs (VA) motivated by a Varicella outbreak in a VA facility. The first model simulates disease spread within a notional contact network representing staff and patients. Several interventions, along with initial infection counts and intervention delay, were evaluated for effectiveness at preventing disease spread. The second model adds staff categories, location, scheduling, and variable contact rates to improve resolution. This model achieved more accurate infection counts and enabled a more rigorous evaluation of comparative effectiveness of interventions.
The goal of Phase 3 the OSD ATL Contingency Contractor Optimization (CCO) project is to create an engineering prototype of a tool for the contingency contractor element of total force planning during the Support for Strategic Analysis (SSA). An optimization model was developed to determine the optimal mix of military, Department of Defense (DoD) civilians, and contractors that accomplishes a set of user defined mission requirements at the lowest possible cost while honoring resource limitations and manpower use rules. An additional feature allows the model to understand the variability of the Total Force Mix when there is uncertainty in mission requirements.