UNCLASSIFIED

Skip to content

GitLab

You need to sign in or sign up before continuing.
Commits (2)
Hide whitespace changes
Inline Side-by-side
Showing with 20 additions and 20 deletions

Too many changes to show.

To preserve performance only 75 of 75+ files are displayed.
sites/oteguide/page-data/OT&E_Guide/1-1-introduction/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/1-1-introduction","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"5bcee507-8b11-50e8-b753-8734ea73dab5","title":"Introduction","slug":"/OT&E_Guide/1-1-introduction"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Introduction\",\n \"metaTitle\": \"Operational Test and Evaluation Guide\",\n \"metaDescription\": \"\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-3\"), mdx(\"h1\", null, \"FOREWORD\"), mdx(\"p\", null, \"This guide captures best practices and corporate knowledge \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" has\\ngained since 1974, to carry out our core mission of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"delivering combat\\ncapability through operational testing\"), \". By conducting \", mdx(\"em\", {\n parentName: \"p\"\n }, \"early\"), \"\\noperational testing and evaluation in relevant environments, we find and\\nfix problems sooner to deliver combat capability at the \\\"speed of\\nrelevance.\\\" We provide early, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"continuous and cumulative feedback\"), \" that\\nidentifies deficiencies, informs warfighters, and influences national\\nresource decisions without delay. Our \", mdx(\"em\", {\n parentName: \"p\"\n }, \"integrated test\"), \" approach is key\\nto early engagement and preventing wasteful duplication. We strive to\\nachieve developmental and operational test objectives by using test\\npoints designed from the outset that optimize developmental and\\noperational data collection\", \"-\", \"-one team, one plan, one test.\"), mdx(\"p\", null, \"This guide is a toolbox of processes, procedures, and techniques that\\nenable an integrated test approach. These tools are designed to promote\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"relevant, credible and timely\"), \" operational testing that uses test\\nresources efficiently. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not measure specification compliance.\\nWe are charged with focusing on a system's effectiveness, suitability,\\nand survivability when employed in its intended operational environment.\\nAccordingly, our measures must reflect this charge.\"), mdx(\"p\", null, \"Importantly, the tools in this Guide are not prescriptive, nor\\nexhaustive, but provide test teams a starting point from which they can\\ndeviate as they \", mdx(\"em\", {\n parentName: \"p\"\n }, \"tailor and streamline\"), \" tools and methods to suit each\\nsystem under test. Our goal is not uniformity, but \", mdx(\"em\", {\n parentName: \"p\"\n }, \"adapting\"), \" test\\nevents to each unique program to meet our chief focus of delivering\\ncombat capability.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" actively participates in all acquisition phases by developing and\\ncoordinating products that refine acquisition strategies and capability\\nrequirements. Our early involvement in initial test design and\\nemployment of design of experiment methodologies helps us avoid late\\ndiscovery of system shortfalls. Through successful integrated testing,\\nwe leverage results from developmental testing to satisfy operational\\ntest objectives earlier, execute dedicated operational test with a\\nhigher probability of success, and support the warfighter with\\noperationally effective, suitable, and combat-capable weapon systems.\\nContinuous, hands-on operational testing enables the team to find and\\nfix system deficiencies early, which yields faster and smarter delivery\\nof combat capability. A continuous operational test approach requires us\\nto incorporate the notion of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"exit criteria\", \"-\", \"-\"), \"defined operational test\\nactivities and assessments that meet test objectives, rather than\\nacquisition-driven requirements-based entrance criteria. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s\\noverarching test framework combines the tools in this Guide with our\\nAdaptive Relevant Testing (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \") principles: Early Operational Test\\nInvolvement; Tailor to the Situation; Continuous and Cumulative\\nFeedback; Streamlined Processes and Products; Integrated and Combined\\nCollection/Test; Adaptive. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test strategies capture these\\nprinciples, ideas, and actions so we can achieve our ultimate goal of\\ndelivering combat capability.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Guide, 11th Edition is significantly different from previous\\neditions. We restructured it to address \\\"what\\\" to do instead of \\\"how\\\" to\\ndo it. This update is non-prescriptive to provide \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" teams a\\nsignificant amount of latitude. It relies on separate supporting\\nfunctional guides and case studies. This update includes guidance on the\\nAdaptive-Relevant Test (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \") principles and the Combined Test Force\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \"), and captures significant changes to the purpose of test,\\noperational test readiness reviews (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Readiness Review\"\n }, \"OTRR\"), \"), test measures, continuous\\nreporting, and effectiveness and suitability ratings. This update\\nfocuses on guiding principles. We removed a significant amount of\\ndetailed information and placed it in separate supporting functional\\nguides that the reader must use in conjunction with this updated edition\\nfor comprehensive \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E guidance. For example, this update does not\\ncontain details on verification, validation, and accreditation, nor\\neffectiveness and suitability ratings. We also eliminated the\\nrequirement to report on whether a system demonstrates mission\\ncapability.\"), mdx(\"h1\", null, \"INTRODUCTION\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" actively participates in all acquisition phases and product\\ndevelopment. Our early involvement helps avoid late discovery of system\\noperational shortfalls. Integrated testing leverages results from early\\nand continuous testing to satisfy operational test objectives earlier\\nand support the warfighter with operationally effective, suitable,\\ncombat-capable weapon systems.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s overarching test framework combines the tools in this Guide\\nwith our Adaptive Relevant Testing (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \") principles: Early \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nInvolvement; Tailor to the Situation; Continuous and Cumulative\\nFeedback; Streamlined Processes and Products; Integrated and Combined\\nCollection/Test; Adaptive.\"), mdx(\"h1\", null, \"Purpose\"), mdx(\"p\", null, \"This guide is intended to provide the overarching, general concepts, and\\nprinciples to structuring \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s involvement in testing and fielding\\ncombat capability. It outlines \\\"what\\\" should be done, with insight to\\n\\\"why,\\\" and places the responsibility and authority on \\\"how\\\" and \\\"when\\\"\\non the test team. The focus of this Guide is not on detailed steps or\\nproducts produced, but on concepts and principles being relevant,\\ncredible, and timely. In addition, the concept that test happens\\nsequentially throughout an acquisition lifecycle process must be\\nreplaced with the concept that test occurs continually and in parallel\\nwith the acquisition lifecycle. Furthermore, the legacy handoff from\\ncontractor testing (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \") to developmental testing (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \") and finally to\\noperational testing (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \") must be an integrated, collaborative effort. We\\nmust shape each test event to meet \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" objectives\\nsimultaneously by collecting data across the continuum that answers\\nrespective test objectives defined within one test plan\", \"-\", \"-one team, one\\nplan, one test.\"), mdx(\"h1\", null, \"How to Use the Operational Test and Evaluation Guide\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles enable earlier discovery of problems and delivery of\\ncombat capability. Functional guides, tools, and case studies provide\\nbest practices and recommendations for specific techniques, procedures,\\nand processes a test team can use to \", mdx(\"em\", {\n parentName: \"p\"\n }, \"tailor\"), \" their program.\"), mdx(\"p\", null, \"The test team will use this Guide in conjunction with its separate\\nfunctional guides, tools, and case studies. Functional guides, such as\\nthe \\\"\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://usaf.dps.mil/:w:/r/sites/AFOTEC-PRIVATE/mainlibrary/oteguide/Shared%20Documents/Functional%20Guides/AFOTEC%20Measures%20Guide.docx?d=wbc0b99c216d046d3be3dc35124bc76e1&csf=1&web=1&e=bxxFWz\"\n }, \"Measures\\nGuide\"), \",\\\"\\n\\\"\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/analyst_test_design_guide/\"\n }, \"Analyst Test Design\\nGuide\"), \",\\\"\\nand the \\\"\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/strat_planning_programming_guide/\"\n }, \"Strategy, Planning, and Programming Process\\nGuide\"), \"\\\"\\ncontain additional how-to details common across test activities. The\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://usaf.dps.mil/sites/AFOTEC-PRIVATE/mainlibrary/oteguide/SitePages/Tools-Page.aspx\"\n }, \"Tools Catalog\"), \"\\ncontains categories and descriptions of tool options for various test\\nstrategies/stages. For example, Communication Tools help the test team\\nconvey their message to disparate audiences throughout the test\\nlifecycle\", \"-\", \"-situational updates, public affairs venues, formal reports,\\ninformal reports, and similar options\", \"-\", \"-depending on the test stage and\\nstakeholder requirements or requests. Case studies provide examples of\\nLessons Learned when applying \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles to different program\\nacquisition strategies, and when leveraging various tools continuously\\nthroughout the test lifecycle.\"), mdx(\"p\", null, \"Test teams may use additional references such as instructions, manuals,\\ndocument templates, and checklists when applying the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles.\\nTest teams should contribute to functional guides by adding tools to the\\ntoolboxes and building case studies. The intent is to update these\\nguides/tools continuously rather than on a periodic schedule or based on\\nthe number/magnitude of changes. In addition to the concepts and\\nprinciples in this guide, generic business processes are included as a\\nreference.\"), mdx(\"p\", null, \"The Commander will issue an operational test information files (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Information Files\"\n }, \"OTIF\"), \") to\\neffect \\\"pen and ink\\\" and/or \\\"remove and replace page\\\" changes to the\\nGuide. When \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" migrates to a flexible electronic Guide (similar to\\nan app), the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Information Files\"\n }, \"OTIF\"), \" will alert personnel that there is a change and then\\nthey can update their app or download the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Information Files\"\n }, \"OTIF\"), \".\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Chapter 1 introduces the goal of fielding combat capability, which\\nincludes \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s role, acquisition pathways to delivering combat\\ncapability, and how to apply \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles to this goal.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Chapter 2 provides an overview of the test lifecycle, or \\\"life of a\\ntest.\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Chapter 3 discusses a test lifecycle's initial activities, standing\\nor continuous activities conducted throughout the test lifecycle,\\nand, importantly, developing a test strategy to match the\\nacquisition strategy.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Chapter 4 begins with a conceptual model of a system and the mission\\neffects a system enables. It introduces the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct as a\\nframework and test activities as building blocks. It outlines five\\ngeneral steps that define a test activity.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Chapter 5 explains activities to conclude a test program, notably\\nthe exit criteria. Typically, this includes producing an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E final\\nreport.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Chapter 6 includes various business processes applied across \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\n(coordination processes, tasking orders, risk management,\\ndocumentation, contract support, etc.)\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#foreword","title":"FOREWORD"},{"url":"#introduction","title":"INTRODUCTION"},{"url":"#purpose","title":"Purpose"},{"url":"#how-to-use-the-operational-test-and-evaluation-guide","title":"How to Use the Operational Test and Evaluation Guide"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/1-1-introduction.md"},"frontmatter":{"metaTitle":"Operational Test and Evaluation Guide","metaDescription":""}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"5bcee507-8b11-50e8-b753-8734ea73dab5"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/1-1-introduction","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"5bcee507-8b11-50e8-b753-8734ea73dab5","title":"Introduction","slug":"/OT&E_Guide/1-1-introduction"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Introduction\",\n \"metaTitle\": \"Operational Test and Evaluation Guide\",\n \"metaDescription\": \"\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-3\"), mdx(\"h1\", null, \"FOREWORD\"), mdx(\"p\", null, \"This guide captures best practices and corporate knowledge \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" has\\ngained since 1974, to carry out our core mission of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"delivering combat\\ncapability through operational testing\"), \". By conducting \", mdx(\"em\", {\n parentName: \"p\"\n }, \"early\"), \"\\noperational testing and evaluation in relevant environments, we find and\\nfix problems sooner to deliver combat capability at the \\\"speed of\\nrelevance.\\\" We provide early, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"continuous and cumulative feedback\"), \" that\\nidentifies deficiencies, informs warfighters, and influences national\\nresource decisions without delay. Our \", mdx(\"em\", {\n parentName: \"p\"\n }, \"integrated test\"), \" approach is key\\nto early engagement and preventing wasteful duplication. We strive to\\nachieve developmental and operational test objectives by using test\\npoints designed from the outset that optimize developmental and\\noperational data collection\", \"-\", \"-one team, one plan, one test.\"), mdx(\"p\", null, \"This guide is a toolbox of processes, procedures, and techniques that\\nenable an integrated test approach. These tools are designed to promote\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"relevant, credible and timely\"), \" operational testing that uses test\\nresources efficiently. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not measure specification compliance.\\nWe are charged with focusing on a system's effectiveness, suitability,\\nand survivability when employed in its intended operational environment.\\nAccordingly, our measures must reflect this charge.\"), mdx(\"p\", null, \"Importantly, the tools in this Guide are not prescriptive, nor\\nexhaustive, but provide test teams a starting point from which they can\\ndeviate as they \", mdx(\"em\", {\n parentName: \"p\"\n }, \"tailor and streamline\"), \" tools and methods to suit each\\nsystem under test. Our goal is not uniformity, but \", mdx(\"em\", {\n parentName: \"p\"\n }, \"adapting\"), \" test\\nevents to each unique program to meet our chief focus of delivering\\ncombat capability.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" actively participates in all acquisition phases by developing and\\ncoordinating products that refine acquisition strategies and capability\\nrequirements. Our early involvement in initial test design and\\nemployment of design of experiment methodologies helps us avoid late\\ndiscovery of system shortfalls. Through successful integrated testing,\\nwe leverage results from developmental testing to satisfy operational\\ntest objectives earlier, execute dedicated operational test with a\\nhigher probability of success, and support the warfighter with\\noperationally effective, suitable, and combat-capable weapon systems.\\nContinuous, hands-on operational testing enables the team to find and\\nfix system deficiencies early, which yields faster and smarter delivery\\nof combat capability. A continuous operational test approach requires us\\nto incorporate the notion of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"exit criteria\", \"-\", \"-\"), \"defined operational test\\nactivities and assessments that meet test objectives, rather than\\nacquisition-driven requirements-based entrance criteria. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s\\noverarching test framework combines the tools in this Guide with our\\nAdaptive Relevant Testing (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \") principles: Early Operational Test\\nInvolvement; Tailor to the Situation; Continuous and Cumulative\\nFeedback; Streamlined Processes and Products; Integrated and Combined\\nCollection/Test; Adaptive. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test strategies capture these\\nprinciples, ideas, and actions so we can achieve our ultimate goal of\\ndelivering combat capability.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Guide, 11th Edition is significantly different from previous\\neditions. We restructured it to address \\\"what\\\" to do instead of \\\"how\\\" to\\ndo it. This update is non-prescriptive to provide \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" teams a\\nsignificant amount of latitude. It relies on separate supporting\\nfunctional guides and case studies. This update includes guidance on the\\nAdaptive-Relevant Test (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \") principles and the Combined Test Force\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \"), and captures significant changes to the purpose of test,\\noperational test readiness reviews (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Readiness Review\"\n }, \"OTRR\"), \"), test measures, continuous\\nreporting, and effectiveness and suitability ratings. This update\\nfocuses on guiding principles. We removed a significant amount of\\ndetailed information and placed it in separate supporting functional\\nguides that the reader must use in conjunction with this updated edition\\nfor comprehensive \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E guidance. For example, this update does not\\ncontain details on verification, validation, and accreditation, nor\\neffectiveness and suitability ratings. We also eliminated the\\nrequirement to report on whether a system demonstrates mission\\ncapability.\"), mdx(\"h1\", null, \"INTRODUCTION\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" actively participates in all acquisition phases and product\\ndevelopment. Our early involvement helps avoid late discovery of system\\noperational shortfalls. Integrated testing leverages results from early\\nand continuous testing to satisfy operational test objectives earlier\\nand support the warfighter with operationally effective, suitable,\\ncombat-capable weapon systems.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s overarching test framework combines the tools in this Guide\\nwith our Adaptive Relevant Testing (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \") principles: Early \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nInvolvement; Tailor to the Situation; Continuous and Cumulative\\nFeedback; Streamlined Processes and Products; Integrated and Combined\\nCollection/Test; Adaptive.\"), mdx(\"h1\", null, \"Purpose\"), mdx(\"p\", null, \"This guide is intended to provide the overarching, general concepts, and\\nprinciples to structuring \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s involvement in testing and fielding\\ncombat capability. It outlines \\\"what\\\" should be done, with insight to\\n\\\"why,\\\" and places the responsibility and authority on \\\"how\\\" and \\\"when\\\"\\non the test team. The focus of this Guide is not on detailed steps or\\nproducts produced, but on concepts and principles being relevant,\\ncredible, and timely. In addition, the concept that test happens\\nsequentially throughout an acquisition lifecycle process must be\\nreplaced with the concept that test occurs continually and in parallel\\nwith the acquisition lifecycle. Furthermore, the legacy handoff from\\ncontractor testing (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \") to developmental testing (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \") and finally to\\noperational testing (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \") must be an integrated, collaborative effort. We\\nmust shape each test event to meet \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" objectives\\nsimultaneously by collecting data across the continuum that answers\\nrespective test objectives defined within one test plan\", \"-\", \"-one team, one\\nplan, one test.\"), mdx(\"h1\", null, \"How to Use the Operational Test and Evaluation Guide\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles enable earlier discovery of problems and delivery of\\ncombat capability. Functional guides, tools, and case studies provide\\nbest practices and recommendations for specific techniques, procedures,\\nand processes a test team can use to \", mdx(\"em\", {\n parentName: \"p\"\n }, \"tailor\"), \" their program.\"), mdx(\"p\", null, \"The test team will use this Guide in conjunction with its separate\\nfunctional guides, tools, and case studies. Functional guides, such as\\nthe \\\"\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://usaf.dps.mil/:w:/r/sites/AFOTEC-PRIVATE/mainlibrary/oteguide/Shared%20Documents/Functional%20Guides/AFOTEC%20Measures%20Guide.docx?d=wbc0b99c216d046d3be3dc35124bc76e1&csf=1&web=1&e=bxxFWz\"\n }, \"Measures\\nGuide\"), \",\\\"\\n\\\"\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/analyst_test_design_guide/\"\n }, \"Analyst Test Design\\nGuide\"), \",\\\"\\nand the \\\"\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/strat_planning_programming_guide/\"\n }, \"Strategy, Planning, and Programming Process\\nGuide\"), \"\\\"\\ncontain additional how-to details common across test activities. The\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://usaf.dps.mil/sites/AFOTEC-PRIVATE/mainlibrary/oteguide/SitePages/Tools-Page.aspx\"\n }, \"Tools Catalog\"), \"\\ncontains categories and descriptions of tool options for various test\\nstrategies/stages. For example, Communication Tools help the test team\\nconvey their message to disparate audiences throughout the test\\nlifecycle\", \"-\", \"-situational updates, public affairs venues, formal reports,\\ninformal reports, and similar options\", \"-\", \"-depending on the test stage and\\nstakeholder requirements or requests. Case studies provide examples of\\nLessons Learned when applying \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles to different program\\nacquisition strategies, and when leveraging various tools continuously\\nthroughout the test lifecycle.\"), mdx(\"p\", null, \"Test teams may use additional references such as instructions, manuals,\\ndocument templates, and checklists when applying the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles.\\nTest teams should contribute to functional guides by adding tools to the\\ntoolboxes and building case studies. The intent is to update these\\nguides/tools continuously rather than on a periodic schedule or based on\\nthe number/magnitude of changes. In addition to the concepts and\\nprinciples in this guide, generic business processes are included as a\\nreference.\"), mdx(\"p\", null, \"The Commander will issue an operational test information files (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Information Files\"\n }, \"OTIF\"), \") to\\neffect \\\"pen and ink\\\" and/or \\\"remove and replace page\\\" changes to the\\nGuide. When \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" migrates to a flexible electronic Guide (similar to\\nan app), the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Information Files\"\n }, \"OTIF\"), \" will alert personnel that there is a change and then\\nthey can update their app or download the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Information Files\"\n }, \"OTIF\"), \".\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Chapter 1 introduces the goal of fielding combat capability, which\\nincludes \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s role, acquisition pathways to delivering combat\\ncapability, and how to apply \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles to this goal.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Chapter 2 provides an overview of the test lifecycle, or \\\"life of a\\ntest.\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Chapter 3 discusses a test lifecycle's initial activities, standing\\nor continuous activities conducted throughout the test lifecycle,\\nand, importantly, developing a test strategy to match the\\nacquisition strategy.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Chapter 4 begins with a conceptual model of a system and the mission\\neffects a system enables. It introduces the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct as a\\nframework and test activities as building blocks. It outlines five\\ngeneral steps that define a test activity.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Chapter 5 explains activities to conclude a test program, notably\\nthe exit criteria. Typically, this includes producing an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E final\\nreport.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Chapter 6 includes various business processes applied across \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\n(coordination processes, tasking orders, risk management,\\ndocumentation, contract support, etc.)\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#foreword","title":"FOREWORD"},{"url":"#introduction","title":"INTRODUCTION"},{"url":"#purpose","title":"Purpose"},{"url":"#how-to-use-the-operational-test-and-evaluation-guide","title":"How to Use the Operational Test and Evaluation Guide"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/1-1-introduction.md"},"frontmatter":{"metaTitle":"Operational Test and Evaluation Guide","metaDescription":""}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"5bcee507-8b11-50e8-b753-8734ea73dab5"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/1-3-fielding-combat-capes/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/1-3-fielding-combat-capes","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"916a1c87-2165-5cd0-abac-2a89862a0827","title":"Fielding Combat Capability","slug":"/OT&E_Guide/1-3-fielding-combat-capes"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Fielding Combat Capability\",\n \"metaTitle\": \"Fielding Combat Capability\",\n \"metaDescription\": \"AFOTEC's role\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" focuses on delivering combat capability to the warfighter at the\\nspeed of relevance. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles apply to all acquisition types,\\ntechnology demonstrations, and experimentation. Combat capability is\\ndefined by how well the system works (performance), how much you have\\n(quantity), and how quickly you receive it (speed to field). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \"\\nprinciples identify problems earlier, enable shorter development and\\nproduction times, maximize the potential to move major decision points\\nleft, buy down costs, and field combat capability earlier, as depicted\\nin Figure 1-1.\"), mdx(\"p\", null, \"Figure 1\\u20111. Fielding Combat Capability\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"447px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/285108d56c66afcdd2a9fa7e611441ba/a2d48/image3.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"88.4169884169884%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAASCAYAAABb0P4QAAAACXBIWXMAABcRAAAXEQHKJvM/AAAE2UlEQVQ4y41Ra0xTdxQ/0DoFFARaCn0/Lu1tAbWdIFjodQKiMpW2lPJoC5VCBUtSEBUbWRAjPpAJPnDON1VB8LFRO+YrsmRxC35ZssyPamqy+GX7NjZLe88uumWZ2bKd5PzP43fOL/9zDsA7whebICE+FwRiUwxLVAcgqEtzKgyXkISFSMbATaUC6uITYVKlgP8lCrIRymsngSC3suJIDyxVOAfqpfk4KeV2BMQpcEYsYp8SieCCVPzfZGJFHaN2kGU6WJlqN6hJZwFPUoXFqXI8LcyYHVeSxKQyE/xyaWxARcA1hezfyQQiMzS4TkEKr4KJSEAcBjlhf8ITlaNNof3Vx03GMxJxsDuVA67ExJiHGhWcEAkgSP7D6EKxeX5EKDDshWxtGztL2w6SzKbdYkkFSjRV4d1ZhXhEwAnvSePieKbC7hfyYZifzv5kSQKMEjKYUsr/TiglHAALykGhcsUq1B5QqFuJQqptliSNSOqc0WalDgNZRMTD4+JBHvfVDD899REnBS5zUmJ+VBPwmfKdX+oK9jKvEu4/+CYmEPgaSsp8wfwCOxasds8Zrbtxf10jPbW+GE/Kxa+383l4PltzbrBQDz15uaz5/n5Bxl9kmZpWkKq8kF/UxaZKeyFP32Uv39SOKo11rqNjkJ64FaSnv3tAz5wexuCGUtpHZkb2GYrwckpS6bnUZDgu5LPOMhc/IxX9sT+JFcSEO4a9xMVE9tSSsq5X6iwLbjL6oqP+AF6bmaD7ZgZx6snn9LcXRnBkRdZcM6nE/ryVT8PMol4wXWPE2x1OENK3pDWO46zm7edh3cZ956gPWnB1UWt44NBFvHUvSHtGO2n3RS/6bvfg43uT9JftXuyT8F/b0zj4MZ+3v4ezFHZxktk1i+OhNyMNQKPdxSK13aBavmddjrYVc5bbo2vX7UJfzzBtOemmjQe2Ytugj7Ycakbv2Z30+HYvjigJuikpgXYlJkSuKxUrLjOX7hdmxH4qlwCoNdtAv7xmQbZ2x1OZqgGV2o5ISVFl5OrhhsglfyeOjh+jx24M0f6xAbwy0okPu7dET+fI6GN8UXjzewuwMzXpqz/vcVujBEjXDoFK290rUnuQWuOeHWoq/S10UDYXPpUTDV1tjz67fSAaGuuMPp/4KBrye6K/MPnnPZLItFkW9om5s+tjY7GXx2lpWrQYHHFxLEjQHFm1clUX2vJL0F+pxul6GU7VL8NJ+zKcqFLh9So13qzR4EQlgTcYG7DnMHg23nUQeH2zHBuFiWhfHDfbmSQhDsezAdo3Wq/crdb9/LKW+/wHU9rLx2ZFKOikQkHX2tC0TRe631AQmmoqDj2a95360B2nIfQFg8+YJKHvzRkvX9hFz+6UJv90nFzY73xfB+CtaynpMNsN5Rs8lLG8haoud1EVhWaqQm+irGUOyrK2ljIWVVKWUjtlXmOlKhjfaLBQNZuaKcuH26gtZW5qh3OnYWu1t1ia18mBuKw2FOi7sNQxhOudJ7Cg8ghStcewsHoAV1YcxDzTYdRXHX2Tn7d661HMNR7CouqjaGBqCpk4fdVOjGd44pSuPoAMU328vNomzW22rSj22pSrWxltsRH522wincsm1DXaBNpGmyyv+Y3K89w2KWPncZW+9U1ukbSqDvjmhlihRfM7NzniWn92WX8AAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image3\",\n \"title\": \"image3\",\n \"src\": \"/static/285108d56c66afcdd2a9fa7e611441ba/a2d48/image3.png\",\n \"srcSet\": [\"/static/285108d56c66afcdd2a9fa7e611441ba/a2ead/image3.png 259w\", \"/static/285108d56c66afcdd2a9fa7e611441ba/a2d48/image3.png 447w\"],\n \"sizes\": \"(max-width: 447px) 100vw, 447px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"h1\", null, \"AFOTECs Role in Fielding Combat Capability\"), mdx(\"p\", null, \"As the Air Force's operational test agency (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \"), \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" tests and\\nevaluates new capabilities in operationally realistic environments.\\nChallenges associated with adaptive acquisition strategies,\\ncybersecurity, and game-changing technologies require that we adapt,\\nevolve, and be flexible in our approach and perspectives. We must be an\\nagile \\\"learning organization\\\" while simultaneously employing our legacy\\nof test designs, rigorous analysis, and fully transparent reporting for\\nour customers. Our charge is to deliver combat capability to the\\nwarfighter through operational testing\", \"-\", \"-accurate and balanced\\noperational truth for every system we test.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" supports urgent operational needs, middle tier of acquisition,\\nmajor capability acquisition, software acquisition, defense business\\nsystems, acquisition of services and experimentation as necessary.\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" provides \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E information and expertise to major commands\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \"), other \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" components, Air National Guard (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air National Guard\"\n }, \"ANG\"), \"), Air Force\\nReserve Command, Chief of Staff of the Air Force, Secretary of the Air\\nForce (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SECAF\"), \"), combatant commands, Office of the Secretary of Defense\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Secretary of Defense\"\n }, \"OSD\"), \"), Congress, and other government agencies.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" engages in early and continuous involvement. We execute\\nintegrated test activities by supporting development of operational\\ncapability requirements, shaping the acquisition strategy, and\\ninfluencing system design and development from program inception through\\nsuccessful fielding.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assesses and evaluates new combat capability by executing\\noperational test activities in a relevant, credible, and timely fashion.\\nTypes of test activities and reporting requirements are dependent on the\\nacquisition strategy. Examples of test activities and reporting options\\nare available in the functional guides, tools, and case studies.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#afotecs-role-in-fielding-combat-capability","title":"AFOTECs Role in Fielding Combat Capability"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/1-3-fielding-combat-capes.md"},"frontmatter":{"metaTitle":"Fielding Combat Capability","metaDescription":"AFOTEC's role"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"916a1c87-2165-5cd0-abac-2a89862a0827"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/1-3-fielding-combat-capes","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"916a1c87-2165-5cd0-abac-2a89862a0827","title":"Fielding Combat Capability","slug":"/OT&E_Guide/1-3-fielding-combat-capes"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Fielding Combat Capability\",\n \"metaTitle\": \"Fielding Combat Capability\",\n \"metaDescription\": \"AFOTEC's role\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" focuses on delivering combat capability to the warfighter at the\\nspeed of relevance. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles apply to all acquisition types,\\ntechnology demonstrations, and experimentation. Combat capability is\\ndefined by how well the system works (performance), how much you have\\n(quantity), and how quickly you receive it (speed to field). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \"\\nprinciples identify problems earlier, enable shorter development and\\nproduction times, maximize the potential to move major decision points\\nleft, buy down costs, and field combat capability earlier, as depicted\\nin Figure 1-1.\"), mdx(\"p\", null, \"Figure 1\\u20111. Fielding Combat Capability\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"447px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/285108d56c66afcdd2a9fa7e611441ba/a2d48/image3.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"88.4169884169884%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAASCAYAAABb0P4QAAAACXBIWXMAABcRAAAXEQHKJvM/AAAE2UlEQVQ4y41Ra0xTdxQ/0DoFFARaCn0/Lu1tAbWdIFjodQKiMpW2lPJoC5VCBUtSEBUbWRAjPpAJPnDON1VB8LFRO+YrsmRxC35ZssyPamqy+GX7NjZLe88uumWZ2bKd5PzP43fOL/9zDsA7whebICE+FwRiUwxLVAcgqEtzKgyXkISFSMbATaUC6uITYVKlgP8lCrIRymsngSC3suJIDyxVOAfqpfk4KeV2BMQpcEYsYp8SieCCVPzfZGJFHaN2kGU6WJlqN6hJZwFPUoXFqXI8LcyYHVeSxKQyE/xyaWxARcA1hezfyQQiMzS4TkEKr4KJSEAcBjlhf8ITlaNNof3Vx03GMxJxsDuVA67ExJiHGhWcEAkgSP7D6EKxeX5EKDDshWxtGztL2w6SzKbdYkkFSjRV4d1ZhXhEwAnvSePieKbC7hfyYZifzv5kSQKMEjKYUsr/TiglHAALykGhcsUq1B5QqFuJQqptliSNSOqc0WalDgNZRMTD4+JBHvfVDD899REnBS5zUmJ+VBPwmfKdX+oK9jKvEu4/+CYmEPgaSsp8wfwCOxasds8Zrbtxf10jPbW+GE/Kxa+383l4PltzbrBQDz15uaz5/n5Bxl9kmZpWkKq8kF/UxaZKeyFP32Uv39SOKo11rqNjkJ64FaSnv3tAz5wexuCGUtpHZkb2GYrwckpS6bnUZDgu5LPOMhc/IxX9sT+JFcSEO4a9xMVE9tSSsq5X6iwLbjL6oqP+AF6bmaD7ZgZx6snn9LcXRnBkRdZcM6nE/ryVT8PMol4wXWPE2x1OENK3pDWO46zm7edh3cZ956gPWnB1UWt44NBFvHUvSHtGO2n3RS/6bvfg43uT9JftXuyT8F/b0zj4MZ+3v4ezFHZxktk1i+OhNyMNQKPdxSK13aBavmddjrYVc5bbo2vX7UJfzzBtOemmjQe2Ytugj7Ycakbv2Z30+HYvjigJuikpgXYlJkSuKxUrLjOX7hdmxH4qlwCoNdtAv7xmQbZ2x1OZqgGV2o5ISVFl5OrhhsglfyeOjh+jx24M0f6xAbwy0okPu7dET+fI6GN8UXjzewuwMzXpqz/vcVujBEjXDoFK290rUnuQWuOeHWoq/S10UDYXPpUTDV1tjz67fSAaGuuMPp/4KBrye6K/MPnnPZLItFkW9om5s+tjY7GXx2lpWrQYHHFxLEjQHFm1clUX2vJL0F+pxul6GU7VL8NJ+zKcqFLh9So13qzR4EQlgTcYG7DnMHg23nUQeH2zHBuFiWhfHDfbmSQhDsezAdo3Wq/crdb9/LKW+/wHU9rLx2ZFKOikQkHX2tC0TRe631AQmmoqDj2a95360B2nIfQFg8+YJKHvzRkvX9hFz+6UJv90nFzY73xfB+CtaynpMNsN5Rs8lLG8haoud1EVhWaqQm+irGUOyrK2ljIWVVKWUjtlXmOlKhjfaLBQNZuaKcuH26gtZW5qh3OnYWu1t1ia18mBuKw2FOi7sNQxhOudJ7Cg8ghStcewsHoAV1YcxDzTYdRXHX2Tn7d661HMNR7CouqjaGBqCpk4fdVOjGd44pSuPoAMU328vNomzW22rSj22pSrWxltsRH522wincsm1DXaBNpGmyyv+Y3K89w2KWPncZW+9U1ukbSqDvjmhlihRfM7NzniWn92WX8AAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image3\",\n \"title\": \"image3\",\n \"src\": \"/static/285108d56c66afcdd2a9fa7e611441ba/a2d48/image3.png\",\n \"srcSet\": [\"/static/285108d56c66afcdd2a9fa7e611441ba/a2ead/image3.png 259w\", \"/static/285108d56c66afcdd2a9fa7e611441ba/a2d48/image3.png 447w\"],\n \"sizes\": \"(max-width: 447px) 100vw, 447px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"h1\", null, \"AFOTECs Role in Fielding Combat Capability\"), mdx(\"p\", null, \"As the Air Force's operational test agency (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \"), \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" tests and\\nevaluates new capabilities in operationally realistic environments.\\nChallenges associated with adaptive acquisition strategies,\\ncybersecurity, and game-changing technologies require that we adapt,\\nevolve, and be flexible in our approach and perspectives. We must be an\\nagile \\\"learning organization\\\" while simultaneously employing our legacy\\nof test designs, rigorous analysis, and fully transparent reporting for\\nour customers. Our charge is to deliver combat capability to the\\nwarfighter through operational testing\", \"-\", \"-accurate and balanced\\noperational truth for every system we test.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" supports urgent operational needs, middle tier of acquisition,\\nmajor capability acquisition, software acquisition, defense business\\nsystems, acquisition of services and experimentation as necessary.\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" provides \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E information and expertise to major commands\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \"), other \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" components, Air National Guard (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air National Guard\"\n }, \"ANG\"), \"), Air Force\\nReserve Command, Chief of Staff of the Air Force, Secretary of the Air\\nForce (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SECAF\"), \"), combatant commands, Office of the Secretary of Defense\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Secretary of Defense\"\n }, \"OSD\"), \"), Congress, and other government agencies.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" engages in early and continuous involvement. We execute\\nintegrated test activities by supporting development of operational\\ncapability requirements, shaping the acquisition strategy, and\\ninfluencing system design and development from program inception through\\nsuccessful fielding.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assesses and evaluates new combat capability by executing\\noperational test activities in a relevant, credible, and timely fashion.\\nTypes of test activities and reporting requirements are dependent on the\\nacquisition strategy. Examples of test activities and reporting options\\nare available in the functional guides, tools, and case studies.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#afotecs-role-in-fielding-combat-capability","title":"AFOTECs Role in Fielding Combat Capability"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/1-3-fielding-combat-capes.md"},"frontmatter":{"metaTitle":"Fielding Combat Capability","metaDescription":"AFOTEC's role"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"916a1c87-2165-5cd0-abac-2a89862a0827"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/1-5-acquisition-pathways/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/1-5-acquisition-pathways","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"a2590483-ccb9-5d11-9338-40de89299f9a","title":"Acquisition Pathways","slug":"/OT&E_Guide/1-5-acquisition-pathways"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Acquisition Pathways\",\n \"metaTitle\": \"Acquisition Pathways\",\n \"metaDescription\": \"Acquisition pathways to delivering combat capability\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"An acquisition pathway is the route of execution a program takes from\\ninception to completion. It is defined by a series of statutory and\\nregulatory activities, milestones, and decision points. Historically,\\nthe generic \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" acquisition program execution pathway was as an\\nall-encompassing set of models defined in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" 5000 series. Today, an\\nacquisition executive or portfolio manager can tailor a program-specific\\nmodel, which enables faster navigation by pre-filtering and clearly\\nidentifying processes, documents, and reviews relevant to that program's\\nacquisition type. Current acquisition pathways (depicted in Figure 1-2)\\ninclude urgent operational needs, middle tier of acquisition (MTA),\\nmajor capability acquisition, software acquisition, defense business\\nsystems, and acquisition of services. A program may use multiple\\nacquisition pathways, such as the major capability acquisition pathway\\nthat has a component being developed using the MTA pathway, and a\\nsoftware capability being developed using the software acquisition\\npathway.\"), mdx(\"p\", null, \"Figure 1\\u20112. Acquisition Pathways\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"1035px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/4371190aad1cd8e5ccc29f2409d6ce2c/60a48/image4.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"70.65637065637065%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAYAAAAvxDzwAAAACXBIWXMAABcRAAAXEQHKJvM/AAAC6klEQVQ4y11T2W7TQBT118NjkYoQpaU8oCKBivpQHiiirUpbmn134sRLFsfxktiJ4y3OdrgzTStgpLHHM3euz7nnHsGyTEiShGKhgGKxCFFsolwuI5fLo9OR4XkeDMNAq9XiccPhEP1+H7quYzAY8O/ZbIb53MdkMoYw5Ac69F2g4zg8gWHqGFkjjMdjfpHtsRh2zqZpmrAsi6+nUw++H9DahRCEIfhYLPgrTVOEQYSuaCLzq4hcNo84jvE8trvXdrubG2w27J5LP5AgxJSA8GJzfIzlckUUdJSLFdx/EfHt4zVatQ5PEMcJxnMXQRLAnbqIo5gwLGg/onuAbf9ErfoWQkSbW6rB+ugIQRRBJ3qFUgmXagbiREReysMyLUwp5rR2gQcji0wzg7Ez5mwWaYLVClSaK6r/IYQlwWaYGcKIqDEaCwos9qpQHBkNRYRt2c/1dT2Xij/hdWUI/dkUYbgm8W4gNt5B0Cgwc3mJ9PQUSRITdBuNagnzu6/ok9Lt+9+wxDo6mQcEmopesQBfkdHN5zCs1lD4cYF2XcY8yKJefw/hli7svXiJ4OwMURiQYlOoiopPny9wm5WgDiaQuw5KNQUNaYBO16bpwB4HWDPKxCpdpFivU2qfCYTVo2TYnpwgThKCH8Ckdvhxk0O+2oak9tFoa/zdlLuQe0NaD+C4Hv4fTDghZKIQqhWJktCa1acjiZiJ+0TrDcS712je7UO83Se6h6hc7aFy/YrofsAqch5biPUNjYhEFaKntjk4wIL0j2nToDp+79skygRtYwRpOEJZVpElF9W6fdRpNnoDWPOIJ9ps/0oYE6q172Nzfs571mMIezqO1Rhlw0WpZyKvjVBja/pJaeBAtH1UDA89L/yHMk/IpO92NTTJq8yT4c45S0I7IrspsgxFUahN+tzXEZ0zu6qqCk3T+JlD9twQbeYogT1cd8KNz/zK2oYlXS5T6r0eXdSevcvOWFLHsfn3k5+Z39lkHfIHipcEMHMNr9UAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image4\",\n \"title\": \"image4\",\n \"src\": \"/static/4371190aad1cd8e5ccc29f2409d6ce2c/e3189/image4.png\",\n \"srcSet\": [\"/static/4371190aad1cd8e5ccc29f2409d6ce2c/a2ead/image4.png 259w\", \"/static/4371190aad1cd8e5ccc29f2409d6ce2c/6b9fd/image4.png 518w\", \"/static/4371190aad1cd8e5ccc29f2409d6ce2c/e3189/image4.png 1035w\", \"/static/4371190aad1cd8e5ccc29f2409d6ce2c/60a48/image4.png 1325w\"],\n \"sizes\": \"(max-width: 1035px) 100vw, 1035px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"h1\", null, \"Urgent Operational Needs\"), mdx(\"p\", null, \"Urgent operational needs (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Urgent Operational Need\"\n }, \"UON\"), \") are capabilities that need to be fielded\\nin less than 2 years and are below the cost thresholds of acquisition\\ncategory (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Category\"\n }, \"ACAT\"), \") I and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Assurance (replaced by “cybersecurity”)\"\n }, \"IA\"), \" programs. The combatant commander, Chairman of\\nthe Joint Chiefs of Staff (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chairman, Joint Chiefs of Staff\"\n }, \"CJCS\"), \"), or Vice Chairman of the Joint Chiefs\\nof Staff (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vice Chairman of the Joint Chiefs of Staff\"\n }, \"VCJCS\"), \") identify an urgent operational need when executing an\\nongoing contingency operation (i.e., a Joint Urgent Operational Need\\n\", \"[\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Urgent Operational Need\"\n }, \"JUON\"), \"\", \"]\", \") or when they have an emergent need for an anticipated or\\npending contingency operation (i.e., Joint Emergent Operational Need\\n\", \"[\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Emergent Operational Need\"\n }, \"JEON\"), \"\", \"]\", \").\"), mdx(\"h1\", null, \"Middle Tier of Acquisition\"), mdx(\"p\", null, \"Two new MTA pathways provide the flexibility to rapidly prototype and\\nfield capabilities. MTA programs include rapid prototyping and rapid\\nfielding programs intended for completion within 2 to 5 years. MTA\\noperational demos offer a unique opportunity to \\\"fly before you buy\\\" by\\ninvolving operational users and testers early in the acquisition\\nprocess, before the initial production decision is made.\"), mdx(\"h2\", null, \"Rapid Prototyping\"), mdx(\"p\", null, \"Rapid prototyping is the development of fieldable prototypes that\\ndemonstrate new capabilities to meet emerging military needs. The\\nprototype must demonstrate residual operational capability in an\\noperational environment within 5 years of an approved requirement.\"), mdx(\"h2\", null, \"Rapid Fielding\"), mdx(\"p\", null, \"Rapid fielding relies heavily on technologies previously demonstrated in\\nvendor or government testing. The objective is to field production\\nquantities of new or upgraded systems that require minimal development.\\nRapid fielding programs must begin production within 6 months and be\\nfielded within 5 years of an approved requirement. Rapid fielding\\ndecisions should be based on integrated developmental and operational\\ntesting that demonstrates how the capability contributes to fulfilling\\nthe warfighter's mission or concept of operations. The test strategy\\nidentifies prior testing and specifies additional testing necessary to\\naddress differences between the tested prototype and the planned\\nproduction configuration. The lead \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \" plans and conducts an operations\\n(ops) demo with representative units, missions, and environments. Ops\\ndemos may consist of a series of incremental test events or separate\\n\\\"capstone\\\" demonstration events based on program requirements. All\\nevents should be integrated and supported by collaborative developer,\\nprogram office, developmental test, and operational test planning.\"), mdx(\"h1\", null, \"Major Capability Acquisition\"), mdx(\"p\", null, \"There are six major capability acquisition models for the following\\ntypes of programs: hardware-intensive; defense-unique\\nsoftware-intensive; incrementally-deployed software-intensive;\\naccelerated acquisition; hybrid A (hardware dominant); and hybrid B\\n(software dominant). Four are basic models that serve as examples of\\ndefense program structures tailored to the type of product being\\nacquired or to the need for accelerated acquisition. There are two\\nhybrid models that combine features of multiple basic models. Each basic\\nmodel is tailored to the dominant characteristics of the product being\\nacquired (e.g., hardware intensive products such as most weapons\\nsystems). Hybrids combine models, such as in the case of developing a\\nweapons system that requires developing related software. Acquisition\\nprograms should use these models as a starting point in structuring a\\nprogram to acquire a specific product. All models contain requirements\\nand product definition analysis, risk reduction, development, testing,\\nproduction, deployment, and sustainment phases punctuated by major\\ninvestment decisions at logical programmatic and contractual decision\\npoints.\"), mdx(\"h1\", null, \"Software Acquisition\"), mdx(\"p\", null, \"Software acquisition focuses on modern iterative software development\\ntechniques such as agile, lean, and development security operations,\\nwhich promise faster delivery of working code to the user. The goal of\\nthis pathway is to achieve continuous integration and delivery to the\\nmaximum extent possible. Since integrated testing is a critical\\ncomponent, you must identify \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"&E and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E requirements early during\\ndevelopment of the test strategy to ensure streamlined testing and\\nfaster delivery to the field.\"), mdx(\"h1\", null, \"Defense Business Systems\"), mdx(\"p\", null, \"Defense Business Systems (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Business Systems\"\n }, \"DBS\"), \") focus on information systems operated by,\\nfor, or on behalf of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \". These include financial systems, financial\\ndata feeder systems, contracting systems, logistics systems, planning\\nand budgeting systems, installation management systems, human resources\\nmanagement systems, and training and readiness systems. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Business Systems\"\n }, \"DBS\"), \" do not\\ninclude national security systems or information systems used\\nexclusively by and within the defense commissary system, exchange\\nsystem, or other instrumentality of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" conducted for the morale,\\nwelfare, and recreation of members of the armed forces using\\nnon-appropriated funds.\"), mdx(\"h1\", null, \"Acquisition of Services\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" can acquire services from private sector entities by or for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \"\\nwhen the total estimated acquisition value is at or above the simplified\\nacquisition threshold in DoDI 5000.74. This includes advisory and\\nassistance services in support of research and development or\\nconstruction activities categorized within the knowledge-based services\\nportfolio group. It is unlikely \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" would execute \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" for an\\nacquisition of service.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#urgent-operational-needs","title":"Urgent Operational Needs"},{"url":"#middle-tier-of-acquisition","title":"Middle Tier of Acquisition","items":[{"url":"#rapid-prototyping","title":"Rapid Prototyping"},{"url":"#rapid-fielding","title":"Rapid Fielding"}]},{"url":"#major-capability-acquisition","title":"Major Capability Acquisition"},{"url":"#software-acquisition","title":"Software Acquisition"},{"url":"#defense-business-systems","title":"Defense Business Systems"},{"url":"#acquisition-of-services","title":"Acquisition of Services"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/1-5-acquisition-pathways.md"},"frontmatter":{"metaTitle":"Acquisition Pathways","metaDescription":"Acquisition pathways to delivering combat capability"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"a2590483-ccb9-5d11-9338-40de89299f9a"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/1-5-acquisition-pathways","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"a2590483-ccb9-5d11-9338-40de89299f9a","title":"Acquisition Pathways","slug":"/OT&E_Guide/1-5-acquisition-pathways"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Acquisition Pathways\",\n \"metaTitle\": \"Acquisition Pathways\",\n \"metaDescription\": \"Acquisition pathways to delivering combat capability\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"An acquisition pathway is the route of execution a program takes from\\ninception to completion. It is defined by a series of statutory and\\nregulatory activities, milestones, and decision points. Historically,\\nthe generic \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" acquisition program execution pathway was as an\\nall-encompassing set of models defined in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" 5000 series. Today, an\\nacquisition executive or portfolio manager can tailor a program-specific\\nmodel, which enables faster navigation by pre-filtering and clearly\\nidentifying processes, documents, and reviews relevant to that program's\\nacquisition type. Current acquisition pathways (depicted in Figure 1-2)\\ninclude urgent operational needs, middle tier of acquisition (MTA),\\nmajor capability acquisition, software acquisition, defense business\\nsystems, and acquisition of services. A program may use multiple\\nacquisition pathways, such as the major capability acquisition pathway\\nthat has a component being developed using the MTA pathway, and a\\nsoftware capability being developed using the software acquisition\\npathway.\"), mdx(\"p\", null, \"Figure 1\\u20112. Acquisition Pathways\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"1035px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/4371190aad1cd8e5ccc29f2409d6ce2c/60a48/image4.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"70.65637065637065%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAYAAAAvxDzwAAAACXBIWXMAABcRAAAXEQHKJvM/AAAC6klEQVQ4y11T2W7TQBT118NjkYoQpaU8oCKBivpQHiiirUpbmn134sRLFsfxktiJ4y3OdrgzTStgpLHHM3euz7nnHsGyTEiShGKhgGKxCFFsolwuI5fLo9OR4XkeDMNAq9XiccPhEP1+H7quYzAY8O/ZbIb53MdkMoYw5Ac69F2g4zg8gWHqGFkjjMdjfpHtsRh2zqZpmrAsi6+nUw++H9DahRCEIfhYLPgrTVOEQYSuaCLzq4hcNo84jvE8trvXdrubG2w27J5LP5AgxJSA8GJzfIzlckUUdJSLFdx/EfHt4zVatQ5PEMcJxnMXQRLAnbqIo5gwLGg/onuAbf9ErfoWQkSbW6rB+ugIQRRBJ3qFUgmXagbiREReysMyLUwp5rR2gQcji0wzg7Ez5mwWaYLVClSaK6r/IYQlwWaYGcKIqDEaCwos9qpQHBkNRYRt2c/1dT2Xij/hdWUI/dkUYbgm8W4gNt5B0Cgwc3mJ9PQUSRITdBuNagnzu6/ok9Lt+9+wxDo6mQcEmopesQBfkdHN5zCs1lD4cYF2XcY8yKJefw/hli7svXiJ4OwMURiQYlOoiopPny9wm5WgDiaQuw5KNQUNaYBO16bpwB4HWDPKxCpdpFivU2qfCYTVo2TYnpwgThKCH8Ckdvhxk0O+2oak9tFoa/zdlLuQe0NaD+C4Hv4fTDghZKIQqhWJktCa1acjiZiJ+0TrDcS712je7UO83Se6h6hc7aFy/YrofsAqch5biPUNjYhEFaKntjk4wIL0j2nToDp+79skygRtYwRpOEJZVpElF9W6fdRpNnoDWPOIJ9ps/0oYE6q172Nzfs571mMIezqO1Rhlw0WpZyKvjVBja/pJaeBAtH1UDA89L/yHMk/IpO92NTTJq8yT4c45S0I7IrspsgxFUahN+tzXEZ0zu6qqCk3T+JlD9twQbeYogT1cd8KNz/zK2oYlXS5T6r0eXdSevcvOWFLHsfn3k5+Z39lkHfIHipcEMHMNr9UAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image4\",\n \"title\": \"image4\",\n \"src\": \"/static/4371190aad1cd8e5ccc29f2409d6ce2c/e3189/image4.png\",\n \"srcSet\": [\"/static/4371190aad1cd8e5ccc29f2409d6ce2c/a2ead/image4.png 259w\", \"/static/4371190aad1cd8e5ccc29f2409d6ce2c/6b9fd/image4.png 518w\", \"/static/4371190aad1cd8e5ccc29f2409d6ce2c/e3189/image4.png 1035w\", \"/static/4371190aad1cd8e5ccc29f2409d6ce2c/60a48/image4.png 1325w\"],\n \"sizes\": \"(max-width: 1035px) 100vw, 1035px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"h1\", null, \"Urgent Operational Needs\"), mdx(\"p\", null, \"Urgent operational needs (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Urgent Operational Need\"\n }, \"UON\"), \") are capabilities that need to be fielded\\nin less than 2 years and are below the cost thresholds of acquisition\\ncategory (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Category\"\n }, \"ACAT\"), \") I and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Assurance (replaced by “cybersecurity”)\"\n }, \"IA\"), \" programs. The combatant commander, Chairman of\\nthe Joint Chiefs of Staff (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chairman, Joint Chiefs of Staff\"\n }, \"CJCS\"), \"), or Vice Chairman of the Joint Chiefs\\nof Staff (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vice Chairman of the Joint Chiefs of Staff\"\n }, \"VCJCS\"), \") identify an urgent operational need when executing an\\nongoing contingency operation (i.e., a Joint Urgent Operational Need\\n\", \"[\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Urgent Operational Need\"\n }, \"JUON\"), \"\", \"]\", \") or when they have an emergent need for an anticipated or\\npending contingency operation (i.e., Joint Emergent Operational Need\\n\", \"[\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Emergent Operational Need\"\n }, \"JEON\"), \"\", \"]\", \").\"), mdx(\"h1\", null, \"Middle Tier of Acquisition\"), mdx(\"p\", null, \"Two new MTA pathways provide the flexibility to rapidly prototype and\\nfield capabilities. MTA programs include rapid prototyping and rapid\\nfielding programs intended for completion within 2 to 5 years. MTA\\noperational demos offer a unique opportunity to \\\"fly before you buy\\\" by\\ninvolving operational users and testers early in the acquisition\\nprocess, before the initial production decision is made.\"), mdx(\"h2\", null, \"Rapid Prototyping\"), mdx(\"p\", null, \"Rapid prototyping is the development of fieldable prototypes that\\ndemonstrate new capabilities to meet emerging military needs. The\\nprototype must demonstrate residual operational capability in an\\noperational environment within 5 years of an approved requirement.\"), mdx(\"h2\", null, \"Rapid Fielding\"), mdx(\"p\", null, \"Rapid fielding relies heavily on technologies previously demonstrated in\\nvendor or government testing. The objective is to field production\\nquantities of new or upgraded systems that require minimal development.\\nRapid fielding programs must begin production within 6 months and be\\nfielded within 5 years of an approved requirement. Rapid fielding\\ndecisions should be based on integrated developmental and operational\\ntesting that demonstrates how the capability contributes to fulfilling\\nthe warfighter's mission or concept of operations. The test strategy\\nidentifies prior testing and specifies additional testing necessary to\\naddress differences between the tested prototype and the planned\\nproduction configuration. The lead \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \" plans and conducts an operations\\n(ops) demo with representative units, missions, and environments. Ops\\ndemos may consist of a series of incremental test events or separate\\n\\\"capstone\\\" demonstration events based on program requirements. All\\nevents should be integrated and supported by collaborative developer,\\nprogram office, developmental test, and operational test planning.\"), mdx(\"h1\", null, \"Major Capability Acquisition\"), mdx(\"p\", null, \"There are six major capability acquisition models for the following\\ntypes of programs: hardware-intensive; defense-unique\\nsoftware-intensive; incrementally-deployed software-intensive;\\naccelerated acquisition; hybrid A (hardware dominant); and hybrid B\\n(software dominant). Four are basic models that serve as examples of\\ndefense program structures tailored to the type of product being\\nacquired or to the need for accelerated acquisition. There are two\\nhybrid models that combine features of multiple basic models. Each basic\\nmodel is tailored to the dominant characteristics of the product being\\nacquired (e.g., hardware intensive products such as most weapons\\nsystems). Hybrids combine models, such as in the case of developing a\\nweapons system that requires developing related software. Acquisition\\nprograms should use these models as a starting point in structuring a\\nprogram to acquire a specific product. All models contain requirements\\nand product definition analysis, risk reduction, development, testing,\\nproduction, deployment, and sustainment phases punctuated by major\\ninvestment decisions at logical programmatic and contractual decision\\npoints.\"), mdx(\"h1\", null, \"Software Acquisition\"), mdx(\"p\", null, \"Software acquisition focuses on modern iterative software development\\ntechniques such as agile, lean, and development security operations,\\nwhich promise faster delivery of working code to the user. The goal of\\nthis pathway is to achieve continuous integration and delivery to the\\nmaximum extent possible. Since integrated testing is a critical\\ncomponent, you must identify \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"&E and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E requirements early during\\ndevelopment of the test strategy to ensure streamlined testing and\\nfaster delivery to the field.\"), mdx(\"h1\", null, \"Defense Business Systems\"), mdx(\"p\", null, \"Defense Business Systems (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Business Systems\"\n }, \"DBS\"), \") focus on information systems operated by,\\nfor, or on behalf of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \". These include financial systems, financial\\ndata feeder systems, contracting systems, logistics systems, planning\\nand budgeting systems, installation management systems, human resources\\nmanagement systems, and training and readiness systems. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Business Systems\"\n }, \"DBS\"), \" do not\\ninclude national security systems or information systems used\\nexclusively by and within the defense commissary system, exchange\\nsystem, or other instrumentality of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" conducted for the morale,\\nwelfare, and recreation of members of the armed forces using\\nnon-appropriated funds.\"), mdx(\"h1\", null, \"Acquisition of Services\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" can acquire services from private sector entities by or for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \"\\nwhen the total estimated acquisition value is at or above the simplified\\nacquisition threshold in DoDI 5000.74. This includes advisory and\\nassistance services in support of research and development or\\nconstruction activities categorized within the knowledge-based services\\nportfolio group. It is unlikely \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" would execute \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" for an\\nacquisition of service.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#urgent-operational-needs","title":"Urgent Operational Needs"},{"url":"#middle-tier-of-acquisition","title":"Middle Tier of Acquisition","items":[{"url":"#rapid-prototyping","title":"Rapid Prototyping"},{"url":"#rapid-fielding","title":"Rapid Fielding"}]},{"url":"#major-capability-acquisition","title":"Major Capability Acquisition"},{"url":"#software-acquisition","title":"Software Acquisition"},{"url":"#defense-business-systems","title":"Defense Business Systems"},{"url":"#acquisition-of-services","title":"Acquisition of Services"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/1-5-acquisition-pathways.md"},"frontmatter":{"metaTitle":"Acquisition Pathways","metaDescription":"Acquisition pathways to delivering combat capability"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"a2590483-ccb9-5d11-9338-40de89299f9a"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/1-6-art-principles/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/1-6-art-principles","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"ee79253f-c411-5876-ad66-740741663bb9","title":"Adaptive Relevant Testing Principles","slug":"/OT&E_Guide/1-6-art-principles"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Adaptive Relevant Testing Principles\",\n \"metaTitle\": \"Adaptive Relevant Testing Principles\",\n \"metaDescription\": \"How to apply ART principles\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"As noted in the introduction, the focus of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" is to deliver combat\\ncapability to the warfighter at the speed of relevance. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" applies\\nthese principles to all acquisition pathways, technology demonstrations,\\nand experimentation. Combat capability is defined by a system's\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"performance\"), \", \", mdx(\"em\", {\n parentName: \"p\"\n }, \"quantity\"), \", and \", mdx(\"em\", {\n parentName: \"p\"\n }, \"speed to field\"), \". Increasing any of the\\nthree increases combat capability. Integrated testing leads to\\ndiscovering and fixing problems early, which increases \", mdx(\"em\", {\n parentName: \"p\"\n }, \"performance\"), \".\\nEarly demonstrated performance enables \", mdx(\"em\", {\n parentName: \"p\"\n }, \"speed to field\"), \". Early delivery\\nreduces costs and those cost savings lead to increased \", mdx(\"em\", {\n parentName: \"p\"\n }, \"quantity\"), \"\\nbecause the customer can purchase more systems. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" directly impacts\\nperformance, quantity, and fielding tomorrow's Air Force faster and\\nsmarter.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s application of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles is crucial to changing our focus\\nfrom an end-game operational test final exam that is late-to-need, to\\nearly involvement in continuous integrated test activities and\\nassessments that provide continuous feedback. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" replaces our former\\nphilosophy of \\\"entering\\\" an initial operational test and evaluation\\nfinal event with performing continuous \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" that reaches completion when\\ntesting meets defined \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit Criteria\"), \". We holistically integrate test as\\na single contractor, developmental, and operational test\\nteam\", \"-\", \"-independent does not mean separate or isolated. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" gathers\\ndata as a team, but assesses it independently. As an integrated test\\nteam, we collaboratively plan data collection to meet test assessment\\nand certification requirements. We test earlier and adopt approaches\\nthat embrace operationally representative as opposed to production\\nrepresentative articles, driving early discovery and early problem\\nresolution. This results in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" delivering combat capability with\\nadaptive, tailored, responsive \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities, processes, and products\\nwhile maintaining test discipline and adequacy.\"), mdx(\"h1\", null, \"Early Involvement\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Early \", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" Involvement\"), \" drives \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" engagement with a program from its\\ninception. The earlier the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" team becomes involved, the greater\\ninfluence we have on delivering combat capability and ensuring the\\nentire test community is part of a system's development. We engage early\\nin design to mitigate or eliminate operational shortfalls, and to\\ninfluence contracting actions that ensure early access to contractor\\ntest data and activities. Early involvement is more than \\\"observation\\\"\\nfrom an oversight perspective or \\\"being seated at the table\\\" as a symbol\\nof collaboration. Applying an operational perspective and conducting\\nearly, active \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" creates a \\\"find and fix early\\\" mentality, delivering\\nwarfighter capability earlier and reducing overall system costs. Early\\ndiscovery enables early fixes that, in turn, yield \\\"faster and smarter\\\"\\ndelivery of combat capability. Early involvement shapes test activities\\nto ensure relevant, credible, and timely information that addresses \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \",\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" objectives simultaneously. We design test activities\\ncollaboratively to minimize duplicative data collection and address\\nrespective test or required certification objectives.\"), mdx(\"h1\", null, \"Tailor to the Situation\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Tailor to the Situation\"), \" is the flexibility to adjust test activities\\nto enable rapid fielding of capabilities. The acquisition community is\\naccelerating product delivery with streamlined and agile approaches. We\\nadjust and tailor our planning, methodologies, execution, and reporting\\nto meet the program's unique acquisition strategy requirements. We\\ntailor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" to focus on integrated, combined test activities and early\\ndiscovery that results in earlier delivery of combat capability.\"), mdx(\"h1\", null, \"Continuous and Cumulative Feedback\"), mdx(\"p\", null, \"The \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Continuous and Cumulative Feedback\"), \" principle ensures that \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nprovides timely feedback throughout the life of a program, particularly\\nin earlier stages. The current acquisition timeline designates \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nreports at specific milestones, but with today's fast-paced\\nacquisitions, the milestone reports may be irrelevant and/or too late to\\n\\\"find and fix early\\\" system deficiencies. Instead, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" continuously\\ndelivers timely, relevant information to developers, program offices,\\nand associated stakeholders regarding our current findings as soon as\\nthey are available. We also provide reports at specified milestones,\\ndepending on the acquisition strategy. Test document deliverables may be\\ncumulative, containing all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" feedback captured prior to a particular\\nmilestone or decision point. This continuous feedback changes the\\nperception of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" as a \\\"final exam\\\" to that of a collaborative\\ninformation exchange. Thus, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" becomes a partner in system\\ndevelopment and delivering combat capability through timely independent\\nassessments.\"), mdx(\"h1\", null, \"Streamline Processes and Products\"), mdx(\"p\", null, \"The principle to \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Streamline Processes and Products\"), \" removes\\nbureaucratic and non-value-added constraints across \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \". Test teams\\nand internal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" support organizations have the flexibility to\\ncreate, modify, and eliminate processes and/or products to meet the\\nneeds of a particular test strategy, enabling combat capability delivery\\nat the speed of relevance.\"), mdx(\"h1\", null, \"Integrate and Combine Collection and Test\"), mdx(\"p\", null, \"Independent does not mean separate or isolated. The goal of the\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Integrate and Combine Collection/Test\"), \" principle is to integrate the\\nprimary test stakeholders\", \"-\", \"-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" teams\", \"-\", \"-into one unified test team.\\nThis principle is closely aligned with early \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" involvement. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nactively pursues integrated collection and data sharing among test\\ncommunities. We remove artificial barriers and maximize collaborative\\ntest activities to achieve \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" objectives. We \", mdx(\"em\", {\n parentName: \"p\"\n }, \"purposely\"), \"\\ndesign test activities to minimize duplicative data collection that\\naddresses each participant's respective test or required certification\\nobjectives. Participants assess collected data independently. This one\\nteam, one plan, one test approach enhances communication across the\\nshareholders' spectrum, and maximizes test efficiency and effectiveness\\nto yield faster and smarter delivery of combat capability.\"), mdx(\"h1\", null, \"Adaptive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is strategically and tactically \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Adaptive\"), \". Providing relevant,\\ncredible, and timely information is difficult to do in relation to\\nrapidly evolving technologies, rapid acquisition strategies, quick-look\\nprototyping, and rapid fielding decisions. Accordingly, test teams must\\nstrategically adapt testing to capture specific program requirements.\\nIndividual programs evolve significantly over time. When appropriate,\\nteams tactically adapt test activities to address specific programmatic\\nchanges. Through lessons learned, we adapt test activities that are more\\neffective and/or efficient and that yield faster and smarter delivery of\\ncombat capabilities.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#early-involvement","title":"Early Involvement"},{"url":"#tailor-to-the-situation","title":"Tailor to the Situation"},{"url":"#continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"},{"url":"#streamline-processes-and-products","title":"Streamline Processes and Products"},{"url":"#integrate-and-combine-collection-and-test","title":"Integrate and Combine Collection and Test"},{"url":"#adaptive","title":"Adaptive"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/1-6-art-principles.md"},"frontmatter":{"metaTitle":"Adaptive Relevant Testing Principles","metaDescription":"How to apply ART principles"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"ee79253f-c411-5876-ad66-740741663bb9"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/1-6-art-principles","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"ee79253f-c411-5876-ad66-740741663bb9","title":"Adaptive Relevant Testing Principles","slug":"/OT&E_Guide/1-6-art-principles"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Adaptive Relevant Testing Principles\",\n \"metaTitle\": \"Adaptive Relevant Testing Principles\",\n \"metaDescription\": \"How to apply ART principles\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"As noted in the introduction, the focus of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" is to deliver combat\\ncapability to the warfighter at the speed of relevance. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" applies\\nthese principles to all acquisition pathways, technology demonstrations,\\nand experimentation. Combat capability is defined by a system's\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"performance\"), \", \", mdx(\"em\", {\n parentName: \"p\"\n }, \"quantity\"), \", and \", mdx(\"em\", {\n parentName: \"p\"\n }, \"speed to field\"), \". Increasing any of the\\nthree increases combat capability. Integrated testing leads to\\ndiscovering and fixing problems early, which increases \", mdx(\"em\", {\n parentName: \"p\"\n }, \"performance\"), \".\\nEarly demonstrated performance enables \", mdx(\"em\", {\n parentName: \"p\"\n }, \"speed to field\"), \". Early delivery\\nreduces costs and those cost savings lead to increased \", mdx(\"em\", {\n parentName: \"p\"\n }, \"quantity\"), \"\\nbecause the customer can purchase more systems. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" directly impacts\\nperformance, quantity, and fielding tomorrow's Air Force faster and\\nsmarter.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s application of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles is crucial to changing our focus\\nfrom an end-game operational test final exam that is late-to-need, to\\nearly involvement in continuous integrated test activities and\\nassessments that provide continuous feedback. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" replaces our former\\nphilosophy of \\\"entering\\\" an initial operational test and evaluation\\nfinal event with performing continuous \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" that reaches completion when\\ntesting meets defined \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit Criteria\"), \". We holistically integrate test as\\na single contractor, developmental, and operational test\\nteam\", \"-\", \"-independent does not mean separate or isolated. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" gathers\\ndata as a team, but assesses it independently. As an integrated test\\nteam, we collaboratively plan data collection to meet test assessment\\nand certification requirements. We test earlier and adopt approaches\\nthat embrace operationally representative as opposed to production\\nrepresentative articles, driving early discovery and early problem\\nresolution. This results in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" delivering combat capability with\\nadaptive, tailored, responsive \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities, processes, and products\\nwhile maintaining test discipline and adequacy.\"), mdx(\"h1\", null, \"Early Involvement\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Early \", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" Involvement\"), \" drives \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" engagement with a program from its\\ninception. The earlier the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" team becomes involved, the greater\\ninfluence we have on delivering combat capability and ensuring the\\nentire test community is part of a system's development. We engage early\\nin design to mitigate or eliminate operational shortfalls, and to\\ninfluence contracting actions that ensure early access to contractor\\ntest data and activities. Early involvement is more than \\\"observation\\\"\\nfrom an oversight perspective or \\\"being seated at the table\\\" as a symbol\\nof collaboration. Applying an operational perspective and conducting\\nearly, active \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" creates a \\\"find and fix early\\\" mentality, delivering\\nwarfighter capability earlier and reducing overall system costs. Early\\ndiscovery enables early fixes that, in turn, yield \\\"faster and smarter\\\"\\ndelivery of combat capability. Early involvement shapes test activities\\nto ensure relevant, credible, and timely information that addresses \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \",\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" objectives simultaneously. We design test activities\\ncollaboratively to minimize duplicative data collection and address\\nrespective test or required certification objectives.\"), mdx(\"h1\", null, \"Tailor to the Situation\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Tailor to the Situation\"), \" is the flexibility to adjust test activities\\nto enable rapid fielding of capabilities. The acquisition community is\\naccelerating product delivery with streamlined and agile approaches. We\\nadjust and tailor our planning, methodologies, execution, and reporting\\nto meet the program's unique acquisition strategy requirements. We\\ntailor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" to focus on integrated, combined test activities and early\\ndiscovery that results in earlier delivery of combat capability.\"), mdx(\"h1\", null, \"Continuous and Cumulative Feedback\"), mdx(\"p\", null, \"The \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Continuous and Cumulative Feedback\"), \" principle ensures that \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nprovides timely feedback throughout the life of a program, particularly\\nin earlier stages. The current acquisition timeline designates \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nreports at specific milestones, but with today's fast-paced\\nacquisitions, the milestone reports may be irrelevant and/or too late to\\n\\\"find and fix early\\\" system deficiencies. Instead, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" continuously\\ndelivers timely, relevant information to developers, program offices,\\nand associated stakeholders regarding our current findings as soon as\\nthey are available. We also provide reports at specified milestones,\\ndepending on the acquisition strategy. Test document deliverables may be\\ncumulative, containing all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" feedback captured prior to a particular\\nmilestone or decision point. This continuous feedback changes the\\nperception of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" as a \\\"final exam\\\" to that of a collaborative\\ninformation exchange. Thus, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" becomes a partner in system\\ndevelopment and delivering combat capability through timely independent\\nassessments.\"), mdx(\"h1\", null, \"Streamline Processes and Products\"), mdx(\"p\", null, \"The principle to \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Streamline Processes and Products\"), \" removes\\nbureaucratic and non-value-added constraints across \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \". Test teams\\nand internal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" support organizations have the flexibility to\\ncreate, modify, and eliminate processes and/or products to meet the\\nneeds of a particular test strategy, enabling combat capability delivery\\nat the speed of relevance.\"), mdx(\"h1\", null, \"Integrate and Combine Collection and Test\"), mdx(\"p\", null, \"Independent does not mean separate or isolated. The goal of the\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Integrate and Combine Collection/Test\"), \" principle is to integrate the\\nprimary test stakeholders\", \"-\", \"-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" teams\", \"-\", \"-into one unified test team.\\nThis principle is closely aligned with early \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" involvement. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nactively pursues integrated collection and data sharing among test\\ncommunities. We remove artificial barriers and maximize collaborative\\ntest activities to achieve \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" objectives. We \", mdx(\"em\", {\n parentName: \"p\"\n }, \"purposely\"), \"\\ndesign test activities to minimize duplicative data collection that\\naddresses each participant's respective test or required certification\\nobjectives. Participants assess collected data independently. This one\\nteam, one plan, one test approach enhances communication across the\\nshareholders' spectrum, and maximizes test efficiency and effectiveness\\nto yield faster and smarter delivery of combat capability.\"), mdx(\"h1\", null, \"Adaptive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is strategically and tactically \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Adaptive\"), \". Providing relevant,\\ncredible, and timely information is difficult to do in relation to\\nrapidly evolving technologies, rapid acquisition strategies, quick-look\\nprototyping, and rapid fielding decisions. Accordingly, test teams must\\nstrategically adapt testing to capture specific program requirements.\\nIndividual programs evolve significantly over time. When appropriate,\\nteams tactically adapt test activities to address specific programmatic\\nchanges. Through lessons learned, we adapt test activities that are more\\neffective and/or efficient and that yield faster and smarter delivery of\\ncombat capabilities.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#early-involvement","title":"Early Involvement"},{"url":"#tailor-to-the-situation","title":"Tailor to the Situation"},{"url":"#continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"},{"url":"#streamline-processes-and-products","title":"Streamline Processes and Products"},{"url":"#integrate-and-combine-collection-and-test","title":"Integrate and Combine Collection and Test"},{"url":"#adaptive","title":"Adaptive"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/1-6-art-principles.md"},"frontmatter":{"metaTitle":"Adaptive Relevant Testing Principles","metaDescription":"How to apply ART principles"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"ee79253f-c411-5876-ad66-740741663bb9"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/2-test-lifecycle-overview/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/2-test-lifecycle-overview","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"9b6a1db0-15c1-5059-b854-50aa0bbefefe","title":"Test Lifecycle Overview","slug":"/OT&E_Guide/2-test-lifecycle-overview"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Test Lifecycle Overview\",\n \"metaTitle\": \"Test Lifecycle Overview\",\n \"metaDescription\": \"Provides an overview of the test lifecycle, or 'life of a test.'\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"This chapter addresses activities and processes across the test\\nlifecycle. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" begins contributing to delivery of combat capability\\nas early as possible. From pie-in-the-sky ideas to existing commercial\\nsolutions, we contribute operational-related insight to potential,\\ninformal, and formal programs. Figure 2-1 depicts the application of the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles applied throughout an acquisition program.\"), mdx(\"p\", null, \"Figure 2\\u20111. Test Lifecycle Macro\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"984px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/4af472bdc7e3b2a881006305bacafd82/0b6f4/image5.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"42.857142857142854%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAJCAYAAAAywQxIAAAACXBIWXMAABYlAAAWJQFJUiTwAAABu0lEQVQoz31Ra3OiQBD0//+WnKmYVGnlTCp3l+SML1SQp6iAgLgoAUFjTukb1oTcp5uqqe5hZnt7h8qtxHAnh2h+YKM3x82zguunMeodk3NeP0qoPYol/z7yca+s0Rwz3MsMtf4S4faASrVl46broD7wUB8ucdWaoPpLxrefY1w+68QVXPyQcPEgElLS96J39TJDrUNnews0hj4u2w6WUYaKIHvQLIZ5EMNZZxAnLgaajaFuE1qQph76ypxqB5JZ8BnnAmFvbEK1AizWO1irBFFCgqAwbIZqYwTJCmGudpgEWZlt2UJXddDXXbSkKaT510yBup8iTPb4czzieDqdBYMwQW9kQ3UiGDSo+1ueBZesNfqGh4EZQDB8qG4MfZme+4QaYZy9FzLIKSt5nuMzCusa3VgMTtkemhfjt2jiriXi9knAQ1cmpx7vFQ4NLpwiSg9nQdLigoXm6ZTDYhkUb8tvHZgrdNQF2oqDruaW/EW2OZfsDRdT3ATx7r00VToskCVvWGz28CJy4G74wnWH8dTsVVkrM59+YgLv9WOeVsZeU+zfDucdfj07B7f7zxr+F5/nBMVDrakiJNG//0eRiEZXHw8AAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image5\",\n \"title\": \"image5\",\n \"src\": \"/static/4af472bdc7e3b2a881006305bacafd82/0b6f4/image5.png\",\n \"srcSet\": [\"/static/4af472bdc7e3b2a881006305bacafd82/a2ead/image5.png 259w\", \"/static/4af472bdc7e3b2a881006305bacafd82/6b9fd/image5.png 518w\", \"/static/4af472bdc7e3b2a881006305bacafd82/0b6f4/image5.png 984w\"],\n \"sizes\": \"(max-width: 984px) 100vw, 984px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"p\", null, \"Combat capability may be delivered at any time during the test\\nlifecycle. Figure 2-2 shows the test lifecycle, which is a macroscopic\\nplanning, executing, and reporting test activity that includes\\ninvolvement, test strategy, test activity, feedback, and exit\\nactivities. This lifecycle has two focus areas: the overall system under\\ntest (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \") being developed to meet the identified capability need and\\nthe lower incremental or modular development activity that might deliver\\nsome useful capability.\"), mdx(\"p\", null, \"Involvement begins early and is continuous and integrated from start to\\nfinish. The maturity of an experimentation or program system defines\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s resource investment. Experimentation or informal programs\\nrarely require a significant resource investment from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", and test\\nteam interactions might be informal. In cases where investment of\\nsignificant resources is required, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" issues a formal involvement\\ndocument. See Section 3.1 for involvement details.\"), mdx(\"p\", null, \"Figure 2\\u20112. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Process Overview\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"984px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/5d033c80356aade0c5e88be206fd9a9f/0b6f4/image6.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"57.14285714285714%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAYAAAB/Ca1DAAAACXBIWXMAACHVAAAh1QEEnLSdAAADWklEQVQozz2Ra2hbBRTHzygo3TrnY3PODir1w6oVHZ1MHLZusMImTLAMP8zWQZE590ERx1A/uDnwgwykU+aDoW0TnRstbG3Xsrk0r5ube3OT9N6kTfO4eXR53NybR5uYpknuTe7xZgU//DkP/vzOORx4duvwHgBooe0sRJfndq5ljUc45nbvpP6vPt4/21cpmvqu3rQOjEzoBq9NjFz69c71j74dNQ5gNQNWawDYpQi4PRFwkCGIxZIaCt7ee0M/08vz4juRMH1lo8ShJLgwylswI7ixkOeQj1rf04xb9r985nj3vlO7jB7iaQftv8BQ/h+4Jf7IAhc6QZP+n0LB2GCTuIO2ey8n4lnR61ucdDFB0WEP5NLSYpq0+jOExVe6bZj5/PVDJ18FGH6j/9jwoT+mJ45RJJ+yGn3o5MLfMa7wddISQN9SbBZ2bDndCbBrO1YRrnxzqfX44fNvnTh6/sDFCyMv9vd+1Xvm9PevfH1uuLWrvf/xs59+efj9k18880EftPytf9D9+29zB6MB9xM3dbO7f/lx5s0/x+7thSdbhjp2th1ta64qxs2AiCDEZx5FgNc6m/3NHB7TtFtTa7POpQnICCQU8/9ATpyHfIaFBacD4OdrY09dvni102TztPq8lnfzGfLGWs46mhMJfTximlgJGyZzknW8kCXHIsHZWznJPF7Mk6Orkk2Xis/r0on58VTcqBNTpJ5bsHTDNjj1XFfHULuTnNSmEZ81H8K6PJiML6CUcSPn8mLIv4iFAoPRMIsUweHDFS9msxQGl/2adxlTCR82ajSmHtoOwnb4cH9Xx2A7ZbkFhZzlrCSwmslfi0VYRRBcdcLkqTMUq2SylMKH3HXWGVBiEa+yuuZQgn5eMRs8ipTm60qVkoUE2dME9rz0wuDzDDkNxVX6k2TMgKxjqp6IPFDLBUINLN5VV0L3VGXDrmKdUhs1UkWFUhEZNS+Z1H/zFrW2bsOG7GgIcdsBaIOhfZvAKQ1InROTZmRsM41kzIhYZ7BWph5FrDtQlR2ICoNKhcbSmg0rJTtW1zdVLpJqOqkBt8LANu3kPTbzHZBS5MdC3IwB7/1KXiRq8gYtV8u0XClR/6u6Tsvlgl3mmDmZmJ+Snfa7Nbt5Wo4EDbWsSPf8B3lfSkoMNFayAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image6\",\n \"title\": \"image6\",\n \"src\": \"/static/5d033c80356aade0c5e88be206fd9a9f/0b6f4/image6.png\",\n \"srcSet\": [\"/static/5d033c80356aade0c5e88be206fd9a9f/a2ead/image6.png 259w\", \"/static/5d033c80356aade0c5e88be206fd9a9f/6b9fd/image6.png 518w\", \"/static/5d033c80356aade0c5e88be206fd9a9f/0b6f4/image6.png 984w\"],\n \"sizes\": \"(max-width: 984px) 100vw, 984px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"p\", null, \"A test strategy is always required when \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" issues an involvement\\nletter. The test team tailors the test strategy to the experimentation\\nor acquisition strategy, and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s senior leaders approve it. Then,\\nthey update and adapt the strategy to take advantage of what we learn\\nduring the test lifecycle. The test strategy also includes \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit\\nCriteria\"), \" to determine when final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities are complete. See\\nSection 3.3 for test strategy details.\"), mdx(\"p\", null, \"An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct is developed to embody what is needed to determine a\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"'s overall effectiveness and suitability. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct provides\\nthe test team context and defines the bounds within which they will\\nprovide continuous feedback.\"), mdx(\"p\", null, \"Typically, system development begins sometime after the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct\\nhas been developed. System development is accomplished within the\\ncontext of the acquisition strategy put together by the program office.\\nA significant amount of time may pass during system development during\\nwhich the test team can refine \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"-level planning as well as look for\\nopportunities to provide operational feedback to the developer and/or\\nuser.\"), mdx(\"p\", null, \"Detailed test activities are included as part of the test strategy to\\nbetter inform delivery of combat capability. The goal of these\\ncollaborative activities is to minimize duplicative data collection\\nwhile preserving independent evaluation of results. The test team\\nupdates and adapts test activities to take advantage of learning during\\nthe test lifecycle. Section 4.2 contains test activity details.\\nContinuous and cumulative feedback is a collaborative information\\nexchange that occurs throughout the test lifecycle as warranted.\\nContinuous feedback during integrated testing is fundamental to\\nreporting discovery of operationally relevant information early and\\ndelivering capability at the speed of relevance.\"), mdx(\"p\", null, \"Eventually, system development will be finished and it will be time to\\ntransition to execution of the final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E. This is the point at which\\nthe test team can look at all of the data that has been collected during\\nthe continuous system development portion of the program and determine\\nif that data is useable for the final determination of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \". The final\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E execution period is used to collect only the data that has not\\nalready been collected or that must be re-collected because there were\\nsystem changes or other reasons that render the data unusable.\"), mdx(\"p\", null, \"Finally, the test team will provide the final determination of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \". This\\nis the final activity performed when concluding involvement in a\\nprogram. This activity might include completion and publication of a\\nfinal report, deactivation of an organizational unit, or transfer of\\nassets, as described in Chapter 5.\"), mdx(\"p\", null, \"Throughout the test lifecycle, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is a partner in system\\ndevelopment. We test earlier, faster, and smarter. With timely\\nindependent assessments, we discover early, fix early, inform\\nstakeholders, and deliver combat capability.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OT&E_Guide/2-test-lifecycle-overview.md"},"frontmatter":{"metaTitle":"Test Lifecycle Overview","metaDescription":"Provides an overview of the test lifecycle, or 'life of a test.'"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"9b6a1db0-15c1-5059-b854-50aa0bbefefe"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/2-test-lifecycle-overview","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"9b6a1db0-15c1-5059-b854-50aa0bbefefe","title":"Test Lifecycle Overview","slug":"/OT&E_Guide/2-test-lifecycle-overview"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Test Lifecycle Overview\",\n \"metaTitle\": \"Test Lifecycle Overview\",\n \"metaDescription\": \"Provides an overview of the test lifecycle, or 'life of a test.'\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"This chapter addresses activities and processes across the test\\nlifecycle. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" begins contributing to delivery of combat capability\\nas early as possible. From pie-in-the-sky ideas to existing commercial\\nsolutions, we contribute operational-related insight to potential,\\ninformal, and formal programs. Figure 2-1 depicts the application of the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles applied throughout an acquisition program.\"), mdx(\"p\", null, \"Figure 2\\u20111. Test Lifecycle Macro\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"984px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/4af472bdc7e3b2a881006305bacafd82/0b6f4/image5.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"42.857142857142854%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAJCAYAAAAywQxIAAAACXBIWXMAABYlAAAWJQFJUiTwAAABu0lEQVQoz31Ra3OiQBD0//+WnKmYVGnlTCp3l+SML1SQp6iAgLgoAUFjTukb1oTcp5uqqe5hZnt7h8qtxHAnh2h+YKM3x82zguunMeodk3NeP0qoPYol/z7yca+s0Rwz3MsMtf4S4faASrVl46broD7wUB8ucdWaoPpLxrefY1w+68QVXPyQcPEgElLS96J39TJDrUNnews0hj4u2w6WUYaKIHvQLIZ5EMNZZxAnLgaajaFuE1qQph76ypxqB5JZ8BnnAmFvbEK1AizWO1irBFFCgqAwbIZqYwTJCmGudpgEWZlt2UJXddDXXbSkKaT510yBup8iTPb4czzieDqdBYMwQW9kQ3UiGDSo+1ueBZesNfqGh4EZQDB8qG4MfZme+4QaYZy9FzLIKSt5nuMzCusa3VgMTtkemhfjt2jiriXi9knAQ1cmpx7vFQ4NLpwiSg9nQdLigoXm6ZTDYhkUb8tvHZgrdNQF2oqDruaW/EW2OZfsDRdT3ATx7r00VToskCVvWGz28CJy4G74wnWH8dTsVVkrM59+YgLv9WOeVsZeU+zfDucdfj07B7f7zxr+F5/nBMVDrakiJNG//0eRiEZXHw8AAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image5\",\n \"title\": \"image5\",\n \"src\": \"/static/4af472bdc7e3b2a881006305bacafd82/0b6f4/image5.png\",\n \"srcSet\": [\"/static/4af472bdc7e3b2a881006305bacafd82/a2ead/image5.png 259w\", \"/static/4af472bdc7e3b2a881006305bacafd82/6b9fd/image5.png 518w\", \"/static/4af472bdc7e3b2a881006305bacafd82/0b6f4/image5.png 984w\"],\n \"sizes\": \"(max-width: 984px) 100vw, 984px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"p\", null, \"Combat capability may be delivered at any time during the test\\nlifecycle. Figure 2-2 shows the test lifecycle, which is a macroscopic\\nplanning, executing, and reporting test activity that includes\\ninvolvement, test strategy, test activity, feedback, and exit\\nactivities. This lifecycle has two focus areas: the overall system under\\ntest (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \") being developed to meet the identified capability need and\\nthe lower incremental or modular development activity that might deliver\\nsome useful capability.\"), mdx(\"p\", null, \"Involvement begins early and is continuous and integrated from start to\\nfinish. The maturity of an experimentation or program system defines\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s resource investment. Experimentation or informal programs\\nrarely require a significant resource investment from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", and test\\nteam interactions might be informal. In cases where investment of\\nsignificant resources is required, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" issues a formal involvement\\ndocument. See Section 3.1 for involvement details.\"), mdx(\"p\", null, \"Figure 2\\u20112. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Process Overview\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"984px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/5d033c80356aade0c5e88be206fd9a9f/0b6f4/image6.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"57.14285714285714%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAYAAAB/Ca1DAAAACXBIWXMAACHVAAAh1QEEnLSdAAADWklEQVQozz2Ra2hbBRTHzygo3TrnY3PODir1w6oVHZ1MHLZusMImTLAMP8zWQZE590ERx1A/uDnwgwykU+aDoW0TnRstbG3Xsrk0r5ube3OT9N6kTfO4eXR53NybR5uYpknuTe7xZgU//DkP/vzOORx4duvwHgBooe0sRJfndq5ljUc45nbvpP6vPt4/21cpmvqu3rQOjEzoBq9NjFz69c71j74dNQ5gNQNWawDYpQi4PRFwkCGIxZIaCt7ee0M/08vz4juRMH1lo8ShJLgwylswI7ixkOeQj1rf04xb9r985nj3vlO7jB7iaQftv8BQ/h+4Jf7IAhc6QZP+n0LB2GCTuIO2ey8n4lnR61ucdDFB0WEP5NLSYpq0+jOExVe6bZj5/PVDJ18FGH6j/9jwoT+mJ45RJJ+yGn3o5MLfMa7wddISQN9SbBZ2bDndCbBrO1YRrnxzqfX44fNvnTh6/sDFCyMv9vd+1Xvm9PevfH1uuLWrvf/xs59+efj9k18880EftPytf9D9+29zB6MB9xM3dbO7f/lx5s0/x+7thSdbhjp2th1ta64qxs2AiCDEZx5FgNc6m/3NHB7TtFtTa7POpQnICCQU8/9ATpyHfIaFBacD4OdrY09dvni102TztPq8lnfzGfLGWs46mhMJfTximlgJGyZzknW8kCXHIsHZWznJPF7Mk6Orkk2Xis/r0on58VTcqBNTpJ5bsHTDNjj1XFfHULuTnNSmEZ81H8K6PJiML6CUcSPn8mLIv4iFAoPRMIsUweHDFS9msxQGl/2adxlTCR82ajSmHtoOwnb4cH9Xx2A7ZbkFhZzlrCSwmslfi0VYRRBcdcLkqTMUq2SylMKH3HXWGVBiEa+yuuZQgn5eMRs8ipTm60qVkoUE2dME9rz0wuDzDDkNxVX6k2TMgKxjqp6IPFDLBUINLN5VV0L3VGXDrmKdUhs1UkWFUhEZNS+Z1H/zFrW2bsOG7GgIcdsBaIOhfZvAKQ1InROTZmRsM41kzIhYZ7BWph5FrDtQlR2ICoNKhcbSmg0rJTtW1zdVLpJqOqkBt8LANu3kPTbzHZBS5MdC3IwB7/1KXiRq8gYtV8u0XClR/6u6Tsvlgl3mmDmZmJ+Snfa7Nbt5Wo4EDbWsSPf8B3lfSkoMNFayAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image6\",\n \"title\": \"image6\",\n \"src\": \"/static/5d033c80356aade0c5e88be206fd9a9f/0b6f4/image6.png\",\n \"srcSet\": [\"/static/5d033c80356aade0c5e88be206fd9a9f/a2ead/image6.png 259w\", \"/static/5d033c80356aade0c5e88be206fd9a9f/6b9fd/image6.png 518w\", \"/static/5d033c80356aade0c5e88be206fd9a9f/0b6f4/image6.png 984w\"],\n \"sizes\": \"(max-width: 984px) 100vw, 984px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"p\", null, \"A test strategy is always required when \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" issues an involvement\\nletter. The test team tailors the test strategy to the experimentation\\nor acquisition strategy, and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s senior leaders approve it. Then,\\nthey update and adapt the strategy to take advantage of what we learn\\nduring the test lifecycle. The test strategy also includes \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit\\nCriteria\"), \" to determine when final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities are complete. See\\nSection 3.3 for test strategy details.\"), mdx(\"p\", null, \"An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct is developed to embody what is needed to determine a\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"'s overall effectiveness and suitability. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct provides\\nthe test team context and defines the bounds within which they will\\nprovide continuous feedback.\"), mdx(\"p\", null, \"Typically, system development begins sometime after the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct\\nhas been developed. System development is accomplished within the\\ncontext of the acquisition strategy put together by the program office.\\nA significant amount of time may pass during system development during\\nwhich the test team can refine \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"-level planning as well as look for\\nopportunities to provide operational feedback to the developer and/or\\nuser.\"), mdx(\"p\", null, \"Detailed test activities are included as part of the test strategy to\\nbetter inform delivery of combat capability. The goal of these\\ncollaborative activities is to minimize duplicative data collection\\nwhile preserving independent evaluation of results. The test team\\nupdates and adapts test activities to take advantage of learning during\\nthe test lifecycle. Section 4.2 contains test activity details.\\nContinuous and cumulative feedback is a collaborative information\\nexchange that occurs throughout the test lifecycle as warranted.\\nContinuous feedback during integrated testing is fundamental to\\nreporting discovery of operationally relevant information early and\\ndelivering capability at the speed of relevance.\"), mdx(\"p\", null, \"Eventually, system development will be finished and it will be time to\\ntransition to execution of the final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E. This is the point at which\\nthe test team can look at all of the data that has been collected during\\nthe continuous system development portion of the program and determine\\nif that data is useable for the final determination of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \". The final\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E execution period is used to collect only the data that has not\\nalready been collected or that must be re-collected because there were\\nsystem changes or other reasons that render the data unusable.\"), mdx(\"p\", null, \"Finally, the test team will provide the final determination of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \". This\\nis the final activity performed when concluding involvement in a\\nprogram. This activity might include completion and publication of a\\nfinal report, deactivation of an organizational unit, or transfer of\\nassets, as described in Chapter 5.\"), mdx(\"p\", null, \"Throughout the test lifecycle, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is a partner in system\\ndevelopment. We test earlier, faster, and smarter. With timely\\nindependent assessments, we discover early, fix early, inform\\nstakeholders, and deliver combat capability.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OT&E_Guide/2-test-lifecycle-overview.md"},"frontmatter":{"metaTitle":"Test Lifecycle Overview","metaDescription":"Provides an overview of the test lifecycle, or 'life of a test.'"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"9b6a1db0-15c1-5059-b854-50aa0bbefefe"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/3-1-involvement-decision/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/3-1-involvement-decision","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"273bd704-aac8-5277-aa7f-cf5039ef23b3","title":"Involvement Decision","slug":"/OT&E_Guide/3-1-involvement-decision"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Involvement Decision\",\n \"metaTitle\": \"Involvement Decision\",\n \"metaDescription\": \"Test lifecycle: Involvement Decision\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"h1\", null, \"Program Identification\"), mdx(\"p\", null, \"Program identification is the initial step when beginning an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nprogram. We establish initial contact with program sponsors and\\ndevelopers (e.g., MAJCOMs, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Material Command\"\n }, \"AFMC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Life Cycle Management Center\"\n }, \"AFLCMC\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Space Command\"\n }, \"AFSPC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space and Missile Systems Center\"\n }, \"SMC\"), \", joint commands) at\\nthe Detachment or corresponding \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" level. Usually, a program sponsor or\\ndeveloper puts out \\\"feelers\\\" to gain a sense of whether the timing and\\ncosts of conducting operational testing are feasible, which indicates an\\ninvolvement is pending. One of the first efforts is to determine when a\\nformal involvement decision is needed. A-3 is the clearinghouse for new\\nprogram involvements\"), mdx(\"h1\", null, \"Program Initiation and Involvement Decision\"), mdx(\"p\", null, \"Typically, involvement decisions are needed prior to participating in\\ntest-planning activities that require significant resources or formal\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" involvement (e.g., conducting an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \" meeting or developing a\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \"). It is important that the Detachment identify the need-by date for\\nan involvement so the involvement package is signed on time to support\\nprogram efforts. The Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" is authorized to apportion \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nfunds to support early pre-involvement activities until \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" makes an\\ninvolvement decision and allocates dedicated funds.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3 begins developing and coordinating an\\ninvolvement/non-involvement package to staff based upon which Detachment\\nwill have \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" responsibility for the program. A-3 may request information\\ndirectly from the program office, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Detachments, and other external\\nPOCs to decide whether we should involve/non-involve. At a minimum, an\\ninvolvement package includes an involvement bullet background paper\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Involvement Bullet Background Paper\"\n }, \"IBBP\"), \"), an involvement/non-involvement letter, and an initial tasking\\norder (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \") when involving. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" will sign the letter and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \",\\nthen send the letter to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" with courtesy copies to the sponsoring\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" and program office. A-3 establishes the format for documents\\nrequired in the involvement/non-involvement package. Using the program\\ncost estimator, an initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" is required within 60 days after the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"'s signature on the involvement letter and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \".\"), mdx(\"p\", null, \"Before formal involvement, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" initiates a program and establishes a\\nTest Program Management (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \") page on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Secure Internet Protocol Router Network\"\n }, \"NIPRNet\"), \" (and SIPRNet, if needed)\\nwith appropriate folders on network drives, and identification of POCs.\\nThe status of a program's acquisition strategy, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", and capability\\nrequirements documents are determined and posted on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \" page. At the\\nconclusion of program initiation, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will either recommend\\ninvolvement and initiate the process, or recommend non-involvement.\"), mdx(\"p\", null, \"Test resource planning begins after \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" establishes its formal\\ninvolvement in programs of record, technology demonstrations, and\\nexperiments. During this phase, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principle of early \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\ninvolvement is key. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" should make involvement determinations as\\nearly as possible. Once \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is involved, test teams should begin\\nexecuting foundational actions that enable early participation. These\\ninclude engaging other agencies to become a recognized member of\\nintegrated planning forums and initiating program research and study to\\ninfluence acquisition strategies, capability requirements, employment\\nand support concepts, and requests for proposal (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Request for Proposal\"\n }, \"RFP\"), \"). Early involvement\\nallows \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" to establish strong partnerships with external\\nstakeholders and start building trust between various organizations.\"), mdx(\"p\", null, \"With exceptions, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" recommends involvement in a program based on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \"\\n99-103 guidance. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" involves when it is the default operational test\\norganization or when it accepts a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \"'s request. The involvement\\nletter notifies external agencies and key personnel receive the initial\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \", which presents an estimated timeline of activities they are tasked\\nto complete. Table 3-1 contains the process for staffing an involvement\\npackage.\"), mdx(\"p\", null, \"Table 3\\u20111. Involvement Package Staffing\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Step\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Activity\"))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"1\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"A-3 drafts the \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Involvement Letter\"\n }, \"IL\"), \", \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" and \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Involvement Bullet Background Paper\"\n }, \"IBBP\"), \" with support from the executing Detachment\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"A-3 submits the \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Involvement Letter\"\n }, \"IL\"), \", \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" and \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Involvement Bullet Background Paper\"\n }, \"IBBP\"), \" for 2-ltr coordination\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"The A-3 sends the involvement package to \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Commander’s Action Group Office Symbol\"\n }, \"CCX\"), \"\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"4\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Once approved by \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \", \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Commander’s Action Group Office Symbol\"\n }, \"CCX\"), \" date stamps the \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Involvement Letter\"\n }, \"IL\"), \", electronically date/time stamp and number the \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" and forwards both to A-3 for posting to the appropriate Test Program Management page. \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/DS will send the \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Involvement Letter\"\n }, \"IL\"), \" to the appropriate owning organization of the program as well as \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" and \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \"\")))), mdx(\"h1\", null, \"Establishing External Points of Contact\"), mdx(\"p\", null, \"Immediately after \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" involves in a program, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test director\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \") will open and maintain channels of communication with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" focal\\npoints, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Air Force\"\n }, \"USAF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \", the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" action officer (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \"), the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Element Monitor\"\n }, \"PEM\"), \", program\\noffice, and the responsible \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Material Command\"\n }, \"AFMC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Life Cycle Management Center\"\n }, \"AFLCMC\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Space Command\"\n }, \"AFSPC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space and Missile Systems Center\"\n }, \"SMC\"), \" office. Before\\nintegrated test and evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E), the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" should establish an\\neffective relationship with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"&E \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \". The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" ensures parties\\naddress operational requirements during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E to allow early\\nidentification of problems and provide recommended fixes ahead of\\nacquisition decisions or milestones.\"), mdx(\"h1\", null, \"Establishing a Relationship with Director of Operational Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" is the principal staff assistant and senior advisor to the\\nSecretary of Defense (SecDef) on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" is responsible for the\\nfollowing:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Issuing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E policy and procedures\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Reviewing and analyzing results of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E conducted for each major \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \"\\nacquisition program\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Providing independent assessments to SecDef, the Under Secretary of\\nDefense for Acquisition, Technology and Logistics, and Congress\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Making budgetary and financial recommendations to the SecDef\\nregarding \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Overseeing major \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" acquisition programs to ensure \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E is adequate\\nto confirm operational effectiveness and suitability of the system\\nfor use in combat\"))), mdx(\"p\", null, \"The key tenet to remember in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s relationship with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" is that\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not work for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \", but we must work with them. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" does\\napprove (per \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" 5000.02 Enclosure 5 and Title 10 where approval of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nplan adequacy \\\"in writing\\\" is required) all program test plans on\\noversight. It is essential that we have frequent interchanges with their\\nAOs on all planning, execution, and reporting aspects of our test\\nprograms. Thus, it is in our best interest to maintain a healthy working\\nrelationship. Early in a program, the Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" should\\nidentify and meet with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \" (generally an O-6, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"General Schedule\"\n }, \"GS\"), \"-15) assigned\\nto the program and communicate with them frequently. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" expects the\\nappropriate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" or A-staff directorate to address\\nconflicts with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" policies and processes.\"), mdx(\"h1\", null, \"Joint Capabilities Integration and Development System\"), mdx(\"p\", null, \"The principal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" decision support processes for transforming military\\nforces in support of national military and defense strategies are the\\nJoint Capabilities Integration and Development System (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capabilities Integration and Development System\"\n }, \"JCIDS\"), \"), Defense\\nAcquisition System, and Planning, Programming, Budgeting and Execution\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Planning, Programming, Budgeting, and Execution\"\n }, \"PPBE\"), \"). Procedures established in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capabilities Integration and Development System\"\n }, \"JCIDS\"), \" support the Chairman and the\\nJoint Requirements Oversight Council (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Requirements Oversight Council\"\n }, \"JROC\"), \") when advising the SecDef\\nregarding identification, assessment, and prioritization of Joint\\nmilitary capability needs. Validated and approved \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capabilities Integration and Development System\"\n }, \"JCIDS\"), \"' documents\\nprovide the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Requirements Oversight Council\"\n }, \"JROC\"), \"'s advice and assessment and ensure the Joint force has\\ncapabilities needed to perform across the range of military operations.\"), mdx(\"h2\", null, \"\", mdx(\"abbr\", {\n parentName: \"h2\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Involvement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s involvement in the Joint requirements process includes the\\ninitial capabilities document (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \")/information system (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System\"\n }, \"IS\"), \") \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \" and the\\ncapabilities development document (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \")/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System Capability Development Document\"\n }, \"IS CDD\"), \". The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System Initial Capabilities Document\"\n }, \"IS ICD\"), \" is the\\nfundamental requirements document that establishes validated capability\\nrequirements and is required for the materiel development decision. A\\ndraft \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \" is required at Milestone (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \") A, and a validated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \" is\\nrequired at the development \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Request for Proposal\"\n }, \"RFP\"), \" release decision point, which informs \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \"\\nB. If there are no changes, a revalidated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \" may be submitted for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" C.\\nThe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System\"\n }, \"IS\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \" for each increment are normally developed by the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \"/User. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 10-601, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Operational Capability Requirements\\nDevelopment\"), \", 6 Nov 13, contains additional information on updating and\\nannexing capability documents.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#program-identification","title":"Program Identification"},{"url":"#program-initiation-and-involvement-decision","title":"Program Initiation and Involvement Decision"},{"url":"#establishing-external-points-of-contact","title":"Establishing External Points of Contact"},{"url":"#establishing-a-relationship-with-director-of-operational-test-and-evaluation","title":"Establishing a Relationship with Director of Operational Test and Evaluation"},{"url":"#joint-capabilities-integration-and-development-system","title":"Joint Capabilities Integration and Development System","items":[{"url":"#afotec-involvement","title":"AFOTEC Involvement"}]}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/3-1-involvement-decision.md"},"frontmatter":{"metaTitle":"Involvement Decision","metaDescription":"Test lifecycle: Involvement Decision"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"273bd704-aac8-5277-aa7f-cf5039ef23b3"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/3-1-involvement-decision","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"273bd704-aac8-5277-aa7f-cf5039ef23b3","title":"Involvement Decision","slug":"/OT&E_Guide/3-1-involvement-decision"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Involvement Decision\",\n \"metaTitle\": \"Involvement Decision\",\n \"metaDescription\": \"Test lifecycle: Involvement Decision\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"h1\", null, \"Program Identification\"), mdx(\"p\", null, \"Program identification is the initial step when beginning an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nprogram. We establish initial contact with program sponsors and\\ndevelopers (e.g., MAJCOMs, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Material Command\"\n }, \"AFMC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Life Cycle Management Center\"\n }, \"AFLCMC\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Space Command\"\n }, \"AFSPC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space and Missile Systems Center\"\n }, \"SMC\"), \", joint commands) at\\nthe Detachment or corresponding \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" level. Usually, a program sponsor or\\ndeveloper puts out \\\"feelers\\\" to gain a sense of whether the timing and\\ncosts of conducting operational testing are feasible, which indicates an\\ninvolvement is pending. One of the first efforts is to determine when a\\nformal involvement decision is needed. A-3 is the clearinghouse for new\\nprogram involvements\"), mdx(\"h1\", null, \"Program Initiation and Involvement Decision\"), mdx(\"p\", null, \"Typically, involvement decisions are needed prior to participating in\\ntest-planning activities that require significant resources or formal\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" involvement (e.g., conducting an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \" meeting or developing a\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \"). It is important that the Detachment identify the need-by date for\\nan involvement so the involvement package is signed on time to support\\nprogram efforts. The Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" is authorized to apportion \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nfunds to support early pre-involvement activities until \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" makes an\\ninvolvement decision and allocates dedicated funds.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3 begins developing and coordinating an\\ninvolvement/non-involvement package to staff based upon which Detachment\\nwill have \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" responsibility for the program. A-3 may request information\\ndirectly from the program office, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Detachments, and other external\\nPOCs to decide whether we should involve/non-involve. At a minimum, an\\ninvolvement package includes an involvement bullet background paper\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Involvement Bullet Background Paper\"\n }, \"IBBP\"), \"), an involvement/non-involvement letter, and an initial tasking\\norder (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \") when involving. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" will sign the letter and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \",\\nthen send the letter to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" with courtesy copies to the sponsoring\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" and program office. A-3 establishes the format for documents\\nrequired in the involvement/non-involvement package. Using the program\\ncost estimator, an initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" is required within 60 days after the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"'s signature on the involvement letter and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \".\"), mdx(\"p\", null, \"Before formal involvement, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" initiates a program and establishes a\\nTest Program Management (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \") page on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Secure Internet Protocol Router Network\"\n }, \"NIPRNet\"), \" (and SIPRNet, if needed)\\nwith appropriate folders on network drives, and identification of POCs.\\nThe status of a program's acquisition strategy, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", and capability\\nrequirements documents are determined and posted on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \" page. At the\\nconclusion of program initiation, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will either recommend\\ninvolvement and initiate the process, or recommend non-involvement.\"), mdx(\"p\", null, \"Test resource planning begins after \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" establishes its formal\\ninvolvement in programs of record, technology demonstrations, and\\nexperiments. During this phase, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principle of early \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\ninvolvement is key. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" should make involvement determinations as\\nearly as possible. Once \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is involved, test teams should begin\\nexecuting foundational actions that enable early participation. These\\ninclude engaging other agencies to become a recognized member of\\nintegrated planning forums and initiating program research and study to\\ninfluence acquisition strategies, capability requirements, employment\\nand support concepts, and requests for proposal (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Request for Proposal\"\n }, \"RFP\"), \"). Early involvement\\nallows \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" to establish strong partnerships with external\\nstakeholders and start building trust between various organizations.\"), mdx(\"p\", null, \"With exceptions, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" recommends involvement in a program based on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \"\\n99-103 guidance. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" involves when it is the default operational test\\norganization or when it accepts a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \"'s request. The involvement\\nletter notifies external agencies and key personnel receive the initial\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \", which presents an estimated timeline of activities they are tasked\\nto complete. Table 3-1 contains the process for staffing an involvement\\npackage.\"), mdx(\"p\", null, \"Table 3\\u20111. Involvement Package Staffing\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Step\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Activity\"))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"1\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"A-3 drafts the \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Involvement Letter\"\n }, \"IL\"), \", \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" and \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Involvement Bullet Background Paper\"\n }, \"IBBP\"), \" with support from the executing Detachment\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"A-3 submits the \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Involvement Letter\"\n }, \"IL\"), \", \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" and \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Involvement Bullet Background Paper\"\n }, \"IBBP\"), \" for 2-ltr coordination\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"The A-3 sends the involvement package to \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Commander’s Action Group Office Symbol\"\n }, \"CCX\"), \"\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"4\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Once approved by \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \", \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Commander’s Action Group Office Symbol\"\n }, \"CCX\"), \" date stamps the \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Involvement Letter\"\n }, \"IL\"), \", electronically date/time stamp and number the \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" and forwards both to A-3 for posting to the appropriate Test Program Management page. \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/DS will send the \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Involvement Letter\"\n }, \"IL\"), \" to the appropriate owning organization of the program as well as \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" and \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \"\")))), mdx(\"h1\", null, \"Establishing External Points of Contact\"), mdx(\"p\", null, \"Immediately after \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" involves in a program, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test director\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \") will open and maintain channels of communication with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" focal\\npoints, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Air Force\"\n }, \"USAF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \", the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" action officer (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \"), the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Element Monitor\"\n }, \"PEM\"), \", program\\noffice, and the responsible \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Material Command\"\n }, \"AFMC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Life Cycle Management Center\"\n }, \"AFLCMC\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Space Command\"\n }, \"AFSPC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space and Missile Systems Center\"\n }, \"SMC\"), \" office. Before\\nintegrated test and evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E), the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" should establish an\\neffective relationship with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"&E \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \". The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" ensures parties\\naddress operational requirements during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E to allow early\\nidentification of problems and provide recommended fixes ahead of\\nacquisition decisions or milestones.\"), mdx(\"h1\", null, \"Establishing a Relationship with Director of Operational Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" is the principal staff assistant and senior advisor to the\\nSecretary of Defense (SecDef) on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" is responsible for the\\nfollowing:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Issuing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E policy and procedures\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Reviewing and analyzing results of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E conducted for each major \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \"\\nacquisition program\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Providing independent assessments to SecDef, the Under Secretary of\\nDefense for Acquisition, Technology and Logistics, and Congress\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Making budgetary and financial recommendations to the SecDef\\nregarding \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Overseeing major \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" acquisition programs to ensure \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E is adequate\\nto confirm operational effectiveness and suitability of the system\\nfor use in combat\"))), mdx(\"p\", null, \"The key tenet to remember in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s relationship with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" is that\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not work for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \", but we must work with them. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" does\\napprove (per \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" 5000.02 Enclosure 5 and Title 10 where approval of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nplan adequacy \\\"in writing\\\" is required) all program test plans on\\noversight. It is essential that we have frequent interchanges with their\\nAOs on all planning, execution, and reporting aspects of our test\\nprograms. Thus, it is in our best interest to maintain a healthy working\\nrelationship. Early in a program, the Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" should\\nidentify and meet with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \" (generally an O-6, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"General Schedule\"\n }, \"GS\"), \"-15) assigned\\nto the program and communicate with them frequently. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" expects the\\nappropriate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" or A-staff directorate to address\\nconflicts with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" policies and processes.\"), mdx(\"h1\", null, \"Joint Capabilities Integration and Development System\"), mdx(\"p\", null, \"The principal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" decision support processes for transforming military\\nforces in support of national military and defense strategies are the\\nJoint Capabilities Integration and Development System (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capabilities Integration and Development System\"\n }, \"JCIDS\"), \"), Defense\\nAcquisition System, and Planning, Programming, Budgeting and Execution\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Planning, Programming, Budgeting, and Execution\"\n }, \"PPBE\"), \"). Procedures established in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capabilities Integration and Development System\"\n }, \"JCIDS\"), \" support the Chairman and the\\nJoint Requirements Oversight Council (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Requirements Oversight Council\"\n }, \"JROC\"), \") when advising the SecDef\\nregarding identification, assessment, and prioritization of Joint\\nmilitary capability needs. Validated and approved \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capabilities Integration and Development System\"\n }, \"JCIDS\"), \"' documents\\nprovide the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Requirements Oversight Council\"\n }, \"JROC\"), \"'s advice and assessment and ensure the Joint force has\\ncapabilities needed to perform across the range of military operations.\"), mdx(\"h2\", null, \"\", mdx(\"abbr\", {\n parentName: \"h2\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Involvement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s involvement in the Joint requirements process includes the\\ninitial capabilities document (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \")/information system (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System\"\n }, \"IS\"), \") \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \" and the\\ncapabilities development document (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \")/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System Capability Development Document\"\n }, \"IS CDD\"), \". The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System Initial Capabilities Document\"\n }, \"IS ICD\"), \" is the\\nfundamental requirements document that establishes validated capability\\nrequirements and is required for the materiel development decision. A\\ndraft \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \" is required at Milestone (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \") A, and a validated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \" is\\nrequired at the development \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Request for Proposal\"\n }, \"RFP\"), \" release decision point, which informs \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \"\\nB. If there are no changes, a revalidated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \" may be submitted for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" C.\\nThe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System\"\n }, \"IS\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \" for each increment are normally developed by the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \"/User. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 10-601, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Operational Capability Requirements\\nDevelopment\"), \", 6 Nov 13, contains additional information on updating and\\nannexing capability documents.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#program-identification","title":"Program Identification"},{"url":"#program-initiation-and-involvement-decision","title":"Program Initiation and Involvement Decision"},{"url":"#establishing-external-points-of-contact","title":"Establishing External Points of Contact"},{"url":"#establishing-a-relationship-with-director-of-operational-test-and-evaluation","title":"Establishing a Relationship with Director of Operational Test and Evaluation"},{"url":"#joint-capabilities-integration-and-development-system","title":"Joint Capabilities Integration and Development System","items":[{"url":"#afotec-involvement","title":"AFOTEC Involvement"}]}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/3-1-involvement-decision.md"},"frontmatter":{"metaTitle":"Involvement Decision","metaDescription":"Test lifecycle: Involvement Decision"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"273bd704-aac8-5277-aa7f-cf5039ef23b3"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/3-2-standing-activities/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/3-2-standing-activities","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"b6c783b3-d703-5514-8e99-609f0b9192d3","title":"Standing Activities","slug":"/OT&E_Guide/3-2-standing-activities"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Standing Activities\",\n \"metaTitle\": \"Standing Activities\",\n \"metaDescription\": \"Standing Activities\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"h1\", null, \"Integrated Test Team and Charter\"), mdx(\"p\", null, \"The integrated test team (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \"), co-chaired by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" and the program\\noffice, is established to involve all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" stakeholders as early as\\npossible to facilitate and coordinate integrated test and evaluation\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E) planning and execution. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \" is the body that develops\\nrequired \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" documentation and functions throughout \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E execution and\\nreporting. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will request initiation of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \" charters within 60 days\\nof the material development decision (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Maintenance Data Documentation OR Material Development Decision\"\n }, \"MDD\"), \"), but not later than \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" A or\\ndevelopment of the Test and Evaluation Master Plan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \"), whichever\\ncomes first.\"), mdx(\"p\", null, \"A formal, signed \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \" charter is required for all ITTs and describes team\\nmembership, responsibilities, resources, and products for which the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \"\\nis responsible. Although the program office owns the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \" charter, the\\ntest team must ensure incorporation of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-unique requirements for an\\nevent-driven deliverable table and a conflict resolution chart. The\\ncharter is staffed by A-3 for 2-letter (2-ltr) coordination (A-3, A-2/9\\nand A-5/8 only) and signed by the A-3. The owning Detachment is\\nresponsible for supporting adjudication of comments and interaction with\\nthe program office. Charters are reviewed every 12 months (or after each\\nmajor decision review) and updated, as necessary, to ensure testing is\\nintegrated as much as possible within statutory and regulatory\\nguidelines.\"), mdx(\"h1\", null, \"Integrated Test and Evaluation Planning and Collaboration\"), mdx(\"p\", null, \"Early and frequent collaboration among \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" stakeholders ensures we\\nsatisfy common testing requirements and collect data that each testing\\ncommunity can use. We must identify \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E requirements early and\\nincorporate them into the developmental contract to ensure data from\\ncontractor developmental testing is available to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \". Optimally, a\\nsignificant amount of data from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E will satisfy \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E requirements\\nand minimize \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" events during the final phase of dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E.\"), mdx(\"p\", null, \"To support \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E culture, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E plans include \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E activities,\\ndata requirements, and sources. When \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" states its intent to include\\noperationally relevant data from specific \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" events, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" becomes an\\nacknowledged stakeholder. Rather than looking back after \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" to determine\\nwhether an event was operationally relevant, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" shall define a\\nruleset (and coordinate with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" as required) for defining \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nrelevance in advance of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" execution.\"), mdx(\"h1\", null, \"Integrated Test and Evaluation Considerations\"), mdx(\"p\", null, \"Early collaboration with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" counterparts facilitates an integrated\\neffort to develop a test strategy that identifies requirements early and\\nincreases the potential to identify shortfalls, develop peculiar\\ncapabilities, and increase preparedness for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \". \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E can also\\ninclude other agencies, such as Joint Interoperability Test Command\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Interoperability Test Command\"\n }, \"JITC\"), \"), to validate and certify technical compliance with compatibility,\\ninteroperability, and integration standards, or the Air Force Research\\nLab for cybersecurity analysis and test-support activities.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" clearly states its \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E intent from first contact with external\\ncommunities and we remain consistent throughout our involvement. We\\ninclude \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E language in the first available \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" or test strategy to\\nset the tone for every acquisition. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"&E can address many\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-developed measures of effectiveness (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \") and measures of\\nperformance and suitability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \"). Even when the lead developmental\\ntest organization (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Lead Developmental Test Organization\"\n }, \"LDTO\"), \") is not yet identified, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" states \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E\\nintent in all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" documentation.\"), mdx(\"h1\", null, \"Combined Test Force\"), mdx(\"p\", null, \"Combined test forces (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \") are integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" product teams empowered to\\nassess/evaluate a weapon system while sharing test burdens to reduce\\noverall cost/schedule and identify problems early through\\nintegrated/combined (parallel) testing. CTFs plan and execute\\nintegrated/combined events, share data, gain possible synergies, and\\nembrace test inputs from a wide range of stakeholders. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" respects\\nstakeholder inputs/requirements and strives to integrate them into\\nvarious phases of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \". Test requirements, resources, objectives, and\\nleadership of various test efforts are integrated to achieve higher\\nlevels of efficiency and maximize the opportunity to accelerate delivery\\nof combat capability to the warfighter. In general, formal CTFs differ\\nfrom ITTs in their primary focus. ITTs focus on overall test management;\\nwhereas, CTFs focus on day-to-day detailed test planning and test\\nexecution. However, the scope of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" responsibilities range from broad\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \"-like efforts down to day-to-day test execution. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" efforts are\\ncategorized into three phases: integrated/combined test planning,\\nintegrated/combined test execution and collection, and\\nintegrated/combined analysis and independent reporting. These phases can\\nbe distinct efforts or can overlap and occur seamlessly.\"), mdx(\"p\", null, \"There is no one-size-fits-all approach to CTFs and no two CTFs are\\nalike. Forcing a program into a pre-determined \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" structure and\\nprescriptive \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" activities (e.g., if there is no \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" charter or the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \"\\nis not in the same geographic location, then it is not considered a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \")\\ncan lead to inflexibility, resistance, and unhealthy friction. Taking\\nadvantage of informal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" synergies requires a non-binary \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" mindset.\\nTeams have flexibility when determining the right \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" environment and\\nthere are several considerations (e.g., program size, complexity, and\\nduration; cost to establish and sustain a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" verses potential return;\\nand the existing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" environment). If a formal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" is not\\nwarranted, an informal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" can often be established. An informal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" is\\nessentially a distributed environment that pursues the same objectives\\nas a formal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \". The intent is burden-sharing to reduce overall\\ncost/schedule through integrated and parallel testing.\"), mdx(\"p\", null, \"Formal and informal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" environments promote application of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \"\\nprinciples better than stove-piped \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" environments. While no\\nsingle consideration drives establishing a formal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \", Table 3-2\\ncontains attributes to consider when making that determination.\"), mdx(\"p\", null, \"Table 3\\u20112. Formal and Informal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" Attributes\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Formal CTF\"), mdx(\"th\", null, \"Informal CTF Environment\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Formally organized with an approved CTF charter (or other agreement)\")), mdx(\"li\", null, mdx(\"p\", null, \"Formalized single leader with operational control (OPCON) and administrative control (ADCON)-potentially rotating leadership with other CTF orgs\")), mdx(\"li\", null, mdx(\"p\", null, \"Formalized roles/responsibilities (User, SPO, LDTO, contractor); members sole responsibility is to the CTF\")), mdx(\"li\", null, mdx(\"p\", null, \"Formal conflict resolution process/decision authority\")), mdx(\"li\", null, mdx(\"p\", null, \"Relationships illustrated by an organizational chart\")), mdx(\"li\", null, mdx(\"p\", null, \"Emphasis on face-to-face interaction and participation in day-to-day test execution\")), mdx(\"li\", null, mdx(\"p\", null, \"Collocated test resources (F-15 EX), but can have distributed operations (GBSD, IBDSS)\")), mdx(\"li\", null, mdx(\"p\", null, \"DT/OT assets shared by same organization (F-15 EX)\")), mdx(\"li\", null, mdx(\"p\", null, \"Ability to data share through shared drives, ready access to all data by all participants\")), mdx(\"li\", null, mdx(\"p\", null, \"Workspaces or data portal access across CTF\")), mdx(\"li\", null, mdx(\"p\", null, \"Large scope acquisitions, such as those projected for more traditional timelines warranting a continuous presence or locations with multiple like programs (Bomber CTF)\")), mdx(\"li\", null, mdx(\"p\", null, \"Programs where organizational proximity/function make formalizing easier (e.g., Bomber CTF)\")), mdx(\"li\", null, mdx(\"p\", null, \"Permanent billets provided by member organizations\")), mdx(\"li\", null, mdx(\"p\", null, \"Challenged with to set-up and sustainment expense\")), mdx(\"li\", null, mdx(\"p\", null, \"May support non-material effort, e.g. develop TTPs\")), mdx(\"li\", null, mdx(\"p\", null, \"Incorporating development contractors in to the CTF typically requires influencing RFPs\")), mdx(\"li\", null, mdx(\"p\", null, \"Efficiencies supporting various program activities such as JRMETS, TDSB, DRB, and IPTWG, TEMP WG, M&SWG, and MRAP-C\")))), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Informally organized through accepted CTF practices\")), mdx(\"li\", null, mdx(\"p\", null, \"Can be an extension of the ITT\")), mdx(\"li\", null, mdx(\"p\", null, \"Roles, responsibilities, practices, and procedures are documented in TEMPs and ITT charters\")), mdx(\"li\", null, mdx(\"p\", null, \"Can be collocated or geographically separated/ distributed organization/resources (F-35, F\\u201122, F-15 EPAWSS)\")), mdx(\"li\", null, mdx(\"p\", null, \"Used when not practical to collocate\")), mdx(\"li\", null, mdx(\"p\", null, \"Flexible and easier to tailor/adapt to the various acquisition pathways and evolve with the programs\")), mdx(\"li\", null, mdx(\"p\", null, \"May work best when no potential to influence RFP and contract type (contractors not part of CTF)\")), mdx(\"li\", null, mdx(\"p\", null, \"Primary means of communication/coordination is via electronic means (emails, VTC, etc.)\")), mdx(\"li\", null, mdx(\"p\", null, \"Not required to reassign member billets\")), mdx(\"li\", null, mdx(\"p\", null, \"No PCA/PCS is required\")), mdx(\"li\", null, mdx(\"p\", null, \"OPCON/ADCON remains with parent units\")), mdx(\"li\", null, mdx(\"p\", null, \"Greater demand for TDY and virtual capabilities\")), mdx(\"li\", null, mdx(\"p\", null, \"Greater challenges with geographic separation, time-sensitive needs and communication\")), mdx(\"li\", null, mdx(\"p\", null, \"Personnel tasked with other roles/responsibilities\")), mdx(\"li\", null, mdx(\"p\", null, \"Increased effort on the part of all stakeholders to right-time high-value detailed planning activities, share/pull data, and participate in data scoring\")), mdx(\"li\", null, mdx(\"p\", null, \"Greater challenge ensuring stakeholder agendas stay aligned with the overall T&E enterprise priorities\")), mdx(\"li\", null, mdx(\"p\", null, \"May have an operating location with enough on-going work over a long enough period of time to warrant a formal CTF transition\"))))))), mdx(\"h1\", null, \"Meeting Attendance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" testers attend numerous acquisition meetings either in person,\\nor via teleconference, video teleconference, or Defense Collaboration\\nServices. Typical meetings include integrated product team (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Product Team\"\n }, \"IPT\"), \")\\nmeetings, integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" working group meetings, user meetings, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \"\\nmeetings, etc. As an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test team member, you should monitor program\\noffice activities and attend meetings that benefit test-planning or\\ninform program developments. When you attend meetings, you represent the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Commander and will, when appropriate, present the current \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ncommand briefing. You will be full participant and must be prepared to\\nask questions and give answers on behalf of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \". If in doubt about an\\nanswer or topic, take an action item to get back with the team at a\\nlater date. Within 2 duty days after key meetings, as determined by the\\nDetachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \", Director, or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", submit a trip report to the\\nDetachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" and/or Director summarizing the meeting.\"), mdx(\"h1\", null, \"Program Support by Detachments and OLs\"), mdx(\"p\", null, \"Detachments and operating locations (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operating Location\"\n }, \"OL\"), \") benefit \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" greatly by\\nengaging with SPOs, Air Force Materiel Command (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Material Command\"\n }, \"AFMC\"), \")/Air Force Life\\nCycle Management Center (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Life Cycle Management Center\"\n }, \"AFLCMC\"), \") or Air Force Space Command\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Space Command\"\n }, \"AFSPC\"), \")/Space and Missile Command (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space and Missile Systems Center\"\n }, \"SMC\"), \"), MAJCOMs, and other key agencies\\n(e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \", Air Force \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" \", \"[\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \"\", \"]\", \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Interoperability Test Command\"\n }, \"JITC\"), \", test ranges) early during\\nrequirements and acquisition processes. Detachments/OLs should support\\nearly program activities by discovering emerging requirements and\\nobtaining key program documentation. Detachments/OLs provide program\\nsupport that ensures \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s planning considerations are addressed,\\nestablishes benefits of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s involvement with external offices, and\\nenhances communications with other organizations.\"), mdx(\"h2\", null, \"Establish Working Relationship with Program Offices\"), mdx(\"p\", null, \"Dets/OLs are encouraged to establish a strong working relationship with\\nprogram offices. In support of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E planning, each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operating Location\"\n }, \"OL\"), \" should\\nactively participate in the product center's acquisition planning\\nprocess and formulate a test strategy that complies with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \".\"), mdx(\"h2\", null, \"Obtain Program Information\"), mdx(\"p\", null, \"Dets/OLs should obtain program information such as program priorities,\\nrequirements documents, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", operating plans, ISPs, and TTPs, as\\nrequested.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#integrated-test-team-and-charter","title":"Integrated Test Team and Charter"},{"url":"#integrated-test-and-evaluation-planning-and-collaboration","title":"Integrated Test and Evaluation Planning and Collaboration"},{"url":"#integrated-test-and-evaluation-considerations","title":"Integrated Test and Evaluation Considerations"},{"url":"#combined-test-force","title":"Combined Test Force"},{"url":"#meeting-attendance","title":"Meeting Attendance"},{"url":"#program-support-by-detachments-and-ols","title":"Program Support by Detachments and OLs","items":[{"url":"#establish-working-relationship-with-program-offices","title":"Establish Working Relationship with Program Offices"},{"url":"#obtain-program-information","title":"Obtain Program Information"}]}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/3-2-standing-activities.md"},"frontmatter":{"metaTitle":"Standing Activities","metaDescription":"Standing Activities"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"b6c783b3-d703-5514-8e99-609f0b9192d3"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/3-2-standing-activities","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"b6c783b3-d703-5514-8e99-609f0b9192d3","title":"Standing Activities","slug":"/OT&E_Guide/3-2-standing-activities"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Standing Activities\",\n \"metaTitle\": \"Standing Activities\",\n \"metaDescription\": \"Standing Activities\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"h1\", null, \"Integrated Test Team and Charter\"), mdx(\"p\", null, \"The integrated test team (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \"), co-chaired by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" and the program\\noffice, is established to involve all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" stakeholders as early as\\npossible to facilitate and coordinate integrated test and evaluation\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E) planning and execution. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \" is the body that develops\\nrequired \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" documentation and functions throughout \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E execution and\\nreporting. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will request initiation of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \" charters within 60 days\\nof the material development decision (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Maintenance Data Documentation OR Material Development Decision\"\n }, \"MDD\"), \"), but not later than \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" A or\\ndevelopment of the Test and Evaluation Master Plan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \"), whichever\\ncomes first.\"), mdx(\"p\", null, \"A formal, signed \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \" charter is required for all ITTs and describes team\\nmembership, responsibilities, resources, and products for which the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \"\\nis responsible. Although the program office owns the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \" charter, the\\ntest team must ensure incorporation of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-unique requirements for an\\nevent-driven deliverable table and a conflict resolution chart. The\\ncharter is staffed by A-3 for 2-letter (2-ltr) coordination (A-3, A-2/9\\nand A-5/8 only) and signed by the A-3. The owning Detachment is\\nresponsible for supporting adjudication of comments and interaction with\\nthe program office. Charters are reviewed every 12 months (or after each\\nmajor decision review) and updated, as necessary, to ensure testing is\\nintegrated as much as possible within statutory and regulatory\\nguidelines.\"), mdx(\"h1\", null, \"Integrated Test and Evaluation Planning and Collaboration\"), mdx(\"p\", null, \"Early and frequent collaboration among \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" stakeholders ensures we\\nsatisfy common testing requirements and collect data that each testing\\ncommunity can use. We must identify \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E requirements early and\\nincorporate them into the developmental contract to ensure data from\\ncontractor developmental testing is available to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \". Optimally, a\\nsignificant amount of data from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E will satisfy \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E requirements\\nand minimize \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" events during the final phase of dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E.\"), mdx(\"p\", null, \"To support \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E culture, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E plans include \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E activities,\\ndata requirements, and sources. When \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" states its intent to include\\noperationally relevant data from specific \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" events, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" becomes an\\nacknowledged stakeholder. Rather than looking back after \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" to determine\\nwhether an event was operationally relevant, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" shall define a\\nruleset (and coordinate with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" as required) for defining \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nrelevance in advance of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" execution.\"), mdx(\"h1\", null, \"Integrated Test and Evaluation Considerations\"), mdx(\"p\", null, \"Early collaboration with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" counterparts facilitates an integrated\\neffort to develop a test strategy that identifies requirements early and\\nincreases the potential to identify shortfalls, develop peculiar\\ncapabilities, and increase preparedness for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \". \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E can also\\ninclude other agencies, such as Joint Interoperability Test Command\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Interoperability Test Command\"\n }, \"JITC\"), \"), to validate and certify technical compliance with compatibility,\\ninteroperability, and integration standards, or the Air Force Research\\nLab for cybersecurity analysis and test-support activities.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" clearly states its \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E intent from first contact with external\\ncommunities and we remain consistent throughout our involvement. We\\ninclude \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E language in the first available \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" or test strategy to\\nset the tone for every acquisition. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"&E can address many\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-developed measures of effectiveness (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \") and measures of\\nperformance and suitability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \"). Even when the lead developmental\\ntest organization (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Lead Developmental Test Organization\"\n }, \"LDTO\"), \") is not yet identified, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" states \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E\\nintent in all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" documentation.\"), mdx(\"h1\", null, \"Combined Test Force\"), mdx(\"p\", null, \"Combined test forces (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \") are integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" product teams empowered to\\nassess/evaluate a weapon system while sharing test burdens to reduce\\noverall cost/schedule and identify problems early through\\nintegrated/combined (parallel) testing. CTFs plan and execute\\nintegrated/combined events, share data, gain possible synergies, and\\nembrace test inputs from a wide range of stakeholders. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" respects\\nstakeholder inputs/requirements and strives to integrate them into\\nvarious phases of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \". Test requirements, resources, objectives, and\\nleadership of various test efforts are integrated to achieve higher\\nlevels of efficiency and maximize the opportunity to accelerate delivery\\nof combat capability to the warfighter. In general, formal CTFs differ\\nfrom ITTs in their primary focus. ITTs focus on overall test management;\\nwhereas, CTFs focus on day-to-day detailed test planning and test\\nexecution. However, the scope of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" responsibilities range from broad\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \"-like efforts down to day-to-day test execution. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" efforts are\\ncategorized into three phases: integrated/combined test planning,\\nintegrated/combined test execution and collection, and\\nintegrated/combined analysis and independent reporting. These phases can\\nbe distinct efforts or can overlap and occur seamlessly.\"), mdx(\"p\", null, \"There is no one-size-fits-all approach to CTFs and no two CTFs are\\nalike. Forcing a program into a pre-determined \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" structure and\\nprescriptive \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" activities (e.g., if there is no \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" charter or the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \"\\nis not in the same geographic location, then it is not considered a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \")\\ncan lead to inflexibility, resistance, and unhealthy friction. Taking\\nadvantage of informal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" synergies requires a non-binary \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" mindset.\\nTeams have flexibility when determining the right \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" environment and\\nthere are several considerations (e.g., program size, complexity, and\\nduration; cost to establish and sustain a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" verses potential return;\\nand the existing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" environment). If a formal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" is not\\nwarranted, an informal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" can often be established. An informal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" is\\nessentially a distributed environment that pursues the same objectives\\nas a formal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \". The intent is burden-sharing to reduce overall\\ncost/schedule through integrated and parallel testing.\"), mdx(\"p\", null, \"Formal and informal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" environments promote application of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \"\\nprinciples better than stove-piped \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" environments. While no\\nsingle consideration drives establishing a formal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \", Table 3-2\\ncontains attributes to consider when making that determination.\"), mdx(\"p\", null, \"Table 3\\u20112. Formal and Informal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" Attributes\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Formal CTF\"), mdx(\"th\", null, \"Informal CTF Environment\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Formally organized with an approved CTF charter (or other agreement)\")), mdx(\"li\", null, mdx(\"p\", null, \"Formalized single leader with operational control (OPCON) and administrative control (ADCON)-potentially rotating leadership with other CTF orgs\")), mdx(\"li\", null, mdx(\"p\", null, \"Formalized roles/responsibilities (User, SPO, LDTO, contractor); members sole responsibility is to the CTF\")), mdx(\"li\", null, mdx(\"p\", null, \"Formal conflict resolution process/decision authority\")), mdx(\"li\", null, mdx(\"p\", null, \"Relationships illustrated by an organizational chart\")), mdx(\"li\", null, mdx(\"p\", null, \"Emphasis on face-to-face interaction and participation in day-to-day test execution\")), mdx(\"li\", null, mdx(\"p\", null, \"Collocated test resources (F-15 EX), but can have distributed operations (GBSD, IBDSS)\")), mdx(\"li\", null, mdx(\"p\", null, \"DT/OT assets shared by same organization (F-15 EX)\")), mdx(\"li\", null, mdx(\"p\", null, \"Ability to data share through shared drives, ready access to all data by all participants\")), mdx(\"li\", null, mdx(\"p\", null, \"Workspaces or data portal access across CTF\")), mdx(\"li\", null, mdx(\"p\", null, \"Large scope acquisitions, such as those projected for more traditional timelines warranting a continuous presence or locations with multiple like programs (Bomber CTF)\")), mdx(\"li\", null, mdx(\"p\", null, \"Programs where organizational proximity/function make formalizing easier (e.g., Bomber CTF)\")), mdx(\"li\", null, mdx(\"p\", null, \"Permanent billets provided by member organizations\")), mdx(\"li\", null, mdx(\"p\", null, \"Challenged with to set-up and sustainment expense\")), mdx(\"li\", null, mdx(\"p\", null, \"May support non-material effort, e.g. develop TTPs\")), mdx(\"li\", null, mdx(\"p\", null, \"Incorporating development contractors in to the CTF typically requires influencing RFPs\")), mdx(\"li\", null, mdx(\"p\", null, \"Efficiencies supporting various program activities such as JRMETS, TDSB, DRB, and IPTWG, TEMP WG, M&SWG, and MRAP-C\")))), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Informally organized through accepted CTF practices\")), mdx(\"li\", null, mdx(\"p\", null, \"Can be an extension of the ITT\")), mdx(\"li\", null, mdx(\"p\", null, \"Roles, responsibilities, practices, and procedures are documented in TEMPs and ITT charters\")), mdx(\"li\", null, mdx(\"p\", null, \"Can be collocated or geographically separated/ distributed organization/resources (F-35, F\\u201122, F-15 EPAWSS)\")), mdx(\"li\", null, mdx(\"p\", null, \"Used when not practical to collocate\")), mdx(\"li\", null, mdx(\"p\", null, \"Flexible and easier to tailor/adapt to the various acquisition pathways and evolve with the programs\")), mdx(\"li\", null, mdx(\"p\", null, \"May work best when no potential to influence RFP and contract type (contractors not part of CTF)\")), mdx(\"li\", null, mdx(\"p\", null, \"Primary means of communication/coordination is via electronic means (emails, VTC, etc.)\")), mdx(\"li\", null, mdx(\"p\", null, \"Not required to reassign member billets\")), mdx(\"li\", null, mdx(\"p\", null, \"No PCA/PCS is required\")), mdx(\"li\", null, mdx(\"p\", null, \"OPCON/ADCON remains with parent units\")), mdx(\"li\", null, mdx(\"p\", null, \"Greater demand for TDY and virtual capabilities\")), mdx(\"li\", null, mdx(\"p\", null, \"Greater challenges with geographic separation, time-sensitive needs and communication\")), mdx(\"li\", null, mdx(\"p\", null, \"Personnel tasked with other roles/responsibilities\")), mdx(\"li\", null, mdx(\"p\", null, \"Increased effort on the part of all stakeholders to right-time high-value detailed planning activities, share/pull data, and participate in data scoring\")), mdx(\"li\", null, mdx(\"p\", null, \"Greater challenge ensuring stakeholder agendas stay aligned with the overall T&E enterprise priorities\")), mdx(\"li\", null, mdx(\"p\", null, \"May have an operating location with enough on-going work over a long enough period of time to warrant a formal CTF transition\"))))))), mdx(\"h1\", null, \"Meeting Attendance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" testers attend numerous acquisition meetings either in person,\\nor via teleconference, video teleconference, or Defense Collaboration\\nServices. Typical meetings include integrated product team (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Product Team\"\n }, \"IPT\"), \")\\nmeetings, integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" working group meetings, user meetings, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \"\\nmeetings, etc. As an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test team member, you should monitor program\\noffice activities and attend meetings that benefit test-planning or\\ninform program developments. When you attend meetings, you represent the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Commander and will, when appropriate, present the current \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ncommand briefing. You will be full participant and must be prepared to\\nask questions and give answers on behalf of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \". If in doubt about an\\nanswer or topic, take an action item to get back with the team at a\\nlater date. Within 2 duty days after key meetings, as determined by the\\nDetachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \", Director, or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", submit a trip report to the\\nDetachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" and/or Director summarizing the meeting.\"), mdx(\"h1\", null, \"Program Support by Detachments and OLs\"), mdx(\"p\", null, \"Detachments and operating locations (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operating Location\"\n }, \"OL\"), \") benefit \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" greatly by\\nengaging with SPOs, Air Force Materiel Command (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Material Command\"\n }, \"AFMC\"), \")/Air Force Life\\nCycle Management Center (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Life Cycle Management Center\"\n }, \"AFLCMC\"), \") or Air Force Space Command\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Space Command\"\n }, \"AFSPC\"), \")/Space and Missile Command (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space and Missile Systems Center\"\n }, \"SMC\"), \"), MAJCOMs, and other key agencies\\n(e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \", Air Force \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" \", \"[\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \"\", \"]\", \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Interoperability Test Command\"\n }, \"JITC\"), \", test ranges) early during\\nrequirements and acquisition processes. Detachments/OLs should support\\nearly program activities by discovering emerging requirements and\\nobtaining key program documentation. Detachments/OLs provide program\\nsupport that ensures \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s planning considerations are addressed,\\nestablishes benefits of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s involvement with external offices, and\\nenhances communications with other organizations.\"), mdx(\"h2\", null, \"Establish Working Relationship with Program Offices\"), mdx(\"p\", null, \"Dets/OLs are encouraged to establish a strong working relationship with\\nprogram offices. In support of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E planning, each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operating Location\"\n }, \"OL\"), \" should\\nactively participate in the product center's acquisition planning\\nprocess and formulate a test strategy that complies with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \".\"), mdx(\"h2\", null, \"Obtain Program Information\"), mdx(\"p\", null, \"Dets/OLs should obtain program information such as program priorities,\\nrequirements documents, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", operating plans, ISPs, and TTPs, as\\nrequested.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#integrated-test-team-and-charter","title":"Integrated Test Team and Charter"},{"url":"#integrated-test-and-evaluation-planning-and-collaboration","title":"Integrated Test and Evaluation Planning and Collaboration"},{"url":"#integrated-test-and-evaluation-considerations","title":"Integrated Test and Evaluation Considerations"},{"url":"#combined-test-force","title":"Combined Test Force"},{"url":"#meeting-attendance","title":"Meeting Attendance"},{"url":"#program-support-by-detachments-and-ols","title":"Program Support by Detachments and OLs","items":[{"url":"#establish-working-relationship-with-program-offices","title":"Establish Working Relationship with Program Offices"},{"url":"#obtain-program-information","title":"Obtain Program Information"}]}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/3-2-standing-activities.md"},"frontmatter":{"metaTitle":"Standing Activities","metaDescription":"Standing Activities"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"b6c783b3-d703-5514-8e99-609f0b9192d3"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/3-3-test-strategy/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/3-3-test-strategy","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"3029582e-9c99-5851-86bf-34dc275d68eb","title":"Test Strategy","slug":"/OT&E_Guide/3-3-test-strategy"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Test Strategy\",\n \"metaTitle\": \"Test Strategy\",\n \"metaDescription\": \"Test Strategy\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"This section describes the purpose and elements involved in an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E test\\nstrategy (hereinafter referred to as \\\"test strategy\\\") for acquisition\\nprograms that require \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s involvement.\"), mdx(\"p\", null, \"The test strategy is the main tool to communicate how \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E will support\\ndelivery of the combat capability being acquired. It is an overarching\\ndocument to obtain buy-in, guidance, and approval from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s senior\\nleaders to proceed with detailed test-planning activities. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s test\\nteam overlays integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" activities onto the acquisition schedule,\\nwhich allows it to gather test data points throughout the program's\\nlifecycle.\"), mdx(\"p\", null, \"The former notion of determining whether a program was ready to enter\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E has been replaced with determining how many dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" events\\nare necessary to complete \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \". Accordingly, the test strategy defines \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nactivities as \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit Criteria.\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles require early, integrated\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" to find and fix system deficiencies early.\"), mdx(\"p\", null, \"The test team accomplishes the test strategy immediately after \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ndecides to involve in an acquisition program and receives adequate\\nprogram information (concept of operation, acquisition strategy, etc.).\\nThey will maintain constant communications with external organizations\\nwhile developing the strategy, but refrain from making statements about\\nwhat \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" may or may not do for the acquisition program until the test\\nstrategy is approved. Senior leaders review and approve the initial,\\ntailored, test strategy, which is the baseline for internal and external\\nstakeholder presentations. As the program matures and the acquisition\\nstrategy is refined, we adapt the test strategy to match.\"), mdx(\"h1\", null, \"Decision to Involve\"), mdx(\"p\", null, \"Before developing a test strategy for the planned system under test, the\\ntest team must ensure \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" has decided to involve in the program (see\\nparagraph 3.1.2). The team will obtain much of the information they need\\nto develop the test strategy during the involvement decision process.\\nOnce they have the formal decision to involve, the test team will use\\nthis information to begin developing their test strategy.\"), mdx(\"h1\", null, \"Gather Information\"), mdx(\"h2\", null, \"User Need (Capability Gap)\"), mdx(\"p\", null, \"It is important to understand the User's perspective and what it is they\\nneed from the system being developed or acquired. Will the system be\\nfilling a capability gap? Will it be an improvement over an existing\\nsystem? Knowing the reason why the system or capability is being\\nacquired or developed will help shape the test strategy because it\\nprovides an understanding of the system's importance.\"), mdx(\"h2\", null, \"Intended Use-\", mdx(\"abbr\", {\n parentName: \"h2\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \"\"), mdx(\"p\", null, \"The user produces the concept of operations (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \"), or equivalent\\ndocument to address the intended employment of forces and systems that\\nprovide guidance for posturing and supporting combat forces. It\\nspecifies standards for deployment, organization, command and control,\\nbasing, and support from which we can derive detailed resource\\nrequirements and implement programs. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" is a cornerstone\\ndocument test teams use to plan integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \". Consult the\\nuser/operator to understand how they plan to employ and support the\\nsystem (provides operational realism for the test), develop \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nscenarios, and inject operational realism into \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \". \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses\\nemployment and support concepts during all phases of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test\\nactivity. Some programs or projects may not have documented employment\\nand/or support concepts or the concepts may lag development. This is\\nespecially common with acquisitions using agile software development\\napproaches. In these cases, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" relies more heavily on current user\\n(operational) expertise. Invite representative users to participate in\\nearly test planning leading to an initial test design, and keep them\\nengaged to the extent needed to support all test activities.\"), mdx(\"h1\", null, \"Acquisition Approach\"), mdx(\"p\", null, \"The test team needs to understand how the system will be acquired to\\nmeet the operational need. There is no single acquisition approach for a\\nparticular type of system. The acquisition approach is influenced by the\\nurgency of need, technology development requirements, the amount of\\nmoney allocated to the program, or other various influences.\\nUnderstanding the acquisition approach will help the test team determine\\nwhich \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E activities to use when developing their test strategy. The\\ntest team must maintain an open dialogue with the program office to\\nunderstand the intricacies of the acquisition approach. The goal is to\\ncreate a single picture of how the system is intended to be\\ndeveloped/acquired and how combat capability will be delivered to the\\nwarfighter.\"), mdx(\"h1\", null, \"Strategy Development (\\\"Think Hard\\\" Part)\"), mdx(\"p\", null, \"After the test team collects the requisite information regarding the\\noperational capability needed, the intended \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", and the acquisition\\napproach, they should begin developing the integrated test strategy. The\\ngoal is to map how integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" will overlay onto the acquisition\\nstrategy for the system under test. At this point, the test team is not\\ncreating a detailed test plan, but deciding where it makes sense to\\nprovide formal or informal feedback. The primary purpose of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E is to\\ndiscover problems early and provide operational feedback (find it early,\\nfix it early). Begin by laying out what is known about the acquisition\\nstrategy to be employed. What acquisition model will be used? What are\\nthe major capability development activities? When will there be major\\nacquisition or operational decisions? Are there increments, blocks,\\nspirals, etc? Depict this acquisition strategy on a chart or some other\\nvisual method so that you can see the entire program in one picture.\"), mdx(\"p\", null, \"After depicting the acquisition strategy, note the points where the\\ndeveloper plans to deliver operational capability. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" focuses on\\ndelivering combat capability. The test team must understand the intent\\nand timing of planned deliveries and what operational capability will be\\nfielded/produced. Will the planned delivery be used operationally? Is\\nthe planned delivery in preparation for delivery of a future capability?\"), mdx(\"p\", null, \"In addition, note major acquisition decisions (milestones, preliminary\\ndesign review \", \"[\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Preliminary Design Review\"\n }, \"PDR\"), \"\", \"]\", \"/critical design review \", \"[\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Design Review\"\n }, \"CDR\"), \"\", \"]\", \", fielding, etc.)\\ndepicted by the program office. There may be formal decision points like\\nmilestones, or less formal decision points like limited fielding\\ndecisions, spiral completions, or contractual decisions. For major\\ncapability acquisitions, decision points are somewhat standard and can\\nbe found in DoDI 5000.02; however, other acquisition programs decision\\npoints will be heavily tailored to support the acquisition approach.\\nEither way, do a review of the decision points identified in the\\nacquisition strategy and tailor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s approach to ensure the\\nappropriate level of testing for each decision point. Ask whether the\\ndecision or acquisition point is significant enough to warrant an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nintegrated test activity.\"), mdx(\"p\", null, \"After depicting all acquisition and operational decision points,\\nincorporate points where \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", through integrated testing, can\\nparticipate or provide feedback. Formal points in the acquisition\\nstrategy should be informed by a formal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assessment or evaluation.\\nEnsure you depict \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s formal means of providing feedback (e.g.,\\nperiodic, observation, and status reports) to the acquisition and\\noperational communities. A useful tool to help determine the proper\\nlevel of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" feedback is the risk assessment and level of test\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Risk Assessment Level of Test\"\n }, \"RALOT\"), \"), which is a risk analysis and mitigation process, used\\npredominantly for software based systems, to determine the appropriate\\nlevel of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \". It is not an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activity in itself, nor is it used for\\nprogram involvement decisions. Refer to the \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://cs2.eis.af.mil/sites/10008/library/jobaidsguides/AFOTEC%20RALOT%20Guide%20Template.dotx?Web=1\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Risk Assessment Level of Test\"\n }, \"RALOT\"), \"\\nGuide\"), \"\\nfor additional information on the use of this process/tool.\"), mdx(\"p\", null, \"For each feedback point, work backwards to identify what major\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-specific planning and execution activities are needed to prepare\\nfor delivering the feedback. Consider the stage of development as well\\nas the planned test activities that will generate test data/information\\nto use in preparing feedback. For example, if the decision being\\ninformed warrants a formal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" report, use a formal planning process\\nthat includes a written and coordinated plan. For less formal decisions,\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" can deliver feedback via a memo documenting observations from\\nparticipating in developmental testing.\"), mdx(\"p\", null, \"Placement of test activities on the test strategy should support the\\nconcept of \\\"find early, fix early\\\" in which the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" feedback can help\\nidentify areas of operational concern with the capability being\\ndeveloped and enable the developer to begin fixing concerns as early as\\npossible. Array \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s test activities on the acquisition strategy so\\nthat they build toward final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities and ensure data collected\\nfulfills overall data requirements to make a final determination of the\\nsystem's operational effectiveness and suitability.\"), mdx(\"p\", null, \"Remember to include exit criteria to determine when final dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nactivities are complete. The initial test strategy may depict this as a\\nnotional block because detailed test planning has not begun. Test\\nstrategies incorporate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" status reviews, when appropriate, to assess\\ndata points against measures. The assessment determines which test\\nactivities are required to meet remaining exit criteria, and whether or\\nnot additional test activities are required. Test reporting deliverables\\nmay be dependent on completing exit criteria. As test strategies evolve\\nand mature, further refinement of exit criteria and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" status review\\ntime frames are included and updated.\"), mdx(\"h1\", null, \"Document and Communicate the Strategy\"), mdx(\"p\", null, \"Assemble the proposed test strategy and supporting rationale for\\ninternal and external review. It is not simply a PowerPoint slide, but\\nthe rationale for incorporating various activities throughout the\\nacquisition program. Before you present the strategy to the\\nDetachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" and eventually the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \", coordinate it for review,\\nedits, comments by senior members of the Detachment and headquarter (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \")\\nstaffs. The test strategy demonstrates the value and contribution of\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" activities to the delivery of combat capability.\"), mdx(\"h1\", null, \"Adapt and Refine the Strategy\"), mdx(\"p\", null, \"The acquisition strategy for a planned combat capability will change\\nover time due to technological, financial, or other issues so be\\nprepared to update and revise the test strategy as necessary. Document\\nthe reason for the updates/changes and provide traceability of the\\nstrategy's evolution so that a future reader will understand how the\\nstrategy changed from one version to the next. Coordinate the updated\\nstrategy, internally and externally, to obtain peer/mentor review and\\neventual leadership approval.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#decision-to-involve","title":"Decision to Involve"},{"url":"#gather-information","title":"Gather Information","items":[{"url":"#user-need-capability-gap","title":"User Need (Capability Gap)"},{"url":"#intended-use-conops","title":"Intended Use-CONOPS"}]},{"url":"#acquisition-approach","title":"Acquisition Approach"},{"url":"#strategy-development-think-hard-part","title":"Strategy Development (\"Think Hard\" Part)"},{"url":"#document-and-communicate-the-strategy","title":"Document and Communicate the Strategy"},{"url":"#adapt-and-refine-the-strategy","title":"Adapt and Refine the Strategy"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/3-3-test-strategy.md"},"frontmatter":{"metaTitle":"Test Strategy","metaDescription":"Test Strategy"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"3029582e-9c99-5851-86bf-34dc275d68eb"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/3-3-test-strategy","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"3029582e-9c99-5851-86bf-34dc275d68eb","title":"Test Strategy","slug":"/OT&E_Guide/3-3-test-strategy"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Test Strategy\",\n \"metaTitle\": \"Test Strategy\",\n \"metaDescription\": \"Test Strategy\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"This section describes the purpose and elements involved in an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E test\\nstrategy (hereinafter referred to as \\\"test strategy\\\") for acquisition\\nprograms that require \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s involvement.\"), mdx(\"p\", null, \"The test strategy is the main tool to communicate how \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E will support\\ndelivery of the combat capability being acquired. It is an overarching\\ndocument to obtain buy-in, guidance, and approval from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s senior\\nleaders to proceed with detailed test-planning activities. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s test\\nteam overlays integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" activities onto the acquisition schedule,\\nwhich allows it to gather test data points throughout the program's\\nlifecycle.\"), mdx(\"p\", null, \"The former notion of determining whether a program was ready to enter\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E has been replaced with determining how many dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" events\\nare necessary to complete \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \". Accordingly, the test strategy defines \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nactivities as \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit Criteria.\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles require early, integrated\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" to find and fix system deficiencies early.\"), mdx(\"p\", null, \"The test team accomplishes the test strategy immediately after \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ndecides to involve in an acquisition program and receives adequate\\nprogram information (concept of operation, acquisition strategy, etc.).\\nThey will maintain constant communications with external organizations\\nwhile developing the strategy, but refrain from making statements about\\nwhat \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" may or may not do for the acquisition program until the test\\nstrategy is approved. Senior leaders review and approve the initial,\\ntailored, test strategy, which is the baseline for internal and external\\nstakeholder presentations. As the program matures and the acquisition\\nstrategy is refined, we adapt the test strategy to match.\"), mdx(\"h1\", null, \"Decision to Involve\"), mdx(\"p\", null, \"Before developing a test strategy for the planned system under test, the\\ntest team must ensure \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" has decided to involve in the program (see\\nparagraph 3.1.2). The team will obtain much of the information they need\\nto develop the test strategy during the involvement decision process.\\nOnce they have the formal decision to involve, the test team will use\\nthis information to begin developing their test strategy.\"), mdx(\"h1\", null, \"Gather Information\"), mdx(\"h2\", null, \"User Need (Capability Gap)\"), mdx(\"p\", null, \"It is important to understand the User's perspective and what it is they\\nneed from the system being developed or acquired. Will the system be\\nfilling a capability gap? Will it be an improvement over an existing\\nsystem? Knowing the reason why the system or capability is being\\nacquired or developed will help shape the test strategy because it\\nprovides an understanding of the system's importance.\"), mdx(\"h2\", null, \"Intended Use-\", mdx(\"abbr\", {\n parentName: \"h2\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \"\"), mdx(\"p\", null, \"The user produces the concept of operations (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \"), or equivalent\\ndocument to address the intended employment of forces and systems that\\nprovide guidance for posturing and supporting combat forces. It\\nspecifies standards for deployment, organization, command and control,\\nbasing, and support from which we can derive detailed resource\\nrequirements and implement programs. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" is a cornerstone\\ndocument test teams use to plan integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \". Consult the\\nuser/operator to understand how they plan to employ and support the\\nsystem (provides operational realism for the test), develop \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nscenarios, and inject operational realism into \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \". \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses\\nemployment and support concepts during all phases of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test\\nactivity. Some programs or projects may not have documented employment\\nand/or support concepts or the concepts may lag development. This is\\nespecially common with acquisitions using agile software development\\napproaches. In these cases, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" relies more heavily on current user\\n(operational) expertise. Invite representative users to participate in\\nearly test planning leading to an initial test design, and keep them\\nengaged to the extent needed to support all test activities.\"), mdx(\"h1\", null, \"Acquisition Approach\"), mdx(\"p\", null, \"The test team needs to understand how the system will be acquired to\\nmeet the operational need. There is no single acquisition approach for a\\nparticular type of system. The acquisition approach is influenced by the\\nurgency of need, technology development requirements, the amount of\\nmoney allocated to the program, or other various influences.\\nUnderstanding the acquisition approach will help the test team determine\\nwhich \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E activities to use when developing their test strategy. The\\ntest team must maintain an open dialogue with the program office to\\nunderstand the intricacies of the acquisition approach. The goal is to\\ncreate a single picture of how the system is intended to be\\ndeveloped/acquired and how combat capability will be delivered to the\\nwarfighter.\"), mdx(\"h1\", null, \"Strategy Development (\\\"Think Hard\\\" Part)\"), mdx(\"p\", null, \"After the test team collects the requisite information regarding the\\noperational capability needed, the intended \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", and the acquisition\\napproach, they should begin developing the integrated test strategy. The\\ngoal is to map how integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" will overlay onto the acquisition\\nstrategy for the system under test. At this point, the test team is not\\ncreating a detailed test plan, but deciding where it makes sense to\\nprovide formal or informal feedback. The primary purpose of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E is to\\ndiscover problems early and provide operational feedback (find it early,\\nfix it early). Begin by laying out what is known about the acquisition\\nstrategy to be employed. What acquisition model will be used? What are\\nthe major capability development activities? When will there be major\\nacquisition or operational decisions? Are there increments, blocks,\\nspirals, etc? Depict this acquisition strategy on a chart or some other\\nvisual method so that you can see the entire program in one picture.\"), mdx(\"p\", null, \"After depicting the acquisition strategy, note the points where the\\ndeveloper plans to deliver operational capability. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" focuses on\\ndelivering combat capability. The test team must understand the intent\\nand timing of planned deliveries and what operational capability will be\\nfielded/produced. Will the planned delivery be used operationally? Is\\nthe planned delivery in preparation for delivery of a future capability?\"), mdx(\"p\", null, \"In addition, note major acquisition decisions (milestones, preliminary\\ndesign review \", \"[\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Preliminary Design Review\"\n }, \"PDR\"), \"\", \"]\", \"/critical design review \", \"[\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Design Review\"\n }, \"CDR\"), \"\", \"]\", \", fielding, etc.)\\ndepicted by the program office. There may be formal decision points like\\nmilestones, or less formal decision points like limited fielding\\ndecisions, spiral completions, or contractual decisions. For major\\ncapability acquisitions, decision points are somewhat standard and can\\nbe found in DoDI 5000.02; however, other acquisition programs decision\\npoints will be heavily tailored to support the acquisition approach.\\nEither way, do a review of the decision points identified in the\\nacquisition strategy and tailor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s approach to ensure the\\nappropriate level of testing for each decision point. Ask whether the\\ndecision or acquisition point is significant enough to warrant an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nintegrated test activity.\"), mdx(\"p\", null, \"After depicting all acquisition and operational decision points,\\nincorporate points where \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", through integrated testing, can\\nparticipate or provide feedback. Formal points in the acquisition\\nstrategy should be informed by a formal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assessment or evaluation.\\nEnsure you depict \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s formal means of providing feedback (e.g.,\\nperiodic, observation, and status reports) to the acquisition and\\noperational communities. A useful tool to help determine the proper\\nlevel of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" feedback is the risk assessment and level of test\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Risk Assessment Level of Test\"\n }, \"RALOT\"), \"), which is a risk analysis and mitigation process, used\\npredominantly for software based systems, to determine the appropriate\\nlevel of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \". It is not an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activity in itself, nor is it used for\\nprogram involvement decisions. Refer to the \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://cs2.eis.af.mil/sites/10008/library/jobaidsguides/AFOTEC%20RALOT%20Guide%20Template.dotx?Web=1\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Risk Assessment Level of Test\"\n }, \"RALOT\"), \"\\nGuide\"), \"\\nfor additional information on the use of this process/tool.\"), mdx(\"p\", null, \"For each feedback point, work backwards to identify what major\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-specific planning and execution activities are needed to prepare\\nfor delivering the feedback. Consider the stage of development as well\\nas the planned test activities that will generate test data/information\\nto use in preparing feedback. For example, if the decision being\\ninformed warrants a formal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" report, use a formal planning process\\nthat includes a written and coordinated plan. For less formal decisions,\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" can deliver feedback via a memo documenting observations from\\nparticipating in developmental testing.\"), mdx(\"p\", null, \"Placement of test activities on the test strategy should support the\\nconcept of \\\"find early, fix early\\\" in which the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" feedback can help\\nidentify areas of operational concern with the capability being\\ndeveloped and enable the developer to begin fixing concerns as early as\\npossible. Array \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s test activities on the acquisition strategy so\\nthat they build toward final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities and ensure data collected\\nfulfills overall data requirements to make a final determination of the\\nsystem's operational effectiveness and suitability.\"), mdx(\"p\", null, \"Remember to include exit criteria to determine when final dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nactivities are complete. The initial test strategy may depict this as a\\nnotional block because detailed test planning has not begun. Test\\nstrategies incorporate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" status reviews, when appropriate, to assess\\ndata points against measures. The assessment determines which test\\nactivities are required to meet remaining exit criteria, and whether or\\nnot additional test activities are required. Test reporting deliverables\\nmay be dependent on completing exit criteria. As test strategies evolve\\nand mature, further refinement of exit criteria and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" status review\\ntime frames are included and updated.\"), mdx(\"h1\", null, \"Document and Communicate the Strategy\"), mdx(\"p\", null, \"Assemble the proposed test strategy and supporting rationale for\\ninternal and external review. It is not simply a PowerPoint slide, but\\nthe rationale for incorporating various activities throughout the\\nacquisition program. Before you present the strategy to the\\nDetachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" and eventually the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \", coordinate it for review,\\nedits, comments by senior members of the Detachment and headquarter (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \")\\nstaffs. The test strategy demonstrates the value and contribution of\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" activities to the delivery of combat capability.\"), mdx(\"h1\", null, \"Adapt and Refine the Strategy\"), mdx(\"p\", null, \"The acquisition strategy for a planned combat capability will change\\nover time due to technological, financial, or other issues so be\\nprepared to update and revise the test strategy as necessary. Document\\nthe reason for the updates/changes and provide traceability of the\\nstrategy's evolution so that a future reader will understand how the\\nstrategy changed from one version to the next. Coordinate the updated\\nstrategy, internally and externally, to obtain peer/mentor review and\\neventual leadership approval.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#decision-to-involve","title":"Decision to Involve"},{"url":"#gather-information","title":"Gather Information","items":[{"url":"#user-need-capability-gap","title":"User Need (Capability Gap)"},{"url":"#intended-use-conops","title":"Intended Use-CONOPS"}]},{"url":"#acquisition-approach","title":"Acquisition Approach"},{"url":"#strategy-development-think-hard-part","title":"Strategy Development (\"Think Hard\" Part)"},{"url":"#document-and-communicate-the-strategy","title":"Document and Communicate the Strategy"},{"url":"#adapt-and-refine-the-strategy","title":"Adapt and Refine the Strategy"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/3-3-test-strategy.md"},"frontmatter":{"metaTitle":"Test Strategy","metaDescription":"Test Strategy"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"3029582e-9c99-5851-86bf-34dc275d68eb"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/4-1-levels-of-test/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/4-1-levels-of-test","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"836464f8-1d28-50a6-9f67-4696c3f77a06","title":"Levels of Test","slug":"/OT&E_Guide/4-1-levels-of-test"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Levels of Test\",\n \"metaTitle\": \"Levels of Test\",\n \"metaDescription\": \"Levels of Test\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"Systems can be broken down into multiple levels; mission effects, system\\ncapabilities, system functions/properties, and system structure. The\\nfocus of operational testing is to look at the mission effects achieved.\\nThe mission effects are the outcomes enabled by the system capabilities,\\nfunctions/properties, and structure.\"), mdx(\"p\", null, \"The levels-of-test pyramid depicts these relationships (Figure 4-1). The\\nconcept is that a system's structure forms the foundation for system\\nfunctions/properties. In turn, system capabilities are the integration\\nof multiple system functions and properties, and mission effect is\\nachieved by combining capabilities.\"), mdx(\"p\", null, \"Figure 4\\u20111. Levels of Test\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"986px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/5505d5947afced2cf5ac8032285c1d3e/0a867/image7.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"63.70656370656371%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAACHVAAAh1QEEnLSdAAADuklEQVQ4y3WS3U+aZxjGb3yb7KDJlmXJ9geY9Gx/QXeyJj3YkiU7WXqypDauxmFmM9sqYTUyJKhd6EqpIF8KCCovHwXxBZHCKxbLh1QFREW+xA/U+lFbF7cKvPdesqMt2ZXcR89z/67rfp4b4D8ymRJAkmK4caMddLowQZJOQETi/BwbFYoJEAh8DZkMQjB4BjbbMfyv2tpcEA6/YesEzOYMp7f32SWx2ArXr1/7VCYb9Xi9i+80mmffabVxYM84FHXKcTjegMPxFuz2w3/DRKIkuN3IJqFAIkkQiDUwGNbA5zv+IhTaLmk0FtTpppiZmTWMRk87i0UElwtBpTpoGB4uw6NHOejrO/kH1nIrB90PNsBAZjj9A3lCKl2tj/iBWh39TS5fQpOphB5P/tBmK1YNhs2q2XyMNtu7EfYOR6ksswH2CKGwAK2tq2yw1wBnmAXt+DxhHMtCS3MCOjtnr4nFqdTQ0CpKJBGUSuNVu/0YlcocikQzjFyeqlqtb3F09PWsQJD+5MEvWyBTFi+xBrB+cgbQ2bfO0Vnm2NjzHwoFm09/ag9ic/MM3r8f+1OhyF+QZAkp6oxRq/OMSlViZLJybWCg/F4o3EeBYL/QKzz6/LF8ExT6ErFQOAKg4gUwU8FvPZHclkxdxKabvlrTzcnq7dt+5HLpyuBg7r30yV5NLD6o3buXYrhtEeZuxwbeaU9f8LrK2N29+wcL/EY7scU+oBOAXt6SmagwSvVOtNKLF4P6xQqXO1e71TSNrT8GsKenyPD5e0zHzxls+SGEbdwYdtyNM739aVSZShWzdxPd0W0MJModRk8YwOJPXCWfJ1bVVhqHJnwVo2ee0TuSVR4/UeV1ZZneX4+wq6vE8PjLjOTpBqOZyDJWf67qT+5d0Cs7DL1SxufLu+iNb7HgfD9MhjLQ98Rw2fUyazVSUZRobIyS9NRIX7om1xYq8pECM+4u1rzxcmX6VaGid83iiCPINhdxOr6NUy/zJcfcms48s/S91kZfqQMJg3MeDthfstEr/DpUMeGrN1Xm13YrgdROrZ7CnygjFSmg0R37a9z7KmoNJEXGqciXd3jiy+lDBOeLddA5QwD22TSMToUb6nsVSO6DnU59ZfEnj1yhNaSXd9CzsF0HHTjm1q22QKqV9C1dYVhzf2IfxjwL0PNQBYVzbGCBhNLs44DJHYVhexCkIw6gUwcEFSmyBrHG6Ugm4JxbVY1S0a9Fv498nD9HmF4oweSLDDR+9BmEMqfEmCfWoLb4oV511Xfxb2JagA9m1pfgAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image7\",\n \"title\": \"image7\",\n \"src\": \"/static/5505d5947afced2cf5ac8032285c1d3e/0a867/image7.png\",\n \"srcSet\": [\"/static/5505d5947afced2cf5ac8032285c1d3e/a2ead/image7.png 259w\", \"/static/5505d5947afced2cf5ac8032285c1d3e/6b9fd/image7.png 518w\", \"/static/5505d5947afced2cf5ac8032285c1d3e/0a867/image7.png 986w\"],\n \"sizes\": \"(max-width: 986px) 100vw, 986px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"h1\", null, \"Mission Effect\"), mdx(\"p\", null, \"At the \\\"top\\\" of the pyramid are operations the system under test enables\\nand effects operations intend to achieve. Typically, operations are at\\nthe tactical level of conflict (small-unit or crew actions, engagements,\\nor battles). We refer to tests designed around operations and effects or\\noutcomes as \\\"operations-based.\\\"\"), mdx(\"h1\", null, \"System Capabilities\"), mdx(\"p\", null, \"System capabilities enable operations and their effects or outcomes. We\\nrefer to tests designed to answer questions about capabilities of a\\nsystem as \\\"capabilities-based.\\\"\"), mdx(\"h1\", null, \"System Functions, Properties and Structure\"), mdx(\"p\", null, \"Typically, systems have functions and properties that provide\\ncapabilities. The structure of a system enables these underlying\\nproperties (i.e., features and functions). Tests that focus on\\nfunctions, properties, and structure evaluate various attributes,\\ncharacteristics, or \\\"-ilities\\\" of a system (e.g., reliability,\\nmaintainability, etc.).\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#mission-effect","title":"Mission Effect"},{"url":"#system-capabilities","title":"System Capabilities"},{"url":"#system-functions-properties-and-structure","title":"System Functions, Properties and Structure"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/4-1-levels-of-test.md"},"frontmatter":{"metaTitle":"Levels of Test","metaDescription":"Levels of Test"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"836464f8-1d28-50a6-9f67-4696c3f77a06"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/4-1-levels-of-test","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"836464f8-1d28-50a6-9f67-4696c3f77a06","title":"Levels of Test","slug":"/OT&E_Guide/4-1-levels-of-test"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Levels of Test\",\n \"metaTitle\": \"Levels of Test\",\n \"metaDescription\": \"Levels of Test\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"Systems can be broken down into multiple levels; mission effects, system\\ncapabilities, system functions/properties, and system structure. The\\nfocus of operational testing is to look at the mission effects achieved.\\nThe mission effects are the outcomes enabled by the system capabilities,\\nfunctions/properties, and structure.\"), mdx(\"p\", null, \"The levels-of-test pyramid depicts these relationships (Figure 4-1). The\\nconcept is that a system's structure forms the foundation for system\\nfunctions/properties. In turn, system capabilities are the integration\\nof multiple system functions and properties, and mission effect is\\nachieved by combining capabilities.\"), mdx(\"p\", null, \"Figure 4\\u20111. Levels of Test\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"986px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/5505d5947afced2cf5ac8032285c1d3e/0a867/image7.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"63.70656370656371%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAACHVAAAh1QEEnLSdAAADuklEQVQ4y3WS3U+aZxjGb3yb7KDJlmXJ9geY9Gx/QXeyJj3YkiU7WXqypDauxmFmM9sqYTUyJKhd6EqpIF8KCCovHwXxBZHCKxbLh1QFREW+xA/U+lFbF7cKvPdesqMt2ZXcR89z/67rfp4b4D8ymRJAkmK4caMddLowQZJOQETi/BwbFYoJEAh8DZkMQjB4BjbbMfyv2tpcEA6/YesEzOYMp7f32SWx2ArXr1/7VCYb9Xi9i+80mmffabVxYM84FHXKcTjegMPxFuz2w3/DRKIkuN3IJqFAIkkQiDUwGNbA5zv+IhTaLmk0FtTpppiZmTWMRk87i0UElwtBpTpoGB4uw6NHOejrO/kH1nIrB90PNsBAZjj9A3lCKl2tj/iBWh39TS5fQpOphB5P/tBmK1YNhs2q2XyMNtu7EfYOR6ksswH2CKGwAK2tq2yw1wBnmAXt+DxhHMtCS3MCOjtnr4nFqdTQ0CpKJBGUSuNVu/0YlcocikQzjFyeqlqtb3F09PWsQJD+5MEvWyBTFi+xBrB+cgbQ2bfO0Vnm2NjzHwoFm09/ag9ic/MM3r8f+1OhyF+QZAkp6oxRq/OMSlViZLJybWCg/F4o3EeBYL/QKzz6/LF8ExT6ErFQOAKg4gUwU8FvPZHclkxdxKabvlrTzcnq7dt+5HLpyuBg7r30yV5NLD6o3buXYrhtEeZuxwbeaU9f8LrK2N29+wcL/EY7scU+oBOAXt6SmagwSvVOtNKLF4P6xQqXO1e71TSNrT8GsKenyPD5e0zHzxls+SGEbdwYdtyNM739aVSZShWzdxPd0W0MJModRk8YwOJPXCWfJ1bVVhqHJnwVo2ee0TuSVR4/UeV1ZZneX4+wq6vE8PjLjOTpBqOZyDJWf67qT+5d0Cs7DL1SxufLu+iNb7HgfD9MhjLQ98Rw2fUyazVSUZRobIyS9NRIX7om1xYq8pECM+4u1rzxcmX6VaGid83iiCPINhdxOr6NUy/zJcfcms48s/S91kZfqQMJg3MeDthfstEr/DpUMeGrN1Xm13YrgdROrZ7CnygjFSmg0R37a9z7KmoNJEXGqciXd3jiy+lDBOeLddA5QwD22TSMToUb6nsVSO6DnU59ZfEnj1yhNaSXd9CzsF0HHTjm1q22QKqV9C1dYVhzf2IfxjwL0PNQBYVzbGCBhNLs44DJHYVhexCkIw6gUwcEFSmyBrHG6Ugm4JxbVY1S0a9Fv498nD9HmF4oweSLDDR+9BmEMqfEmCfWoLb4oV511Xfxb2JagA9m1pfgAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image7\",\n \"title\": \"image7\",\n \"src\": \"/static/5505d5947afced2cf5ac8032285c1d3e/0a867/image7.png\",\n \"srcSet\": [\"/static/5505d5947afced2cf5ac8032285c1d3e/a2ead/image7.png 259w\", \"/static/5505d5947afced2cf5ac8032285c1d3e/6b9fd/image7.png 518w\", \"/static/5505d5947afced2cf5ac8032285c1d3e/0a867/image7.png 986w\"],\n \"sizes\": \"(max-width: 986px) 100vw, 986px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"h1\", null, \"Mission Effect\"), mdx(\"p\", null, \"At the \\\"top\\\" of the pyramid are operations the system under test enables\\nand effects operations intend to achieve. Typically, operations are at\\nthe tactical level of conflict (small-unit or crew actions, engagements,\\nor battles). We refer to tests designed around operations and effects or\\noutcomes as \\\"operations-based.\\\"\"), mdx(\"h1\", null, \"System Capabilities\"), mdx(\"p\", null, \"System capabilities enable operations and their effects or outcomes. We\\nrefer to tests designed to answer questions about capabilities of a\\nsystem as \\\"capabilities-based.\\\"\"), mdx(\"h1\", null, \"System Functions, Properties and Structure\"), mdx(\"p\", null, \"Typically, systems have functions and properties that provide\\ncapabilities. The structure of a system enables these underlying\\nproperties (i.e., features and functions). Tests that focus on\\nfunctions, properties, and structure evaluate various attributes,\\ncharacteristics, or \\\"-ilities\\\" of a system (e.g., reliability,\\nmaintainability, etc.).\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#mission-effect","title":"Mission Effect"},{"url":"#system-capabilities","title":"System Capabilities"},{"url":"#system-functions-properties-and-structure","title":"System Functions, Properties and Structure"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/4-1-levels-of-test.md"},"frontmatter":{"metaTitle":"Levels of Test","metaDescription":"Levels of Test"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"836464f8-1d28-50a6-9f67-4696c3f77a06"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/4-2-OT-test-activity-cycles/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/4-2-OT-test-activity-cycles","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"28dc0493-e6d2-51fc-abc3-bfd04ede6533","title":"OT&E Test Activity Cycles","slug":"/OT&E_Guide/4-2-OT-test-activity-cycles"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"OT&E Test Activity Cycles\",\n \"metaTitle\": \"OT&E Test Activity Cycles\",\n \"metaDescription\": \"OT&E Test Activity Cycles\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"h1\", null, \"Test, Analyze, and Fix (Re-Test)\"), mdx(\"p\", null, \"A general process to find problems early and fix them before they are\\nreleased to the field is called test, analyze, and fix (TAAF), or\\nsometimes test, analyze, fix, re-test (TAFT). We use this concept when\\ndeveloping a test strategy.\"), mdx(\"h1\", null, \"Test Activity\"), mdx(\"p\", null, \"Figure 4-2 depicts the steps in a test activity sequence. The sequence\\ndefines what we will test, how we will test it, and how we will execute\\nthe test, collect data, analyze results, and report conclusions.\"), mdx(\"p\", null, \"Figure 4\\u20112. Steps in a Test Activity\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"1035px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/3932446dab1e0c30b75d21010eda7bcb/d073d/image8.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"17.760617760617762%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAECAYAAACOXx+WAAAACXBIWXMAABcRAAAXEQHKJvM/AAABK0lEQVQY0x2My07CUBCG+1Tu3Wvk8hC+gTRGGaseE2JcKGriwihGI7eFEHBMrCAB24KVFlqooKEYYhB1oa6clZ528WVu3z/C3HYzFowb6+G9FgvEDRbYMVho12QhPof3LTazWWXTYppNzcfZ7Jbq77nPgp7D8Xyv935wYsJGzlmLJpvRSEKFlXQLpEwLxBMNFo4VWDxtQOSoBuJhGcSDK1jlN0iZHAOWzx8gklBAyrZh6UznWTMqZS1JMBz3rz/6/K3UTeqNPsid/NBg/EW6/Uz1dp8a1hOpxiN1h+/kDCfUdcfUGYz96rtv36SaDtV020eoNHuyZg8vU4USFsoN1HuvqFoDjouq7aLC++LtPaYKN5iTFcyXNLy4Vjh3KGttrHde/FwyL2OmWMZ/xyffFrvbRGUAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image8\",\n \"title\": \"image8\",\n \"src\": \"/static/3932446dab1e0c30b75d21010eda7bcb/e3189/image8.png\",\n \"srcSet\": [\"/static/3932446dab1e0c30b75d21010eda7bcb/a2ead/image8.png 259w\", \"/static/3932446dab1e0c30b75d21010eda7bcb/6b9fd/image8.png 518w\", \"/static/3932446dab1e0c30b75d21010eda7bcb/e3189/image8.png 1035w\", \"/static/3932446dab1e0c30b75d21010eda7bcb/d073d/image8.png 1297w\"],\n \"sizes\": \"(max-width: 1035px) 100vw, 1035px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"p\", null, \"We must accomplish the following five steps and multiple sub-steps:\"), mdx(\"p\", null, \"1) Define the What\"), mdx(\"pre\", null, mdx(\"code\", {\n parentName: \"pre\"\n }, \"a. What is the system under test (SUT)?\\n\\nb. What is the intended use of the SUT (operations and conditions)?\\n\\nc. What do you need to measure to determine combat capability of\\n the SUT?\\n\")), mdx(\"p\", null, \"2) Test Design\"), mdx(\"pre\", null, mdx(\"code\", {\n parentName: \"pre\"\n }, \"a. Establish goals of a test\\n\\nb. Pick test events to support the goal\\n\\nc. Define when the test is complete (exit criteria)\\n\")), mdx(\"p\", null, \"3) Test Execution Considerations\"), mdx(\"pre\", null, mdx(\"code\", {\n parentName: \"pre\"\n }, \"a. Create an operationally realistic environment\\n\\nb. Collect and gather data/information\\n\\nc. Test execution\\n\")), mdx(\"p\", null, \"4) Analysis and Evaluation\"), mdx(\"pre\", null, mdx(\"code\", {\n parentName: \"pre\"\n }, \"a. Analyze the data\\n\\nb. Evaluate the analysis to determine the \\\"so what\\\"\\n\\nc. Have exit criteria been met?\\n\")), mdx(\"p\", null, \"5) Conclusions and Reporting\"), mdx(\"pre\", null, mdx(\"code\", {\n parentName: \"pre\"\n }, \"a. Communicate results\\n\\nb. Determine impact to the warfighter\\n\")), mdx(\"p\", null, \"In general, you conduct these five main steps in order, but you may\\nreorder, abbreviate, move, or overlap them (e.g., analysis during\\nexecution).\"), mdx(\"h1\", null, \"Cycles of Test Activities\"), mdx(\"p\", null, \"Applying the five main steps can be a single flow through the five\\nsteps, or it may be multiple iterations at varying levels of test.\\nMultiple test activities may form an overall test and may be conducted\\nsingly, sequentially, concurrently, recursively, or nested and at\\ndifferent levels. Ultimately, however, the intent is to answer the\\nmission-level questions of the critical operational issues (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"). Figure\\n4-3 depicts the general relationship of test activities. Note the\\noverarching, or first level of test activity, is oriented to evaluating\\nmission effects that lead to a final report of combat capability.\"), mdx(\"p\", null, \"Figure 4\\u20113. Cycles of Test Activity\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"992px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/9c8f9d3ba9bdc5e1484dc04038cf319b/91f10/image9.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"63.32046332046332%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAACHVAAAh1QEEnLSdAAAEBklEQVQ4yx1Sa0ybVRh+e0EW98PIrVS2ITqYuikaXUxmwHTO6KBXkMkim1v84dhilmxRfhjRBiIYGLcChZbSSKGFXoBIoS30wqDXDyjw2QsrY1A6BnRjTh1MGXI87CRPnvd5npz3PW9y4PMGJxTUjJ0qFLkqChucP55vnRJ+IXIKC8p6hYJSlfBMhV6Y/1OPkP9Dl1CA8ZlQIyysHhZekM6UnhW56nmVw9n8X8yQV22jwN6xTcyBxeP/dsw7v2KfuTOptxHTxnEvqbe6yWG7lxy0esghG0GaxqdIw+gEOWB2ksaxKXLA4p4enQjeJQKR67OLGzAxt0J71lBvMMOgyZZ80zX98ZDF4bU4ydDE3LrbE1idsBIhQmdwEAOWSaJv2E3oR72EJ7hKeAL3PC7f3VmLO/iN2+NJCIe8MEnegm31AQCTzUEZtROAUDlIVUYuYR9qigRst5cDo/6Q1xgkrOqgy9ITdIyogjP2viD2g2G/zRf2WyO3HIqixRk9LHm19IirESJDxQAucyf4jUIqugxQPI/ggbGoMuIQ/b1488ZawFQZ9RkqorP6csw/P6tvW6uiEXvd2oqr6a91w4VGlAJ0JAHY7M2krA6eB0Ca41Begl861kj9R/kiO2ourr/jlHhmjVX2gLXO4bfUOQIYv4/UOILWese0oQrrWsfqlNy5aC7tjei/LFswXdqHPLVw33AFwCdmUh/2MAH1p722q0nNR+qDWaj/EAv1H2Yh3QHMySzUx2Sh3hQW0r6EdSrrqS7j5I485kTQVNUQMldZUP9b70U070BIm0OFkcpkWO9JemVNlfzbhpbRudHD6Ih2Jv76RBOvmFendrqUryumVUcUPk26wqdNVyxoDnXu6OIUOwOJis3++I4HqnhZtJuhX+tmvB3uSMYrI4DxZmaOX5aE1rri/72nSkTWtpeRUXNst0KXtV2jzN4RKbOQRHtit64rG91QZm8Pqo7tzsqZu1u6uMdhReJ/AXkSmhQzziFzAkBaXEpaPsALlz9lHMm8fvyTN0Q5V1J684qoEoGa1sr17WvneGPbOHN0OS9IkfExBDMgFoyDmPddguz0R2e+yjh69f24jMz0gxn7P3gzFmK68/ZTpNxL0M6vBjlfirkWpNzvqTKOiybhbFElHESRchBNzEYxTbmI3pyLaFL2E6qUE4F2XhmoCwSgPnsU7X1qOQ8g9sbpDHoLm6RL2G56K3t8DzFi9jJNylnG/sJzzewI5ghdnBvGA/7AmYsq55bQ2rkV9DbORWoH7xxFyb8GSv7XGO/CqxezIa70FDCvsSC+5CQ8f/VDGm5qx5efUmXcR7Q2zp90CUYL+xHWmzEtnCU8bInaxlnFW2zg/CHO7mPvMa63/gck4C8omRtM4wAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image9\",\n \"title\": \"image9\",\n \"src\": \"/static/9c8f9d3ba9bdc5e1484dc04038cf319b/91f10/image9.png\",\n \"srcSet\": [\"/static/9c8f9d3ba9bdc5e1484dc04038cf319b/a2ead/image9.png 259w\", \"/static/9c8f9d3ba9bdc5e1484dc04038cf319b/6b9fd/image9.png 518w\", \"/static/9c8f9d3ba9bdc5e1484dc04038cf319b/91f10/image9.png 992w\"],\n \"sizes\": \"(max-width: 992px) 100vw, 992px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"p\", null, \"You can construct an individual test activity (e.g., a test within the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \") at various system levels (mission effects,\\ncapabilities, functions/properties, structure). This is particularly\\nappropriate for acquisition strategies with a development model (such as\\nagile techniques) in which individual capabilities are developed\\nincrementally, but the full mission effect cannot be achieved until all\\nor many of the capabilities are present. In this case, you may construct\\ntest activities for individual capabilities or sets of capabilities.\\nWith some exceptions, you will follow the same five steps and construct\\nthem within the context of overarching COIs, operations, and mission\\neffects. Figures 4-4 through 4-6 depict applying multiple test\\nactivities notionally to an acquisition pathway.\"), mdx(\"p\", null, \"Figure 4\\u20114. Notional Test Activities for a Traditional Major Capability\\nAcquisition\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"1035px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/026f6a11df29bcc870713ce9e9afc43e/5c98f/image10.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"47.87644787644788%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAKCAYAAAC0VX7mAAAACXBIWXMAABcRAAAXEQHKJvM/AAACgElEQVQoz22QSUxTURSGT1uqCZYZJ7QhFaeFkVdmk7pRQlyQEIwLjSvRwAbjRg08kUTQGDEmuFQgFEFw4QobIaJMdgRDKaUtrW1ty7O1M1Cg1AjX8xBMSbjJl3POf/78790LF1smmpB6hN7BMw1d+nySljR8pM/ceEkX33tPl73Qbuq7eOtKWyaeXHiqrIVe1c+Rt0qmH5HFg7qsW+6SdQyZZK8+TMraBvWyHlaP92yjYvpx97lr3CkFVzBKHIHVTZyBKGFnFiYcIxYmRNR6K5kyM0Q9YyVGp5+4Qms7fP/9qNu8y7/AH17KX4yR3Mg6obzBBbF5PlikMPskX01eic4ZPrewtEwFF1eolT+EimwQCv2U2xcS6x3BEvmcT6JEr+JfPT9m8BRCXuP4beG11uoDFc23ih4p7p59KK/s03igR+4CqOjLKGjS1FIPhqtFVe01+8sba8QNYzdLHmvoo3c+iVsHrRBaioL2RwimHWGYsPoBusfts51DBkXHoE4hHbUZeuTO3ox6E7SNuqBz1F7cp2J0b8ZsSumXOXX7gFaNvRw/Znunmr//esQBA9MePgZyMZCLgVyYnLWRb0YHmbYwhO31dq8FoBLChMCUPVBm90ZIvEej/07wWYjZE+nyrhIYVs/wIf5YwiRf516jjP4NyhQgecYgOSXKFsKlyqtsaKLBt55v9BNqxh0T457CmZqaXy3Uun8La+uaYbdzCElDkpB05CAi4vF42VgPI5lbevqWLxURsDOfv+cI1qytHWczLSk55URKWroQaw7bJ+4THEf5GJLN5fFOJ6ek5iAiQVLyybSMzKwr16v4ZeWX9+YWlLBXTeBwOAlYedt/9xdZHKssSd18lwAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image10\",\n \"title\": \"image10\",\n \"src\": \"/static/026f6a11df29bcc870713ce9e9afc43e/e3189/image10.png\",\n \"srcSet\": [\"/static/026f6a11df29bcc870713ce9e9afc43e/a2ead/image10.png 259w\", \"/static/026f6a11df29bcc870713ce9e9afc43e/6b9fd/image10.png 518w\", \"/static/026f6a11df29bcc870713ce9e9afc43e/e3189/image10.png 1035w\", \"/static/026f6a11df29bcc870713ce9e9afc43e/5c98f/image10.png 1283w\"],\n \"sizes\": \"(max-width: 1035px) 100vw, 1035px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"p\", null, \"Figure 4\\u20115. Notional Test Activities for a\\nMajor Capability Acquisition\\\\\\nwith Incremental Capability Delivery\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"1035px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/78e986469d711751467fe0b3b1af4e0e/08037/image11.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"50.965250965250966%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAKCAYAAAC0VX7mAAAACXBIWXMAABcRAAAXEQHKJvM/AAACpElEQVQoz02Oa0hTYRjH31IqnBdCNNO8Oy8Z+SkoHA0Ckb5khlQaVNSHoMCkiyLUh74UGbiV7EyJiIxQIQIRsZrzsk1ycxd30+1surOds3M227S1swuG2XPiCHvhx/95/s+f53nRjWEPuooZutvlpneADMBSkF8bMmOtL6aw5sfvsQ5Mj3VA3y43ylMzwEA7Zhy9MqA7hVpfzZZbfJGvTia25aBZykFHaVDaybCUKxgnTWsb9KLdS/+wEbR2leRmfjwQ8zkY9n+Oy0OWtPujcZNn8za6+FJZT4VjXcxWAgtEtiVB9q80+CvZ79mIDULwg4cO9ZschNTuCUituFfiC7Fv7FT0E7MVl0BeyuUDkKfC8aFp20Ybqr/QmZ5/f7Yh7+7UuYOXsLOosVt8+M6kqLpnvrW2V3W58IFalHt9WJzW9Exc1DUjKn0013zyifpmXues6FDbkBideSjOvvWlsaJ7vkX0fFGEmno+lstnvHJMsaaXTlhUfWMLakyxrpFNe7SDM4QSUxIayfiyum9Uo5F9d6ug12LT63PyGUL9esKi6RsD/xs+J1N6VzCFuwU1944cdzG/F8y4b0dndUdMTh+7ZHNHcf9mzBdOxsCP6qwu1rBKsHrbWhSnwiwRSsSsbiqqteCsyUmyMI/gZGjXFWDvofNPP6NFD1tsIBM1Bl9caGG2q8zMH+ES1DqCFVoCO0LOX6aSQgMZF+qh1pPJKiP0RjIBxIUax8+a+ZVgncLsP4wK6k7vQwhVAiVAAVAIlPEU8z7nlfJ6DCji4WblQPrIpAp5E7sI5VY0oAxBZpkgM6s2KzunArQG+nquzszKrswQCE5wM6B6LwN+Varm5uXnvx0ZT2N3YSH/jvIXj/BXi3mvJOUnhbzmAGk86cB+4MDeon8XMZMF/XYbUwAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image11\",\n \"title\": \"image11\",\n \"src\": \"/static/78e986469d711751467fe0b3b1af4e0e/e3189/image11.png\",\n \"srcSet\": [\"/static/78e986469d711751467fe0b3b1af4e0e/a2ead/image11.png 259w\", \"/static/78e986469d711751467fe0b3b1af4e0e/6b9fd/image11.png 518w\", \"/static/78e986469d711751467fe0b3b1af4e0e/e3189/image11.png 1035w\", \"/static/78e986469d711751467fe0b3b1af4e0e/08037/image11.png 1379w\"],\n \"sizes\": \"(max-width: 1035px) 100vw, 1035px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"p\", null, \"Figure 4\\u20116. Notional Cycles of Test Activities\\nfor a Software Acquisition\\\\\\nUsing Sprints to Deliver Capabilities\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"1035px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/614bf2a0c6f6998a7e784972cce0e975/08037/image12.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"62.16216216216216%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAYAAABiDJ37AAAACXBIWXMAABcRAAAXEQHKJvM/AAADgUlEQVQoz02RfUwTZxzHny1z/rNs2YtThxMwboujRUayxfDSLLq5LCEGxohiQB17021o1jHRRBxCwDAsnde7Uh2d02ha3eqymQXowL4BPYcUWun1lbbXXnt3BQRsS9mMdL9z/OEfn+TzfJ7vX8+D9l8Kot3E2NE9yvGePUobDhArKHcDe1V2ory9l3i34QJRTYwS1XAW+qM7AIOmqcJuvYkqOg05dnqh180mZ12xRBhgXLFk1B1LRrxcirZNxaNWJ82M3AkyJBUR7hgPm6SFzcNtNMHAlp5kEklbYPZjVN4xKGJmU9+wc+nz3MK/GJ98gHPzS1gwnurxcKnLgdgMNu4O4s4gi9/x0orITFJJRRNa2Ctgj/PJZZyFPXN3UT3ojH+ICvc2rXrxiCH/hUO9bz9ZQZSiom8lz37+Z/GrjabyLcfNVeul5uLnai9JHn+nWZL1taE4u8G4M/+E5cCawzeLV1eqJGibVPJ03fWiTUfNu0rbyRK0XarOIgZCBK6fGpX/4TB2aIfNin6/BdMHSGIgOAB3lq7fJ8wd2iEz1uc1Kf4Kkbg+YIBugv3/vddzE7oT1/t3obKWG+9TkbnRcXcoY3PTqdtUKH3L4U27wjNLoenFJZsrmIaeHnPRi9YJd9odnl4KCt0dghZ62Em7J0WF+IyPS30Fn2J8LZPJrAHWm3yJgqskUwr+PEmnxRoyJgFfG55/8MpFS3iHsPknk8lRmyLvCZ5aFpwWfN3d+5nNJ69730Jv1LSuKmjs277pgKq6sOG3Q9tODdVl1ygqC6S6z4paRz7JrVVUiY9c21fSZv0ipwarEtVra0vbrPW5+5SVonrNRyVtI1/m7u+uENdrDu6U24tQ2Xe6bOLGeLdMaxyT68i/z/U7DeDDXb9awSmjTGMYErqqjzKDm6GPglu6tEaT7NrwbVU/ZZZfNRlkvwxT5wd8H6CyZp3IxczpHf7oPEVPsz52IQ7OgnN+7h4PzrnoOO9n7/F2X5SDtxJ63O5jOGeQ5wJ8kp/wRFiHP5aepGcPok+vTKG6w8dFJ8+c29qK/fx6C3ZxS9P33fnHTivyG9sV4pazP4lOydV5x04T4tazF/KaOlXipjM/5rX8oBad6OwWS5tlW3t0g5vt/PKGfjv7FNpYuOMxhFA28DKwDsh6hI0r7SVgA7B2ZZcDPAM8AayGT0GWyQhycPfRf+oOTSKP6SH8AAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image12\",\n \"title\": \"image12\",\n \"src\": \"/static/614bf2a0c6f6998a7e784972cce0e975/e3189/image12.png\",\n \"srcSet\": [\"/static/614bf2a0c6f6998a7e784972cce0e975/a2ead/image12.png 259w\", \"/static/614bf2a0c6f6998a7e784972cce0e975/6b9fd/image12.png 518w\", \"/static/614bf2a0c6f6998a7e784972cce0e975/e3189/image12.png 1035w\", \"/static/614bf2a0c6f6998a7e784972cce0e975/08037/image12.png 1379w\"],\n \"sizes\": \"(max-width: 1035px) 100vw, 1035px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#test-analyze-and-fix-re-test","title":"Test, Analyze, and Fix (Re-Test)"},{"url":"#test-activity","title":"Test Activity"},{"url":"#cycles-of-test-activities","title":"Cycles of Test Activities"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/4-2-OT-test-activity-cycles.md"},"frontmatter":{"metaTitle":"OT&E Test Activity Cycles","metaDescription":"OT&E Test Activity Cycles"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"28dc0493-e6d2-51fc-abc3-bfd04ede6533"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/4-2-OT-test-activity-cycles","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"28dc0493-e6d2-51fc-abc3-bfd04ede6533","title":"OT&E Test Activity Cycles","slug":"/OT&E_Guide/4-2-OT-test-activity-cycles"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"OT&E Test Activity Cycles\",\n \"metaTitle\": \"OT&E Test Activity Cycles\",\n \"metaDescription\": \"OT&E Test Activity Cycles\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"h1\", null, \"Test, Analyze, and Fix (Re-Test)\"), mdx(\"p\", null, \"A general process to find problems early and fix them before they are\\nreleased to the field is called test, analyze, and fix (TAAF), or\\nsometimes test, analyze, fix, re-test (TAFT). We use this concept when\\ndeveloping a test strategy.\"), mdx(\"h1\", null, \"Test Activity\"), mdx(\"p\", null, \"Figure 4-2 depicts the steps in a test activity sequence. The sequence\\ndefines what we will test, how we will test it, and how we will execute\\nthe test, collect data, analyze results, and report conclusions.\"), mdx(\"p\", null, \"Figure 4\\u20112. Steps in a Test Activity\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"1035px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/3932446dab1e0c30b75d21010eda7bcb/d073d/image8.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"17.760617760617762%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAECAYAAACOXx+WAAAACXBIWXMAABcRAAAXEQHKJvM/AAABK0lEQVQY0x2My07CUBCG+1Tu3Wvk8hC+gTRGGaseE2JcKGriwihGI7eFEHBMrCAB24KVFlqooKEYYhB1oa6clZ528WVu3z/C3HYzFowb6+G9FgvEDRbYMVho12QhPof3LTazWWXTYppNzcfZ7Jbq77nPgp7D8Xyv935wYsJGzlmLJpvRSEKFlXQLpEwLxBMNFo4VWDxtQOSoBuJhGcSDK1jlN0iZHAOWzx8gklBAyrZh6UznWTMqZS1JMBz3rz/6/K3UTeqNPsid/NBg/EW6/Uz1dp8a1hOpxiN1h+/kDCfUdcfUGYz96rtv36SaDtV020eoNHuyZg8vU4USFsoN1HuvqFoDjouq7aLC++LtPaYKN5iTFcyXNLy4Vjh3KGttrHde/FwyL2OmWMZ/xyffFrvbRGUAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image8\",\n \"title\": \"image8\",\n \"src\": \"/static/3932446dab1e0c30b75d21010eda7bcb/e3189/image8.png\",\n \"srcSet\": [\"/static/3932446dab1e0c30b75d21010eda7bcb/a2ead/image8.png 259w\", \"/static/3932446dab1e0c30b75d21010eda7bcb/6b9fd/image8.png 518w\", \"/static/3932446dab1e0c30b75d21010eda7bcb/e3189/image8.png 1035w\", \"/static/3932446dab1e0c30b75d21010eda7bcb/d073d/image8.png 1297w\"],\n \"sizes\": \"(max-width: 1035px) 100vw, 1035px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"p\", null, \"We must accomplish the following five steps and multiple sub-steps:\"), mdx(\"p\", null, \"1) Define the What\"), mdx(\"pre\", null, mdx(\"code\", {\n parentName: \"pre\"\n }, \"a. What is the system under test (SUT)?\\n\\nb. What is the intended use of the SUT (operations and conditions)?\\n\\nc. What do you need to measure to determine combat capability of\\n the SUT?\\n\")), mdx(\"p\", null, \"2) Test Design\"), mdx(\"pre\", null, mdx(\"code\", {\n parentName: \"pre\"\n }, \"a. Establish goals of a test\\n\\nb. Pick test events to support the goal\\n\\nc. Define when the test is complete (exit criteria)\\n\")), mdx(\"p\", null, \"3) Test Execution Considerations\"), mdx(\"pre\", null, mdx(\"code\", {\n parentName: \"pre\"\n }, \"a. Create an operationally realistic environment\\n\\nb. Collect and gather data/information\\n\\nc. Test execution\\n\")), mdx(\"p\", null, \"4) Analysis and Evaluation\"), mdx(\"pre\", null, mdx(\"code\", {\n parentName: \"pre\"\n }, \"a. Analyze the data\\n\\nb. Evaluate the analysis to determine the \\\"so what\\\"\\n\\nc. Have exit criteria been met?\\n\")), mdx(\"p\", null, \"5) Conclusions and Reporting\"), mdx(\"pre\", null, mdx(\"code\", {\n parentName: \"pre\"\n }, \"a. Communicate results\\n\\nb. Determine impact to the warfighter\\n\")), mdx(\"p\", null, \"In general, you conduct these five main steps in order, but you may\\nreorder, abbreviate, move, or overlap them (e.g., analysis during\\nexecution).\"), mdx(\"h1\", null, \"Cycles of Test Activities\"), mdx(\"p\", null, \"Applying the five main steps can be a single flow through the five\\nsteps, or it may be multiple iterations at varying levels of test.\\nMultiple test activities may form an overall test and may be conducted\\nsingly, sequentially, concurrently, recursively, or nested and at\\ndifferent levels. Ultimately, however, the intent is to answer the\\nmission-level questions of the critical operational issues (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"). Figure\\n4-3 depicts the general relationship of test activities. Note the\\noverarching, or first level of test activity, is oriented to evaluating\\nmission effects that lead to a final report of combat capability.\"), mdx(\"p\", null, \"Figure 4\\u20113. Cycles of Test Activity\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"992px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/9c8f9d3ba9bdc5e1484dc04038cf319b/91f10/image9.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"63.32046332046332%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAACHVAAAh1QEEnLSdAAAEBklEQVQ4yx1Sa0ybVRh+e0EW98PIrVS2ITqYuikaXUxmwHTO6KBXkMkim1v84dhilmxRfhjRBiIYGLcChZbSSKGFXoBIoS30wqDXDyjw2QsrY1A6BnRjTh1MGXI87CRPnvd5npz3PW9y4PMGJxTUjJ0qFLkqChucP55vnRJ+IXIKC8p6hYJSlfBMhV6Y/1OPkP9Dl1CA8ZlQIyysHhZekM6UnhW56nmVw9n8X8yQV22jwN6xTcyBxeP/dsw7v2KfuTOptxHTxnEvqbe6yWG7lxy0esghG0GaxqdIw+gEOWB2ksaxKXLA4p4enQjeJQKR67OLGzAxt0J71lBvMMOgyZZ80zX98ZDF4bU4ydDE3LrbE1idsBIhQmdwEAOWSaJv2E3oR72EJ7hKeAL3PC7f3VmLO/iN2+NJCIe8MEnegm31AQCTzUEZtROAUDlIVUYuYR9qigRst5cDo/6Q1xgkrOqgy9ITdIyogjP2viD2g2G/zRf2WyO3HIqixRk9LHm19IirESJDxQAucyf4jUIqugxQPI/ggbGoMuIQ/b1488ZawFQZ9RkqorP6csw/P6tvW6uiEXvd2oqr6a91w4VGlAJ0JAHY7M2krA6eB0Ca41Begl861kj9R/kiO2ourr/jlHhmjVX2gLXO4bfUOQIYv4/UOILWese0oQrrWsfqlNy5aC7tjei/LFswXdqHPLVw33AFwCdmUh/2MAH1p722q0nNR+qDWaj/EAv1H2Yh3QHMySzUx2Sh3hQW0r6EdSrrqS7j5I485kTQVNUQMldZUP9b70U070BIm0OFkcpkWO9JemVNlfzbhpbRudHD6Ih2Jv76RBOvmFendrqUryumVUcUPk26wqdNVyxoDnXu6OIUOwOJis3++I4HqnhZtJuhX+tmvB3uSMYrI4DxZmaOX5aE1rri/72nSkTWtpeRUXNst0KXtV2jzN4RKbOQRHtit64rG91QZm8Pqo7tzsqZu1u6uMdhReJ/AXkSmhQzziFzAkBaXEpaPsALlz9lHMm8fvyTN0Q5V1J684qoEoGa1sr17WvneGPbOHN0OS9IkfExBDMgFoyDmPddguz0R2e+yjh69f24jMz0gxn7P3gzFmK68/ZTpNxL0M6vBjlfirkWpNzvqTKOiybhbFElHESRchBNzEYxTbmI3pyLaFL2E6qUE4F2XhmoCwSgPnsU7X1qOQ8g9sbpDHoLm6RL2G56K3t8DzFi9jJNylnG/sJzzewI5ghdnBvGA/7AmYsq55bQ2rkV9DbORWoH7xxFyb8GSv7XGO/CqxezIa70FDCvsSC+5CQ8f/VDGm5qx5efUmXcR7Q2zp90CUYL+xHWmzEtnCU8bInaxlnFW2zg/CHO7mPvMa63/gck4C8omRtM4wAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image9\",\n \"title\": \"image9\",\n \"src\": \"/static/9c8f9d3ba9bdc5e1484dc04038cf319b/91f10/image9.png\",\n \"srcSet\": [\"/static/9c8f9d3ba9bdc5e1484dc04038cf319b/a2ead/image9.png 259w\", \"/static/9c8f9d3ba9bdc5e1484dc04038cf319b/6b9fd/image9.png 518w\", \"/static/9c8f9d3ba9bdc5e1484dc04038cf319b/91f10/image9.png 992w\"],\n \"sizes\": \"(max-width: 992px) 100vw, 992px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"p\", null, \"You can construct an individual test activity (e.g., a test within the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \") at various system levels (mission effects,\\ncapabilities, functions/properties, structure). This is particularly\\nappropriate for acquisition strategies with a development model (such as\\nagile techniques) in which individual capabilities are developed\\nincrementally, but the full mission effect cannot be achieved until all\\nor many of the capabilities are present. In this case, you may construct\\ntest activities for individual capabilities or sets of capabilities.\\nWith some exceptions, you will follow the same five steps and construct\\nthem within the context of overarching COIs, operations, and mission\\neffects. Figures 4-4 through 4-6 depict applying multiple test\\nactivities notionally to an acquisition pathway.\"), mdx(\"p\", null, \"Figure 4\\u20114. Notional Test Activities for a Traditional Major Capability\\nAcquisition\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"1035px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/026f6a11df29bcc870713ce9e9afc43e/5c98f/image10.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"47.87644787644788%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAKCAYAAAC0VX7mAAAACXBIWXMAABcRAAAXEQHKJvM/AAACgElEQVQoz22QSUxTURSGT1uqCZYZJ7QhFaeFkVdmk7pRQlyQEIwLjSvRwAbjRg08kUTQGDEmuFQgFEFw4QobIaJMdgRDKaUtrW1ty7O1M1Cg1AjX8xBMSbjJl3POf/78790LF1smmpB6hN7BMw1d+nySljR8pM/ceEkX33tPl73Qbuq7eOtKWyaeXHiqrIVe1c+Rt0qmH5HFg7qsW+6SdQyZZK8+TMraBvWyHlaP92yjYvpx97lr3CkFVzBKHIHVTZyBKGFnFiYcIxYmRNR6K5kyM0Q9YyVGp5+4Qms7fP/9qNu8y7/AH17KX4yR3Mg6obzBBbF5PlikMPskX01eic4ZPrewtEwFF1eolT+EimwQCv2U2xcS6x3BEvmcT6JEr+JfPT9m8BRCXuP4beG11uoDFc23ih4p7p59KK/s03igR+4CqOjLKGjS1FIPhqtFVe01+8sba8QNYzdLHmvoo3c+iVsHrRBaioL2RwimHWGYsPoBusfts51DBkXHoE4hHbUZeuTO3ox6E7SNuqBz1F7cp2J0b8ZsSumXOXX7gFaNvRw/Znunmr//esQBA9MePgZyMZCLgVyYnLWRb0YHmbYwhO31dq8FoBLChMCUPVBm90ZIvEej/07wWYjZE+nyrhIYVs/wIf5YwiRf516jjP4NyhQgecYgOSXKFsKlyqtsaKLBt55v9BNqxh0T457CmZqaXy3Uun8La+uaYbdzCElDkpB05CAi4vF42VgPI5lbevqWLxURsDOfv+cI1qytHWczLSk55URKWroQaw7bJ+4THEf5GJLN5fFOJ6ek5iAiQVLyybSMzKwr16v4ZeWX9+YWlLBXTeBwOAlYedt/9xdZHKssSd18lwAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image10\",\n \"title\": \"image10\",\n \"src\": \"/static/026f6a11df29bcc870713ce9e9afc43e/e3189/image10.png\",\n \"srcSet\": [\"/static/026f6a11df29bcc870713ce9e9afc43e/a2ead/image10.png 259w\", \"/static/026f6a11df29bcc870713ce9e9afc43e/6b9fd/image10.png 518w\", \"/static/026f6a11df29bcc870713ce9e9afc43e/e3189/image10.png 1035w\", \"/static/026f6a11df29bcc870713ce9e9afc43e/5c98f/image10.png 1283w\"],\n \"sizes\": \"(max-width: 1035px) 100vw, 1035px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"p\", null, \"Figure 4\\u20115. Notional Test Activities for a\\nMajor Capability Acquisition\\\\\\nwith Incremental Capability Delivery\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"1035px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/78e986469d711751467fe0b3b1af4e0e/08037/image11.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"50.965250965250966%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAKCAYAAAC0VX7mAAAACXBIWXMAABcRAAAXEQHKJvM/AAACpElEQVQoz02Oa0hTYRjH31IqnBdCNNO8Oy8Z+SkoHA0Ckb5khlQaVNSHoMCkiyLUh74UGbiV7EyJiIxQIQIRsZrzsk1ycxd30+1surOds3M227S1swuG2XPiCHvhx/95/s+f53nRjWEPuooZutvlpneADMBSkF8bMmOtL6aw5sfvsQ5Mj3VA3y43ylMzwEA7Zhy9MqA7hVpfzZZbfJGvTia25aBZykFHaVDaybCUKxgnTWsb9KLdS/+wEbR2leRmfjwQ8zkY9n+Oy0OWtPujcZNn8za6+FJZT4VjXcxWAgtEtiVB9q80+CvZ79mIDULwg4cO9ZschNTuCUituFfiC7Fv7FT0E7MVl0BeyuUDkKfC8aFp20Ybqr/QmZ5/f7Yh7+7UuYOXsLOosVt8+M6kqLpnvrW2V3W58IFalHt9WJzW9Exc1DUjKn0013zyifpmXues6FDbkBideSjOvvWlsaJ7vkX0fFGEmno+lstnvHJMsaaXTlhUfWMLakyxrpFNe7SDM4QSUxIayfiyum9Uo5F9d6ug12LT63PyGUL9esKi6RsD/xs+J1N6VzCFuwU1944cdzG/F8y4b0dndUdMTh+7ZHNHcf9mzBdOxsCP6qwu1rBKsHrbWhSnwiwRSsSsbiqqteCsyUmyMI/gZGjXFWDvofNPP6NFD1tsIBM1Bl9caGG2q8zMH+ES1DqCFVoCO0LOX6aSQgMZF+qh1pPJKiP0RjIBxIUax8+a+ZVgncLsP4wK6k7vQwhVAiVAAVAIlPEU8z7nlfJ6DCji4WblQPrIpAp5E7sI5VY0oAxBZpkgM6s2KzunArQG+nquzszKrswQCE5wM6B6LwN+Varm5uXnvx0ZT2N3YSH/jvIXj/BXi3mvJOUnhbzmAGk86cB+4MDeon8XMZMF/XYbUwAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image11\",\n \"title\": \"image11\",\n \"src\": \"/static/78e986469d711751467fe0b3b1af4e0e/e3189/image11.png\",\n \"srcSet\": [\"/static/78e986469d711751467fe0b3b1af4e0e/a2ead/image11.png 259w\", \"/static/78e986469d711751467fe0b3b1af4e0e/6b9fd/image11.png 518w\", \"/static/78e986469d711751467fe0b3b1af4e0e/e3189/image11.png 1035w\", \"/static/78e986469d711751467fe0b3b1af4e0e/08037/image11.png 1379w\"],\n \"sizes\": \"(max-width: 1035px) 100vw, 1035px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"p\", null, \"Figure 4\\u20116. Notional Cycles of Test Activities\\nfor a Software Acquisition\\\\\\nUsing Sprints to Deliver Capabilities\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"1035px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/614bf2a0c6f6998a7e784972cce0e975/08037/image12.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"62.16216216216216%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAYAAABiDJ37AAAACXBIWXMAABcRAAAXEQHKJvM/AAADgUlEQVQoz02RfUwTZxzHny1z/rNs2YtThxMwboujRUayxfDSLLq5LCEGxohiQB17021o1jHRRBxCwDAsnde7Uh2d02ha3eqymQXowL4BPYcUWun1lbbXXnt3BQRsS9mMdL9z/OEfn+TzfJ7vX8+D9l8Kot3E2NE9yvGePUobDhArKHcDe1V2ory9l3i34QJRTYwS1XAW+qM7AIOmqcJuvYkqOg05dnqh180mZ12xRBhgXLFk1B1LRrxcirZNxaNWJ82M3AkyJBUR7hgPm6SFzcNtNMHAlp5kEklbYPZjVN4xKGJmU9+wc+nz3MK/GJ98gHPzS1gwnurxcKnLgdgMNu4O4s4gi9/x0orITFJJRRNa2Ctgj/PJZZyFPXN3UT3ojH+ICvc2rXrxiCH/hUO9bz9ZQZSiom8lz37+Z/GrjabyLcfNVeul5uLnai9JHn+nWZL1taE4u8G4M/+E5cCawzeLV1eqJGibVPJ03fWiTUfNu0rbyRK0XarOIgZCBK6fGpX/4TB2aIfNin6/BdMHSGIgOAB3lq7fJ8wd2iEz1uc1Kf4Kkbg+YIBugv3/vddzE7oT1/t3obKWG+9TkbnRcXcoY3PTqdtUKH3L4U27wjNLoenFJZsrmIaeHnPRi9YJd9odnl4KCt0dghZ62Em7J0WF+IyPS30Fn2J8LZPJrAHWm3yJgqskUwr+PEmnxRoyJgFfG55/8MpFS3iHsPknk8lRmyLvCZ5aFpwWfN3d+5nNJ69730Jv1LSuKmjs277pgKq6sOG3Q9tODdVl1ygqC6S6z4paRz7JrVVUiY9c21fSZv0ipwarEtVra0vbrPW5+5SVonrNRyVtI1/m7u+uENdrDu6U24tQ2Xe6bOLGeLdMaxyT68i/z/U7DeDDXb9awSmjTGMYErqqjzKDm6GPglu6tEaT7NrwbVU/ZZZfNRlkvwxT5wd8H6CyZp3IxczpHf7oPEVPsz52IQ7OgnN+7h4PzrnoOO9n7/F2X5SDtxJ63O5jOGeQ5wJ8kp/wRFiHP5aepGcPok+vTKG6w8dFJ8+c29qK/fx6C3ZxS9P33fnHTivyG9sV4pazP4lOydV5x04T4tazF/KaOlXipjM/5rX8oBad6OwWS5tlW3t0g5vt/PKGfjv7FNpYuOMxhFA28DKwDsh6hI0r7SVgA7B2ZZcDPAM8AayGT0GWyQhycPfRf+oOTSKP6SH8AAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image12\",\n \"title\": \"image12\",\n \"src\": \"/static/614bf2a0c6f6998a7e784972cce0e975/e3189/image12.png\",\n \"srcSet\": [\"/static/614bf2a0c6f6998a7e784972cce0e975/a2ead/image12.png 259w\", \"/static/614bf2a0c6f6998a7e784972cce0e975/6b9fd/image12.png 518w\", \"/static/614bf2a0c6f6998a7e784972cce0e975/e3189/image12.png 1035w\", \"/static/614bf2a0c6f6998a7e784972cce0e975/08037/image12.png 1379w\"],\n \"sizes\": \"(max-width: 1035px) 100vw, 1035px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#test-analyze-and-fix-re-test","title":"Test, Analyze, and Fix (Re-Test)"},{"url":"#test-activity","title":"Test Activity"},{"url":"#cycles-of-test-activities","title":"Cycles of Test Activities"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/4-2-OT-test-activity-cycles.md"},"frontmatter":{"metaTitle":"OT&E Test Activity Cycles","metaDescription":"OT&E Test Activity Cycles"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"28dc0493-e6d2-51fc-abc3-bfd04ede6533"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/4-3-OT-construct/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/4-3-OT-construct","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"0b71c49c-d37d-5497-a1c8-7b722e49381c","title":"OT&E Construct","slug":"/OT&E_Guide/4-3-OT-construct"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"OT&E Construct\",\n \"metaTitle\": \"OT&E Construct\",\n \"metaDescription\": \"OT&E Construct\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct is the framework for conducting operational test. It\\nidentifies the following elements of an operational test and their\\nrelationship to each other:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Operational Effectiveness.\"), \" Measurement of the system's overall\\nability to accomplish a mission when used by representative\\npersonnel in the expected/planned operational environment\\nconsidering organization, doctrine, supportability, survivability,\\nvulnerability, and threat. (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 99-103, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Capability Based Test and\\nEvaluation\"), \"). Typically, referred to as \\\"effectiveness.\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Operational Suitability.\"), \" The degree to which a system can be\\nplaced satisfactorily for use in the field considering its\\navailability, compatibility, transportability, interoperability,\\nreliability, wartime usage rates, maintainability, safety, human\\nfactors, manpower supportability, logistics supportability, natural\\nenvironmental effects and impacts, documentation, and training\\nrequirements. (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 99-103). Typically, referred to as \\\"suitability.\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Mission Statement.\"), \" Mission statements are written at a high,\\noverarching level consistent with the mission the system is intended\\nto support or enable.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Critical Operational Issues (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \").\"), \" A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" addresses a critical\\nmission element or operational objective examined during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E to\\ndetermine the system's overall capability to support mission\\naccomplishment (often referred to as operations-based COIs).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Operations.\"), \" A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" is composed of one or more operations.\\nOperations describe the actions, activities, or phases of a mission\\nneeded to accomplish the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". With two or more operations, the\\noverarching operational objective is the same; however, the steps\\nand/or conditions to achieve the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" are different between\\noperations.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Mission Effects.\"), \" Mission effects are outcomes or results of\\nconducting an operation.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Operational Capabilities.\"), \" OCs provide operational context for\\nsystem capabilities or attributes of high interest or importance\\nwithin an operation. It may be useful to distinguish between system\\ncapabilities (i.e., the potential to perform some action) and system\\nattributes (i.e., the functions, properties, structure) of a system.\\nOperational capabilities provide the means to conduct an operation\\nand achieve effects.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Operational (User) Requirements.\"), \" A system capability, attribute,\\nor characteristic required to accomplish approved capability needs.\\nOperational requirements (including suitability) are typically\\nperformance attributes, but they may also be derived from cost and\\nschedule (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 10-601). Typically referred to as \\\"requirements.\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Operational Conditions.\"), \" Operational conditions are identified for\\neach \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or operation and depict the operational battlespace. An\\noperational condition is defined by a set of factors, each set at a\\ngiven level. A factor is a variable of the environment that may\\naffect task performance. A level is a set value within the range of\\nvalues a factor can hold.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Measures.\"), \" Measures are designed to convey information about a\\nsystem's effect, capabilities, functions, properties, or structure\\nbeing addressed.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Data/Data Element.\"), \" Data is any measurement or information used to\\ndetermine the value of a measure. Data may be quantitative,\\nqualitative, subjective, or objective.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Design.\"), \" The test design is a set of test events for each\\noperation and battlespace condition, including the rationale for\\nselecting the test events.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Event.\"), \" A test event is a single execution of an operation or\\nsequence/set of operations under specified conditions for the\\noperations.\"))), mdx(\"p\", null, \"There is no single depiction relating these elements to each other.\\nFigure 4-7 shows an example of a tool used to capture initial elements\\nof the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct and their relationships.\"), mdx(\"p\", null, \"Figure 4\\u20117. Measure of Effectiveness (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \")\\nInitial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct Example\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"1035px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/2e9633d6075c7cf286a3bc2677c96687/d318f/image13.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"33.59073359073359%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAHCAYAAAAIy204AAAACXBIWXMAABcRAAAXEQHKJvM/AAABl0lEQVQozy2Sa08TURCGn7Z7vzXLdndp91bAbgtiLBRETBQ1oiYKMWoUPyhr/Df+QX+OvhvcZDJzzsyc95nJwv9vwm8cHjcBnxcebxqTe1nA15OAT63Bburz4Tjg5sjmtPJ5v1Ru4/K8cDhXz815wJe1evL+rREMLXnb4iCzeTQ2mIdDkrEaUomEyvkW69jlIjGoY4PSc3kVqcWxOSl9rnZ8rhcWD0sifm25PBuu+IvHu7nL5VSEucdlbnM89vkYOzxNVKMHX2Yer7clMAi59Xtvc5SZ7PvykegLTPYcJUyZJbWZw5NtkVQapZRVLi9yUZYeb1d6uLLZTIfEnoR2NZljcVhaPJhIXACnez1hHPLNa/iDxtHlZjbAHWvkZESRmrRbEhtrP6K86Ok86QeiLRS7I2aFQZOOyCcD7BTNP5N63u9L2HOL+7XIltpnbbKSwFklAt2vS+23EFEj0b6m7u9MFrXodhzOWpNlTcj3A9kq5MdhRNdG/NwP6XTuWlkfK99NtbNMNal8ehffTu/OXR/nihP9IYN/W0sw8TdgmwsAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image13\",\n \"title\": \"image13\",\n \"src\": \"/static/2e9633d6075c7cf286a3bc2677c96687/e3189/image13.png\",\n \"srcSet\": [\"/static/2e9633d6075c7cf286a3bc2677c96687/a2ead/image13.png 259w\", \"/static/2e9633d6075c7cf286a3bc2677c96687/6b9fd/image13.png 518w\", \"/static/2e9633d6075c7cf286a3bc2677c96687/e3189/image13.png 1035w\", \"/static/2e9633d6075c7cf286a3bc2677c96687/d318f/image13.png 1421w\"],\n \"sizes\": \"(max-width: 1035px) 100vw, 1035px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct is a constantly evolving and maturing framework. You\\nwill develop the construct using multiple steps, possibly with multiple\\niterations, while applying \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles (early, tailoring, adapting,\\ncontinuous and cumulative, streamline, and integrating).\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct evolves, but starts with COIs, operations, and\\nmeasures of effectiveness (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \"). You may use other tools to depict\\nelements of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct and their relationships (\", mdx(\"em\", {\n parentName: \"p\"\n }, \"see\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct Guide).\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct relates to the levels-of-test pyramid. Generally,\\nCOIs and operations correlate to mission effects. You can make testing\\nand corresponding measures at all levels of the pyramid. While the focus\\nof operational testing is mission effects achieved, individual test\\nactivities may focus on a system's capabilities or its functions,\\nproperties, and/or structure. These test activities should always be in\\nthe context of enabling or contributing to mission effects.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OT&E_Guide/4-3-OT-construct.md"},"frontmatter":{"metaTitle":"OT&E Construct","metaDescription":"OT&E Construct"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"0b71c49c-d37d-5497-a1c8-7b722e49381c"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/4-3-OT-construct","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"0b71c49c-d37d-5497-a1c8-7b722e49381c","title":"OT&E Construct","slug":"/OT&E_Guide/4-3-OT-construct"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"OT&E Construct\",\n \"metaTitle\": \"OT&E Construct\",\n \"metaDescription\": \"OT&E Construct\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct is the framework for conducting operational test. It\\nidentifies the following elements of an operational test and their\\nrelationship to each other:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Operational Effectiveness.\"), \" Measurement of the system's overall\\nability to accomplish a mission when used by representative\\npersonnel in the expected/planned operational environment\\nconsidering organization, doctrine, supportability, survivability,\\nvulnerability, and threat. (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 99-103, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Capability Based Test and\\nEvaluation\"), \"). Typically, referred to as \\\"effectiveness.\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Operational Suitability.\"), \" The degree to which a system can be\\nplaced satisfactorily for use in the field considering its\\navailability, compatibility, transportability, interoperability,\\nreliability, wartime usage rates, maintainability, safety, human\\nfactors, manpower supportability, logistics supportability, natural\\nenvironmental effects and impacts, documentation, and training\\nrequirements. (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 99-103). Typically, referred to as \\\"suitability.\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Mission Statement.\"), \" Mission statements are written at a high,\\noverarching level consistent with the mission the system is intended\\nto support or enable.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Critical Operational Issues (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \").\"), \" A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" addresses a critical\\nmission element or operational objective examined during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E to\\ndetermine the system's overall capability to support mission\\naccomplishment (often referred to as operations-based COIs).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Operations.\"), \" A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" is composed of one or more operations.\\nOperations describe the actions, activities, or phases of a mission\\nneeded to accomplish the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". With two or more operations, the\\noverarching operational objective is the same; however, the steps\\nand/or conditions to achieve the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" are different between\\noperations.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Mission Effects.\"), \" Mission effects are outcomes or results of\\nconducting an operation.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Operational Capabilities.\"), \" OCs provide operational context for\\nsystem capabilities or attributes of high interest or importance\\nwithin an operation. It may be useful to distinguish between system\\ncapabilities (i.e., the potential to perform some action) and system\\nattributes (i.e., the functions, properties, structure) of a system.\\nOperational capabilities provide the means to conduct an operation\\nand achieve effects.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Operational (User) Requirements.\"), \" A system capability, attribute,\\nor characteristic required to accomplish approved capability needs.\\nOperational requirements (including suitability) are typically\\nperformance attributes, but they may also be derived from cost and\\nschedule (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 10-601). Typically referred to as \\\"requirements.\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Operational Conditions.\"), \" Operational conditions are identified for\\neach \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or operation and depict the operational battlespace. An\\noperational condition is defined by a set of factors, each set at a\\ngiven level. A factor is a variable of the environment that may\\naffect task performance. A level is a set value within the range of\\nvalues a factor can hold.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Measures.\"), \" Measures are designed to convey information about a\\nsystem's effect, capabilities, functions, properties, or structure\\nbeing addressed.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Data/Data Element.\"), \" Data is any measurement or information used to\\ndetermine the value of a measure. Data may be quantitative,\\nqualitative, subjective, or objective.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Design.\"), \" The test design is a set of test events for each\\noperation and battlespace condition, including the rationale for\\nselecting the test events.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Event.\"), \" A test event is a single execution of an operation or\\nsequence/set of operations under specified conditions for the\\noperations.\"))), mdx(\"p\", null, \"There is no single depiction relating these elements to each other.\\nFigure 4-7 shows an example of a tool used to capture initial elements\\nof the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct and their relationships.\"), mdx(\"p\", null, \"Figure 4\\u20117. Measure of Effectiveness (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \")\\nInitial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct Example\"), mdx(\"p\", null, mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"1035px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/2e9633d6075c7cf286a3bc2677c96687/d318f/image13.png\",\n \"style\": {\n \"display\": \"block\"\n },\n \"target\": \"_blank\",\n \"rel\": \"noopener\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"33.59073359073359%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAHCAYAAAAIy204AAAACXBIWXMAABcRAAAXEQHKJvM/AAABl0lEQVQozy2Sa08TURCGn7Z7vzXLdndp91bAbgtiLBRETBQ1oiYKMWoUPyhr/Df+QX+OvhvcZDJzzsyc95nJwv9vwm8cHjcBnxcebxqTe1nA15OAT63Bburz4Tjg5sjmtPJ5v1Ru4/K8cDhXz815wJe1evL+rREMLXnb4iCzeTQ2mIdDkrEaUomEyvkW69jlIjGoY4PSc3kVqcWxOSl9rnZ8rhcWD0sifm25PBuu+IvHu7nL5VSEucdlbnM89vkYOzxNVKMHX2Yer7clMAi59Xtvc5SZ7PvykegLTPYcJUyZJbWZw5NtkVQapZRVLi9yUZYeb1d6uLLZTIfEnoR2NZljcVhaPJhIXACnez1hHPLNa/iDxtHlZjbAHWvkZESRmrRbEhtrP6K86Ok86QeiLRS7I2aFQZOOyCcD7BTNP5N63u9L2HOL+7XIltpnbbKSwFklAt2vS+23EFEj0b6m7u9MFrXodhzOWpNlTcj3A9kq5MdhRNdG/NwP6XTuWlkfK99NtbNMNal8ehffTu/OXR/nihP9IYN/W0sw8TdgmwsAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image13\",\n \"title\": \"image13\",\n \"src\": \"/static/2e9633d6075c7cf286a3bc2677c96687/e3189/image13.png\",\n \"srcSet\": [\"/static/2e9633d6075c7cf286a3bc2677c96687/a2ead/image13.png 259w\", \"/static/2e9633d6075c7cf286a3bc2677c96687/6b9fd/image13.png 518w\", \"/static/2e9633d6075c7cf286a3bc2677c96687/e3189/image13.png 1035w\", \"/static/2e9633d6075c7cf286a3bc2677c96687/d318f/image13.png 1421w\"],\n \"sizes\": \"(max-width: 1035px) 100vw, 1035px\",\n \"style\": {\n \"width\": \"100%\",\n \"height\": \"100%\",\n \"margin\": \"0\",\n \"verticalAlign\": \"middle\",\n \"position\": \"absolute\",\n \"top\": \"0\",\n \"left\": \"0\"\n },\n \"loading\": \"lazy\"\n }), \"\\n \"), \"\\n \")), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct is a constantly evolving and maturing framework. You\\nwill develop the construct using multiple steps, possibly with multiple\\niterations, while applying \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles (early, tailoring, adapting,\\ncontinuous and cumulative, streamline, and integrating).\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct evolves, but starts with COIs, operations, and\\nmeasures of effectiveness (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \"). You may use other tools to depict\\nelements of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct and their relationships (\", mdx(\"em\", {\n parentName: \"p\"\n }, \"see\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct Guide).\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct relates to the levels-of-test pyramid. Generally,\\nCOIs and operations correlate to mission effects. You can make testing\\nand corresponding measures at all levels of the pyramid. While the focus\\nof operational testing is mission effects achieved, individual test\\nactivities may focus on a system's capabilities or its functions,\\nproperties, and/or structure. These test activities should always be in\\nthe context of enabling or contributing to mission effects.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OT&E_Guide/4-3-OT-construct.md"},"frontmatter":{"metaTitle":"OT&E Construct","metaDescription":"OT&E Construct"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"0b71c49c-d37d-5497-a1c8-7b722e49381c"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/4-4-building-the-ot-construct/page-data.json
View file @ 784fbeaf
This source diff could not be displayed because it is too large. You can view the blob instead.
sites/oteguide/page-data/OT&E_Guide/5-test-lifecycle-exit/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/5-test-lifecycle-exit","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"df270c7b-4f84-539a-a079-d3fadad09785","title":"Test Lifecycle: Exit","slug":"/OT&E_Guide/5-test-lifecycle-exit"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Test Lifecycle: Exit\",\n \"metaTitle\": \"Test Lifecycle: Exit\",\n \"metaDescription\": \"Test Lifecycle: Exit\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"h1\", null, \"Exit Criteria\"), mdx(\"p\", null, \"In order to declare operational testing complete, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" must meet the\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit Criteria\"), \" defined in a program's test strategy. Otherwise, testing\\ncan drag out and flow into the next operational test phase, which\\nchallenges the notion of a finished milestone (i.e., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E followed by\\nan \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Operational Test and Evaluation\"\n }, \"FOT&E\"), \" for unfinished \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E measures).\"), mdx(\"p\", null, \"Operational testing is overly influenced by \\\"entrance criteria,\\\" which\\nis inconsistent with our \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles of early and continuous\\ninvolvement. Legacy and adaptive acquisition strategies use entrance\\ncriteria to enter a new acquisition phase as opposed to \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit Criteria\"), \"\\nto exit an acquisition phase. For example, an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Readiness Review\"\n }, \"OTRR\"), \" uses entrance\\ncriteria to determine whether the overall system under test is ready to\\nenter \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \", rather than assessing the applicability of existing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" data.\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s test strategy promotes gathering test data points \", mdx(\"em\", {\n parentName: \"p\"\n }, \"throughout\"), \"\\nthe acquisition program, which makes dependence on entrance criteria, as\\nrequired for an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Readiness Review\"\n }, \"OTRR\"), \", unnecessary. The objective of an \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit Criteria\"), \"\\napproach is early discovery to enable early fixes, which in turn yields\\n\\\"faster and smarter\\\" delivery of combat capability.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit Criteria\"), \" can be based on singular criterion or a combination of\\nseveral criteria (i.e., time, events, performance, planning) as\\ninfluenced by the type and timing of the test activity. Exit criteria\\nevolves as do other aspects of planned test activities. Test strategies\\nincorporate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" status reviews, when appropriate, to assess test activity\\ndata points against \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" measures, and determine whether we need to\\nconduct additional test activities to meet the test strategy's \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit\\nCriteria\"), \". Test reporting deliverables depend on when we complete exit\\ncriteria. Involved organizations\", \"-\", \"-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \", OTAs, SPOs, and others\", \"-\", \"-must\\nhave a broad understanding of the test strategy and its associated \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit\\nCriteria\"), \". The following are examples of exit criteria for a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \":\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Desired and sufficient coverage of the requirements and\\nfunctionalities under the defined test\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Budget\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Schedule\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Acquisition strategy\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Execution of test cases\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Identified DRs are addressed or there is a plan to address them\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Retesting (if required) and high-priority defects closed to execute\\ncorresponding regression scenarios that must be completed\\nsuccessfully\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"All identified high priority, severity, and/or issues have been\\nincluded (ex: KC-46 boom operations)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"An assessment as to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or test measure data sufficiency\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"An assessment as to developmental activities projected or planned\\nwithin the timeline defined by AQ\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A fielding decision or acquisition decision with no further\\ndevelopmental activities\"))), mdx(\"p\", null, \"As discussed previously, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assesses results of test activities to\\ndetermine whether we fulfilled our exit criteria. In addition, we assess\\nresults for every test strategy activity prior to completing the test\\nlifecycle. When we fulfill the test strategy's macroscopic exit\\ncriteria, the test lifecycle reaches its final exit phase.\"), mdx(\"p\", null, \"Exit activities may include final documentation, transfer or relocation\\nof personnel and test assets, contract modification or termination, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \"\\nand \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Understanding\"\n }, \"MOU\"), \" termination, and deactivation of operating locations and/or\\ndetachments.\"), mdx(\"p\", null, \"Test teams produce a final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E report for most programs, with the\\nexception of experimentation or prototype test programs, which do not\\nrequire one. They produces a final report after the culmination of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nactivities. The final report provides the determination of effectiveness\\nand suitability, and results of COIs and measures. These reports are\\ncumulative and contain all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" feedback that led up to a particular\\nmilestone or decision point. They provide evaluations of a system's\\noperational effectiveness and suitability while typical operators and\\nmaintainers employ them in realistic operational environments (including\\nexposure to representative threats). Evaluations require operational\\nexperience to apply judgment and place system performance in the context\\nof intended operations. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not base its operational evaluations\\non findings caused by operational unit or operator performance\\nshortfalls that are not attributable to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" organizations manage and oversee additional exit activities. The\\nfollowing is a list of what each office manages and oversees:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"HQ AFOTEC History Office\"\n }, \"HO\"), \": Maintaining historical files\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-1: Transferring or relocating test personnel\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-2/9: Lessons learned program\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3: Transferring or relocating test assets\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-4/7: Modifying or terminating contracts\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-5/8: Terminating MOAs and MOUs, and deactivating OLs and/or Dets\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#exit-criteria","title":"Exit Criteria"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/5-test-lifecycle-exit.md"},"frontmatter":{"metaTitle":"Test Lifecycle: Exit","metaDescription":"Test Lifecycle: Exit"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"df270c7b-4f84-539a-a079-d3fadad09785"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/5-test-lifecycle-exit","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"df270c7b-4f84-539a-a079-d3fadad09785","title":"Test Lifecycle: Exit","slug":"/OT&E_Guide/5-test-lifecycle-exit"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Test Lifecycle: Exit\",\n \"metaTitle\": \"Test Lifecycle: Exit\",\n \"metaDescription\": \"Test Lifecycle: Exit\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"h1\", null, \"Exit Criteria\"), mdx(\"p\", null, \"In order to declare operational testing complete, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" must meet the\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit Criteria\"), \" defined in a program's test strategy. Otherwise, testing\\ncan drag out and flow into the next operational test phase, which\\nchallenges the notion of a finished milestone (i.e., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E followed by\\nan \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Operational Test and Evaluation\"\n }, \"FOT&E\"), \" for unfinished \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E measures).\"), mdx(\"p\", null, \"Operational testing is overly influenced by \\\"entrance criteria,\\\" which\\nis inconsistent with our \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles of early and continuous\\ninvolvement. Legacy and adaptive acquisition strategies use entrance\\ncriteria to enter a new acquisition phase as opposed to \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit Criteria\"), \"\\nto exit an acquisition phase. For example, an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Readiness Review\"\n }, \"OTRR\"), \" uses entrance\\ncriteria to determine whether the overall system under test is ready to\\nenter \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \", rather than assessing the applicability of existing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" data.\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s test strategy promotes gathering test data points \", mdx(\"em\", {\n parentName: \"p\"\n }, \"throughout\"), \"\\nthe acquisition program, which makes dependence on entrance criteria, as\\nrequired for an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Readiness Review\"\n }, \"OTRR\"), \", unnecessary. The objective of an \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit Criteria\"), \"\\napproach is early discovery to enable early fixes, which in turn yields\\n\\\"faster and smarter\\\" delivery of combat capability.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit Criteria\"), \" can be based on singular criterion or a combination of\\nseveral criteria (i.e., time, events, performance, planning) as\\ninfluenced by the type and timing of the test activity. Exit criteria\\nevolves as do other aspects of planned test activities. Test strategies\\nincorporate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" status reviews, when appropriate, to assess test activity\\ndata points against \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" measures, and determine whether we need to\\nconduct additional test activities to meet the test strategy's \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit\\nCriteria\"), \". Test reporting deliverables depend on when we complete exit\\ncriteria. Involved organizations\", \"-\", \"-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \", OTAs, SPOs, and others\", \"-\", \"-must\\nhave a broad understanding of the test strategy and its associated \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Exit\\nCriteria\"), \". The following are examples of exit criteria for a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \":\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Desired and sufficient coverage of the requirements and\\nfunctionalities under the defined test\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Budget\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Schedule\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Acquisition strategy\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Execution of test cases\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Identified DRs are addressed or there is a plan to address them\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Retesting (if required) and high-priority defects closed to execute\\ncorresponding regression scenarios that must be completed\\nsuccessfully\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"All identified high priority, severity, and/or issues have been\\nincluded (ex: KC-46 boom operations)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"An assessment as to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or test measure data sufficiency\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"An assessment as to developmental activities projected or planned\\nwithin the timeline defined by AQ\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A fielding decision or acquisition decision with no further\\ndevelopmental activities\"))), mdx(\"p\", null, \"As discussed previously, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assesses results of test activities to\\ndetermine whether we fulfilled our exit criteria. In addition, we assess\\nresults for every test strategy activity prior to completing the test\\nlifecycle. When we fulfill the test strategy's macroscopic exit\\ncriteria, the test lifecycle reaches its final exit phase.\"), mdx(\"p\", null, \"Exit activities may include final documentation, transfer or relocation\\nof personnel and test assets, contract modification or termination, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \"\\nand \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Understanding\"\n }, \"MOU\"), \" termination, and deactivation of operating locations and/or\\ndetachments.\"), mdx(\"p\", null, \"Test teams produce a final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E report for most programs, with the\\nexception of experimentation or prototype test programs, which do not\\nrequire one. They produces a final report after the culmination of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nactivities. The final report provides the determination of effectiveness\\nand suitability, and results of COIs and measures. These reports are\\ncumulative and contain all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" feedback that led up to a particular\\nmilestone or decision point. They provide evaluations of a system's\\noperational effectiveness and suitability while typical operators and\\nmaintainers employ them in realistic operational environments (including\\nexposure to representative threats). Evaluations require operational\\nexperience to apply judgment and place system performance in the context\\nof intended operations. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not base its operational evaluations\\non findings caused by operational unit or operator performance\\nshortfalls that are not attributable to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" organizations manage and oversee additional exit activities. The\\nfollowing is a list of what each office manages and oversees:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"HQ AFOTEC History Office\"\n }, \"HO\"), \": Maintaining historical files\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-1: Transferring or relocating test personnel\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-2/9: Lessons learned program\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3: Transferring or relocating test assets\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-4/7: Modifying or terminating contracts\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-5/8: Terminating MOAs and MOUs, and deactivating OLs and/or Dets\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#exit-criteria","title":"Exit Criteria"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/5-test-lifecycle-exit.md"},"frontmatter":{"metaTitle":"Test Lifecycle: Exit","metaDescription":"Test Lifecycle: Exit"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"df270c7b-4f84-539a-a079-d3fadad09785"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/6-0-ot-business-practices/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-0-ot-business-practices","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"48e1e761-73cd-59aa-8cde-8166a475e5bb","title":"OT Business Practices","slug":"/OT&E_Guide/6-0-ot-business-practices"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"OT Business Practices\",\n \"metaTitle\": \"OT Business Practices\",\n \"metaDescription\": \"Begins with a conceptual model of a system and the mission effects a system enables. It introduces the OT&E Construct as a framework and test activities as building blocks. It outlines five general steps that define a test activity.\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"The essence of sound business processes reside in their simplicity. A\\nseries of logically related activities or tasks that when performed\\ntogether, or sequentially, produce defined results. The events listed in\\nthis section take place in the course of an operational test. Some occur\\nonce, while others recur multiple times throughout its course. The\\nintent of these business processes is to establish a baseline of\\nexpectations when we involve in, task, resource, and coordinate test\\nrequirements.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-0-ot-business-practices.md"},"frontmatter":{"metaTitle":"OT Business Practices","metaDescription":"Begins with a conceptual model of a system and the mission effects a system enables. It introduces the OT&E Construct as a framework and test activities as building blocks. It outlines five general steps that define a test activity."}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"48e1e761-73cd-59aa-8cde-8166a475e5bb"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-0-ot-business-practices","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"48e1e761-73cd-59aa-8cde-8166a475e5bb","title":"OT Business Practices","slug":"/OT&E_Guide/6-0-ot-business-practices"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"OT Business Practices\",\n \"metaTitle\": \"OT Business Practices\",\n \"metaDescription\": \"Begins with a conceptual model of a system and the mission effects a system enables. It introduces the OT&E Construct as a framework and test activities as building blocks. It outlines five general steps that define a test activity.\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"The essence of sound business processes reside in their simplicity. A\\nseries of logically related activities or tasks that when performed\\ntogether, or sequentially, produce defined results. The events listed in\\nthis section take place in the course of an operational test. Some occur\\nonce, while others recur multiple times throughout its course. The\\nintent of these business processes is to establish a baseline of\\nexpectations when we involve in, task, resource, and coordinate test\\nrequirements.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-0-ot-business-practices.md"},"frontmatter":{"metaTitle":"OT Business Practices","metaDescription":"Begins with a conceptual model of a system and the mission effects a system enables. It introduces the OT&E Construct as a framework and test activities as building blocks. It outlines five general steps that define a test activity."}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"48e1e761-73cd-59aa-8cde-8166a475e5bb"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/6-1-1-tasking/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-1-1-tasking","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"20bd56bd-5943-5a4b-922f-f71eb7ca8a2b","title":"Tasking","slug":"/OT&E_Guide/6-1-1-tasking"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Tasking\",\n \"metaTitle\": \"Tasking\",\n \"metaDescription\": \"Tasking\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"h1\", null, \"Initial Tasking Order\"), mdx(\"p\", null, \"The tasking order is the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"'s broad direction on the scope of our\\ninvolvement, allocation of resources, and the test team's\\nresponsibilities, including whether we need an operating location and\\nwhat required deliverables we will produce. A-3 initiates and\\ncoordinates the initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \", which identifies the lead and supporting\\nDetachments, the projected timeline to present a test strategy (and, if\\nrequired, an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \"), and directs development of the initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \". The\\nA-Staff supports the Detachment throughout its execution of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \".\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" and the Detachment fund resources for the program until we secure\\nfunding from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Office\"\n }, \"SPO\"), \", which is based on the dollar amount of the test.\"), mdx(\"h1\", null, \"Tasking Order Update\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" updates TOs every 2 years, when the current \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" expires, or when\\nthe program undergoes significant changes. TOs and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" updates are\\nhistorical documents that capture a program's progression by updating\\ntimelines, tracking resources, and maintaining a list of former/current\\ntest team members (former test team members can be good sources of\\ninformation about a program). With support from the responsible\\nDetachment, A-3 staffs and coordinates the updated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \", along with the\\nsupporting \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \". A-3 is the signature approval authority for changes\\nwithin the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \", and verifies that the updated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" and current \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" match so\\nthere are no unintended disconnects when tracking the program's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nfunds.\"), mdx(\"h1\", null, \"Program Transfer\"), mdx(\"p\", null, \"If a program transfers from one Detachment to another (or from a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" to\\nA-3), the losing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" ensures his team completes applicable program\\ntransfer checklist items. The Detachment will prepare a memorandum for\\nrecord (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum for Record\"\n }, \"MFR\"), \") and submit it to the A-3 Director of Operations. Both the\\ntransfer checklist and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum for Record\"\n }, \"MFR\"), \" are available on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SharePoint.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#initial-tasking-order","title":"Initial Tasking Order"},{"url":"#tasking-order-update","title":"Tasking Order Update"},{"url":"#program-transfer","title":"Program Transfer"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-1-1-tasking.md"},"frontmatter":{"metaTitle":"Tasking","metaDescription":"Tasking"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"20bd56bd-5943-5a4b-922f-f71eb7ca8a2b"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-1-1-tasking","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"20bd56bd-5943-5a4b-922f-f71eb7ca8a2b","title":"Tasking","slug":"/OT&E_Guide/6-1-1-tasking"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Tasking\",\n \"metaTitle\": \"Tasking\",\n \"metaDescription\": \"Tasking\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"h1\", null, \"Initial Tasking Order\"), mdx(\"p\", null, \"The tasking order is the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"'s broad direction on the scope of our\\ninvolvement, allocation of resources, and the test team's\\nresponsibilities, including whether we need an operating location and\\nwhat required deliverables we will produce. A-3 initiates and\\ncoordinates the initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \", which identifies the lead and supporting\\nDetachments, the projected timeline to present a test strategy (and, if\\nrequired, an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \"), and directs development of the initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \". The\\nA-Staff supports the Detachment throughout its execution of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \".\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" and the Detachment fund resources for the program until we secure\\nfunding from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Office\"\n }, \"SPO\"), \", which is based on the dollar amount of the test.\"), mdx(\"h1\", null, \"Tasking Order Update\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" updates TOs every 2 years, when the current \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" expires, or when\\nthe program undergoes significant changes. TOs and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" updates are\\nhistorical documents that capture a program's progression by updating\\ntimelines, tracking resources, and maintaining a list of former/current\\ntest team members (former test team members can be good sources of\\ninformation about a program). With support from the responsible\\nDetachment, A-3 staffs and coordinates the updated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \", along with the\\nsupporting \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \". A-3 is the signature approval authority for changes\\nwithin the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \", and verifies that the updated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" and current \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" match so\\nthere are no unintended disconnects when tracking the program's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nfunds.\"), mdx(\"h1\", null, \"Program Transfer\"), mdx(\"p\", null, \"If a program transfers from one Detachment to another (or from a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" to\\nA-3), the losing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" ensures his team completes applicable program\\ntransfer checklist items. The Detachment will prepare a memorandum for\\nrecord (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum for Record\"\n }, \"MFR\"), \") and submit it to the A-3 Director of Operations. Both the\\ntransfer checklist and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum for Record\"\n }, \"MFR\"), \" are available on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SharePoint.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#initial-tasking-order","title":"Initial Tasking Order"},{"url":"#tasking-order-update","title":"Tasking Order Update"},{"url":"#program-transfer","title":"Program Transfer"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-1-1-tasking.md"},"frontmatter":{"metaTitle":"Tasking","metaDescription":"Tasking"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"20bd56bd-5943-5a4b-922f-f71eb7ca8a2b"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/6-1-2-team-standup/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-1-2-team-standup","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"ad9c781a-9549-5d22-b383-547869f5fed7","title":"Team Stand-up","slug":"/OT&E_Guide/6-1-2-team-standup"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Team Stand-up\",\n \"metaTitle\": \"Team Stand-up\",\n \"metaDescription\": \"Team Stand-up\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"The composition of the test team depends on the scope of the test. The\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E tasking order shows the formal organization of the test team. In\\nsome cases, test teams that are not co-located with a Detachment may\\nneed to establish an operating location at the test location. When\\nconducting small tests that are short in duration, teams may consist\\nentirely of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" personnel; however, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" may augment its test teams\\nwith \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" personnel when tests are more complex and take longer to\\ncomplete. The lead \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" (if being supported by more than one \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \")\\nidentifies a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \". The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"'s concurrence, may make\\nadjustments to personnel and where they are assigned. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" should\\nconsider obtaining expertise from the mission area where the test is\\nconducted. These selected personnel should have experience and knowledge\\nof local procedures and policies, as well as executing test budgets.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \": Your assignment to a test team does not mean you are dedicated\\nto that team exclusively. As a test team member, you must be agile and\\nsupport different teams for specific tasks.\"), mdx(\"h1\", null, \"Test Team Selection\"), mdx(\"p\", null, \"It is important to form the test team early to ensure there is time to\\nindoctrinate and train personnel to accomplish tasks required to\\ncomplete \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. The two types of test team positions are permanent\\npositions on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s unit manning document, and temporary positions\\nfilled by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" augmentees. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" positions are filled via the\\nvulnerable to move list (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vulnerable to Move List\"\n }, \"VML\"), \") process. A-1W publishes \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vulnerable to Move List\"\n }, \"VML\"), \" timelines.\\nSelected test team members should have skill levels that are\\nrepresentative of personnel expected to maintain and operate the system.\\nThe validity of evaluating the test depends on using representative\\noperators from using commands and avoiding highly qualified or specially\\ntrained personnel. Ideally, those involved in test execution should have\\noperational experience in the system to be tested, or in a similar\\nsystem; although, based on manpower availability this may not always be\\npossible. Consider the following when building test teams:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Team Positions. The preferred approach is for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" personnel\\nto occupy key management positions on a test team. Key positions\\ninclude the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and deputies for operations (sometime known as the\\nassistant \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"), analysis, logistics, cybersecurity, and Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \"\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" staff. However, if the most qualified individual for a test team\\nposition, to include TDs, is a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" tester, then it is acceptable\\nto use that person (with discretion of the Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \") and\\nconcurrence of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Team Requisition. For \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-authorized test team slots, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"\\nmission support officers submit requisitions for personnel, along\\nwith selection criteria, through the applicable Director or\\nDetachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" to A-1W as soon as possible, but not later than the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vulnerable to Move List\"\n }, \"VML\"), \" timelines provided by A-1W. Usually, the test team requests\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" augmentees in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \", which they coordinate with the\\napplicable \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Multiservice Operational Test and Evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \") test team\\nstructure. Use the multiservice test team structure described in the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \" regarding MOT&Es found on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s SharePoint.\"))), mdx(\"h1\", null, \"Administrative Support Requirements\"), mdx(\"p\", null, \"The test team must document administrative requirements in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \". If\\nthe test includes high- or special-interest events, they should request\\nadministrative support (including protocol) to assist with needs of\\nvisitors. If the test team is co-located with an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Detachment, the\\nDetachment should request administrative support when it coordinates the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" with the Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \". If the test team is not co-located with an\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Detachment, or the Detachment is unable to provide the\\nadministrative support required, the test team should include a\\nrequirement in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" that participating MAJCOMs provide administrative\\nsupport.\"), mdx(\"h1\", null, \"Major Command-Assigned Test Team Members\"), mdx(\"p\", null, \"MAJCOMs retain command authority over their personnel and may establish\\na formal agreement for rating, retaining, or replacing them on a\\nspecific test team. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" collaborate in developing a\\npersonnel memorandum of agreement (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \"). A-8P oversees the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \" process\\nand staffs it for signature at the appropriate level. A-1W ensures\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" signs the agreement at the command level commensurate with the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" organization providing personnel. Define administrative and\\noperational control over test team members early; preferably, in the\\nagreement. Address how \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" test team personnel will be rated (i.e.,\\nperformance reports, appraisals) when you formalize host/tenant and\\nother test team administrative procedures. Ensure test team members and\\ntheir parent command understand clearly who has authority for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \"\\nmembers' officer performance reports and enlisted performance reports\\n(Ref: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 36-2406, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Officer and Enlisted Evaluation Systems\"), \", 30 Nov\\n15). Coordinate deviations from these guidelines through A-1W for\\nAFOTE/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vice Commander OR Capability Viewpoint\"\n }, \"CV\"), \" approval. In addition to documenting agreed-upon rationale for\\nretaining or replacing test team personnel, stipulate that once they are\\ntrained, test team personnel cannot be replaced for the duration of the\\ntest (to include reporting). Address potential absences for activities\\nsuch as schools, symposiums, and career enhancement training. While it\\nis preferable to retain test team personnel, there are occasionally\\nreasons that justify replacing a test team member.\"), mdx(\"h1\", null, \"Test Program Applications\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses a suite of web-based applications to monitor, assess, plan\\nand execute test operations. A-3 and A-5/8 post current policy,\\nprocedures and templates for test operations.\"), mdx(\"p\", null, \"The managing Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" or A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" is responsible for maintaining\\ncurrent, complete, and accurate program information and documents\\n(externally and internally generated) in test program management (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \").\\nThe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" will update test documentation continually by ensuring\\ncurrent documents are posted within 1 work day of receipt for external\\ndocuments and 1 work day of signature for internally generated\\ndocuments. A-3 PMs manage programs prior to formal involvement and\\nprograms transferred back to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" in lieu of closeout. TDs manage programs\\nafter formal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" involvement. Even after a program is assigned to a\\nDetachment, A-3 PMs upload command staff-approved documentation and help\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" maintain information in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \" by regularly reviewing data and\\nsupporting TDs by making necessary corrections. Every 30 days the\\nmanaging \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" must certify information and documents on the\\nprogram's test program management page are current, complete, and\\naccurate. Table 6-1 contains a possible list of documents maintained on\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \".\"), mdx(\"p\", null, \"Table 6\\u20111. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SharePoint \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \" Baseline Documentation\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Document Folder\"), mdx(\"th\", null, \"Typical Documents\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Acquisition Documentation\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"ADM\")), mdx(\"li\", null, mdx(\"p\", null, \"Acquisition Program Baseline/Acquisition Strategy\")), mdx(\"li\", null, mdx(\"p\", null, \"AoA\")), mdx(\"li\", null, mdx(\"p\", null, \"System Requirements/ Engineering Document\")), mdx(\"li\", null, mdx(\"p\", null, \"SOC/Statement of Work (SOW)\")), mdx(\"li\", null, mdx(\"p\", null, \"SCG\")), mdx(\"li\", null, mdx(\"p\", null, \"Client Requirements Document\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Capability Requirements Documents\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"ICD/IS\")), mdx(\"li\", null, mdx(\"p\", null, \"ICD/CDD/IS\")), mdx(\"li\", null, mdx(\"p\", null, \"CDD, including all capstone requirements\")), mdx(\"li\", null, mdx(\"p\", null, \"Operations Requirement Document, if still used by program\"))))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"CONOPS and Threat Documents\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"CONOPS\")), mdx(\"li\", null, mdx(\"p\", null, \"STAR/VOLT\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Orders and Resources\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Orders (initial/updated TO)\")), mdx(\"li\", null, mdx(\"p\", null, \"RRB Slide\")), mdx(\"li\", null, mdx(\"p\", null, \"TRP\")), mdx(\"li\", null, mdx(\"p\", null, \"Involvement Letter\")), mdx(\"li\", null, mdx(\"p\", null, \"Non Involvement Letter\")), mdx(\"li\", null, mdx(\"p\", null, \"Closeout Memo\"))))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Initial Test Design\"), mdx(\"td\", null, \"ITD Briefing, including embedded information\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Test Concept\"), mdx(\"td\", null, \"TC Briefing, including embedded information\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Technical Reviews\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"TRD\")), mdx(\"li\", null, mdx(\"p\", null, \"Technical Review MFRs\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Test Plans and Plan briefings\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"AFOTEC Test Plan/Plan Briefing\")), mdx(\"li\", null, mdx(\"p\", null, \"Identified Standards Letter\")), mdx(\"li\", null, mdx(\"p\", null, \"DMAP\")), mdx(\"li\", null, mdx(\"p\", null, \"Test Capability VV&A Plan\")), mdx(\"li\", null, mdx(\"p\", null, \"Program Introduction Document (PID)/Statement of Capabilities (SOC)\"))))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Operational Test Certification\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Certification of System Readiness Letter\")), mdx(\"li\", null, mdx(\"p\", null, \"Operational Test Acknowledgement Letter\")), mdx(\"li\", null, mdx(\"p\", null, \"TRR Briefing\")), mdx(\"li\", null, mdx(\"p\", null, \"Stop Test/Decertification Letter\")), mdx(\"li\", null, mdx(\"p\", null, \"Recertification Message/ Letter\")), mdx(\"li\", null, mdx(\"p\", null, \"Readiness-to-Test Briefing\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Test Reports and Report Briefings\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"AFOTEC Test Report/Briefing\")), mdx(\"li\", null, mdx(\"p\", null, \"Quick Look Briefing\")), mdx(\"li\", null, mdx(\"p\", null, \"Category 1 deficiency reports (DR)\")), mdx(\"li\", null, mdx(\"p\", null, \"Multimedia/Graphic files\")), mdx(\"li\", null, mdx(\"p\", null, \"Significant Event Report\")), mdx(\"li\", null, mdx(\"p\", null, \"Status Report\")), mdx(\"li\", null, mdx(\"p\", null, \"ISR\")), mdx(\"li\", null, mdx(\"p\", null, \"Test Capability Accreditation Report\")), mdx(\"li\", null, mdx(\"p\", null, \"Situation Reports\"))))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"TEMP\"), mdx(\"td\", null, \"TEMP\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Agreements/Charters\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"ITT Charter\")), mdx(\"li\", null, mdx(\"p\", null, \"MOA/MOU\"))))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Correspondence/Email\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Internal AFOTEC and external agency correspondence\")), mdx(\"li\", null, mdx(\"p\", null, \"Meeting Minutes\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Trip Reports\"), mdx(\"td\", null, \"Trip reports specific to the test program\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Cybersecurity\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"RMF implementation package or ATO\")), mdx(\"li\", null, mdx(\"p\", null, \"Cybersecurity test report from designated cybersecurity test organization (Blue/Red Team)\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Safety\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"ESOH document\")), mdx(\"li\", null, mdx(\"p\", null, \"ESOHCB Memo and HSP\")), mdx(\"li\", null, mdx(\"p\", null, \"Safety Reports/Reviews\"))))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"em\", null, \"Note\"), \": These typical documents are program dependent--some might not apply or be needed for your particular program.\"), mdx(\"td\", null)))), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \" is available on both the Non-Secure Internet Protocol Router Network\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Secure Internet Protocol Router Network\"\n }, \"NIPRNet\"), \") and Secure Internet Protocol Router Network (SIPRNet).\\nNormally, programs have a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Secure Internet Protocol Router Network\"\n }, \"NIPRNet\"), \" Test Program Management page. If a\\nprogram has classified documents, A-3 in coordination with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", will\\ncreate a SIPRNet page for it. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" maintains Top Secret and Special\\nAccess Required (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \") documents on appropriate information systems\\noutside of Test Program Management (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \").\"), mdx(\"h1\", null, \"Air Force Manual 63-119 Responsibilities\"), mdx(\"p\", null, \"Air Force Manual (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \") 63\\u2011119, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Certification of System Readiness for\\nDedicated Operational Testing\"), \", presents a structured mechanism or\\n\\\"process\\\" to identify problems and risks associated with transitioning\\nfrom \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"&E to the final phase of dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E.\"), mdx(\"p\", null, \"The certification process helps acquisition managers at all levels\\nidentify risks, reach negotiated agreements on issues, and render an\\naccurate assessment of a system's readiness to begin the final phase of\\ndedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will pursue all possible initiatives to enable\\ndelivery of lethal combat capability at the speed of relevance. To\\nimplement this, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will seek early \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" credit to eliminate\\nduplication of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"'s previous testing, reduce dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E, and support\\ndelivery of combat capability as early as possible. Consequently, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nno longer relies on the certification process at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Readiness Review\"\n }, \"OTRR\"), \".\"), mdx(\"p\", null, \"If the program office or the program execution officer (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \") determines\\nan \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Readiness Review\"\n }, \"OTRR\"), \" is required, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will support the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \"'s certification review\\nby presenting an operational test review (OTR) that covers status of\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E data collection efforts to date, significant findings we have\\nidentified, remaining requirements to complete \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E, and risks to\\ncompleting \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E.\"), mdx(\"p\", null, \"If the program office or the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \" requires certification, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will\\ntailor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \" 63-119 templates to meet specific project needs as agreed\\nto by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" communities. Then, we will assess templates using\\nobjective measurements to the maximum extent to determine whether we met\\nexit criteria.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools\"), \": Periodic O-6 level reviews with stakeholders.\"), mdx(\"h2\", null, \"Air Force Manual 63-119 Flexibility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \" 63-119 templates are flexible and apply to any acquisition\\nprogram. Consider template attachments because some require \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \" action,\\nspecifically. Maintain continuous dialogue with the program office and\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" community to comply with template requirements. Scrutinize\\ndeviations from a true operational or production-representative article\\nfor potential limitations to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. Tailor the templates or add new ones\\nto achieve objectives of the certification process.\"), mdx(\"h1\", null, \"Program-Related Document Reviews\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" helps prepare key requirements and acquisition documents to\\nincorporate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" interests into the acquisition process. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s\\nparticipation varies depending on the situation. A-3 manages the product\\nreview process.\"), mdx(\"h1\", null, \"Technical Reviews\"), mdx(\"p\", null, \"The test team conducts technical reviews for every test activity. Who\\nconducts the technical review will depend upon the level of test and\\nexpected reporting. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" conducts the review for test activities expected\\nto answer effectiveness and/or suitability. The Detachment technical\\nadvisor conducts the review for all other test activities. The test team\\nmay request a technical review by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" for any level of test activity.\"), mdx(\"h1\", null, \"Technical Advisors Board\"), mdx(\"p\", null, \"Technical advisors (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Advisor OR Test Area\"\n }, \"TA\"), \") make up the TAB, under the leadership of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \"\\nTechnical Advisor (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \"). The TAB's primary role is to advise\\nDirectors, Detachment Commanders, and Detachment personnel on processes\\nand/or non-standard approaches for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities, and applying \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \"\\nprinciples to meet the Commander's intent and vision.\"), mdx(\"h1\", null, \"Technical and Scientific Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" government personnel are the first choice for technical support,\\nfollowed by external government personnel, and then lastly, contracted\\nsupport personnel. If none of these are available, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" (A1, A2/9,\\nA3, A4/7, A5/8) will work with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" to identify technical and\\nscientific contract support needs to perform specific tasks when they\\nbegin formulating the test strategy or initial test design. Technical\\nand scientific support should be thought of broadly and include\\ncontractor services, leases, and any operational or logistical support\\nrequired.\"), mdx(\"h1\", null, \"Technical and Scientific Support\"), mdx(\"p\", null, \"Detachment test teams should explore the availability of technical\\nsupport from A-2/9, A-5/8, Detachment TAs, and other external military\\nand government agencies when developing the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \". A-2/9 personnel have a\\nbroad ability to provide technical and scientific support in areas of\\neffectiveness evaluation, suitability evaluation, human factors,\\nintelligence, and test capability verification, validation, and\\naccreditation. In addition, they ensure technically feasible test plans,\\nanalytically sound measures and methods, and supportable conclusions for\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. A-2/9 personnel ensure \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" addresses human factors and system\\ntraining issues adequately, and they provide technical expertise in\\nobservational methods and questionnaire development and administration.\\nA-2N and Detachment (if assigned) Intel personnel must ensure the test\\nprogram threat list and the test threat environment are addressed\\nadequately and that appropriate intelligence is used to support planning\\nand developing the threat portions of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s test documents. Finally,\\nthey provide special security office support.\"), mdx(\"p\", null, \"A-5R identifies, advocates, and develops test capabilities (e.g., open\\nair range, ground test facilities, instrumentation, targets and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \") to\\nsupport test teams. A-5R provides technical assistance for space, air,\\nand ground systems.\"), mdx(\"h1\", null, \"Lessons Learned\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" actively seeks to improve our processes and products. Our Lessons\\nLearned (LL) program is one method through which we demonstrate our\\ncommitment to being a learning organization.\", mdx(\"sup\", {\n parentName: \"p\",\n \"id\": \"fnref-1\"\n }, mdx(\"a\", {\n parentName: \"sup\",\n \"href\": \"#fn-1\",\n \"className\": \"footnote-ref\"\n }, \"1\")), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" defines LLs as,\\n\\\"\", mdx(\"em\", {\n parentName: \"p\"\n }, \"A documented event or experience that provides test team insight and\\nmission improvement\"), \".\\\" The goal of LL is to foster a culture in which we\\nidentify those experiences and learn from them, both individually and\\ncollectively. We learn by changing our business practices, which\\nincludes updating policies, such as the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Guide, or updating training\\ncurriculum on an ongoing basis. \\\"Mission improvement\\\" is embedded in the\\ndefinition of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" LL because it emphasizes our intent to transform\\nthe organization continuously. Refer to the \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/lessons_learned_guide/\"\n }, \"Lessons Learned\\nGuide\"), \".\"), mdx(\"h1\", null, \"Information Releases\"), mdx(\"p\", null, \"Forward all requests for information through the appropriate point of\\ncontact (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \"), as outlined in Table 6-2. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" releases the\\ninformation after reviewing its distribution and release markings and\\ncoordinating it through ACAP for approval.\"), mdx(\"p\", null, \"Table 6\\u20112. POCs for Information Requests\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Type of Request\"), mdx(\"th\", null, \"POC\"), mdx(\"th\", null, \"*Coordination\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"DoD Agency\"), mdx(\"td\", null, \"HO\"), mdx(\"td\", null, \"A-3\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Agency not authorized by distribution statement\"), mdx(\"td\", null, \"HO\"), mdx(\"td\", null, \"FOIA Officer/A-3\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"FOIA\"), mdx(\"td\", null, \"FOIA Office (A\\u20116)\"), mdx(\"td\", null, \"HO/LC/PA/A\\u20117K/IP/OPSEC/A-3\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Media Release\"), mdx(\"td\", null, \"PA\"), mdx(\"td\", null, \"FOIA Office/ HO/LC/IP/OPSEC/A-3\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Foreign Disclosure\"), mdx(\"td\", null, \"A\\u20112/9\"), mdx(\"td\", null, \"FOIA Office/ HO/LC/PA/IP/OPSEC/A\\u20113 AFOTEC FDO\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*Coordination will vary depending on nature of information requested\"), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"h1\", null, \"Determining the Need for Contractor Services and Leases\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" planners should make every effort to use in-house support before\\nturning to contractor services. With limited funding available, closely\\nmanaging \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" contractor activity is critical. A-5/8 coordinates all\\nnew contractor efforts. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" must formally review proposed contractor\\nsupport that is \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-funded. We will determine the best approach to\\nobtain funding for externally funded contractors on a case-by-case\\nbasis. Find details in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/strat_planning_programming_guide/\"\n }, \"Strategy, Planning, and Programming\\nProcess (SP3)\\nGuide\"), \".\\nContact A-5/8 for assistance.\"), mdx(\"p\", null, \"A-5/8 will work with you to identify resource options. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" planners\\nshould have a good idea of the technical services required before\\nworking with A-4/7K to prepare the contract task order performance work\\nstatement (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Work Statement\"\n }, \"PWS\"), \"). \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \": Only the procuring contracting officer (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Procuring Contracting Officer\"\n }, \"PCO\"), \")\\ncan direct the contractor to perform services.\"), mdx(\"h1\", null, \"Contracts\"), mdx(\"p\", null, \"A-7K (contracting office) administers long-term technical service\\ncontracts with different companies that support \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s mission. These\\ncontracts are indefinite delivery/indefinite quantity (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Identification\"\n }, \"ID\"), \"/IQ) contracts\\nthat allow issuance of cost plus fixed fee or firm, fixed price task\\norders. A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Procuring Contracting Officer\"\n }, \"PCO\"), \" in A-7K manages these contracts. A contracting officer's\\nrepresentative (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer’s Representative\"\n }, \"COR\"), \") acts on behalf of the contracting officer to\\nmonitor contractor performance as outlined in a letter provided by A-7K,\\nwhich assigns the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer’s Representative\"\n }, \"COR\"), \" for a specific contracting task order. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer’s Representative\"\n }, \"COR\"), \"\\nresides where the work is being performed (Director/Detachment) and\\nshould clearly understand the tasks and associated technical work and\\nproducts the contractor is producing.\"), mdx(\"h1\", null, \"Selecting a Contractor\"), mdx(\"p\", null, \"Test teams that require technical services from existing contracts\\nprepare a contract task order \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Work Statement\"\n }, \"PWS\"), \" so contractors can prepare technical\\nand cost proposals, which the technical team evaluates. Requirements are\\ndefined as explicit work to be done and are independent of individual\\ncontractors or contractor personnel. The technical team evaluates\\ntechnical and cost approaches to determine which contractor offers the\\nbest value to the government. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Procuring Contracting Officer\"\n }, \"PCO\"), \" reviews these results and upon\\naccepting a contractor's proposal, A-7K awards a contract task order to\\nthe selected contractor. Fairness and open competition are critical to\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" getting the best return on its investment. There are rare\\nexceptions to the \\\"fair opportunity\\\" clause of the contract, which you\\ncan discuss with A-7K. The Air Force has established goals for expanding\\nsmall business opportunities and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is committed to supporting those\\ngoals. Test teams need to work closely with PCOs and contract\\nspecialists in A-7K for contractual support.\"), mdx(\"h1\", null, \"Contract Task Order\"), mdx(\"p\", null, \"The contract task order \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Work Statement\"\n }, \"PWS\"), \" describes the scope, technical requirements,\\ndeliverables, and period of performance. Provide the contract task order\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Work Statement\"\n }, \"PWS\"), \" to the contract specialist in electronic format. The contractor\\ncannot begin work on a contract task order until A-7K issues it to the\\ncontractor. Depending on the contract task order's complexity, the\\nentire review and award process may take up to 4 weeks after A-7K\\nreceives it. Consider overall contractor needs early in the test\\nprogram, just as for other resource requirements.\"), mdx(\"h1\", null, \"Contract Task Order Management\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer’s Representative\"\n }, \"COR\"), \" is not authorized to change any element of the contract task\\norder, but they process required changes through the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Procuring Contracting Officer\"\n }, \"PCO\"), \".\\nResponsibilities of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer’s Representative\"\n }, \"COR\"), \" are described in their assignment letter from\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Procuring Contracting Officer\"\n }, \"PCO\"), \". \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" provides \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer’s Representative\"\n }, \"COR\"), \" training periodically and designated\\npersonnel must attend that training prior to being nominated or\\nassigned.\"), mdx(\"h1\", null, \"Release of Intelligence Information to Contractors\"), mdx(\"p\", null, \"Intelligence information is restricted from release to government\\ncontractors. Contact A-2/9 and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s contracting officer for guidance\\nbefore releasing intelligence to contractors. These requirements pertain\\nto collateral and sensitive compartmented information (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Sensitive Compartmented Information\"\n }, \"SCI\"), \"). The purpose\\nof these requirements is to ensure dissemination of intelligence\\ninformation is controlled properly and does not give a competitive edge\\nto a particular contractor. Classified information remains the property\\nof the U.S. government and the program office must return it to\\ngovernment control upon a program's completion. DD Form 254, \\\"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \"\\nContract Security Classification Specification,\\\" for each contract\\nspecifies whether the release of intelligence is authorized for that\\ncontract. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer’s Representative\"\n }, \"COR\"), \" requests release of intelligence on behalf of the\\ncontractor, and A-2/9 ensures the contractor receives the intelligence\\ndata necessary to meet their obligations.\"), mdx(\"h1\", null, \"Real Property, Facilities, Furniture, Communications and Off Base Leases\"), mdx(\"p\", null, \"Plan facility, furniture, and real-property acquisitions early. In\\ngeneral, submit small facility projects, such as room renovations and\\nfurniture procurements in memorandum form with an explanatory \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" Form\\n332, \\\"Base Civil Engineer Work Request\\\" to the Engineering, Facilities\\nand Logistics Division (A-4F) as part of the budget call for the\\nfollowing fiscal year (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fiscal Year\"\n }, \"FY\"), \"). Submit an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" Form 332 to A-4F at least 3\\nyears prior to the projected need date for large projects such as new\\nbuildings, building additions, extensive renovations and off-base leased\\nfacilities space or land. Consider the following:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Document new requirements that require office space, land, or\\nspecial use areas on Part 1 of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" Form 332, along with a brief\\njustification, and submit it to A-4F as soon as the requirement is\\nknown.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Document repair and maintenance of existing facilities on Part 1 of\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" Form 332 and submit it to A-4F. Items that require submission\\ninclude new carpeting, painting, wall coverings, modification to a\\nbuilding's mechanical or electrical systems, or installation of\\nequipment that will be connected to a building's systems or\\nutilities permanently.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Submit furniture and facility equipment requirements to A-4F. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nwill meet all other requirements from its existing inventory, UNICOR\\n(Prison Industry), Government Services Administration (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Services Administration\"\n }, \"GSA\"), \"),\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Services Administration\"\n }, \"GSA\"), \"-approved vendors, or the open market, in that order.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Submit \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" eCSRD (Electronic Communication Systems Requirements\\nDocument) to A-6 to identify communication requirements. Test\\nrequirements usually include SIPRNet access, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Secure Internet Protocol Router Network\"\n }, \"NIPRNet\"), \" access, secure\\nterminal equipment access and/or home-station reach-back\\nrequirements. A-6 will coordinate with test locations to ensure\\nthese capabilities exist and are coordinated in time for test\\nevents. Elevate communication requirements to the Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"\\nand/or the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" command section, if required.\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#test-team-selection","title":"Test Team Selection"},{"url":"#administrative-support-requirements","title":"Administrative Support Requirements"},{"url":"#major-command-assigned-test-team-members","title":"Major Command-Assigned Test Team Members"},{"url":"#test-program-applications","title":"Test Program Applications"},{"url":"#air-force-manual-63-119-responsibilities","title":"Air Force Manual 63-119 Responsibilities","items":[{"url":"#air-force-manual-63-119-flexibility","title":"Air Force Manual 63-119 Flexibility"}]},{"url":"#program-related-document-reviews","title":"Program-Related Document Reviews"},{"url":"#technical-reviews","title":"Technical Reviews"},{"url":"#technical-advisors-board","title":"Technical Advisors Board"},{"url":"#technical-and-scientific-support","title":"Technical and Scientific Support"},{"url":"#technical-and-scientific-support-1","title":"Technical and Scientific Support"},{"url":"#lessons-learned","title":"Lessons Learned"},{"url":"#information-releases","title":"Information Releases"},{"url":"#determining-the-need-for-contractor-services-and-leases","title":"Determining the Need for Contractor Services and Leases"},{"url":"#contracts","title":"Contracts"},{"url":"#selecting-a-contractor","title":"Selecting a Contractor"},{"url":"#contract-task-order","title":"Contract Task Order"},{"url":"#contract-task-order-management","title":"Contract Task Order Management"},{"url":"#release-of-intelligence-information-to-contractors","title":"Release of Intelligence Information to Contractors"},{"url":"#real-property-facilities-furniture-communications-and-off-base-leases","title":"Real Property, Facilities, Furniture, Communications and Off Base Leases"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-1-2-team-standup.md"},"frontmatter":{"metaTitle":"Team Stand-up","metaDescription":"Team Stand-up"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"ad9c781a-9549-5d22-b383-547869f5fed7"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-1-2-team-standup","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"ad9c781a-9549-5d22-b383-547869f5fed7","title":"Team Stand-up","slug":"/OT&E_Guide/6-1-2-team-standup"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Team Stand-up\",\n \"metaTitle\": \"Team Stand-up\",\n \"metaDescription\": \"Team Stand-up\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"The composition of the test team depends on the scope of the test. The\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E tasking order shows the formal organization of the test team. In\\nsome cases, test teams that are not co-located with a Detachment may\\nneed to establish an operating location at the test location. When\\nconducting small tests that are short in duration, teams may consist\\nentirely of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" personnel; however, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" may augment its test teams\\nwith \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" personnel when tests are more complex and take longer to\\ncomplete. The lead \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" (if being supported by more than one \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \")\\nidentifies a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \". The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"'s concurrence, may make\\nadjustments to personnel and where they are assigned. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" should\\nconsider obtaining expertise from the mission area where the test is\\nconducted. These selected personnel should have experience and knowledge\\nof local procedures and policies, as well as executing test budgets.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \": Your assignment to a test team does not mean you are dedicated\\nto that team exclusively. As a test team member, you must be agile and\\nsupport different teams for specific tasks.\"), mdx(\"h1\", null, \"Test Team Selection\"), mdx(\"p\", null, \"It is important to form the test team early to ensure there is time to\\nindoctrinate and train personnel to accomplish tasks required to\\ncomplete \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. The two types of test team positions are permanent\\npositions on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s unit manning document, and temporary positions\\nfilled by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" augmentees. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" positions are filled via the\\nvulnerable to move list (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vulnerable to Move List\"\n }, \"VML\"), \") process. A-1W publishes \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vulnerable to Move List\"\n }, \"VML\"), \" timelines.\\nSelected test team members should have skill levels that are\\nrepresentative of personnel expected to maintain and operate the system.\\nThe validity of evaluating the test depends on using representative\\noperators from using commands and avoiding highly qualified or specially\\ntrained personnel. Ideally, those involved in test execution should have\\noperational experience in the system to be tested, or in a similar\\nsystem; although, based on manpower availability this may not always be\\npossible. Consider the following when building test teams:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Team Positions. The preferred approach is for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" personnel\\nto occupy key management positions on a test team. Key positions\\ninclude the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and deputies for operations (sometime known as the\\nassistant \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"), analysis, logistics, cybersecurity, and Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \"\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" staff. However, if the most qualified individual for a test team\\nposition, to include TDs, is a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" tester, then it is acceptable\\nto use that person (with discretion of the Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \") and\\nconcurrence of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Team Requisition. For \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-authorized test team slots, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"\\nmission support officers submit requisitions for personnel, along\\nwith selection criteria, through the applicable Director or\\nDetachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" to A-1W as soon as possible, but not later than the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vulnerable to Move List\"\n }, \"VML\"), \" timelines provided by A-1W. Usually, the test team requests\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" augmentees in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \", which they coordinate with the\\napplicable \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Multiservice Operational Test and Evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \") test team\\nstructure. Use the multiservice test team structure described in the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \" regarding MOT&Es found on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s SharePoint.\"))), mdx(\"h1\", null, \"Administrative Support Requirements\"), mdx(\"p\", null, \"The test team must document administrative requirements in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \". If\\nthe test includes high- or special-interest events, they should request\\nadministrative support (including protocol) to assist with needs of\\nvisitors. If the test team is co-located with an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Detachment, the\\nDetachment should request administrative support when it coordinates the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" with the Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \". If the test team is not co-located with an\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Detachment, or the Detachment is unable to provide the\\nadministrative support required, the test team should include a\\nrequirement in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" that participating MAJCOMs provide administrative\\nsupport.\"), mdx(\"h1\", null, \"Major Command-Assigned Test Team Members\"), mdx(\"p\", null, \"MAJCOMs retain command authority over their personnel and may establish\\na formal agreement for rating, retaining, or replacing them on a\\nspecific test team. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" collaborate in developing a\\npersonnel memorandum of agreement (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \"). A-8P oversees the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \" process\\nand staffs it for signature at the appropriate level. A-1W ensures\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" signs the agreement at the command level commensurate with the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" organization providing personnel. Define administrative and\\noperational control over test team members early; preferably, in the\\nagreement. Address how \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" test team personnel will be rated (i.e.,\\nperformance reports, appraisals) when you formalize host/tenant and\\nother test team administrative procedures. Ensure test team members and\\ntheir parent command understand clearly who has authority for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \"\\nmembers' officer performance reports and enlisted performance reports\\n(Ref: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 36-2406, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Officer and Enlisted Evaluation Systems\"), \", 30 Nov\\n15). Coordinate deviations from these guidelines through A-1W for\\nAFOTE/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vice Commander OR Capability Viewpoint\"\n }, \"CV\"), \" approval. In addition to documenting agreed-upon rationale for\\nretaining or replacing test team personnel, stipulate that once they are\\ntrained, test team personnel cannot be replaced for the duration of the\\ntest (to include reporting). Address potential absences for activities\\nsuch as schools, symposiums, and career enhancement training. While it\\nis preferable to retain test team personnel, there are occasionally\\nreasons that justify replacing a test team member.\"), mdx(\"h1\", null, \"Test Program Applications\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses a suite of web-based applications to monitor, assess, plan\\nand execute test operations. A-3 and A-5/8 post current policy,\\nprocedures and templates for test operations.\"), mdx(\"p\", null, \"The managing Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" or A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" is responsible for maintaining\\ncurrent, complete, and accurate program information and documents\\n(externally and internally generated) in test program management (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \").\\nThe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" will update test documentation continually by ensuring\\ncurrent documents are posted within 1 work day of receipt for external\\ndocuments and 1 work day of signature for internally generated\\ndocuments. A-3 PMs manage programs prior to formal involvement and\\nprograms transferred back to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" in lieu of closeout. TDs manage programs\\nafter formal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" involvement. Even after a program is assigned to a\\nDetachment, A-3 PMs upload command staff-approved documentation and help\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" maintain information in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \" by regularly reviewing data and\\nsupporting TDs by making necessary corrections. Every 30 days the\\nmanaging \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" must certify information and documents on the\\nprogram's test program management page are current, complete, and\\naccurate. Table 6-1 contains a possible list of documents maintained on\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \".\"), mdx(\"p\", null, \"Table 6\\u20111. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SharePoint \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \" Baseline Documentation\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Document Folder\"), mdx(\"th\", null, \"Typical Documents\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Acquisition Documentation\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"ADM\")), mdx(\"li\", null, mdx(\"p\", null, \"Acquisition Program Baseline/Acquisition Strategy\")), mdx(\"li\", null, mdx(\"p\", null, \"AoA\")), mdx(\"li\", null, mdx(\"p\", null, \"System Requirements/ Engineering Document\")), mdx(\"li\", null, mdx(\"p\", null, \"SOC/Statement of Work (SOW)\")), mdx(\"li\", null, mdx(\"p\", null, \"SCG\")), mdx(\"li\", null, mdx(\"p\", null, \"Client Requirements Document\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Capability Requirements Documents\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"ICD/IS\")), mdx(\"li\", null, mdx(\"p\", null, \"ICD/CDD/IS\")), mdx(\"li\", null, mdx(\"p\", null, \"CDD, including all capstone requirements\")), mdx(\"li\", null, mdx(\"p\", null, \"Operations Requirement Document, if still used by program\"))))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"CONOPS and Threat Documents\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"CONOPS\")), mdx(\"li\", null, mdx(\"p\", null, \"STAR/VOLT\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Orders and Resources\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Orders (initial/updated TO)\")), mdx(\"li\", null, mdx(\"p\", null, \"RRB Slide\")), mdx(\"li\", null, mdx(\"p\", null, \"TRP\")), mdx(\"li\", null, mdx(\"p\", null, \"Involvement Letter\")), mdx(\"li\", null, mdx(\"p\", null, \"Non Involvement Letter\")), mdx(\"li\", null, mdx(\"p\", null, \"Closeout Memo\"))))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Initial Test Design\"), mdx(\"td\", null, \"ITD Briefing, including embedded information\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Test Concept\"), mdx(\"td\", null, \"TC Briefing, including embedded information\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Technical Reviews\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"TRD\")), mdx(\"li\", null, mdx(\"p\", null, \"Technical Review MFRs\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Test Plans and Plan briefings\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"AFOTEC Test Plan/Plan Briefing\")), mdx(\"li\", null, mdx(\"p\", null, \"Identified Standards Letter\")), mdx(\"li\", null, mdx(\"p\", null, \"DMAP\")), mdx(\"li\", null, mdx(\"p\", null, \"Test Capability VV&A Plan\")), mdx(\"li\", null, mdx(\"p\", null, \"Program Introduction Document (PID)/Statement of Capabilities (SOC)\"))))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Operational Test Certification\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Certification of System Readiness Letter\")), mdx(\"li\", null, mdx(\"p\", null, \"Operational Test Acknowledgement Letter\")), mdx(\"li\", null, mdx(\"p\", null, \"TRR Briefing\")), mdx(\"li\", null, mdx(\"p\", null, \"Stop Test/Decertification Letter\")), mdx(\"li\", null, mdx(\"p\", null, \"Recertification Message/ Letter\")), mdx(\"li\", null, mdx(\"p\", null, \"Readiness-to-Test Briefing\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Test Reports and Report Briefings\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"AFOTEC Test Report/Briefing\")), mdx(\"li\", null, mdx(\"p\", null, \"Quick Look Briefing\")), mdx(\"li\", null, mdx(\"p\", null, \"Category 1 deficiency reports (DR)\")), mdx(\"li\", null, mdx(\"p\", null, \"Multimedia/Graphic files\")), mdx(\"li\", null, mdx(\"p\", null, \"Significant Event Report\")), mdx(\"li\", null, mdx(\"p\", null, \"Status Report\")), mdx(\"li\", null, mdx(\"p\", null, \"ISR\")), mdx(\"li\", null, mdx(\"p\", null, \"Test Capability Accreditation Report\")), mdx(\"li\", null, mdx(\"p\", null, \"Situation Reports\"))))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"TEMP\"), mdx(\"td\", null, \"TEMP\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Agreements/Charters\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"ITT Charter\")), mdx(\"li\", null, mdx(\"p\", null, \"MOA/MOU\"))))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Correspondence/Email\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Internal AFOTEC and external agency correspondence\")), mdx(\"li\", null, mdx(\"p\", null, \"Meeting Minutes\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Trip Reports\"), mdx(\"td\", null, \"Trip reports specific to the test program\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Cybersecurity\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"RMF implementation package or ATO\")), mdx(\"li\", null, mdx(\"p\", null, \"Cybersecurity test report from designated cybersecurity test organization (Blue/Red Team)\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Safety\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"ESOH document\")), mdx(\"li\", null, mdx(\"p\", null, \"ESOHCB Memo and HSP\")), mdx(\"li\", null, mdx(\"p\", null, \"Safety Reports/Reviews\"))))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"em\", null, \"Note\"), \": These typical documents are program dependent--some might not apply or be needed for your particular program.\"), mdx(\"td\", null)))), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \" is available on both the Non-Secure Internet Protocol Router Network\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Secure Internet Protocol Router Network\"\n }, \"NIPRNet\"), \") and Secure Internet Protocol Router Network (SIPRNet).\\nNormally, programs have a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Secure Internet Protocol Router Network\"\n }, \"NIPRNet\"), \" Test Program Management page. If a\\nprogram has classified documents, A-3 in coordination with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", will\\ncreate a SIPRNet page for it. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" maintains Top Secret and Special\\nAccess Required (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \") documents on appropriate information systems\\noutside of Test Program Management (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \").\"), mdx(\"h1\", null, \"Air Force Manual 63-119 Responsibilities\"), mdx(\"p\", null, \"Air Force Manual (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \") 63\\u2011119, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Certification of System Readiness for\\nDedicated Operational Testing\"), \", presents a structured mechanism or\\n\\\"process\\\" to identify problems and risks associated with transitioning\\nfrom \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"&E to the final phase of dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E.\"), mdx(\"p\", null, \"The certification process helps acquisition managers at all levels\\nidentify risks, reach negotiated agreements on issues, and render an\\naccurate assessment of a system's readiness to begin the final phase of\\ndedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will pursue all possible initiatives to enable\\ndelivery of lethal combat capability at the speed of relevance. To\\nimplement this, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will seek early \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" credit to eliminate\\nduplication of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"'s previous testing, reduce dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E, and support\\ndelivery of combat capability as early as possible. Consequently, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nno longer relies on the certification process at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Readiness Review\"\n }, \"OTRR\"), \".\"), mdx(\"p\", null, \"If the program office or the program execution officer (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \") determines\\nan \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Readiness Review\"\n }, \"OTRR\"), \" is required, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will support the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \"'s certification review\\nby presenting an operational test review (OTR) that covers status of\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E data collection efforts to date, significant findings we have\\nidentified, remaining requirements to complete \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E, and risks to\\ncompleting \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E.\"), mdx(\"p\", null, \"If the program office or the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \" requires certification, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will\\ntailor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \" 63-119 templates to meet specific project needs as agreed\\nto by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" communities. Then, we will assess templates using\\nobjective measurements to the maximum extent to determine whether we met\\nexit criteria.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools\"), \": Periodic O-6 level reviews with stakeholders.\"), mdx(\"h2\", null, \"Air Force Manual 63-119 Flexibility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \" 63-119 templates are flexible and apply to any acquisition\\nprogram. Consider template attachments because some require \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \" action,\\nspecifically. Maintain continuous dialogue with the program office and\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" community to comply with template requirements. Scrutinize\\ndeviations from a true operational or production-representative article\\nfor potential limitations to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. Tailor the templates or add new ones\\nto achieve objectives of the certification process.\"), mdx(\"h1\", null, \"Program-Related Document Reviews\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" helps prepare key requirements and acquisition documents to\\nincorporate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" interests into the acquisition process. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s\\nparticipation varies depending on the situation. A-3 manages the product\\nreview process.\"), mdx(\"h1\", null, \"Technical Reviews\"), mdx(\"p\", null, \"The test team conducts technical reviews for every test activity. Who\\nconducts the technical review will depend upon the level of test and\\nexpected reporting. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" conducts the review for test activities expected\\nto answer effectiveness and/or suitability. The Detachment technical\\nadvisor conducts the review for all other test activities. The test team\\nmay request a technical review by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" for any level of test activity.\"), mdx(\"h1\", null, \"Technical Advisors Board\"), mdx(\"p\", null, \"Technical advisors (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Advisor OR Test Area\"\n }, \"TA\"), \") make up the TAB, under the leadership of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \"\\nTechnical Advisor (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \"). The TAB's primary role is to advise\\nDirectors, Detachment Commanders, and Detachment personnel on processes\\nand/or non-standard approaches for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities, and applying \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \"\\nprinciples to meet the Commander's intent and vision.\"), mdx(\"h1\", null, \"Technical and Scientific Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" government personnel are the first choice for technical support,\\nfollowed by external government personnel, and then lastly, contracted\\nsupport personnel. If none of these are available, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" (A1, A2/9,\\nA3, A4/7, A5/8) will work with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" to identify technical and\\nscientific contract support needs to perform specific tasks when they\\nbegin formulating the test strategy or initial test design. Technical\\nand scientific support should be thought of broadly and include\\ncontractor services, leases, and any operational or logistical support\\nrequired.\"), mdx(\"h1\", null, \"Technical and Scientific Support\"), mdx(\"p\", null, \"Detachment test teams should explore the availability of technical\\nsupport from A-2/9, A-5/8, Detachment TAs, and other external military\\nand government agencies when developing the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \". A-2/9 personnel have a\\nbroad ability to provide technical and scientific support in areas of\\neffectiveness evaluation, suitability evaluation, human factors,\\nintelligence, and test capability verification, validation, and\\naccreditation. In addition, they ensure technically feasible test plans,\\nanalytically sound measures and methods, and supportable conclusions for\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. A-2/9 personnel ensure \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" addresses human factors and system\\ntraining issues adequately, and they provide technical expertise in\\nobservational methods and questionnaire development and administration.\\nA-2N and Detachment (if assigned) Intel personnel must ensure the test\\nprogram threat list and the test threat environment are addressed\\nadequately and that appropriate intelligence is used to support planning\\nand developing the threat portions of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s test documents. Finally,\\nthey provide special security office support.\"), mdx(\"p\", null, \"A-5R identifies, advocates, and develops test capabilities (e.g., open\\nair range, ground test facilities, instrumentation, targets and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \") to\\nsupport test teams. A-5R provides technical assistance for space, air,\\nand ground systems.\"), mdx(\"h1\", null, \"Lessons Learned\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" actively seeks to improve our processes and products. Our Lessons\\nLearned (LL) program is one method through which we demonstrate our\\ncommitment to being a learning organization.\", mdx(\"sup\", {\n parentName: \"p\",\n \"id\": \"fnref-1\"\n }, mdx(\"a\", {\n parentName: \"sup\",\n \"href\": \"#fn-1\",\n \"className\": \"footnote-ref\"\n }, \"1\")), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" defines LLs as,\\n\\\"\", mdx(\"em\", {\n parentName: \"p\"\n }, \"A documented event or experience that provides test team insight and\\nmission improvement\"), \".\\\" The goal of LL is to foster a culture in which we\\nidentify those experiences and learn from them, both individually and\\ncollectively. We learn by changing our business practices, which\\nincludes updating policies, such as the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Guide, or updating training\\ncurriculum on an ongoing basis. \\\"Mission improvement\\\" is embedded in the\\ndefinition of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" LL because it emphasizes our intent to transform\\nthe organization continuously. Refer to the \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/lessons_learned_guide/\"\n }, \"Lessons Learned\\nGuide\"), \".\"), mdx(\"h1\", null, \"Information Releases\"), mdx(\"p\", null, \"Forward all requests for information through the appropriate point of\\ncontact (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \"), as outlined in Table 6-2. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" releases the\\ninformation after reviewing its distribution and release markings and\\ncoordinating it through ACAP for approval.\"), mdx(\"p\", null, \"Table 6\\u20112. POCs for Information Requests\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Type of Request\"), mdx(\"th\", null, \"POC\"), mdx(\"th\", null, \"*Coordination\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"DoD Agency\"), mdx(\"td\", null, \"HO\"), mdx(\"td\", null, \"A-3\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Agency not authorized by distribution statement\"), mdx(\"td\", null, \"HO\"), mdx(\"td\", null, \"FOIA Officer/A-3\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"FOIA\"), mdx(\"td\", null, \"FOIA Office (A\\u20116)\"), mdx(\"td\", null, \"HO/LC/PA/A\\u20117K/IP/OPSEC/A-3\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Media Release\"), mdx(\"td\", null, \"PA\"), mdx(\"td\", null, \"FOIA Office/ HO/LC/IP/OPSEC/A-3\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Foreign Disclosure\"), mdx(\"td\", null, \"A\\u20112/9\"), mdx(\"td\", null, \"FOIA Office/ HO/LC/PA/IP/OPSEC/A\\u20113 AFOTEC FDO\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*Coordination will vary depending on nature of information requested\"), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"h1\", null, \"Determining the Need for Contractor Services and Leases\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" planners should make every effort to use in-house support before\\nturning to contractor services. With limited funding available, closely\\nmanaging \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" contractor activity is critical. A-5/8 coordinates all\\nnew contractor efforts. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" must formally review proposed contractor\\nsupport that is \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-funded. We will determine the best approach to\\nobtain funding for externally funded contractors on a case-by-case\\nbasis. Find details in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/strat_planning_programming_guide/\"\n }, \"Strategy, Planning, and Programming\\nProcess (SP3)\\nGuide\"), \".\\nContact A-5/8 for assistance.\"), mdx(\"p\", null, \"A-5/8 will work with you to identify resource options. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" planners\\nshould have a good idea of the technical services required before\\nworking with A-4/7K to prepare the contract task order performance work\\nstatement (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Work Statement\"\n }, \"PWS\"), \"). \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \": Only the procuring contracting officer (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Procuring Contracting Officer\"\n }, \"PCO\"), \")\\ncan direct the contractor to perform services.\"), mdx(\"h1\", null, \"Contracts\"), mdx(\"p\", null, \"A-7K (contracting office) administers long-term technical service\\ncontracts with different companies that support \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s mission. These\\ncontracts are indefinite delivery/indefinite quantity (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Identification\"\n }, \"ID\"), \"/IQ) contracts\\nthat allow issuance of cost plus fixed fee or firm, fixed price task\\norders. A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Procuring Contracting Officer\"\n }, \"PCO\"), \" in A-7K manages these contracts. A contracting officer's\\nrepresentative (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer’s Representative\"\n }, \"COR\"), \") acts on behalf of the contracting officer to\\nmonitor contractor performance as outlined in a letter provided by A-7K,\\nwhich assigns the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer’s Representative\"\n }, \"COR\"), \" for a specific contracting task order. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer’s Representative\"\n }, \"COR\"), \"\\nresides where the work is being performed (Director/Detachment) and\\nshould clearly understand the tasks and associated technical work and\\nproducts the contractor is producing.\"), mdx(\"h1\", null, \"Selecting a Contractor\"), mdx(\"p\", null, \"Test teams that require technical services from existing contracts\\nprepare a contract task order \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Work Statement\"\n }, \"PWS\"), \" so contractors can prepare technical\\nand cost proposals, which the technical team evaluates. Requirements are\\ndefined as explicit work to be done and are independent of individual\\ncontractors or contractor personnel. The technical team evaluates\\ntechnical and cost approaches to determine which contractor offers the\\nbest value to the government. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Procuring Contracting Officer\"\n }, \"PCO\"), \" reviews these results and upon\\naccepting a contractor's proposal, A-7K awards a contract task order to\\nthe selected contractor. Fairness and open competition are critical to\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" getting the best return on its investment. There are rare\\nexceptions to the \\\"fair opportunity\\\" clause of the contract, which you\\ncan discuss with A-7K. The Air Force has established goals for expanding\\nsmall business opportunities and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is committed to supporting those\\ngoals. Test teams need to work closely with PCOs and contract\\nspecialists in A-7K for contractual support.\"), mdx(\"h1\", null, \"Contract Task Order\"), mdx(\"p\", null, \"The contract task order \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Work Statement\"\n }, \"PWS\"), \" describes the scope, technical requirements,\\ndeliverables, and period of performance. Provide the contract task order\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Work Statement\"\n }, \"PWS\"), \" to the contract specialist in electronic format. The contractor\\ncannot begin work on a contract task order until A-7K issues it to the\\ncontractor. Depending on the contract task order's complexity, the\\nentire review and award process may take up to 4 weeks after A-7K\\nreceives it. Consider overall contractor needs early in the test\\nprogram, just as for other resource requirements.\"), mdx(\"h1\", null, \"Contract Task Order Management\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer’s Representative\"\n }, \"COR\"), \" is not authorized to change any element of the contract task\\norder, but they process required changes through the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Procuring Contracting Officer\"\n }, \"PCO\"), \".\\nResponsibilities of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer’s Representative\"\n }, \"COR\"), \" are described in their assignment letter from\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Procuring Contracting Officer\"\n }, \"PCO\"), \". \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" provides \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer’s Representative\"\n }, \"COR\"), \" training periodically and designated\\npersonnel must attend that training prior to being nominated or\\nassigned.\"), mdx(\"h1\", null, \"Release of Intelligence Information to Contractors\"), mdx(\"p\", null, \"Intelligence information is restricted from release to government\\ncontractors. Contact A-2/9 and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s contracting officer for guidance\\nbefore releasing intelligence to contractors. These requirements pertain\\nto collateral and sensitive compartmented information (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Sensitive Compartmented Information\"\n }, \"SCI\"), \"). The purpose\\nof these requirements is to ensure dissemination of intelligence\\ninformation is controlled properly and does not give a competitive edge\\nto a particular contractor. Classified information remains the property\\nof the U.S. government and the program office must return it to\\ngovernment control upon a program's completion. DD Form 254, \\\"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \"\\nContract Security Classification Specification,\\\" for each contract\\nspecifies whether the release of intelligence is authorized for that\\ncontract. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer’s Representative\"\n }, \"COR\"), \" requests release of intelligence on behalf of the\\ncontractor, and A-2/9 ensures the contractor receives the intelligence\\ndata necessary to meet their obligations.\"), mdx(\"h1\", null, \"Real Property, Facilities, Furniture, Communications and Off Base Leases\"), mdx(\"p\", null, \"Plan facility, furniture, and real-property acquisitions early. In\\ngeneral, submit small facility projects, such as room renovations and\\nfurniture procurements in memorandum form with an explanatory \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" Form\\n332, \\\"Base Civil Engineer Work Request\\\" to the Engineering, Facilities\\nand Logistics Division (A-4F) as part of the budget call for the\\nfollowing fiscal year (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fiscal Year\"\n }, \"FY\"), \"). Submit an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" Form 332 to A-4F at least 3\\nyears prior to the projected need date for large projects such as new\\nbuildings, building additions, extensive renovations and off-base leased\\nfacilities space or land. Consider the following:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Document new requirements that require office space, land, or\\nspecial use areas on Part 1 of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" Form 332, along with a brief\\njustification, and submit it to A-4F as soon as the requirement is\\nknown.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Document repair and maintenance of existing facilities on Part 1 of\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" Form 332 and submit it to A-4F. Items that require submission\\ninclude new carpeting, painting, wall coverings, modification to a\\nbuilding's mechanical or electrical systems, or installation of\\nequipment that will be connected to a building's systems or\\nutilities permanently.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Submit furniture and facility equipment requirements to A-4F. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nwill meet all other requirements from its existing inventory, UNICOR\\n(Prison Industry), Government Services Administration (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Services Administration\"\n }, \"GSA\"), \"),\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Services Administration\"\n }, \"GSA\"), \"-approved vendors, or the open market, in that order.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Submit \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" eCSRD (Electronic Communication Systems Requirements\\nDocument) to A-6 to identify communication requirements. Test\\nrequirements usually include SIPRNet access, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Secure Internet Protocol Router Network\"\n }, \"NIPRNet\"), \" access, secure\\nterminal equipment access and/or home-station reach-back\\nrequirements. A-6 will coordinate with test locations to ensure\\nthese capabilities exist and are coordinated in time for test\\nevents. Elevate communication requirements to the Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"\\nand/or the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" command section, if required.\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#test-team-selection","title":"Test Team Selection"},{"url":"#administrative-support-requirements","title":"Administrative Support Requirements"},{"url":"#major-command-assigned-test-team-members","title":"Major Command-Assigned Test Team Members"},{"url":"#test-program-applications","title":"Test Program Applications"},{"url":"#air-force-manual-63-119-responsibilities","title":"Air Force Manual 63-119 Responsibilities","items":[{"url":"#air-force-manual-63-119-flexibility","title":"Air Force Manual 63-119 Flexibility"}]},{"url":"#program-related-document-reviews","title":"Program-Related Document Reviews"},{"url":"#technical-reviews","title":"Technical Reviews"},{"url":"#technical-advisors-board","title":"Technical Advisors Board"},{"url":"#technical-and-scientific-support","title":"Technical and Scientific Support"},{"url":"#technical-and-scientific-support-1","title":"Technical and Scientific Support"},{"url":"#lessons-learned","title":"Lessons Learned"},{"url":"#information-releases","title":"Information Releases"},{"url":"#determining-the-need-for-contractor-services-and-leases","title":"Determining the Need for Contractor Services and Leases"},{"url":"#contracts","title":"Contracts"},{"url":"#selecting-a-contractor","title":"Selecting a Contractor"},{"url":"#contract-task-order","title":"Contract Task Order"},{"url":"#contract-task-order-management","title":"Contract Task Order Management"},{"url":"#release-of-intelligence-information-to-contractors","title":"Release of Intelligence Information to Contractors"},{"url":"#real-property-facilities-furniture-communications-and-off-base-leases","title":"Real Property, Facilities, Furniture, Communications and Off Base Leases"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-1-2-team-standup.md"},"frontmatter":{"metaTitle":"Team Stand-up","metaDescription":"Team Stand-up"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"ad9c781a-9549-5d22-b383-547869f5fed7"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/6-1-3-team-training/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-1-3-team-training","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"11c599a2-b29d-54b9-b0e1-74929d1e6266","title":"Team Training","slug":"/OT&E_Guide/6-1-3-team-training"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Team Training\",\n \"metaTitle\": \"Team Training\",\n \"metaDescription\": \"Team Training\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"Before initiating a test, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" trains \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E members and support\\npersonnel (including \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" testers) on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles, testing\\npolicies, and the test program, commensurate with each team member's\\nresponsibilities. The A-1 Training Division is the focal point that\\nconducts a variety of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E courses that cover a portion of the training\\nrequired by test team members. A-1 personnel assist the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" with his/her\\nobligation to determine \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E training requirements for test team\\npersonnel and participants. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" works with A-1 to ensure training is\\nscheduled in sufficient time (prior to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E) to enable test personnel to\\nplan and develop detailed test procedures and identify test data\\ncollection requirements. Test team personnel, including \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \"-assigned\\nmembers, attend the Test Team Operations Course (TTOC) prior to\\nconducting test to establish how the team will conduct the test and how\\nthey will collect data. A-1T (and occasionally A-3) personnel conduct\\nthe TTOC (just prior to the start of the test), which is a combination\\nof \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", program office, contractor, and test team efforts that\\ninvolve the following procedures, instructions and responsibilities:\"), mdx(\"h1\", null, \"Governing Policies and Procedures on Involvements\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand the scope and purpose of the test, specific test events,\\ndescription of test items, test methods, and program milestones\\nsupported.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Define operational effectiveness and suitability.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Define test team roles and responsibilities throughout the test\\nevent.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand/apply the test plan, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Management and Analysis Plan\"\n }, \"DMAP\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detailed Test Plan\"\n }, \"DTP\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Classification Guide\"\n }, \"SCG\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s critical information list (CIL), and\\noperations security (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operations Security\"\n }, \"OPSEC\"), \") plan.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand concept of test execution.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand proper handling of media and visiting personnel,\\nreleasing early data, managing source selection, and competition\\nsensitive data.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Administer/manage test data collection tools.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Know test team rules of engagement during test execution.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" situation reports (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Situational Report\"\n }, \"SITREP\"), \").\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand \\\"pause test\\\" and \\\"stop test\\\" requirements and actions.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Identify significant impacts during test.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand types of data and how to administer test questionnaires.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Be familiar with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Referential Integrity\"\n }, \"DRI\"), \"&R system and submitting DRs.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand Deficiency Review Board (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deficiency Review Board\"\n }, \"DRB\"), \") functions.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand test team roles and responsibilities during the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Reliability and Maintainability Evaluation Team\"\n }, \"JRMET\"), \" and\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Data Scoring Board\"\n }, \"TDSB\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand the test's analysis and evaluation process.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s reporting and coordination processes.\"))), mdx(\"h1\", null, \"Test Team System Training\"), mdx(\"p\", null, \"Team members might require operator/maintainer system familiarization\\ntraining to support \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E on a new or modified system. If the developing\\ncontractor provides system familiarization training, ensure you identify\\nthat in the contract (Type-1 training) via the program office \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \". The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"\\nshould consider obtaining other special training (Type-2 training) that\\nmight be necessary for supporting or using the system, such as system\\nacademics, airdrop training, or specific training on what a system\\nfailure would look like.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#governing-policies-and-procedures-on-involvements","title":"Governing Policies and Procedures on Involvements"},{"url":"#test-team-system-training","title":"Test Team System Training"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-1-3-team-training.md"},"frontmatter":{"metaTitle":"Team Training","metaDescription":"Team Training"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"11c599a2-b29d-54b9-b0e1-74929d1e6266"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-1-3-team-training","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"11c599a2-b29d-54b9-b0e1-74929d1e6266","title":"Team Training","slug":"/OT&E_Guide/6-1-3-team-training"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Team Training\",\n \"metaTitle\": \"Team Training\",\n \"metaDescription\": \"Team Training\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"Before initiating a test, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" trains \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E members and support\\npersonnel (including \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" testers) on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles, testing\\npolicies, and the test program, commensurate with each team member's\\nresponsibilities. The A-1 Training Division is the focal point that\\nconducts a variety of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E courses that cover a portion of the training\\nrequired by test team members. A-1 personnel assist the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" with his/her\\nobligation to determine \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E training requirements for test team\\npersonnel and participants. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" works with A-1 to ensure training is\\nscheduled in sufficient time (prior to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E) to enable test personnel to\\nplan and develop detailed test procedures and identify test data\\ncollection requirements. Test team personnel, including \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \"-assigned\\nmembers, attend the Test Team Operations Course (TTOC) prior to\\nconducting test to establish how the team will conduct the test and how\\nthey will collect data. A-1T (and occasionally A-3) personnel conduct\\nthe TTOC (just prior to the start of the test), which is a combination\\nof \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", program office, contractor, and test team efforts that\\ninvolve the following procedures, instructions and responsibilities:\"), mdx(\"h1\", null, \"Governing Policies and Procedures on Involvements\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand the scope and purpose of the test, specific test events,\\ndescription of test items, test methods, and program milestones\\nsupported.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Define operational effectiveness and suitability.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Define test team roles and responsibilities throughout the test\\nevent.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand/apply the test plan, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Management and Analysis Plan\"\n }, \"DMAP\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detailed Test Plan\"\n }, \"DTP\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Classification Guide\"\n }, \"SCG\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s critical information list (CIL), and\\noperations security (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operations Security\"\n }, \"OPSEC\"), \") plan.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand concept of test execution.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand proper handling of media and visiting personnel,\\nreleasing early data, managing source selection, and competition\\nsensitive data.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Administer/manage test data collection tools.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Know test team rules of engagement during test execution.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" situation reports (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Situational Report\"\n }, \"SITREP\"), \").\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand \\\"pause test\\\" and \\\"stop test\\\" requirements and actions.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Identify significant impacts during test.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand types of data and how to administer test questionnaires.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Be familiar with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Referential Integrity\"\n }, \"DRI\"), \"&R system and submitting DRs.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand Deficiency Review Board (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deficiency Review Board\"\n }, \"DRB\"), \") functions.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand test team roles and responsibilities during the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Reliability and Maintainability Evaluation Team\"\n }, \"JRMET\"), \" and\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Data Scoring Board\"\n }, \"TDSB\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand the test's analysis and evaluation process.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Understand \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s reporting and coordination processes.\"))), mdx(\"h1\", null, \"Test Team System Training\"), mdx(\"p\", null, \"Team members might require operator/maintainer system familiarization\\ntraining to support \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E on a new or modified system. If the developing\\ncontractor provides system familiarization training, ensure you identify\\nthat in the contract (Type-1 training) via the program office \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \". The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"\\nshould consider obtaining other special training (Type-2 training) that\\nmight be necessary for supporting or using the system, such as system\\nacademics, airdrop training, or specific training on what a system\\nfailure would look like.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#governing-policies-and-procedures-on-involvements","title":"Governing Policies and Procedures on Involvements"},{"url":"#test-team-system-training","title":"Test Team System Training"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-1-3-team-training.md"},"frontmatter":{"metaTitle":"Team Training","metaDescription":"Team Training"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"11c599a2-b29d-54b9-b0e1-74929d1e6266"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/6-2-risk-management/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-2-risk-management","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"30d2e7cc-66ef-5a19-b4fe-1693c6c2b194","title":"Risk Management","slug":"/OT&E_Guide/6-2-risk-management"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Risk Management\",\n \"metaTitle\": \"Risk Management\",\n \"metaDescription\": \"Risk Management\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" applies risk management (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \") throughout all activities and test\\nprograms at both \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \" levels\", \"-\", \"-deliberate and real time\", \"-\", \"-in compliance\\nwith \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 90-802, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Risk Management\"), \", and Air Force Pamphlet (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Pamphlet\"\n }, \"AFPAM\"), \")\\n90\\u2011803, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Risk Management (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \") Guidelines and Tools\"), \". The deliberate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \"\\nsteps apply throughout the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E phases, from program inception\\nto the final report. Real-time steps apply during test execution, SDPE\\nand EX rapid tests. Both deliberate and real-time \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \" are codified in the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/safety_risk_mgmt_guide/\"\n }, \"Safety Risk Management\\nGuide\"), \".\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" and the test team work collaboratively with the contractor and the\\nsystem program office to address multiple kinds of risks, which include\\nsystem (technology) hazards, human system integration hazards,\\noccupational health hazards, environmental hazards, and testing hazards.\\nAll risk factors will be included in a final review through the\\nIntegrated Safety Review Board and/or the Environment Safety and\\nOccupational Health Certification Board prior to any test activity. The\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" office will adapt the review based on the test team's level of\\nexposure and type of test activity. The final review will provide a risk\\nto test decision that will be accepted by the appropriate risk\\nacceptance authority, as follows: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" for No impact, DO for Minimal\\nimpact, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" for Substantial impact, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" for Severe impact. The\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and test teams will proceed to test activities (observations, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \",\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Evaluation\"\n }, \"OUE\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E, etc.) only after completing the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \" process. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \":\\nProgram risk, schedule risk, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Risk Assessment Level of Test\"\n }, \"RALOT\"), \", etc. are addressed in other sections\\nof this \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Guide.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-2-risk-management.md"},"frontmatter":{"metaTitle":"Risk Management","metaDescription":"Risk Management"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"30d2e7cc-66ef-5a19-b4fe-1693c6c2b194"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-2-risk-management","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"30d2e7cc-66ef-5a19-b4fe-1693c6c2b194","title":"Risk Management","slug":"/OT&E_Guide/6-2-risk-management"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Risk Management\",\n \"metaTitle\": \"Risk Management\",\n \"metaDescription\": \"Risk Management\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" applies risk management (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \") throughout all activities and test\\nprograms at both \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \" levels\", \"-\", \"-deliberate and real time\", \"-\", \"-in compliance\\nwith \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 90-802, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Risk Management\"), \", and Air Force Pamphlet (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Pamphlet\"\n }, \"AFPAM\"), \")\\n90\\u2011803, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Risk Management (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \") Guidelines and Tools\"), \". The deliberate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \"\\nsteps apply throughout the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E phases, from program inception\\nto the final report. Real-time steps apply during test execution, SDPE\\nand EX rapid tests. Both deliberate and real-time \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \" are codified in the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/safety_risk_mgmt_guide/\"\n }, \"Safety Risk Management\\nGuide\"), \".\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" and the test team work collaboratively with the contractor and the\\nsystem program office to address multiple kinds of risks, which include\\nsystem (technology) hazards, human system integration hazards,\\noccupational health hazards, environmental hazards, and testing hazards.\\nAll risk factors will be included in a final review through the\\nIntegrated Safety Review Board and/or the Environment Safety and\\nOccupational Health Certification Board prior to any test activity. The\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" office will adapt the review based on the test team's level of\\nexposure and type of test activity. The final review will provide a risk\\nto test decision that will be accepted by the appropriate risk\\nacceptance authority, as follows: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" for No impact, DO for Minimal\\nimpact, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" for Substantial impact, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" for Severe impact. The\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and test teams will proceed to test activities (observations, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \",\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Evaluation\"\n }, \"OUE\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E, etc.) only after completing the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \" process. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \":\\nProgram risk, schedule risk, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Risk Assessment Level of Test\"\n }, \"RALOT\"), \", etc. are addressed in other sections\\nof this \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Guide.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-2-risk-management.md"},"frontmatter":{"metaTitle":"Risk Management","metaDescription":"Risk Management"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"30d2e7cc-66ef-5a19-b4fe-1693c6c2b194"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/6-3-resources/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-3-resources","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"912205be-c578-5818-a620-3d648c16f8af","title":"Resources","slug":"/OT&E_Guide/6-3-resources"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Resources\",\n \"metaTitle\": \"Resources\",\n \"metaDescription\": \"Resources\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"A-5/8 assists in obtaining the correct test resources tools, manpower,\\nand facilities to complete our \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" mission. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses a transparent,\\ndefendable, data-driven process to identify and source resource\\nrequirements. The overarching process is described in the \\\"\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/strat_planning_programming_guide/\"\n }, \"Strategic\\nProgramming and Planning Process (SP3)\\nGuide\"), \".\\\"\\nA-8P, Strategy, Planning and Programming, is \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \"'s office of primary\\nresponsibility (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Primary Responsibility\"\n }, \"OPR\"), \") that assists the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" in documenting resources\\nassociated with their test program. TDs, working with their Detachment\\ntest resource manager (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \"), document resources in the program's test\\nresource plan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \"). The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" is the cornerstone document for test\\nactivity resources and contains detailed information (internal and\\nexternal) regarding funding, test personnel, travel, range requirements,\\nfacilities, cyber, modeling and simulation, missiles, munitions,\\ntargets, and certain administrative supplies and equipment. This\\ninformation is used to compile resource requirements \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-wide. The\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" also communicates \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s requirements to outside resourcing\\nagencies.\"), mdx(\"p\", null, \"When identifying resources, TDs should incorporate integrated and\\nsynchronized \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" events and schedule their use to streamline\\nactivities whenever possible. Resources should be aligned as closely as\\npossible to the test activities they support. The following paragraphs\\noutline the process and products associated with test activity\\nresources.\"), mdx(\"h1\", null, \"Detachment Test Resource Manager\"), mdx(\"p\", null, \"The Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" is the primary test team member responsible for\\nresolution of test program resource management issues for the Detachment\\ncommander. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" identifies initial estimated resource requirements\\nearly in the test strategy and presents them to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" senior leaders\\nfor approval. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" documents initial estimates in the initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \". The\\nDetachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" evaluates assigned programs during early planning\\nactivities to support identification and validation of test program\\nresource requirements (e.g., ranges, transportation requirements,\\nsupport equipment, operationally representative users) and the best\\nstrategy development for securing resources. As a member of the test\\nteam, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" supports the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" by advocating for and defending\\nkey resource requirements to the acquisition and using commands. By\\nensuring key test resources are available when required, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" TRMs\\nsupport creating the most operationally representative test evaluation\\nenvironment possible. It is essential to identify test range\\nrequirements early. If testing requires range resources\", \"-\", \"-e.g., White\\nSands Missile Range (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"White Sands Missile Range\"\n }, \"WSMR\"), \"), Utah Test and Training Range (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Utah Test and Training Range\"\n }, \"UTTR\"), \"),\\nEglin\", \"-\", \"-TRMs will contact A-3 and A-5R. If testing requires the use of\\nthe Nevada Test and Training Range (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nevada Test and Training Range\"\n }, \"NTTR\"), \"), TRMs will contact A-3/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operating Location\"\n }, \"OL\"), \"-NN\\nand A-8Z at least 1 year (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"No or Not Later Than\"\n }, \"NLT\"), \" 6 months) before they need range time.\\nWhen testing has unique \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E program requirements, TRMs will engage the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" and internal (e.g., A-3, A\\u20114/7, A-5/8) and external stakeholders\\nto obtain those resources. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" TRMs ensure the test team acquires\\nnecessary resources to perform successful \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. They collaborate with\\nTDs to ensure TRPs are managed and updated regularly. Finally, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ntest teams have worked with other test organizations to share range\\ntimes. As range resources and times become harder to schedule, TDs\\nshould consider and request opportunities to share with another test\\norganization, which could potentially reduce costs.\"), mdx(\"h1\", null, \"Test Resource Cost Estimation Tool\"), mdx(\"p\", null, \"TDs and TRMs use the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-developed cost estimation tool (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \"\\nenter data for each category required and the tool generates an Excel\\nspreadsheet. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" uses this cost estimate data to input required\\nresource records into the program's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \"), along with its associated\\nbusiness rules, to generate cost estimates for TRPs. The tool is located\\non the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet and covers every \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" cost category. Contact A-8P\\nfor assistance.\"), mdx(\"h1\", null, \"Test Resource Plan\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" captures and documents required resources for all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities.\\nThey must stay current to support \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s resource allocation\\nprocesses.\"), mdx(\"p\", null, \"Each test program has a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" maintained by the Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" that\\nextends over multiple years and is refined continuously over the test\\nlifecycle. TRPs contain detailed information (internal and external)\\nregarding funding, test personnel, travel, range requirements,\\nfacilities, cyber, modeling and simulation, missiles, munitions,\\ntargets, and certain administrative supplies and equipment. TRPs are\\nliving documents and require routine attention and updates by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \". As\\ngreater fidelity is gained for a particular test, the test team must\\nrefine the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \".\"), mdx(\"p\", null, \"Keeping pace with rapid acquisition presents unique concerns for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"\\nand resources required for test activities. When developing TRPs, you\\nmust place special attention on \\\"what\\\" resources you need and \\\"when\\\" you\\nneed them to support an adaptive, responsive test approach. TDs must\\naggressively track program timelines and ensure they align required\\nresources with scheduling needs. A-8P can provide insight and assistance\\nwith documenting resource needs for rapid acquisition programs.\"), mdx(\"p\", null, \"Again, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" management is a continuous process. TDs and TRMs must review\\nand validate requirements by the first Monday of each month and update\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" information, at a minimum, every 6 months or when major changes\\noccur. A major change is defined as any cost estimate change that\\nexceeds \", \"$\", \"250K or a programmatic event that results in a test activity\\nslipping out of the fiscal year. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" TRMs will immediately notify A-8P\\nof funding requirement changes that exceed \", \"$\", \"250K.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" is the basis for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s input into the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Planning,\\nProgramming, Budgeting, and Execution (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Planning, Programming, Budgeting, and Execution\"\n }, \"PPBE\"), \") process and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s\\ninternal SP3\", \"-\", \"-the process through which \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" justifies and obtains\\nresources. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" also informs \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s Unfunded Requirements (UFR)\\nlists and Financial Management Board (FMB) decisions. In addition, the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" supports \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s annual Requirements Review Board (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \") process,\\ndiscussed later in this chapter.\"), mdx(\"p\", null, \"Using \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" and other financial data during the year of execution, A-5/8\\nand A-4/7 prepare a monthly Time-Phased Investment Document (T-PhID)\\nshowing funding requirements for the current and following fiscal years.\\nA-5/8 sends the T-PhID to Detachment Commanders to review and validate\\nrequirements. If the T-PhID changes substantially from the previous\\nmonth, A-5/8 presents those changes to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Commander. The T-PhID\\nis a consolidated document that the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Commander, A-4/7, and A-5/8\\npresent to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" organizations to advocate for resources.\"), mdx(\"p\", null, \"Once a test program's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" is approved and transferred to a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \", the A-3\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" will work with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" to prepare an initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" within\\n60 days of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" approval. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" and test team coordinate the initial\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" before submitting it to A-8P. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" update the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \"\\ncontinuously as the program updates. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" personnel can access the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \"\\nthrough \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SharePoint. Test teams will not initiate TRPs for\\nprograms in pre-involvement, or those \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" recommends for\\nnon-involvement.\"), mdx(\"p\", null, \"TDs identify specialties and skill levels they need for their test team.\\nThe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" includes requirements for skills, reporting dates, and number of\\ntest team members. Detachment leadership decides which test team\\npositions are permanently assigned and which will use individuals in a\\ntemporary duty (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Temporary Duty\"\n }, \"TDY\"), \") status. Normally, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" fulfills permanent-party\\npositions through current directorate/Detachment resources. Carefully\\nconsider the timing of standing up your test team as part of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nplanning. Usually, you will assign the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \", and initial\\nadministrative support personnel first, then add deputies of operations,\\ncybersecurity, analysts and logistics personnel (if required) later.\\nWhen you determine how early to position your test team, allow adequate\\ntime to train and familiarize members on the test systems/environment.\\nDepending on the scope of the test, the location (i.e., not co-located\\nwith a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"), or special activities associated with a specific test\\nactivity, you may need to assign and place key test team members sooner\\nthan normal. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" coordinate with A-3 and the acquisition\\nprogram office to ensure we stand up test teams as timely and\\nefficiently as possible.\"), mdx(\"p\", null, \"In some circumstances, active duty resources are not available to\\nsupport \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E requirements (i.e., cybersecurity adversarial assessments\\nconducted by the Air National Guard). Due to differing funding policies\\nbetween active and Guard units, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" must include provisions for\\nmilitary personnel authorization (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manpower Authorization\"\n }, \"MPA\"), \") man-day funding if \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air National Guard\"\n }, \"ANG\"), \" or Air\\nReserve Component test support is anticipated (check with A-1W for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manpower Authorization\"\n }, \"MPA\"), \"\\nallocation and A-8P on how to properly enter \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manpower Authorization\"\n }, \"MPA\"), \" man-days into the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \").\\nFor additional information and details on missile, munitions, and target\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Munitions, Missiles, and Target\"\n }, \"MMT\"), \") forecasting requirements contact A-5R.\"), mdx(\"p\", null, \"In general, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" pays for most program activities. In the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \", the\\nrequirements \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" funds are labeled \\\"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\\" in the \\\"Funded By\\\" record\\nfield. Resources provided by another command or agency in support of an\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E activity are defined as external resources in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \", and\\nthe agency's name is entered in the \\\"Funded By\\\" record field.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s three largest test activity costs are TDYs, contractor support,\\nand range requirements.\"), mdx(\"p\", null, \"You can determine \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Temporary Duty\"\n }, \"TDY\"), \" costs by using the per diem web site at:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.defensetravel.dod.mil/site/perdiemCalc.cfm\"\n }, \"http://www.defensetravel.dod.mil/site/perdiemCalc.cfm\"), \". Contact A-7K\\nfor contract cost assistance.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" includes test range resources. TRMs contact A-3 and A-5R for\\nassistance with most test ranges. However, for Nevada Test and Training\\nRange (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nevada Test and Training Range\"\n }, \"NTTR\"), \") resources, TRMs should contact A-3/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operating Location\"\n }, \"OL\"), \"-NN and A-8Z. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \":\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not pay for range infrastructure improvements. Rarely will\\ntest infrastructure improvements be a program cost. A-5R and A-8Z\\naddress test infrastructure capability gaps through the SP3, by\\ngathering \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" test activity range infrastructure requirements. Test\\nteams should identify test infrastructure capability gaps as early as\\npossible to allow A-5R and A-8Z sufficient time to advocate requirements\\nto \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" test infrastructure resource organizations.\"), mdx(\"p\", null, \"For missiles, munitions and target (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Munitions, Missiles, and Target\"\n }, \"MMT\"), \") requirements assistance,\\ncontact A-5R.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" includes indirect test activity support requirements (e.g.,\\ncomputers, furniture, copiers, and telephones). It also includes support\\nrequirements that other organizations must coordinate (e.g., telephone\\ninstallation, administrative switchboard and access to facilities,\\nSIPRNet, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Secure Internet Protocol Router Network\"\n }, \"NIPRNet\"), \", red phone). The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" should list all equipment necessary\\nto conduct the test activity that is not already on hand or available\\nthrough current supply inventory. Many of these items are available\\nthrough redistribution from other completed test programs. Contact A-4F\\nfor assistance with existing equipment availability. Whenever possible,\\nTDs/TRMs should plan to use already purchased (warehouse) equipment\\nrather than planning to purchase new equipment. For test activity\\nsupport cost assistance, contact A-8P. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" does not include\\nexpendable equipment items required to conduct test activities.\"), mdx(\"h1\", null, \"Special Access Program Test Resource Plans\"), mdx(\"p\", null, \"Due to various classifications of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" programs, A-3Z, in conjunction\\nwith the Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" and required test team members, prepares an\\ninitial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" once the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" is approved. A-3Z handles \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" TRPs via special\\nprocedures, not via \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s SharePoint. They coordinate funding with\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" Management Office (SAPMO) through proper communication\\nchannels. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"A-3Z must not submit \", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \"-related requirements to SP3\\nactivities without prior approval from \", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s SAPMO\"), \". A-3Z coordinates\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" TRPs with appropriate commands and agencies.\"), mdx(\"h1\", null, \"Test Resource Plan Procedures\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" coordinates TRPs formally twice a year. During the first cycle\\n(Jul--Sep), TDs update and A-5/8 approves all TRPs, then the Detachments\\ndistribute to external stakeholders by 30 Sep. During the second cycle\\n(Jan--Mar) TDs update all TRPs. TRPs that have a test scheduled within\\nthe next 2 years are distributed to external shareholders by 31 Mar. The\\ntest team must keep the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" current to reflect maturing resource\\nrequirements as their test plan develops. When a program or test\\nschedule changes, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" should have the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" assist him/her in revising\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \". Teams coordinate out-of-cycle TRPs to inform program POCs if\\nmajor resource requirements change before the next \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" cycle. Teams\\npublish out-of-cycle TRPs for programs that are new and on a fast track,\\nrestructuring, or undergoing substantial changes (i.e., schedule slips)\\nthat affect budget and resource requirements. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \": Ultimately,\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/CCs must manage their overall program requirements as part of their\\noverall portfolio (a balanced approach to every program and indirect\\nresource required), as opposed to managing individual TRPs. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/CCs\\npresent their respective portfolio status during quarterly financial\\nmanagement review boards, hosted by A\\u20114/7, and during RRBs. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s\\nSAPMO coordinates separate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" presentations.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" distributes TRPs to outside agencies as early as possible to give\\nthem time to program, obtain, and provide resource requirements. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" receive approval from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" to post TRPs (with approved\\nTOs) into the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Collaborative Action Platform (ACAP) for 2-letter\\ncoordination. A-5/8 and A-3 coordinate on all TRPs. If other 2-letters\\n(e.g., A-2/9, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \") or Dets need to provide support, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" TRMs will add\\nthem to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" coord. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" will adjudicate comments and send,\\nvia email, the corrected \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" to A-8P for final standardization/\\nevaluation. Once A-8P verifies comments were adjudicated satisfactorily,\\nthe A-5/8 Director, or designee, approves the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \"'s release to outside\\nagencies. A-8P notifies the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" that the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" is approved for release\\nvia email. Then, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" generates a cover memo for the approved\\nprogram's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \", which the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" signs. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" distributes the\\nsigned memo/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" to POCs on the list, which include organizations\\nsupporting \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", A-3, A-8P, and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"HQ AFOTEC History Office\"\n }, \"HO\"), \". \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \": Due to various\\nclassifications of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" programs, follow A-3Z's guidance on developing,\\nreviewing, coordinating, approving, and distributing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" TRPs. A-3Z\\nfunctions as A-8P and A-5R/8Z for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" TRPs. A-3Z strictly enforces SCGs\\nand may dictate modification of the process for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" TRPs.\"), mdx(\"h1\", null, \"Requirements Review Board\"), mdx(\"p\", null, \"The Requirements Review Board (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \") is an SP3 sub-process that reviews\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s resource requirements for the upcoming and future FYs. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \"\\nexamines resource requirements to determine whether \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" has adequate\\nfunding and manpower resources to perform test activities. A-8P\\ninitiates \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \" preparation in May. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" chairs the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \", which\\noccurs annually in July. After the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" approves the board's\\nresults, the program-owning detachment will update TRPs accordingly.\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \": For \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" programs, coordinate proposed \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \" discussions involving\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" requirements through A-3Z prior to submitting information to A-8Z as\\nan agenda item.\"), mdx(\"h1\", null, \"Basis of Estimate for Test Resources\"), mdx(\"p\", null, \"The basis of estimate for test resources is the compilation of test\\nevents, test methodologies, test scenarios, and the cost estimation\\ntool. It describes why you are testing, what you are going to do, and\\nhow you are going to do it, which forms the basis to estimate resources\\nrequired to execute the test. Underlying the basis of estimate is a set\\nof assumptions validated to the extent possible and then documented. For\\nan \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" and/or test strategy, we focus on high cost (which includes high\\nlevel of effort) and long-lead items (e.g., threats, instrumentation,\\nand \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"). Some of these items were identified previously. When forming\\nthe basis of estimate, consolidate these previously identified items and\\nreview test designs to identify new items. Resources required for COIs,\\ncollectively, may overlap. Identify these areas, and provide a\\nconsolidated list of resources with traceability and rationale.\\nUltimately, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/CCs are responsible for managing their respective\\nportfolios and resources. Table 6-3 contains contents of a basis of\\nestimate.\"), mdx(\"p\", null, \"Table 6\\u20113. Contents of Basis of Estimate\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Content Area\"), mdx(\"th\", null, \"Content Expectations\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"COIs\"), mdx(\"td\", null, \"Reviewing COIs provides insight into what resources may be required to collect data and analyze the results. Instrumentation, databases, data extraction tools and analysis tools are examples of resources that may be required. COIs provide the rationale or basis for these resources.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Test Events\"), mdx(\"td\", null, \"For the particular test designs underlying the test events, a review of the factors and levels provides insight into the resources to establish the conditions. Man-made threats, particular climate (artic, desert, etc.) conditions and terrain are examples of factors and levels that might drive resources. Threats are often expensive or long-lead to develop. Differing climates conditions and terrain could drive multiple deployments. The conditions required to execute the test events provide the rationale or basis for these resources.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Test Methodology\"), mdx(\"td\", null, \"How a set of test events are executed also provides the rationale or basis for resources. Field-testing may incur range costs, or possibly even the development of new range capabilities. M&S incurs both costs and potentially long-lead development. Reviewing the test methodologies provides insight on what might be needed to execute the test events.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Test Scenarios\"), mdx(\"td\", null, \"Test scenarios form the operationally realistic environment. Reviewing all the factors identified in the test design provides insight into the additional assets and test capabilities required to build the operationally realistic scenarios. Many of these factors, particularly the as-is factors, need to be measured and resources identified in order to collect and analyze data when executing the test scenario.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Assumptions\"), mdx(\"td\", null, \"Although assumptions may not directly drive resources, they provide indicators of potential risks and disconnects with other organizations.\")))), mdx(\"h1\", null, \"Initial Resource Estimates\"), mdx(\"p\", null, \"The core team uses the test strategy and/or the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" basis of estimate to\\nrefine resource estimates documented in the initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \". The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \"\\nupdates the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" to support the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" brief. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" review each\\nresource category of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" to determine which line items need costing\\nand which ones \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" must pay. Table 6-4 shows which \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E support costs\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" pays and which it does not pay.\"), mdx(\"p\", null, \"Table 6\\u20114. Operational \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" Support Costs\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Pays\"), mdx(\"th\", null, \"AFOTEC Does Not Pay\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Range costs\")), mdx(\"li\", null, mdx(\"p\", null, \"Equipment Rental\")), mdx(\"li\", null, mdx(\"p\", null, \"Printing and reproduction\")), mdx(\"li\", null, mdx(\"p\", null, \"Communications\")), mdx(\"li\", null, mdx(\"p\", null, \"Real property maintenance and construction\")), mdx(\"li\", null, mdx(\"p\", null, \"Contractor support for OT&E\")), mdx(\"li\", null, mdx(\"p\", null, \"Data reduction\")), mdx(\"li\", null, mdx(\"p\", null, \"Special supplies and equipment\")), mdx(\"li\", null, mdx(\"p\", null, \"Leases\")), mdx(\"li\", null, mdx(\"p\", null, \"Civilian pay for (temporary over hires)\")), mdx(\"li\", null, mdx(\"p\", null, \"Per diem and travel\")), mdx(\"li\", null, mdx(\"p\", null, \"Transportation of equipment required for test\")), mdx(\"li\", null, mdx(\"p\", null, \"Supplies and equipment\")), mdx(\"li\", null, mdx(\"p\", null, \"Dry run planning\")), mdx(\"li\", null, mdx(\"p\", null, \"Test preparation\")), mdx(\"li\", null, mdx(\"p\", null, \"COTS M&S supporting test planning and reporting (including accreditation)\")), mdx(\"li\", null, mdx(\"p\", null, \"Cybersecurity testing (cooperative vulnerability and penetration assessment [CVPA], adversarial assessment [AA])\")))), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Acquisition/modification of the system\")), mdx(\"li\", null, mdx(\"p\", null, \"Aircraft flying hours (other than range support aircraft)\")), mdx(\"li\", null, mdx(\"p\", null, \"Acquisition costs for major test vehicles\")), mdx(\"li\", null, mdx(\"p\", null, \"Cost of procuring test item or direct test item support. Maintaining the test item is the funding responsibility of the owning command. Includes contractor services and supply items to maintain the test item and fuel for the test item.\")), mdx(\"li\", null, mdx(\"p\", null, \"Missiles, munitions and targets\")), mdx(\"li\", null, mdx(\"p\", null, \"Telemetry kits\")), mdx(\"li\", null, mdx(\"p\", null, \"Range infrastructure\")), mdx(\"li\", null, mdx(\"p\", null, \"Type-1 (contractor) training and associated TDYs\")), mdx(\"li\", null, mdx(\"p\", null, \"Digital M&S that produces data for OT&E\")), mdx(\"li\", null, mdx(\"p\", null, \"M&S V&V\"))))))), mdx(\"h1\", null, \"Resource Management During Test\"), mdx(\"p\", null, \"Some tests are scheduled to be executed over an extended period. If\\ncurrent \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fiscal Year\"\n }, \"FY\"), \" costs exceed funding, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" engages with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \" and program\\noffice to determine whether the test event can be slipped until \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nhas sufficient funds, or whether the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \" is willing to provide funds to\\nkeep the current schedule. To support this decision, we must update the\\nprogram's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \". The elements of resource management for the test team do\\nnot change during test execution. An important test team best practice\\nis to rely on the resource manager/financial analyst during test\\nexecution so that the test team can devote more time to test events and\\nanalysis. Once test execution begins, resources are considered dedicated\\nand generally unavailable for reassignment until the test is completed.\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \": Report to A-4/7, immediately, significant changes to costs\\nanticipated or encountered during test execution.\"), mdx(\"h1\", null, \"Funds Management\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \", and financial analyst must track funding levels in all\\nestablished accounts. It is easy to over-obligate the travel account by\\nprocessing a lot of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Temporary Duty\"\n }, \"TDY\"), \" orders for test team augmentees and deployments.\\nYou can deplete the test range account quickly with unprojected flight\\ntest events. If you do not manage accounts properly, it may be months\\nbefore you realize the account is overdrawn. You are never authorized to\\noperate in the red. If you discover an expense (range or flight\\nactivity) that will drive your test into the red, contact A-4/7\\nimmediately so they can secure funds through the appropriate program\\noffice, or initiate a pause test until they can secure additional\\nfunding.\"), mdx(\"h1\", null, \"Government Purchase Card\"), mdx(\"p\", null, \"The government purchase card (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purchase Card\"\n }, \"GPC\"), \") is useful to purchase common supply\\nitems locally. If an unusual situation arises where you need to use the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purchase Card\"\n }, \"GPC\"), \", call the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"'s financial management personnel or A-7F to get a\\nfinancial ruling before you make the expenditure. Each Detachment has a\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purchase Card\"\n }, \"GPC\"), \" cardholder. If you have questions concerning the use of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purchase Card\"\n }, \"GPC\"), \",\\ncall the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purchase Card\"\n }, \"GPC\"), \" program manager in A-7K. Never use the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purchase Card\"\n }, \"GPC\"), \" for\\nunnecessary or unauthorized items. Improper purchases violate the law\\nand you could be punished and have to repay the charges personally.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#detachment-test-resource-manager","title":"Detachment Test Resource Manager"},{"url":"#test-resource-cost-estimation-tool","title":"Test Resource Cost Estimation Tool"},{"url":"#test-resource-plan","title":"Test Resource Plan"},{"url":"#special-access-program-test-resource-plans","title":"Special Access Program Test Resource Plans"},{"url":"#test-resource-plan-procedures","title":"Test Resource Plan Procedures"},{"url":"#requirements-review-board","title":"Requirements Review Board"},{"url":"#basis-of-estimate-for-test-resources","title":"Basis of Estimate for Test Resources"},{"url":"#initial-resource-estimates","title":"Initial Resource Estimates"},{"url":"#resource-management-during-test","title":"Resource Management During Test"},{"url":"#funds-management","title":"Funds Management"},{"url":"#government-purchase-card","title":"Government Purchase Card"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-3-resources.md"},"frontmatter":{"metaTitle":"Resources","metaDescription":"Resources"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"912205be-c578-5818-a620-3d648c16f8af"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-3-resources","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"912205be-c578-5818-a620-3d648c16f8af","title":"Resources","slug":"/OT&E_Guide/6-3-resources"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Resources\",\n \"metaTitle\": \"Resources\",\n \"metaDescription\": \"Resources\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"p\", null, \"A-5/8 assists in obtaining the correct test resources tools, manpower,\\nand facilities to complete our \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" mission. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses a transparent,\\ndefendable, data-driven process to identify and source resource\\nrequirements. The overarching process is described in the \\\"\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/strat_planning_programming_guide/\"\n }, \"Strategic\\nProgramming and Planning Process (SP3)\\nGuide\"), \".\\\"\\nA-8P, Strategy, Planning and Programming, is \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \"'s office of primary\\nresponsibility (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Primary Responsibility\"\n }, \"OPR\"), \") that assists the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" in documenting resources\\nassociated with their test program. TDs, working with their Detachment\\ntest resource manager (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \"), document resources in the program's test\\nresource plan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \"). The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" is the cornerstone document for test\\nactivity resources and contains detailed information (internal and\\nexternal) regarding funding, test personnel, travel, range requirements,\\nfacilities, cyber, modeling and simulation, missiles, munitions,\\ntargets, and certain administrative supplies and equipment. This\\ninformation is used to compile resource requirements \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-wide. The\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" also communicates \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s requirements to outside resourcing\\nagencies.\"), mdx(\"p\", null, \"When identifying resources, TDs should incorporate integrated and\\nsynchronized \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" events and schedule their use to streamline\\nactivities whenever possible. Resources should be aligned as closely as\\npossible to the test activities they support. The following paragraphs\\noutline the process and products associated with test activity\\nresources.\"), mdx(\"h1\", null, \"Detachment Test Resource Manager\"), mdx(\"p\", null, \"The Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" is the primary test team member responsible for\\nresolution of test program resource management issues for the Detachment\\ncommander. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" identifies initial estimated resource requirements\\nearly in the test strategy and presents them to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" senior leaders\\nfor approval. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" documents initial estimates in the initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \". The\\nDetachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" evaluates assigned programs during early planning\\nactivities to support identification and validation of test program\\nresource requirements (e.g., ranges, transportation requirements,\\nsupport equipment, operationally representative users) and the best\\nstrategy development for securing resources. As a member of the test\\nteam, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" supports the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" by advocating for and defending\\nkey resource requirements to the acquisition and using commands. By\\nensuring key test resources are available when required, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" TRMs\\nsupport creating the most operationally representative test evaluation\\nenvironment possible. It is essential to identify test range\\nrequirements early. If testing requires range resources\", \"-\", \"-e.g., White\\nSands Missile Range (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"White Sands Missile Range\"\n }, \"WSMR\"), \"), Utah Test and Training Range (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Utah Test and Training Range\"\n }, \"UTTR\"), \"),\\nEglin\", \"-\", \"-TRMs will contact A-3 and A-5R. If testing requires the use of\\nthe Nevada Test and Training Range (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nevada Test and Training Range\"\n }, \"NTTR\"), \"), TRMs will contact A-3/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operating Location\"\n }, \"OL\"), \"-NN\\nand A-8Z at least 1 year (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"No or Not Later Than\"\n }, \"NLT\"), \" 6 months) before they need range time.\\nWhen testing has unique \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E program requirements, TRMs will engage the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" and internal (e.g., A-3, A\\u20114/7, A-5/8) and external stakeholders\\nto obtain those resources. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" TRMs ensure the test team acquires\\nnecessary resources to perform successful \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. They collaborate with\\nTDs to ensure TRPs are managed and updated regularly. Finally, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ntest teams have worked with other test organizations to share range\\ntimes. As range resources and times become harder to schedule, TDs\\nshould consider and request opportunities to share with another test\\norganization, which could potentially reduce costs.\"), mdx(\"h1\", null, \"Test Resource Cost Estimation Tool\"), mdx(\"p\", null, \"TDs and TRMs use the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-developed cost estimation tool (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \"\\nenter data for each category required and the tool generates an Excel\\nspreadsheet. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" uses this cost estimate data to input required\\nresource records into the program's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \"), along with its associated\\nbusiness rules, to generate cost estimates for TRPs. The tool is located\\non the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet and covers every \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" cost category. Contact A-8P\\nfor assistance.\"), mdx(\"h1\", null, \"Test Resource Plan\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" captures and documents required resources for all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities.\\nThey must stay current to support \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s resource allocation\\nprocesses.\"), mdx(\"p\", null, \"Each test program has a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" maintained by the Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" that\\nextends over multiple years and is refined continuously over the test\\nlifecycle. TRPs contain detailed information (internal and external)\\nregarding funding, test personnel, travel, range requirements,\\nfacilities, cyber, modeling and simulation, missiles, munitions,\\ntargets, and certain administrative supplies and equipment. TRPs are\\nliving documents and require routine attention and updates by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \". As\\ngreater fidelity is gained for a particular test, the test team must\\nrefine the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \".\"), mdx(\"p\", null, \"Keeping pace with rapid acquisition presents unique concerns for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"\\nand resources required for test activities. When developing TRPs, you\\nmust place special attention on \\\"what\\\" resources you need and \\\"when\\\" you\\nneed them to support an adaptive, responsive test approach. TDs must\\naggressively track program timelines and ensure they align required\\nresources with scheduling needs. A-8P can provide insight and assistance\\nwith documenting resource needs for rapid acquisition programs.\"), mdx(\"p\", null, \"Again, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" management is a continuous process. TDs and TRMs must review\\nand validate requirements by the first Monday of each month and update\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" information, at a minimum, every 6 months or when major changes\\noccur. A major change is defined as any cost estimate change that\\nexceeds \", \"$\", \"250K or a programmatic event that results in a test activity\\nslipping out of the fiscal year. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" TRMs will immediately notify A-8P\\nof funding requirement changes that exceed \", \"$\", \"250K.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" is the basis for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s input into the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Planning,\\nProgramming, Budgeting, and Execution (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Planning, Programming, Budgeting, and Execution\"\n }, \"PPBE\"), \") process and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s\\ninternal SP3\", \"-\", \"-the process through which \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" justifies and obtains\\nresources. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" also informs \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s Unfunded Requirements (UFR)\\nlists and Financial Management Board (FMB) decisions. In addition, the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" supports \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s annual Requirements Review Board (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \") process,\\ndiscussed later in this chapter.\"), mdx(\"p\", null, \"Using \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" and other financial data during the year of execution, A-5/8\\nand A-4/7 prepare a monthly Time-Phased Investment Document (T-PhID)\\nshowing funding requirements for the current and following fiscal years.\\nA-5/8 sends the T-PhID to Detachment Commanders to review and validate\\nrequirements. If the T-PhID changes substantially from the previous\\nmonth, A-5/8 presents those changes to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Commander. The T-PhID\\nis a consolidated document that the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Commander, A-4/7, and A-5/8\\npresent to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" organizations to advocate for resources.\"), mdx(\"p\", null, \"Once a test program's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" is approved and transferred to a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \", the A-3\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" will work with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" to prepare an initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" within\\n60 days of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" approval. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" and test team coordinate the initial\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" before submitting it to A-8P. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" update the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \"\\ncontinuously as the program updates. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" personnel can access the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \"\\nthrough \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SharePoint. Test teams will not initiate TRPs for\\nprograms in pre-involvement, or those \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" recommends for\\nnon-involvement.\"), mdx(\"p\", null, \"TDs identify specialties and skill levels they need for their test team.\\nThe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" includes requirements for skills, reporting dates, and number of\\ntest team members. Detachment leadership decides which test team\\npositions are permanently assigned and which will use individuals in a\\ntemporary duty (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Temporary Duty\"\n }, \"TDY\"), \") status. Normally, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" fulfills permanent-party\\npositions through current directorate/Detachment resources. Carefully\\nconsider the timing of standing up your test team as part of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nplanning. Usually, you will assign the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \", and initial\\nadministrative support personnel first, then add deputies of operations,\\ncybersecurity, analysts and logistics personnel (if required) later.\\nWhen you determine how early to position your test team, allow adequate\\ntime to train and familiarize members on the test systems/environment.\\nDepending on the scope of the test, the location (i.e., not co-located\\nwith a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"), or special activities associated with a specific test\\nactivity, you may need to assign and place key test team members sooner\\nthan normal. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" coordinate with A-3 and the acquisition\\nprogram office to ensure we stand up test teams as timely and\\nefficiently as possible.\"), mdx(\"p\", null, \"In some circumstances, active duty resources are not available to\\nsupport \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E requirements (i.e., cybersecurity adversarial assessments\\nconducted by the Air National Guard). Due to differing funding policies\\nbetween active and Guard units, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" must include provisions for\\nmilitary personnel authorization (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manpower Authorization\"\n }, \"MPA\"), \") man-day funding if \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air National Guard\"\n }, \"ANG\"), \" or Air\\nReserve Component test support is anticipated (check with A-1W for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manpower Authorization\"\n }, \"MPA\"), \"\\nallocation and A-8P on how to properly enter \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manpower Authorization\"\n }, \"MPA\"), \" man-days into the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \").\\nFor additional information and details on missile, munitions, and target\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Munitions, Missiles, and Target\"\n }, \"MMT\"), \") forecasting requirements contact A-5R.\"), mdx(\"p\", null, \"In general, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" pays for most program activities. In the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \", the\\nrequirements \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" funds are labeled \\\"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\\" in the \\\"Funded By\\\" record\\nfield. Resources provided by another command or agency in support of an\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E activity are defined as external resources in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \", and\\nthe agency's name is entered in the \\\"Funded By\\\" record field.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s three largest test activity costs are TDYs, contractor support,\\nand range requirements.\"), mdx(\"p\", null, \"You can determine \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Temporary Duty\"\n }, \"TDY\"), \" costs by using the per diem web site at:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.defensetravel.dod.mil/site/perdiemCalc.cfm\"\n }, \"http://www.defensetravel.dod.mil/site/perdiemCalc.cfm\"), \". Contact A-7K\\nfor contract cost assistance.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" includes test range resources. TRMs contact A-3 and A-5R for\\nassistance with most test ranges. However, for Nevada Test and Training\\nRange (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nevada Test and Training Range\"\n }, \"NTTR\"), \") resources, TRMs should contact A-3/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operating Location\"\n }, \"OL\"), \"-NN and A-8Z. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \":\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not pay for range infrastructure improvements. Rarely will\\ntest infrastructure improvements be a program cost. A-5R and A-8Z\\naddress test infrastructure capability gaps through the SP3, by\\ngathering \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" test activity range infrastructure requirements. Test\\nteams should identify test infrastructure capability gaps as early as\\npossible to allow A-5R and A-8Z sufficient time to advocate requirements\\nto \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" test infrastructure resource organizations.\"), mdx(\"p\", null, \"For missiles, munitions and target (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Munitions, Missiles, and Target\"\n }, \"MMT\"), \") requirements assistance,\\ncontact A-5R.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" includes indirect test activity support requirements (e.g.,\\ncomputers, furniture, copiers, and telephones). It also includes support\\nrequirements that other organizations must coordinate (e.g., telephone\\ninstallation, administrative switchboard and access to facilities,\\nSIPRNet, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Secure Internet Protocol Router Network\"\n }, \"NIPRNet\"), \", red phone). The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" should list all equipment necessary\\nto conduct the test activity that is not already on hand or available\\nthrough current supply inventory. Many of these items are available\\nthrough redistribution from other completed test programs. Contact A-4F\\nfor assistance with existing equipment availability. Whenever possible,\\nTDs/TRMs should plan to use already purchased (warehouse) equipment\\nrather than planning to purchase new equipment. For test activity\\nsupport cost assistance, contact A-8P. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" does not include\\nexpendable equipment items required to conduct test activities.\"), mdx(\"h1\", null, \"Special Access Program Test Resource Plans\"), mdx(\"p\", null, \"Due to various classifications of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" programs, A-3Z, in conjunction\\nwith the Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" and required test team members, prepares an\\ninitial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" once the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" is approved. A-3Z handles \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" TRPs via special\\nprocedures, not via \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s SharePoint. They coordinate funding with\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" Management Office (SAPMO) through proper communication\\nchannels. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"A-3Z must not submit \", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \"-related requirements to SP3\\nactivities without prior approval from \", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s SAPMO\"), \". A-3Z coordinates\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" TRPs with appropriate commands and agencies.\"), mdx(\"h1\", null, \"Test Resource Plan Procedures\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" coordinates TRPs formally twice a year. During the first cycle\\n(Jul--Sep), TDs update and A-5/8 approves all TRPs, then the Detachments\\ndistribute to external stakeholders by 30 Sep. During the second cycle\\n(Jan--Mar) TDs update all TRPs. TRPs that have a test scheduled within\\nthe next 2 years are distributed to external shareholders by 31 Mar. The\\ntest team must keep the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" current to reflect maturing resource\\nrequirements as their test plan develops. When a program or test\\nschedule changes, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" should have the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" assist him/her in revising\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \". Teams coordinate out-of-cycle TRPs to inform program POCs if\\nmajor resource requirements change before the next \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" cycle. Teams\\npublish out-of-cycle TRPs for programs that are new and on a fast track,\\nrestructuring, or undergoing substantial changes (i.e., schedule slips)\\nthat affect budget and resource requirements. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \": Ultimately,\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/CCs must manage their overall program requirements as part of their\\noverall portfolio (a balanced approach to every program and indirect\\nresource required), as opposed to managing individual TRPs. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/CCs\\npresent their respective portfolio status during quarterly financial\\nmanagement review boards, hosted by A\\u20114/7, and during RRBs. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s\\nSAPMO coordinates separate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" presentations.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" distributes TRPs to outside agencies as early as possible to give\\nthem time to program, obtain, and provide resource requirements. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" receive approval from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" to post TRPs (with approved\\nTOs) into the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Collaborative Action Platform (ACAP) for 2-letter\\ncoordination. A-5/8 and A-3 coordinate on all TRPs. If other 2-letters\\n(e.g., A-2/9, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \") or Dets need to provide support, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" TRMs will add\\nthem to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" coord. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" will adjudicate comments and send,\\nvia email, the corrected \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" to A-8P for final standardization/\\nevaluation. Once A-8P verifies comments were adjudicated satisfactorily,\\nthe A-5/8 Director, or designee, approves the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \"'s release to outside\\nagencies. A-8P notifies the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" that the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" is approved for release\\nvia email. Then, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" generates a cover memo for the approved\\nprogram's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \", which the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" signs. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" distributes the\\nsigned memo/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" to POCs on the list, which include organizations\\nsupporting \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", A-3, A-8P, and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"HQ AFOTEC History Office\"\n }, \"HO\"), \". \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \": Due to various\\nclassifications of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" programs, follow A-3Z's guidance on developing,\\nreviewing, coordinating, approving, and distributing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" TRPs. A-3Z\\nfunctions as A-8P and A-5R/8Z for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" TRPs. A-3Z strictly enforces SCGs\\nand may dictate modification of the process for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" TRPs.\"), mdx(\"h1\", null, \"Requirements Review Board\"), mdx(\"p\", null, \"The Requirements Review Board (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \") is an SP3 sub-process that reviews\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s resource requirements for the upcoming and future FYs. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \"\\nexamines resource requirements to determine whether \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" has adequate\\nfunding and manpower resources to perform test activities. A-8P\\ninitiates \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \" preparation in May. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" chairs the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \", which\\noccurs annually in July. After the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" approves the board's\\nresults, the program-owning detachment will update TRPs accordingly.\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \": For \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" programs, coordinate proposed \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \" discussions involving\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" requirements through A-3Z prior to submitting information to A-8Z as\\nan agenda item.\"), mdx(\"h1\", null, \"Basis of Estimate for Test Resources\"), mdx(\"p\", null, \"The basis of estimate for test resources is the compilation of test\\nevents, test methodologies, test scenarios, and the cost estimation\\ntool. It describes why you are testing, what you are going to do, and\\nhow you are going to do it, which forms the basis to estimate resources\\nrequired to execute the test. Underlying the basis of estimate is a set\\nof assumptions validated to the extent possible and then documented. For\\nan \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" and/or test strategy, we focus on high cost (which includes high\\nlevel of effort) and long-lead items (e.g., threats, instrumentation,\\nand \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"). Some of these items were identified previously. When forming\\nthe basis of estimate, consolidate these previously identified items and\\nreview test designs to identify new items. Resources required for COIs,\\ncollectively, may overlap. Identify these areas, and provide a\\nconsolidated list of resources with traceability and rationale.\\nUltimately, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/CCs are responsible for managing their respective\\nportfolios and resources. Table 6-3 contains contents of a basis of\\nestimate.\"), mdx(\"p\", null, \"Table 6\\u20113. Contents of Basis of Estimate\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Content Area\"), mdx(\"th\", null, \"Content Expectations\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"COIs\"), mdx(\"td\", null, \"Reviewing COIs provides insight into what resources may be required to collect data and analyze the results. Instrumentation, databases, data extraction tools and analysis tools are examples of resources that may be required. COIs provide the rationale or basis for these resources.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Test Events\"), mdx(\"td\", null, \"For the particular test designs underlying the test events, a review of the factors and levels provides insight into the resources to establish the conditions. Man-made threats, particular climate (artic, desert, etc.) conditions and terrain are examples of factors and levels that might drive resources. Threats are often expensive or long-lead to develop. Differing climates conditions and terrain could drive multiple deployments. The conditions required to execute the test events provide the rationale or basis for these resources.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Test Methodology\"), mdx(\"td\", null, \"How a set of test events are executed also provides the rationale or basis for resources. Field-testing may incur range costs, or possibly even the development of new range capabilities. M&S incurs both costs and potentially long-lead development. Reviewing the test methodologies provides insight on what might be needed to execute the test events.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Test Scenarios\"), mdx(\"td\", null, \"Test scenarios form the operationally realistic environment. Reviewing all the factors identified in the test design provides insight into the additional assets and test capabilities required to build the operationally realistic scenarios. Many of these factors, particularly the as-is factors, need to be measured and resources identified in order to collect and analyze data when executing the test scenario.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Assumptions\"), mdx(\"td\", null, \"Although assumptions may not directly drive resources, they provide indicators of potential risks and disconnects with other organizations.\")))), mdx(\"h1\", null, \"Initial Resource Estimates\"), mdx(\"p\", null, \"The core team uses the test strategy and/or the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" basis of estimate to\\nrefine resource estimates documented in the initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \". The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \"\\nupdates the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" to support the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" brief. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" review each\\nresource category of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" to determine which line items need costing\\nand which ones \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" must pay. Table 6-4 shows which \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E support costs\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" pays and which it does not pay.\"), mdx(\"p\", null, \"Table 6\\u20114. Operational \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" Support Costs\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Pays\"), mdx(\"th\", null, \"AFOTEC Does Not Pay\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Range costs\")), mdx(\"li\", null, mdx(\"p\", null, \"Equipment Rental\")), mdx(\"li\", null, mdx(\"p\", null, \"Printing and reproduction\")), mdx(\"li\", null, mdx(\"p\", null, \"Communications\")), mdx(\"li\", null, mdx(\"p\", null, \"Real property maintenance and construction\")), mdx(\"li\", null, mdx(\"p\", null, \"Contractor support for OT&E\")), mdx(\"li\", null, mdx(\"p\", null, \"Data reduction\")), mdx(\"li\", null, mdx(\"p\", null, \"Special supplies and equipment\")), mdx(\"li\", null, mdx(\"p\", null, \"Leases\")), mdx(\"li\", null, mdx(\"p\", null, \"Civilian pay for (temporary over hires)\")), mdx(\"li\", null, mdx(\"p\", null, \"Per diem and travel\")), mdx(\"li\", null, mdx(\"p\", null, \"Transportation of equipment required for test\")), mdx(\"li\", null, mdx(\"p\", null, \"Supplies and equipment\")), mdx(\"li\", null, mdx(\"p\", null, \"Dry run planning\")), mdx(\"li\", null, mdx(\"p\", null, \"Test preparation\")), mdx(\"li\", null, mdx(\"p\", null, \"COTS M&S supporting test planning and reporting (including accreditation)\")), mdx(\"li\", null, mdx(\"p\", null, \"Cybersecurity testing (cooperative vulnerability and penetration assessment [CVPA], adversarial assessment [AA])\")))), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Acquisition/modification of the system\")), mdx(\"li\", null, mdx(\"p\", null, \"Aircraft flying hours (other than range support aircraft)\")), mdx(\"li\", null, mdx(\"p\", null, \"Acquisition costs for major test vehicles\")), mdx(\"li\", null, mdx(\"p\", null, \"Cost of procuring test item or direct test item support. Maintaining the test item is the funding responsibility of the owning command. Includes contractor services and supply items to maintain the test item and fuel for the test item.\")), mdx(\"li\", null, mdx(\"p\", null, \"Missiles, munitions and targets\")), mdx(\"li\", null, mdx(\"p\", null, \"Telemetry kits\")), mdx(\"li\", null, mdx(\"p\", null, \"Range infrastructure\")), mdx(\"li\", null, mdx(\"p\", null, \"Type-1 (contractor) training and associated TDYs\")), mdx(\"li\", null, mdx(\"p\", null, \"Digital M&S that produces data for OT&E\")), mdx(\"li\", null, mdx(\"p\", null, \"M&S V&V\"))))))), mdx(\"h1\", null, \"Resource Management During Test\"), mdx(\"p\", null, \"Some tests are scheduled to be executed over an extended period. If\\ncurrent \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fiscal Year\"\n }, \"FY\"), \" costs exceed funding, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" engages with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \" and program\\noffice to determine whether the test event can be slipped until \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nhas sufficient funds, or whether the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \" is willing to provide funds to\\nkeep the current schedule. To support this decision, we must update the\\nprogram's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \". The elements of resource management for the test team do\\nnot change during test execution. An important test team best practice\\nis to rely on the resource manager/financial analyst during test\\nexecution so that the test team can devote more time to test events and\\nanalysis. Once test execution begins, resources are considered dedicated\\nand generally unavailable for reassignment until the test is completed.\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \": Report to A-4/7, immediately, significant changes to costs\\nanticipated or encountered during test execution.\"), mdx(\"h1\", null, \"Funds Management\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \", and financial analyst must track funding levels in all\\nestablished accounts. It is easy to over-obligate the travel account by\\nprocessing a lot of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Temporary Duty\"\n }, \"TDY\"), \" orders for test team augmentees and deployments.\\nYou can deplete the test range account quickly with unprojected flight\\ntest events. If you do not manage accounts properly, it may be months\\nbefore you realize the account is overdrawn. You are never authorized to\\noperate in the red. If you discover an expense (range or flight\\nactivity) that will drive your test into the red, contact A-4/7\\nimmediately so they can secure funds through the appropriate program\\noffice, or initiate a pause test until they can secure additional\\nfunding.\"), mdx(\"h1\", null, \"Government Purchase Card\"), mdx(\"p\", null, \"The government purchase card (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purchase Card\"\n }, \"GPC\"), \") is useful to purchase common supply\\nitems locally. If an unusual situation arises where you need to use the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purchase Card\"\n }, \"GPC\"), \", call the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"'s financial management personnel or A-7F to get a\\nfinancial ruling before you make the expenditure. Each Detachment has a\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purchase Card\"\n }, \"GPC\"), \" cardholder. If you have questions concerning the use of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purchase Card\"\n }, \"GPC\"), \",\\ncall the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purchase Card\"\n }, \"GPC\"), \" program manager in A-7K. Never use the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purchase Card\"\n }, \"GPC\"), \" for\\nunnecessary or unauthorized items. Improper purchases violate the law\\nand you could be punished and have to repay the charges personally.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#detachment-test-resource-manager","title":"Detachment Test Resource Manager"},{"url":"#test-resource-cost-estimation-tool","title":"Test Resource Cost Estimation Tool"},{"url":"#test-resource-plan","title":"Test Resource Plan"},{"url":"#special-access-program-test-resource-plans","title":"Special Access Program Test Resource Plans"},{"url":"#test-resource-plan-procedures","title":"Test Resource Plan Procedures"},{"url":"#requirements-review-board","title":"Requirements Review Board"},{"url":"#basis-of-estimate-for-test-resources","title":"Basis of Estimate for Test Resources"},{"url":"#initial-resource-estimates","title":"Initial Resource Estimates"},{"url":"#resource-management-during-test","title":"Resource Management During Test"},{"url":"#funds-management","title":"Funds Management"},{"url":"#government-purchase-card","title":"Government Purchase Card"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-3-resources.md"},"frontmatter":{"metaTitle":"Resources","metaDescription":"Resources"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"912205be-c578-5818-a620-3d648c16f8af"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file
sites/oteguide/page-data/OT&E_Guide/6-4-coordination-across-afotec/page-data.json
View file @ 784fbeaf
{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-4-coordination-across-afotec","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"7a8a0eda-6ef1-52d2-940b-21ffd416e153","title":"Coordination Across AFOTEC","slug":"/OT&E_Guide/6-4-coordination-across-afotec"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Coordination Across AFOTEC\",\n \"metaTitle\": \"Coordination Across AFOTEC\",\n \"metaDescription\": \"Includes various business processes applied across AFOTEC (coordination processes, tasking orders, risk management, documentation, contract support, etc.)\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"h1\", null, \"Directorate Roles and Responsibilities\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" A-staff (2-ltr) personnel play a valuable role when staffing test\\nproducts. They are responsible for ensuring the Detachment produces\\ntimely, high-quality products (e.g., test strategies, initial test\\ndesigns, test concept developments, test plans, test reports) and\\noutcomes (e.g., test execution, test analysis). They provide Dets a\\nvariety of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" processes, procedures, tools, and reviews, and facilitate\\nand participate in product development activities such as ITDs and\\nmeasures workshops. They also provide technical reviews of products\\nduring 2-ltr coord before they go up to the command section for\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" approval/signature. A-staff roles and responsibilities include\\nthe following:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-2/9 ensures technical adequacy. This includes test design, test\\nmeasures (in particular, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are not confused with MOPs or MOSs),\\nrelevant threat environments, data collection methods, scoring,\\nanalysis, modeling and simulation, and test capability\\naccreditation.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 leads overall development, management, and execution of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" products, processes, procedures, tools, and reviews with support\\nfrom A-2/9, A-5/8 and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \". A-3 ensures operational sufficiency. This\\nincludes operational processes (missions, operations, tasks,\\nactivities) and operational conditions. In addition, A-3 ensures\\nquality, effective feedback, and timeliness for internal and\\nexternal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" products not delegated to Dets or directorates.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-5/8 ensures compliance with policy and accurate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" development.\\nA-5/8 assesses test resource sufficiency, reviews requirements,\\nidentifies test infrastructure requirements, manages and oversees\\nMOAs/MOUs, and activation/ deactivation of Dets and OLs.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" advises on systems safety requirements and analysis and ensures\\ncompliance with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" standards during test planning and execution.\"))), mdx(\"p\", null, \"It is paramount that \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" test teams coordinate with A-3 when developing\\nnew products. Dets tailor and adapt products to meet testing timelines\\nand coordinating those products with A-3 enables parties to stay in sync\\nwith the way ahead. Maintaining a running dialogue with A-3 ensures a\\nsmoother coordination process and quality products.\"), mdx(\"p\", null, \"Before test documents (plans, reports, etc.) receive approval for\\nrelease, whether at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" level, they must be operationally\\nsufficient and technically adequate.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Operational sufficiency: The breadth of operations addressed while\\nemploying new or modified capabilities within the context of\\nrepresentative employment and support concepts. The evaluation is\\nconsidered operationally sufficient if it provides the decision\\nmaker and warfighter results from test events executed across\\nsufficient operational conditions. The evaluation must identify\\ncapabilities and limitations associated with employment, as well as\\ndetermine effectiveness and suitability.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Technical adequacy: Addresses the relevance of the technical\\ninformation produced by the test in relation to the purpose of the\\ntest (i.e., test events address operationally relevant questions). A\\ntest is technically adequate if the test data evaluation provides\\nthe acquisition decision maker information to inform the relevant\\ndecision.\"))), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s goal is to deliver combat capability as rapidly as possible. We\\nstrive to maintain our well-established reputation for relevant,\\ncredible, and timely test reporting with accurate, balanced, and timely\\ninformation throughout the acquisition continuum.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Accurate\"), \": Information will be precise in analysis and\\nevaluation to ensure the narrative and ratings are consistent and\\nconclusions are defendable.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Balanced\"), \": Narrative highlights both system capabilities and\\nlimitations.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Timely\"), \": Delivered to decision makers with time to review and\\nunderstand the results prior to the decision date.\"))), mdx(\"h1\", null, \"Signature and Approval\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" will delegate signature or approval authority \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \" the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Information Files\"\n }, \"OTIF\"), \"\\ncurrently in effect.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#directorate-roles-and-responsibilities","title":"Directorate Roles and Responsibilities"},{"url":"#signature-and-approval","title":"Signature and Approval"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-4-coordination-across-afotec.md"},"frontmatter":{"metaTitle":"Coordination Across AFOTEC","metaDescription":"Includes various business processes applied across AFOTEC (coordination processes, tasking orders, risk management, documentation, contract support, etc.)"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"7a8a0eda-6ef1-52d2-940b-21ffd416e153"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} {"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-4-coordination-across-afotec","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"7a8a0eda-6ef1-52d2-940b-21ffd416e153","title":"Coordination Across AFOTEC","slug":"/OT&E_Guide/6-4-coordination-across-afotec"},"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n \"title\": \"Coordination Across AFOTEC\",\n \"metaTitle\": \"Coordination Across AFOTEC\",\n \"metaDescription\": \"Includes various business processes applied across AFOTEC (coordination processes, tasking orders, risk management, documentation, contract support, etc.)\"\n};\nvar layoutProps = {\n _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n var components = _ref.components,\n props = _objectWithoutProperties(_ref, [\"components\"]);\n\n return mdx(MDXLayout, _extends({}, layoutProps, props, {\n components: components,\n mdxType: \"MDXLayout\"\n }), mdx(\"h1\", null, \"Directorate Roles and Responsibilities\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" A-staff (2-ltr) personnel play a valuable role when staffing test\\nproducts. They are responsible for ensuring the Detachment produces\\ntimely, high-quality products (e.g., test strategies, initial test\\ndesigns, test concept developments, test plans, test reports) and\\noutcomes (e.g., test execution, test analysis). They provide Dets a\\nvariety of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" processes, procedures, tools, and reviews, and facilitate\\nand participate in product development activities such as ITDs and\\nmeasures workshops. They also provide technical reviews of products\\nduring 2-ltr coord before they go up to the command section for\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" approval/signature. A-staff roles and responsibilities include\\nthe following:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-2/9 ensures technical adequacy. This includes test design, test\\nmeasures (in particular, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are not confused with MOPs or MOSs),\\nrelevant threat environments, data collection methods, scoring,\\nanalysis, modeling and simulation, and test capability\\naccreditation.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 leads overall development, management, and execution of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" products, processes, procedures, tools, and reviews with support\\nfrom A-2/9, A-5/8 and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \". A-3 ensures operational sufficiency. This\\nincludes operational processes (missions, operations, tasks,\\nactivities) and operational conditions. In addition, A-3 ensures\\nquality, effective feedback, and timeliness for internal and\\nexternal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" products not delegated to Dets or directorates.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-5/8 ensures compliance with policy and accurate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" development.\\nA-5/8 assesses test resource sufficiency, reviews requirements,\\nidentifies test infrastructure requirements, manages and oversees\\nMOAs/MOUs, and activation/ deactivation of Dets and OLs.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" advises on systems safety requirements and analysis and ensures\\ncompliance with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" standards during test planning and execution.\"))), mdx(\"p\", null, \"It is paramount that \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" test teams coordinate with A-3 when developing\\nnew products. Dets tailor and adapt products to meet testing timelines\\nand coordinating those products with A-3 enables parties to stay in sync\\nwith the way ahead. Maintaining a running dialogue with A-3 ensures a\\nsmoother coordination process and quality products.\"), mdx(\"p\", null, \"Before test documents (plans, reports, etc.) receive approval for\\nrelease, whether at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" level, they must be operationally\\nsufficient and technically adequate.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Operational sufficiency: The breadth of operations addressed while\\nemploying new or modified capabilities within the context of\\nrepresentative employment and support concepts. The evaluation is\\nconsidered operationally sufficient if it provides the decision\\nmaker and warfighter results from test events executed across\\nsufficient operational conditions. The evaluation must identify\\ncapabilities and limitations associated with employment, as well as\\ndetermine effectiveness and suitability.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Technical adequacy: Addresses the relevance of the technical\\ninformation produced by the test in relation to the purpose of the\\ntest (i.e., test events address operationally relevant questions). A\\ntest is technically adequate if the test data evaluation provides\\nthe acquisition decision maker information to inform the relevant\\ndecision.\"))), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s goal is to deliver combat capability as rapidly as possible. We\\nstrive to maintain our well-established reputation for relevant,\\ncredible, and timely test reporting with accurate, balanced, and timely\\ninformation throughout the acquisition continuum.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Accurate\"), \": Information will be precise in analysis and\\nevaluation to ensure the narrative and ratings are consistent and\\nconclusions are defendable.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Balanced\"), \": Narrative highlights both system capabilities and\\nlimitations.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Timely\"), \": Delivered to decision makers with time to review and\\nunderstand the results prior to the decision date.\"))), mdx(\"h1\", null, \"Signature and Approval\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" will delegate signature or approval authority \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \" the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Information Files\"\n }, \"OTIF\"), \"\\ncurrently in effect.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#directorate-roles-and-responsibilities","title":"Directorate Roles and Responsibilities"},{"url":"#signature-and-approval","title":"Signature and Approval"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-4-coordination-across-afotec.md"},"frontmatter":{"metaTitle":"Coordination Across AFOTEC","metaDescription":"Includes various business processes applied across AFOTEC (coordination processes, tasking orders, risk management, documentation, contract support, etc.)"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes","title":"Fielding Combat Capability"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways","title":"Acquisition Pathways"}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles","title":"Adaptive Relevant Testing Principles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit","title":"Test Lifecycle: Exit"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking","title":"Tasking"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training","title":"Team Training"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices","title":"Best Practices"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","title":"Air Force Agency for Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","title":"Modeling and Simulation Coordination Office"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary","title":"Summary"}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance","title":"Governance"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources","title":"References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","title":"The Operational Test and Evaluation Construct"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","title":"Operational Test and Evaluation Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","title":"Construct Development Meetings"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","title":"Using a Core Team Approach."}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","title":"Documenting the Operational Test and Evaluation Construct "}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","title":"ELEMENTS OF THE TEST PLANNING PROCESS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW","title":"OVERVIEW"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification","title":"Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize","title":"Characterize"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","title":"GOALS AND TYPES OF TEST"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","title":"TYPES OF TEST DESIGNS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs","title":"Augmented Designs"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","title":"Designs for Computer Experiments"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","title":"Test Designs for Comparing Systems"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","title":"Optimal Designs (Computer Generated Designs)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials","title":"Factorials"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","title":"Test Designs for Problem Identification"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases","title":"Cases"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations","title":"Demonstrations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","title":"Combinatorial Designs (Covering Arrays)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","title":"TEST DESIGN MEASURES OF MERIT"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","title":"Comparing Measures of Merit"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization","title":"Randomization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication","title":"Replication"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","title":"Best Practices and Pitfalls in Test Design"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance","title":"Test Design Guidance"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","title":"Executive Summary, Body, and Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key","title":"Consistency is Key"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","title":"TYPICAL SITUATIONS"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates","title":"Templates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice","title":"One Voice"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes","title":"Footnotes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options","title":"Microsoft Word Options"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas","title":"Focus Areas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","title":"Next Page and Page Breaks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages","title":"Blank Pages"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers","title":"Headers and Footers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization","title":"Capitalization"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","title":"Citing Air Force (or Other Military) Bases"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables","title":"Tables"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists","title":"Vertical Lists"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","title":"Numbering Tables and Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences","title":"Choppy Sentences"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","title":"Hyphens, En Dashes, and Em Dashes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering","title":"Page Numbering"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","title":"Symbols and Units of Measure"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings","title":"Classification Markings"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List","title":"Distribution List"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents","title":"Table of Contents"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","title":"TEST ACTIVITY SEQUENCE"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/7-Ratings-for-Continuous-and-Cumulative-Feedback","title":"Ratings for Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/6-RATING-TENETS-AND-PRINCIPLES","title":"RATING TENETS AND PRINCIPLES"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","title":"Vocabulary of Lessons Learned"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance","title":"Policy Guidance"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-6-Milestone-and-Event-Triggers","title":"Milestone and Event Triggers"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-8-Dissemination","title":"Dissemination"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-9-Lessons-Learned-(Resolution)","title":"Lessons Learned (Resolution)"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-7-Observations-Review","title":"Observations Review"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/8-RATING-MEASURES","title":"RATING MEASURES"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-1-CONCLUSION","title":"CONCLUSION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-2-OBSERVATION-SHEET","title":"OBSERVATION SHEET"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/2-3-INTERVIEW-SHEET","title":"INTERVIEW SHEET "}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1:-FUNDAMENTALS-OF","title":"SECTION 1: FUNDAMENTALS OF"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A:-CATEGORIES-OF-MEASURES","title":"APPENDIX A: CATEGORIES OF MEASURES"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2:-MEASURES-DEVELOPMENT","title":"SECTION 2: MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3:-MEASURE-DOCUMENTATION","title":"SECTION 3: MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/9-RATING-CRITICAL-OPERATIONAL-ISSUES","title":"RATING CRITICAL OPERATIONAL ISSUES "}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-B:-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B: MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/9-APPENDIX-C:-CYBER-RELATED-MEASURES","title":"APPENDIX C: CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/7-Continuous-Measures","title":"Continuous Measures"}}}]}},"pageContext":{"id":"7a8a0eda-6ef1-52d2-940b-21ffd416e153"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]}
\ No newline at end of file \ No newline at end of file

UNCLASSIFIED